Re: [web-annotation] Allow >1 role per resource

@iherman Of course I agree with your reasoning to use the Priority of 
Constituencies (users over authors over implementors over specifiers 
over theoretical purity), but I differ with your conclusion.

As @azaroth42 points out, users aren't going to hand-code annotations 
[1]. Unlike tagging, where users can select from a pre-set vocabulary 
or even write in free-form tags, users won't be explicitly selecting 
the  annotation motivation, they'll be selecting it from UI options, 
which are most likely to be modal (e.g. you either select the 
highlight tool, or the comment tool, or whatever other tool; for 
variations (like editing), you might type into the input field for 
some aspect, or leave it blank. Based on which tool the user selects, 
the UA picks the most appropriate motivation. (If the motivation 
choice isn't clear, then that's a problem with which set of 
motivations we've define, which is why I raised #113 ).

So, the question is, what behavior best meets user needs, each body or
 target having multiple motivations or a single one? You suggest that 
users will always select "more options"; I think it's more likely that
 users want simple choices (or better yet, to not have to think at all
 about the options at this level), to make it easier to create an 
annotation, and also will want their annotations to work the same 
across different annotation UAs. Both of these considerations could 
argue for a single value, which is simpler and more likely to achieve 
interoperablity. 

Obviously, we could construct other arguments around "which is better 
for user experience"… but we don't have real data. I suggest that once
 we introduce multiple values for `role`, we are not going to have the
 option to step back out of that once we have real data from a variety
 of UAs; whereas, if we constrain it to a single value, we could 
revisit that decision in v2, if some evidence shows that we really do 
need it.

I like @BigBlueHat's suggestion that we write up examples of both 
models, and try to test the performance characteristics.

[1]: "the number of annotations that are writen by hand without a UI 
is going to be vanishingly small". (I'm not sure why he though I was 
asserting that people would hand-code annotations… I was referring to 
different annotation generators, not people, making different choices 
about combinations.)

-- 
GitHub Notification of comment by shepazu
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/104#issuecomment-158688119
 using your GitHub account

Received on Saturday, 21 November 2015 22:36:13 UTC