RESTful Web Services Development Checklist

Vinoski, S.

doi:10.1109/mic.2008.130

Cited by 41 publications

(38 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…HTTP uses Multipurpose Internet Mail Extensions (MIME) media types to identify the data formats [2], Some of the common MIME are given in table 1 used by the restful services. Table 1.…”

Section: ) Jerseymentioning

confidence: 99%

See 1 more Smart Citation

Survey on Restful Web Services Using Open Authorization (Oauth)

Kanmani¹,

Smitha²

2013

IOSR-JCE

View full text Add to dashboard Cite

“…HTTP uses Multipurpose Internet Mail Extensions (MIME) media types to identify the data formats [2], Some of the common MIME are given in table 1 used by the restful services. Table 1.…”

Section: ) Jerseymentioning

confidence: 99%

“…The building blocks of the Web are called resources [3].Resources are manipulated through messages that have standard meanings on the Web called as HTTP methods. Resources are named with uniform resource identifier (URIs) [2].…”

Section: Introductionmentioning

confidence: 99%

Survey on Restful Web Services Using Open Authorization (Oauth)

Kanmani¹,

Smitha²

2013

IOSR-JCE

View full text Add to dashboard Cite

“…REST was not introduced as an approach to designing web services, yet it has been adopted by the non-corporate Web Service community as alternative to SOAP/WSDL. Although not always adhering to the all of REST's constraints [10] [11] [12], RESTful Web Services are gaining popularity and are adopted by major service providers like Google, Amazon and Yahoo.…”

Section: Introductionmentioning

confidence: 99%

EXPRESS: EXPressing REstful Semantic Services Using Domain Ontologies

Alowisheq

Millard

Tiropanis

2009

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. Existing approaches to Semantic Web Services (SWS) require a domain ontology and a semantic description of the service. In the case of lightweight SWS approaches, such as SAWSDL, service description is achieved by semantically annotating existing web service interfaces. Other approaches such as OWL-S and WSMO describe services in a separate ontology. So, existing approaches separate service description from domain description, therefore increasing design efforts. We propose EXPRESS a lightweight approach to SWS that requires the domain ontology definition only. Its simplicity stems from the similarities between REST and the Semantic Web such as resource realization, self describing representations, and uniform interfaces. The semantics of a service is elicited from a resource's semantic description in the domain ontology and the semantics of the uniform interface, hence eliminating the need for ontologically describing services. We provide an example that illustrates EXPRESS and then discuss how it compares to SA-REST and WSMO.

show abstract

“…To build our catalog, we surveyed several studies of REST APIs elaborated by Massé [6], Rodrigues et al [2], Palma et al [8,9], Vinoski [13], Stowe [12], and Richardson and Ruby [11]. In particular, Massé [6] provides a concise catalog of practices organised by categories.…”

mentioning

confidence: 99%

“…Error Handling practices specify how HTTP messages must be used as a response of a HTTP request method (Table 4). HTTP Header practices describe how must be used HTTP headers to complete requests with metadata or complementary data ( 2 GET must be used to retrieve a representation of a resource [6,11,12,13] 3 HEAD should be used to retrieve response headers [6,11,12,13] -4 PUT must be used to both insert and update a stored resource [6,11,12,13] --5 PUT must be used to update mutable resources [6,11,12,13] 6 POST must be used to create a new resource in a collection [6,11,12,13] 7 POST must be used to execute controllers [6,12] 8 DELETE must be used to remove a resource from its parent [6,11,12,13] …”

mentioning

confidence: 99%

Are REST APIs for Cloud Computing Well-Designed? An Exploratory Study

Petrillo

Merle

Moha

et al. 2016

Service-Oriented Computing

View full text Add to dashboard Cite

Abstract. Cloud computing is currently the most popular model to offer and access computational resources and services. Many cloud providers use the REST architectural style (Representational State Transfer) for offering such computational resources. However, these cloud providers face challenges when designing and exposing REST APIs that are easy to handle by end-users and/or developers. Yet, they benefit from best practices to help them design understandable and reusable REST APIs. However, these best practices are scattered in the literature and they have not be studied systematically on real-world APIs. Consequently, we propose two contributions. In our first contribution, we survey the literature and compile a catalog of 73 best practices in the design of REST APIs making APIs more understandable and reusable. In our second contribution, we perform a study of three different and well-known REST APIs from three cloud providers to investigate how their APIs are offered and accessed. These cloud providers are Google Cloud Platform, OpenStack, and Open Cloud Computing Interface (OCCI). In particular, we evaluate the coverage of the features provided by the REST APIs of these cloud providers and their conformance with the best practices for REST APIs design. Our results show that Google Cloud follows 66% (48/73), OpenStack follows 62% (45/73), and OCCI 1.2 follows 56% (41/73) of the best practices. Second, although these numbers are not necessarily high, partly because of the strict and precise specification of best practices, we showed that cloud APIs reach an acceptable level of maturity.

show abstract

RESTful Web Services Development Checklist

Cited by 41 publications

References 0 publications

Survey on Restful Web Services Using Open Authorization (Oauth)

Survey on Restful Web Services Using Open Authorization (Oauth)

EXPRESS: EXPressing REstful Semantic Services Using Domain Ontologies

Are REST APIs for Cloud Computing Well-Designed? An Exploratory Study

Contact Info

Product

Resources

About