OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebsoa message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Re: [ebsoa] SOA Collaboration Semantics

Thanks for your feedback. These are my answers:
- The run-time architecture is based on analysis of over 130 collaborative installations. It is based on FERA which classifies and categorizes capabilities required to support all of the use cases analyzed. The components are actually reference functional modules that have specified functions and interfaces. Our run time SOA is based on that model and each component has a well defined role and interface to communicate with other components to support the collaborative process.
- SOA IM is based on the process definition in FERA that requires certain level of specificity of the process detail. True, FERA does not require QoS details, but it provides a robust security policy model. The IM is derived from FERA process characteristics and there are additional data elements required for the run time semantics that are used for quality, escalation, monitoring and other administrative aspects of run time execution. The SOA IM contains sufficient level of detail to extract the semantics and to execute it over the run time SOA. True it is a process based model, and that is intentional, because that maintains the fidelity of business requirements throughout the entire deployment. In this framework, it is less important to define what is a service then to satisfy all basic principles of SOA. That is why it is an SOA IM. However, the Service entity is defined in Section 2.1.35 in SOA IM document. Hence, you see activities, decisions, events, roles, rules and metrics as key entities. A service can therefore be any activity, or a decision that has defined inputs and outputs, conditions for its invocation, metrics for its performance, rules for its execution, matrix with the input processing logic and few other entities in the model. Hence the entire model in fact defines services, their orchestration, their business rules and other aspects required for SOA definition, deployment, maintenance and continuous operational support. The entire IM and the architecture is an SOA based on the principles of service orientation. Just like in the sport of soccer nothing is really called soccer, but everything else defines the game, players, referees, goals, spectators, ball, pitch, etc.
----- Original Message -----
Sent: Tuesday, October 25, 2005 4:10 PM
Subject: RE: [ebsoa] SOA Collaboration Semantics

Thanks for sending these documents - it's clear that a great deal of work has gone into them.
I have a few questions, please:
Run-Time SOA: I get the notion of a reference architecture as shown in Figure 1 on p.3. Having said that, I would expect that any run-time (concrete) architecture that is depicted as being based on the reference architecture is merely for exemplary purposes, yet the run-time architecture is simply presented without any indication of its purpose. Since the run-time architecture is greatly concrete, is it intended that products be based on it? Is it intended for exemplary purposes? Other?
SOA Information Model: Though this is called a "SOA" information model, this document looks more to me like a "Process Information Model" that is actually independent of SOA (that is, I did not see anything that restricted it to SOA). In fact, in order to call something a "SOA" information model, I would assert that there are several other areas that would need to be incorporated beyond processes - e.g. security, policy, QoS, etc. Even considering the process perspective, there is nothing that I see in this information model that speaks distinctly to a service-oriented paradigm - in fact, figure 1 (p.24) does not even have a "Service" concept. What is the intended use of this document for ebSOA?
Joseph Chiusano
Booz Allen Hamilton
700 13th St. NW
Washington, DC 20005
O: 202-508-6514 
C: 202-251-0731
Visit us online@ http://www.boozallen.com

From: Goran Zugic [mailto:goran.zugic@semantion.com]
Sent: Friday, October 21, 2005 2:21 AM
Subject: [ebsoa] SOA Collaboration Semantics

Hello ebSOA TC,


Semantion is pleased to announce the completion of its FERA-based SOA contribution to ebSOA TC.


The SOA Collaboration Semantics document




contains FERA-based SOA semantics specification that together with two previously submitted documents, Run-time SOA and SOA Information Model, represent Semantion's SOA specification framework.


The new releases of the Run-time SOA document and the SOA Information Model  document are available at






These documents should be reviewed in the following order:


- Run-time SOA

- SOA Information Model

- SOA Collaboration Semantics


Please let me know if you have any questions or need more information regarding the submitted documents.


Goran Zugic
Chief Architect
Semantion Inc.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]