You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The most direct match to how TPEN does transcription information in presentation 2 AnnotationList is the presentation 3 AnnotationPage.
There are a couple situations in which these semantics fall somewhat short. For example, what if we want to have a Transcription and Translation by the same user for the same canvas within a single project. How does the interface know which to preference or whether to offer a choice or filter? It does not know whether they should be shown together, at the same time, or at all.
We have also considered making the "Column" construct as a List -- as in ORDER matters and can be labeled -- Making each Column as an individual AnnotationPage could do this, but then it could confuse the Transcription and Translation scenario if all of them are AnnotationPages where some are column groupings to show at the same time and some are Transcription/Translation to show one at a time.
Presentation API 3, via modern Web Annotation standards, offers us the Annotation Collection construct.
IIIF Says:
Annotation Collections represent groupings of Annotation Pages that should be managed as a single whole, regardless of which Canvas or resource they target. This allows, for example, all of the Annotations that make up a particular translation of the text of a book to be collected together. A client might then present a user interface that allows all of the Annotations in an Annotation Collection to be displayed or hidden according to the user’s preference.
For Annotation Collections with many Annotations, there will be many pages. The Annotation Collection refers to the first and last page, and then the pages refer to the previous and next pages in the ordered list. Each page is part of the Annotation Collection.
As Annotation Collections might get very large, the model distinguishes between the Collection itself and sequence of component pages that in turn list the Annotations. The Collection maintains information about itself, including creation or descriptive information to aid with discovery and understanding of the Collection, and also references to at least the first Page of Annotations. By starting with the first Annotation in the first Page, and traversing the Pages to the last Annotation of the last Page, all Annotations in the Collection will have been discovered.
Annotations may be within multiple Collections at the same time, and the Collection may be created or maintained by agents other than those that create or maintain the included Annotations.
We still need to put two and two together. How could TPEN use this? What use case(s) does it solve? What has to be done on the interface to process and render this information to the correct users?
The text was updated successfully, but these errors were encountered:
The most direct match to how TPEN does transcription information in presentation 2 AnnotationList is the presentation 3 AnnotationPage.
There are a couple situations in which these semantics fall somewhat short. For example, what if we want to have a Transcription and Translation by the same user for the same canvas within a single project. How does the interface know which to preference or whether to offer a choice or filter? It does not know whether they should be shown together, at the same time, or at all.
We have also considered making the "Column" construct as a List -- as in ORDER matters and can be labeled -- Making each Column as an individual AnnotationPage could do this, but then it could confuse the Transcription and Translation scenario if all of them are AnnotationPages where some are column groupings to show at the same time and some are Transcription/Translation to show one at a time.
Presentation API 3, via modern Web Annotation standards, offers us the Annotation Collection construct.
IIIF Says:
Web Annotation Says:
We still need to put two and two together. How could TPEN use this? What use case(s) does it solve? What has to be done on the interface to process and render this information to the correct users?
The text was updated successfully, but these errors were encountered: