[Odrl-version2] ODRL Version 2.0 - XML Encoding

[Michael Steidl (IPTC)]

Hi Renato,

hm, building URNs works quite differently from what you describe:
- the syntax of a URN is described in RFC 2141 [1]
- by this syntax any URN looks like this: <URN> ::= "urn:" <NID> ":" <NSS>
- the NIDs (Namespace IDs) are assigned by IANA - only upon request [2]
- this request included a precise definition of the NSS = Namespace Specific
String. As my organisation, the IPTC, has registered 2 URN NSS (newsml and
iptc) I can only tell such a definition and registration requires some
ponderings and discussions
- for test and demo purposes only one of the "urn-1" to "urn-7" NIDs may be
used

The ODRL XML Encoding draft specifies the uid of elements is "URI or QName",
as a URI can be URN or URL I recommend using http-URLs for the examples -
much less formal issues with them.

And I would like to add that the specification "URI or QName" is a bit
tricky to process: how to make a distinction? The processor on the receiving
side must know whether the string is a URI or QName as QNames have to be
resolved to URIs before they are further processed.

Further I would support Stuart's pointing at a major issue with QNames:
their local part MUST NOT start with a digit - but there are many, many
existing vocabularies which have codes/terms which start with a digit, the
ISBN is a good example.
For that reason the IPTC has specified a QCode which is actually the same as
a QName, except this lexical space constraint, we invite ODRL to look into
QCodes.

Btw: we are looking forward having Daniel with us at the next IPTC meeting,
next week.

Michael

[1] http://www.ietf.org/rfc/rfc2141.txt 
[2] http://www.iana.org/assignments/urn-namespaces/urn-namespaces.xml 

===============
Michael Steidl
Managing Director of the IPTC <mdirector at iptc.org>
International Press Telecommunications Council - http://www.iptc.org/
Business office address: 
20 Garrick Street, London WC2E 9BT, United Kingdom
Registered in England, company no 101096


> -----Original Message-----
> From: odrl-version2-bounces at odrl.net [mailto:odrl-version2-
> bounces at odrl.net] On Behalf Of ri at odrl.net
> Sent: Monday, October 25, 2010 2:36 AM
> To: ODRL-Version2
> Subject: Re: [Odrl-version2] ODRL Version 2.0 - XML Encoding
> 
> 
> On 23 Oct 2010, at 05:19, Myles, Stuart wrote:
> 
> > Also, I notice that there are several urn's sprinkled throughout the
> > encoding, e.g.
> >
> > <o:asset uid="urn:asset:9898"/>`
> >
> > But isn't there a formal mechanism that is required to register a URN
> > (i.e. http://www.ietf.org/rfc/rfc2611.txt)?  Were these URNs intended
> to
> > be compact URIs?  I couldn't find a discussion of URNs in the ODRL
> XML
> > Encoding document (but maybe I just missed it?)
> 
> Stuart - the UIDs used for Assets and Party Roles are all
> "hypothetical" identifiers.
> (since these are external resources that users/owners will be
> defining/using)
> 
> Since example.com is a reserved domain [1] for such examples, I may
> change them all over
> to urn:example.com:asset:XX and urn:example.com:party:YY
> 
> 
> Cheers
> 
> Renato Iannella
> ODRL Initiative
> http://odrl.net
> 
> 
> [1] http://www.rfc-editor.org/rfc/rfc2606.txt
> _______________________________________________
> Odrl-version2 mailing list
> Odrl-version2 at odrl.net
> http://odrl.net/mailman/listinfo/odrl-version2_odrl.net