NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Old Version 3

changes.mady.by.user Unknown User (digret)

Saved on

compared with

New Version 4

changes.mady.by.user Unknown User (digret)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • 5.2.5.3.1 - Discover Sept. 6, 2010 A key function desired by virtually all stakeholders is the ability to query by example using an item from a model or vocabulary (e.g., data element, property, data type, constraint, relation, concept, etc.) to find equivalent and related elements defined anywhere in the knowledge repository. The response should provide an easily understood description of the degree and nature of the semantic convergence between the example item and responsive items.
  • 5.2.5.3.2 - Find Sept. 6, 2010
  • 5.2.5.3.3 - Runtime Contract Discovery Sept. 6, 2010 A powerful query mechanism that allows either the service orchestrator or a program to find the services that best fit the requirements of a given process. This increases both runtime and design time flexibility by enabling selection of services based on computable metadata.
  • 5.2.5.3.4 - Service Generation Sept. 6, 2010 The execution context of a service interaction is the set of infrastructure elements, process entities, policy assertions and agreements that are identified as part of an instantiated service interaction, and thus forms a path between those with needs and those with capabilities. Service generation is the ability to generate services from user defined service metadata. The semantic infrastructure provides this metadata and the platform leverages this metadata for service generation. The constraints and policies specified in the semantic infrastructure are inherited by the platform and are enforced as runtime policiesprovision an execution context from the service descriptions, and associated artifacts, managed by the Semantic Infrastructure.
  • 5.2.5.3.5 - Visualize Sept. 6, 2010 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.

...