Priorities for SRI Testing - Next steps

[RichardBruskiewich]

Moving forward past the initial roll-out of the SRI Testing Web Dashboard (14th September 2022 TRAPI 1.4 Relay session), a few big picture tasks for the validation functionality of the SRI Testing harness lie ahead:

• [ ] #58
• Codify (parameterized) validation messages (maintaining a formal dictionary of codes)
• Introduce 'warning' messages, to allow some non-failure modes of reporting of compliance deficiencies (i.e. distinguishing between 'hard' compliance violations with 'would-prefer-to-see' compliance. Possibly add helpful additional 'information' feedback.
  • Revise the SRI Testing MVP Dashboard to display test validation outcomes (messages) in a more user friendly manner.
• [ ] Fresh release of the reasoner-validator with improved validation metrics and structure
  • Including a new "one stop" validator method for complete semantic validation of a single TRAPI Query Response Message.
• [ ] Add full Biolink Model release 3 validation support; iterate on future model releases
• [ ] Secure MongoDb installation.
• [ ] Refine the web service API for new and existing use cases.
• [ ] Refine the TRAPI Testing Web Dashboard.
• [ ] Design and implement a suitable CLI script for (auth/auth secured) administrative - manual and cron job mediated - test run execution.
• [ ] Promote and catalyse ARA and KP integration of test edge data for their resources (i.e. registration of an info.x-trapi.test_data_location property in the Translator SmartAPI Registry, pointing to a valid KP test data or ARA test configuration file).
• [ ] Enhance TRAPI 1.3 schema validation support
• Add validation support for novel qualifiers and constraints in the schema (and perhaps, 1.2 era features not yet fully validated)
• Add validation of TRAPI compliance with Translator workflow documentation
• Add additional non-schema but programmable TRAPI constraint validation
• [ ] Add validation support for TRAPI 1.4 as it evolves (including 'beta' versions, as applicable)
• [ ] Iterative enhancement (from user feedback) of the SRI Testing Web Dashboard
• [ ] Add additional validation use cases (i.e. in the reasoner-validator supporting library) and reporting to the system
• Document participation (or lack thereof) of Translator ARAs and KPs in providing info.x-trapi.test_data_location dereferenced (properly formatted) KP test data or ARA run configuration (JSON) data files.
• Extent of proper implementation of the /meta_knowledge_graph endpoint.
• [ ] Review and resolve internal code quality (i.e. TODO code comments and overall technical debt?)