RE: Updated ODRL in JSON DRAFT

That's the way these kinds of plans go, I know...


Ø  2 - Update the XML Encoding to use the same URIs from the ODRL Ontology [2]

Ø  (this includes uppercase changes to the XML Schema, such as <policy> to <Policy>)

Oh - I don't recall that ever being discussed. Did I miss it? It is a pretty large change. For example, all of the examples that we've compiled on the IPTC website use the current XML syntax and element names:

http://dev.iptc.org/RightsML-Simple-Example-An-Action


Ø  In the *long term* the ODRL Ontology will become our normative specification, so using the same URIs now in the other encodings will save us some grief ;-)

I can certainly see that using the same URIs makes sense. But there is also the question of backwards compatibility. It is one thing to be able to change the URL scheme for vocabulary values, but it is quite another to alter the element and attribute names in XML. For example, the current RightsML examples use the current XML encoding spec:

<o:policy uid="http://example.com/RightsML/policy/idActionPrint1"
 type="http://w3.org/ns/odrl/vocab#set"
 xmlns:o="http://w3.org/ns/odrl/2/">
   <o:permission>
      <o:asset uid="urn:newsml:example.com:20090101:120111-999-000022"
       relation="http://w3.org/ns/odrl/vocab#target"/>
      <o:action name="http://w3.org/ns/odrl/vocab#print"/>
      <o:party uid="http://example.com/cv/party/epa"
       function="http://w3.org/ns/odrl/vocab#assigner"/>
      <o:party uid="http://example.com/cv/policy/group/epapartners"
       function="http://w3.org/ns/odrl/vocab#assignee"/>
   </o:permission>
</o:policy>

It is relatively simple to instead use the Ontology URLs for vocabulary items:

<o:policy uid="http://example.com/RightsML/policy/idActionPrint1"
 type="http://www.w3.org/ns/odrl/2/set"
 xmlns:o="http://www.w3.org/ns/odrl/2/">
   <o:permission>
      <o:asset uid="urn:newsml:example.com:20090101:120111-999-000022"
       relation="http://www.w3.org/ns/odrl/2/target"/>
      <o:action name="http://www.w3.org/ns/odrl/2/print"/>
      <o:party uid="http://example.com/cv/party/epa"
       function="http://www.w3.org/ns/odrl/2/assigner"/>
      <o:party uid="http://example.com/cv/policy/group/epapartners"
       function="http://www.w3.org/ns/odrl/2/assignee"/>
   </o:permission>
</o:policy>

The two are essentially equivalent - just different URL schemes and easy for a parse to support both, for example.

However, altering the element and attribute names means that they are totally different schemas:

<o:Policy Uid="http://example.com/RightsML/policy/idActionPrint1"
 Type="http://www.w3.org/ns/odrl/2/set"
 xmlns:o="http://www.w3.org/ns/odrl/2/">
   <o:Permission>
      <o:Asset Uid="urn:newsml:example.com:20090101:120111-999-000022"
       Relation="http://www.w3.org/ns/odrl/2/target"/>
      <o:Action Name="http://www.w3.org/ns/odrl/2/print"/>
      <o:Party Uid="http://example.com/cv/party/epa"
       Function="http://www.w3.org/ns/odrl/2/assigner"/>
      <o:Party Uid="http://example.com/cv/policy/group/epapartners"
       Function="http://www.w3.org/ns/odrl/2/assignee"/>
   </o:Permission>
</o:Policy>

(I'm guessing the attribute names would need to be different, too. However, hopefully the above illustrates my point).

Regards,

Stuart


From: Renato Iannella [mailto:ri@semanticidentity.com]
Sent: Friday, May 16, 2014 3:09 AM
To: Myles, Stuart
Cc: ODRL Community Group (Contrib)
Subject: Re: Updated ODRL in JSON DRAFT


Myles...there is  plan....its just that we are way behind schedule ;-)

1 - Update the ODRL Model to include the "profile" attribute [1]
2 - Update the XML Encoding to use the same URIs from the ODRL Ontology [2]
(this includes uppercase changes to the XML Schema, such as <policy> to <Policy>)
3 - Update the ODRL/CC Policy (to support the new profile attribute, and deprecated Vocab terms) [3]
4 - Update the ODRL Common Vocab (once the external semantic review is complete) [4]

In the *long term* the ODRL Ontology will become our normative specification, so using the same URIs now in the other encodings will save us some grief ;-)

I will work on 1) and 2) as a priority now.

Cheers...
Renato Iannella
Semantic Identity
http://semanticidentity.com
Mobile: +61 4 1313 2206

[1] http://www.w3.org/community/odrl/work/2-0-core-model-constraint-draft-changes/
[2] http://www.w3.org/community/odrl/work/2-0-xml-encoding-constraint-draft-changes/
[3] http://www.w3.org/community/odrl/work/cc/
[4] http://www.w3.org/community/odrl/work/2-0-common-vocabulary-constraint-draft-changes/


The information contained in this communication is intended for the use
of the designated recipients named above. If the reader of this 
communication is not the intended recipient, you are hereby notified
that you have received this communication in error, and that any review,
dissemination, distribution or copying of this communication is strictly
prohibited. If you have received this communication in error, please 
notify The Associated Press immediately by telephone at +1-212-621-1898 
and delete this email. Thank you.
[IP_US_DISC]

msk dccc60c6d2c3a6438f0cf467d9a4938