W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2003

URI scheme uniqueness (was Re: rfc2518-bis-04 issues (part 2))

From: Elias Sinderson <elias@cse.ucsc.edu>
Date: Wed, 30 Jul 2003 21:52:33 -0700
Message-ID: <3F28A091.8060702@cse.ucsc.edu>
To: w3c-dist-auth@w3.org
Julian Reschke wrote:

>>><Julian Reschke> 02-C05 Section 6.3, p3
>>>Replace
>>>"However resources are free to return any URI scheme so long as it meets the
>>>      
>>>
>>>uniqueness requirements."
>>>by
>>>"However servers are free to use any IETF-registered URI scheme so long as
>>>      
>>>
>>>it meets the uniqueness requirements."
>>>(If it's not IETF-registered, I don't see how it can possibly meet the
>>>uniqueness criterium).
>>>      
>>>
>><Jason Crawford> I'd vote to leave the text as it is.
>>    
>>
><Julian Reschke> Again, please help me understand...:
>
>1) Are you suggesting that to for a scheme to be IETF-registered is not a
>requirement? In which case I'll argue that by definition there can't be any
>uniquess guarantee otherwise.
>
<Elias Sinderson> It's a given that any IETF-registered URI scheme will 
meet the stated uniqueness requirements. I don't believe that it is the 
only way to do so, however. For example, private intranets may utilize 
their own, homegrown system to guarantee uniquenes. It's also entirely 
possible that, in the distant future, there may be alternative means to 
accomplish this on the public internet. Perhaps something along the 
lines of the following would be acceptable?

"...are free to use any URI scheme so long as it meets the stated 
uniqueness requirements. One way to accomplish this is to use 
IETF-registered URI schemes."

This language seems specific enough to be unambiguous while flexible 
enough to allow for other mechanisms to ensure uniqueness. The drawback 
of not taking a firmer position on this is that it opens the possibility 
that someone will implement some half-baked idea and it won't meet the 
necessary requirements...


Cheers,
Elias
Received on Thursday, 31 July 2003 00:54:39 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:04 GMT