Implementation reports

[rubensworks]

(Apologies if this has been discussed during the calls already, I unfortunately missed quite a bit of them)

Does this WG aim to produce implementation reports for each spec to prove the success criterion of "each normative specification is expected to have at least two independent implementations of every feature defined in the specification" as defined in the charter?

I know this was used for the JSON-LD WG: https://w3c.github.io/json-ld-api/reports/

[gkellogg]

It has been my plan to produce implementation reports, similar to how it had been done in the past. My tooling can do this, but we might consider alternatives.

We may also want to associate normative statements with specific tests (and the reverse). I also have some different tooling that does this for manifests, and it may be useful, but is definitely more work. But, it is really useful to know what a given test actually is intended to test, and where to find relevant tests from the spec.

[afs]

Does this WG aim to produce implementation reports

It's a requirement of W3C process to show that there are two independent and interoperable implementations for every feature.

The next step is probably to draw up a list of additional tests needed ; we have some done and we should make sure there are no gaps.

Two wiki pages, for RDF and for SPARQL, maybe?