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

? best practice about extending motivations

From: Bob Morris <morris.bob@gmail.com>
Date: Thu, 11 Apr 2013 14:02:10 -0400
Message-ID: <CADUi7O4XhMYJtbHN5xgaZQAMcT6aHX+RzSXawzv9mQi7vfOnOQ@mail.gmail.com>
To: public-openannotation <public-openannotation@w3.org>
I'm finding a need for what appear to be somewhat annotation specific
motivations, typically more specific than one of the standard ones or
a few application-specific motivations.  Typically these are
text-based and not reusable, so the solution seems to add a local one,
e.g.:

=============================
ex:anno a oa:Annotation;
  oa:motivatedBy oa:editing;
  oa:motivatedBy ex:myMotivation;
  ....

ex:myMotivation a oa:Motivation;
  skos:inScheme ex:myScheme;
  skos:prefLabel "Integrate data found on the lab spreadsheet into the
database."

...

ex:myScheme ....
=============================

Somehow having a skos concept and scheme local to the annotation seems
very un-skos-like, but I don't see what else to do.

Bob





--
Robert A. Morris

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

IT Staff
Filtered Push Project
Harvard University Herbaria
Harvard University

email: morris.bob@gmail.com
web: http://efg.cs.umb.edu/
web: http://wiki.filteredpush.org
http://www.cs.umb.edu/~ram
===
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 Thursday, 11 April 2013 18:02:38 UTC

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