RE: Updated ODRL in JSON DRAFT

Does anyone have any further comments or questions on this?

What do we do next to move this forward?

Regards,

Stuart



From: Myles, Stuart
Sent: Wednesday, March 05, 2014 2:21 PM
To: ODRL Community Group (Contrib)
Subject: RE: Updated ODRL in JSON DRAFT

I made a couple of other minor updates to the ODRL in JSON DRAFT document (there were some other typo's in the examples):

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

Thanks to all who have provided comments so far. Feel free to add more.

Regards,

Stuart


From: Renato Iannella [mailto:ri@semanticidentity.com]
Sent: Thursday, February 27, 2014 5:55 AM
To: ODRL Community Group (Contrib)
Subject: Re: Updated ODRL in JSON DRAFT


On 27 Feb 2014, at 07:44, Myles, Stuart <SMyles@ap.org<mailto:SMyles@ap.org>> wrote:

to clarify things and introduce the IPTC-requested changes of rightoperandunit and rightoperanddatatype (which I think haven't yet made it into the official XML Encoding, yet, but hopefully will do, soon).

The XML Encoding draft [1] does include the unit/datatype additions.

Examples 2, 3, and 6 in the JSON spec will need to be updated to use the new method of expressing a payment.

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

[1] http://www.w3.org/community/odrl/work/2-0-xml-encoding-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