Implementation reports

Where applicable, specifications should link to a document about the implementation reports - a summary/index. In addition to making implementations discoverable via specification, it communicates what could be used with their coverage. It provides supporting data/evidence for success/exit criteria ( https://github.com/solid/specification/issues/373 ) as well as the conformance criteria ( https://github.com/solid/specification/issues/282 ).

The summary/index (in RDF) can be similar to https://www.w3.org/TR/ldn/ linking to https://linkedresearch.org/ldn/tests/summary where individual implementation report (in RDF) can also be found. Where the projects implementing the specifications are also described in RDF... we end up with this (overview): https://csarven.ca/media/images/articles/linked-specifications-reports.svg .

This will generally require the summary/index document to be either updated manually or generated automatically, e.g., based on reports submitted (typically by the maintainer of the project implementing the specification) to a repository or to an inbox - the latter is the approach taken with LDN /ldn/tests/reports/ - and conforming reports are included in the summary.

For the summary and individual implementation reports, we'll need to allocate a URI space (similar to publishing technical reports /TR/{id})

Start by reviewing the linked issues 373 and 282, then compare the LDN summary and individual report examples referenced in the issue. Done would require a decided approach for specification links, RDF summary and implementation reports, report URI space, and whether the index is updated manually or generated from submissions.