• From: David Ornstein <davido@p...>
• To: David Megginson <ak117@f...>
• Date: Sun, 04 Jan 1998 15:31:19 -0800

David Megginson wrote [02:45 PM 1/4/98 ]:

>ATTRIBUTES
>----------
>
>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);

I assume that this approach mandates that the Client accumulate these and
then use them when the element comes along.  Yick.  It's OK, but not great.
 I'd rather the interface.  I don't much buy the argument that adding
another interface (or even two more) will lead us straight to DOM.


================================
David Ornstein
Pragmatica, Inc.
http://www.pragmaticainc.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: Attributes and Entity Resolution
    • From: David Megginson <ak117@f...>

• Prev by Date: SAX: Attributes and Entity Resolution
• Next by Date: Re: SAX: Attributes
• Previous by thread: SAX: Attributes and Entity Resolution
• Next by thread: Re: SAX: Attributes and Entity Resolution
• Index(es):
  • Date
  • Thread