Include older SPARQL tests in newer manifests

[erdemonal]

Fixes #307

[rubensworks]

I believe the tests are intentionally separated like this to be able to run test manifests for each SPARQL version independently.

[afs]

Having worked with the RDF tests with included style, I prefer them separate. It means the 1.2 test responses reflect the state just of 1.2 features.

As we gather implementation reports this will be more convenient. Once the implementation report phase is over, then maybe combine them.

[lisp]

if the issue is that a test is superseded or obsoleted, it would be better that have a protocol whereby a test with the same identifier in a later manifest can modify the approval status of an the earlier test to be withdrawn or obsoleted.
i see nothing in https://www.w3.org/2001/sw/DataAccess/tests/README.html in that regard.
that could be changed.

[afs]

if the issue is that a test is superseded or obsoleted, it would be better that have a protocol whereby a test with the same identifier in a later manifest can modify the approval status of an the earlier test to be withdrawn or obsoleted. i see nothing in https://www.w3.org/2001/sw/DataAccess/tests/README.html in that regard. that could be changed.

No - it's not the issue.

An SPARQL 1.2 must pass SPARQL 1.0 and 1.1 tests - indeed the tests here wre updated for RDF 1.1 changes around xsd:string.

1.2 tests are tests for features not in 1.1 or, sometimes, clarification tests. They are not replacements.

[lisp]

if it is the case that, once 1.1 test had been corrected, any "SPARQL 1.2 must pass SPARQL 1.0 and 1.1 tests", then there is no reason to make this change.

[kasei]

As we gather implementation reports this will be more convenient. Once the implementation report phase is over, then maybe combine them.

I think a better approach might be to have a "top"-level sparql/manifest.ttl that just mf:included the version-specific manifests. This would leave intact the ability to run the version-specific tests if desired.