You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As an open source project that seeks to be trusted as well as trustworthy, maybe this project needs certifaction(s) at least starting with self-certifications.
A clearer sense of possible objectives, near- and further-term, regarding software certification, with Issues planning any work to be done.
Dependencies:
None known.
Acceptance Criteria
This Issue is somewhat open-ended. It can be closed, with comments, when follow-on Issues have been created; it has been superseded for another reason; or other priorities have intervened and the idea is judged not actionable.
The text was updated successfully, but these errors were encountered:
* Metaschema composition XSpecs
* Adding 'a8' prune-unused-definitions filter for comparison (most advanced yet).
* Added new prune filter with slight adjustments to interface; new test for running it standalone
* Removing noisy XSpec result
* More tuning up v9 pruning step for #198
* Cleanup; restoring top-level compose XSLT
* Updating files before merge
* First draft of testing approach with current WIP prune phase transform.
* Fix tests to align with Wendell exception msg check.
* Move pruning tests back to their own folder.
* Refactor test input XML docs into separate files
* Make the tests more reusable across implementations.
* Relocate input files to subdir per convo with @wendellpiez.
* Slight improvement to prototype
* Much cleanup and rearrangement; readme docs
* Updating readme plus entry (shell) XSLT and XProc to current
* Removing obsolete XSpec reports
* Adding .gitignore to exclude XSpec results
* More rearrangement and cleanup; adding step 4 XSpec
* New filter detecting and removing unused definitions passes unit tests
* Removing early copy of remedied step 4 XSLT
* Updating Metaschema Schematron XSpecs to functional state: they are now stable, addressing usnistgov#47
* More adjustments prepping to M4 unit tests - usnistgov#81 #186 #201 - now everything is green or grey (pending) no pink
* Added more clarification to pruning XSpec
* Edits in response to feedback from @aj-stein-nist thanks AJ!
* adding blank lines at end of files
Co-authored-by: Alexander Stein <[email protected]>
Co-authored-by: David Waltermire <[email protected]>
User Story:
As an open source project that seeks to be trusted as well as trustworthy, maybe this project needs certifaction(s) at least starting with self-certifications.
Let's do a research spike on this question, maybe starting with https://www.bestpractices.dev/en
Goals:
A clearer sense of possible objectives, near- and further-term, regarding software certification, with Issues planning any work to be done.
Dependencies:
None known.
Acceptance Criteria
This Issue is somewhat open-ended. It can be closed, with comments, when follow-on Issues have been created; it has been superseded for another reason; or other priorities have intervened and the idea is judged not actionable.
The text was updated successfully, but these errors were encountered: