| |
State of the Art SOA |
ASG Platform |
| Reusability |
 The reuse of services is mainly based on technical descriptions
of services. |
 Services functionalities can be reused based on the semantic information
in ASG service specifications. |
| Standards |
 Based on standards like SOAP, WSDL, UDDI or BPEL. |
 Based on standards like SOAP, WSDL, UDDI or BPEL. As semantic-based
enhancements are currently not standardised, ASG will contribute to
standards in the Semantic Web Services area. |
| Adaptability |
 Selection of services are hard coded and therefore not adaptive.
The service landscape is mainly comprised of a fixed service set. |
Selection of services can be done dynamically at runtime and is therefore
adaptive. |
| Transparent process planning |
 All available alternative service compositions need to be hard coded.
A service composition is therefore static and need to be created manually. |
 Adaptive service composition according to constraints in the environment
and the semantic service specifications. |
| Quality of service awareness |
 Little or no Quality of Service awareness. |
Quality of Service parameters are attached to user requests and incorporated
into service specifications. |
| Openness |
Clients do not automatically use new published services. These need
to be integrated in running processes manually and at design time. |
New published services are automatically used within service compositions.
Publishing of a new service requires manual definition of semantics
that are supported by ASG tools and service models. |
| Semantic awareness |
Clients need to know atomic service functionalities due to the lack
of semantics in their service specifications. |
Tasks like discovery and composition of services based on functional
service capabilities can be carried out automatically due to included
semantics in service specifications. |
| Reliability |
Reliability depends heavily on the availability of service implementations.
Finding of semantically equivalent services needs to be done manually. |
Reliability depends on the availability of service functionalities,
regardless of the technical interfaces. Mediated renegotiation and
re-planning mechanisms will find the desired service functionality
based on the semantic service specification. |
