W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > January to March 2001

RE: URIs and information typing

From: Jonathan Borden <jborden@mediaone.net>
Date: Thu, 8 Mar 2001 00:18:11 -0500
To: "Eric van der Vlist" <vdv@dyomedea.com>
Cc: "Simon St.Laurent" <simonstl@simonstl.com>, <xml-dev@lists.xml.org>, <www-xml-schema-comments@w3.org>
Message-ID: <00a301c0a78f$2ba9e3d0$0201a8c0@ne.mediaone.net>
Eric van der Vlist wrote:
> Jonathan Borden wrote:
> >
> > right, so: "xsd:unsignedInt" is just shorthand for
> > http://www.w3.org/2000/10/XMLSchema#unsignedInt -- which is references a
> > location in the XML Schema schema <simpleType id="unsignedInt">... ?
> If I am not mistaken, the association is done though the id attribute
> that has been added to the simpleType element in order to make sure that
> the fragment id "http://www.w3.org/2000/10/XMLSchema#unsignedInt" points
> to the corresponding element of the schema.
> This is working fine with schemas having a stable location that is
> pointed by this namespace and which element names are duplicated by
> their ids,  such as http://www.w3.org/2000/10/XMLSchema, however, the
> fragment identifier "http://example.com/ns/example#mytype" would not
> point to the definition of "myns:mytype" if the schema location was
> anything else than "http://example.com/ns/example" or if the id of the
> simpleType element wouldn't match its id.

this is a big problem. it is unacceptable to have different W3C recs having
completely different and, on reading CR XML Schema-1 20001024, arbitrary
rules for mapping XML QNames to [namespace name, localname] pairs or to URI.
The rules for constructing a text/xml or application/xml fragment id are
indicated by RFC 3023 as XPointer, and (IMHO) it is essential that a QName
have a direct and unambiguous interpretation as a URI. XML Schema datatypes
are (again IMHO) otherwise broken.

Received on Thursday, 8 March 2001 00:16:50 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:49:54 UTC