Evaluation and Repair Tools Working Group Teleconference -- 23 Mar 2011

Welcome

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

Updated issues lists

Shadi: fairly elaborate issue list; for each section of the document; some issues still open
... open issues: many of them editorial or fairly simple
... If you have additional issues or comments, please bring them in
... Issues list also contains proposals

CarlosV: How proceed?

Shadi: Taking the most substantial comments first: see agenda.
... This week and next: address most substantial comments. Then go document by document.

CarlosV: not sure if I have latest editor's draft

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

Shadi: http://www.w3.org/WAI/ER/#deliv uses lists all drafts. Any later drafts?

CarlosV: Content & HTTP: not sure?

<shadi> ACTION: SAZ confirm http://www.w3.org/WAI/ER/#deliv has the latest links [recorded in http://www.w3.org/2011/03/23-er-minutes.html#action01]

<trackbot> Sorry, couldn't find user - SAZ

Shadi: Issue with Schema spec: two version: 2006 and 2008. There is also a recorded issue for this. Talked to Johannes before he left; sorted out draft.

CarlosV: Create a redirect from the 2006 version?

Shadi: Could be done; first check what best way is.
... Check the issues list again to see if anything is missing.

EARL 1.0 Schema Software Class

<shadi> http://www.w3.org/WAI/ER/EARL10/issues#Software

<shadi> http://www.w3.org/TR/2009/WD-EARL10-Schema-20091029/#Software

Shadi: some issues related to EARL software class.
... 2nd link: section 2.8: describe software that could be an evaluator ((semi)-automated tool).
... first issue: Dublin Core: dct:hasversion: incorrect use

<shadi> http://trac.usefulinc.com/doap

Shadi: Also: should we be using DOAP to describe software?
... DOAP is another RDF voc to describe software; used by Apache
... got some comments in support of using DOAP. CarlosV, what is your current take?

CarlosV: Use by Apache project. Others: some projects on SourceForge and elsewhere. Some automatic generation. Looks pretty stable.

Shadi: Need to decide if DOAP can be used instead of current Software class. Can it represent what we need, eg title, description.
... Next thing: dependency, as with DC and FOAF, or use our own vocabulary?

CarlosV: Looked at it during last discussions. No changes since 2008, so looks stable.
... No changes in vocabulary since 2009.

Shadi: CarlosV and Philip look at DOAP and work on proposal?

