- From: Sandro Hawke <sandro@w3.org>
- Date: Wed, 19 Apr 2017 21:01:29 -0400
- To: "public-data-shapes-wg@w3.org" <public-data-shapes-wg@w3.org>
The answer is that if we're able to delineate a safe subset of SPARQL
for use in SPARQL-based Constraints, that would not require restarting
the CR clock. I'll be very interested to see if we end up with
consensus that that's technically feasible (eg that Peter agrees the
subset is safe).
Meanwhile, the test results [1] for core/* look amazing. Very close
to CR-exit for Core right now. It would be good to understand why we
have no-data on two, and what's going on with the failed Netage tests,
but still it looks good.
The test results for sparql/* are more modest. Do we know the stories
here? Holger, are the failing TopBraid tests ones you don't think
should be in the test suite for some reason? ("shared" we discussed;
pre-binding/minus sounds like one you want to exclude from the language;
not sure about pre-binding/bind.) Do other folks plan to implement the
sparql stuff? If we're not sure, that's another reason to try to
separate sections 5 & 6 into a different document.
Where are we on positive and negative syntax tests being in the suite &
reporting?
-- Sandro
[1]
http://w3c.github.io/data-shapes/data-shapes-test-suite/#validate-rdf-data-tests
Received on Thursday, 20 April 2017 01:01:36 UTC