RESTful Service Architectures for Pervasive Networking Environments

Caporuscio, Mauro; Funaro, Marco; Ghezzi, Carlo

doi:10.1007/978-1-4419-8303-9_18

Cited by 7 publications

(8 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Pervasive REST Architectural Style (P-REST) expands and modifies REST according to the characteristic of the smart environment [ 57 ]. P-REST separates Uniform Resource Identifiers (URI) into two categories: Concrete URI (C-URI) and Abstract URI (A-URI).…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

ROSA: Resource-Oriented Service Management Schemes for Web of Things in a Smart Home

Liao

Chen²

2017

Sensors

View full text Add to dashboard Cite

A Pervasive-computing-enriched smart home environment, which contains many embedded and tiny intelligent devices and sensors coordinated by service management mechanisms, is capable of anticipating intentions of occupants and providing appropriate services accordingly. Although there are a wealth of research achievements in recent years, the degree of market acceptance is still low. The main reason is that most of the devices and services in such environments depend on particular platform or technology, making it hard to develop an application by composing the devices or services. Meanwhile, the concept of Web of Things (WoT) is becoming popular recently. Based on WoT, the developers can build applications based on popular web tools or technologies. Consequently, the objective of this paper is to propose a set of novel WoT-driven plug-and-play service management schemes for a smart home called Resource-Oriented Service Administration (ROSA). We have implemented an application prototype, and experiments are performed to show the effectiveness of the proposed approach. The results of this research can be a foundation for realizing the vision of “end user programmable smart environments”.

show abstract

Section: Related Workmentioning

confidence: 99%

“…In this paper, the formal approach is used in design time. The notation presented in this paper is based on [ 30 ] with minor extensions and modifications to enhance the readability and to fit in the context of our work such as the need for group communications, multiple responses to a request, and A-URI [ 57 ].…”

Section: Related Workmentioning

confidence: 99%

ROSA: Resource-Oriented Service Management Schemes for Web of Things in a Smart Home

Liao

Chen²

2017

Sensors

View full text Add to dashboard Cite

show abstract

“…Such middleware is designed and implemented following a service-oriented approach supporting, respectively, SOAP and RESTful Services. This flexible and dynamic vision is also proposed in (Caporuscio et al, 2011) in which thirdparty applications discovered at run time should be integrated in applications to offer more sophisticated functionalities.…”

Section: Related Workmentioning

confidence: 99%

Service-Oriented Architectures: From Design to Production Exploiting Workflow Patterns

Gabbrielli

Giallorenzo

Montesi

2014

Advances in Intelligent Systems and Computing

View full text Add to dashboard Cite

Application Programming Interfaces (APIs) are a standard feature of any application that exposes its functionalities to external invokers. APIs can be composed thus obtaining new programs with new functionalities. However API composition easily becomes a frustrating and time-costly task that hinders API reuse. The issue derives from technology-dependent features of API composition such as the need of extensive documentation, protocol integration, security issues, etc.. In this paper we introduce the perspective of the API-as-a-Service (APIaaS) layer as tool to ease the development and deployment of applications based on API composition, abstracting communication protocols and message formats. We elicit the desirable features of such a layer and provide a proof-of-concept prototype implemented using a service-oriented language.

show abstract

“…All the resources exploit both the lookup operation to discover the needed resources, and the DNS service to translate URIs into physical addresses. P-RESTful applications are built following the P-REST conceptual model [10], which defines: (1) a environment as a resource container providing infrastructural facilities (i.e., lookup and observe/notify); (2) a resource as a first-class object that, according to the REST uniformity [18], implements a fixed set of well-defined operations (i.e., PUT, DELETE, POST, GET, and INSPECT); (3) a semantics-aware description specifying both functional and non-functional properties of resources with respect to given ontologies.…”

Section: Related Workmentioning

confidence: 99%

“…This chapter presents the ubiREST middleware, which enhances the ubiSOAP approach [12] by providing RESTful access to services. Specifically, ubiREST adopts the P-REST architectural style [10], a refinement of the REST style [18] that we have introduced to fulfill the aforementioned requirements, namely flexibility, genericity, and dynamism.…”

Section: Introductionmentioning

confidence: 99%