RE: ODRL V2.1 Process - Lets Start

Thanks for reviewing so closely. I corrected those errors and altered the reference to be ODRL 2.1 in the spec. (It talked about 2.0 before).

http://www.w3.org/community/odrl/work/json/


Ø  Also, in the JSON-Schema, how/where is the best way to state this is version "2.1" for machine processing?

The JSON schema has a id property:

"id": "http://www.w3.org/ns/odrl/2/jsonschema#<http://www.w3.org/ns/odrl/2/jsonschema>"

This is saying that it is the JSON schema for ODRL v2. It elides whether it is for 2.1 (or 2.2 or ...). Presumably we only plan to make backwards compatible changes to ODRL (only adding new features, not removing any) otherwise it needs to be v3, doesn't it?

Regards,

Stuart


From: Renato Iannella [mailto:ri@semanticidentity.com]
Sent: Monday, September 29, 2014 8:46 AM
To: Myles, Stuart
Cc: <public-odrl@w3.org>
Subject: Re: ODRL V2.1 Process - Lets Start


On 27 Sep 2014, at 03:55, Myles, Stuart <SMyles@ap.org<mailto:SMyles@ap.org>> wrote:


I've reviewed the ODRL in JSON spec and it is in synch with the Core Model and Vocabulary specs (of course, let me know if I've missed something!)

Stuart, can you double-check the URIs used for ODRL vocab terms (use the examples in XML encoding to verify)
Eg numberOfUses should be count, publish should be reproduce, the policy Types should has first letter capitals...)

Also, in the JSON-Schema, how/where is the best way to state this is version "2.1" for machine processing?

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