Re: [web-annotation] Multiplicity and Collections

@azaroth42 I see the points you're making. I agree with your final one
 that identity debates are not something we need to have here. +1 for 
dropping Composite from the model. Counter proposal for Choice and 
List.

Remove Choice and List from model and refer implementers to activity 
stream's ordered collections via non-normative best practice 
documentation as both choice and list seem out of scope for 
annotations per se. 

One of the issues I'm stumbling with is consistency of approach. For 
Composites you say, "I disagree that there is any implication that a 
consuming software agent will combine resources in a Composite in any 
way that they might not also do for a List." However your expectation 
for Choice is precisely the opposite. Thus the need to differentiate 
it from a List. I hate to sound unreasonable but this approach only 
meets the needs of certain community members. Since, on the whole, I 
think this is a Containers issue, I think the whole matter is out of 
scope for us and better left for a group dedicated to looking at 
Containers and combinatorial expectations.

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

Received on Tuesday, 19 January 2016 16:36:48 UTC