- From: dorian taylor <dorian.taylor@gmail.com>
- Date: Sun, 19 Jan 2014 10:13:21 -0800
- To: public-openannotation <public-openannotation@w3.org>
For what it's On Sun, Jan 19, 2014 at 9:51 AM, Doug Schepers <schepers@w3.org> wrote: > Hi, Tim, Ivan– > > Yeah, what Tim said. > > But I also think there's a broader, more straightforward rationale: > > For a vast number of use cases, possibly the majority, the consumer of an > annotation will see it in HTML, in the form of footnotes, comments, or > proper annotations (like the Annotator sidebar or stickynotes); in many of > these cases, the annotation will even be stored as HTML, or a some > intermediate format like markdown that is predictably transformable into > HTML, rather than in some abstracted form like RDF or JSON or even > normalized SQL. Many annotations will be only accessible as HTML, even > through a service's API; think of Twitter, which will let you embed a tweet > on a page by hitting their API and getting back the HTML snippet. > > So, if we think it would be desirable to be able to consume, aggregate, and > catalog those annotations, we will want to provide clear guidance for how > developers of annotation-producing software (e.g., microblogs, commenting > systems, annotation libraries, and so on) can make markup that can be > explicitly consumed as conforming to the OA data model. > > Regards- > -Doug For what it's worth, this is more or less how I intend to use OA. In fact, I designed this protocol: http://doriantaylor.com/rdf-kv (reference implementation: http://search.cpan.org/dist/RDF-KV/lib/RDF/KV.pm ) with OA in mind. -- Dorian Taylor Make things. Make sense. http://doriantaylor.com
Received on Monday, 20 January 2014 10:49:29 UTC