NIH | National Cancer Institute | NCI Wiki  

Contents of this Page
Summary
Description of the profile

Given the complexity of the models in use, and the large number, users are constantly confronted with the problem of trying to gain an understanding of new domains not familiar to them. Visualizations of models and vocabularies are perceived as essential to this task. The requirement is to provide visualizations that are easy to navigate, that identify the contact points between models and between vocabularies and that allow users to seamlessly move from model constructs to data.

The Visualize Profile derives its capabilities from Information and Behavior Models, and consequently specializes capabilities architecturally implied by the concept of Information Model and Behavior Model..

Visualize specializes capabilities architecturally implied by its associated concepts of Artifact , Behavior Model , Change , Information Model , Semantic Model . The implied architectural capabilities are described in the following paragraphs.

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

Behavior Model A well-defined service Behavior Model.

The capabilities of the Behavior Model include:

  • characterizes the knowledge of the actions invokes against the service and events that report real world effects as a result of those actions;
  • characterizes the temporal relationships and temporal properties of actions and events associated in a service interaction;
  • describe activities involved in a workflow activity that represents a unit of work;
  • describes the role(s) that a role player performs in a service-oriented business process or service-oriented business collaboration;
  • is both human readable and machine processable;
  • is referenceable from the Service Description artifact.

Change Artifact descriptions change over time and their contents will reflect changing needs and context.

Architectural implications of change on the Semantic Infrastructure are reflected in the following capabilities:

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

Information Model A well-defined service Information Model.

The capabilities of the Information Model include:

  • describes the syntax and semantics of the messages used to denote actions and events;
  • describes the syntax and semantics of the data payload(s) contained within messages;
  • documents exception conditions in the event of faults due to network outages, improper message/data formats, etc.;
  • is both human readable and machine processable
  • is referenceable from the Service Description artifact.

Semantic Model Artifact Descriptions make use of defined semantics, where the semantics may be used for categorization or providing other property and value information for description classes.

Architectural implications of semantics on the Semantic Infrastructure are reflected in the following capabilities:

  • 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. This is a refinement of the Artifact metadata capability.
  • mechanisms to support the storage, referencing, and access to these semantic models. This is a refinement of the Artifact store capability.
  • 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. This is a refinement of the Change configurationManagement capability.
  • 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.
Capabilities
Requirements traceability

Requirement

Source

Capability

Provide a means to visualize the models that have been loaded into the KR. The UML Model Browser displays the granular details of a model in list format, but there isn't away to visualize and navigate the whole model. The grid portal provides this feature from the metadata, there should be a way to do this when viewing models in the KR. This would enhance a potential new user’s ability to determine if they can use all or part of a model.

Gap Analysis::Visualize::038 - Visualize and navigate whole models

modelBrowser

The ability to navigate, search, order, group (predefined & ad-hoc), and compare data element definitions, associations, and code lists is a requirement for defining CDISC standards.   In the CDISC SHARE (Shared Health and Research Electronic Library) Pilot it was very difficult to navigate/search/compare definitions; the semantic Wiki did not provide good tooling for these capabilities.  There was no ability to display, order, and align any code sets or their associations with data elements.  KR Searching capabilities should include ad hoc views, pre-defined views, wild card, and synonym searches, ignore word stems, the exclusion of some results, and the ability to search/view hierarchies.  Other search capabilities include control over which objects to search, the ability to view results and data element display by source or other criteria. In addition, the LED displays did not provide enough visual real-estate.   This includes the display of horizontal and vertical data structures.  A big CDISC problem is that most standards developers are content experts and not information modelers or IT experts.  Generally, they are volunteers who meet once a week.  They also have a few content curators, technical data modelers as well as technical experts.  An easy-to-use asynchronous collaboration environment is central to the success of their CDISC standards work. *Source:  * * 5/20/2010 Interview, David Iberson-Hurst * CDISC Share Pilot Report and CDISC Requirements Package 1 - NCI Semantic Infrastructure, 5/28/2010, Section 2.1 & Section 2.2, Section 2.3

