Page History

...

Dependencies between Semantic Infrastructure 2.0 and caGrid 2.0

...

Refer to the following sections of 6 - Dependencies Between Semantic Infrastructure 2.0 and caGrid 2.0 August 30, 2010 in the caGrid 2.0 Roadmap August 30, 2010:Documents

• Semantic Infrastructure Registry
  • Registry Reliance on Platform
  • Platform Reliance on Registry
• Metamodel and Information Model

Semantic Infrastructure Overview

In an effort similar to developing this roadmap for the future platform, security and tools, a team is defining the future direction for CBIIT Semantic Infrastructure. While the The Semantic Infrastructure Roadmap effort is just beginning, it is expected to be deeply harmonious with the future direction of caGrid. With the adoption of SAIF (Service-Aware Information Framework) and Enterprise Conformance and Compliance Framework (ECCF) and the introduction of behavioral semantics, the infrastructure of the grid must provide increasingly sophisticated support to leverage and enforce these behavioral specifications.

...

The CIM, PIM and PSM are again a collection of artifacts (models). The ECCF matrix is placeholder for these artifacts organized by Reference Model of Open Distributed Processing (RM-ODP) viewpoints and model-drive architecture (MDA) perspectives.

Currently a Microsoft Word document acts as a template or placeholder for describing the
Computation-Independent Mode (CIM), Platform Independent Model (PIM) and Platform Specific Model (PSM) (along with the artifacts of each viewpoint), while the future semantic infrastructure will define computable representation formats for this information.

Part of this computable representation is expected to be a SOA onotology Service-Oriented Architecture (SOA) ontology for describing variations various entities involved in the numerous conformance assertions (with examples including but not limited to services, operations, data types, faults, and actors). This onotology ontology will provide the backbone for reasoning to be performed by the platform and tools at both runtime and design time (as illustrated later in this section).

...

Similarly, the platform will inform the content and format of various platform specific artifacts to be stored in the registry (including but not limited to XML Schema (XSD) and Web Service Definition Language (WSDL)). The platform will provide the capability to enforce or test conformance to those profiles by, for example, checking service interfaces against published PSMs and doing data validation against published information models. Finally, the platform will act as the service implementation technology for the grid services of the registry (that is, be the management interfaces or consumer facing services).

...

Further, such "understanding" of behavioral and static semantics can provide a powerful feature in a tool for workflow or service composition. It could leverage this information to make suggestions on "next steps" in a workflow, even suggesting specific services to use. It could also provide powerful integrity checking of the data flow and functional effect, by validating that the invocations are consistent with published conformance assertions and rules.

At deploy deployment time, the platform (or deployment tools built upon on it) can automate the generation and execution of a test suite to check conformance assertions published in the registry, relevant to the service being deployed.

At run time, the service can provide powerful self-descriptive metadata by referencing profiles, policies, conformance assertions, and specifications in the ECCF registry. This metadata will provide significant details about the nature and behavior of the service, and can be used to discover it, as well as to ascertain programmatically programatically how to correctly consume it (as well as and validate it is functioning correctly). The platform may also be able to automatically flag non-comforming service instances (for example, servces services sending incorrect data, or running outside of published performance metrics) by monitoring runtime behavior.

Metamodel and Information Model

The Semantic Infrastructure 2.0 effort is still deciding on the format and structure to be used. This decision will be important to caGrid 2.0, as it will inform how things like the publishing of service metadata work, and how higher layer semantics (for example, operation preconditions) are built upon static descriptions (for example, WSDL). It is expected, however, that a transition from ISO 11179 metadata to RIM-derived semantics is important in the future infrastructure. As further information is available from both roadmpa efforstroadmap efforts, this section will evolve to discuss the impact on the platform.