Dynamic Service Composition using Semantic Information

http://portal.acm.org/citation.cfm?id=1035174

Static Service Composition (proactive)

• workflow or state chart is designed to describe the interaction pattern
• BPEL, WSCI
  

Dynamic Service Composition (reactive)

• autonomous application composition
• eFlow[4], SWORD[13]
• dynamic service composition is useful for ubiquitous and end user applications

Scenaio

1. get address for restaurant and home
2. invoke the direction generator web service
3. print out the result image

four domains are introduced

1. data types
2. semantics (Concept)
3. logics
4. components

Comparing CoSMoS with SCA

• data types in CoSMoS are equivalent to DSO in SCA
• semantics are not supported in SCA
• logics is somewhat meaningless for CoSMoS
• components have equivalents in SCA
• composites are not defined in CoSMoS

CoSMoS is a new component model CoRE converts the metadata for the discovered components into CoSMoS and CORE has a pluggable architecture.

Semantic Graph Based Service Composition (SeGSec)

Request Analyzer <-> ServiceComposer <-> Reasoner <-> ServicePerformer

"ServiceComposer genrates the execution path by connecting operations of components", How?? This is not something trivial. Matching the operations for different interfaces for services is quite difficult. I am not sure how it is done. How do they perform this matching of operations at the high level? Reasoning and semantic resolution should be performed before the ServiceComposer module generates the path.

for other systems, there should be a template implementing the requested service. so a B2B template matching is required in this case.