Provide a test suite for the SEP

[Tpt]

The SEP are currently "text-only". It might be nice to provide some test case with them to provide examples and compare the first implementations.

About the structure, the the setup done for the rdf-star CG might be reuse and adapted with one manifest per SEP.

[Tpt]

If considered useful I am willing to take some time to setup this work and write some tests for the existing SEPs (but if existing implementations like Kineo or Jena want to provide their tests it would be even better).

[kasei]

For SEP-0002, I linked to tests for the proposed functions in a fork of the sparql-12 repo.

[afs]

Yes!

There are links Apache Jena's tests at the end of 0006 and they are test manifest driven.

I'm happy to put a copy in sparql-12 and be under the W3C Software Notice and License which is open source. As the author I can provide them direct, and with a different license to Jena.

(The W3C Document Licence used for specifications is a different license.)

[JervenBolleman]

Would it be good to have a default test directory per SEP? e.g. as I am trying to demonstrate in kasei#2

[Tpt]

@JervenBolleman That sounds great! Or maybe a directory for each SEP in a global tests directory. Thank you!

[Tpt]

I have opened #180 with some tests for SEP 0004. I believe a global shared tests directory is better because it allows tests to be close to the test tooling (HTML generation). On the tooling side, we might reuse the one from the rdf-star CG by @gkellogg

[gkellogg]

Recently, we’ve discussed some reorganization of the SPARQL portion of the rdf-tests repo, and I recall the sparql-12 tests might just be added (hopefully, after reconsidering the naming to sparql-dev). Bifurcated test suites become a problem to keep track of. Adding or reusing some attribute to associate sep tests would be useful for provisioning runs.