Gap Analysis::CDISC::CDISC-6 -  Provide enhanced visualization, browsing and search tools

CDISC-06

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. SOA governance requires numerous architectural capabilities on the Semantic Infrastructure: Governance is expressed through policies and assumes multiple use of focused policy modules that can be employed across many common circumstances This is elaborated in the inherited Policy profile. Governance requires that the participants understand the intent of governance, the structures created to define and implement governance, and the processes to be followed to make governance operational. This is provided by capabilities specialized from the inherited Management Profile. Governance policies are made operational through rules and regulations. This is provided by the following capabilities, most of which are specializations of the inherited Artifact Profile: * descriptions to enable the rules and regulations to be visible, where the description includes a unique identifier and a sufficient, and preferably a machine process-able, representation of the meaning of terms used to describe the rules and regulations; * one or more discovery mechanisms that enable searching for rules and regulations that may apply to situations corresponding to the search criteria specified by the service participant; where the discovery mechanism will have access to the individual descriptions of rules and regulations, possibly through some repository mechanism; * accessible storage of rules and regulations and their respective descriptions, so service participants can understand and prepare for compliance, as defined. * SOA services to access automated implementations of the Governance Processes. Governance implies management to define and enforce rules and regulations.. This is elaborated in the inherited Management profile. Governance relies on metrics to define and measure compliance. This is elaborated in the inherited Metric profile.

Semantic Profile::OASIS SOA::Governance Model

discovery from inherited abstract profile Artifactidentity from inherited abstract profile Artifactmetadata from inherited abstract profile Artifactstore from inherited abstract profile Artifact

Interaction is the activity involved in using a service to access capability in order to achieve a particular desired real world effect, where real world effect is the actual result of using a service. An interaction can be characterized by a sequence of actions. Consequently, interacting with a service, i.e. performing actions against the service--usually mediated by a series of message exchanges--involves actions performed by the service. Different modes of interaction are possible such as modifying the shared state of a resource. Note that a participant (or agent acting on behalf of the participant) can be the sender of a message, the receiver of a message, or both. Interacting with Services has the following architectural implications on mechanisms that facilitate service interaction: A well-defined service Information Model, as elaborated in the inherited Information Model profile. A well-defined service Behavior Model, as elaborated in the inherited Behavior Model profile. Service composition mechanisms to support orchestration of service-oriented business processes and choreography of service-oriented business collaborations, as elaborated in the inherited Service Composition profile. Infrastructure services that provides mechanisms to support service interaction, as elaborated in the inherited Interaction profile. A layered and tiered service component architecture that supports multiple message exchange patterns (MEPs)l, as elaborated in the inherited Message Exchange profile.

Semantic Profile::OASIS SOA::Interacting with Services Model

message from inherited abstract profile Information Modelpayload from inherited abstract profile Information Modelexception from inherited abstract profile Information ModelserviceBinding from inherited abstract profile Information ModeldiagramModelBinding from inherited abstract profile Information ModeldiagramModelBinding from inherited abstract profile Behavior ModelserviceBinding from inherited abstract profile Behavior Modelaction from inherited abstract profile Behavior Modeltemporal from inherited abstract profile Behavior Modelworkflow from inherited abstract profile Behavior Modelparticipant from inherited abstract profile Behavior Model

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. A service description artifact may be a single document or it may be an interlinked set of documents. Architectural implications of service description on the Semantic Infrastructure are reflected in the following functional decomposition: * Description will change over time and its contents will reflect changing needs and context. This is elaborated in the inherited Change profile. * 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 is elaborated in the inherited Semantic Model profile. * Descriptions include reference to policies defining conditions of use and optionally contracts representing agreement on policies and other conditions. This is elaborated in the inherited Policy profile. * Descriptions include references to metrics which describe the operational characteristics of the subjects being described. This is elaborated in the inherited Metrics profile. * 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 is elaborated in the inherited Interaction profile. * 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 is elaborated in the inherited Composition 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. This is elaborated in the inherited Interoperability profile. Policy capabilities are specialization of Artifact capabilities.

Semantic Profile::OASIS SOA::Service Description Model

