Re: [web-annotation] Unable to have a graph as the body of an annotation

Not sure why this is called "Unable to have a graph as the body" as 
there should be nothing wrong with your proposed example anyway. In 
the default graph it would simply say 

```json
{
  "@id": "http://example.org/annos/1",
  "@type": "oa:Annotation",
  "body": "http://example.org/users/rob",
  "target": "http://example.com/logo.jpg"
}
```

That the graph `http://example.org/users/rob` happens to be included 
is just a convenience. 

I think I agree on closing this though, as trying to formalize this is
 tricky with regards to annotation servers (we faced this issue in 
Annotopia) - as the client can use arbitrary `@id` for their graph 
without the graph content necessarily matching at all what you get if 
you resolve that URI.  (This is covered by the [RDF 1.1: On Semantics 
of RDF Datasets](http://www.w3.org/TR/rdf11-datasets/) W3C note.)

-- 
GitHub Notif of comment by stain
See 
https://github.com/w3c/web-annotation/issues/16#issuecomment-150137320

Received on Thursday, 22 October 2015 07:54:37 UTC