- From: Renato Iannella <renato.iannella@monegraph.com>
- Date: Tue, 11 Apr 2017 12:14:32 +1000
- To: W3C POE WG <public-poe-wg@w3.org>
- Message-Id: <5A2C5D8E-B16C-4F05-B2B3-EF657FB422C3@monegraph.com>
> On 10 Apr 2017, at 22:49, Ivan Herman <ivan@w3.org> wrote: > > That is because the @context part is incomplete. If you do something like: > > Ideally, we should use an external context document that we would refer to. Yes…we are still trying to finalise that external context document in github issue #46 [1] But for the ODRL model examples, we did not feel we needed to include all the “inline” context, as we defer to the Vocab+Expression for normative serialisations. Unless they are incorrect? Or should we “namespace” everything like: { "@context": { “o": "http://www.w3.org/ns/odrl/2/ <http://www.w3.org/ns/odrl/2/>" }, "@type": "odrl:Set", "@id": "http://example.com/policy:1010 <http://example.com/policy:1010>", “o:permission": [{ “o:target": "http://example.com/asset:9898 <http://example.com/asset:9898>", “o:action": "o:read" }], “o:prohibition": [{ “o:target": "http://example.com/asset:9898 <http://example.com/asset:9898>", “o:action": "o:reproduce" }] } Renato Iannella, Monegraph Co-Chair, W3C Permissions & Obligations Expression (POE) Working Group [1] https://github.com/w3c/poe/issues/46 <https://github.com/w3c/poe/issues/46>
Received on Tuesday, 11 April 2017 02:15:11 UTC