URI Resolution
Go to “LIDO Terminology – LOD Interface”
Upon invocation over the network, each URI from the LIDO Terminology is answered with an associated data (or metadata) record. Application programs intended to consume data from the LIDO Terminology can choose between two calling conventions and four serialization formats. This applies to concepts as well as metadata in the case where the URI identifies an entire concept scheme.
Selecting the response format
When requesting a single concept or metadata about a concept scheme, the response format can be determined in one of the following ways:
a. by setting the HTTP Accept request reader, as described in section Content Negotiation/Serialization under HTTP header.
b. by appending a filetype suffix to the URI, as described in section Content Negotiation/Serialization under Filename extension.
HTTP Accept
Concept by canonical URI:
curl -H ‘accept: application/rdf+xml’ http://terminology.lido-schema.org/lido00023
curl -H ‘accept: application/ld+json’ http://terminology.lido-schema.org/lido00023
curl -H ‘accept: application/n-triples’ http://terminology.lido-schema.org/lido00023
curl -H ‘accept: text/turtle’ http://terminology.lido-schema.org/lido00023
Concept by symbolic URI:
curl -H ‘accept: application/rdf+xml’ http://terminology.lido-schema.org/eventType/type_assignment
curl -H ‘accept: application/ld+json’ http://terminology.lido-schema.org/eventType/type_assignment
curl -H ‘accept: application/n-triples’ http://terminology.lido-schema.org/eventType/type_assignment
curl -H ‘accept: text/turtle’ http://terminology.lido-schema.org/eventType/type_assignment
Metadata about a concept scheme:
curl -H ‘accept: application/rdf+xml’ http://terminology.lido-schema.org/eventType
curl -H ‘accept: application/ld+json’ http://terminology.lido-schema.org/eventType
curl -H ‘accept: application/n-triples’ http://terminology.lido-schema.org/eventType
curl -H ‘accept: text/turtle’ http://terminology.lido-schema.org/eventType
Filetype suffix
This method is not only suitable for API calls, but in some cases also for invocation from a web browser.
Concept by canonical URI:
[curl] http://terminology.lido-schema.org/lido00023.rdf returns MIME-Type application/rdf+xml
[curl] http://terminology.lido-schema.org/lido00023.json returns MIME-Type application/json
[curl] http://terminology.lido-schema.org/lido00023.nt returns MIME-Type text/plain
[curl] http://terminology.lido-schema.org/lido00023.ttl returns MIME-Type text/plain
Concept by symbolic URI (for corresponding MIME types, see above):
[curl] http://terminology.lido-schema.org/eventType/type_assignment.rdf
[curl] http://terminology.lido-schema.org/eventType/type_assignment.json
[curl] http://terminology.lido-schema.org/eventType/type_assignment.nt
[curl] http://terminology.lido-schema.org/eventType/type_assignment.ttl
Metadata about a concept scheme (for corresponding MIME types, see above):
[curl] http://terminology.lido-schema.org/eventType.rdf
[curl] http://terminology.lido-schema.org/eventType.json
[curl] http://terminology.lido-schema.org/eventType.nt
[curl] http://terminology.lido-schema.org/eventType.ttl
SPARQL queries
Response formats for SPARQL queries cannot be selected with any of the above methods, but only by setting a format parameter as part of the HTTP GET or POST request. Please note that the response syntax for xml and json differs between query types.
|
<code>format=</code> |
SELECT |
CONSTRUCT, DESCRIBE |
|---|---|---|
|
<code>xml</code> |
||
|
<code>json</code> |
||
|
<code>csv</code> |
– |
|
|
<code>nt</code> |
– |
|
|
<code>trig</code> |
– |
|
|
<code>ttl</code> |
– |
