NIH | National Cancer Institute | NCI Wiki  

Error rendering macro 'rw-search'

null

Versions Compared

Old Version 52

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

Saved on

compared with

New Version 53

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

Saved on

Key

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

...

  • 5.2.1 - Artifact Management Sept. 6, 2010 The Semantic Infrastructure supports management, analysis, annotation, publication, query, and transformation of artifacts, including static and dynamic models.
    • 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.2 - Analyze Artifacts Sept. 6, 2010 Analyze Artifacts defines profiles supporting the analysis of artifacts utilizing semantic queries, reasoning, and rules.
    • 5.2.1.3 - Model and Annotate Sept. 6, 2010 Model and Annotate defines profiles supporting models, including model maintenance, constraints, bindings, extensions, and semantic annotations.
    • 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.
  • 5.2.2 - caGRID 2.0 Platform and Terminology Integration Sept. 6, 2010 The Semantic Infrastructure supports seamless integration with the caGRID 2.0 platform.
    • 5.2.2.1 - Export Sept. 6, 2010 Event Processing and Notifications enables monitoring of services in the ecosystem and provides for asynchronous updates by services, effectively allowing a loose coordination of services that both provide and respond to conditions (possibly defined in business rules).
    • 5.2.2.2 - Search and Access Sept. 6, 2010 This group of capabilities 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.
  • 5.2.3 - Case Report Forms Definition and Modeling Sept. 6, 2010 Case Report Forms are the primary channel for capturing information in the healthcare and clinical domain. Forms also play a key role in information exchange and are critical to supporting interoperability in healthcare.
  • 5.2.4 - Conformance Testing Sept. 6, 2010 Services specifications developed by NCI and the community have to be testable to ensure that the implementation conforms to the specification.
    • 5.2.4.1 - Create Conformance Statements Sept. 6, 2010
    • 5.2.4.2 - Search and Access Conformance Statements Sept. 6, 2010 Conformance testing leverages the artifact and service metadata to validate that an implementation adequately addresses the requirements stated in the service specification. An example of service requirement is the ability to specify a response time in the specification (design time) and validate that this response time is valid for an implementation of the service. Additional test points include but are not limited to binding to specific terminologies and domain models.
    • 5.2.4.3 - Test for Conformance Sept. 6, 2010 Testing for SOA combines the typical challenges of software testing and certification with the additional needs of accommodating the distributed nature of the resources, the greater access of a more unbounded consumer population, and the desired flexibility to create new solutions from existing components over which the solution developer has little if any control. The purpose of testing is to demonstrate a required level of reliability, correctness, and effectiveness that enable prospective consumers to have adequate confidence in using a service.
  • 5.2.5 - Service Discovery and Governance Sept. 6, 2010 Service discovery and governance allows service developers to specify rich metadata about services. This enables better discovery, and governance of services.
  • 5.2.6 - Knowledge Engineering, Inference and Reasoning

...