RE: Embedded Content

Rob - I can sum up my position on this as follows: if nobody else had recommended it, I was planning to.  Thanks.  --Ray

From: Robert Sanderson [mailto:azaroth42@gmail.com]
Sent: Sunday, October 12, 2014 4:42 PM
To: Web Annotation
Subject: Embedded Content


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?

Thanks!

Rob


--
Rob Sanderson
Technology Collaboration Facilitator
Digital Library Systems and Services
Stanford, CA 94305