Evaluation and Repair Tools Working Group Teleconference

14 Sep 2011


See also: IRC log


Shadi, Kostas, Christophe, CarlosV
Emmanuelle, Philip, Samuel


Continue processing comments

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

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

CV: Editorial comment?

SAZ: requirements apply to entire EARL package.
... So, yes the requirements appy.
... So: the requirements document is for the entire EARL package, not for each document separately.
... proposed resolution: we reference the requirements document from each of the documents.

RESOLUTION: we will reference the requirements document from each of the specifications.

SAZ: Commenter looking at editor's draft instead of published version?
... HIs follow-up e-mail mentions this... so he's looking at the wrong document.

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

Bug 36

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

RESOLUTION: Fix section numbering in Content in RDF.

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

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

CV: example not clear...

SAZ: (...)
... If you have dynamic content like in his example, you would need to know that as an "evaluator" and record that DOM.
... We need to explain how we meet that requirement.
... If you use EARL in the correct way it enables persistency.
... could add a not in the requirements document saying that you need to EARL in a specific way to enable persistency; it is not automatic.

RESOLUTION: add a note to requirement F03 explaining the limitation and the way in which EARL supports persistency.

SAZ: follow-up email: looking at wrong document, but comment applies

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

SAZ: we discussed this in the past.
... We intended intially to look much more at HTML, but there is a lot of invalidity; you cannot represent HTML except as plain text (or binary) or by extracting the DOM (which would also be XML).
... s you say whether you evaluated based on DOM or based on plain text version.
... we also looked into fuzzy pointers. The invalidity of HTML on the Web did not allow to go further.
... there are so many XML-related things in th spec because of the XML serialisation of RDF, i.e. XML inside XML,

RESOLUTION: explain to commenter that we address HTML as plain text or as XML derived from the DOM. For some multimedia (and any binary content) we use base-64 encoding.

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

CV: would be nice...

SAZ: We get this comment regularly. With a wiki we would have a hard time finding stuff. With a bug tracker it would need to remember who can edit the bugs that someone already submitted. Not a trivial system.
... We use tracker for some of the issues. We also use our own commenting list.
... We hope to have a better system in the future.

RESOLUTION: Explain to the commenter the current bug tracking procedure that we use and that we are aware of the issue and hope to have a better system in the future.

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

RESOLUTION: comment accepted (editorial)

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

RESOLUTION: comment accepted.

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

RESOLUTION: comment accepted (missing # in source code).

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

CV: problem with the request.

<shadi> http://xmlns.com/foaf/spec/#term_member

<shadi> http://xmlns.com/foaf/0.1/member redirects to http://xmlns.com/foaf/spec/

CV: First URI goes to foaf:member; second one goes to FOAF spec

<shadi> http://xmlns.com/foaf/spec/member is a 404

<shadi> http://xmlns.com/foaf/spec/#member does not exist

<shadi> <rdf:Property rdf:about="http://xmlns.com/foaf/0.1/member" vs:term_status="stable" rdfs:label="member" rdfs:comment="Indicates a member of a Group">

SAZ: correct URI is http://xmlns.com/foaf/spec/#term_member . In the RDF we have http://xmlns.com/foaf/0.1/member
... Seems to be a bug on the FOAF side.

<shadi> <rdfs:subPropertyOf rdf:resource="http://xmlns.com/foaf/spec/#term_member"/>

<shadi> http://www.w3.org/ns/earl

<shadi> should be: <rdfs:subPropertyOf rdf:resource="http://xmlns.com/foaf/0.1/member"/>

KV: in the EARL: ...#term-member : OK. (...)

<shadi> ...but use isDefinedBy="http://xmlns.com/foaf/spec/#term_member

KV: Maybe we should correct it.

SAZ: Two different things: in the RDF schema, for isDefinedBy we can point into the spec ...

<carlosV> http://xmlns.com/foaf/spec/index.rdf

CV: may need to add a comment that we use http://xmlns.com/foaf/spec/index.rdf

RESOLUTION: to fix the ID in the EARL RDF schema and add a comment about the FOAF version we use

Upcoming meeting schedule

SAZ: we meet again in 3 weeks.

KV: anyone going to Poland?

SAZ: Then next meeting would be on 12 October?
... possibly list of proposals in two weeks (tentative)
... 28 September is tentative. Some follow-up questions, maybe.
... In the 1,5 weeks, we would need to review the proposed changes.
... 5 October is also tentative.

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

SAZ: please look at your action items.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2011/09/14 13:42:04 $