Powered by OpenAIRE graph
Found an issue? Give us feedback
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/ ZENODOarrow_drop_down
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Report . 2019
License: CC BY
Data sources: Datacite
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Report . 2019
License: CC BY
Data sources: ZENODO
image/svg+xml art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos Open Access logo, converted into svg, designed by PLoS. This version with transparent background. http://commons.wikimedia.org/wiki/File:Open_Access_logo_PLoS_white.svg art designer at PLoS, modified by Wikipedia users Nina, Beao, JakobVoss, and AnonMoos http://www.plos.org/
ZENODO
Report . 2019
License: CC BY
Data sources: Datacite
versions View all 3 versions
addClaim

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

Authors: Bachler, Daniel; Dokler, Joh; Dudgeon, Tim; Willighagen, Egon; Karatzas, Pantelis; Lynch, Iseult; Hardy, Barry; +1 Authors

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

Abstract

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. This deliverable is related to Task 2.2 (API specification and semantic interoperability) and in a continuation of the work performed within Deliverable 2.2 (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. 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 “OpenRiskNet annotated OpenAPI definitions” 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.

Keywords

Application programming interface, e-infrastructure

  • BIP!
    Impact byBIP!
    selected citations
    These citations are derived from selected sources.
    This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    0
    popularity
    This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
    Average
    influence
    This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
    Average
    impulse
    This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
    Average
    OpenAIRE UsageCounts
    Usage byUsageCounts
    visibility views 9
    download downloads 5
  • 9
    views
    5
    downloads
    Powered byOpenAIRE UsageCounts
Powered by OpenAIRE graph
Found an issue? Give us feedback
visibility
download
selected citations
These citations are derived from selected sources.
This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Citations provided by BIP!
popularity
This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.
BIP!Popularity provided by BIP!
influence
This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).
BIP!Influence provided by BIP!
impulse
This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.
BIP!Impulse provided by BIP!
views
OpenAIRE UsageCountsViews provided by UsageCounts
downloads
OpenAIRE UsageCountsDownloads provided by UsageCounts
0
Average
Average
Average
9
5
Green
Related to Research communities