2009 3rd IEEE International Conference on Digital Ecosystems and Technologies 2009
DOI: 10.1109/dest.2009.5276716
|View full text |Cite
|
Sign up to set email alerts
|

What, not how: A generative approach to service composition

Abstract: We argue that the complexity of the WS-* service stack is a barrier to the exploitation of service composition in digital ecosystems (and indeed, quite generally). As an alternative, we focus on the emerging interest in REpresentational State Transfer (REST) as an architectural style, and the Semantics of Business Vocabulary and Business Rules (SBVR) for the expression of business requirements. We describe an architecture by which declarative service requests can be dynamically generated from a pool of RESTful… Show more

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

2009
2009
2015
2015

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 9 publications
(6 citation statements)
references
References 7 publications
0
6
0
Order By: Relevance
“…The current state-of-the-art requires manipulation of source code in which each line is context dependent, and so a single intended change may necessitates significant alterations at different locations in the codebase. A paradigm shift to declarative generative programming [104] would be greatly beneficial, avoiding the need to manually manage cascading changes to the codebase. As the requirements behind a service would be made explicit and executable, and being human readable could therefore be manipulated directly as stand-alone artifacts.…”
Section: Coordination Layermentioning
confidence: 99%
See 1 more Smart Citation
“…The current state-of-the-art requires manipulation of source code in which each line is context dependent, and so a single intended change may necessitates significant alterations at different locations in the codebase. A paradigm shift to declarative generative programming [104] would be greatly beneficial, avoiding the need to manually manage cascading changes to the codebase. As the requirements behind a service would be made explicit and executable, and being human readable could therefore be manipulated directly as stand-alone artifacts.…”
Section: Coordination Layermentioning
confidence: 99%
“…Still, without a more granular approach to conflict resolution from different patching sources, poor developer relations could risk fragmentation of the codebase and network. So, an alternative non-centralised software innovation model would be required, such as the declarative generative programming paradigm [104] mentioned.…”
Section: Distributed Innovationmentioning
confidence: 99%
“…The relational database is also automatically generated by the model. The work in [17] demonstrates Figure 6: SBVR rules transformed to SQL queries [23] how information systems can be generated directly from SBVR. Therefore, SBVR can be used to formulate complex data queries in a way that provides a higher level of abstraction than SQL (or any other query language) as shown in [23].…”
Section: Discussionmentioning
confidence: 99%
“…For example, as discussed in [31] where we propose a different approach to service composition that builds on declarative technologies, a request for organising a trip in a DE setting would result in a long-running transaction that includes subtransactions for booking a flight, a hotel and local transport. These would execute concurrently, but would also be provided by different organisations (in fact, different ones even for each run of the corresponding transaction).…”
Section: Related Workmentioning
confidence: 99%