Page History

{scrollbar:icons=false}

Page info
title title

Summary

Description of the profile

There are numerous data repositories on the web today. These data repositories contain essential information that must be accessible to services in the ecosystem. As a result, caGrid 2.0 must provide capabilities to integrate these external repositories into the grid with the assumption that the remote service cannot be changed.

The semantic infrastructure will support integration with other metadata repositories, allowing the platform to leverage the semantic infrastructure for federated metadata discovery and analysis. The federated data query capabilities will be implemented by the platform.
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.

Capabilities

• complianceDiscovery
• discovery
• externalMetadataRepositoryIntegration
• identity
• interoperabilityDiscovery
• localizeMetadataMaintenance
• metadata
• metrics
• metricsDiscovery
• monitor
• provenance
• serviceChangeNotification
• store

Requirements traceability

Anchor
_16_5_1_24a0131_1283702219073_894098_3212 _16_5_1_24a0131_1283702219073_894098_3212

complianceDiscovery

Description

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

Requirements addressed

• Service Description Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283714222600_103266_4106 _16_5_1_24a0131_1283714222600_103266_4106

discovery

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

• Governance Model
• Service Description Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283427358555_770801_9268 _16_5_1_24a0131_1283427358555_770801_9268

externalMetadataRepositoryIntegration

Description

The semantic infrastructure will support integration with other metadata repositories, allowing the platform to leverage the semantic infrastructure for federated metadata discovery and analysis. The federated data query capabilities will be implemented by the platform.

Requirements addressed

• External Data Repositories

Overview of possible operations

Anchor
_16_5_1_24a0131_1283714222601_506267_4107 _16_5_1_24a0131_1283714222601_506267_4107

identity

Description

Descriptions which include a unique identifier for the artifact.

Requirements addressed

• Service Description Model
• Governance Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283704952692_78857_3340 _16_5_1_24a0131_1283704952692_78857_3340

interoperabilityDiscovery

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

• Service Description Model

Overview of possible operations

Anchor
EAID_5373C59B_35B3_4cad_87DA_C2BF43482C25 EAID_5373C59B_35B3_4cad_87DA_C2BF43482C25

localizeMetadataMaintenance

Description

Federate the metadata infrastructure such that different organizations, departments, labs, software applications, etc. can maintain their own metadata while standards flow both topdown and bottom-up. The current semantic infrastructure at NCI is not amenable to this type of federated model.

Requirements addressed

• External Data Repositories
• External Data Repositories
• 084 - Localize Metadata Maintenance

Overview of possible operations

Anchor
_16_5_1_24a0131_1283714222603_853936_4108 _16_5_1_24a0131_1283714222603_853936_4108

metadata

Description

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

Requirements addressed

• Service Description Model
• Governance Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283702219069_775824_3210 _16_5_1_24a0131_1283702219069_775824_3210

metrics

Description

Access to metrics information generated or accessible by related services

Requirements addressed

• Service Description Model
• Governance Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283702219071_411273_3211 _16_5_1_24a0131_1283702219071_411273_3211

metricsDiscovery

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

• Service Description Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283702219067_789210_3209 _16_5_1_24a0131_1283702219067_789210_3209

monitor

Description

Access to platform infrastructure monitoring and reporting capabilities.

Requirements addressed

• Service Description Model
• Governance Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283793030699_512571_7056 _16_5_1_24a0131_1283793030699_512571_7056

provenance

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
_16_5_1_24a0131_1283704952697_176583_3341 _16_5_1_24a0131_1283704952697_176583_3341

serviceChangeNotification

Description

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

Requirements addressed

• Service Description Model

Overview of possible operations

Anchor
_16_5_1_24a0131_1283714222609_981432_4109 _16_5_1_24a0131_1283714222609_981432_4109

store

Description

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

Requirements addressed

• Governance Model
• Service Description Model

Overview of possible operations

{scrollbar:icons=false}