 |
Page History
...
| Children Display |
|---|
| Page info | ||||
|---|---|---|---|---|
|
...
Summary
Description of the profile
A key function desired by virtually all stakeholders is the ability to query by example using an item from a model or vocabulary (e.g., data element, property, data type, constraint, relation, concept, etc.) to find equivalent and related elements defined anywhere in the knowledge repository. The response should provide an easily understood description of the degree and nature of the semantic convergence between the example item and responsive items.
From inherited abstract Artifact Functional Profile
An artifact is a managed resource within the Semantic Infrastructure.
...
- 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.
...
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:
...
- 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.
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:
Capabilities
- 026.3
- 029
- complianceDiscovery
- discovery
- identity
- interoperabilityDiscovery
- metadata
- metrics
- metricsDiscovery
- monitor
- provenance
- publishedLiteratureIndex
- queryEvsAndModels
- queryModelTouchpoints
- queryUnstructuredSources
- saveQueryResults
- serviceChangeNotification
- store
...
Requirements
...
traceability
Requirement | Source | Capability | |||||
|---|---|---|---|---|---|---|---|
System allows for discovery of touch points to other models | Gap Analysis::Discover::
|
...
Provide a mechanism to assist the user in choosing the right data element |
...
Gap Analysis::Discover::
|
...
Support search like 'x' for concepts in the EVS using natural language processing to identify possible matches | Gap Analysis::Discover::
|
...
029, |
Provide a discovery service/tool which exposes data elements not based on the Names stored in the KR but by using a concept from the EVS search and pulling associated Administered Components from the KR to match. | Gap Analysis::Discover:: |
...
| |||||||
Create indexes of published literature using natural language processing and ontologies to index the content | Gap Analysis::Discover:: |
...
| |||||||
Automatically extract information for reuse from unstructured sources, programmatic access to the 'materials and methods section of a paper' so the same experiments can be performed using your own data | Gap Analysis:: |
...
Discover::
| |||||||
There is a need to provide retention of query results in different formats | Gap Analysis:: |
...
HL7 CIC::
| ||||||||
End-users need the ability to perform a search for models and to search EVS through a single user interface | Gap Analysis::EVS::
| |||||||
| Semantic Profile::OASIS SOA::
| monitor from inherited abstract profile Metrics, metrics from inherited abstract profile Metrics, discovery from inherited abstract profile Artifact, identity from inherited abstract profile Artifact, metadata from inherited abstract profile Artifact, store from inherited abstract profile Artifact, | ||||||
| Semantic Profile::OASIS SOA::
| discovery from inherited abstract profile Artifact, identity from inherited abstract profile Artifact, metadata from inherited abstract profile Artifact, store from inherited abstract profile Artifact, monitor from inherited abstract profile Metrics, metrics from inherited abstract profile Metrics, metricsDiscovery from inherited abstract profile Metrics, complianceDiscovery from inherited abstract profile Metrics, interoperabilityDiscovery from inherited abstract profile Interoperability, serviceChangeNotification from inherited abstract profile Interoperability, |
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
Provide a mechanism to assist the user in choosing the right data element
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
Support search like 'x' for concepts in the EVS using natural language processing to identify possible matches
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
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
Descriptions which include a unique identifier for the artifact.
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
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
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
Create indexes of published literature using natural language processing and ontologies to index the content
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
Support search for models and the EVS through a single User Interface
Provide a discovery service/tool which exposes data elements not based on the Names stored in the KR but by using a concept from the EVS search and pulling associated Administered Components from the KR to match.
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
System allows for discovery of touch points to other models
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
Automatically extract information for reuse from unstructured sources, programmatic access to the 'materials and methods section of a paper' so the same experiments can be performed using your own data
Requirements addressed
Overview of possible operations
| Anchor | ||||
|---|---|---|---|---|
|
...
Description
There is a need to provide retention of query results in different formats
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
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
| Scrollbar |
|---|
