2009 ICSE Workshop on Principles of Engineering Service Oriented Systems 2009
DOI: 10.1109/pesos.2009.5068824
|View full text |Cite
|
Sign up to set email alerts
|

Adapting service requests to actual service interfaces through semantic annotations

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
21
0

Year Published

2009
2009
2012
2012

Publication Types

Select...
3
2

Relationship

4
1

Authors

Journals

citations
Cited by 5 publications
(21 citation statements)
references
References 7 publications
0
21
0
Order By: Relevance
“…The second relationship concerns the compatibility between names and data associated to some operation oexp ∈ Oexp in the expected WS and those associated to some operation o act ∈ Oact in the actual WS. For the sake of simplicity, here we assume that states and operation names and data are compatible if they are called the same way (more sophisticated compatibility relationships can be identified by assuming the existence of a semantic network of concepts as in [9]). Given these definitions, we say that, given a sequence of operations in the automaton of the expected WS, this can be substitutable by another sequence of operations in the automaton of the actual WS if the following conditions hold:…”
Section: Automatic Replacement Of Conversational Servicesmentioning
confidence: 99%
See 2 more Smart Citations
“…The second relationship concerns the compatibility between names and data associated to some operation oexp ∈ Oexp in the expected WS and those associated to some operation o act ∈ Oact in the actual WS. For the sake of simplicity, here we assume that states and operation names and data are compatible if they are called the same way (more sophisticated compatibility relationships can be identified by assuming the existence of a semantic network of concepts as in [9]). Given these definitions, we say that, given a sequence of operations in the automaton of the expected WS, this can be substitutable by another sequence of operations in the automaton of the actual WS if the following conditions hold:…”
Section: Automatic Replacement Of Conversational Servicesmentioning
confidence: 99%
“…In order to complete our translation we map each of GetLyric inputs on an univocal label and we do the same for each of getSong inputs, so, for instance, both id (input of getSong) and GetLyric_lyricId (input of GetLyric), which represent the id of a song, are mapped on the label lyricId. This translation step is carried on exploiting ontology-based reasoning, which we do not describe into details here, but can be found in our previous work [9]. The compatibility relations for input and return parameters of the example expected and actual services are reported respectively in Table 1 and Table 2.…”
Section: Using Behavior Protocols To Build Protocol Mapping Scriptmentioning
confidence: 99%
See 1 more Smart Citation
“…Previous studies have extensively investigated how to set up interface mappings for two services [2,3,7], which therefore, will not be our focus in this paper. Assuming the interface mappings have been defined, we will only concentrate on how an adaptation contract can be generated for a given abstract operation sequence.…”
Section: Representing Adaptive Service Substitution As a Graph Plmentioning
confidence: 99%
“…Adaptation is a promising technique to overcome such mismatches in a non-intrusive way [2][3][4][5][6]. With the help of an adaptor, the abstract service invocations are adapted to their concrete implementations, making the resulting substitution satisfy the expectation of the composition properly.…”
Section: Introductionmentioning
confidence: 99%