-
### Description
Here are some highlighted notes from IIIF emails on where Avalon can prepare, and/or be informed of upcoming IIIF group meeting desired outcomes. Maybe this helps as a reference item…
-
### Description
Add support in the IIIF player / parser for `thumbnail` property. Example manifest created by @mcwhitaker here: http://dlib.indiana.edu/iiif_av/lunchroom_manners/lunchroom_manners_v4…
-
This sentence reads a bit strange to me.
`Note well that Annotation Lists must not be embedded within the manifest`
Source: http://iiif.io/api/presentation/2.1/#annotation-list
Maybe the `we…
-
Any reason why we omitted these from the list of do-not-strip tags?
From: DDMAL/tripoli#2
-
If we allow the canvases to be referenced from the main sequence, then this is only as much additional information as another range.
(Related to #58, #646)
-
Collections with the viewingHint of `multi-part` can be used to represent multi-volume works. Each volume is a separate manifest, and the set of volumes is the collection. If we had modeled this a…
-
In the implementation notes for the Presentation API, we say that clients should process the `@graph` JSON-LD keyword if they want to be fully conforming. Either this should be a requirement in the t…
-
As a subset of #76, the Presentation API should at least be consistent in how it describes client requirements. Currently the requirements are spread throughout the text, making it difficult to kno…
-
As per presentation API 2.1 labels are required for canvases.
While having labels is certainly a Good Things, the fact that there are mandatory may tempt manifest publishers to create not-so-useful la…
-
It would've helped if I looked harder for this previously. It's not stable yet but there are some changes we can make now.
https://github.com/IIIF/iiif.io/blob/prezi3/source/api/presentation/3.0/in…