-
For scanned maps we serve a version 3 manifest at a path like v3/manifest. For audio we just serve v3 manifests from the original path.
Should we choose one of these two approaches over the other?
Ar…
-
## Description
Avalon currently writes `http://www.w3.org/ns/anno.jsonld` into the @context of all IIIF manifests. Running the IIIF validator against our manifests, the error "Top level @context is no…
-
Some works are being flagged in the alerts channel when a user tries to access the Item Viewer (https://wellcome.slack.com/archives/CQ720BG02/p1717403402624589).
This is because it can't find the III…
-
All the examples at https://mirador-download-plugin.netlify.app/ use IIIF presentation level 2 examples. Manifests using IIIF level 3 instead don't work - the plugin loads but no actual page gets show…
-
The IIIF specifications use warning blocks (marked `{: .warning}` in the source) which appear with a red bar and background, e.g. the "Incompatibility Warning" in https://iiif.io/api/presentation/3.0/…
-
In the IANA registration [1], we define a media type parameter called 'profile'. Its value is a space separated list of URIs, for which we registered six initial values. These can be composed togeth…
-
## Recipe Name
IIIF Manifest URIs in MARC21
## Use case
Store links to IIIF manifests in MARC21.
## Suggestion:
Field: 856
Subfield u: URI of the IIIF Manifest
Subfield q: Content-Type …
-
Thanks to @giacomomarchioro for reporting [here](https://github.com/IIIF/presentation-validator/issues/117).
Giacomo noticed that the rights statement in the example manifest:
https://iiif.io/ap…
-
For description see
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Content_negotiation
- https://iiif.io/api/presentation/3.0/#63-responses
On a property-by-property basis you will need to …
-
## Problem
In https://iiif.io/api/presentation/3.0/#51-collection, one usage of a Collection could be to allow clients to:
> - Receive a set of Manifests, such as search results, for rendering.
…