Re: [Specifications] Clarify behaviour when ApiDocumentation resource contains more than just itself (#202)

I think that framed example that fits better in this situation would look like this:

```jsonld
{
  "@context": {  },
  "@id": "http://some.app/api",
  "@type": "hydra:ApiDocumentation",
  "hydra:supportedClass": [
    {
      "@id": "api:ClassTwo"
    },
    {
      "@id": "api:ClassOne"
    }
  ]
}
```

Please note the lack of `@graph` - this is the shape of the document many of the JSON-LD users would aim to achieve and this is the sole issue non-RDF users may have.

-- 
GitHub Notification of comment by alien-mcl
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/202#issuecomment-558845891 using your GitHub account

Received on Tuesday, 26 November 2019 22:31:16 UTC