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

RE: SAX2: DeclHandler

• From: Khun Yee Fung <kyeefung@e...>
• To: XMLDev list <xml-dev-digest@i...>
• Date: Wed, 22 Dec 1999 10:31:12 -0500

I have a question. Right now, the Xerces SAX implementation calls the
comment() method when a comment is encountered in a DTD. Is this the
intended behaviour?

As to whether element and attribute declarations are useful for downstream
processing. I did find a use. In XPath, there is a function called 'id()'
which returns a node with a certain ID. Without getting access to the DTD,
it is actually quite difficult to find out which attribute is the ID of an
element.

Regards,
Khun Yee Fung

		-----Original Message-----
		From:	David Megginson [mailto:david@m...]
<mailto:[mailto:david@m...]> 
		Sent:	Wednesday, December 22, 1999 9:35 AM
		To:	XMLDev list
		Subject:	SAX2: DeclHandler

		Here's the DeclHandler that we designed for SAX2alpha, with
		IOException replacing SAXException in the throws clauses:

		  public interface DeclHandler
		  {
		    public void elementDecl (String name, String model)
throws IOException;
		    public void attributeDecl (String eName, String name,
String type,
					       String valueDefault, String
value)
		      throws IOException;
		    public void internalEntityDecl (String name, String
value)
		      throws IOException;

		    public void externalEntityDecl (String name, String
publicId,
						    String systemId)
		      throws IOException;
		  }

		Notes:

		1. Unparsed entity and notation declarations are reported by
the (now
		   confusingly-named) DTDHandler.  The distinction is that
the XML 1.0 
		   REC requires parsers to report unparsed-entity and
notation
		   declarations, but not other DTD-based declarations.

		2. The model argument in elementDecl is a normalized string
		   representation of a content model.  It's not ideal, but
everyone
		   agreed last time that it was workable.

		This interface seems hopelessly anachronistic, and I'm not
willing to
		invest too much time in it -- after all, while DTDs are
useful in
		themselves, the declarations should hardly form part of
downstream
		processing -- but enough people want it that it's useful to
include it
		as an optional feature.


		All the best,


		David

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

		xml-dev: A list for W3C XML Developers. To post,
mailto:xml-dev@i... <mailto:xml-dev@i...> 
		Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
<http://www.lists.ic.ac.uk/hypermail/xml-dev/>  and on CD-ROM/ISBN
981-02-3594-1
		To unsubscribe, mailto:majordomo@i...
<mailto:majordomo@i...>  the following message;
		unsubscribe xml-dev
		To subscribe to the digests, mailto:majordomo@i...
<mailto:majordomo@i...>  the following message;
		subscribe xml-dev-digest
		List coordinator, Henry Rzepa (mailto:rzepa@i...
<mailto:rzepa@i...> )


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/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:majordomo@i... the following message;
unsubscribe xml-dev
To subscribe to the digests, mailto:majordomo@i... the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@i...)

• Follow-Ups:
  • Re: SAX2: DeclHandler
    • From: David Megginson <david@m...>

• Prev by Date: SAX2: Parser interface
• Next by Date: SAX2: Features and Properties
• Previous by thread: Re: SAX2: DeclHandler
• Next by thread: Re: SAX2: DeclHandler
• Index(es):
  • Date
  • Thread