Platform mechanisms providing support for awareness will likely have the following minimum capabilities:
- creation of Description, preferably conforming to a standard Description format and structure;
- publishing of Description directly to a consumer or through a third party mediator;
- discovery of Description, preferably conforming to a standard for Description discovery;
- notification of Description updates or notification of the addition of new and relevant Descriptions;
- classification of Description elements according to standardized classification schemes.
In a SOA ecosystem with complex social structures, awareness may be provided for specific communities of interest. The platform capabilities for providing awareness to communities of interest include:
- policies that allow dynamic formation of communities of interest;
- trust that awareness can be provided for and only for specific communities of interest, the bases of which is typically built on keying and encryption technology.
The platform architectural mechanisms for determining willingness to interact include capabilities for:
- verification of identity and credentials of the provider and/or consumer;
- access to and understanding of description;
- inspection of functionality and capabilities;
- inspection of policies and/or contracts.
The platform architectural mechanisms for establishing reachability will require capabilities for:
- the location or address of an endpoint;
- verification and use of a service interface by means of a communication protocol;
- determination of presence with an endpoint which may only be determined at the point of interaction but may be further aided by the use of a presence protocol for which the endpoints actively participate.
Functional Profile
- 5.2.5.1.1 - Service Classification Schemes Sept. 6, 2010 A classification scheme for organizing services based on business objectives, domain, and usage
- 5.2.5.1.2 - Service Metadata Sept. 6, 2010 A service description defines or references the information needed to use, deploy, manage and otherwise control a service. This includes not only the information and behavior models associated with a service to define the service interface but also includes information needed to decide whether the service is appropriate for the current needs of the service consumer. Thus, the service description will also include information such as service reachability, service functionality, and the policies and contracts associated with a service.
- 5.2.5.1.3 - Transaction Management Sept. 6, 2010 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.
