Re: Are w3.org/2013/*Tests/ directories in sync with github.com/w3c/rdf-tests/ ?

> On Jan 4, 2016, at 4:08 PM, Rob Stewart <robstewart57@gmail.com> wrote:
> 
> Hi Gregg and Eric,
> 
> Thanks for explaining the current situation about GitHub and apache synchronisation. At the moment, I've got a Makefile in my repository that downloads the .tar.gz files from the apache URL for each RDF format:
> 
> https://github.com/robstewart57/rdf4h <https://github.com/robstewart57/rdf4h>
> 
> My ongoing process has been to periodically use the Makefile to synchronise my repository with the latest W3C RDF parser unit tests. I've come to notice that it's not pulling anything new, despite seeing the GitHub repo receiving commits.
> 
> There's two things I could do:
> 
> 1. Wait for Eric to sort out a post-hook to keep apache in sync with the GitHub repo, and I continue to periodically sync with apache using my Makefile. The down side is that the tests in my repo are only as upto date with the rdf-tests repo as often as I run make then git push the changes.  
> 
> 2. Add https://github.com/w3c/rdf-tests <https://github.com/w3c/rdf-tests> as a git submodule inside my repo. Before running my unit testsuite, I fetch and update the rdf-tests submodule. And I modify my .travis.yml "before_install:" entry to fetch the git submodule before running the testsuite.
> 
> The second approach is perhaps more elegant and a more sensible git workflow, and one I'll probably opt for provided that the rdf-tests is regards as "final" as the apache files are, as opposed to the git repo being treated as an experimental staging area prior to the apache upload.

Personally, I’ve had problems with git sub-modules before in that they get stuck on the commit they’re initialized with, but, in principle, this is probably the way to go. Of course, you can also simply access them over HTTP.

> So going forward, should the git master branch be regarded as official as the .tar.gz files on apache?

The Github gh-pages branch represents the community consensus on RDF and SPARQL tests. We’ll include a tarball of the original tests. I believe the Github API allows you to download arbitrary archive formats, for example:

curl -L https://github.com/w3c/rdf-tests/tarball/gh-pages

My own test scaffolds intercept URL loading by looking for patterns in some local directory and returning them, if they exist, which would be similar to what you might do with a submodule.

Gregg

> --
> Rob 
> 
> 
> On 4 January 2016 at 16:56, Gregg Kellogg <gregg@greggkellogg.net <mailto:gregg@greggkellogg.net>> wrote:
> Eric and I discussed this further yesterday, and came to some different conclusions:
> 
> There is value in reusing the existing test suite URIs; the need to preserve the original state of these test suites is served by keeping a tarball of the original state of the suites.
> 
> There is precedent for updating the implementation reports in place, as this has been done already for Turtle, TriG and a couple of others. They can maintain a reference to the version used for the transition call (although this seems broken in at least one case).
> 
> A post-commit hook can easily be used to synchronize the content of the RDF Test group’s Github repository in W3C spec, thus guarding against some future change that might make it unavailable remotely.
> 
> Eric is going to experiment with this. He’ll create tarballs of the existing directories, which can be added to our Github repo. Once we’re satisfied, the existing test directories and implementation reports can be set to either redirect to the synchronized location, or Apache configuration can be updated to make these appear in the existing locations.
> 
> This can help avoid confusion about what the “official” tests are. A future WG may, of course, change this, but is more likely to create a new location for tests, and certainly implementation reports.
> 
> Gregg Kellogg
> gregg@greggkellogg.net <mailto:gregg@greggkellogg.net>
> 
>> On Jan 3, 2016, at 12:40 PM, Gregg Kellogg <gregg@greggkellogg.net <mailto:gregg@greggkellogg.net>> wrote:
>> 
>> Hi Rob, the group discussed this on RDF Tests [1] and came to the conclusion that leaving the existing tests in place would be better, with a reference to the new tests and implementation reports. Of course, we may revisit this in the future, but the CG has no official standing, and there are no active RDF nor SPARQL working groups.
>> 
>> I prepared alternate landing pages for each of the test suites and implementation reports to refer to the new locations [2][3]. I asked Eric in November to replace the original pages with those referenced, but that obviously hasn’t happened yet. Eric, can we make this happen?
>> 
>> Gregg Kellogg
>> gregg@greggkellogg.net <mailto:gregg@greggkellogg.net>
>>> On Jan 3, 2016, at 3:54 AM, Rob Stewart <robstewart57@gmail.com <mailto:robstewart57@gmail.com>> wrote:
>>> 
>>> Hi,
>>> 
>>> The following URLs are each a pair of W3C RDF parser tests on the w3.org <http://w3.org/> page and the GitHub URL for the corresponding directory. The files in the w3.org <http://w3.org/> directories don't appear to be up to date with the GitHub directories. Is the w3.org <http://w3.org/> directories going to be periodically updated with the GitHub files, or should the w3.org <http://w3.org/> directories be treated as an archive?
>>> 
>>> http://www.w3.org/2013/TurtleTests/ <http://www.w3.org/2013/TurtleTests/>
>>> https://github.com/w3c/rdf-tests/tree/gh-pages/turtle <https://github.com/w3c/rdf-tests/tree/gh-pages/turtle>
>>> 
>>> http://www.w3.org/2013/N-TriplesTests/ <http://www.w3.org/2013/N-TriplesTests/>
>>> https://github.com/w3c/rdf-tests/tree/gh-pages/ntriples <https://github.com/w3c/rdf-tests/tree/gh-pages/ntriples>
>>> 
>>> http://www.w3.org/2013/NQuadsTests/ <http://www.w3.org/2013/NQuadsTests/>
>>> https://github.com/w3c/rdf-tests/tree/gh-pages/nquads <https://github.com/w3c/rdf-tests/tree/gh-pages/nquads>
>>> 
>>> http://www.w3.org/2013/RDFXMLTests/ <http://www.w3.org/2013/RDFXMLTests/>
>>> https://github.com/w3c/rdf-tests/tree/gh-pages/rdf-xml <https://github.com/w3c/rdf-tests/tree/gh-pages/rdf-xml>
>>> 
>>> http://www.w3.org/2013/TriGTests/ <http://www.w3.org/2013/TriGTests/>
>>> https://github.com/w3c/rdf-tests/tree/gh-pages/trig <https://github.com/w3c/rdf-tests/tree/gh-pages/trig>
>>> 
>>> Thanks,
>>> 
>>> --
>>> Rob Stewart
>> 
>> 
>> Gregg Kellogg
>> Chair RDF Test Curation CG
>> 
>> [1] https://lists.w3.org/Archives/Public/public-rdf-tests/2015Nov/0006.html <https://lists.w3.org/Archives/Public/public-rdf-tests/2015Nov/0006.html>
>> [2] https://lists.w3.org/Archives/Public/public-rdf-tests/2015Nov/0016.html <https://lists.w3.org/Archives/Public/public-rdf-tests/2015Nov/0016.html>
>> [3] https://lists.w3.org/Archives/Public/public-rdf-tests/2015Nov/0018.html <https://lists.w3.org/Archives/Public/public-rdf-tests/2015Nov/0018.html>
>> 
> 
>