Hey,
On 17 Apr 2008, at 17:42, John Snelson wrote:
-------- Original Message --------
Subject: Re: Xerces-C API changes for XQilla
Date: Thu, 17 Apr 2008 16:31:57 +0100
From: John Snelson <[EMAIL PROTECTED]>
Reply-To: [email protected]
To: [email protected]
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
Hi Boris,
Boris Kolpackov wrote:
John Snelson <[EMAIL PROTECTED]> writes:
1) Problem:
XPath 2.0 is just different to XPath 1.0. We've therefore got our
own
version of DOMXPathResult (XPath2Result) which makes more sense in
this
context:
http://xqilla.sourceforge.net/docs/dom3-api/classXPath2Result.html
Solution:
It's probably simple enough to either extend DOMXPathResult to
include
the extra functionality in XPath2Result, or to include it as a new
class
called DOMXPath2Result.
I did a quick check and it appears that the DOMXPathResult is very
similar to DOMXPath2Result. I would therefore suggest that we try
to add the missing functionality to DOMXPathResult as non-standard
extensions (though we should try to use names that will likely be
used in the next version of DOM3 when it is updated to include
support for XPath 2, for example getIntegerValue instead of asInt).
What is your feeling on this approach? Also did you base your
DOMXPath2Result on any draft spec (e.g., where do the asDouble,
asInt, etc., names come from)?
XPath2Result wasn't based on any draft spec IIRC. Gareth probably
remembers more about it's design, since I wasn't heavily involved in
Pathan at the time.
It was off some draft note. Some conversation and the note is here:
http://lists.w3.org/Archives/Public/www-dom/2003JulSep/0125.html
Gareth--
Gareth Reakes, CTO WE7
+44-20-7117-0809 http://www.we7.com
