W3C home > Mailing lists > Public > public-rdfa-wg@w3.org > December 2010

RDFa 1.1 Test Suite (XHTML, HTML4, HTML5, and SVG)

From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sun, 12 Dec 2010 22:14:52 -0500
Message-ID: <4D058FAC.3030306@digitalbazaar.com>
To: RDFa WG <public-rdfa-wg@w3.org>
I spent most of today dusting off the old RDFa 1.0 Test Suite and
getting it into shape for our push to Candidate Rec for RDFa 1.1 Core
and XHTML+RDFa 1.1. I also got the SVGTiny1.2+RDFa Test Suite started.
Unfortunately, I wasn't able to finish testing the new unit tests
because sparql.org's query service started being flaky.

Updates include:

* 20 new RDFa 1.1-specific tests, TC180-200 (with many thanks to
  Gregg Kellogg for writing these tests)
* Auto-update from github on commits (to speed development of tests)
* Nicer display of test details.
* SVGTiny1.2 + RDFa Test Suite (only has one test right now)
* Different way of classifying tests (required, optional, buggy)
* There is no longer an XHTML+RDFa 1.0 test suite since we had
  decided to make RDFa 1.1 (and presumably all future versions of RDFa)
  version-less. This may be controversial, if so, we can always put
  the old test suite back.
* New development process for unit tests (explained below) - less
  structured, more wild-wild west.

You can view/use the updated test suite here:


The source code for the test suite is in github:


There are instructions on how to add unit tests in the README file:


The new test suite development process is a rather large departure from
the way that we developed the test suite for RDFa 1.1. I would like to
start out by giving the following people direct commit access to the
RDFa test suite (as well as anyone else that will be making active
contributions to the test suite):

Ivan Herman
Toby Inkster
Shane McCarron
Nathan Rixham (already added)
Gregg Kellogg (already added)

That means that if any of the people above make a commit to the test
suite, it will take immediate effect on the live test suite site. This
means that RDFa Processor developers can add tests as they think of them
without waiting for the RDFa WG to approve the tests. If a questionable
test gets added to the Test Suite, and there is disagreement, we can
move its state to "buggy" until we reach consensus. Hopefully, this is
the right balance between providing a mostly stable test suite and
allowing as many people as possible to responsibly improve the test
suite throughout the coming months.

-- manu

Manu Sporny (skype: msporny, twitter: manusporny)
President/CEO - Digital Bazaar, Inc.
blog: Linked Data in JSON
Received on Monday, 13 December 2010 03:15:23 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:05:22 UTC