Maybe need a "linter" for KP (and ARA?) test data files, to validate their format prior to use in testing?

[RichardBruskiewich]

It is a bit challenging for KP test data / ARA configuration JSON files to remain compliant with the evolving standard. Perhaps some kind of 'linter' service would help, conforming to a defined jsonschema.

We'd need to actually formally specify such a schema, then write the code to validate KP test data inputs against it (maybe similar to the TRAPI schema validation...).

Perhaps this can simply be an added endpoint to the regular API, i.e. give the type of component (KP or ARA) and a URL to the test data file, then have the system validate its syntax?