Re: [URN] Re: Relative URLs and URNs

"Roy T. Fielding" <[email protected]>
Newsgroups gmane.ietf.url
Message-ID <[email protected]>
> Thus spoke Keith Moore:
> 
>> If we disallow unencoded '/' within URNs for now, we can always add 
>> relative URNs later when we understand them better.

I couldn't disagree more.

If '/' is disallowed in URNs, then a conforming parser will reject
a URN containing '/'.  That means you will never be able to introduce
relative URNs.  Creating barriers to technology just because it isn't
understood is a mistake, particularly when the only time '/' is
meaningful for *any* URI is when it is used as a base for parsing
relative URIs.

If you aren't using relative forms, then there is no reason to encode '/'.
If you are, then you don't want '/' encoded.  There does not exist a
situation in which it is beneficial to disallow '/' in URNs.

.....Roy
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.