W3C home > Mailing lists > Public > xml-uri@w3.org > September 2000

RE: I-D ACTION:draft-daigle-uri-std-00.txt

From: Henrik Frystyk Nielsen <frystyk@microsoft.com>
Date: Thu, 7 Sep 2000 12:30:59 -0700
Message-ID: <009001c01902$2a9794e0$fb4c1fac@redmond.corp.microsoft.com>
To: "Simon St.Laurent" <simonstl@simonstl.com>, <XML-uri@w3.org>
> I've had more than enough
> epistemology and language theory to appreciate the
> distinction between a
> name and a thing and the perilous connections between them.

Apparently not - you are mixing up the name and the description of the
thing the name identifies.

> Does http://www.w3.org/1999/xhtml refer to that Web page
> alone?  I don't think so.

The Web page is one manifestation of that resource - there may be others.
You are likely to be told in the HTTP response whether there are others
and how they differ.

> >> >For "elements of the common syntax", the equality operation
> >> is defined by
> >> >RFC 2396. For everything else, you use case-sensitive matching.
> >>
> >> That's not specified anywhere I've seen, except in the
> >> Namespaces in XML
> >> Rec that got us into these problems in the first place.
> >
> >No, the XML-NS doesn't make it clear that the first part of
> the sentence
> >is true.
> It makes it clear that the second sentence is true.

which is not enough.

> >RFC 2396 specifies the equality rules for each common syntax element.
> But it doesn't provide equality rules for URIs that don't use
> the common
> syntax elements - and acknowledges the possibility of such cases.

Yes it does - it is the "opaque_part" BNF construction. By default,
elements are case-insensitive, the exceptions are listed in section 6.

Received on Thursday, 7 September 2000 15:30:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:32:44 UTC