Inverse properties using the @reverse keyword

[albertemozo]

Is there a way to use the JSON-LD @reverse keyword to invert properties?

Like in:

{
  "@context": "http://schema.org",
  "@id": "#homer",
  "@type": "Person",
  "name": "Homer",
  "@reverse": { "parent": [
      {
        "@id": "#bart",
        "@type": "Person",
        "name": "Bart"
      },
      {
        "@id": "#lisa",
        "@type": "Person",
        "name": "Lisa"
      }
    ]
  }
}

If not supported, what would be the correct way to represent a bidirectional relationship, if one of the sides is not present within the RDFA, from that particular side?

JSON-LD Specification
Schema.org docs

[teohhanhui]

Example 48 in the JSON-LD spec looks much more usable to me. Having all the reverse properties under @reverse seems so unintuitive...

[albertemozo]

I chose Example 47 after having failed my attempts to have Google's Structured Data Testing Tool parse Example 48 without errors.

In particular, I tried with this alternative:

{
  "@context": {
    "@vocab": "http://schema.org",
    "children": { "@reverse": "parent" }
  },
  "@id": "#homer",
  "@type": "Person",
  "name": "Homer",
  "children": [
    {
      "@id": "#bart",
      "@type": "Person",
      "name": "Bart"
    },
    {
      "@id": "#lisa",
      "@type": "Person",
      "name": "Lisa"
    }
  ]
}

Getting the following error:

There was an invalid type in your JSON-LD.

And also resulting in a different data structure.

So I'm not sure about what could be the best implementation, any of them would be great.

[teohhanhui]

This should have been fixed by #752