api
api copied to clipboard
Source for API and model specifications documents (api and model)
Is the language property allowed in rendering? ```json "rendering": [{ "id":"https://example.org/book1.pdf", "type":"Text", "label":{"en":["Download as PDF"],"de":["Als PDF herunterladen"]},"format":"application/pdf", "lanugage": ["de", "en"] }] ``` For me the documentation is a little bit...
partOf in https://iiif.io/api/presentation/3/context.json does not exist in dcterms, the correct dcterms property would be :isPartOf. @OyvindLGjesdal investigated the issue further and found that there likely was a mixup when "within"...
There is some ambiguity with the [IIIF Image API Selector](https://iiif.io/api/annex/openannotation/#iiif-image-api-selector) and how rotation relates to the annotation target. When you have an annotation body like this: ``` { "type": "SpecificResource",...
In the [IIIF Presentation 3 specification](https://iiif.io/api/presentation/3.0/) the `language` property is documented under [3.2 Technical properties](https://iiif.io/api/presentation/3.0/#32-technical-properties) but in the [Summary of property requirements](https://iiif.io/api/presentation/3.0/#a-summary-of-property-requirements) table it is listed as a "Descriptive and...
The IIIF Image API supports a kind of `selector` as defined in https://iiif.io/api/annex/openannotation/#iiif-image-api-selector. It states: > This document describes extensions to the [Web Annotation](http://w3.org/TR/annotation-model/) Data Model required within the IIIF...
For example to allow a thumbnail sprite sheet
* Spec name to include starship `Vesuvian Starship`
Relies upon work in https://github.com/IIIF/api/issues/2202
There are many applications for specific use-cases which produce large amounts of annotations on multiple images. Examples are OCR/HTR or crowdsourcing of transcription of books producing transcribing annotations or AI/CV...
For example, as we migrate between systems, identifiers will change which will break annotations (and so on). While it's not the spec's job to /solve/ persistent identifiers, we could add...