You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2019/12/19 17:27:00 UTC

[jira] [Closed] (DOXIA-238) define a Sink Object Model in terms of a XSD

     [ https://issues.apache.org/jira/browse/DOXIA-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Elliotte Rusty Harold closed DOXIA-238.
---------------------------------------

> define a Sink Object Model in terms of a XSD
> --------------------------------------------
>
>                 Key: DOXIA-238
>                 URL: https://issues.apache.org/jira/browse/DOXIA-238
>             Project: Maven Doxia
>          Issue Type: Wish
>          Components: Sink API
>            Reporter: Lukas Theussl
>            Priority: Major
>
> From DOXIA-236:
> A thought with regard to event order/nesting: What about defining a Sink Object Model in terms of a XSD? This tree structure should not be expressed by a programmatic API but merely serves as a reference for parser validation. I.e. a CanonicalSink would output the XML document
> {code:xml}
> <sink>
>   <head>
>     <title>
>       <text>foo</text>
>      </title>
>    </head>
> </sink>
> {code}
> for the event sequence head(), title(), text("foo"), _title(), _head(). This tree could then be passed through a validating XML parser (conveniently wrapped in a ValidatingSink, superceding the WellformednessCheckingSink) to check that the parser obeys the ordering/nesting rules defined by the XSD. Of course, the XSD would also serve the purpose of documenting the intended usage of the Sink API to implementors.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)