 |
Page History
| Wiki Markup |
|---|
{scrollbar:icons=false}
h4. {page-info:title}
{panel:title=Contents of this Page}
{toc:minlevel=5}
{panel}
h5. Summary
h6. 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.
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.
Discovery is the set of capabilities which enable searching for artifacts that best meet the search criteria specified by the service participant.
Aspects of discovery include:
* Search for services, policies, and other artifact descriptions accessible via some repository mechanism
* Search for operational characteristics of artifacts, which are metrics defined in artifact descriptions. The information is accessible via infrastructure monitoring capabilties or directly from services.
* Tracking and notification mechanisms related to artifact usage, service availability, operational conformance
Capabilities associated with discovery are delineated in the functional profiles inherited, and specialized, by the discovery profile, namely:
* Artifact
* Metrics
* Interoperability
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.
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.
h6. Capabilities
* [complianceDiscovery|#_16_5_1_24a0131_1283702219073_894098_3212]
* [dataDiscovery|#_16_5_1_24a0131_1283167155540_936130_3058]
* [discovery|#_16_5_1_24a0131_1283714222600_103266_4106]
* [identity|#_16_5_1_24a0131_1283714222601_506267_4107]
* [interoperabilityDiscovery|#_16_5_1_24a0131_1283704952692_78857_3340]
* [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]
* [provenance|#_16_5_1_24a0131_1283793030699_512571_7056]
* [serviceChangeNotification|#_16_5_1_24a0131_1283704952697_176583_3341]
* [store|#_16_5_1_24a0131_1283714222609_981432_4109]
h5. Requirements traceability
|| Requirement || Source || Capability ||
| | 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, |
| | Semantic Profile::OASIS SOA::{anchor:_16_5_1_24a0131_1283763560612_868976_4608}Service Description Model | [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, [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, [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, |
| 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:_16_5_1_24a0131_1283090073139_167512_4524}Service Discovery and Utilization | [dataDiscovery|#_16_5_1_24a0131_1283167155540_936130_3058], |
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_1283167155540_936130_3058}dataDiscovery
h6. 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.
h6. Requirements addressed
* [Service Discovery and Utilization|#_16_5_1_24a0131_1283090073139_167512_4524]
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
* [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_1283714222601_506267_4107}identity
h6. Description
Descriptions which include a unique identifier for the artifact.
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_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:_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
* [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_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_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_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:_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
* [Governance Model|#_16_5_1_24a0131_1283763638521_214441_4616]
* [Service Description Model|#_16_5_1_24a0131_1283763560612_868976_4608]
h6. Overview of possible operations
{scrollbar:icons=false} |
