"Costello, Roger L." <costello@mitre.org> wrote on 08/16/2010 11:16:24 AM:
> I wrote:
>
> >> 6. What XML parsers support XInclude?
>
> And Michael Glavassevich responded:
>
> > Both Xerces-J and Xerces-C++ have support for XInclude.
>
> Michael, do you mean that XInclude in built _within_ the Xerces-J
> and Xerces-C++ XML parsers? Or, do you mean that the Xerces-J and
> Xerces-C++ XML parsers are _supplemented_ (extended) with XInclude?
In Xerces-J it is exposed though the JAXP API, the same interfaces that one uses to invoke the parser. So in that sense it is "built-in" to the parser, but agree that XInclude is logically a separate thing that one could put anywhere in their pipeline (and can define it declaratively with a language like XProc [1]). Someone willing to dive into the XNI layer of Xerces-J could compose their own component pipeline with XInclude anywhere they want it (e.g. before or after schema validation).
I think the XInclude support in Xerces-C++ is decoupled; some kind of utility which takes a DOM as input which processes the <xi:include>s.
> /Roger
>
>
> _______________________________________________________________________
>
> XML-DEV is a publicly archived, unmoderated list hosted by OASIS
> to support XML implementation and development. To minimize
> spam in the archives, you must subscribe before posting.
>
> [Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
> Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
> subscribe: xml-dev-subscribe@lists.xml.org
> List archive: http://lists.xml.org/archives/xml-dev/
> List Guidelines: http://www.oasis-open.org/maillists/guidelines.php
Thanks.
[1] http://www.w3.org/TR/xproc/#c.xinclude
Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: mrglavas@ca.ibm.com
E-mail: mrglavas@apache.org