 |
Page History
| Wiki Markup |
|---|
{scrollbar:icons=false} |
| Page info | ||||
|---|---|---|---|---|
|
| Panel | ||||
|---|---|---|---|---|
| ||||
|
Summary
Description of the profile
Users expressed requirements that suggest caBIG services are not sufficiently described to determine if they meets a user’s requirements or are interoperable with other services. These requirements are deemed applicable to future KR services.
The Services Functional Profile derives its capabilities from the SOA Service Description Model and consequently specialize capabilities architecturally implied by the concept of Service Description Model
Services specializes capabilities architecturally implied by its associated concepts of Artifact , Change , Composition , Interaction , Interoperability , Metrics , Policy , Semantic Model , Service Description Model . The implied architectural capabilities are described in the following paragraphs.
Artifact An artifact is a managed resource within the Semantic Infrastructure.
An artifact is associated with the following capabilities:
- descriptions to enable the artifact to be visible, where the description includes a unique identifier for the artifact and a sufficient, and preferably a machine processible, representation of the meaning of terms used to describe the artifact, its functions, and its effects;
- 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;
- accessible storage of artifacts and artifact descriptions, so service participants can access, examine, and use the artifacts as defined.
Change Artifact descriptions change over time and their contents will reflect changing needs and context.
Architectural implications of change on the Semantic Infrastructure are reflected in the following capabilities:
- mechanisms to support the storage, referencing, and access to normative definitions of one or more versioning schemes that may be applied to identify different aggregations of descriptive information, where the different schemes may be versions of a versioning scheme itself;
- configuration management mechanisms to capture the contents of the each aggregation and apply a unique identifier in a manner consistent with an identified versioning scheme;
- one or more mechanisms to support the storage, referencing, and access to conversion relationships between versioning schemes, and the mechanisms to carry out such conversions.
Composition 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.
Interaction Descriptions of interactions are important for enabling auditability and repeatability, thereby establishing a context for results and support for understanding observed change in performance or results. Infrastructure services provide mechanisms to support service interaction.
Architectural implications of interactions on the Semantic Infrastructure are reflected in 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.
- mediation services such as message and event brokers, providers, and/or buses that provide message translation/transformation, gateway capability, message persistence, reliable message delivery, and/or intelligent routing semantics;
- binding services that support translation and transformation of multiple application-level protocols to standard network transport protocols;
- auditing and logging services that provide a data store and mechanism to record information related to service interaction activity such as message traffic patterns, security violations, and service contract and policy violations
- security services that abstract techniques such as public key cryptography, secure networks, virus protection, etc., which provide protection against common security threats in a SOA ecosystem;
- monitoring services such as hardware and software mechanisms that both monitor the performance of systems that host services and network traffic during service interaction, and are capable of generating regular monitoring reports.
Interoperability 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.
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.
Metrics 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.
Policy Artifact Descriptions include references to policies defining conditions of use and optionally contracts representing agreement on policies and other conditions.
Architectural implications of policy on the Semantic Infrastructure are reflected in the following capabilities:
- descriptions to enable the policy modules to be visible, where the description includes a unique identifier for the policy and a sufficient, and preferably a machine processible, representation of the meaning of terms used to describe the policy, its functions, and its effects;
- one or more discovery mechanisms that enable searching for policies that best meet the search criteria specified by the service participant; where the discovery mechanism will have access to the individual policy descriptions, possibly through some repository mechanism;
- accessible storage of policies and policy descriptions, so service participants can access, examine, and use the policies as defined.
Policy capabilities are specialization of Artifact capabilities.
Semantic Model Artifact Descriptions make use of defined semantics, where the semantics may be used for categorization or providing other property and value information for description classes.
Architectural implications of semantics on the Semantic Infrastructure are reflected in the following capabilities:
- semantic models that provide normative descriptions of the utilized terms, where the models may range from a simple dictionary of terms to an ontology showing complex relationships and capable of supporting enhanced reasoning. This is a refinement of the Artifact metadata capability.
- mechanisms to support the storage, referencing, and access to these semantic models. This is a refinement of the Artifact store capability.
- configuration management mechanisms to capture the normative description of each semantic model and to apply a unique identifier in a manner consistent with an identified versioning scheme. This is a refinement of the Change configurationManagement capability.
- one or more mechanisms to support the storage, referencing, and access to conversion relationships between semantic models, and the mechanisms to carry out such conversions.
Service Description Model A service description is an artifact, usually document-based, that 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.
A service description artifact may be a single document or it may be an interlinked set of documents.
Architectural implications of service description on the Semantic Infrastructure are reflected in the following functional decomposition:
- Description will change over time and its contents will reflect changing needs and context. This is elaborated in the inherited Change profile.
- Description makes use of defined semantics, where the semantics may be used for categorization or providing other property and value information for description classes. This is elaborated in the inherited Semantic Model profile.
- Descriptions include reference to policies defining conditions of use and optionally contracts representing agreement on policies and other conditions. This is elaborated in the inherited Policy profile.
- Descriptions include references to metrics which describe the operational characteristics of the subjects being described. This is elaborated in the inherited Metrics profile.
- 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 is elaborated in the inherited Interaction profile.
- 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 is elaborated in the inherited Composition 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 is elaborated in the inherited Interoperability profile.
Policy capabilities are specialization of Artifact capabilities.
Capabilities
- assembly
- binding
- cadsrModel
- complianceDiscovery
- componentAcquisition
- compositionArchive
- compositionChange
- configurationManagement
- discovery
- eprModel
- identity
- interactionLog
- interactionResults
- interoperabilityDiscovery
- lexEvsAPI
- lexEvsRdfBackend
- lexEvsSparqlEndpoint
- logging
- mediation
- metadata
- metrics
- metricsDiscovery
- monitor
- monitoring
- provenance
- security
- semanticConversion
- serviceChangeNotification
- serviceMetadataCompatabilityLevel
- serviceMetadataValidation
- serviceQualityAndStabilityAssessmentModel
- store
- transition
- uniqueIdentifierResolution
- versioning
Requirements traceability
Requirement | Source | Capability | ||||||
|---|---|---|---|---|---|---|---|---|
Make it mandatory that user-friendly service metadata (e.g., service name) is always exposed. Even better, provide automated validation of the service metadata. | Gap Analysis::Service::
| |||||||
Service metadata should capture the compatibility level of the service, including the date of the review. | Gap Analysis::Service::
| |||||||
Service metadata should be extended to provide some assessment of service quality and stability | Gap Analysis::Service::
| |||||||
Use Introduce Toolkit generated service metadata and a service loader tool to register use/reuse of data elements in caDSR | Gap Analysis::Service::
| |||||||
Semantic infrastructure should support metadata around EPRs | Gap Analysis::Service::
| |||||||
Provide a SPARQL endpoint for querying. LexEVS | Gap Analysis::Federation::
| |||||||
Provide an RDF triple store backend for LexEVS, so that LexEVS can leverage tools and technologies (i.e, querying, browsing) developed by the Semantic Web community. | Gap Analysis::Service::
| |||||||
Programmatic Access to LexEVS API | Gap Analysis::Interface::
| |||||||
Provide Unique Identifier Resolution across Grid | Gap Analysis::Service::
| |||||||
Artifact lifecycle management and metadata requirements include the ability to: * Manage lifecycle, governance and versioning of the models, content and forms * Establish relationships and dependencies between models, content and forms * Determine provenance, jurisdiction, authority and intellectual property * Create represention and views of the information, realized through the appropriate transforms * Provide access control and other security constraints * Create annotations for better discovery and searching of artifacts * Develop usage scenarios and context for the information * Provide terminology and value set binding The artifacts are bound to the services via the service metadata. The service metadata combined with the artifacts and supporting metadata provide a comprehensive service specification. The artifact management requirements listed above are derived from the following use cases: * caEHR: The caEHR project has adopted ECCF for specifications and CDA documents for interoperability. The caEHR project requirements include the need for an infrastructure for managing all the artifacts generated during specification process, including HL7 models and documents. The caEHR project also intends to publish these artifacts for the community and vendors. The infrastructure needs to support better discovery, making all the relevant information available in the right context. * ONC and other external EHR adopters: ONC has adopted CCD and CCR for meaningful use. All national EHR implementations are expected to support forms and the semantics of these forms play a critical role in interoperability. The semantic infrastructure must provide a mechanism to create, store and manage these forms. * Clinical Trials: Clinical trials use forms to capture clinical information, and the semantics captured by these forms are critical for interoperability and reporting. The semantic infrastructure must provide a mechanism to manage the lifecycle of these forms. | Semantic Infrastructure Requirements::Artifact Management::
| |||||||
KR needs terminology from the enterprise vocabulary services at both the concept and value set level to bind to metadata objects in the knowledge repository. | Gap Analysis::EVS::
| |||||||
KR needs the ability to check in and version the newly annotated metadata objects and link back to the terminology value sets stored in EVS. This requires tracking versioning of the value set as well as versioning of the value set binding to the metadata object | Gap Analysis::EVS::
| |||||||
Service Oriented Architecture is an architectural paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains. Consequently, it is important that organizations that plan to engage in service interactions adopt governance policies and procedures sufficient to ensure that there is standardization across both internal and external organizational boundaries to promote the effective creation and use of SOA-based services. SOA governance requires numerous architectural capabilities on the Semantic Infrastructure: Governance is expressed through policies and assumes multiple use of focused policy modules that can be employed across many common circumstances This is elaborated in the inherited Policy profile. Governance requires that the participants understand the intent of governance, the structures created to define and implement governance, and the processes to be followed to make governance operational. This is provided by capabilities specialized from the inherited Management Profile. Governance policies are made operational through rules and regulations. This is provided by the following capabilities, most of which are specializations of the inherited Artifact Profile: * descriptions to enable the rules and regulations to be visible, where the description includes a unique identifier and a sufficient, and preferably a machine process-able, representation of the meaning of terms used to describe the rules and regulations; * one or more discovery mechanisms that enable searching for rules and regulations that may apply to situations corresponding to the search criteria specified by the service participant; where the discovery mechanism will have access to the individual descriptions of rules and regulations, possibly through some repository mechanism; * accessible storage of rules and regulations and their respective descriptions, so service participants can understand and prepare for compliance, as defined. * SOA services to access automated implementations of the Governance Processes. Governance implies management to define and enforce rules and regulations.. This is elaborated in the inherited Management profile. Governance relies on metrics to define and measure compliance. This is elaborated in the inherited Metric profile. | Semantic Profile::OASIS SOA::
| monitor from inherited abstract profile Metricsmetrics from inherited abstract profile Metricsdiscovery from inherited abstract profile Artifactidentity from inherited abstract profile Artifactmetadata from inherited abstract profile Artifactstore from inherited abstract profile Artifact | ||||||
Interaction is the activity involved in using a service to access capability in order to achieve a particular desired real world effect, where real world effect is the actual result of using a service. An interaction can be characterized by a sequence of actions. Consequently, interacting with a service, i.e. performing actions against the service--usually mediated by a series of message exchanges--involves actions performed by the service. Different modes of interaction are possible such as modifying the shared state of a resource. Note that a participant (or agent acting on behalf of the participant) can be the sender of a message, the receiver of a message, or both. Interacting with Services has the following architectural implications on mechanisms that facilitate service interaction: A well-defined service Information Model, as elaborated in the inherited Information Model profile. A well-defined service Behavior Model, as elaborated in the inherited Behavior Model profile. Service composition mechanisms to support orchestration of service-oriented business processes and choreography of service-oriented business collaborations, as elaborated in the inherited Service Composition profile. Infrastructure services that provides mechanisms to support service interaction, as elaborated in the inherited Interaction profile. A layered and tiered service component architecture that supports multiple message exchange patterns (MEPs)l, as elaborated in the inherited Message Exchange profile. | Semantic Profile::OASIS SOA::
| interactionLog from inherited abstract profile InteractioninteractionResults from inherited abstract profile Interactionmediation from inherited abstract profile Interactionbinding from inherited abstract profile Interactionlogging from inherited abstract profile Interactionsecurity from inherited abstract profile Interactionmonitoring from inherited abstract profile Interaction | ||||||
A service description is an artifact, usually document-based, that 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. A service description artifact may be a single document or it may be an interlinked set of documents. Architectural implications of service description on the Semantic Infrastructure are reflected in the following functional decomposition: * Description will change over time and its contents will reflect changing needs and context. This is elaborated in the inherited Change profile. * Description makes use of defined semantics, where the semantics may be used for categorization or providing other property and value information for description classes. This is elaborated in the inherited Semantic Model profile. * Descriptions include reference to policies defining conditions of use and optionally contracts representing agreement on policies and other conditions. This is elaborated in the inherited Policy profile. * Descriptions include references to metrics which describe the operational characteristics of the subjects being described. This is elaborated in the inherited Metrics profile. * 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 is elaborated in the inherited Interaction profile. * 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 is elaborated in the inherited Composition 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 is elaborated in the inherited Interoperability profile. Policy capabilities are specialization of Artifact capabilities. | Semantic Profile::OASIS SOA::
| versioning from inherited abstract profile ChangeconfigurationManagement from inherited abstract profile Changetransition from inherited abstract profile Changediscovery from inherited abstract profile Artifactidentity from inherited abstract profile Artifactmetadata from inherited abstract profile Artifactstore from inherited abstract profile ArtifactsemanticConversion from inherited abstract profile Semantic Modelmonitor from inherited abstract profile Metricsmetrics from inherited abstract profile MetricsmetricsDiscovery from inherited abstract profile MetricscomplianceDiscovery from inherited abstract profile MetricsinteractionLog from inherited abstract profile InteractioninteractionResults from inherited abstract profile InteractioncompositionArchive from inherited abstract profile Compositionassembly from inherited abstract profile CompositioncompositionChange from inherited abstract profile CompositioncomponentAcquisition from inherited abstract profile CompositioninteroperabilityDiscovery from inherited abstract profile InteroperabilityserviceChangeNotification from inherited abstract profile Interoperability | ||||||
One of the key requirements for participants interacting with each other in the context of a SOA is achieving visibility: before services can interoperate, the participants have to be visible to each other using whatever means are appropriate. The Reference Model analyzes visibility in terms of awareness, willingness, and reachability. Visibility in a SOA ecosystem has the following architectural implications on mechanisms providing support for awareness, willingness, and reachability: 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 architectural mechanisms for providing awareness to communities of interest will require support for: * 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 architectural mechanisms for determining willingness to interact will require support 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 architectural mechanisms for establishing reachability will require support 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 interaction but may be further aided by the use of a presence protocol for which the endpoints actively participate. | Semantic Profile::OASIS SOA::
| discovery from inherited abstract profile Artifact |
| 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
binding services that support translation and transformation of multiple application-level protocols to standard network transport protocols;
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Use Introduce Toolkit generated service metadata and a service loader tool to register use/reuse of data elements in caDSR
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Mechanisms to catalog and enable discovery of compliance records associated with policies, contracts, and constraints that are based on these metrics.
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
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
Mechanisms to support the storage, referencing, and access to normative definitions of one or more versioning schemes that may be applied to identify different aggregations of descriptive information, where the different schemes may be versions of a versioning scheme itself.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
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.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Semantic infrastructure should support metadata around EPRs
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Descriptions which include a unique identifier for the artifact.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
One or more mechanisms to capture, describe, store, discover, and retrieve interaction logs, execution contexts, and the combined interaction descriptions.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
One or more mechanisms for attaching to any results the means to identify and retrieve the interaction description under which the results were generated.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
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.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Programmatic Access to LexEVS API
KR needs terminology from the enterprise vocabulary services at both the concept and value set level to bind to metadata objects in the knowledge repository.
Requirements addressed
- EVS-6 - Value Set Versioning
- EVS-1 - Concept and Value set Terminology binding
- 129 - Programmatic Access to LexEVS API
- Artifact Lifecycle Management
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Provide an RDF triple store backend for LexEVS, so that LexEVS can leverage tools and technologies (i.e, querying, browsing) developed by the Semantic Web community.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Provide a SPARQL endpoint for querying. LexEVS
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
auditing and logging services that provide a data store and mechanism to record information related to service interaction activity such as message traffic patterns, security violations, and service contract and policy violations
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
mediation services such as message and event brokers, providers, and/or buses that provide message translation/transformation, gateway capability, message persistence, reliable message delivery, and/or intelligent routing semantics;
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
A representation of the meaning of terms used to describe the artifact, its functions, and its effects.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Access to metrics information generated or accessible by related services
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Mechanisms to catalog and enable discovery of which metrics are available for a described artifact and information on how these metrics can be accessed.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Access to platform infrastructure monitoring and reporting capabilities.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
monitoring services such as hardware and software mechanisms that both monitor the performance of systems that host services and network traffic during service interaction, and are capable of generating regular monitoring reports.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
While the Resource identity provides the means to know which subject and subject description are being considered, Provenance as related to the Description class provides information that reflects on the quality or usability of the subject. Provenance specifically identifies the entity (human, defined role, organization, ...) that assumes responsibility for the resource being described and tracks historic information that establishes a context for understanding what the resource provides and how it has changed over time. Responsibilities may be directly assumed by the Stakeholder who owns a Resource or the Owner may designate Responsible Parties for the various aspects of maintaining the resource and provisioning it for use by others. There may be more than one entity identified under Responsible Parties; for example, one entity may be responsible for code maintenance while another is responsible for provisioning of the executable code. The historical aspects may also have multiple entries, such as when and how data was collected and when and how it was subsequently processed, and as with other elements of description, may provide links to other assets maintained by the Resource owner.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
security services that abstract techniques such as public key cryptography, secure networks, virus protection, etc., which provide protection against common security threats in a SOA ecosystem;
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
One or more mechanisms to support the storage, referencing, and access to conversion relationships between semantic models, and the mechanisms to carry out such conversions.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Tools to appropriately track users of the descriptions and notify them when a new version of the description is available.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Service metadata should capture the compatibility level of the service, including the date of the review.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Make it mandatory that user-friendly service metadata (e.g., service name) is always exposed. Even better, provide automated validation of the service metadata.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Service metadata should be extended to provide some assessment of service quality and stability
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Accessible storage of artifacts and artifact descriptions, so service participants can access, examine, and use the artifacts as defined.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
One or more mechanisms to support the storage, referencing, and access to conversion relationships between versioning schemes, and the mechanisms to carry out such conversions.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Provide Unique Identifier Resolution across Grid
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
Description
Configuration management mechanisms to capture the contents of the each aggregation and apply a unique identifier in a manner consistent with an identified versioning scheme.
Requirements addressed
Overview of possible operations
| Wiki Markup |
|---|
{scrollbar:icons=false} |
