- From: Henrik Frystyk Nielsen <frystyk@microsoft.com>
- Date: Mon, 19 Jun 2000 21:48:34 -0700
- To: "David Carlisle" <david@dcarlisle.demon.co.uk>
- Cc: <XML-uri@w3.org>
> That isn't the `Case A' that James referred to. The two URI are > different URI, the fact that they are equivalent in the http scheme > does not mean that they are the same URI or that they name the same > namespace. Using xpath one can distinguish elements in those two > namespaces and so could apply different styles to them using xsl or > any other namespace aware language. Three questions (with answers): * Who is the naming authority of DNS? (DNS) * Who defines the semantics and propertied of DNS hostnames? (DNS) * Can somebody else (us for example) redefine these semantics and properties of DNS names? (No) Assigning different semantics at the NS level to two names that at the authoritative namespace owner are identical is a clear case A scenario: DNS at the bottom, an NS app using a namespace including DNS name on top. > An XSL processor must reject as a stylesheet a document in a namespace > that differs from the specified namespace in any way, including case > differences. You still haven't told me what that is or why you can't use a GUID which doesn't have the case-sensitivity problem or even relative/absolute problem. Then the rest of us can use more useful URIs for what we want to do. > > You pick the namespace > > you want with the semantics you want > > The semantics I want are the semantics provided by the namepace spec: Nope, it doesn't provide any knowledge about the URI spaces used what so ever. > But applying arbitrary uri scheme specific normalisations is just > completely out of the question. Could you please point me to what (if anything) in my previous mail [1] reflects this statement? Henrik [1] http://lists.w3.org/Archives/Public/xml-uri/2000Jun/0718.html
Received on Tuesday, 20 June 2000 00:49:17 UTC