- From: Garret Wilson <garret@globalmentor.com>
- Date: Tue, 02 Sep 2003 16:51:14 -0700
- To: www-rdf-interest@w3.org
In RDF, to get a URI from a qname, one concatenates the URI designated by the prefix with the local name. For example, rdf:Description yields http://www.w3.org/1999/02/22-rdf-syntax-ns#Description. So what about XML Schema? The RDF Primer ( http://www.w3.org/TR/2003/WD-rdf-primer-20030815/ ) uses the resource http://www.w3.org/2001/XMLSchema#integer which, working backwards, yields xsd:integer iff the namespace to XML Schema is http://www.w3.org/2001/XMLSchema# . In fact, the RDF primer says that it is: <blockquote> Primer examples will also use several "well-known" QName prefixes (without explicitly specifying them each time), defined as follows: ... prefix xsd:, namespace URI: http://www.w3.org/2001/XMLSchema# </blockquote> Unfortunately, the XML Schema specification itself ( http://www.w3.org/TR/xmlschema-2/#namespaces ) says that the XML Schema namespace is http://www.w3.org/2001/XMLSchema (without the ending pound sign). Isn't the XML Schema specification authoritative here? I'm guessing why there's a discrepancy: we'd rather not look at a URI like http://www.w3.org/2001/XMLSchemastring or http://www.w3.org/2001/XMLSchemaint . But what justifies changing the XML Schema namespace URI? Should we change the XLink namespace, too, so we have http://www.w3.org/1999/xlink#href instead of http://www.w3.org/1999/xlinkhref? Can RDF do that unilaterally? If I missed some new RDF rule that clears all this up, let me know. Thanks, Garret
Received on Tuesday, 2 September 2003 19:51:26 UTC