Fwd: Summary of 10/28 TPAC f2f meeting

FYI on the annotation issue

Begin forwarded message:

> Resent-From: public-annotation@w3.org
> From: Robert Sanderson <azaroth42@gmail.com>
> Subject: Summary of 10/28 TPAC f2f meeting
> Date: 29 Oct 2014 11:19:13 PDT
> To: Web Annotation <public-annotation@w3.org>, public-openannotation <public-openannotation@w3.org>
> Archived-At: <http://www.w3.org/mid/CABevsUF7=o6RzxWsoKzPzNtdeOQRD7FBBRDoJuWqqruNMVPMgw@mail.gmail.com>
> List-Id: <public-annotation.w3.org>
> 
> 
> Dear all,
> 
> The raw, completely unedited, but reasonably readable minutes of the meeting yesterday at TPAC are online at:   http://www.w3.org/2014/10/28-annotation-minutes.html
> 
> To summarize the consensus points:
> 
> * There was a request from the CSV Working Group to allow strings directly as the body of an annotation.  This also came up in the community group, as many may recall.
> 
> The consensus was to accept the request with the following conditions:
> -- Only plain xsd:strings are supported.
> -- As soon as the body has any other datatype, language or property, the current resource model must be used.
> 
> Thus the following becomes a legal annotation:
> { 
>   "@type": "oa:Annotation",
>   "oa:hasBody": "This is my comment",
>   "oa:hasTarget": "http://some.uri/index.html"
> }
> 
> A consequence is that external bodies MUST take the form:
> {
>   "oa:hasBody": {"@id": "http://some.uri/body.txt"}
> }
> 
> (But note that targets are unchanged and must always be resources, thus allowing just the URI as a string in the JSON-LD serialization)
> 

<snip/>

> Any corrections to my memory and interpretation are very welcome :)
> 
> Best regards,
> 
> Rob
> 
> -- 
> Rob Sanderson
> Technology Collaboration Facilitator
> Digital Library Systems and Services
> Stanford, CA 94305


----
Ivan Herman, W3C 
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
GPG: 0x343F1A3D
WebID: http://www.ivan-herman.net/foaf#me