W3C home > Mailing lists > Public > public-odrl@w3.org > November 2015

RE: W3C WG Update

From: Myles, Stuart <SMyles@ap.org>
Date: Wed, 4 Nov 2015 16:54:37 +0000
To: Renato Iannella <renato@knowledgeflux.com>, "public-odrl@w3.org Group" <public-odrl@w3.org>
Message-ID: <2B3AA5056E3CB8428BDE670B2CEEC54F58AEE97C@CTCXMBX10.ap.org>
One of the things I notice is that the plan for OLE would include serializations in XML, RDF and JSON-LD. Whereas, of course, ODRL 2.1 has serializations in XML, RDF and JSON. We considered JSON-LD but decided against it essentially because it adds a layer of complexity and means that certain implementations that currently use JSON (but not JSON-LD) wouldn't be able to use ODRL. (Implementations which use JSON-LD would be able to use ODRL 2.1, however, since JSON-LD Is one of the ways that you can serialize the RDF data model).

So, given this, and given that the at least some of the current implementations of ODRL 2.1 support JSON already, can we get the W3C to retain the existing format?



From: Renato Iannella [mailto:renato@knowledgeflux.com]
Sent: Thursday, October 29, 2015 7:15 PM
To: public-odrl@w3.org Group
Subject: W3C WG Update

Dear all, the W3C Membership meet this week [1] and discussed the Draft Charter [2] to take the ODRL CG to Working Group.

The minutes from the breakout discussion [3] are available, and seem mostly positive.

They are calling for more comments on the Charter (until end of Nov) via this comments list [4].

Renato Iannella

[1] http://www.w3.org/2015/10/TPAC/
[2] http://w3c.github.io/ole/charter.html
[3] http://www.w3.org/2015/10/28-ole-minutes.html
[4] https://lists.w3.org/Archives/Public/public-ole-comment/

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.

msk dccc60c6d2c3a6438f0cf467d9a4938
Received on Wednesday, 4 November 2015 16:55:32 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:35:35 UTC