 |
Page History
| Scrollbar |
|---|
| Page info | ||||
|---|---|---|---|---|
|
ECCF Registry Description
The semantic infrastructure inception team is planning to create demos and prototypes to refine the requirements and solicit additional input from the community.
Scope and Objectives
The primary objective of the ECCF registry is to demonstrate how the registry can address the artifact management and service discovery/governance requirements. The prototype will identify all the key capabilities; realize a core set of functions in the registry prototype as services and develop a User Interface to demonstrate these capabilities to all the stakeholders. The prototyping team will work with caEHR as a pilot customer; and use the caEHR artifacts and specifications for all the demonstrations.
...
The goal of this exercise is not create fully functional software but to demonstrate a working prototype that realizes a subset of the requirements that require further clarification and refinement.
Capability Description
The periodic table in the architecture section provides a quick summary of the key capabilities that will be demonstrated in the prototype, the prototype will not demonstrate all usage scenarios/functions of these capabilities. The goal of the prototype is to demonstrate a subset of functions within each capability. The following is a high-level summary of those capabilities.
- Storage and Retrieval of Models in different formats
- Model Transformation
- Artifact Metadata authoring
- Artifact lifecycle management
- Establish equivalence and dependency between artifacts
- Binding to terminology
- Service Governance
- Service Metadata authoring
- Integration with platform and forms authoring tools
- Ability to constrain models and value-sets (the registry is not a model authoring tool, but provides very limited editing capabilities)
- Artifact validation for consistency and conformance
- Support for conformance statements
Requirements Addressed
The prototype addresses all the artifact management, service discovery/governance and caGRID platform 2.0 requirements listed in section 4.
...
Conformance testing prototypes will also be developed to leverage the metadata to generate tests that validate services/artifacts for conformance. This activity is expected to be very limited in scope and will be closely coordinated with the platform team. The testing framework will be primarily developed by the platform team as framework is expected to test services deployed on the caGRID 2.0 platform.
Community Feedback and comments
TBD based on feedback and comments on the first draft and the prototype/demo.
Lessons learned
TBD based on feedback and comments on the first draft and the prototype/demo.
