On Oct 29, 2019, at 2:30 PM, Gregg Kellogg <gregg@greggkellogg.net> wrote: > >> On Oct 29, 2019, at 2:07 PM, Andy Seaborne <andy@apache.org <mailto:andy@apache.org>> wrote: >> >> I have always been pleasantly surprised by the high level of interoperability in SPARQL implements when compared to other technologies. Yes, there are differences but users genuinely expect interoperability because general that is their experience. >> >> Expectations are high - test suites have been very effective with the distributed working and with http://w3c.github.io/rdf-tests/ <http://w3c.github.io/rdf-tests/> continue to evolve. > > Tests are quite useful, and my practice has always been to develop tests alongside the spec, which is how JSON-LD has evolved. > > To that end, it might be useful to create a new category, or test options in https://github.com/w3c/rdf-tests <https://github.com/w3c/rdf-tests> (perhaps /sparql12bis, or similar), or duplicate that test infrastructure into https://github.com/w3c/sparql-12/tests <https://github.com/w3c/sparql-12/tests>, where people could submit their proposed tests to go along with proposals. It would be useful to flesh-out the corners of different proposals. Of course, it’s better if the feature has been implemented someplace first. +1 I’d be very happy to see proposed 1.2 tests integrated in some way in the rdf-tests repo. I had previously constructed a set of proposed tests for #32 (xsd operators for durations/dates/times) and committed them to a fork of the sparql-12 repo: https://github.com/kasei/sparql-12/tree/xsd_datetime_duration/tests/xsd_functions <https://github.com/kasei/sparql-12/tree/xsd_datetime_duration/tests/xsd_functions> but it would make it easier to use with existing SPARQL test harnesses if it were integrated directly in rdf-tests. Thanks, Greg
Received on Tuesday, 29 October 2019 22:28:58 UTC