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

I (likely unsurprisingly) prefer the liberal option. No implementation
 is going to support 100% of the features. If an implementation will 
only process one role, then that's very unlikely to be a significant 
problem (IMO). Compare to, for example, not processing 
HTTPRequestState, where you would end up with the wrong 
representation.  Or not processing the only Selector associated with a
 SpecificResource, and thus not know where to anchor the selection to.

I agree with @iherman about time being important and focusing on 
making progress. We have a lot of much bigger decisions to make than 
this, on all of our deliverables.

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

Received on Monday, 23 November 2015 17:47:43 UTC