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

Hi David,

Yeah, by "now:" I mean an agreed-upon DNS-based non-dereferenceable scheme.
(I also took Chris's comment in the minutes to mean the same) It could even
be "urn:" based. IANA registration would probably eventually be appropriate
were this not a hypothetical discussion.

Mainly, I'm just naïvely curious if something along these lines could help
resolve conflicting views on URIs. Introducing new schemes is costly, I
know, but

1) a non-dereferencable scheme has a smaller cost
and
2) it might be less than the cost of ongoing confusion with the status-quo

Thanks,

.micah

-----Original Message-----
From: David Orchard [mailto:dorchard@bea.com]
Sent: Friday, October 04, 2002 3:38 PM
To: 'Micah Dubinko'; www-tag@w3.org
Cc: chris@w3.org; GK@ninebynine.org
Subject: RE: //example.org/car (was lack of consensus on httpRange-14)


Seems that it doesn't matter what the scheme is, beit "now" or "id" or
"foo", as long as there are no methods defined in the IANA registry.  If
that's the approach you are suggesting.

Cheers,
Dave

> -----Original Message-----
> From: www-tag-request@w3.org
> [mailto:www-tag-request@w3.org]On Behalf Of
> Micah Dubinko
> Sent: Friday, October 04, 2002 3:21 PM
> To: 'www-tag@w3.org'
> Cc: 'chris@w3.org'; 'GK@ninebynine.org'
> Subject: now://example.org/car (was lack of consensus on httpRange-14)
>
>
>
> From the TAG f2f minutes:
>
> [ChrisL]
>     now://example.org/car
>     Where 'now' is defined to be a
>     non-dereferencable protocol
>
> Other than this short statement, I couldn't find any other
> references in the
> minutes about this idea.
>
> Graham Klyne separately suggested:
>
>  http://id.ninebynine.org/people/gk/ to identify a person
> and
>  http://www.ninebynine.org/Ident/people/gk/ to identity a web page.
>
> With a small twist, that could be:
>
>  now://www.ninebynine.org/Ident/people/gk/ to identify a person
> and
>  http://www.ninebynine.org/Ident/people/gk/ to identify a web page
>
>
> From the viewpoint of a web developer, it makes sense to differentiate
> between network-accessible and non-network-accessible
> resources. A trivial
> transform ('now:' -> 'http:') can provide additional details
> on the abstract
> thing-that-means-whatever-the-DNS-owner-defines-it-to-be.
>
> Thoughts from the TAG?
>
> .micah
>
>