[web-annotation] Allow >1 role per resource

azaroth42 has just created a new issue for 
https://github.com/w3c/web-annotation:

== Allow >1 role per resource ==

TextualBody and SpecificResource say that there may be 0-1 roles, 
however there are use cases where multiple roles would be valuable:

  * Tagging + clarification. For example tagging + describing, to 
distinguish from just describing where the body is full text.
  * Broad + specific. For example editing + ext:typoReplacing, to have
 a general category and a more specific, machine actionable role that 
would only be understood by limited implementations 
  * Conciseness. If the same resource really plays two roles, it would
 be strange to have it as two bodies rather than just giving it two 
roles. For example, the text of the body may both describe and 
identify the target.

Proposal: Change 3.2.2.2 and 4.1 to both be MAY have 1 or more roles


See https://github.com/w3c/web-annotation/issues/104

Received on Friday, 6 November 2015 19:40:15 UTC