W3C home > Mailing lists > Public > public-socialweb@w3.org > October 2014

RE: Hosted JSON-LD context

From: Markus Lanthaler <markus.lanthaler@gmx.net>
Date: Tue, 7 Oct 2014 10:07:27 +0200
To: <public-socialweb@w3.org>
Message-ID: <07de01cfe205$bd2d9a30$3788ce90$@gmx.net>
On 6 Okt 2014 at 23:36, 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.

You could map it to a blank node as a workaround. Simply set "@vocab" to "_:" and type-coerce "verb" to "@vocab" in the context.


> 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 Tuesday, 7 October 2014 08:07:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:26:13 UTC