W3C home > Mailing lists > Public > public-qt-comments@w3.org > December 2008

[Bug 6275] New: [XQuery 1.1] Computed Namespace Constructors

From: <bugzilla@wiggum.w3.org>
Date: Thu, 04 Dec 2008 15:11:06 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-6275-523@http.www.w3.org/Bugs/Public/>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=6275

           Summary: [XQuery 1.1] Computed Namespace Constructors
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XQuery 1.1
        AssignedTo: jonathan.robie@redhat.com
        ReportedBy: mike@saxonica.com
         QAContact: public-qt-comments@w3.org


This relates to the public WD dates 3 December 2008.

Section 3.7.3.7 Computed Namespace Constructors

1. A trivial typo: "creates a new namespacee node,"

2. The current text says:

...the prefix expression is evaluated as follows: Atomization is applied to the
result of the name expression. If the result of atomization [is] a single
atomic value of type xs:NCName, xs:string, or xs:untypedAtomic, it is used as
the prefix property of the newly constructed namespace node.

2a: missing "is" where shown

2b: "xs:NCName or xs:string" is redundant. If it's an xs:NCName then it will
also be an xs:string.

2c: there needs to be a rule that it must be valid as an NCName. I would
suggest:

...the prefix expression is evaluated as follows: Atomization is applied to the
result of the name expression. If the result of atomization is a single atomic
value of type xs:string or xs:untypedAtomic, it is cast to type xs:NCName
(which may raise an error FORG0001) and the result is used as the prefix
property of the newly constructed namespace node.

3. Section 3.7.4: It seems to me that error XQTY0102 should be XQDY0102. It's a
dynamic error not a type error.

4. The newly-introduced error codes (XQ**0096 onwards), unlike all the older
error codes, have no link to the term "static error", "dynamic error", or "type
error" in their descriptions. Some of them include the term, but unlinked;
others do not include the term at all.


-- 
Configure bugmail: http://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 Thursday, 4 December 2008 15:11:15 UTC

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