Web annotation & data usage vocabulary

Hi Frederick,

I thought I had sent something on this topic in the past but it seems to be
missing from my sent box, so maybe not. Even though the Web Anno standard
is designed such that folks can easily extend with their own motivations, a
few of the DUV motivations jump out at me.

In particular "cites", "rates", and "corrects". The "consumes" and
"endorses" motivations might be a little more tricky to accommodate. They
both remind me of use cases that Bob Morris brought to us from the natural
history musuem digitization work he was involved with. In their case an
additional property "hasExpectation" was also needed to clearly define the
expected task that the machine should carry out in relation to particular
motivations -- like "consumes" and "endorses".

At risk of resurrecting long dead horses, is there a certain sub-class of
motivations which directly relate to expected behaviors for machine
workflows? Is this an issue that we should discuss further? Because it
seems like expectations are going to be important to something like DUV
where there is a clear cycle of "why something was annotation" -- the
motivation -- informing some workflow about "what to do with it" -- an
expectation.

Regards,

Jacob
_____________________________________________________
Jacob Jett
Research Assistant
Center for Informatics Research in Science and Scholarship
The Graduate School of Library and Information Science
University of Illinois at Urbana-Champaign
501 E. Daniel Street, MC-493, Champaign, IL 61820-6211 USA
(217) 244-2164
jjett2@illinois.edu