W3C home > Mailing lists > Public > public-rdf-comments@w3.org > August 2013

Official response to RDF-ISSUE-133: Provisional support for Reverse properties

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Tue, 13 Aug 2013 14:37:17 -0400
Message-ID: <520A7CDD.2070502@digitalbazaar.com>
To: Gregg Kellogg <gregg@kellogg-assoc.com>, RDF WG Comments <public-rdf-comments@w3.org>, Niklas Lindström <lindstream@gmail.com>, David Rogers <david.rogers@bbc.co.uk>
Hi David, Niklas, and Gregg,

This is an official response to RDF-ISSUE-133: Provisional support for
Reverse properties, which is being tracked here:


and here


Each of you had requested that the group support reverse properties in
JSON-LD. These have also been called inverse properties in the past. We
added provisional support for it in the JSON-LD Last Call and received a
number of responses in support of keeping the feature in future versions
of the spec.

The JSON-LD group discussed keeping the feature in the spec here:


and made the following resolution:

RESOLVED: Support reverse properties in JSON-LD 1.0.

Additionally, there were two follow up resolutions related to reverse
properties here:

RESOLVED: Allow "@container": "@set" for reverse properties.

RESOLVED: Remove the @type restriction for reverse properties. This also
means that a reverse property won't be implicitly type-coerced to @id

The feature has been implemented and deemed to be stable. The JSON-LD
group believes that this addresses your concerns with respect to this
particular issue. Please respond to this email as soon as possible to
let us know if we've addressed your concerns related to this issue to
your satisfaction.

-- manu

Manu Sporny (skype: msporny, twitter: manusporny, G+: +Manu Sporny)
Founder/CEO - Digital Bazaar, Inc.
blog: Meritora - Web payments commercial launch
Received on Tuesday, 13 August 2013 18:37:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:59:36 UTC