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

Re: Element navigation additions

From: Joseph Kesselman <keshlam@us.ibm.com>
Date: Wed, 14 Apr 2004 12:46:10 -0400
To: Robin Berjon <robin.berjon@expway.fr>
Cc: www-dom@w3.org
Message-ID: <OF7FFDA41C.B4C93B9C-ON85256E76.005B4238-85256E76.005C1E26@us.ibm.com>





When XPath ran into similar issues -- specifically, when they wanted to
consider an element the parent of its attributes, despite their not being
children -- the DOM's response was that, while we were willing to given
them an ownerElement attribute on Attrs so this navigation was possible, we
were not willing to accept and implement their definition of parent; it was
their responsibility to write their implementation of XPath's parent
operation so that when run over a DOM it Did The Right Thing.

Frankly, I think the response to SVG's request should be similar. There's
nothing wrong with a firstNonTextChild operation being provided by the SVG
abstract data model. But I don't see any strong reason it has to be a
property of the DOM Node, rather than an operation provided by SVG which
may be applied to a DOM Node.

______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
Received on Wednesday, 14 April 2004 12:47:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:13:57 GMT