This page contains documentation for using web services provided by Nomisma and how to access machine readable serializations through REST and content negotiation.
| API | XML | JSON | Turtle |
|---|---|---|---|
| avgAxis | XML | JSON | |
| avgDiameter | XML | JSON | |
| avgWeight | XML | JSON | |
| closingDate | XML | JSON | |
| getLabel | XML | JSON | |
| getFindspots | geoJSON | ||
| getHoards | geoJSON | ||
| getMints | geoJSON | ||
| query.json | geoJSON | ||
| query.kml | KML | ||
| getRdf | RDF/XML | JSON-LD | RDF/TTL |
Get average axis for given SPARQL query.
Webservice Type : REST
Url : nomisma.org/avgAxis?
Parameters : constraints (following predicate - object format. multiple contraints separated by ' AND '. See examples below), format
('json' or 'xml', default 'xml')
Result : returns a decimal number in a response wrapper.
Examples: http://nomisma.org/apis/avgAxis?constraints=dcterms:source nm:ric AND nmo:hasMint nm:rome AND nmo:hasDenomination nm:denarius
http://nomisma.org/apis/avgWeight?constraints=nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A>
Get average diameter for given SPARQL query.
Webservice Type : REST
Url : nomisma.org/avgDiameter?
Parameters : constraints (following predicate - object format. multiple contraints separated by ' AND '. See examples below), format
('json' or 'xml', default 'xml')
Result : returns a decimal number in a response wrapper.
Examples: http://nomisma.org/apis/avgDiameter?constraints=dcterms:source nm:ric AND nmo:hasMint nm:rome AND nmo:hasDenomination nm:denarius
http://nomisma.org/apis/avgDiameter?constraints=nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A>
Get average weight for given SPARQL query.
Webservice Type : REST
Url : nomisma.org/avgWeight?
Parameters : constraints (following predicate - object format. multiple contraints separated by ' AND '. See examples below), format
('json' or 'xml', default 'xml')
Result : returns a decimal number in a response wrapper.
Examples: http://nomisma.org/apis/avgWeight?constraints=dcterms:source nm:ric AND nmo:hasMint nm:rome AND nmo:hasDenomination nm:denarius
http://nomisma.org/apis/avgWeight?constraints=nmo:hasTypeSeriesItem <http://numismatics.org/ocre/id/ric.1(2).aug.1A>
Get the closing date of a hoard based on coin type URIs provided in the request parameter.
Webservice Type : REST
Url : nomisma.org/closingDate?
Parameters : identifiers (coin type URIs divided by a pipe '|'), format ('json' or 'xml', default 'xml')
Result : returns an integer which represents the year. Negative numbers refer to B.C. dates.
Examples: http://nomisma.org/apis/closingDate?identifiers=http://numismatics.org/crro/id/rrc-385.4|http://numismatics.org/crro/id/rrc-409.2|http://numismatics.org/ocre/id/ric.1(2).aug.1A
Get all individual find spots for a given skos:Concept defined by the id parameter or for a given coin type (nmo:TypeSeriesItem) defined by
the coinType parameter
Webservice Type : REST
Url : nomisma.org/getFindspots?
Parameters : id (of Nomisma ID) OR coinType (full URI for a coin type) OR symbol (full URI for a symbol [monogram, mint mark, etc.])
Result : returns geoJSON for features (points or polygons)
Examples: apis/getFindspots?id=denarius, apis/getFindspots?coinType=http://numismatics.org/crro/id/rrc-408.1a, apis/getFindspots?symbol=http://numismatics.org/ocre/symbol/monogram.ric.10.marcian.1
Get all hoards associated with a given skos:Concept defined by the id parameter or for a given coin type (nmo:TypeSeriesItem) defined by the
coinType parameter. If the skos:Concept is a hoard, then only one point is returned.
Webservice Type : REST
Url : nomisma.org/getHoards?
Parameters : id (of Nomisma ID) OR coinType (full URI for a coin type) OR symbol (full URI for a symbol [monogram, mint mark, etc.])
Result : returns geoJSON for features (points or polygons)
Examples: apis/getHoards?id=denarius, apis/getHoards?coinType=http://numismatics.org/crro/id/rrc-408.1a, apis/getHoards?symbol=http://numismatics.org/ocre/symbol/monogram.ric.10.marcian.1
Get all minting locations (may be nmo:Mint or nmo:Region) associated with a given skos:Concept defined by the id parameter. If the
skos:Concept is a mint or region, then only one point or polygon is returned.
Webservice Type : REST
Url : nomisma.org/getMints?
Parameters : id (of Nomisma ID) OR symbol (full URI for a symbol [monogram, mint mark, etc.])
Result : returns geoJSON for features (points or polygons)
Examples: apis/getMints?id=denarius, apis/getMints?symbol=http://numismatics.org/ocre/symbol/monogram.ric.10.marcian.1
Get the label of a Nomisma ID given its URI and language code.
Webservice Type : REST
Url : nomisma.org/getLabel?
Parameters : uri (of Nomisma ID), lang (two-letter ISO language code), format ('json' or 'xml', default 'xml')
Result : returns the label in given language, or English as default.
Examples: apis/getLabel?uri=http://nomisma.org/id/ar&lang=fr
Get a GeoJSON response for a SPARQL query that contains coordinates (SELECT, CONSTRUCT, DESCRIBE)
Webservice Type : REST
Url : nomisma.org/query.json?
Parameters : query (URL encoded SPARQL query)
Result : GeoJSON
Examples: (click for full URL)
Get a KML response for a SPARQL query that contains coordinates (SELECT, CONSTRUCT, DESCRIBE)
Webservice Type : REST
Url : nomisma.org/query.kml?
Parameters : query (URL encoded SPARQL query)
Result : GeoJSON
Examples: (click for full URL)
Aggregate RDF for Nomisma ids. The default stream is in RDF/XML, but Turtle and JSON-LD are available.
Webservice Type : REST
Url : nomisma.org/getRdf?
Parameters : identifiers (Nomisma ids divided by a pipe '|'), format ('xml', 'ttl', 'json'; default 'xml')
Result : RDF/XML, RDF/TTL. Other RDF formats will be supported eventually.
Examples: apis/getRdf?identifiers=rome|augustus|av|aureus
Service URI: http://nomisma.org/apis/reconcile
Nomisma supports the following reconciliation services for OpenRefine:
All API responses are in JSON. Please see the API documentation and usage documentation for more details. The blog post, Nomisma launches OpenRefine reconciliation service, contains further information about this particular implementation in Nomisma.
Numishare supports delivery of individual records in a variety of models and serializations through both REST and content negotiation. Content negotiation (with the accept header) requests should be sent to the URI space http://nomisma/id/. Requesting an unsupported content type will result in an HTTP 406: Not Acceptable error.
| Model | REST | Content Type |
|---|---|---|
| HTML | http://nomisma.org/id/{$id} |
text/html
|
| KML | http://nomisma.org/id/{$id}.kml |
application/vnd.google-earth.kml+xml
|
| RDF/XML | http://nomisma.org/id/{$id}.rdf |
application/rdf+xml
|
| Turtle | http://nomisma.org/id/{$id}.ttl |
text/turtle
|
| JSON-LD | http://nomisma.org/id/{$id}.jsonld |
application/ld+json
|
Search results (the browse page) are returned in HTML5, but Numishare supports Atom and RSS via REST, as well as Atom and raw Solr XML via content negotiation of the browse page URL, http://nomisma.org/browse. The REST-based Atom feed sorts by the Lucene syntax 'timestamp desc' by default, but the sort parameter may be provided manually to alter the default field and order.
| Model | REST | Content Type |
|---|---|---|
| HTML | http://nomisma.org/browse |
text/html
|
| Atom | http://nomisma.org/feed/ |
application/atom+xml
|
| Solr/XML | N/A |
application/xml
|
Data dumps conforming to the Pelagios 3 model are linked on the index page. At present, these files are only available in RDF/XML.
Unless specified otherwise, content in Nomisma.org is licensed under a Creative Commons Attribution 3.0 License.