Page History

Provide support for Curation Workflow Activities

Gap Analysis::Workflow::

workflowModel,

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::Workflow::

workflowModel,

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::Workflow::

workflowModel,

Use business process workflow tool to automate the process of model submissions( and other related data) to the KR.

Gap Analysis::Workflow::

workflowModel,

Provide workflow component modularization and customization

Gap Analysis::Workflow::

workflowModel,

Application developers need to be able to easily use the infrastructure to create workflows without having to figure out how to integrate the data or services, the infrastructure should step them through it and just ask for things that are not already available

Gap Analysis::Workflow::

workflowModel,

Behavioral dynamic models capture the behavior of services. Behavior of services provides an unambiguous definition of the service constraints, capabilities, dependencies and interactions. The metadata and grammar required to realize service behavior is called behavioral semantics. Behavioral semantics provide a mechanism for better service discovery and enforcing the constraints at design and runtime.

Semantic Infrastructure Requirements::Artifact Management::

workflowModel,

Semantic Profile::OASIS SOA::

monitor from inherited abstract profile Metrics, metrics from inherited abstract profile Metrics, managementInformation from inherited abstract profile Management, managementNotification from inherited abstract profile Management, managementProcesses from inherited abstract profile Management, governanceService from inherited abstract profile Governance, discovery from inherited abstract profile Artifact, identity from inherited abstract profile Artifact, metadata from inherited abstract profile Artifact, store from inherited abstract profile Artifact,

Semantic Profile::OASIS SOA::

discovery from inherited abstract profile Artifact, identity from inherited abstract profile Artifact, metadata from inherited abstract profile Artifact, store from inherited abstract profile Artifact, monitor from inherited abstract profile Metrics, metrics from inherited abstract profile Metrics, metricsDiscovery from inherited abstract profile Metrics, complianceDiscovery from inherited abstract profile Metrics,

This includes predefined templates, workflows, and governance policies for governing the service lifecycle as well as an approval and review process for service specifications and the ability to promote services through the stages of the service lifecycle.

Semantic Infrastructure Requirements::Service Discovery and Governance::

workflowModel,

Service orchestration and choreography allows both application developers and non-developers to discover service "building blocks" that can be composed dynamically to provide business capabilities. Special cases include the orchestration of multiple services for a distributed query, or for a transactional workflow. Service orchestration and choreography will leverage static and behavioral semantics from the Semantic Infrastructure 2.0. The Semantic Infrastructure provides the behavioral semantics required for dynamic composibility of services or generation of distributed queries. This includes runtime contract discovery and negotiation to determine composibility of services based on service capabilities and constraints. Another use case is dynamic retrieval and enforcement of the policies that are in effect for a service interaction in the areas of logging, validations, data transformation, or routing. This information can be used either during the design of the orchestration or during the execution of the defined flow. Link to use case satisfied from caGRID 2.0 Roadmap: Federated query over the TCGA data and other data sets is performed using a service orchestration.

Semantic Infrastructure Requirements::caGRID 2.0 Platform and Terminology Integration::

workflowModel,

Semantic Profile::OASIS SOA::

Service Visibility Model

discovery from inherited abstract profile Artifact,