W3C home > Mailing lists > Public > w3c-wai-er-ig@w3.org > October 2001

Re: Where does the EARL go?

From: Sean B. Palmer <sean@mysterylights.com>
Date: Fri, 19 Oct 2001 20:18:02 +0100
Message-ID: <047501c158d2$e0c88a60$7ce793c3@y0r1d9>
To: "Jim Ley" <jim@jibbering.com>
Cc: <w3c-wai-er-ig@w3.org>
> How does that work with a web site, a unique earl report
> for each url on the site, how does that work with urls with
> query portions?

No, you don't have to have a "unique EARL report" for every URL on the
site, as we've just been discussing!

> How can EARL exist unless this has already been decided,
> how EARL is used is much more important than what the
> tags look like.  I'm astonished by this thread.

"Than what the tags look like"? Your reply is a little incoherant here, but
mine was also badly phrased. EARL just offers the framework for giving the
context, the subject of the test, validity, and metadata for the test case.
The way in which these are represented is flexible, of course, to allow for
a wide range of evaluations to be carried out. We are only just coming to
specific implementations, and are finding that we need to pin down the
scenarios, detailing ever smaller parts of the EARL framework.

We're by no means finished yet, and the current version of the framework is
only a beta 0.95. If you're astonished by this thread, then I submit that
it is because you have done little competent research, and/or are missing
the point entirely.

> > For now, all EARL is going to be served as text/plain
> > or text/xml, so just leave the "type" attribute off. It's
> > only advisory.
> Why is EARL served as text/plain - why do you feel it
> should not have a mime-type, [incredible length sentence
> snipped]

EARL can be served as text/plain because EARL is based on RDF, and RDF is
often served as text/plain, or text/xml depending upon the serialization.
This is something that is dictated wholly by RDF, and is not under our
control: we must use whatever MIME type is mandated by the Semantic Web
activity for RDF, and as there is little current agreement about it at the
moment, we simply follow developer practice, which as I say, is to serve as
text/plain or text/xml. If you have a problem with that (and it is a valid
problem), I suggest you take it up on RDF IG, but it is a thread which
comes up every so often, and on which little progress is ever made.

> > People tend to ignore that, sadly.
> If it's as little thought out as EARL seems to be, I'm
> not surprised.

At least EARL seems to be a little better thought out than your
delightfully condescending reply :-) As Wendy pointed out, please let's be
constructive here. We've been working on EARL for many months now, and you
have had plenty of time with which to send feedback.


Kindest Regards,
Sean B. Palmer
@prefix : <http://webns.net/roughterms/> .
:Sean :hasHomepage <http://purl.org/net/sbp/> .
Received on Friday, 19 October 2001 15:19:02 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:01:33 UTC