Re: social-ISSUE-36 (JSON-LD contexts): Role and evolution of recommended JSON-LD @contexts [Activity Streams 2.0]

On 03/29/2015 09:04 PM, ☮ elf Pavlik ☮ wrote:
> On 03/29/2015 06:47 PM, Social Web Working Group Issue Tracker wrote:
>> social-ISSUE-36 (JSON-LD contexts): Role and evolution of recommended JSON-LD @contexts [Activity Streams 2.0]
>>
>> http://www.w3.org/Social/track/issues/36
>>
>> Raised by: Pavlik elf
>> On product: Activity Streams 2.0
> 
> We could also leverage JSON-LD @context for *inverse* properties. I just
> added note quoted below to this issue:
> 
> Inverse properties - we could also just use JSON-LD @reverse instead of
> defining them in vocabulary(ies)
> http://www.w3.org/TR/json-ld/#reverse-properties
I added this ISSUE to our agenda for next week
https://www.w3.org/wiki/Socialwg/2015-04-14#Activity_Streams_2.0

James, could you please elaborate little more on a comment you included
in the last week's agenda?
"Do we want to leverage JSON-LD mechanisms for reverse properties. There
are inherent complexities with this approach when working strictly with
the JSON-LD expanded form."

Thanks!