W3C home > Mailing lists > Public > public-wai-ert@w3.org > February 2007

Re: 20060927-conformant RDF?

From: Alan Dean <alan.dean@gmail.com>
Date: Wed, 14 Feb 2007 14:19:38 +0000
Message-ID: <6fb173f50702140619l16e5df11nd9fbca70d7e8f04a@mail.gmail.com>
To: "Shadi Abou-Zahra" <shadi@w3.org>
Cc: public-wai-ert@w3.org


Thank you for your reply. See responses inline below.

> Thanks for your interest in EARL. I'm curious what you would like to use
> it for, and if there is an implementation under development that you may
> be sharing some time in the future. Please find some feedback below.

I want to use EARL to represent assertions upon RESTful web applications.

My implementation will be hosted on thoughpad.net

My intention is to make the final implementation public.

Two resources may provide a clearer picture:
1. My news page at http://thoughtpad.net/who/alan-dean/news/
2. The HTTP activity diagram that represents the set of assertions I
will be targeting -

Please note: I have quite literally just started cutting code, so
there is nothing to exercise as yet.

> Looks good except the assertor class. Firstly, the dc:description
> belongs in the result if it describes the outcome of the test. As you
> have it now, it is not guaranteed to be processed by EARL-compliant parsers.

Updated, see below.

> Secondly and more importantly, you don't specify a test for the
> assertion. You need to specific what are you testing for, and point to
> it using a URI.

Yes, I have been looking at the test-related sections of the spec and
I have to admit that I have found the spec very hard going. My
apologies, but I have found it hard make sense of what has been
written. Below, I did a simple copy & paste of Example 8 at
http://www.w3.org/TR/2006/WD-EARL10-Schema-20060927/#testable and
tweaked it for my sample RDF:

<?xml version="1.0" encoding="UTF-8"?>

  <earl:Software rdf:about="#assertor">
     <dc:title xml:lang="en">Example Application</dc:title>
     <dc:description xml:lang="en">An example testing

  <earl:WebContent rdf:about="#subject">
     <dc:title>Example Web Page</dc:title>
     <dc:date>Sat, 10 Feb 2007 16:04:19 GMT</dc:date>
           <http:responseCode>200 OK</http:responseCode>
           <http:date>Sat, 10 Feb 2007 16:04:19 GMT</http:date>
           <http:last-modified>Tue, 15 Nov 2005 13:24:10
           <http:content-type>text/html; charset=UTF-8</http:content-type>

  <earl:TestCase rdf:ID="testcase">
    <dc:title xml:lang="en">REST Test 1</dc:title>
    <dc:description xml:lang="en">Test 1 of the REST test suite</dc:description>
    <dcterms:isPartOf rdf:resource="http://example.org/tests/rest/"/>

  <earl:Assertion rdf:about="#ok">
     <earl:assertedBy rdf:resource="#assertor" />
rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#automatic" />
     <earl:subject rdf:resource="#subject" />
     <earl:test rdf:resource="http://example.org/tests/rest/#1" />
     <earl:result rdf:parseType="Resource">
        <dc:description>The result was a pass.</dc:description>
rdf:resource="http://www.w3.org/WAI/ER/EARL/nmg-strawman#pass" />

Is this now a conformant document?

Further, I have been trying to understand how I can use
to indicate a non-content location. For example, to indicate that the
location is the HTTP status. Also, I have been unable to deduce how to
represent an assertion of non-existence or null, for example an
assertion that the ETag header should not be present in a response. I
had a look at some WCAG examples, but of course they are only
referring to body content.

Regards and thank you for assisting me,
Alan Dean
Received on Wednesday, 14 February 2007 14:25:55 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:55 UTC