Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

[Additional example EKT]

...

Note

What you need to do when you don’t provide images but have a manifest:

  • Open your manifest

  • Fill out the value you you take from resource @id in edm:isShownBy or edm:hasView and in the class edm:WebResource

  • Add your manifest-link to the dcterms:isReferencedBy in edm:WebResource

  • Add a class svcs:Service, fill this out using the value you take from your manifest in service @id and connect it to the edm:WebResource class using svcs:has_service

  • Indicate that the WebService conforms to (dcterms:conformsTo) the IIIF profile. The value of dcterms:conformsTo MUST be the URI http://iiif.io/api/image

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.

...