Page History

page-info

:title}
{panel:title=Contents of this Page}
{toc:minlevel=5}
{panel}

h5. Summary

h6. 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.


h6. Capabilities


* [assembly|#_16_5_1_24a0131_1283703443772_860088_3293]
* [binding|#_16_5_1_24a0131_1283774411368_995660_5431]
* [cadsrModel|#EAID_D2EEFCBC_0D35_4cff_B33A_B9897FDFE1F9]
* [complianceDiscovery|#_16_5_1_24a0131_1283702219073_894098_3212]
* [componentAcquisition|#_16_5_1_24a0131_1283704509983_673729_3325]
* [compositionArchive|#_16_5_1_24a0131_1283703443770_810122_3292]
* [compositionChange|#_16_5_1_24a0131_1283703443775_178969_3294]
* [configurationManagement|#_16_5_1_24a0131_1283700133655_905377_3117]
* [discovery|#_16_5_1_24a0131_1283714222600_103266_4106]
* [eprModel|#EAID_A54679AA_EA15_4452_BF06_FFF00735BDE3]
* [identity|#_16_5_1_24a0131_1283714222601_506267_4107]
* [interactionLog|#_16_5_1_24a0131_1283703044067_803205_3257]
* [interactionResults|#_16_5_1_24a0131_1283703044069_331285_3258]
* [interoperabilityDiscovery|#_16_5_1_24a0131_1283704952692_78857_3340]
* [lexEvsAPI|#EAID_E9D59ED9_19F2_44b5_9B29_2D6CE49C8B08]
* [lexEvsRdfBackend|#EAID_1D155EE9_7822_4d15_986C_AC750198E5E9]
* [lexEvsSparqlEndpoint|#EAID_70FD0874_6EB0_4833_9411_135583B8DF76]
* [logging|#_16_5_1_24a0131_1283774412029_665259_5444]
* [mediation|#_16_5_1_24a0131_1283774410554_993474_5418]
* [metadata|#_16_5_1_24a0131_1283714222603_853936_4108]
* [metrics|#_16_5_1_24a0131_1283702219069_775824_3210]
* [metricsDiscovery|#_16_5_1_24a0131_1283702219071_411273_3211]
* [monitor|#_16_5_1_24a0131_1283702219067_789210_3209]
* [monitoring|#_16_5_1_24a0131_1283774413444_304515_5470]
* [provenance|#_16_5_1_24a0131_1283793030699_512571_7056]
* [security|#_16_5_1_24a0131_1283774412802_440973_5457]
* [semanticConversion|#_16_5_1_24a0131_1283765671415_826766_4835]
* [serviceChangeNotification|#_16_5_1_24a0131_1283704952697_176583_3341]
* [serviceMetadataCompatabilityLevel|#EAID_9476F63D_48C3_4c81_BF6E_9BC8FC8B87F4]
* [serviceMetadataValidation|#EAID_E99B99B4_76D4_42cd_BC53_2E66633F885D]
* [serviceQualityAndStabilityAssessmentModel|#EAID_F0031E93_C54E_4118_889D_E14099E9FB45]
* [store|#_16_5_1_24a0131_1283714222609_981432_4109]
* [transition|#_16_5_1_24a0131_1283700246486_44421_3128]
* [uniqueIdentifierResolution|#EAID_3D5B90C8_FAF2_4f9b_97D4_BE8F97A24A06]
* [versioning|#_16_5_1_24a0131_1283699095521_961509_3106]

h5. 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::{anchor:_16_5_1_24a0131_1283086804081_291392_4389}060 - Service metadata validation | [serviceMetadataValidation|#EAID_E99B99B4_76D4_42cd_BC53_2E66633F885D]\\
  |
| Service metadata should capture the compatibility level of the service, including the date of the review. | Gap Analysis::Service::{anchor:_16_5_1_24a0131_1283086805491_171990_4392}061 - Service compatibility level | [serviceMetadataCompatabilityLevel|#EAID_9476F63D_48C3_4c81_BF6E_9BC8FC8B87F4]\\
  |
| Service metadata should be extended to provide some assessment of service quality and stability | Gap Analysis::Service::{anchor:_16_5_1_24a0131_1283086805618_88420_4395}062 - Service quality and stability assessment | [serviceQualityAndStabilityAssessmentModel|#EAID_F0031E93_C54E_4118_889D_E14099E9FB45]\\
  |
| Use Introduce Toolkit generated service metadata and a service loader tool to register use/reuse of data elements in caDSR | Gap Analysis::Service::{anchor:_16_5_1_24a0131_1283086806280_653707_4401}065 - caDSR data element registration | [cadsrModel|#EAID_D2EEFCBC_0D35_4cff_B33A_B9897FDFE1F9]\\
  |
| Semantic infrastructure should support metadata around EPRs | Gap Analysis::Service::{anchor:_16_5_1_24a0131_1283086806892_120201_4404}071 - EPR metadata | [eprModel|#EAID_A54679AA_EA15_4452_BF06_FFF00735BDE3]\\
  |
| Provide a SPARQL endpoint for querying. LexEVS | Gap Analysis::Federation::{anchor:_16_5_1_24a0131_1283084230286_388917_4269}115 - LexEVS SPARQL Endpoint | [lexEvsSparqlEndpoint|#EAID_70FD0874_6EB0_4833_9411_135583B8DF76]\\
  |
| 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::{anchor:_16_5_1_24a0131_1283086807348_279429_4407}122 - RDF triple store backend for LexEVS | [lexEvsRdfBackend|#EAID_1D155EE9_7822_4d15_986C_AC750198E5E9]\\
  |
| Programmatic Access to LexEVS API | Gap Analysis::Interface::{anchor:_16_5_1_24a0131_1283084943843_568089_4305}129 - Programmatic Access to LexEVS API | [lexEvsAPI|#EAID_E9D59ED9_19F2_44b5_9B29_2D6CE49C8B08]\\
  |
| Provide Unique Identifier Resolution across Grid | Gap Analysis::Service::{anchor:_16_5_1_24a0131_1283086807514_569289_4410}130.3 - Unique Identifier Resolution | [uniqueIdentifierResolution|#EAID_3D5B90C8_FAF2_4f9b_97D4_BE8F97A24A06]\\
  |
| 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::{anchor:_16_5_1_24a0131_1283090023842_213150_4485}Artifact Lifecycle Management | [lexEvsAPI|#EAID_E9D59ED9_19F2_44b5_9B29_2D6CE49C8B08]\\
  |
| 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::{anchor:_16_5_1_24a0131_1283078021537_443320_4093}EVS-1 - Concept and Value set Terminology binding | [lexEvsAPI|#EAID_E9D59ED9_19F2_44b5_9B29_2D6CE49C8B08]\\
  |
| 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::{anchor:_16_5_1_24a0131_1283078025163_411990_4108}EVS-6 - Value Set Versioning | [lexEvsAPI|#EAID_E9D59ED9_19F2_44b5_9B29_2D6CE49C8B08]\\
  |
| 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::{anchor:_16_5_1_24a0131_1283763638521_214441_4616}Governance Model | [monitor|#_16_5_1_24a0131_1283702219067_789210_3209] *from inherited abstract profile* Metrics[metrics|#_16_5_1_24a0131_1283702219069_775824_3210] *from inherited abstract profile* Metrics[discovery|#_16_5_1_24a0131_1283714222600_103266_4106] *from inherited abstract profile* Artifact[identity|#_16_5_1_24a0131_1283714222601_506267_4107] *from inherited abstract profile* Artifact[metadata|#_16_5_1_24a0131_1283714222603_853936_4108] *from inherited abstract profile* Artifact[store|#_16_5_1_24a0131_1283714222609_981432_4109] *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::{anchor:_16_5_1_24a0131_1283763631267_880282_4612}Interacting with Services Model | [interactionLog|#_16_5_1_24a0131_1283703044067_803205_3257] *from inherited abstract profile* Interaction[interactionResults|#_16_5_1_24a0131_1283703044069_331285_3258] *from inherited abstract profile* Interaction[mediation|#_16_5_1_24a0131_1283774410554_993474_5418] *from inherited abstract profile* Interaction[binding|#_16_5_1_24a0131_1283774411368_995660_5431] *from inherited abstract profile* Interaction[logging|#_16_5_1_24a0131_1283774412029_665259_5444] *from inherited abstract profile* Interaction[security|#_16_5_1_24a0131_1283774412802_440973_5457] *from inherited abstract profile* Interaction[monitoring|#_16_5_1_24a0131_1283774413444_304515_5470] *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::{anchor:_16_5_1_24a0131_1283763560612_868976_4608}Service Description Model | [versioning|#_16_5_1_24a0131_1283699095521_961509_3106] *from inherited abstract profile* Change[configurationManagement|#_16_5_1_24a0131_1283700133655_905377_3117] *from inherited abstract profile* Change[transition|#_16_5_1_24a0131_1283700246486_44421_3128] *from inherited abstract profile* Change[discovery|#_16_5_1_24a0131_1283714222600_103266_4106] *from inherited abstract profile* Artifact[identity|#_16_5_1_24a0131_1283714222601_506267_4107] *from inherited abstract profile* Artifact[metadata|#_16_5_1_24a0131_1283714222603_853936_4108] *from inherited abstract profile* Artifact[store|#_16_5_1_24a0131_1283714222609_981432_4109] *from inherited abstract profile* Artifact[semanticConversion|#_16_5_1_24a0131_1283765671415_826766_4835] *from inherited abstract profile* Semantic Model[monitor|#_16_5_1_24a0131_1283702219067_789210_3209] *from inherited abstract profile* Metrics[metrics|#_16_5_1_24a0131_1283702219069_775824_3210] *from inherited abstract profile* Metrics[metricsDiscovery|#_16_5_1_24a0131_1283702219071_411273_3211] *from inherited abstract profile* Metrics[complianceDiscovery|#_16_5_1_24a0131_1283702219073_894098_3212] *from inherited abstract profile* Metrics[interactionLog|#_16_5_1_24a0131_1283703044067_803205_3257] *from inherited abstract profile* Interaction[interactionResults|#_16_5_1_24a0131_1283703044069_331285_3258] *from inherited abstract profile* Interaction[compositionArchive|#_16_5_1_24a0131_1283703443770_810122_3292] *from inherited abstract profile* Composition[assembly|#_16_5_1_24a0131_1283703443772_860088_3293] *from inherited abstract profile* Composition[compositionChange|#_16_5_1_24a0131_1283703443775_178969_3294] *from inherited abstract profile* Composition[componentAcquisition|#_16_5_1_24a0131_1283704509983_673729_3325] *from inherited abstract profile* Composition[interoperabilityDiscovery|#_16_5_1_24a0131_1283704952692_78857_3340] *from inherited abstract profile* Interoperability[serviceChangeNotification|#_16_5_1_24a0131_1283704952697_176583_3341] *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::{anchor:_16_5_1_24a0131_1283763628053_328597_4610}Service Visibility Model | [discovery|#_16_5_1_24a0131_1283714222600_103266_4106] *from inherited abstract profile* Artifact |


h5. {anchor:_16_5_1_24a0131_1283703443772_860088_3293}assembly


h6. Description

Tools to facilitate identifying description elements that are to be aggregated to assemble the composite description.

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283774411368_995660_5431}binding


h6. Description

binding services that support translation and transformation of multiple application-level  protocols to standard network transport protocols;

h6. Requirements addressed

* [Interacting with Services Model|#_16_5_1_24a0131_1283763631267_880282_4612]

h6. Overview of possible operations



h5. {anchor:EAID_D2EEFCBC_0D35_4cff_B33A_B9897FDFE1F9}cadsrModel


h6. Description

Use Introduce Toolkit generated service metadata and a service loader tool to register use/reuse of data elements in caDSR

h6. Requirements addressed

* [065 - caDSR data element registration|#_16_5_1_24a0131_1283086806280_653707_4401]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283702219073_894098_3212}complianceDiscovery


h6. Description

Mechanisms to catalog and enable discovery of compliance records associated with policies, contracts, and constraints that are based on these metrics.

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283704509983_673729_3325}componentAcquisition


h6. Description

Tools to facilitate identifying the sources of information to associate with the description elements.

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283703443770_810122_3292}compositionArchive


h6. Description

Tools to collect the identified description elements and their associated sources into a standard, referenceable format that can support general access and understanding.

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283703443775_178969_3294}compositionChange


h6. 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.

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283700133655_905377_3117}configurationManagement


h6. 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.

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283714222600_103266_4106}discovery


h6. 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.

h6. Requirements addressed

* [Service Visibility Model|#_16_5_1_24a0131_1283763628053_328597_4610]
* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]
* [Governance Model|#_16_5_1_24a0131_1283763638521_214441_4616]

h6. Overview of possible operations



h5. {anchor:EAID_A54679AA_EA15_4452_BF06_FFF00735BDE3}eprModel


h6. Description

Semantic infrastructure should support metadata around EPRs

h6. Requirements addressed

* [071 - EPR metadata|#_16_5_1_24a0131_1283086806892_120201_4404]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283714222601_506267_4107}identity


h6. Description

Descriptions which include a unique identifier for the artifact.

h6. Requirements addressed

* [Governance Model|#_16_5_1_24a0131_1283763638521_214441_4616]
* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283703044067_803205_3257}interactionLog


h6. Description

One or more mechanisms to capture, describe, store, discover, and retrieve interaction logs, execution contexts, and the combined interaction descriptions.

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]
* [Interacting with Services Model|#_16_5_1_24a0131_1283763631267_880282_4612]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283703044069_331285_3258}interactionResults


h6. 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.

h6. Requirements addressed

* [Interacting with Services Model|#_16_5_1_24a0131_1283763631267_880282_4612]
* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283704952692_78857_3340}interoperabilityDiscovery


h6. 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.

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]

h6. Overview of possible operations



h5. {anchor:EAID_E9D59ED9_19F2_44b5_9B29_2D6CE49C8B08}lexEvsAPI


h6. 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.

h6. Requirements addressed

* [EVS-6 - Value Set Versioning|#_16_5_1_24a0131_1283078025163_411990_4108]
* [EVS-1 - Concept and Value set Terminology binding|#_16_5_1_24a0131_1283078021537_443320_4093]
* [129 - Programmatic Access to LexEVS API|#_16_5_1_24a0131_1283084943843_568089_4305]
* [Artifact Lifecycle Management|#_16_5_1_24a0131_1283090023842_213150_4485]

h6. Overview of possible operations



h5. {anchor:EAID_1D155EE9_7822_4d15_986C_AC750198E5E9}lexEvsRdfBackend


h6. 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.

h6. Requirements addressed

* [122 - RDF triple store backend for LexEVS|#_16_5_1_24a0131_1283086807348_279429_4407]

h6. Overview of possible operations



h5. {anchor:EAID_70FD0874_6EB0_4833_9411_135583B8DF76}lexEvsSparqlEndpoint


h6. Description

Provide a SPARQL endpoint for querying. LexEVS

h6. Requirements addressed

* [115 - LexEVS SPARQL Endpoint|#_16_5_1_24a0131_1283084230286_388917_4269]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283774412029_665259_5444}logging


h6. 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

h6. Requirements addressed

* [Interacting with Services Model|#_16_5_1_24a0131_1283763631267_880282_4612]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283774410554_993474_5418}mediation


h6. 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;

h6. Requirements addressed

* [Interacting with Services Model|#_16_5_1_24a0131_1283763631267_880282_4612]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283714222603_853936_4108}metadata


h6. Description

A representation of the meaning of terms used to describe the artifact, its functions, and its effects.

h6. Requirements addressed

* [Governance Model|#_16_5_1_24a0131_1283763638521_214441_4616]
* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283702219069_775824_3210}metrics


h6. Description

Access to metrics information generated or accessible by related services

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]
* [Governance Model|#_16_5_1_24a0131_1283763638521_214441_4616]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283702219071_411273_3211}metricsDiscovery


h6. 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.

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283702219067_789210_3209}monitor


h6. Description

Access to platform infrastructure monitoring and reporting capabilities.

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]
* [Governance Model|#_16_5_1_24a0131_1283763638521_214441_4616]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283774413444_304515_5470

}monitoring


h6. 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.

h6. Requirements addressed

* [Interacting with Services Model|#_16_5_1_24a0131_

1283763631267_

880282_4612]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283793030699_512571_7056

}provenance


h6. 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.

h6. Requirements addressed


h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283774412802_440973_5457

}security


h6. 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;

h6. Requirements addressed

* [Interacting with Services Model|#_16_5_1_24a0131_

1283763631267_

880282_4612]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283765671415_826766_4835

}semanticConversion


h6. 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.

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_

1283763560612_

868976_4608]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283704952697_176583_3341

}serviceChangeNotification


h6. Description

Tools to appropriately track users of the descriptions and notify them when a new version of the description is available.

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]

h6. Overview of possible operations



h5. {anchor:EAID_9476F63D_48C3_4c81_BF6E_9BC8FC8B87F4

}serviceMetadataCompatabilityLevel


h6. Description

Service metadata should capture the compatibility level of the service, including the date of the review.

h6. Requirements addressed

* [061 - Service compatibility level|#_16_5_1_24a0131_1283086805491_171990_4392]

h6. Overview of possible operations



h5. {anchor:EAID_E99B99B4_76D4_42cd_BC53_2E66633F885D

}serviceMetadataValidation


h6. 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.

h6.

 Requirements addressed

* [060 - Service metadata

 validation|#_16_5_1_24a0131_1283086804081_291392_4389]

h6. Overview of possible operations



h5. {anchor:EAID_F0031E93_C54E_4118_889D_E14099E9FB45

}serviceQualityAndStabilityAssessmentModel


h6. Description

Service metadata should be extended to provide some assessment of service quality and stability

h6. Requirements addressed

* [062 - Service quality and stability assessment|#_16_5_1_24a0131_

1283086805618_

88420_4395]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283714222609_981432_4109

}store


h6. Description

Accessible storage of artifacts and artifact descriptions, so service participants can access, examine, and use the artifacts as defined.

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]
* [Governance Model|#_16_5_1_24a0131_

1283763638521_

214441_4616]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283700246486_44421_3128

}transition


h6. 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.

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]

h6. Overview of possible operations



h5. {anchor:EAID_3D5B90C8_FAF2_4f9b_97D4_BE8F97A24A06

}uniqueIdentifierResolution


h6. Description

Provide Unique Identifier Resolution across Grid

h6. Requirements addressed

* [130.3 - Unique Identifier Resolution|#_16_5_1_24a0131_1283086807514_569289_4410]

h6. Overview of possible operations



h5. {anchor:_16_5_1_24a0131_1283699095521_961509_3106

}versioning


h6. 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.

h6. Requirements addressed

* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]

h6. Overview of possible operations



{scrollbar:icons=false}