2013
DOI: 10.1109/tnsm.2013.022213.120229
|View full text |Cite
|
Sign up to set email alerts
|

A Dynamic Composition and Stubless Invocation Approach for Information-Providing Services

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
6
0

Year Published

2013
2013
2019
2019

Publication Types

Select...
6
1
1

Relationship

0
8

Authors

Journals

citations
Cited by 9 publications
(6 citation statements)
references
References 35 publications
0
6
0
Order By: Relevance
“…Finally, future work will include an improvement of the IDN performance and an of the EPCWeb application with improved search and discovery capabilities through the adoption of semantic annotations [38] [39] [40].…”
Section: Discussionmentioning
confidence: 99%
“…Finally, future work will include an improvement of the IDN performance and an of the EPCWeb application with improved search and discovery capabilities through the adoption of semantic annotations [38] [39] [40].…”
Section: Discussionmentioning
confidence: 99%
“…Unlike static composition, in dynamic composition, service components are selected at runtime; and a composition plan based on functional and non-functional requirements is generated and executed also at runtime. Dynamic composition strategies are categorised in several ways (D'Mello et al, 2011): based on constraints and business rules (Orriëns et al, 2003), based on planning techniques from artificial intelligence (Zhang et al, 2010), based on interaction and user customisation (Agarwal and Jalote, 2010), based on contextual information (Medjahed and Atif, 2007) and based on service's signature (input and output parameters) (Paganelli and Parlanti, 2013). From a different perspective (Alamri et al, 2006), dynamic composition strategies can be grouped into those that use wrappers or adapters to create a new service interface at runtime; others use a language describing the composition; others are based on workflows and an abstract process model where each activity can be linked to a service.…”
Section: Dynamic Compositionsmentioning
confidence: 99%
“… name the resource using a URI;  identify the subset of allowed operations on that resource;  design the representation(s) of the resource as accepted by the client (in a request) and sent to the client in a response;  connect the resource with other resources through hyperlinks;  analyze the typical course of events by considering how the service is supposed to behave and possible error conditions. In some cases, an operation on a resource (i.e., a RESTful service) can be executed by invoking a set of operations on the resource or on different resources [35]. These types of operations are typically referred to as "composite RESTful services".…”
Section: A Rest Guidelinesmentioning
confidence: 99%