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

SAX: Attributes and Entity Resolution

  • From: David Megginson <ak117@f...>
  • To: xml-dev Mailing List <xml-dev@i...>
  • Date: Sun, 4 Jan 1998 17:45:52 -0500

sax attribute
During our discussion this weekend, we have had two excellent
proposals for additional SAX interfaces, beyond just XmlParser and

1. An interface for entity resolution, rather than using a
   resolveEntity callback.

2. An interface for attributes, rather than using


While I agree that a full entity manager would be more powerful than a
simple callback, I am not certain that the power will really be needed
by most SAX users; furthermore, if it is needed, that functionality
can be supplied more generally by an HTTP or FTP proxy server.  For
now, then, I recommend that we stick with the resolveEntity callback,
which is simple to use and to learn, but provides 80% of the required
functionality (that's 80% in the abstract 80/20 sense).


The good arguments and patient explanations of list members have
convinced me that java.lang.Dictionary is unsuitable for three
reasons: because it is a base class rather than an interface, because
it is already deprecated in Java 1.2, and (most importantly) because
there is no single, obvious equivalent in other programming languages.

So what do we do?  It is certainly tempting to introduce a new
interface for attribute resolution, and that in itself would not bloat
SAX too much, but if we did that, why not add other interfaces?  It
would be nice, for example, to have an Element interface, an Entity
interface, a PI interface, a characterData interface, etc., all of
which implement useful functionality; in the end, we will have
rewritten the DOM.

The alternative is to return to what I had originally done with
Ælfred, and generate a separate event for each attribute:

  public void attribute (String elementName, String aname, String value);

For example, with the following markup

  <para id="p1" level="advanced">This is a paragraph.</para>

We would have five SAX events:

  attribute:    elementName="para" aname="id" value="p1"
  attribute:    elementName="para" aname="level" value="advanced"
  startElement: name="para"
  charData:     ch="This is a paragraph."
  endElement:   name="para"

This is not pretty, but it is simple, and should translate cleanly to
all languages.  I am far from decided on this point, and encourage
further public discussion.

All the best,


David Megginson                 ak117@f...
Microstar Software Ltd.         dmeggins@m...

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...)


Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Buy Stylus Studio Now

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Don't miss another message! Subscribe to this list today.
First Name
Last Name
Subscribe in XML format
RSS 2.0
Atom 0.3

Stylus Studio has published XML-DEV in RSS and ATOM formats, enabling users to easily subcribe to the list from their preferred news reader application.

Stylus Studio Sponsored Links are added links designed to provide related and additional information to the visitors of this website. they were not included by the author in the initial post. To view the content without the Sponsor Links please click here.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member
Stylus Studio® and DataDirect XQuery ™are products from DataDirect Technologies, is a registered trademark of Progress Software Corporation, in the U.S. and other countries. © 2004-2013 All Rights Reserved.