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

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

From: Rob Sanderson via GitHub <sysbot+gh@w3.org>
Date: Fri, 20 Nov 2015 17:40:18 +0000
To: public-annotation@w3.org
Message-ID: <issue_comment.created-158469393-1448041218-sysbot+gh@w3.org>

1)  Concrete use cases are given in the issue, and were brought up by 
@paolociccarese as an implementation requirement.  So I disagree with 
your first point. Unless you intend to refute those provided use 

2) Agree that processing an array is more expensive than switching on 
a string. However I think that switching on many strings (and note 
that they're not /actually/ strings, they're URIs that identify 
instances of the oa:Motivation class) is harder than processing an 
array of enumerable options.  All three use cases in the issue would 
require a combinatorial explosion, which is worse than combining as 
needed in an array.

3) Don't do that then. We can't predict what everyone will need, and 
we should not try to.  If someone creates an annotation with a body 
that has two roles that the UA doesn't know what to do with, then it 
won't display properly, and it'll get fixed. No one likes broken 
windows when it comes to their own content.  Secondly, and more 
relevantly, the number of annotations that are writen by hand without 
a UI is going to be vanishingly small. Creation UAs won't permit 
conflicting combinations, and hence there won't be a problem for 
Display UAs.  Likely those UAs will be fill both roles (but not 

4) We haven't done that so far, otherwise we would not have string 
literal bodies and we would not have hasRole on TextualBody, we'd 
require a SpecificResource.  So yes, I agree with your point ... and 
if we can agree on that as a design principle and follow through with 
it, then I think the model would be much more coherent and elegant. 
But at the moment, that's not the case.

I also disagree with:
> We are still in the early phases of this annotation model...

__We__ have had a lot of experience with it, and there are many 
hundreds of millions of annotations out there using OA. Just yesterday
 we got 500,000 of them from a partner on a small project. The use in 
IIIF at the Internet Archive alone is significantly greater than 10 
million. In the IIIF space as a whole there's greater than 100 million
 annotations.  Combined with other implementations and there's 
probably over a billion annotations in the OA model.  It has been 
worked on consistently for more than 5 years, and has global adoption.

GitHub Notification of comment by azaroth42
Please view or discuss this issue at 
 using your GitHub account
Received on Friday, 20 November 2015 17:40:22 UTC

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