- From: <bugzilla@jessica.w3.org>
- Date: Tue, 30 Apr 2013 20:25:35 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21882
Michael Kay <mike@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |mike@saxonica.com
Resolution|--- |INVALID
--- Comment #2 from Michael Kay <mike@saxonica.com> ---
The relevant rules are in F+O section 18.2. To quote:
The supplied string is mapped to a typed value of the target type as defined in
[XML Schema Part 2: Datatypes Second Edition]. Whitespace normalization is
applied as indicated by the whiteSpace facet for the datatype. The resulting
whitespace-normalized string must be a valid lexical form for the datatype. The
semantics of casting follow the rules of XML Schema validation.
I think you have overlooked the rule about whitespace normalization. The
whitespace facet for xs:normalizedString is "replace". This means that the
first thing casting does is x09, x0A, and x0C by x20; after this replacement
the value is within the lexical space of xs:normalizedSpace and casting
therefore succeeds.
The rules in 18.2 take precedence over those in 18.3.3 by virtue of the fifth
paragraph of section 18 which states: "When casting from xs:string or
xs:untypedAtomic the semantics in 18.2 Casting from xs:string and
xs:untypedAtomic apply, regardless of target type."
I am therefore closing this as invalid.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 30 April 2013 20:25:36 UTC