Re: Getting Started

I’ve set up the repository [1] with the existing state of a number of different RDF and SPARQL tests. The default branch is gh-pages, viewable at https://w3c.github.io/rdf-tests/. In theory, you should be able to use this as the basis of executing tests by directly accessing a manifest (e.g., <https://w3c.github.io/rdf-tests/turtle/manifest.ttl>).

People should take some time to check this out to see if anything is missing. We can then use this to create issues and discuss updates to these test suites, or add more test suites for curation. Please file issues at https://github.com/w3c/rdf-tests/issues.

The index page points to READMEs, which don’t seem to render in browser. We may want to create index pages for each of the test suites to make this more useful.

Gregg Kellogg
gregg@greggkellogg.net

[1] http://github.com/w3c/rdf-tests/

> On Sep 8, 2015, at 10:55 PM, Gregg Kellogg <gregg@greggkellogg.net> wrote:
> 
> FYI, we’re just getting http://github.com/w3c/rdf-tests set up; once permissions are squared away, I should have an initial commit with the current state of various test suites included.
> 
> For those of you who have just joined, welcome! Below are some guidelines I suggested to get started, with some comments interleaved.
> 
> For more detail, see https://lists.w3.org/Archives/Public/public-rdf-tests/. I also hang out on the “rdf-tests” channel on irc.w3.org. which is generally available to the CG.
> 
> Also, we’re experiencing intermittent mail failures on the W3C mail servers; I’ve sent out some requests to have this addressed, in the meantime, if you re-send, it seems to eventually make it through.
> 
> Gregg Kellogg
> gregg@greggkellogg.net
> 
>> Begin forwarded message:
>> 
>> From: Gregg Kellogg <gregg@greggkellogg.net>
>> Subject: Getting Started
>> Date: September 7, 2015 at 10:10:31 AM PDT
>> To: public-rdf-tests@w3.org
>> 
>> Now that the group is up and has critical mass, I suggest we do the following:
>> 
>> * Create a GitHub repository (ideally on the w3c account) for rdf-tests. (Perhaps Eric can help facilitate this for the w3c account).
>> 
>> * Copy existing tests suites into the gh-pages branch, so that tests can be accessed, e.g., as https://w3c.github.io/rdf-tests/turtle/manifest.ttlfor Turtle, TriG, N-Triples, N-Quads, RDF/XML, SPARQL. (Note, JSON-LD [1] and RDFa [2] test suites are managed in different GitHub repos already.
>> 
>> * Copy implementation reports to, e.g., https://w3c.github.io/rdf-tests/turtle/reports/
>> 
>> * Discussion can take place on this list with specific issues tracked on the GitHub issues tracker.
>> 
>> * Proposed changes should go on a separate branch related to a specific issue issue. Participants should have modify rights to the repo, so that branches off of the main repo are preferred to using a separate fork, but both are reasonable.
> 
> - Ruben suggested prefixing feature branches with "feature-“
> - Rather than merging the feature back to gh-pages, we can use the GitHub Pull Request integration for merging branches back. This is essentially equivalent to the fork/pull-request mechanism people may be more used to.
> 
>> 
>> * Features may be merged back into the main (gh-pages) branch when consensus is reached, which should be validated by at least two separate implementations. Note that naming conventions for tests often make conflicting overlaps inevitable, so we may want to adopt a different naming convention for test IRIs going forward.
> 
> - Of course, consensus from the broader community will also be necessary before new or changed tests are integrated.
> 
>> * Some updates, e.g. more extensive updates to the SPARQL test suite, may require branching off of a separate feature branch, so that  a set of changes can be staged before updating the main branch. We may want to use a “sparql11-rev-1” branch for this purpose.
> 
> - We may want to use a “release-“ prefix for things which are both being developed for release, and the state of the repository at the time of it’s release.
> 
>> * After a changes to a given test suite become stable, a “release” branch can be created to record the state of the test suite at that time; this also becomes the best target for subsequent implementation reports.
>> 
>> * All changes affecting a given test suite should be broadcast to the appropriate comments list (public-rdf-comments@w3.org or public-sparql-dev@w3.org at this point).
>> 
>> Open for discussion is if existing test locations off of w3.org should be redirected or proxied to GitHub, or if new URIs representing these tests (as well as intermediate releases) should be created. I personally favor updating existing test locations, as they are referenced from the specs.
>> 
>> (Note, the mailing list is experiencing intermittent failures; until the W3C webmaster attends to this, retrying emails may be necessary).
>> 
>> Gregg Kellogg
>> gregg@greggkellogg.net
>> 
>> [1] https://github.com/json-ld/json-ld.org/tree/master/test-suite
>> [2] https://github.com/rdfa/rdfa-website/tree/master/tests

Received on Wednesday, 9 September 2015 15:23:26 UTC