This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 29610 - Differing namespace definitions for xqt-errors
Summary: Differing namespace definitions for xqt-errors
Status: RESOLVED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XQuery 3.0 (show other bugs)
Version: Working drafts
Hardware: All All
: P2 major
Target Milestone: ---
Assignee: Jonathan Robie
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-05 14:51 UTC by Adam Retter
Modified: 2016-09-08 19:21 UTC (History)
3 users (show)

See Also:


Attachments

Description Adam Retter 2016-05-05 14:51:56 UTC
The namespace for errors described in this document https://www.w3.org/2005/xqt-errors/, says that the namespace is "https://www.w3.org/2005/xqt-errors/"

However in this document https://www.w3.org/TR/xquery-30, it says that the namespace for errors is "http://www.w3.org/2005/xqt-errors".

Note that one has a trailing '/' in the namespace whilst the other does not.
I also note that XPath 2.0, 3.0, and 3.1, and XQuery 1.0, and 3.1 are all consistent with XQuery 3.0 in not having a trailing '/'.

Which one is correct I wonder? I note that Saxon uses http://www.w3.org/2005/xqt-errors, however eXist is using http://www.w3.org/2005/xqt-errors/
Comment 1 Josh Spiegel 2016-05-05 15:06:56 UTC
XQuery and FNO appear to consistently use "http://www.w3.org/2005/xqt-errors".  I don't think the namespace document is considered a normative reference.
Comment 2 Adam Retter 2016-05-05 16:45:33 UTC
(In reply to Josh Spiegel from comment #1)
> XQuery and FNO appear to consistently use
> "http://www.w3.org/2005/xqt-errors".  I don't think the namespace document
> is considered a normative reference.

I don't see either a formal normative or non-normative reference to that document in the XQuery 3.0 spec... perhaps there should be one, which would make whether it is normative or non-normative explicit.

IMHO the specs should at least be consistent in the naming of the namespace regardless though.
Comment 3 Josh Spiegel 2016-05-05 17:37:18 UTC
The namespace document should be fixed but I don't think there can be a normative reference to it.

"Only W3C Recommendations should be referenced normatively. If a W3C document is not a "W3C Recommendation", do not reference it normatively."
https://www.w3.org/2013/02/stdref
Comment 4 Michael Kay 2016-05-10 17:02:34 UTC
The place to fix this appears to be line 9 (plus possibly line 8) in qtspecs/specifications/xpath-functions-31/src/ns-errors.xml

8: <!ENTITY doc.publoc "http://www.w3.org/2005/&doc.nsname;/">
9: <!ENTITY nsname     "http://www.w3.org/2005/&doc.nsname;/">

Both should probably have the trailing slash removed; but since these are actual HTTP resources we will also need to get a redirect from the wrong URL to the correct one.
Comment 5 Andrew Coleman 2016-07-08 13:13:51 UTC
This was resolved with the following action item:

ACTION A-643-05:  Andy to investigate how to solve Q2.3.2 Bug 29610 - 
Differing namespace definitions for xqt-errors.

The fix was applied to ns-errors.xml in F&O
Comment 6 Adam Retter 2016-08-07 23:08:24 UTC
@andy This document - https://www.w3.org/2005/xqt-errors/ still states: `https://www.w3.org/2005/xqt-errors/`.

So is it now that we have two namespaces for the same thing, i.e. `https://www.w3.org/2005/xqt-errors` used from F+O and `https://www.w3.org/2005/xqt-errors/` used in the "XQuery and XPath Functions and Operators Error Codes Namespace Document" document itself?

I am still confused :-/
Comment 7 Andrew Coleman 2016-09-08 19:21:57 UTC
Hi Adam - we haven't published the latest drafts yet.  The fix to the namespace document can be viewed here:
https://www.w3.org/XML/Group/qtspecs/specifications/xpath-functions-31/html/ns-errors.html

When we next publish (PR) this will replace the document at https://www.w3.org/2005/xqt-errors/

Hope that makes sense.