Decide on the format and schema of the TCK input

The task at hand is to determine the appropriate format and schema for the TCK input. Currently, the format being used is plain text, which contains only the content of the main AsciiDoc document. While this format may suffice for basic testing scenarios, it won't be suitable for testing more complex cases, such as an AsciiDoc document with includes. In such cases, it would be necessary to have an array of files, including their paths and contents.

It may also be useful to include contextual data in the input, such as the TCK version. To facilitate efficient processing of the input and output, it might be a good idea to consider using JSON as the format for the TCK input. This is because JSON is already being used as the output format for the TCK.

Using JSON for the input format also makes sense since we are considering adding a client/server interface (in addition to the existing stdin/stdout interface). JSON is a ubiquitous format in client/server data exchange. I believe that using JSON for the input and output format would make it easier to implement a TCK adapter/server (i.e., it's fairly common to implement a server that consumes JSON and returns JSON).

There are some open questions that need to be addressed when deciding on the format and schema of the TCK input. For instance, should the configuration be included, and should information about the test case (such as test name, test suite, specification reference, etc.) also be included?