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

> On 4 May 2016, at 15:52, Paolo Ciccarese <notifications@github.com> 
wrote:
> 
> Hi @iherman, 
> I am ok with having a separate discussion, however I am not sure 
this is a different topic.
> 
> We can ask to use multiple targets for targeting translations as you
 stated above, in fact that is consistent with the current definition 
of multiple targets ("Body is considered to be equally related to each
 Target individually"). If we annotate different content formats, that
 is addressed by having different States.
> 
> So, I would say that allowing multiple selectors would serve the 
purpose of annotating multiple targets as a single unit. Which to me 
seems a pretty straightforward interpretation as well.
> 

I am not sure we are in agreement here, but I may misunderstand you.

In my understanding, the correct solution for encoding your example, 
ie, the reference to Paolo and Ciccarese, is to use multiple targets 
in the same annotation. One target is for 'Paolo' and the other is for
 'Ciccarese'. Each of those targets may use several selectors, but 
each of those selectors  should address 'Paolo' (resp. 'Ciccarese') in
 some way or another.

Conceptually, at least in my mind, having several targets in the same 
annotation is like adding an annotation on the 'combination' (without 
specifying what 'combination' means) of the targets. That is the 
reason of keeping them in the same annotation.

Is this what you meant?

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

Received on Wednesday, 4 May 2016 16:06:32 UTC