Re: Test suite skeleton

The Web Platform Test infrastructure is just a fancy name for a GitHub 
repo full of various files (markup and scripts) against which you can 
test clients, notably browsers [1]. The annotation tests, originally 
located in their own GH repo are now duplicated across into the central 
one [2]. We can, and probably should, copy our examples there too, but 
that's once they're all stable and essentially finished. For now we 
should work in our own repo (and I'm not sure whether GH supports 
conneg, which we really should use. If it doesn't, then the tests may 
need to be hosted at

I've also been thinking more about the SHACL issue. If we don't provide 
those, then how will someone test whether their ODRL is valid?

An example of a vocab that has cardinality constraints is the RDF Data 
Cube. For that, the editor created a validator and made it available 
online [3] (although that link is currently broken - I've reported it). 
Others have since created validators. i.e. people have written software.

We can shortcut that development effort by providing the SHACL files and 
pointing people to the SHACL playground.

Although that won't help with the XML serialisations. For that we'd need 
an xsd. Any offers? Ahem - Stuart?



On 10/05/2017 03:19, Renato Iannella wrote:
>> On 9 May 2017, at 17:55, Phil Archer <> wrote:
>> This raises a question: should we include SHACL files for each of the examples?
>> Against:
> +1 for all the Against points.
> The W3C Annotation WG tests: <>
> uses something called "W3C's Web Platform Tests infrastructureā€¯
> What is that? and can we use it?
> R


Phil Archer
Data Strategist, W3C
+44 (0)7887 767755

Received on Wednesday, 10 May 2017 08:42:53 UTC