Re: [tap] W3C Evaluation and Report Language (EARL)

[Ovid <[e-mail]>]

Hi Christophe,

Thanks for dropping us a note.

Just from glancing through the EARL specs, it appears that there is some overlap, but the two are not congruent. A TAP producer would have a difficult time producing the requisite output for a few reasons.

1. You produce output we don't support natively in a TAP stream.
2. RDF documents are, well, documents, not streams.

We're working on a proposal which could address some of point #1, but as TAP allows for infinite streams (for example, repeatedly pinging a server to see that it's responsive), I don't think an infinite stream wouldn't be well-represented in a documented-oriented protocol.

As a side note, from glancing at http://trac.usefulinc.com/doap/wiki/ProjectGoals:

* We don't support "suspend[ing] more zombies in the row".
* I'm uncertain how you plan to extend the vocabulary for http://hepburnspringsaccommodation.webs.com
* Zombies are actually made of tasty, tasty spam (we eat them and before they eat us)

You might want someone to take a look at that page and clean up the spam :)

Cheers,
Ovid
--
Live and work overseas - http://overseas-exile.blogspot.com/
Buy the book           - http://www.oreilly.com/catalog/perlhks/
Tech blog              - http://blogs.perl.org/users/ovid/
Twitter                - http://twitter.com/OvidPerl/


>________________________________
>From: Christophe Strobbe <[e-mail]>
>To: [e-mail]
>Cc: Shadi Abou-Zahra <[e-mail]>
>Sent: Wednesday, 9 November 2011, 14:23
>Subject: [tap] W3C Evaluation and Report Language (EARL)
>
>Hello,
>
>I am a participant of the W3C's Evaluation and Repair Tools Working Group (ERT WG), a working group that develops the Evaluation and Report Language (EARL) and a few related specifications. EARL's core use case is reporting the results of accessibility evaluations of websites (i.e. accessibility for persons with disabilities), but the language itself is generic, so it can also be used in other contexts. The language is based on RDF; the specification is available at <http://www.w3.org/TR/EARL10/>.
>
>During our last call for comments, one of the reviewers asked the working group if EARL duplicates TAP's efforts, or vice versa. The working group thinks that this is not the case; we think that EARL could be an alternative report format for TAP if a TAP consumer could be written that produces EARL. For this reason, we thought it would be interesting to contact you and to make sure we are aware of each other's work.
>
>Shadi Abou-Zahra, in CC, is the working group's chair and W3C staff contact.
>
>Best regards,
>
>Christophe
>
>
>-- Christophe Strobbe
>K.U.Leuven - Dept. of Electrical Engineering - SCD
>Research Group on Document Architectures
>Kasteelpark Arenberg 10 bus 2442
>B-3001 Leuven-Heverlee
>BELGIUM
>tel: [phone]
>http://www.docarch.be/
>Twitter: @RabelaisA11y
>---
>Open source for accessibility: results from the AEGIS project www.aegis-project.eu
>---
>Please don't invite me to Facebook, Quechup or other "social networks". You may have agreed to their "privacy policy", but I haven't.
>
>_______________________________________________
>tap mailing list
>[e-mail]
>https://www.ietf.org/mailman/listinfo/tap
>
>
>