![]() |
Page History
...
Children Display |
---|
Page info | ||||
---|---|---|---|---|
|
Runtime Contract Discovery Functional Profile
A powerful query mechanism that allows either the service orchestrator or a program to find the services that best fit the requirements of a given process. This increases both runtime and design time flexibility by enabling selection of services based on computable metadata.
From inherited abstract Artifact Functional Profile
An artifact is a managed resource within Contract Discovery has architectural implications on the Semantic Infrastructure: .
An artifact is associated with Service descriptions include reference to contracts representing agreement on policies and other conditions. This requires the following capabilities:
- descriptions to enable the contracts artifact to be visible, where the description includes a unique identifier for the contract artifact and a sufficient, and preferably a machine processible, representation of the meaning of terms used to describe the contractartifact, its functions, and its effects;
- one or more discovery mechanisms that enable searching for contracts artifacts that best meet the search criteria specified by the service participant; where the discovery mechanism will have access to the individual contract artifact descriptions, possibly through some repository mechanism;
- accessible storage of contractartifacts and artifact descriptions, so service participants can access, examine, and use the contracts artifacts as defined.
Contracts include references to metrics which describe the operational characteristics of the subjects being described. This requires the following capabilities:
- the infrastructure monitoring and reporting information on SOA resources;
- possible interface requirements to make accessible metrics information generated or most easily accessed by the service itself;
- mechanisms to catalog and enable discovery of which metrics are available for a described resources and information on how these metrics can be accessed;
- mechanisms to catalog and enable discovery of compliance records associated with contracts that are based on these metrics.
Descriptions of the interactions are important for enabling auditability and repeatability, thereby establishing a context for results and support for understanding observed change in performance or results. This requires the following capabilities:
- one or more mechanisms to capture, describe, store, discover, and retrieve interaction logs, execution contexts, and the combined interaction descriptions;
- one or more mechanisms for attaching to any results the means to identify and retrieve the interaction description under which the results were generated.
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. This requires the existence of:
...
From inherited abstract Discovery Functional Profile
Discovery is the set of capabilities which enable searching for artifacts that best meet the search criteria specified by the service participant.
Aspects of discovery include:
- Search for services, policies, and other artifact descriptions accessible via some repository mechanism
- Search for operational characteristics of artifacts, which are metrics defined in artifact descriptions. The information is accessible via infrastructure monitoring capabilties or directly from services.
- Tracking and notification mechanisms related to artifact usage, service availability, operational conformance
Capabilities associated with discovery are delineated in the functional profiles inherited, and specialized, by the discovery profile, namely:
- Artifact
- Metrics
- Interoperability
From inherited abstract Interoperability Functional Profile
...
Descriptions provide up-to-date information on what a resource is, the conditions for interacting with the resource, and the results of such interactions. As such, the description is the source of vital information in establishing willingness to interact with a resource, reachability to make interaction possible, and compliance with relevant conditions of use. This requires the existence of
Architectural implications of interoperability on the Semantic Infrastructure are reflected in the following capabilities:
- one or more discovery mechanisms that enable searching for described resources that best meet the criteria specified by a service participant, where the discovery mechanism will have access to individual descriptions, possibly through some repository mechanism;
- tools to appropriately track users of the descriptions and notify them when a new version of the description is available.
From inherited abstract Metrics Functional Profile
Artifact Descriptions include references to metrics which describe the operational characteristics of the subjects being described
Architectural implications of metrics on the Semantic Infrastructure are reflected in the following capabilities:
- access to platform infrastructure monitoring and reporting capabilities
- access to metrics information generated or accessible by related services
- mechanisms to catalog and enable discovery of which metrics are available for a described artifact and information on how these metrics can be accessed;
- mechanisms to catalog and enable discovery of compliance records associated with policies, contracts, and constraints that are based on these metrics.
Capability Elaborations
This Functional Profile includes, but is not limited to, the following capability elaborations:
- complianceDiscovery
- discovery
- identity
- interoperabilityDiscovery
- metadata
- metrics
- metricsDiscovery
- monitor
- queryBestCdeVersion
- semanticAlignment
- serviceChangeNotification
- store
Derived From Requirements
- Gap Analysis::Discover::013 - Identify semantically similar data elements Identify semantically similar data elements
- Gap Analysis::Discover::048 - Improve searching for best CDE version Improve searching for “best” CDE version
- Gap Analysis::HL7 CIC::CIC-10 - Compare data elements for semantic similarities There is a need for users to upload/download sets and concurrently compare to existing registry elements for semantic similarities
Anchor | ||||
---|---|---|---|---|
|
Mechanisms to catalog and enable discovery of compliance records associated with policies, contracts, and constraints that are based on these metrics.
Anchor | ||||
---|---|---|---|---|
|
One or more discovery mechanisms that enable searching for artifacts that best meet the search criteria specified by the service participant; where the discovery mechanism will have access to the individual artifact descriptions, possibly through some repository mechanism.
Anchor | ||||
---|---|---|---|---|
|
Descriptions which include a unique identifier for the artifact.
Anchor | ||||
---|---|---|---|---|
|
One or more discovery mechanisms that enable searching for described resources that best meet the criteria specified by a service participant, where the discovery mechanism will have access to individual descriptions, possibly through some repository mechanism.
Anchor | ||||
---|---|---|---|---|
|
A representation of the meaning of terms used to describe the artifact, its functions, and its effects.
Anchor | ||||
---|---|---|---|---|
|
Access to metrics information generated or accessible by related services
Anchor | ||||
---|---|---|---|---|
|
Mechanisms to catalog and enable discovery of which metrics are available for a described artifact and information on how these metrics can be accessed.
Anchor | ||||
---|---|---|---|---|
|
Access to platform infrastructure monitoring and reporting capabilities.
Anchor | ||||
---|---|---|---|---|
|
Improve searching for “best” CDE version
Anchor | ||||
---|---|---|---|---|
|
Identify semantically similar data elements
Anchor | ||||
---|---|---|---|---|
|
Tools to appropriately track users of the descriptions and notify them when a new version of the description is available.
Anchor | ||||
---|---|---|---|---|
|
Accessible storage of artifacts and artifact descriptions, so service participants can access, examine, and use the artifacts as defined.
Scrollbar |
---|