Suggestion: We need to tighten the outcome data format – possibly restricting it to one form. The examples suggested for data-format are not trimmed to only those pieces of the format which are 100% necessary. For example, we likely need the id of the coded test being run, the testing engine name + version, the id of the rule being claimed as supported, the id of the unit test and the outcome from the coded test.

Reason: People are already starting to implement tools which read this outcome format. It would be best to promote a single format ASAP, which of course could be a cut-down form of EARL. You’ll notice, that both Alfa and aXe already report using different structural versions of EARL (and, Deque’s earl context seems different to the earl-act.json context) – with differences in the additional information presented too. Without clarity more variants from more tool developers will follow.