Open mathewjordan opened 11 months ago
The Life of the Buddha project is an actual use-case for this. It currently uses the old Open Annotation motivations, oa:transcribing and oa:translating, to display transcriptions and translations of Tibetan texts that accompany several murals, associated with SVG outline annotations. An example of the current annotation list is here. We are upgrading and would certainly use these motivations if they were in the specification.
There is also this proof of concept from the Mmmonk project:
https://www.mmmonk.be/en/about-iiif/iiif-demo-liber-floridus
Thanks @glenrobson. I'll also add some additional context with screenshots for the component I am developing for a DH project. A different view using the same Manifests referenced above.
Another usecase from the cookbook repo regarding linking to ALTO and having annotations:
@mathewjordan Did you say you added screenshots for your current project work? I'm not seeing them in the story (just the original Mirador example).
Thank you @elynema. I forgot to attach. This is still in progress. But current state should convey direction of development. The general idea is that researcher using this IIIF component (dare I say viewer) can use the interface to distinguish between and search within the different textual bodies of the Annotations.
Description
You have a set of manuscripts in Arabic script that are represented as IIIF Manifests. The manuscripts have been transcribed in Arabic and translated to English. As part of a digital scholarship project, you would like to apply the transcriptions and translations as Annotations upon each Canvas, and have a way to inform the presentation layer which Annotations are transcriptions and which are translations so that they can be displayed appropriately.
Variation(s)
This use case applies a verbatim transcription of an Arabic manuscript along with an English language translation; however, there is no limitation on the number of translations that could be applied to the respective resources.
In another project focused wholly on transcriptions, more than one language may be present on a resource, requiring multiple Annotations with respective language properties. In that case, all Annotations of varying languages are
transcribing
and NOTtranslating
.Proposed Solutions
Introduce the Motivations of
transcribing
andtranslating
to properly declare "why" the Annotation is being applied to the respective resource.https://github.com/mathewjordan/iiif/blob/main/manifest/tsg/transcribing-translating.json#L176-L207
Additional Background
If considered,
translating
andtranscribing
are appliedsupplementing
motivations as they integrate content “from the Canvas.” IIIF Viewers such as Mirador output textual bodies in a desirable fashion for Annotations with the viewer-supportedcommenting
motivation, however, this Motivation is not aligned with why the Annotation is being applied. In either case, ifcommenting
orsupplementing
are utilized, there is no way to distinguish if the Annotations translate or transcribe the annotated resource. A user or a bespoke IIIF viewer would be required to infer that that one is a transcription and/or translation by language. Likewise, an Annotation adding commentary could not be distinguished from a translation or transcription of the resource.Web Annotation Data Model - 3.3.5 Motivation and Purpose
commenting
IIIF Presentation API 3.0 - 3.5 Values - Values for motivation
supplementing
See two Annotations with the Motivation of
commenting
using Mirador: https://projectmirador.org/embed/?iiif-content=https://raw.githubusercontent.com/mathewjordan/iiif/main/manifest/tsg/commenting.json