Survey of Semantic Description of REST APIs

Verborgh, Ruben; Harth, Andreas; Maleshkova, Maria; Stadtmüller, Steffen; Steiner, Thomas; Taheriyan, Mohsen; Walle, Rik Van de

doi:10.1007/978-1-4614-9299-3_5

Cited by 38 publications

(19 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Even other environments such as those focused on Semantic Web approaches result in even different description approaches, in this case often referred to as Semantic Web Service Descriptions [16]. Languages in this space include WSMO and OWL-S [8] as well as EXPRESS [1].…”

Section: Describing Restmentioning

confidence: 99%

Managing a RESTful SOA: Providing guidance for service designers and orientation for service consumers

Wilde¹

2014

It - Information Technology

View full text Add to dashboard Cite

Managing a Service Oriented Architecture (SOA) requires a well-defined model of what a service actually is, and a structure within which services can be published, documented, and consumed. Without such a definition and organizational structure, it is hard to reap the benefits of a SOA. This paper presents a case study that is closely aligned with how the Web is organized as a SOA, but adds some structure so that service producers and service consumers can be supported in their goals. Using this approach, it is possible to realize the architectural benefits of a RESTful architecture, but can still make sure that the published services follow a set of guidelines and constraints that the SOA is based on.

show abstract

Section: Describing Restmentioning

confidence: 99%

Managing a RESTful SOA: Providing guidance for service designers and orientation for service consumers

Wilde¹

2014

It - Information Technology

View full text Add to dashboard Cite

show abstract

“…That is say, the transfer of application state is driven by representation, which sent back as response to request. The concept of sending a representation of a resource along with the controls (such as links) that lead to next steps, is called hypermedia-driven [14]. Thanks to hypermedia, servers do not need to remember state.…”

Section: Data Viewmentioning

confidence: 99%

“…It acts as both, client and server in order to forward, with possible translation, requests and responses. Connectors: Connector is an abstract mechanism that mediates communication, coordination, or cooperation among components [14]. Connectors represent the interfaces involved in accessing resources and transferring representations.…”

Section: A Overview Of the Elements Of Rest Architecturementioning

confidence: 99%

Formalization and Verification of REST Architecture in Viewpoints

Tang

Zhu

et al. 2015

2015 IEEE 16th International Symposium on High Assurance Systems Engineering

View full text Add to dashboard Cite

Representational State Transfer (REST), as a promising software architecture style, has been used in large scale since proposed. However, there still exist considerable confusions about the REST architecture, which may lead to inappropriate application. We apply formal method CSP in modeling the REST architectural style to give a comprehensive explanation of it. We partition the architectural description into three separate views: process view, connector view and data view, each capturing one architectural element and related properties of the architecture. Furthermore, REST constraints can be described in our models and validated by the model checker PAT. Besides, we focus on the relation between the stateless constraint and resource state, as well as the uniform interface constraint and hypermedia-driven property. The related properties of them are also verified in this paper.

show abstract

“…In recent years, several description formats for the more lightweight Web APIs have emerged (Verborgh et al 2014). Linked Open Services (LOS, Norton and Krummenacher 2010) expose functionality on the Web using Linked Data technologies, such as HTTP and RDF.…”

Section: Web Api Descriptionmentioning

confidence: 99%

The pragmatic proof: Hypermedia API composition and execution

Verborgh¹,

Arndt²,

Hoecke³

et al. 2016

Theory and Practice of Logic Programming

Self Cite

View full text Add to dashboard Cite

Machine clients are increasingly making use of the Web to perform tasks. While Web services traditionally mimic remote procedure calling interfaces, a new generation of socalled hypermedia APIs works through hyperlinks and forms, in a way similar to how people browse the Web. This means that existing composition techniques, which determine a procedural plan upfront, are not sufficient to consume hypermedia APIs, which need to be navigated at runtime. Clients instead need a more dynamic plan that allows them to follow hyperlinks and use forms with a preset goal. Therefore, in this article, we show how compositions of hypermedia APIs can be created by generic Semantic Web reasoners. This is achieved through the generation of a proof based on semantic descriptions of the APIs' functionality. To pragmatically verify the applicability of compositions, we introduce the notion of pre-execution and post-execution proofs. The runtime interaction between a client and a server is guided by proofs but driven by hypermedia, allowing the client to react to the application's actual state indicated by the server's response. We describe how to generate compositions from descriptions, discuss a computer-assisted process to generate descriptions, and verify reasoner performance on various composition tasks using a benchmark suite. The experimental results lead to the conclusion that proof-based consumption of hypermedia APIs is a feasible strategy at Web scale.Under consideration in Theory and Practice of Logic Programming (TPLP).

show abstract

Survey of Semantic Description of REST APIs

Cited by 38 publications

References 0 publications

Managing a RESTful SOA: Providing guidance for service designers and orientation for service consumers

Managing a RESTful SOA: Providing guidance for service designers and orientation for service consumers

Formalization and Verification of REST Architecture in Viewpoints

The pragmatic proof: Hypermedia API composition and execution

Contact Info

Product

Resources

About