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

[Bug 3172] [FO] 5.1 Constructor Functions: exception for QName and NOTATION

From: <bugzilla@wiggum.w3.org>
Date: Mon, 01 May 2006 17:33:55 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1FacHT-00076o-SP@wiggum.w3.org>

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

           Summary: [FO] 5.1 Constructor Functions: exception for QName and
                    NOTATION
           Product: XPath / XQuery / XSLT
           Version: Candidate Recommendation
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Functions and Operators
        AssignedTo: ashok.malhotra@oracle.com
        ReportedBy: jmdyck@ibiblio.org
         QAContact: public-qt-comments@w3.org


5.1 Constructor Functions for XML Schema Built-in Types
'The semantics of the constructor function " xs:TYPE(arg) " are identical to
the semantics of " arg cast as xs:TYPE? ", except for constructors for xs:QName
and types derived from xs:NOTATION which are identical to "cast as xs:TYPE ".'

--- Presumably, that last snippet is missing "arg". That is, it should be
         arg cast as xs:TYPE

--- Note that the XQuery doc (3.12.5) doesn't include the exception for
    xs:QName and types derived from xs:NOTATION.

--- But it seems to me that the exception isn't necessary. Two paragraphs
later,
    we're told that, in the cases covered by this exception, the argument is
    constrained to be a string literal. Thus, the cast expression's atomization
    is guaranteed to result in a single string value, in which case the result
    of
        arg cast as xs:TYPE
    is the same as
        arg cast as xs:TYPE?
    Isn't it?
Received on Monday, 1 May 2006 17:34:06 UTC

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