Re: [web-annotation] Model should allow multiple Selectors per SpecificResource

Hm. There is a bit of a mess indeed. As far as I can see (and looking 
at targets only) we have

1. the possibility to define multiple targets, which means "each Body 
is considered to be equally related to each Target individually, 
rather than to the set of all of the Targets."
2. the possibility to define a Choice, which "A Choice has an ordered 
list of resources from which an application should select only one to 
process or display. The order is given from the most preferable to 
least preferable, according to the Annotation's creator or publisher. 
" (which is a suitable terminology for a body, but should be different
 for a target; I believe this is, essentially, the OR feature of 
@jjett )
3. @tcole3 refers to "AnnotationCollection", but I am not sure that is
 relevant; that is a collection of full blown annotations, and not 
related to targets and bodies

Ie, we need, again to use @jjett's terminology, an AND. Can we do it 
similarly to "Choice", calling it "Combination" or something similar? 
That would also cover @paolociccarese's use case. We can add this to 
the model easily...

(However, this is _irrelevant_ to the multiple selector issue! Can we 
really move this thread to a separate issue, unless we get to a quick 
solution?)

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

Received on Thursday, 5 May 2016 09:39:23 UTC