W3C home > Mailing lists > Public > public-rdf-in-xhtml-tf@w3.org > January 2009

Re: Validation issue with the xsi namespace

From: Christoph LANGE <ch.lange@jacobs-university.de>
Date: Sun, 25 Jan 2009 00:16:59 +0100
To: Toby A Inkster <mail@tobyinkster.co.uk>
Cc: Shane McCarron <shane@aptest.com>, Stephane Corlosquet <stephane.corlosquet@deri.org>, RDFa <public-rdf-in-xhtml-tf@w3.org>
Message-Id: <200901250017.00432.ch.lange@jacobs-university.de>
On Saturday 24 January 2009 23:51:47 Toby A Inkster wrote:
> In general XML terms, a namespace plus local name do not "expand" to
> anything - they are simply a pair. The idea of expanding them is RDF-
> specific. This is why there are a number of namespace URIs that do
> not end in a hash or slash - they are like that because they were
> never intended to be used as RDF vocabularies. e.g. the XHTML
> namespace is "http://www.w3.org/1999/xhtml".

Thanks, I just hadn't thought of that, i.e. that (namespace,localname) is just
a pair.

> One thing I've noticed in the hash vs slash discussion is that '='
> and '?' are rarely talked about as suitable final characters for
> namespace URIs. They seem ideal to me. e.g.
> 	xmlns:ex1="http://example.com/myterms?term="
> 	xmlns:ex2="http://example.net/some-vocab?"

Indeed.  No idea.  Maybe the reason for not using such namespace URIs is that
their semantics is less well defined than what Shane recapitulated for / and
#.  IIRC, it's basically up to the web server application how to interpret
such URLs.



Christoph Lange, Jacobs Univ. Bremen, http://kwarc.info/clange, Skype duke4701

Received on Saturday, 24 January 2009 23:17:19 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:30 UTC