Re-using EDM in Nomisma.org

For several years now Europeana has made a lot of efforts to make the Europeana Data Model an interoperable framework for describing digital cultural heritage data. We strived in making EDM as re-usable as possible for the community. It is therefore always great to see such news!

On extending the https://t.co/F2TXI1DYnm data model with the @Europeanaeu #IIIF specs with coins from Rutgers https://t.co/l6Cr9JHi6n #lawdi

— Ethan Gruber (@ewg118) January 5, 2017

EDM has been designed as a flexible model that is meant to be re-used by the Cultural Heritage community to cover their domain specific requirements. And it is exactly what the Nomisma.org project did by re-using only one part of the model.

When Europeana decided to incorporate the International Image Interoperability Framework (IIIF) service to its service infrastructure, we needed a solution to describe IIIF resources within EDM. As for every extension of the model, we tried to root as much as possible EDM into existing standards and expert communities. It was therefore natural for us to adopt the solutions defined by the IIIF community to enable links to IIIF resources in the metadata. The EDM profile for IIIF explains to data providers how to make their IIIF resources available as part of the metadata they send to Europeana.

Nomisma.org is a collaborative project that provides stable digital representations of numismatic concepts according to the principles of Linked Open Data. The project has updated their RDF data model with the features of the EDM profile for IIIF in order to serve the IIIF resources of their new data contributor (the Rutgers University's Badian Collection) into the Coinage of the Roman Republic Online portal.

In modeling terms, the Nomisma reference image currently represented as a foaf:depiction gives rise to an edm:WebResource. The new edm:WebResource is linked to a JSON-LD IIIF manifest or information object (via dcterms:isReferencedBy) and to the URI for the service (with the svcs:has_service property). The service (svcs:Service) should include several statements that defines it as a IIIF image service.

<edm:WebResource rdf:about="

<svcs:has_service rdf:resource=""/>

<a href="" class="redactor-autoparser-object" >https:="" rucore.libraries.rutge...<="" a="">

<a href="" class="redactor-autoparser-object" >https:="" rucore.libraries.rutge...<="" a=""><dcterms:isReferencedBy rdf:resource="<a href="" class="redactor-autoparser-object" >https:="" rucore.libraries.rutge...<="" a="">"/>

<a href="" class="redactor-autoparser-object" >https:="" rucore.libraries.rutge...<="" a="">

<a href="" class="redactor-autoparser-object" >https:="" rucore.libraries.rutge...<="" a=""><svcs:Service rdf:about="<a href="" class="redactor-autoparser-object" >https:="" rucore.libraries.rutge...<="" a="">">

<a href="" class="redactor-autoparser-object" >https:="" rucore.libraries.rutge...<="" a="">

<a href="" class="redactor-autoparser-object" >https:="" rucore.libraries.rutge...<="" a=""><dcterms:conformsTo rdf:resource="<a href="" class="redactor-autoparser-object" >http:="" iiif.io="" api="" image<="" a="">"/>

<a href="" class="redactor-autoparser-object" >http:="" iiif.io="" api="" image<="" a="">

<a href="" class="redactor-autoparser-object" >http:="" iiif.io="" api="" image<="" a=""><doap:implements rdf:resource="<a href="" class="redactor-autoparser-object" >http:="" iiif.io="" api="" image="" 2="" lev...<="" a="">"/>

<a href="http://iiif.io/api/image/2/lev..." class="redactor-autoparser-object" >http:="" iiif.io="" api="" image="" 2="" lev...<="" a="">

<a href="http://iiif.io/api/image/2/lev..." class="redactor-autoparser-object" >http:="" iiif.io="" api="" image="" 2="" lev...<="" a=""></svcs:Service><a href="http://iiif.io/api/image/2/lev..." class="redactor-autoparser-object" >http:="" iiif.io="" api="" image="" 2="" lev...<="" a="">

<a href="http://iiif.io/api/image/2/lev..." class="redactor-autoparser-object" >http:="" iiif.io="" api="" image="" 2="" lev...<="" a="">The user interface in Numishare (and Coinage of the Roman Republic Online) are now displaying coin images using the Leaflet IIIF-viewer and allows the query of the IIIF manifest metadata via the dcterms:isReferencedBy. An example of a Rutgers coin is available at http://numismatics.org/crro/id/rrc-474.2b (see "Denarius - Sydenham 999 - Crawford 474/2b.

The Nomisma case is a great example of the vision underpinning EDM in which data models can be designed is a decentralised way for specific domain applications while the created data remains interoperable.

This post is based on Ethan Gruber’s blog post: http://numishare.blogspot.nl/2017/01/rutgers-universitys-badian-collection.html