Re: now://example.org/car (was lack of consensus on httpRange-14)

Micah Dubinko wrote:
>...
> 
> b) URIs in general can identify anything. http:// URIs can identify anything
> that's network-accessible. thingy:// URIs (meaning something like ChrisL's
> now:// or LarryM's tbd:// without getting hung up on the name) can identify
> anything non-network-accessible.

You talk about b) but there are really b) and c). In one variant there 
is a way of turning the non-dereferencable URI into a dereferencable one 
using client-side string manipulations. In other words these URIs are 
ultimately dereferencable but a little bit of syntax prevents them from 
being directly so.

In the other, there is no such manipulation. These URIs are truly not 
dereferencable. This is attractive for some people because it implies no 
reliance on some particular protocol (usually HTTP) or on some 
particular DNS host.

 > ...
> Another reason to examine b) is that a non-dereferencable URI can have a
> fragment identifier that doesn't rely on the representation--which could be
> a way for RDF to keep on doing what it's doing, with a good explanation for
> why # has special significance!

I don't see how that follows.

  Paul Prescod

Received on Monday, 7 October 2002 19:03:14 UTC