Evaluation and Repair Tools Working Group Teleconference

11 Jan 2012


See also: IRC log


Shadi, Christophe, Philip, CarlosV


Status-check on EARL 1.0 drafts

<shadi> http://lists.w3.org/Archives/Public/public-earl10-comments/2011Dec/0000.html

SAZ: There have also been some exchanges on the DOAP mailing list.
... No significant issues from that side.

<shadi> http://www.w3.org/WAI/ER/EARL10/WD-EARL10-Schema-20111205

<shadi> http://www.w3.org/WAI/ER/EARL10/WD-EARL10-Guide-20111205

SAZ: Schema and Guide: new drafts dated 5 December.
... You can recognise the same terms in the Schema and the Guide, but the Guide has more examples, as requested by commenters.
... more context around the schema; the Schema itself should remain short, e.g. to allow people to quickly look up definitions.
... Anyone looked at these drafts?
... Can people have a look at it this week? Schema: changes are mostly editorial. See also the list of issues in the agenda. So you don't need to do a very detailed review.
... Guide has been updated to section 3.2.

<shadi> Guide until section 3.2

SAZ: Guide: look at approach and tone. Look at section 3.1 and 3.2 more for the approach.

Status-check on EARL 1.0 test suites

<shadi> http://www.w3.org/WAI/ER/EARL10/tests/

SAZ: Talked about test suites before the holiday break. See the current list at http://www.w3.org/WAI/ER/EARL10/tests/

<shadi> http://w3c-test.org/framework/

SAZ: Separately, in the WAI-ACT project, we are looking at the accessibility support database and looking to reusing the W3C test framework.
... Fraunhofer team looking at W3C test framework.
... Test framework possibly more geared towards browser-based specs rather than EARL (RDF).
... WG will later need to decide about installing an instance of this framework or another tool.
... Question to participants: look into your respective projects / implementations to see if you have test files that can be submitted.

<shadi> http://www.w3.org/WAI/ER/EARL10/tests/test0003.rdf

SAZ: test 0003 has an error

CS: corrected version available in mailing list archive.

SAZ: developers check that they can output EARL; other tools check if they can consume EARL.
... Feed the tools with different types of input to get different types of output; so, ideally not created by hand.
... some manual tweaking may be necessary, e.g. no reports for existing websites (replace with example.org)
... Timeline?

CV: Most realistic time period is February.

CS: EARL reports can be created right away, but need to check whether all required data are included, e.g. identification of the tool.

SAZ: Some variability is OK; 50 EARL reports that have the same structure is not very interesting.
... Every test file would need to demonstrate a different use of EARL.

CS: Timeline: probably starting middle of next week.

SAZ: Will also contact Kostas for files from the ACCESSIBLE tools.

CV: Vangelis looking into test harness etc. Maybe also applicable here.

<shadi> http://dvcs.w3.org/hg/testframework/

SAZ: Focus should currently be on producing EARL tests rather than finding a tool.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2012/01/17 07:45:20 $