- From: stuartmyles via GitHub <sysbot+gh@w3.org>
- Date: Tue, 31 Jan 2017 16:19:53 +0000
- To: public-poe-archives@w3.org
I'm a bit confused as to where this (creating a JSON-LD mapping) stands now. Based on Rob and Renato's emails, it sounds like someone needs to create a JSON-LD context file. And that, essentially, it needs to be done manually. Is that right? If so, is there someone already working on doing that? If not, then I can volunteer. (I just don't want to do it if someone - likely better qualified than me - is already slaving away). I also looked at Rob's example earlier in this thread and it looks good to me. (In other words, it seems like it would be fine to ignore the JSON-LD context and just handle it like a proper JSON file, which is my definition of "good" in this situation!) http://json-ld.org/playground/?startTab=tab-compacted©Context=true&json-ld=%7B%22%40context%22%3A%7B%22odrl%22%3A%22http%3A%2F%2Fwww.w3.org%2Fns%2Fodrl%2F2%2F%22%2C%22Set%22%3A%22odrl%3ASet%22%2C%22Permission%22%3A%22odrl%3APermission%22%2C%22Prohibition%22%3A%22odrl%3AProhibition%22%2C%22target%22%3A%22odrl%3Atarget%22%2C%22action%22%3A%7B%22%40id%22%3A%22odrl%3Aaction%22%2C%22%40type%22%3A%22%40vocab%22%7D%2C%22permission%22%3A%22odrl%3Apermission%22%2C%22prohibition%22%3A%22odrl%3Aprohibition%22%2C%22reproduce%22%3A%22odrl%3Areproduce%22%2C%22modify%22%3A%22odrl%3Amodify%22%2C%22id%22%3A%22%40id%22%2C%22type%22%3A%22%40type%22%7D%2C%22id%22%3A%22http%3A%2F%2Fexample.com%2Fpolicy%3A0099%22%2C%22type%22%3A%22Set%22%2C%22permission%22%3A%7B%22type%22%3A%22Permission%22%2C%22target%22%3A%22http%3A%2F%2Fexample.com%2Fasset%3A9898%22%2C%22action%22%3A%22reproduce%22%7D%2C%22prohibition%22%3A%7B%22type%22%3A%22Prohibition%22%2C%22target%22%3A%22http%3A%2F%2Fexample.com%2Fasset%3A9898%22%2C%22action%22%3A%22modify%22%7D%7D On Fri, Jan 27, 2017 at 12:20 PM, Rob Sanderson <notifications@github.com> wrote: > @riannella <https://github.com/riannella> That should work :) You would > want to distinguish between @type <https://github.com/type>:@id > <https://github.com/id>, and @type <https://github.com/type>: @vocab > <https://github.com/vocab> if you want to avoid prefixes in the values. > The distinction is described here: https://www.w3.org/TR/json-ld/ > #type-coercion > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://github.com/w3c/poe/issues/46#issuecomment-275720914>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ADwBfyqBYIEvUyRvfWYeDUBqq2mAM3OPks5rWidLgaJpZM4KZWR0> > . > -- GitHub Notification of comment by stuartmyles Please view or discuss this issue at https://github.com/w3c/poe/issues/46#issuecomment-276411010 using your GitHub account
Received on Tuesday, 31 January 2017 16:20:00 UTC