RE: Updated ODRL in JSON DRAFT

Ø  I wanted to true and use the same URIs across the XML, RDF/OWL, and JSON encodings.

I can see why this is very helpful (and much less confusing) to those of us who are working on the standards and who are typically going to be working with more than one format. But what is the advantage for someone who is only working with JSON? (The JSON properties like "permissions" don't use URIs, after all).

Actually, this touches on another point that I wanted to raise: we now have (roughly) three encodings of ODRL, but none of them are 100% in step with the others. I've been working on a Python library to generate ODRL documents (currently, it supports XML and JSON). One nice side effect of this is that I've found and fixed a few bugs in the ODRL in JSON draft, which is why it now has a "5 May 2014" date... It is still early days with the library, but I am putting it up on Github and will announce it more formally once it is a bit more mature.

However, even with just those two formats, I found quite a few differences. I had to create a custom version of the XSD, for example, to have it reference the OWL-style URIs (and yet the OWL representation hasn't been formally adopted by the CG yet). I would say that this inconsistent state of the adopted and draft versions of the standards would be a significant barrier to anyone planning to adopt ODRL for a production system. Certainly, if I don't know all of the good work that has been going on to create and support ODRL, it would make me think twice.

Perhaps we should figure out a plan for how we will bring it all together before too long?

Regards,

Stuart



From: Renato Iannella [mailto:ri@semanticidentity.com]
Sent: Tuesday, May 13, 2014 9:11 PM
To: Myles, Stuart
Cc: ODRL Community Group (Contrib)
Subject: Re: Updated ODRL in JSON DRAFT


On 25 Apr 2014, at 06:40, Myles, Stuart <SMyles@ap.org<mailto:SMyles@ap.org>> wrote:


So, to pave the way for this kind of change, I make every property that must be plural have a plural name.

True, but they can also be singular (and in most cases are, eg "permissions")

I wanted to true and use the same URIs across the XML, RDF/OWL, and JSON encodings.

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



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