gkellogg
commented
1 year ago That's great! The implementation report referenced from the recommendations is frozen, as it represents the evidenced used for the Proposed Recommendation transition. Common practice now is to have these reports be updatable, but as the group is not active, there's really no way to change that now.
However, I believe we can update the live version of the report, and update the README to reference that report for more recent submissions. @iherman would probably be the best to verify this, but it seems consistent with the operations of current groups.
In the report, there are instructions for submitting an EARL submission that shows your conformance and provides basic information about the implementation. As this is often hard to get right, it's worth cloning the repository, adding your EARL report (Turtle format recommended) to the tests/reports directory and following the instructions on the README there to generate the consolidated output. You can then create a PR with your report and the results of updating earl.jsonld, earl.ttl, and index.html in that directory. Please reach out if you run into any issues.
We've done some work towards a CSV-W validator called csvw-check which is designed along the lines of csvlint. We've written it with an eye to perfromance as well as providing targetted and descriptive warning and error messages.
It's by no means perfect and isn't correctly validating some smaller parts of the specification (parts we're not currently using), but we believe it passes all of the test definitions.
Would it be possible to have it added on to the list of implementation test subjects and the associated results tables?