2548 2005-11-22 03:44:49 +0000 [XQuery] Change namespace binding for anyAtomicType, yearMonthDuration and dayTimeDuration 2007-02-25 23:48:46 +0000 1 1 1 Unclassified XPath / XQuery / XSLT XQuery 1.0 Candidate Recommendation All All CLOSED FIXED P2 normal --- 1 kuanhui jonathan.robie public-qt-comments oldest_to_newest 7256 0 kuanhui 2005-11-22 03:44:50 +0000 Kindly consider changing the namespace binding for anyAtomicType, yearMonthDuration and dayTimeDuration to http://www.w3.org/2001/XMLSchema rather than http://www.w3.org/2005/xpath-datatypes Either that or propose to the XML Schema 1.1 working group to retain the bindings to http://www.w3.org/2005/xpath-datatypes. Kindly reference :- XML Schema 1.1 Part 2: Datatypes Working Draft dated 24 February 2005 http://www.w3.org/TR/2005/WD-xmlschema11-2-20050224/#anyAtomicType-def http://www.w3.org/TR/2005/WD-xmlschema11-2-20050224/#yearMonthDuration http://www.w3.org/TR/2005/WD-xmlschema11-2-20050224/#dayTimeDuration Otherwise, with the subsequent introduction of XML Schema 1.1, redundancies (and ambiguities) will be introduced into the 3 (current) xdt types. I see no harm in binding anyAtomicType, yearMonthDuration and dayTimeDuration to xs rather than xdt. If this issue has been dealt with before, kindly enlighten me on the considerations. Thank you. Kuan Hui 8022 1 jonathan.robie 2006-01-27 22:21:48 +0000 I agree - in fact, I have written on this at http://blogs.datadirect.com/jonathan_robie/2006/01/archaeology_and.html. Both of your suggestions are logically reasonable, but I prefer the first suggestion, to use the XML Schema namespace. After all, these are types that are used explicitly in schema declarations, and for all other such types, we use the XML Schema type name, which is in the XML namespace. At the time we wrote the Candidate Recommendation, Schema 1.1 Datatypes had not been published as a Working Draft, so this was not possible. 8391 2 liam 2006-02-22 23:14:03 +0000 Thank you for your comment. At a joint face-to-face meeting the XSL WG, XML Query WG and Schema WG discussed this issue (which had also been raised internally at W3C). I have marked this issue as closed, "fixed" -- please feel free to reopen it if you are not satisified with the following resolution: Here is the resolution: The XQuery Working Group has discussed this question with the XML Schema Working Group, which has given us permission to move xdt:anyAtomicType, xdt:yearMonthDuration, and xdt:dayTimeDuration in the XML Schema namespace "http://www.w3.org/2001/XMLSchema", along with xdt:untyped, and xdt:untypedAtomic. We will rename these types to xs:anyAtomicType, xs:yearMonthDuration, xs:dayTimeDuration xs:untyped, and xs:untypedAtomic. At that point, all XQuery built-in types will be defined in the XML Schema namespace. Although this change may cause some short term difficulties, we believe this simplifies our type system in the long run, and will benefit users of both XQuery and XML Schema. Because XML Schema 1.1 is still only a Working Draft, these types are defined in the XQuery and XPath Data Model specification in XQuery 1.0 and XPath 2.0. The XML Schema Working Group has added some of these types to the current XML Schema 1.1 Working Draft [1]. We will coordinate with the XML Schema Working Group as the two specifications progress. [1] http://www.w3.org/TR/2006/WD-xmlschema11-2-20060116/#status 14158 3 jim.melton 2007-02-25 23:48:46 +0000 Closing bug because commenter has not objected to the resolution posted and more than two weeks have passed.