This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
XML Query has agreed to put their datatypes into the XML Schema namespace, including the untyped values (untypedAtomic, untypedAny). What mention or treatment, if any, should XML Schema 1.1 make of these "un"types.
We don't seem to have an immediate use for them (unless we wish to replace 'absent' type definitions with xsd:untypedAny and xsd:untypedAtomic). So I propose that we inform QT that we don't plan to mention them, giving QT the opportunity to explain to us that we should, and why, and how. Or alternatively we might add a Note to the section that introduces the namespaces (the same place we added the note on the relation between the 1.0 and 1.1 namespaces), saying that there are some other things in the namespace, defined by the QT specs. And (as a matter of namespace policy) there might be more in the future.
On 20 October 2006 the WG agreed to resolve this issue by adding a Note to the section of the spec where the namespaces are introduced, saying Note: The data model used by [XPath 2.0] and other specifications, namely [XDM] makes use of type labels (untyped, untypedAtomic) not defined in this specification; see the [XDM] specification for details of those types. Also by adding a paragraph to the section: Users of the namespaces defined here should be aware, as a matter of namespace policy, that more names may be defined in these namespaces in future versions of this or other specifications. And by adding a reference in the Informative References to [XDM] XQuery 1.0 and XPath 2.0 Data Model (XDM) http://www.w3.org/TR/xpath-datamodel/ These changes have now been integrated into the status quo text of the spec and will be included in due course in the next published working draft.