- New test suites may be added via a PR request against the rdf-tests repository, or by filing an issue using the issue tracker for subsequent activity.
- Proposed changes to a given test suite may be discussed on email@example.com (archive), but ultimately should result in an issue being created on the issue tracker.
- Changes should either be made on a separate fork of the repository, and integrated via pull request, or on a feature branch within the main repository (prefix branch name with “feature-” or “issue-n-“, where “n” is the issue number relating to the proposed update). Any change that results in a functional change to an existing test suite must be included by consensus of this group, and the related comments group of the associated working group, and should have two implementations which pass the tests. Once consensus is reached, a pull request including this feature branch may be integrated into the main (gh-pages) branch.
Note that naming conventions for tests often make conflicting overlaps inevitable, so consider this when naming new tests and formatting the test manifests.
- Some updates, e.g. more extensive updates to the SPARQL test suite, may require branching off of, and merging back into, a separate feature branch, so that a set of changes can be staged before updating the gh-pages branch.
- 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.
- All changes affecting a given test suite should be broadcast to the appropriate comments list (firstname.lastname@example.org or email@example.com at this point).
- Implementations can typically access a given test suite using the gh-pages view. For example, the Turtle test manifest can be accessed at https://w3c.github.io/rdf-tests/turtle/manifest.ttl. Accessing test suites though an alternative branch via HTTP requires the use of a different facility, such as https://raw.githubusercontent.com/w3c/rdf-tests/gh-pages/turtle/manifest.ttl, where “gh-pages” is replaced by the appropriate branch name.
RDF Test Suite Curation Community Group
Note: Community Groups are proposed and run by the community. Although W3C hosts these conversations, the groups do not necessarily represent the views of the W3C Membership or staff.