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

Re: [Sax-devel] XInclude and SAX Incompatibility

• To: <xml-dev@l...>,<sax-devel@l...>,<sax-users@l...>,"Peter McCracken" <peterjm@c...>
• Subject: Re: [Sax-devel] XInclude and SAX Incompatibility
• From: "Karl Waclawek" <karl@w...>
• Date: Tue, 24 Jun 2003 12:00:46 -0400
• References: <OF0F3DE394.DD9D2F6F-ON85256D4F.0054A8CF@t...>

> (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],
> [3].  In SAX, this means sending DTD events.

Why? These are not declarations. They are reported by the content handler.

> SAX specifies that no DTD
> events can be sent after the endDTD/startElement event.  However, there is
> no way of knowing which unparsed entities and notations must be sent until
> after element events start being processed.  

What do you mean? Unparsed entity and Notation declarations are reported
before the EndDTD event, so you know which ones are declared before
the first StartElement call.

Maybe I am mis-understanding you?

Karl

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

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