W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2012

[Bug 15637] [QT3] K2-Axes-54

From: <bugzilla@jessica.w3.org>
Date: Fri, 20 Jan 2012 09:30:23 +0000
To: public-qt-comments@w3.org
Message-Id: <E1RoAnf-0001Uk-SW@jessica.w3.org>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15637

Tim Mills <tim@cbcl.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID

--- Comment #2 from Tim Mills <tim@cbcl.co.uk> 2012-01-20 09:30:23 UTC ---
No, it looks as if it is me who is confused, however, I'm sure I've just
introduced support for the namespace axis in XQuery 3.0 to get some test or
other to pass.

On investigation, it turns out that

fn-name-27
fn-string-27

have a dependency on the "namespace-axis" feature rather than a dependency on
the specification version.  Would it be worth removing the little used
"namespace-axis" dependency in favour of a specification dependency?  It's only
used a few times in

fn/generate-id.xml (twice)
fn/local-name.xml (once)
fn/name.xml (once)
fn/path.xml (thrice)
fn/string.xml (once)

I too wish there wasn't this difference between XPath and XQuery.  It's just
confusing.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 20 January 2012 09:30:29 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:47 UTC