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

@azaroth42 
> 1) Concrete use cases are given in the issue, and were brought up by
 
> @paolociccarese as an implementation requirement. So I disagree with
 
> your first point. Unless you intend to refute those provided use 
cases?

By concrete use cases, do you mean "tagging + describing", "editing + 
ext:typoReplacing", and "describe + identify"? None of those seemed 
compelling enough to overcome the downsides of added complexity, 
additional processing requirements, and risk of non-interop. In some 
cases, you could simply add tags to get the additional nuance you're 
looking for, especially in the case of the motivation extension 
("ext:typoReplacing").

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

Received on Friday, 20 November 2015 19:54:32 UTC