John Snelson wrote:
Boris Kolpackov wrote:
John Snelson <[EMAIL PROTECTED]> writes:
I'm not so sure about that. The existing DOMXPathResult is an
implementation of a W3C published DOM interface, and I think there's
value in keeping it that way. There's all sorts of improvements I'd like
to make to W3C DOM otherwise ;-).
Here are some of the reasons why I believe we should merge the two
interfaces:
1. The XPath 2 interface supports requirements of XPath 1.
2. It is my understanding (from talking to various people and reading
the W3C mailing lists) that the XPath 1 DOM interface is commonly
believed to be a half-backed work that is full of holes and omissions
mainly because it was done in a hurry to get it into the DOM spec.
To me personally the fact that the official interface of NSResolver
does not allow the user to specify custom namespace-prefix mappings
makes it clear that the authors of the spec had no real-world
experience in this area.
3. There won't be any revisions to the DOM spec so there is no hope
of the official support for XPath 2.
So I think, as far as the XPath part of the DOM spec is concerned, we
should try to make the interface sensible rather than trying to conform
to the spec. I chatted to Alberto and he also thinks that we should
rather generalize the interface. Any thoughts?
That makes sense, and the fact that the W3C Web API group took control
of the spec makes me think that the W3C might change it anyway. I guess
I'm agnostic about what to do - does anyone else have any opinions?
We normally err on the side of supporting interfaces for the standard
reasons. In this case I don't really mind either way.
Gareth
--
Gareth Reakes, CTO WE7
+44-20-7117-0809 http://www.we7.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
