- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 06 Mar 2009 10:06:10 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4901 --- Comment #2 from Michael Kay <mike@saxonica.com> 2009-03-06 10:06:10 --- ACTION-A-392-12 invited me to produce a proposal to resolve this. The proposal is as follows (using the XSLT 2.0 specification as the baseline): 1. No change is needed to section 5.3 (Constructor functions for xs:QName and xs:NOTATION) 2. In the table in 17.1, change the entry for QName->NOTATION to "M" (maybe), and that for NOTATION->QName to "Y". 3. In 17.1.1 (Casting from string) in the paragraph starting "Casting is permitted from xs:string literals to xs:QName and types derived from xs:NOTATION...", delete the word "respectively". 4 Add a new section 17.1.9 Casting to xs:QName and xs:NOTATION Casting from xs:string or xs:untypedAtomic to xs:QName or xs:NOTATION is specified in section 17.1.1. It is also possible to cast from xs:NOTATION to xs:QName, and from xs:QName to any type derived by restriction from xs:NOTATION. (Casting to xs:NOTATION itself is not allowed, because xs:NOTATION is an abstract type.) The resulting xs:QName or xs:NOTATION has the same prefix, local name, and namespace URI parts as the supplied value. -- 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 Friday, 6 March 2009 10:06:20 UTC