Closed afs closed 3 years ago
I tried to provide manifest-X.jsonld files but the existing Turtle example "tests/turtle/manifest.jsonld" does not work for me. I guess because of relative URIs in the worker manifests.
This PR include the trig in #147 which has other manifest changes. I'll come back to the JSONLD when that's in.
Note, we still have a single implementation report that reports on all tests, both SPARQL and concrete syntax. And the tests/index.html combines all the tests together.
Personally, I think this is appropriate, as the spec lists a single test suite and a single implementation report.
The logic for make-jsonld-manifests needs a slight tweak to generate the JSON-LD versions of these manifests, which I can do as a commit to this PR.
I rebased due to some conflicts.
Now we have some experience of the implementation reports process, is this still work doing?
Maybe it's better to have just the per-directory manifests - less duplication, maintenance.
In practice, I have not been running from any of the top-level manifest*
files.
We need the top-level HTML index, but that's built by hand. We could remove the manifest files in /tests, otherwise, but we should probably have them in sparql/, turtle/, and trig/ directories if we remove the top-level.
Rebased. Removed intermediate manifest-lang andmanifest-sparql. Ready to merge.
In reports/index.html, separate the links to Turtle and JSON-LD so they don't run together (second use).
Separate manifests for language and sparql tests (convenience for people who have different tools to run tests).