- From: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
- Date: Mon, 06 Oct 2014 23:42:00 +0200
- To: James M Snell <jasnell@gmail.com>
- CC: "public-socialweb@w3.org" <public-socialweb@w3.org>
On 10/06/2014 11:36 PM, James M Snell wrote: > Yep... that's a challenge with the JSON-LD mapping in this case. > Activity Streams 1.0 allows "verb" and "objectType" to be simple token > values like "post", or "person"... those don't expand out to URI's... > they are *just* tokens. The values of those fields can also be fully > qualified IRI's, however. There's no way to model that in JSON-LD > currently. I hope tomorrow we'll get chance to discuss it over call: https://www.w3.org/wiki/Socialwg/2014-10-07#ActivityStreams_2.0_compatibility_with_AS1.0_and_JSON-LD /me needs to catch some ZZZzzz... now :) gnight! > > On Mon, Oct 6, 2014 at 2:32 PM, ☮ elf Pavlik ☮ > <perpetual-tripper@wwelves.org> wrote: >> On 10/06/2014 11:09 PM, James M Snell wrote: >>> For debugging and experimentation purposes, I have hosted the current >>> editor's draft version of the Activity Streams 2.0 JSON-LD @context >>> here: http://asjsonld.mybluemix.net/ >> oh yeah! CORS enabled \o/ >> >>> >>> You can use this, for instance, with the JSON-LD Playground: >>> http://goo.gl/bY3p5j >> in your example you have "verb": "post" (string literal not IRI, while >> no @base set) >> while context defines >> "verb": { >> "@id": "as:verb", >> "@type": "@id" >> } >> >> so N-Quads tab has only 3 statements and no as:verb "post" >> >> which makes me once again worry about >> https://github.com/jasnell/w3c-socialwg-activitystreams/issues/23 >
Received on Monday, 6 October 2014 21:44:11 UTC