Review of URL syntax

Ian King | 13 Sep 1999 07:36

RE: Proposed amendment to language of draft-ietf-url-procedures

Then what do you suggest to provide collision management, identification and
interoperability in URL schemes?  I'd be thrilled if you have a viable
alternative to offer.  But a lot of very intelligent folks have discussed
this matter for a long time, and this is what they came up with.  I'd be
delighted if we did not need process around this, and these matters could
somehow "just work out".  But the consensus is that this just is not the
case, at least not today.  

If you feel you have a viable alternative, that would prevent namespace
collision, encourage development of interoperable standards, and provide
sensible management of this highly visible namespace -- I'm all ears.  

Ian King <iking <at> microsoft.com>
Speech Product Group/Intelligent Interface Technologies
MICROSOFT CORPORATION

-----Original Message-----
From: Masataka Ohta [mailto:mohta <at> necom830.hpcl.titech.ac.jp]
Sent: Sunday, September 12, 1999 2:26 AM
To: moore <at> cs.utk.edu
Cc: mohta <at> necom830.hpcl.titech.ac.jp; moore <at> cs.utk.edu; Ian King;
ietf-url <at> imc.org; urn-ietf <at> lists.internic.net; paf <at> swip.net;
RPetke <at> wcom.net
Subject: Re: Proposed amendment to language of draft-ietf-url-procedures

Keith;

> > Are you saying that IETF is infallible and has never published
> > any bad ideas of its own?
>

(Continue reading)

headers

Masataka Ohta | 13 Sep 1999 23:02

RE: Proposed amendment to language of draft-ietf-url-procedures

Ian;

> But a lot of very intelligent folks have discussed
> this matter for a long time, and this is what they came up with.  I'd be
> delighted if we did not need process around this, and these matters could
> somehow "just work out". But the consensus is that this just is not the
> case, at least not today.  

The bottomline is that it is really difficult to solve a problem
when the problem does not exist.

							Masataka Ohta

headers

Masataka Ohta | 13 Sep 1999 18:21

RE: Proposed amendment to language of draft-ietf-url-procedures

Ian;

> Then what do you suggest to provide collision management, identification and
> interoperability in URL schemes?

Huh?

How, do you think, IANA is managing collisons, identifications
and interoperability of TCP port numbers?

> If you feel you have a viable alternative, that would prevent namespace
> collision, encourage development of interoperable standards, and provide
> sensible management of this highly visible namespace

DNS has a purely technical mechanism to enforce unique assignment
through well known single set of root servers, even which can be
ignored by local conventions.

URL does not.

> -- I'm all ears.  

You only have to see the real world.

> But a lot of very intelligent folks have discussed
> this matter for a long time, and this is what they came up with.

You seems to have a very strange definition of intelligence.

							Masataka Ohta

(Continue reading)