RE: Some Questions about the XML Encoding of ODRL v2

I think it is impossible to make the policy mandatory by XML Schema means as
by the general ODRL design it is the root element - and root elements have
no cardinality. But maybe it would help to say explicitly on the XML
Encoding page that <o:policy> must be the root of any ODRL expression.

 

And by my counting only the snippets in section 4 don't have a policy root
element, all the 11 full examples in section 5 have one. In 6. Other
Examples policy is missing in the last two snippets out of 6.

 

Btw: what is the status of the Draft Changes page at
http://www.w3.org/community/odrl/work/2-0-xml-encoding-constraint-draft-chan
ges/ - all example codes are missing there.

 

Michael

 

 

From: Renato Iannella [mailto:ri@semanticidentity.com] 
Sent: Friday, January 17, 2014 2:36 AM
To: ODRL Community Group (Contrib)
Subject: Re: Some Questions about the XML Encoding of ODRL v2

 

 

On 17 Jan 2014, at 06:38, Myles, Stuart <SMyles@ap.org> wrote:





In reviewing the ODRL v2 XML encoding document, we came up with a couple of
questions:

 <http://www.w3.org/community/odrl/two/xml>
http://www.w3.org/community/odrl/two/xml

Is policy required? It seems to be, but is mainly omitted from the actual
examples. Is that just to save space or is it optional?

 

Yes, it is required. Since uid and type are mandatory attributes, it was
assumed, but is mandatory in the XML Schema.

Will make it more specific....

 





 In the Inline Assets example, it looks like there is a typo:

  <http://www.w3.org/community/odrl/two/xml/#section-4>
http://www.w3.org/community/odrl/two/xml/#section-4

It starts off as <o:permission> but ends up with</o:prohibition>

 

That has been fixed in the Draft xml spec:
http://www.w3.org/community/odrl/work/2-0-xml-encoding-constraint-draft-chan
ges/

 

 

Renato

 

Cheers...

Renato Iannella

Semantic Identity

http://semanticidentity.com

Mobile: +61 4 1313 2206