- From: Myles, Stuart <SMyles@ap.org>
- Date: Tue, 4 Feb 2014 21:18:29 +0000
- To: "ODRL Community Group WG (public-odrl-contrib@w3.org)" <public-odrl-contrib@w3.org>
- Message-ID: <2B3AA5056E3CB8428BDE670B2CEEC54F33CC6C72@CTCXMBX02.ap.org>
We have updated the ODRL 2 JSON Encoding draft document: http://www.w3.org/community/odrl/work/json/ It now has a JSON schema and some examples, plus a general description of the approach. Briefly, in this attempt at a JSON schema, we use full URLs to identify values. This simplifies mixing of vocabularies (such as RightsML and the ODRL Common Vocabulary). And we think that the schema we are proposing results in a more "natural" JSON. Here's one example (which is in the document), which uses both a RightsML action (distribute) and an ODRL CV (display): { "policytype": "http://w3.org/ns/odrl/vocab#request", "policyid": "http://example.com/policy:04311", "permissions": [ { "target": "http://example.com/news:0099", "action": "http://iptc.org/std/RightsML/2011-10-07/distribute", "assignee": "http://example.com/guest:0589" }, { "target": "http://example.com/news:0099", "action": "http://w3.org/ns/odrl/vocab#display", "assignee": "http://example.com/guest:0589" } ] } Feedback on any aspect of this draft is very welcome. Regards, Stuart 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
Received on Tuesday, 4 February 2014 21:18:57 UTC