RE: protocol question

Rob – Yes  I  realized that;  the “dual property” issue isn’t the issue I’m raising .   I would like to see an example (regardless of property) where the body is a resource.  Intuitively, it feels like the object would simply be the URI of the body, residing at the client,  but recent discussion has hinted that the body needs to be transferred to the server (where the annotated resource resides) which doesn’t make a lot of sense to me.

Thanks.

Ray

From: Robert Sanderson [mailto:azaroth42@gmail.com]
Sent: Tuesday, March 17, 2015 5:56 PM
To: Denenberg, Ray
Cc: Web Annotation
Subject: Re: protocol question


Hi Ray,

I put this example in before the discussion that resulted in returning to the simple indeterminate "body" key.

I'll fix this when I get to the next round of edits (hopefully next week!) and will make a github issue to track.

Thanks!

Rob


On Tue, Mar 17, 2015 at 2:49 PM, Denenberg, Ray <rden@loc.gov<mailto:rden@loc.gov>> wrote:


In example 10, http://w3c.github.io/web-annotation/protocol/wd/


Example 10
HTTP/1.1 201 CREATED
Content-Type: application/ld+json
ETag: "_87e52ce126126"
Location: http://example.org/annotations/anno1

Allow: PUT,GET,OPTIONS,HEAD,DELETE,PATCH
Content-Length: 246

{
  "@context": "http://www.w3.org/ns/oa",
  "@id": "http://example.org/annotations/anno1",
  "@type": "oa:Annotation",
  "annotatedAt": "2015-01-31T12:03:45Z",
  "bodyValue": "I like this page!",
  "target": http://www.example.com/index.html


}

The annotation uses a literal body "I like this page!".

I don’t see an example where the body is a resource.  Could you give an example of this (or if there is one and I am missing it please point me to it), because I am not clear about the behavior in that case.

Thanks.

Ray



--
Rob Sanderson
Information Standards Advocate
Digital Library Systems and Services
Stanford, CA 94305