W3C home > Mailing lists > Public > public-ole-comment@w3.org > December 2015

Re: JSON vs. JSON-LD?

From: Renato Iannella <renato@knowledgeflux.com>
Date: Tue, 8 Dec 2015 11:24:29 +0000
To: "public-ole-comment@w3.org" <public-ole-comment@w3.org>
CC: Ivan Herman <ivan@w3.org>
Message-ID: <C2750D9A-D0CF-4D0F-8F7E-1FDDCD5F701C@knowledgeflux.com>

On 7 Dec 2015, at 10:32 PM, Ivan Herman <ivan@w3.org<mailto:ivan@w3.org>> wrote:

1. Is the ODRL community o.k. not to have a 'vanilla' JSON encoding as part of the deliverables as it is defined now? Or
2. Should the deliverables also include a 'vanilla', non JSON-LD encoding as part of the deliverables?

If the decision is #1 above, ie, only a JSON-LD document is produced, then, I guess, [2] should not be listed as an input document.

The correct approach should be, in my view, to leave this question open for the WG to decide. Make the deliverables JSON and add a note that the WG will consider whether that is a JSON-LD compliant encoding or not, and/or whether both JSON versions should be standardized.\

The ODRL CG has discussed this point:

https://lists.w3.org/Archives/Public/public-odrl/2015Nov/0000.html

https://lists.w3.org/Archives/Public/public-odrl/2015Nov/0001.html

https://lists.w3.org/Archives/Public/public-odrl/2015Nov/0002.html

https://lists.w3.org/Archives/Public/public-odrl/2015Nov/0003.html

https://lists.w3.org/Archives/Public/public-odrl/2015Nov/0004.html


The preference is a JSON deliverable, with a Context document.

Action: update the Deliverable title to be just “JSON"


Renato Iannella
Head of Innovation and Emerging Technologies, KnowledgeFlux
Level 7, 100 Edward St, Brisbane 4000 AUSTRALIA +61 4 1313 2206









Received on Tuesday, 8 December 2015 11:25:04 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 8 December 2015 11:25:05 UTC