W3C home > Mailing lists > Public > public-qt-comments@w3.org > March 2010

[Bug 9183] New: [XPath 2.1] Dynamic invocation of xs:QName or xs:NOTATION constructor functions

From: <bugzilla@wiggum.w3.org>
Date: Wed, 03 Mar 2010 22:37:47 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-9183-523@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9183

           Summary: [XPath 2.1] Dynamic invocation of xs:QName or
                    xs:NOTATION constructor functions
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Platform: All
               URL: http://www.w3.org/XML/Group/qtspecs/specifications/xquer
                    y-11/html/xpath-21.html#id-constructor-functions
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XPath 2.1
        AssignedTo: jonathan.robie@redhat.com
        ReportedBy: zongaro@ca.ibm.com
         QAContact: public-qt-comments@w3.org


According to section 3.11.4, "The constructor functions for xs:QName and for
types derived from xs:QName and xs:NOTATION require their arguments to be
string literals or to have a base type that is the same as the base type of the
target type; otherwise a type error [err:XPTY0004] is raised."

Consider the following expression.

(xs:QName#1)('abc')

Does the fact that the argument to the dynamic function invocation is a string
literal satisfy the constraint quoted in 3.11.4?  I suspect this was intended
to raise an error. . .  but perhaps not.  As things stand I think no error
should be reported.

Any decision on the static context issues raised in bug 9139 probably has a
direct bearing on this one.


-- 
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 Wednesday, 3 March 2010 22:37:49 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:59 GMT