SAX: Attributes and Entity Resolution

[Paul Prescod]

David Megginson wrote:
> 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?  

I think that we can define a general "map" interface that will translate
easily into any language and is more general than attributes. As SAX
supersets are created it can return notations by name, entities by name,
element types by name and so forth. My concerns with the attributeEvent
interface are:

 * an implication that attributes are ordered
 * performance (I often ignore more attributes than I use -- I don't
want one interface-lookup-based method call per attribute)
 * either 
	* the non-intuitive convention of having attributes FIRST or
	* the inconvenience of having them come later

When I process a start-tag, I want all of the attributes to be queriable
and I would much rather not be forced to gather them up myself.

 Paul Prescod
--
http://itrc.uwaterloo.ca/~papresco

Art is always at peril in universities, where there are so many people, 
young and old, who love art less than argument, and dote upon a text 
that provides the nutritious pemmican on which scholars love to chew. 
				-- Robertson Davies in "The Cunning Man"



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