[Playlist] Question on identifier content, URI and URN

[Sebastian Pipping]

Lucas Gonze wrote:
> Thanks for digging in at this level of detail, Sebastien.
> 
> The definition we use for a URN comes from
> http://gbiv.com/protocols/uri/rev-2002/rfc2396bis.html#URLvsURN :
> 'The term "Uniform Resource Name" (URN) has been used historically to
> refer to both URIs under the "urn" scheme [RFC2141], which are required
> to remain globally unique and persistent even when the resource ceases
> to exist or becomes unavailable, and to any other URI with the
> properties of a name.'
> 
> Because there is a potential clash over the definition (must use "urn"
> scheme VS. is a URI which may not be a locator), the XSPF v1 spec
> explicitly defines the term:
> ...
> 2.3.1 URI, URLs and URNs
> 
> The terms URI, URL, and URN should be interpreted here as follows: a URL
> is an address of something that can be fetched by a computer; a URN is a
> name of something which may be purely an abstraction; a URI is either.
> In this document, //playlist[@xmlns], //playlist/identifier, meta[@rel],
> link[@rel], and //playlist/trackList/track/identifier are URNs, all
> other elements are URLs.
> 
> See also: RFC2396bis; URIs, URLs, and URNs: Clarifications and
> Recommendations 1.0
> ...
> 
> That is, we do not use RFC2141 as the basis for the definition of a URN.
>    A URN is a URI which is not necessarily a locator; any other use of
> the term URI excludes names which are not locators.

----------------------------------------------------------------
So in XSPF a URN is everything starting with "<scheme>:"?
All URLs are URNs? All URIs are URNs?

Please point me to the right grammars so I can be sure to
implement the right thing for isURN() and isURL().

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

There are several places where the URL/URN migration of
XSPF-1 was not finished (where it still reads "URI").
Here is my summary:

* URN - 4.1.1.2.11.1.1 - playlist.link[@rel]
* URN - 4.1.1.2.12.1.1 - playlist.meta[@rel]
* URL - 4.1.1.2.13.1.1 - playlist.extension[@application]
* URL - 4.1.1.2.14.1.1.1.13.1.1 - track.playlist.extension[@application]
* URL - 6.3 Extension URIs
* URL/URN - All testcases that match *-noturi-*.xspf
----------------------------------------------------------------



> It is easy to argue that this is silly, confusing, and wrong, but there
> it is -- a spec means nothing if it can be modified at will.  Fixing
> this would touch a lot of spots, I don't believe that I could do this
> many edits without creating what is essentially a new version, and there
> aren't resources for doing a new version.

----------------------------------------------------------------
Which edits do you mean exactly? I don't understand.


Regards, Sebastian


-- 
Sebastian Pipping
http://www.hartwork.org/