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 3172 - [FO] 5.1 Constructor Functions: exception for QName and NOTATION
Summary: [FO] 5.1 Constructor Functions: exception for QName and NOTATION
Status: CLOSED LATER
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: Functions and Operators 1.0 (show other bugs)
Version: Candidate Recommendation
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ashok Malhotra
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-01 17:33 UTC by Michael Dyck
Modified: 2007-02-25 23:28 UTC (History)
0 users

See Also:


Attachments

Description Michael Dyck 2006-05-01 17:33:55 UTC
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?
Comment 1 Ashok Malhotra 2006-05-09 15:51:23 UTC
The sections that discuss the constructor functions for QName and NOTATION have been heavily reworked as a result of our decisions on Bug 2678.  Please look at the revised sections in the draft of the F&O that will be published shortly and let us know if your concerns have been addressed.
Comment 2 Jim Melton 2007-02-25 23:28:18 UTC
Closing bug because commenter has not objected to the resolution posted and more than two weeks have passed.