W3C home > Mailing lists > Public > public-annotation@w3.org > November 2015

Re: [web-annotation] Multiplicity and Collections

From: BigBlueHat via GitHub <sysbot+gh@w3.org>
Date: Mon, 23 Nov 2015 22:18:38 +0000
To: public-annotation@w3.org
Message-ID: <issue_comment.created-159085214-1448317117-sysbot+gh@w3.org>
Anyone want to do a quick cost analysis on removing (vs. keeping) the 
multiplicity stuff we have now vs. switching to AS's *Collection 

The area I see this being the most risky (and valuable) are for 
storing selectors--especially `Choice`--but even here, I see UA's 
doing whatever they think is best despite what they're given.

For instance, you could tell a UI to choose between two selectors, but
 if the UA tries one and it fails?...it's going to try the other one 
(or that's how I'd write it). If you didn't define it as a `Choice` 
(but just put them in the `target` array), a UA would try them both 
and Do The Right Thing (in its eyes only) for resulting in what the 
user expects--i.e. the best selection that UA can give them.

So. If there's some other scenario where these things *must* be 
used--and for which a UA wouldn't just "figure it out" (as best it 
can)...then we should spec to those use cases. If not, then we should 
at least mark this section as "at risk"...or replace with something 
simpler (as is the propose of this issue).

@jjett you're the one with the greatest interest in these things 
(afaik). Would you mind connecting the current multiplicity bits to 
some use cases (maybe in the wiki?) and explain why the other options 
aren't useful to you? I'm thinking something similar to what we did 
for the 
[Roles](http://w3c.github.io/web-annotation/model/wd/roles.html) work 
which originally started on the wiki.

Thanks in advance! :wink:

GitHub Notification of comment by BigBlueHat
Please view or discuss this issue at 
 using your GitHub account
Received on Monday, 23 November 2015 22:18:42 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:42 UTC