Is there, or could there be declared, a suitable value of
oa:modelVersion corresponding to
(how about, dare I say it, use that as the value)?

In our annotation generation  and consumption components, RuleML
rules, SPARQL queries from forms, ...., we are starting to move from
AO to OA. Embedding an oa:modelVersion in our annotations would help
us keep track of exactly where we stand, especially as OA evolves and
we find we need to make changes. We have several parts of our system
that all need to be using the same annotation vocabulary. I guess we
don't need a standardized oa:modelVersion, but we are also beginning
to think about the scope of our collaboration with others working on
the same kinds of biodiversity data annotation using OA. The more
agreement on modelVersion the less confusion...


Robert A. Morris

Emeritus Professor  of Computer Science
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://etaxonomy.org/mw/FilteredPush
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, 1 November 2012 20:31:43 UTC