 |
Page History
| Scrollbar |
|---|
| Children Display |
|---|
| Page info | ||||
|---|---|---|---|---|
|
| Panel | ||||
|---|---|---|---|---|
| ||||
|
Summary
...
Description of the profile
...
Data discovery enables secondary users to find the types of data available in the ecosystem as well as summary-level information about available data sets.
An artifact is a managed resource within the Semantic Infrastructure.
...
- 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.
...
Capabilities
...
- complianceDiscovery
- dataDiscovery
- discovery
- identity
- interoperabilityDiscovery
- metadata
- metrics
- metricsDiscovery
- monitor
- provenance
- serviceChangeNotification
- store
Requirements traceability
Requirement | Source | Capability | ||||||
|---|---|---|---|---|---|---|---|---|
| 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, | ||||||
This group of requirements focuses on enabling developers of composite services and applications to discover, compose, and invoke services. This includes the discovery of published services based on service metadata and the generation of client APIs in multiple languages to provide cross-platform access to existing services. The platform will use the semantic infrastructure service metadata to address all the service discovery requirements. The semantic infrastructure relies on metadata about services and artifacts. Link to use case satisfied from caGRID 2.0 Roadmap: As institutions share de-identified glioblastoma data sets, they are available to others via data discovery. The treatment recommendation service used by the oncologist is able to discover these new data sets and their corresponding information models, and include that data for subsequent use in recommendation of treatment. Link to use case satisfied from caGRID 2.0 Roadmap: all of the data management and access services in the use case are utilized by application developers to build the user interfaces that the clinicians use during the course of patient care. | Semantic Infrastructure Requirements::caGRID 2.0 Platform and Terminology Integration::
|
| 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
...
Data Discovery
Data discovery capabilities include:
- tools to appropriately track users of the modeled descriptions and notify them when a new version of the modeled description is available.
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
...
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 |
|---|
