...
...
Note |
---|
What you need to do when you don’t provide images but have a manifest:
|
Note |
---|
What we do when you dont provide images but have a manifest We are able to process your data as any other IIIF record, after you have taken the steps above. |
Example of an EDM record implementing all steps of the pattern (including the optional steps)
Code Block |
---|
<ore:Aggregation rdf:about="[...]">
[...]
<edm:isShownBy rdf:resource="http://dams.llgc.org.uk/iiif/image/2.0/1294670/full/512,/0/default.jpg">
[...]
</ore:Aggregation>
<edm:WebResource rdf:about="http://dams.llgc.org.uk/iiif/image/2.0/1294670/full/512,/0/default.jpg">
<svcs:has_service rdf:resource="http://dams.llgc.org.uk/iiif/image/2.0/1294670"/>
<dcterms:isReferencedBy rdf:resource="http://dams.llgc.org.uk/iiif/2.0/1294670/manifest.json"/>
</edm:WebResource>
<svcs:Service rdf:about="http://dams.llgc.org.uk/iiif/image/2.0/1294670">
<dcterms:conformsTo rdf:resource="http://iiif.io/api/image"/>
<doap:implements rdf:resource="http://iiif.io/api/image/2/level1.json">
</svcs:Service> |
Note that the set of parameters available as part of the URI <edm:isShownBy rdf:resource="http://iiif.europeana.eu/AZ_1927_01_04_0001/full/full/0/default.jpg">
will vary depending on the image the data provider wants to make available.
...