W3C

Evaluation and Repair Tools Working Group Teleconference

04 May 2011

Agenda

See also: IRC log

Attendees

Present
Shadi, Philip, Kostas
Regrets
CarlosV, Christophe, Emmanuelle
Chair
Shadi
Scribe
Kostas

Contents


[EARL 1.0 Schema] final review, decision on publication

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2011Apr/0044

shadi: EARL Schema there were some bug fixes
... maybe add an introduction sentence in all the documents it could be a good idea (for explaining the conformance text)

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

<shadi> "The Developer Guide for Evaluation and Report Language (EARL) 1.0 explains how to implement and use EARL, including conformance requirements for software tools. An Evaluation and Report Language (EARL) Overview is also available."

shadi: included the sentence:The Developer Guide for Evaluation and Report Language (EARL) 1.0 explains how to implement and use EARL, including conformance requirements for software tools. in the introduction part of the EARL schema

kostas: aggree

philip_: aggree

RESOLUTION: publish the document as a last working draft

[HTTP-in-RDF] final review, decision on publication

<shadi> http://www.w3.org/WAI/ER/HTTP/WD-HTTP-in-RDF10-20110502

shadi: philip and Carlos have been done a lot of work in order to update the document

<philip_> Perhaps "This document is part of the W3C Evaluation And Report Language (EARL) but can be reused in other contexts too. When used in the EARL context, please refer to the Developer Guide for Evaluation and Report Language (EARL) 1.0 explains how to implement and use EARL, including conformance requirements for software tools."

<shadi> This specification is part of the Evaluation And Report Language (EARL) but can be reused in other contexts too.

shadi: we need sth more expanded in the introduction section

<shadi> "This document is part of the W3C Evaluation And Report Language (EARL) but can be reused in other contexts too. A Developer Guide for Evaluation and Report Language (EARL) 1.0 explains how to implement and use EARL, including conformance requirements for software tools."

shadi: maybe it is better to include sth like philip_ suggestion in the introduction part of alla documents

kostas: it is fine

philip_: it is ok

RESOLUTION: publish the document as an updated working draft

[Content-in-RDF] final review, decision on publication

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2011May/0001

shadi: also the same with other documents - add one paragraph to the introduction section
... no other changes

RESOLUTION: publish the document as an updated working draft

[Pointers-in-RDF] final review, decision on publication

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2011Apr/0043

shadi: in the namespaces section we have to allign the namespaces tabular

RESOLUTION: publish the document as an updated working draft

[Developer Guide] final review, decision on publication

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2011May/0012

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

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

shadi: in section 2.3 limitation are very minimal
... section 3 to be revised editorialy
... section 4 has been rewritten from scratch
... all requirements have been simplified and included
... will be published as a working draft

and we need more time for further review and improvement for this document

RESOLUTION: publish the document as an updated working draft

Upcoming meeting schedule

<shadi> http://www.w3.org/WAI/ER/timeline#meeting

SHADI: document to be published early next week
... to follow the publication rules for the publication of all the documents
... 25th of May could be the deadline for further improvement

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.133 (CVS log)
$Date: 2011/05/04 16:17:38 $