- From: Henrik Frystyk Nielsen <frystyk@microsoft.com>
- Date: Thu, 22 Jun 2000 15:02:59 -0700
- To: <xml-uri@w3.org>, "David G. Durand" <david@dynamicDiagrams.com>, <masinter@attlabs.att.com>
- Cc: <xml-uri@w3.org>
> >I think it should be noted, that the examples that David has put forward > >are not solved at all by fixed base. He wants to be able to say that > >http://WWW.W3.ORG is semantically different from http://www.w3.org even > >though this breaks in a number of ways and falls in the category of "don't > >do that". In fact, he has pointed out that he would prefer java class > >names instead. > > Larry Masinter has contradicted you on exactly this point (I don't > have a record as to who he was responding to). Argument from > authority is probably not admissible, but given his evidence, and his > authority, I think we can lay the case insensitivity issue in DNS > names to rest permanently. > > That's just not part of URIs. I assume you refer to [1] (it took me less than 30 secs to find it so the fact that you didn't look it up and read what it said takes away almost anything you say). However, I should point out that I can't see any conflict between what Larry and I say although I would let Larry speak for himself. My point is that somebody defining a namespace MUST NOT assign different semantics to two names that according to the properties of the URI space are the same name. This doesn't mean that an application consuming a document with namespace identifiers have to now any normalization rules at all - and what I think Larry points out is that an application generating a document using namespace identifiers MUST NOT rely on those normalization rules. In fact, this is very much in alignment with what I said. Henrik [1] http://lists.w3.org/Archives/Public/xml-uri/2000Jun/0091.html
Received on Thursday, 22 June 2000 18:03:49 UTC