[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: [Sax-devel] XInclude and SAX Incompatibility

• To: "Peter McCracken" <peterjm@c...>, xml-dev@l...,sax-devel@l...
• Subject: Re: [Sax-devel] XInclude and SAX Incompatibility
• From: Elliotte Rusty Harold <elharo@m...>
• Date: Tue, 24 Jun 2003 15:27:58 -0400
• In-reply-to: <OF0F3DE394.DD9D2F6F-ON85256D4F.0054A8CF@t...>
• References: <OF0F3DE394.DD9D2F6F-ON85256D4F.0054A8CF@t...>

At 11:40 AM -0400 6/24/03, Peter McCracken wrote:

In general streaming processes are known to have the issues with 
XInclude you've encountered. There's no good solution, but several 
changes were made to XInclude in previous drafts to ameliorate the 
problems.

>(1) When attributes with references to unparsed entities or notations are
>encountered in included documents, these unparsed entities and notations
>must be added to the [unparsed entities] and [notations] properties of the
>document information item, as defined in the XML Infoset specification [2],

Actually no. That's a may, not a must. XInclude implementations are 
not required to support notation and unparsed entity information 
items/properties.

>(2) The XInclude spec allows document fragments to be included using
>XPointer [4] paths.  These create lots of problems with stream-based
>processing.  For instance, an XML document could include a fragment of
>itself which has already been processed, and unless the document stream can
>be re-opened and reparsed, that information is not available.

Yes, that's tricky. In general however, I would claim it is possible 
to reopen and reparse a stream in this circumstance. You can only 
point to the stream with an XPointer if it has a URL. Given that it 
has a URL you can open it. The content at the URL may be time varying 
but that it is not an issue unique to streaming implementations of 
XInclude.

>My team and I thought it would be best to bring this up with the SAX
>community, so that the issue of XInclude support with SAX is made public.
>Perhaps the restriction on DTD events in the SAX API could be adjusted to
>account for the possibility of unparsed entity and notation events occuring
>after the end of the DTD events?

No, I don't think SAX needs to change. Given the very limited use of 
unparsed entities and notations in the community today, I think 
simply omitting them from the subset of the infoset that is handled 
is fully adequate for almost all practical purposes.
-- 

   Elliotte Rusty Harold
   elharo@m...
   Processing XML with Java (Addison-Wesley, 2002)
   http://www.cafeconleche.org/books/xmljava
   http://www.amazon.com/exec/obidos/ISBN%3D0201771861/cafeaulaitA

• References:
  • XInclude and SAX Incompatibility
    • From: "Peter McCracken" <peterjm@c...>

• Prev by Date: Re: Re: [Sax-devel] XInclude and SAX Incompatibility
• Next by Date: Re: Re: [Sax-devel] XInclude and SAX Incompatibility
• Previous by thread: Re: [Sax-devel] XInclude and SAX Incompatibility
• Next by thread: Re: [Sax-devel] XInclude and SAX Incompatibility
• Index(es):
  • Date
  • Thread