W3C home > Mailing lists > Public > public-grddl-wg@w3.org > March 2007

Manifest suggestion (was Re: Test document draft)

From: Jeremy Carroll <jjc@hpl.hp.com>
Date: Wed, 14 Mar 2007 13:49:24 +0000
Message-ID: <45F7FD64.4050407@hpl.hp.com>
To: Chimezie Ogbuji <ogbujic@bio.ri.ccf.org>
CC: public-grddl-wg <public-grddl-wg@w3.org>


I think the easiest extension is to add a single class, a GRDDLTest, as 
follows:


   <rdfs:Class rdf:ID="GRDDLTest">
     <rdfs:label xml:lang="en">GRDDL Test</rdfs:label>
     <rdfs:comment xml:lang="en">These tests consist of one input 
document, and one or more output documents. The test is passed if 
processing of the input document results in an RDF graph that is 
isomorphic to the RDF graph formed by reading any one of the output 
documents. When reading an output document, the base URI should be set 
to the URI of the input document. Each test may also include supporting 
documents, such as profiles and transforms, which are required during 
execution of the test.</rdfs:comment>
     <rdfs:isDefinedBy rdf:resource="#"/>
   </rdfs:Class>


The supporting documents can be defined simply using test:document, but 
better maybe:


   <rdf:Property rdf:ID="supportingDocument">
     <rdfs:label xml:lang="en">Supporting Document</rdfs:label>
     <rdfs:comment xml:lang="en">A test case document needed during the 
execution of a test, while being neither an input nor an output 
document.</rdfs:comment>
     <rdfs:isDefinedBy rdf:resource=""/>
   </rdf:Property>
Received on Wednesday, 14 March 2007 13:49:45 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:11:48 GMT