Current Working Draft
This section will provide information about interim development for Semantic Infrastructure 2.0, based on results from the Migration Protoyping project.
The migration strategy for Semantic Infrastructure includes:
- Support for current users of CDEs
- Transforming a set of CDEs to the new Semantic Infrastructure representation
- Determining the process for the transformation
- Determining how many CDEs need to be transformed, including usage and re-use
- Determining whether parts of process can be automated
- Determining the level of effort
- Determining what will the user experience will be, that is, what interfaces community members will use
Semantic Workflow Prototyping (see https://wiki.nci.nih.gov/x/cpIhAg
)
Semantic workflow prototyping includes:
- Defining three specific use cases, and resulting requirements for workflows, for example from:
- Life Sciences
- TCGA (Translational medicine)
- caBIG® Clinical Information Suite
- Defining the metadata and data needed for discovery, composition and execution of a workflow
- Bottom up: from use cases and requirements
- Top Down: In part from Behavioral Framework Metamodel outlined in HL7 SAIF
- Meet in the middle
- Determining the usefulness of World Wide Web Consortium tooling for computational derivation of metadata
- Contract metadata from Web Service Definition Language (WSDL) and Web Application Description Language (WADL)
- Semantic queries
- Prototyping workflows (concentrating on exercising the INFRASTRUCTURE)from the above use cases
- Determining how to discover, assemble services
- Use of tools (for example, high level programming language, Taverna, Business Process Execution Language (BPEL) engine)
Security Prototyping (see https://wiki.nci.nih.gov/x/cJIhAg)
Security Prototyping includes:
- Consideration of aspects of interoperability
- RESTful and SOAP programming models
- Interoperability between Java and .NET technology security services at different institutions
- Working in concert with three other teams:
- Enterprise Security Program at NCI CBIIT
- caBIG® Clinical Information Suite
- MD Anderson
- Develop and Deploy a Security Token Service (STS) with multiple interfaces
- WS- Trust Service: capable of issuing SAML 2.0 Assertions and X.509 Certificates
- SOAP and REST
- Develop and Deploy a secure SOAP Web Service that is secured using tokens from a Security Token Service (STS)
- Leverages WS-Security SAML Token Profile to accept and process SAML 2.0 assertions issued by the STS (Task 1)
- Leverages WS-Security X.509 Token profile to accept and process X.509 credentials issues by the STS (Task 1)
- Develop and Deploy a secure RESTful service that is secured using tokens from a Security Token Service (STS)
- Web Single Sign On (in concert with the Enterprise Security Program at CBIIT): prototype Web SSO solution for facilitating single sign on across web application, SOAP Web services, and RESTful services
Other Inception Phase Activities
The other inception phase activities include:
- Support for specification generation: discussions between Semantic Infrastructure group and SAIF IG group, caBIG® Clinical Information Suite team (see https://wiki.nci.nih.gov/x/LA89Ag)
- Models (UML, OWL) and tools
- DITA Framework and Eclipse Modeling Framework (EMF)
- Determining how to ensure conformance and compliance
- Within a specification stack?
- Of implementations to specifications?
- Further Requirements gathering (see https://wiki.nci.nih.gov/x/GCY9Ag)
- Support for Life Sciences Domain Modeling: How can we ensure timely discovery and deployment in the high change, environment of Life Sciences?
- "Dynamic Extensions"
- Life Science Modeling in new representation.