W3C home > Mailing lists > Public > public-openannotation@w3.org > November 2012

F2F Decision: Sub-classing - Editing, Motivation/Expectation

From: Paolo Ciccarese <paolo.ciccarese@gmail.com>
Date: Fri, 2 Nov 2012 09:12:42 -0400
Message-ID: <CAFPX2kBPwE37kxeBxgD66-8gMejbHvi_A0YebO20v_6LOZp1JQ@mail.gmail.com>
To: public-openannotation <public-openannotation@w3.org>
Layla,
I agree with you that Editing is a bit vague. However,  I could think of it
as a superclass of, for instance, Updating.
I am not expecting OA to provide all the motivations classes but to provide
some useful scaffolding.

Keeping in mind that it was not our intention, at this stage, to include
Expectation in the specs, the way I would distinguish between Motivation
and Expectation is that the first is about now and the second is about
later.

Example:
I see a typo in a document I can attach an annotation to fix that and
motivate it as 'updating' or 'fixing'. I can still have an expectation that
is 'updating'. The motivation explain why I've created the annotation. The
expectation details - if necessary - what I expect some agent - including
myself -  to do.

I don't use Expectations in Domeo yet. But I am starting thinking about it
to make the annotation actionable.

Paolo

-- 
Dr. Paolo Ciccarese
http://www.paolociccarese.info/
Biomedical Informatics Research & Development
Instructor of Neurology at Harvard Medical School
Assistant in Neuroscience at Mass General Hospital
+1-857-366-1524 (mobile)   +1-617-768-8744 (office)

CONFIDENTIALITY NOTICE: This message is intended only for the addressee(s),
may contain information that is considered
to be sensitive or confidential and may not be forwarded or disclosed to
any other party without the permission of the sender.
If you have received this message in error, please notify the sender
immediately.
Received on Friday, 2 November 2012 13:13:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 2 November 2012 13:13:10 GMT