Re: [URN] Potential inconsistency between URL and URN syntaxes...

Leslie Daigle (leslie@bunyip.com)
Wed, 18 Dec 1996 18:24:18 -0500


Message-Id: <199612182324.SAA04077@beethoven.bunyip.com>
From: leslie@bunyip.com (Leslie Daigle)
Date: Wed, 18 Dec 1996 18:24:18 -0500
In-Reply-To: Ryan Moats's message as of Dec 18,  9:11
To: Ryan Moats <jayhawk@ds.internic.net>, uri@bunyip.com
Subject: Re: [URN] Potential inconsistency between URL and URN syntaxes...
Cc: urn-ietf@bunyip.com


It looks like the following questions are on the table:

	. should URN and URL syntaxes be consistent?
	
	. if yes, which should now change:

		. URLs cannot, because of legacy support, although
	 	  there is the issue of "I18N"

		. URNs "can", except that the existing syntax was
		  built for specific reasons to address issues that
		  have concerned URNs more than URLs (e.g., bringing
		  in other namespaces and addressing multiple language
		  issues).


Is it "desirable" that URN syntax be compliant with URL syntax, or "required"?
What _breaks_ if it is not?

[Ryan quotes from the URL draft:]
> > 
> >    Although this specification restricts its discussion to URLs, the
> >    syntax defined is that of URI in general.  Any requirements placed on
> >    the URL syntax also apply to the URI syntax.  This uniform syntax for
> >    all resource identifiers allows a URN to be used in any data field
> >    that might otherwise hold a URL.

This draft is for the _URL_ syntax, and this is the only paragraph that
lays claim to all of URI syntaxes.  It was written before there was a concrete
proposal for URNs.  I think the URL syntax RFC would be quite complete
_without_ this paragraph.

The URL syntax is going to face its own battles as the issues of 
character sets and languages are brought up -- it seems like now is a logical
time to separate out the evolution of these two things, _unless_ there
are some very concrete things that will break if they are not kept
consistent.

Cheers!
Leslie.

-- 

----------------------------------------------------------------------------

  "_Be_                                           Leslie Daigle
             where  you                           Vice President, Research
                          _are_."                 Bunyip Information Systems
                                                  (514) 875-8611
                      -- ThinkingCat              leslie@bunyip.com
----------------------------------------------------------------------------