ERT WG

Review the plan for publishing EARL 1.0 Guide

carlosV: still waiting for review/comments
... new draft will be ready by next tuesday

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

shadi: i see a lot of the issues are in the RDF/XML itself. looks like we need to simplify a bit

<scribe> ACTION: CarlosV to reissue next draft version of EARL 1.0 guide [recorded in http://www.w3.org/2007/07/04-er-minutes.html#action01]

<scribe> ACTION: CarlosV to send comment on content section of EARL 1.0 Schema [recorded in http://www.w3.org/2007/07/04-er-minutes.html#action02]

Review the plan for publishing Pointer Methods in RDF

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2007Jul/0004.html

<scribe> ACTION: Shadi to check with CarlosI on preparing proposal for next week [recorded in http://www.w3.org/2007/07/04-er-minutes.html#action03]

Check-in on vacation plans and summer availability

drooks: im away for last week of July (21st - 29th)

shadi: no meeting for last week of july
... otherwise, regular meetings throughout summer
... hoping to get EARL schema and HTTP RDF out soon
... may need another last call draft for earl schema
... lets aim for big publication towards end of august

POWDER Use Cases and Requirements

shadi: we need to send comments by end of this week

johannesK: i have nothing much to comment about

shadi: we've had lots of discussion between POWDER and ERT to align the groups

<scribe> ACTION: JohannesK to send any comments he has to POWDER WG by end of week [recorded in http://www.w3.org/2007/07/04-er-minutes.html#action04]

EARL 1.0 Schema: Test Mode

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

<shadi> http://lists.w3.org/Archives/Public/public-wai-ert/2007Jul/0000

shadi: we've reviewd ATAG 2.0 WD and sent comments regarding test mode (semi automated testing)
... we agreed semi automated testing is when the decision is mainly done by the tool with minimal human interaction
... got in contact with ATAG group about aligning our view with ATAG's
... EARL:huristic appears to be misleading name or it should be property of result

<shadi> earl:semiAutomatic

<shadi> Where a software tool WAS ABLE TO IDENTIFY POTENTIAL PROBLEM INSTANCES,

<shadi> BUT WHERE HUMAN judgment WAS STILL REQUIRED TO DECIDE OR HELP TO DECIDE

<shadi> WHETHER AN ACTUAL PROBLEM EXISTS. This should be additionally noted

<shadi> through the earl:compoundAssertor class of the Assertor.

johannesK: in semi-automated the tool should primarily be responsible for making the decision

shadi: non-automated = manual
... manual the more acceptable term
... we need to invite ATAG to next weeks call

<shadi> earl:heuristic

<shadi> This property was designed to cover assertions which are made by

<shadi> inference, for example based on several existing test results.

shadi: this term is throwing off a lot of people
... propose we rename it to inferred or drop it entirely

EARL: inferred makes more sense

johannesK: EARL:inferred a much better name than heuristic

proposal: rename EARL:heuristic to EARL:inferred and think about putting it elsewhere

RESOLUTION: rename EARL:heuristic to EARL:inferred and think about putting it elsewhere

shadi: do we all think notavailable is not a very good name?

i think notavailable is pretty concise

shadi: how do we define it when the test mode is not known

carlosV: how about unknown

how about notProvided

or notSupplied

<scribe> ACTION: Shadi to collect ideas for renaming EARL:notAvailable [recorded in http://www.w3.org/2007/07/04-er-minutes.html#action05]

<scribe> ACTION: Shadi to invite Jan Richards to next teleconf [recorded in http://www.w3.org/2007/07/04-er-minutes.html#action06]