NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

  • Created by Unknown User (digret), last modified by Unknown User (wileyal) on Oct 01, 2010

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 35 Next »

The Semantic Infrastructure supports management, analysis, annotation, publication, query, and transformation of artifacts, including static and dynamic models.

Managed artifacts include:

  • Static Models
  • Dynamic Models
  • Unstructured documents, images, and other content
  • Clinical forms
  • Service specifications
  • Metadata for all managed artifacts

Artifact management primarily deals with managing artifact lifecycle and authoring of artifact metadata.

The Semantic Infrastructure is a Service-Oriented Architecture (SOA), a system of services. Within SOA, 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. In short, a service description artifact is an interlinked set of documents (that is, artifacts), which ultimately encompasses all artifacts of interest in the Semantic Infrastructure..

A service description, and consequently the artifacts it includes, have a number of architecture implications for artifacts managed by the Semantic Infrastructure:

Description will change over time and its contents will reflect changing needs and context. This requires the existence of:

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

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 requires the existence of:

  • 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;
  • mechanisms to support the storage, referencing, and access to these semantic models;
  • 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;
  • 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.

Descriptions include references to metrics which describe the operational characteristics of the subjects being described. This requires the existence of:

  • the infrastructure monitoring and reporting information on SOA resources;
  • possible interface requirements to make accessible metrics information generated or most easily accessed by the service itself;
  • mechanisms to catalog and enable discovery of which metrics are available for a described resources and information on how these metrics can be accessed;
  • mechanisms to catalog and enable discovery of compliance records associated with policies and contracts that are based on these metrics.

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 requires the existence of:

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

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 requires the existence of:

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

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 requires the existence of:

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

Functional Profile Group

  • 5.2.1.1 - Administer Artifacts Sept. 6, 2010 Artifact lifecycle management defines profiles to manage the lifecycle, governance, provenance, versioning, and representation of artifacts, as well as the relationships between artifacts.
    • 5.2.1.1.1 - Governance Sept. 6, 2010 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.
    • 5.2.1.1.2 - Load Sept. 6, 2010 Load any new artifact, through multiple interfaces
    • 5.2.1.1.3 - Manage Sept. 6, 2010 Determine provenance, jurisdiction, authority and intellectual property.
    • 5.2.1.1.4 - Register Sept. 6, 2010 Mediated awareness promotes loose coupling by keeping the consumers and services from explicitly referring to each other and the descriptions. Mediation lets interaction vary independently. Rather than all potential service consumers being informed on a continual basis about all services, there is a known or agreed upon facility or location that houses the service description. A common mechanism for mediated awareness is a registry-repository.
    • 5.2.1.1.5 - Version Sept. 6, 2010 The Semantic Infrastructure keeps track of each version, any relevant provenance information (e.g., who made the change), and supports the concept of being able to revert to any prior state. This version control would include the authoring of any new metadata (making contexts more explicit) and the assertions of model alignments.
  • 5.2.1.2 - Analyze Artifacts Sept. 6, 2010 Analyze Artifacts defines profiles supporting the analysis of artifacts utilizing semantic queries, reasoning, rules, and data mediation.
    • 5.2.1.2.1 - Analysis Sept. 6, 2010 Information and behavioral models, in conjunction with discovery mechanisms, mediation, classification, traceability from requirement to operation, and interaction logs, enable comprehensive analysis to be performed through-out the life-cycle of artifacts , from design through run-time implementation.
    • 5.2.1.2.2 - Reasoning Sept. 6, 2010 The semantic models managed by the Semantic Infrastructure enable enhanced reasoning.
    • 5.2.1.2.3 - Rules Sept. 6, 2010 A Rule is a prescribed guide for carrying out activities and processes leading to desired results, e.g. the operational realization of policies. A Regulation is a mandated process or the specific details that derive from the interpretation of Rules and lead to measureable quantities against which compliance can be measured. Policy is made operational through the promulgating and implementing of Rules and Regulations
  • 5.2.1.3 - Model and Annotate Sept. 6, 2010 The Model and Annotate category defines profiles supporting models, and includes capabilities related to model maintenance, constraints, bindings, extensions, and semantic annotations.
    • 5.2.1.3.1 - Bind Models Sept. 6, 2010 An artifact description associates a resource with normative definitions of value specifiers. A value specifier includes a collection of value sets. A value set is defined in terms of its structure and semantics. A property-value pair construct binds an artifact description to the semantics of a value set within a given execution context.
    • 5.2.1.3.2 - Constrain Sept. 6, 2010 A policy represents some constraint or condition on the use, deployment or description of a resource as defined by a participant or, more generally, a stakeholder. A contract is a constraint that has the agreement of the constrained participants. A policy constraint is a measurable proposition that characterizes the constraint that the policy is about. A permission constraint governs the ability of a participant or other actor to perform an action or enter some specified state. An obligation constraint governs the requirement that a participant must perform some action or maintain some state.
    • 5.2.1.3.3 - Extend Sept. 6, 2010 A policy represents some constraint or condition on the use, deployment or description of a resource as defined by a participant or, more generally, a stakeholder. A permission constraint governs the ability of a participant or other actor to perform an action or enter some specified state. The ability to extend a service specification, including any associated model artifact, is subject to the permission policies embodied in the contract between the participants.
    • 5.2.1.3.4 - Model Sept. 6, 2010 Create, destroy, edit, and maintain models.
    • 5.2.1.3.5 - Semantic Annotation Sept. 6, 2010 In a diverse information environment, semantics must be used to clearly indicate the meaning of data. This requirement is expected to be addressed by the Semantic Infrastructure, although there will be a touchpoint between the caGrid 2.0 and the Semantic Infrastructure to annotate data with semantics.
  • 5.2.1.4 - Publish Sept. 6, 2010 The ability to publish and discover information models will be supported by the semantic infrastructure, and the platform will leverage these capabilities.
  • 5.2.1.5 - Search and Access Sept. 6, 2010 The Semantic Infrastructure enables integrated access, search, and visualization of artifacts using a variety of search criteria, model serialization formats, and user interaction empowerment tools.
  • 5.2.1.6 - Transform Sept. 6, 2010 Transform defines profiles for management and application of transformations to support multiple views, serialization formats, inter-operability, semantic convergence, model migration, model merge and compare, and provisioning of target artifacts.
  • No labels