W3C home > Mailing lists > Public > public-annotation@w3.org > November 2015

[web-annotation] Justify each Motivation with a behavior

From: Doug Schepers via GitHub <sysbot+gh@w3.org>
Date: Fri, 20 Nov 2015 17:57:43 +0000
To: public-annotation@w3.org
Message-ID: <issues.opened-118092627-1448042262-sysbot+gh@w3.org>
shepazu has just created a new issue for 

== Justify each Motivation with a behavior ==
Currently, we have 13 motivations (to be used as a set of values for 
the `Motivation` and `role`/`motive` properties): 
`bookmarking`, `classifying`, `commenting`, `describing`, `editing`, 
`highlighting`, `identifying`, `linking`, `moderating`, `questioning`,
 `replying`, `reviewing`, `tagging`.

I have no problem with any of these values, but at least some of them 
seem arbitrary… that is, what distinguishes them from any other 
perfectly reasonable value (or rough synonym for any of the existing 

My suggestion is that we establish a core set of motivations that are 
distinguished by their expected behavior in UAs, either in terms of 
processing or presentation, and that other values are considered as 
subsets of those core motivations.

For example, `commenting`, `tagging`, `replying`, `highlighting`, and 
`editing` have each been described, in some conversations (though not 
in the spec) as having a unique presentation style, and in some cases,
 unique action options for end users. I'm not suggesting we mandate 
those behaviors, but we could describe examples that a UA might use as

This makes it easier for implementations to know how to apply a 
motivation to each body or target, and how to process each of them; by
 describing concrete behaviors, it also helps users to understand 
these motivations.

It also lets communities that have a specific set of motivation terms 
use those, and simply map them to ones that the UA "understands"… 
since we can't serve every community (or language), we simply define 
behaviors and actions, and not shades of meaning. If some particular 
motivation is not understood by a UA, it could default to treating it 
like a `commenting` body.

Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/113 using your GitHub 
Received on Friday, 20 November 2015 17:57:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:42 UTC