W3C home > Mailing lists > Public > public-openannotation@w3.org > April 2013

Suggestions from iAnnotate Conference

From: Robert Sanderson <azaroth42@gmail.com>
Date: Wed, 24 Apr 2013 14:13:05 -0600
Message-ID: <CABevsUGuf2+2M7kf6aft2t9T548S2QmBVfhEJw_o1MdM20-hKg@mail.gmail.com>
To: public-openannotation <public-openannotation@w3.org>
Dear all,

Two weeks ago there was a very successful conference in San Francisco:
Some suggestions were raised which I will endeavor to paraphrase.

*  From Puneet Kishor of Creative Commons:
There should be an explicit license/rights statement for the annotation, or
any of the other resources.

Rob: Agreed. I propose that we add dcterms:rights to the provenance table
Although this is clearly possible already just not stated, it seems an
important enough use case to be included in the specification itself.

And an additional question: How do we determine which fields are worth
discussing in the specification and which are community driven?  For
example rdfs:label / dc:title for an Annotation seems like another very
common property that could benefit from standardization.

* From Randall Leeds of Hypothes.is and Blaine Cook of Poetica:
The revised context misses the point of JSON-LD contexts, which are to make
the serialization as natively JSON friendly as possible.  The "hasFoo"
style properties should be made more JSON-esque rather than RDF-esque.

Rob: Which is what we used to have, and then changed it to mirror the RDF
The JSON context to me is where we can make the lives of developers easier
... but we need more information on what is easier and what isn't.  It
seems like further discussion would be useful as this is an area where
getting it right will make a large different to implementations with no
added cost to the model or semantics.

* Nick Stenning previously of the Open Knowledge Foundation, plus others:
Interoperability comes from APIs not [just] data models. How do I get these

Rob:  HTTP is the API. However there was a long and very good discussion
about how exactly that should work. Should there be a companion API
document? Or should have a further section in the publishing module to
explain a simple REST API using the JSON-LD serialization as payload?

Many thanks all,

Received on Wednesday, 24 April 2013 20:13:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:38:22 UTC