To:
michaelm@netsol.com
Cc:
George Belotsky <george@register.com>, Martin Oldfield <m@mail.tc>, "Hollenbeck, Scott" <shollenbeck@verisign.com>, ietf-provreg@cafax.se
From:
Martin Oldfield <m@mail.tc>
Date:
Thu, 15 Mar 2001 17:25:10 +0000 (GMT)
In-Reply-To:
<20010315120006.J12359@bailey.dscga.com>
Sender:
owner-ietf-provreg@cafax.se
Subject:
Re: Unique handle generation
>>>>> "Michael" == Michael Mealling <michael@bailey.dscga.com> writes:
Michael> On Thu, Mar 15, 2001 at 11:55:09AM -0500, George Belotsky
Michael> wrote:
>> Can we automatically generate these URIs and ensure uniqueness
>> without resorting to some central repository?
>>
>> If we can (I don't see why not), then this is potentially a
>> good approach.
Michael> Please. No. I've been involved in a lot of these XML/URI
Michael> discusions and you really don't want to do this. Do you
Michael> really want to have your system to have to deal with a
Michael> registry using "mailto:joe@aol.com" as its registry
Michael> identifier? Allowing any URI means you allow _ANY_ URI
Michael> here. The issues surrounding the nearly 100 different
Michael> unregistered URIs that folks are using with no
Michael> coordination and several conflicts [1][2] make this a
Michael> currently very badly managed space. This is the
Michael> identifier the _entire_ provreg system is going to depend
Michael> on at its _core_. You really don't want it based on such
Michael> loose identification scheme...
Michael> -MM
Michael> [1]http://www.w3.org/Addressing/schemes
Michael> [2]http://www.isi.edu/in-notes/iana/assignments/url-schemes
So much for that daft idea then!
If you'll indulge my stupidity for a little longer, would you
objections persist if the URI had to be an http: thing, and the target
of the URI had to deliver a particular document ?
Cheers,
--
Martin Oldfield,
AdamsNames Ltd.