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

Re: Annotation creation and updates

From: Bob Morris <morris.bob@gmail.com>
Date: Fri, 25 Apr 2014 15:38:16 -0400
Message-ID: <CADUi7O56=NoXL7gXUfWsmLgntG+QBW_FhCoJcuU727LnuUa2Vw@mail.gmail.com>
To: Paolo Ciccarese <paolo.ciccarese@gmail.com>
Cc: public-openannotation <public-openannotation@w3.org>
Hmmm.  Come to think of it, consider  parsing in natural English
("subject predicate object"), we would expect that it is not the
Target, but rather the oa:Annotation that is being annotatedAt
2014-02-17T09:46:11EST, . At the very least, to preserve your model
and natural English, the creation predicates would need changing to a
form like the pav:  forms, which suggests that (a)the pav: forms are
enough alone (b) the breadth of the PROV expressiveness is so high
that, has Herbert et al. suggest,  OA could express its use as
connected by a single top-level provenance predicate
("oa:hasProvenance") with rdfs:range in PROV, perhaps along with some
minimal expected prov terms.

None of the above is meant to address your questions about what should
be the nature of update history.  IMO this is a very domain-specific
issue.  For example,  the scientific names of species change over
time, each change associated with a publication.  The order of these
changes and the provenance of citations of them, is very relevant and
,sadly, often impossible to memorialize in one or another relational
database.  Thus  arguably, if a set of annotations is about species,
then having nothing but "original" and "latest" updates to an
annotation might be far from enough.  On the other hand, consider an
annotation of <http://mbta.com/commuterRailLine/Fitchburg#> which has
Body a train schedule object. This might well do with only a
'lastUpdate' attribute.


On Fri, Apr 25, 2014 at 11:09 AM, Paolo Ciccarese
<paolo.ciccarese@gmail.com> wrote:
> Dear all,
> I am currently developing the Annotopia Open Annotation server [1][2][3] and
> there are a few topics that I believe would be wise to discuss in the
> mailing list in order to collect some additional feedback.
> I will start with one topic: keeping track of annotation creation and update
> (date/agent).
> I collected some non conclusive thoughts here:
> http://hcklab.blogspot.com/2014/04/annotopia-creationupdates-with-open.html
> No versioning for now. If that is of interest, months ago, I wrote some
> thoughts here: http://www.w3.org/community/openannotation/wiki/Versioning
> In short, I am currently thinking of using PAV [4] with something like this:
> {
>     "@id" : "http://host/s/annotation/830ED7EE-BF7B-4A18-8AE1-A9AF96AC135B",
>     "@type" : "oa:Annotation",
>     "annotatedAt" : "2014-02-17T09:46:11EST",
>     "annotatedBy" : {
>       "@id" : "http://orcid.org/0000-0002-5156-2703",
>       "@type" : "foaf:Person",
>       "name" : "Paolo Ciccarese"
>     },
>     "pav:createdOn" : "2014-02-17T09:48:11EST",
>     "pav:createdBy" : {
>       "@id" : "http://orcid.org/0000-0002-5156-2703",
>       "@type" : "foaf:Person",
>       "name" : "Paolo Ciccarese"
>     },
>     "pav:lastUpdateOn" : "2014-03-11T11:46:11EST",
>     "pav:lastUpdateBy" : {
>       "@id" : "http://example.org/johndoe",
>       "@type" : "foaf:Person",
>       "name" : "John Doe"
>     }
> ...
> }
> Where:
> (i) 'createdOn/createdBy' for the original creation on the (Annotopia)
> server
> (ii) 'lastUpdateOn/lastUpdateBy' for the last update on the (Annotopia)
> server
> Question is: what is 'annotatedAt' going to indicate once the annotation has
> been updated? The original creation or the latest update? In fact, some
> application will understand only the 'annotatedAt' property.
> Another option I have, to keep the actual annotation pure OA, is to collect
> the additional provenance data in a separate provenance graph that can be
> provided on demand by who can understand it.
> Any thoughts?
> Best,
> Paolo
> [1] GitHub (Code/wiki): https://github.com/Annotopia/AtSmartStorage
> [2] Slides (living documentation):
> http://www.slideshare.net/paolociccarese/annotopia-overview-by-paolo-ciccarese
> [3] Talk @ 'I Annotate 2014' https://www.youtube.com/watch?v=UGvUbFv0Zl8
> [4] PAV: http://www.jbiomedsem.com/content/4/1/37
> --
> Dr. Paolo Ciccarese
> Assistant Professor of Neurology, Harvard Medical School
> Assistant in Neuroscience, Massachusetts General Hospital
> Senior Information Scientist, MGH Biomedical Informatics Core

Robert A. Morris

Emeritus Professor  of Computer Science
100 Morrissey Blvd
Boston, MA 02125-3390

Filtered Push Project
Harvard University Herbaria
Harvard University

email: morris.bob@gmail.com
web: http://efg.cs.umb.edu/
web: http://wiki.filteredpush.org
The content of this communication is made entirely on my
own behalf and in no way should be deemed to express
official positions of The University of Massachusetts at Boston or
Harvard University.
Received on Friday, 25 April 2014 19:38:46 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:22:05 UTC