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

Re: SAX: Next Round (Lexical Event Handler)

• From: David Megginson <david@m...>
• To: David Brownell <db@E...>
• Date: Sun, 31 Jan 1999 16:28:44 -0500 (EST)

David Brownell writes:

 > > > I haven't checked, but I think that this gives us everything we need
 > > > for DOM level one.
 > 
 > Doesn't quite ... there's some more DTD information needed to:
 > 
 > 	*  ensure that PIs within the DTD (e.g. internal subset)
 > 	   don't show up anywhere in the DOM tree (ugh);

You can determine this using the start/end DTD events and start/end
entity events, I think.

 > 	*  see declarations of external general entities;

Do we need the declarations, or just the boundaries -- or, in other
words, do we need to provide information about declared but unused
external parsed entities?  Sorry I'm too lazy to puzzle this out from
the spec right now.

 > 	*  expose values of defaults so that the DOM can ensure
 > 	   that defaulted attributes always have values;

The parser should take care of this.

 > 	*  distinguish attributes which were defaulted from those
 > 	   that were explicitly in the document.

Yes, this is necessary, as a few others have also pointed out
(grumble, grumble).

 > (In addition the above, if XML namespaces are to be layerable over
 > a normal XML 1.0 parser, declarations of all other entities need to
 > be exposed so they can be examined for conformance:  they must not
 > contain colons!)

This is probably overkill for SAX -- if someone wants to layer
namespaces on top of SAX, they'll have to miss this one.

 > > I wonder whether LexicalHandler ought to extend DocumentHandler.  The
 > > events it reports are synchronous with the events reported by
 > > DocumentHandler.  It seems to me that applications are always going to
 > > want to implement either DocumentHandler or both DocumentHandler and
 > > LexicalHandler.

Probably -- the problem is that if we extend Parser then we'll have
both a setDocumentHandler and a setLexicalDocumentHandler event, and
that causes some funny problems that I'd rather punt.


All the best,


David

-- 
David Megginson                 david@m...
           http://www.megginson.com/

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i...
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo@i... the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• References:
  • SAX: Next Round
    • From: <david@m...>
  • Re: SAX: Next Round (Lexical Event Handler)
    • From: James Clark <jjc@j...>
  • Re: SAX: Next Round (Lexical Event Handler)
    • From: David Brownell <db@E...>

• Prev by Date: Re: XML query engines: was RE: Is XML dead already or what?
• Next by Date: Re: What is XML for?
• Previous by thread: Re: SAX: Next Round (Lexical Event Handler)
• Next by thread: Re: SAX: Next Round
• Index(es):
  • Date
  • Thread