W3C home > Mailing lists > Public > public-qt-comments@w3.org > May 2013

[Bug 21893] New: [XP30] Casting to QName - error codes

From: <bugzilla@jessica.w3.org>
Date: Wed, 01 May 2013 10:47:39 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-21893-523@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21893

            Bug ID: 21893
           Summary: [XP30] Casting to QName - error codes
    Classification: Unclassified
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XPath 3.0
          Assignee: jonathan.robie@gmail.com
          Reporter: mike@saxonica.com
        QA Contact: public-qt-comments@w3.org

XPath 3.0 claims in 2.5.2 that casting to a namespace-sensitive type raises
XPTY0117 if the prefix is not in scope.

This is incorrect. F+O, which has the definitive specification for casting,
says this is a dynamic error FONS0004.

This must be a dynamic error rather than a type error because it depends on
knowledge of the actual supplied value.

XPTY0117 is in fact a different error: it is raised when an untypedAtomic value
is supplied to a function that expects a QName (regardless whether the prefix
is in scope or not). The error is correctly described in 3.1.5.2 (function
conversion rules) but is wrongly described in the error codes appendix.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 1 May 2013 10:47:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:43 UTC