<shadi> ACTION: carlosv and philip to provide a proposal on DOAP class(es) and properties to relpace the current earl:Software class [recorded in http://www.w3.org/2011/03/23-er-minutes.html#action02]

<trackbot> Created ACTION-115 - And philip to provide a proposal on DOAP class(es) and properties to relpace the current earl:Software class [on Carlos A. Velasco - due 2011-03-30].

Kostas: Good to use DOAP.

Conformance (general)

Shadi: Conformance has been ongoing issue.
... We're coming from a very XML-centric approach - syntax and how tools would use/process the syntax.
... However, Semantic Web people look more at vocabulary.
... We keep getting comments from them.
... EARL Schema and HTTP-in-RDF: describing the conformance reqs differently: syntactic and semantic approaches.
... good comments from Dominique H-M and Dan Connolly.
... For example, consider conformance in a separate document. Separate what EARL reports should look like from the vocabulary document.
... That could then be put together in the EARL Guide: describe what we expect from tools that create EARL, from EARL reports, and from tools that process EARL.

CarlosV: The spec should also contain requirements for conformance; Guide is more like a tutorial.

Carlos: Separate note?

Shadi: If we understand Guide as the procedural guidance for tool builders...
... Dom's suggestion was specifically about EARL reports.
... Having conformance outside Voc document. Semantic Web people ... e.g. DOAP: we use only part of it. There would be a continual conflict between our use of DOAP and DOAP itself.

<shadi> http://www.w3.org/TR/2009/WD-EARL10-Schema-20091029/#reports

Shadi: Guide would then mainly be for a11y tool developers about how to use the spec in a useful way.

Philip: Could be good to separate it from the spec itself. (...)

Kostas: We also need to have something about conformance in the spec itself.

Shadi: Taking your example of Assertor and Assertion (each Assertion - one Assertor) : makes sense in our context. Some of the comments we get think outside of the box, outside accessibility evaluation.
... Making the conformance section should be short and refer tool developer to the other document / the Guide.
... Have a careful look at the conformance section and the related issues; see how best to address them. Other suggestions are welcome. Have resolution next time.

<shadi> ACTION: shadi to send an e-mail on the particular issue of conformance, with a suggested resolution, for people to review by next meeting [recorded in http://www.w3.org/2011/03/23-er-minutes.html#action03]

<trackbot> Created ACTION-116 - Send an e-mail on the particular issue of conformance, with a suggested resolution, for people to review by next meeting [on Shadi Abou-Zahra - due 2011-03-30].

HTTP-in-RDF Message Class

<shadi> http://www.w3.org/TR/2009/WD-HTTP-in-RDF10-20091029/#MessageClass

<shadi> http://www.w3.org/WAI/ER/HTTP/issues#MessageClass

Shadi: Some things not very explicit (?) in HTTP
... Two approaches re entity class (not in HTTP protocol): (1) remodel slightly and include entity concept/class; (2) Johannes' proposal to use messageHeader class
... Solution looks simple and effective; not sure what to do wit this.

Johannes' proposal: http://lists.w3.org/Archives/Public/public-wai-ert/2010Mar/0007.html

Shadi: Should be written up a bit more clearly.

CarlosV: entities could be part of header?

Shadi: One of the issues re conformance: every message class needs to have a HTTP property; because of request and response sequences.
... An entity is basically an ... without an HTTP version
... argument to put conformance outside EARL spec.
... Also: just one class for MessageHeader in HTTP voc, but there are different types of headers. Johannes' proposal would break this down into different classes.
... Write up clearer version of Johannes' proposal. Volunteers?

<shadi> ACTION: shadi to write up specific proposal with changes to the HTTP-in-RDF vocabulary to resolve the "Entity" modelling issue [recorded in http://www.w3.org/2011/03/23-er-minutes.html#action04]

<trackbot> Created ACTION-117 - Write up specific proposal with changes to the HTTP-in-RDF vocabulary to resolve the "Entity" modelling issue [on Shadi Abou-Zahra - due 2011-03-30].

<shadi> http://www.w3.org/TR/2009/WD-HTTP-in-RDF10-20091029/#MethodClass

Shadi: 8 methods supported by HTTP 1.1
... one more method has been adopted in RFC 5789: method PATCH

<shadi> http://www.w3.org/2008/http-methods

Shadi: So we need to add this to the RDF.
... should be straightforward change. Accept this?

CarlosV: OK.

Shadi: No objections?

<shadi> RESOLUTION: add PATCH method to the HTTP-in-RDF Method class

<shadi> http://www.w3.org/2008/http-methods

Shadi: someone take action item to add it?

RFC 5789: PATCH Method for HTTP: http://tools.ietf.org/html/rfc5789

<shadi> ACTION: philip to add PATCH description to the http-methods RDF http://www.w3.org/2008/http-methods [recorded in http://www.w3.org/2011/03/23-er-minutes.html#action05]

<trackbot> Created ACTION-118 - Add PATCH description to the http-methods RDF http://www.w3.org/2008/http-methods [on Philip Ackermann - due 2011-03-30].

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

Shadi: You can go to http://www.w3.org/WAI/ER/tracker/ to see the currently open issues and action items.

<shadi> http://www.w3.org/WAI/ER/tracker/actions/open

Upcoming meeting schedule

Shadi: no meeting next week; next meeting on 6 April (consensus)

Meeting closed.

Evaluation and Repair Tools Working Group Teleconference

23 Mar 2011

Attendees