Report Open Access

Final API available for internal and external service providers (Deliverable 2.4)

Bachler, Daniel; Dokler, Joh; Dudgeon, Tim; Willighagen, Egon; Karatzas, Pantelis; Lynch, Iseult; Hardy, Barry; Exner, Thomas


MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">Application programming interface</subfield>
  </datafield>
  <datafield tag="653" ind1=" " ind2=" ">
    <subfield code="a">e-infrastructure</subfield>
  </datafield>
  <controlfield tag="005">20200120142532.0</controlfield>
  <controlfield tag="001">2597061</controlfield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Edelweiss Connect</subfield>
    <subfield code="a">Dokler, Joh</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Informatics Matters Ltd</subfield>
    <subfield code="a">Dudgeon, Tim</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Universiteit Maastricht</subfield>
    <subfield code="a">Willighagen, Egon</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">National Technical University Of Athens</subfield>
    <subfield code="a">Karatzas, Pantelis</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">University Of Birmingham</subfield>
    <subfield code="a">Lynch, Iseult</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Edelweiss Connect</subfield>
    <subfield code="a">Hardy, Barry</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Edelweiss Connect</subfield>
    <subfield code="a">Exner, Thomas</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">494773</subfield>
    <subfield code="z">md5:9a2fbff6b25e70256a0a30dd6114c234</subfield>
    <subfield code="u">https://zenodo.org/record/2597061/files/D2.4 Final API available for internal and external service providers.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2019-03-18</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="o">oai:zenodo.org:2597061</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">Edelweiss Connect</subfield>
    <subfield code="a">Bachler, Daniel</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Final API available for internal and external service providers (Deliverable 2.4)</subfield>
  </datafield>
  <datafield tag="536" ind1=" " ind2=" ">
    <subfield code="c">731075</subfield>
    <subfield code="a">OpenRiskNet: Open e-Infrastructure to Support Data Sharing, Knowledge Integration and in silico Analysis and Modelling in Risk Assessment</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">https://creativecommons.org/licenses/by/4.0/legalcode</subfield>
    <subfield code="a">Creative Commons Attribution 4.0 International</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;This document reports the work on the final API specification for semantic interoperability that was developed as part of the OpenRiskNet e-infrastructure. It briefly outlines the challenges encountered and the solution that has been implemented and is now in use in OpenRiskNet.&lt;/p&gt;

&lt;p&gt;This deliverable is related to Task 2.2 (API specification and semantic interoperability) and in a continuation of the work performed within &lt;a href="https://doi.org/10.5281/zenodo.1479444"&gt;Deliverable 2.2&lt;/a&gt; (Initial API version provided to providers of services), that are now in the process of being incorporated into OpenRiskNet as part of the service catalogue. Deliverable 2.2 gives in-depth information on the evaluation of the various technologies for describing APIs we considered, whereas this report focuses on the solution that was finally chosen and put in place, and the justification of this choice to support other databases / e-infrastructures in their deliberations on API solutions.&lt;/p&gt;

&lt;p&gt;The main requirement of describing operations of an API, on both the semantic and technical (structural) levels, was met by creating a novel fusion of the well established OpenAPI standard and the tools of linked data using JSON-LD. This combination allowed us to use and reuse the already existing OpenAPI definitions (and already available OpenAPI tooling), and combine it, with relatively little effort for a service provider, with semantic annotations to facilitate interoperability. The OpenRiskNet Service Registry was developed to scan for such &amp;ldquo;OpenRiskNet annotated OpenAPI definitions&amp;rdquo; of active services running in an OpenShift cluster and indexes the data to provide semantic queries using the well established SPARQL linked data query language.&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isVersionOf</subfield>
    <subfield code="a">10.5281/zenodo.2597060</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.2597061</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">publication</subfield>
    <subfield code="b">report</subfield>
  </datafield>
</record>
53
28
views
downloads
All versions This version
Views 5353
Downloads 2828
Data volume 13.9 MB13.9 MB
Unique views 4141
Unique downloads 2222

Share

Cite as