W3C home > Mailing lists > Public > www-dom@w3.org > April to June 1998

Re: iterators, etc. + Attribute question

From: Mike Champion <mcc@arbortext.com>
Date: Tue, 2 Jun 1998 09:29:05 -0400
Message-Id: <98Jun2.092619edt.26884@thicket.arbortext.com>
To: Claude Zervas <claude@utlco.com>, www-dom@w3.org
At 01:20 AM 6/2/98 -0400, Claude Zervas wrote:
>At 09:34 AM 6/1/98 -0400, Mike Champion wrote:
>>At 03:31 AM 6/1/98 -0400, Claude Zervas wrote:

>But I would still like to know if the Attribute interface should
>inherit from Node or not because Element.getAttributes() is very
>handy but since it returns a NodeIterator (in the current spec)
>I'm kind of confused. I'm assuming there is a typo either in the
>declaration of the Attribute interface or in the declaration
>of Element.getAttributes() but I can't know which. Kent Tamura's (IBM)
>implementation of Attribute inherits from Node but this may just
>be to facilitate the implementation. Am I missing something here?
>The prose is pretty unhelpful on this, it mentions "attrubute node"
>but does not explicitly state or show inheritance of Node.

Give us a week; there's a face to face DOM WG meeting coming up, and this
will be resolved.  My best guess is that individual attributes will
continue to be Nodes, the set of attributes will be a NodeList with
associative array semantics (or AttributeList).  

To answer your question in another message, the whole point of
AttributeList is to provide associative array semantics so that attributes
can be looked up by name.  NamedNodeList was once used as the name for
this, but we found that attributes were the only objects that needed these

Mike Champion
Received on Tuesday, 2 June 1998 09:30:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:04 UTC