W3C home > Mailing lists > Public > uri@w3.org > September 2003

RE: URNs for 'naming authority assignment', not 'permanent'

From: <Patrick.Stickler@nokia.com>
Date: Wed, 17 Sep 2003 12:30:55 +0300
Message-ID: <A03E60B17132A84F9B4BB5EEDE57957B02630325@trebe006.europe.nokia.com>
To: <LMM@acm.org>, <skw@hp.com>
Cc: <uri@w3.org>, <urn-nid@lists.verisignlabs.com>, <leslie@thinkingcat.com>, <thiemann@acm.org>, <Patrick.Stickler@nokia.com>

> -----Original Message-----
> From: ext Larry Masinter [mailto:LMM@acm.org]
> Sent: 16 September, 2003 21:25
> To: 'Williams, Stuart'
> Cc: uri@w3.org; urn-nid@lists.verisignlabs.com; 
> leslie@thinkingcat.com;
> thiemann@acm.org
> Subject: URNs for 'naming authority assignment', not 'permanent'
> When you define a URI scheme, you are expected to define the
> access semantics of the scheme -- how it is that a receiver
> of a URI in the scheme is supposed determine the resource
> that the URI identifies. For 'http', the definition URIs with
> the http scheme is in the HTTP protocol specification, and
> the definition is tied to the HTTP protocol.  (People might
> use HTTP URIs in other ways to indicate something else, but
> that use isn't part of the definition of the HTTP scheme.)

I thought this was one of the shortcomings of HTTP, that one
cannot know based on the representations one might GET what
exactly is denoted by the http: URI.

The HTTP protocol seems only to be telling you how to obtain
representations of whatever is denoted by the URI, not how to
obtain the actual semantics/denotation of the URI.



Patrick Stickler
Nokia, Finland
Received on Wednesday, 17 September 2003 05:31:06 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:06 UTC