- From: Ivan Herman via GitHub <sysbot+gh@w3.org>
- Date: Thu, 10 Mar 2016 09:01:55 +0000
- To: public-annotation@w3.org
> On 10 Mar 2016, at 00:40, Rob Sanderson <notifications@github.com> wrote: > > This came up in the IIIF use of collections (lists) of Annotations [1], so I'll raise it here too for consideration. > > If you have a set of AnnotationCollections, each with some reasonably large number of Annotations in them, it would be a practical improvement to not require the client download all of the lists just to determine which of them contain annotations that target the resource(s) of interest. Instead the annotation collection could optionally link through to the target of the annotations. > > Essentially this is the propertyChain of from AnnotationCollection through AnnotationCollectionPage to the individual Annotations in items, to each hasTarget, and then potentially also down to hasSource if the target is a specific resource. > > I understand the value of this in terms of the interaction patterns and optimization, but equally could be premature optimization. Any thoughts as to the value would be appreciated :) > My gut feeling is that this is indeed some sort of a premature optimization. Do we have implementation experience for something like that? I think we may want to decide to postpone this for a possible 2nd version. > [1] AnnotationList and forCanvas: IIIF/iiif.io#754 <https://github.com/IIIF/iiif.io/issues/754> -- GitHub Notification of comment by iherman Please view or discuss this issue at https://github.com/w3c/web-annotation/issues/184#issuecomment-194743807 using your GitHub account
Received on Thursday, 10 March 2016 09:02:00 UTC