- From: stuartmyles via GitHub <sysbot+gh@w3.org>
- Date: Wed, 01 Feb 2017 20:42:04 +0000
- To: public-poe-archives@w3.org
@azaroth42 looking at your example, it seems you rewrote the JSON - was that to make it easier to map it into JSON-LD? If so, I have some questions... Here is the original JSON example: { "policytype": "http://www.w3.org/ns/odrl/2/Set", "policyid": "http://example.com/policy:0099", "permissions": [{ "target": "http://example.com/asset:9898", "action": "http://www.w3.org/ns/odrl/2/reproduce" }], "prohibitions": [{ "target": "http://example.com/asset:9898", "action": "http://www.w3.org/ns/odrl/2/modify" }] } And here is your rewritten version (minus the context): { "id": "http://example.com/policy:0099", "type": "Set", "permission": { "type": "Permission", "action": "reproduce", "target": "http://example.com/asset:9898" }, "prohibition": { "type": "Prohibition", "action": "modify", "target": "http://example.com/asset:9898" } } One obvious problem with the JSON-LD version: you can't have more than one permission or prohibition in a given expression! Is that a necessary restriction for the JSON-LD? Also, I use full URLs for the actions (e.g. "action": "http://www.w3.org/ns/odrl/2/modify") whereas your example uses URLs that are built into the context (i.e. "action": "modify"). The use of full URLs is so that ODRL users can plug in whatever vocabulary of actions they want. Are we no longer able to use full URLs in JSON-LD? -- GitHub Notification of comment by stuartmyles Please view or discuss this issue at https://github.com/w3c/poe/issues/46#issuecomment-276775830 using your GitHub account
Received on Wednesday, 1 February 2017 20:42:12 UTC