versioning from inherited abstract profile ChangeconfigurationManagement from inherited abstract profile Changetransition from inherited abstract profile Changediscovery from inherited abstract profile Artifactidentity from inherited abstract profile Artifactmetadata from inherited abstract profile Artifactstore from inherited abstract profile ArtifactsemanticConversion from inherited abstract profile Semantic Model

One of the key requirements for participants interacting with each other in the context of a SOA is achieving visibility: before services can interoperate, the participants have to be visible to each other using whatever means are appropriate. The Reference Model analyzes visibility in terms of awareness, willingness, and reachability. Visibility in a SOA ecosystem has the following architectural implications on mechanisms providing support for awareness, willingness, and reachability: Mechanisms providing support for awareness will likely have the following minimum capabilities: * creation of Description, preferably conforming to a standard Description format and structure; * publishing of Description directly to a consumer or through a third party mediator; * discovery of Description, preferably conforming to a standard for Description discovery; * notification of Description updates or notification of the addition of new and relevant Descriptions; * classification of Description elements according to standardized classification schemes. In a SOA ecosystem with complex social structures, awareness may be provided for specific communities of interest. The architectural mechanisms for providing awareness to communities of interest will require support for: * policies that allow dynamic formation of communities of interest; * trust that awareness can be provided for and only for specific communities of interest, the bases of which is typically built on keying and encryption technology. The architectural mechanisms for determining willingness to interact will require support for: * verification of identity and credentials of the provider and/or consumer; * access to and understanding of description; * inspection of functionality and capabilities; * inspection of policies and/or contracts. The architectural mechanisms for establishing reachability will require support for: * the location or address of an endpoint; * verification and use of a service interface by means of a communication protocol; * determination of presence with an endpoint which may only be determined at the point interaction but may be further aided by the use of a presence protocol for which the endpoints actively participate.

Semantic Profile::OASIS SOA::Service Visibility Model

discovery from inherited abstract profile Artifact

action
Description

characterizes the knowledge of the actions invokes against the service and events that report real world effects as a result of those actions;

Requirements addressed
Overview of possible operations
CDISC-06
Description

Provide enhanced visualization, browsing and search tools.

Requirements addressed
Overview of possible operations
configurationManagement
Description

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.

Requirements addressed
Overview of possible operations
diagramModelBinding
Description

Is both human readable and machine processable.

Requirements addressed
Overview of possible operations
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
Overview of possible operations
exception
Description

Documents exception conditions in the event of faults due to network outages, improper message/data formats, etc.

Requirements addressed
Overview of possible operations
identity
Description

Descriptions which include a unique identifier for the artifact.

Requirements addressed
Overview of possible operations
message
Description

Describes the syntax and semantics of the messages used to denote actions and events

Requirements addressed
Overview of possible operations
metadata
Description

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

Requirements addressed
Overview of possible operations
modelBrowser
Description

Provide a means to visualize the models that have been loaded into the KR. The UML Model Browser displays the granular details of a model in list format, but there isn't away to visualize and navigate the whole model. The grid portal provides this feature from the metadata, there should be a way to do this when viewing models in the KR. This would enhance a potential new user’s ability to determine if they can use all or part of a model.

Requirements addressed
Overview of possible operations
participant
Description

describes the role(s) that a role player performs in a service-oriented business process or service-oriented business collaboration;

Requirements addressed
Overview of possible operations
payload
Description

Describes the syntax and semantics of the data payload(s) contained within messages

Requirements addressed
Overview of possible operations
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
semanticConversion
Description

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.

Requirements addressed
Overview of possible operations
serviceBinding
Description

Is referenceable from the Service Description artifact.

Requirements addressed
Overview of possible operations
store
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
temporal
Description

characterizes the temporal relationships and temporal properties of actions and events associated in a service interaction;

Requirements addressed
Overview of possible operations
transition
Description

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.

Requirements addressed
Overview of possible operations
versioning
Description

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.

Requirements addressed
Overview of possible operations
workflow
Description

describe activities involved in a workflow activity that represents a unit of work;

Requirements addressed
Overview of possible operations
  • No labels