when there are multiple annotation pages, is it ok to just have users select a specific annotation page to display at one time, like Aviary (rather than trying to combine multiple annotation pages into a single display)?
When providing a label to filter annotation sets and to display next to each annotation, do we use the AnnotationPage label (Aviary and AvAnnotate provide) or the textualBody with purpose=tagging label (just AVannotate provides but might be better solution)?
How to handle multiple annotation bodies in a single annotation? Do they all get concatenated into a single annotation? Do we want all textualbodies regardless of purpose or just some?
Annotations with motivation of commenting (AVAnnotate) and supplementing (Aviary) were called out. Are there other motivation types that we need to support?
Will textualbodies that have HTML have the format=text/html attached so we know to expect HTML?
-- From Ben: "I think that's an artifact of us designing the datamodel and then users putting HTML into the app. We probably should change the format to text/html."
Aviary currently uses motivation=transcribing and motivation=subtitling. Can we ignore annotations with those motivations for now as we expect there to be a new provides property to label them?
Sample AVAnnotate manifests:
Tanya's presentation from the IIIF Online Meeting workshop has a nice list of sample manifests, including multi-item manifests.
Aviary
Structural ranges that cross file boundaries - we don't have an example AVAnnotate or Aviary manifest for this yet
Some things noted that Ramp needs to support: