...
| Info |
|---|
The definitions of the terms MUST, MUST NOT, SHOULD, etc. used in this document can be found at https://tools.ietf.org/html/rfc2119 |
Step 1: Provide the IIIF Resource as EDM WebResource
| Tip |
|---|
Providers MUST identify the type of link between the IIIF resource for the object and the object. |
...
| Tip |
|---|
From IIIF v2.1 guidelines: https://iiif.io/api/image/2.1/#uri-syntax: The IIIF Image API URI for requesting an image must conform to the following URI Template: {scheme}://{server}{/prefix}/{identifier}/{region}/{size}/{rotation}/{quality}.{format} e.g. http://www.example.org/image-service/abcd1234/info.json |
Step 2: Flag the WebResource as IIIF-compliant
| Tip |
|---|
The identifier of the Service MUST be the 'base URI' of the IIIF resource. |
...
| Tip |
|---|
Make sure that you have enabled CORS [Cross Origin Resource Sharing=security feature for browsers] to enable Europeana to display the images |
Step 3: Indicate a level of IIIF implementation
| Tip |
|---|
The provider MAY indicate a level of IIIF implementation. |
...
| Code Block | ||
|---|---|---|
| ||
<svcs:Service rdf:about="https://gallica.bnf.fr/iiif/ark:/12148/btv1b55001425m/f1"/>
<dcterms:conformsTo rdf:resource="http://iiif.io/api/image"/>
<doap:implements rdf:resource="http://iiif.io/api/image/2/level2.json">
</svcs:Service> |
Step 4: Provide access to a IIIF manifest
| Tip |
|---|
The provider MAY provide access to a IIIF Manifest |
...