List view
* Ensure error reporting for semantic validation is user-friendly * Fully document the system for both end-users and future contributors, ready to publish to ReadTheDocs * Package fully set up and ready for publication to PyPI * Unit test coverage to at least 80%
Overdue by 2 year(s)•Due by October 2, 2023* Finalize evaluation and choice of semantic validation tools (SHACL remains the leading contender as of late May 2023) * Write enough semantic validation rules to add substantial value and show how to add further rules * Basic documentation of adding more rules – enough for interested parties to try it out and give feedback * Increase unit test coverage
Overdue by 2 year(s)•Due by August 28, 2023•0/1 issues closed* Design a user-friendly error reporting format * Integrate error reporting across different validation technologies and libraries * Reduce noise from JSON Schema error reporting as much as possible * Set up proper unit testing with tox and code coverage (40% statement coverage, to be increased in milestones 3 and 4) * Fill in any major gaps in syntax validation – any validation of this sort remaining should be possible to accomplish with easy extensions of existing functionality * Improve user documentation – while not yet being an installable package on PyPI, this milestone should be accessible to most users capable of writing a non-trivial OAS document
Overdue by 2 year(s)•Due by July 17, 2023•3/10 issues closed