Re: Embedded Content

On 12 Oct 2014, at 22:42 , Robert Sanderson <azaroth42@gmail.com> wrote:

> 
> One of the most significant changes that we need to make is what to do about the use of the seemingly abandoned Content in RDF specification.
> 
> The issue:
> * https://github.com/w3c/web-annotation/issues/3
> * http://www.w3.org/annotation/track/issues/1
> 
> The proposal in the github issue is to create two new classes for embedded plain text and embedded base64 encoded text, corresponding to cnt:ContentAsText and cnt:ContentAsBase64 respectively.  
> 
> These classes would use the properties:
> * rdf:value -- for recording the content (required)
> * dc:format -- for the media type of the content (optional)
> * dc:language -- for the language of the content (optional)
> 
> In JSON-LD this might look like:
> 
> { 
>   "@type": "oa:Content",
>   "value": "I love this book!",
>   "format": "text/plain",
>   "language": "en"
> }
> 
> Comments?

That sounds fine to me. We certainly cannot and should depend on the Content in RDF; it is probably an overkill for what we need, and, as you observed on the call, it is unclear whether (and even if yes when) it will be finalized. 

Ivan

> 
> Thanks!
> 
> 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