 |
Page History
...
| Children Display |
|---|
| Page info | ||||
|---|---|---|---|---|
|
...
Summary
Description of the profile
An important class of joint service action is the business transaction, or contract exchange. Many interactions between participants in the SOA ecosystem are based around business transactions. A business transaction is a joint action engaged in by two or more participants in which the ownership of one of more resources is exchanged.
...
Data updates that trigger transactions are captured by the platform and are propagated upstream to the semantic infrastructure. An example would be the platform monitoring events to identify changes to data.
Capability Elaborations
This Functional Profile includes, but is not limited to, the following capability elaborations:
Derived From Requirements
...
Artifact Descriptions may capture very focused information subsets or can be an aggregate of numerous component descriptions. Service description is an example of a likely aggregate for which manual maintenance of all aspects would not be feasible.
Architectural implications of composition on the Semantic Infrastructure are reflected in the following capabilities:
- tools to facilitate identifying description elements that are to be aggregated to assemble the composite description;
- tools to facilitate identifying the sources of information to associate with the description elements;
- tools to collect the identified description elements and their associated sources into a standard, referenceable format that can support general access and understanding;
- tools to automatically update the composite description as the component sources change, and to consistently apply versioning schemes to identify the new description contents and the type and significance of change that occurred.
Service composition mechanisms to support orchestration of service-oriented business processes and choreography of service-oriented business collaborations.
The capabilities of Service Composition include:
- Declarative and programmatic compositional languages
- Orchestration and/or choreography engines that support multi-step processes as part of a short-lived or long-lived business transaction;
- Orchestration and/or choreography engines that support compensating transactions in the presences of exception and fault conditions.
Capabilities
- assembly
- businessTransaction
- compensatingTransaction
- componentAcquisition
- compositionalLanguage
- compositionArchive
- compositionChange
- dataUpdateMonitor
Requirements traceability
Requirement | Source | Capability | ||||||
|---|---|---|---|---|---|---|---|---|
Data management includes linking of disparate data sets and updates of data across the ecosystem. Data updates may include updates to multiple data sources, necessitating the need for transactions. Linkages between the different disparate data sets will be managed by the semantic infrastructure. Data updates that trigger transactions are captured by the platform and are propagated upstream to the semantic infrastructure. An example would be the platform monitoring events to identify changes to data. Link to use case satisfied from caGRID 2.0 Roadmap: the patient has an electronic medical record that spans multiple institutions. The clinical workup data (for example, genomics and proteomics data) is linked to the clinical care record; similarly pathology and radiology findings must be attached to the patient's electronic medical record. | Semantic Infrastructure Requirements::caGRID 2.0 Platform and Terminology Integration::
| |||||||
| Semantic Profile::OASIS SOA::
| compositionalLanguage from inherited abstract profile Service Composition, businessTransaction from inherited abstract profile Service Composition, compensatingTransaction from inherited abstract profile Service Composition, | ||||||
| Semantic Profile::OASIS SOA::
| compositionArchive from inherited abstract profile Composition, assembly from inherited abstract profile Composition, compositionChange from inherited abstract profile Composition, componentAcquisition from inherited abstract profile Composition, |
| Anchor | ||||
|---|---|---|---|---|
|
Description
Tools to facilitate identifying description elements that are to be aggregated to assemble the composite description.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Orchestration and/or choreography engines that support multi-step processes as part of a short-lived or long-lived business transaction;
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Orchestration and/or choreography engines that support compensating transactions in the presences of exception and fault conditions.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Tools to facilitate identifying the sources of information to associate with the description elements.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Declarative and programmatic compositional languages
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Tools to collect the identified description elements and their associated sources into a standard, referenceable format that can support general access and understanding.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Tools to automatically update the composite description as the component sources change, and to consistently apply versioning schemes to identify the new description contents and the type and significance of change that occurred.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
Data updates may include updates to multiple data sources, necessitating the need for transactions.
Data updates that trigger transactions are captured by the platform and are propagated upstream to the semantic infrastructure. An example would be the platform monitoring events to identify changes to data.
Requirements addressed
Overview of possible operations
| Scrollbar |
|---|
