OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: XInclude vs SAX vs validation

A side question is : is it really possible to validate any document against
any DTD (replace with XSDL or RELAX NG or other) within a SAX pipeline ?
Shouldn't the validation module be exposed as a SAX ContentHandler, so that
we could plug it in at the stage we want in the SAX pipeline, thus resolving
your problem (it would suffice to put the XInclude processor before the
validator in the pipeline) ?

I don't really like the way validation is handeld by parsers right now. We
just have control other the fact that the parser validates or not, and
that's all. I'd like to be able to choose when the document is validated
(placing the validation as a SAX processing stage in a pipeline). I'd also
like to be able to specify an arbitrary DTD or XSDL instance or whatever to
validate against through an API, not by writing it inside the document.


>-----Message d'origine-----
>De : Julian Reschke [mailto:julian.reschke@gmx.de]
>Envoyé : mardi 21 août 2001 17:38
>À : xml-dev@lists.xml.org
>Objet : XInclude vs SAX vs validation
>it seems that implementing XInclude on the SAX layer is a reasonable
>approach. Not having worked a lot with SAX before, I'd approach it by
>writing a SAX filter, catching XInclude instructions and 
>generating new SAX
>My question is: how would this affect validation against a DTD? From my
>understanding, validation normally happens at a lower level, so it is
>already done when I receive a SAX event, right?
>The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
>initiative of OASIS <http://www.oasis-open.org>
>The list archives are at http://lists.xml.org/archives/xml-dev/
>To subscribe or unsubscribe from this elist use the subscription
>manager: <http://lists.xml.org/ob/adm.pl>