See also: IRC log
<shadi> [round table introductions]
<shadi> http://lists.w3.org/Archives/Public/public-earl10-comments/2011May/0014.html
Philip: naming conflict to object earl:Assertor?
Shadi: rdf theoretically make difference between
lowercase and uppercase, but practically there could be problems
... best practices would be something like "earl:has....."
CarlosV: don't have any preference
... most consistent approch: use lowercase
Christophe: I would not rename it
<kostas> i would like to keep it as it is
RESOLUTION: Keep the property name as it is
Shadi: anybody think we should look at other property names?
<shadi> assertedBy
<shadi> subject
<shadi> test
<shadi> result
<shadi> mode
<shadi> mainAssertor
<shadi> outcome
<shadi> pointer
<shadi> info
<shadi> http://lists.w3.org/Archives/Public/public-earl10-comments/2011May/0015.html
<carlosV> no revisit
Shadi: we did not find a vocabulary that describe
Software for our purpose
... just one sentence in the schema and more examples in the guide
<kostas> the idea of including more examples it could be nice
<shadi> ACTION: shadi to follow-up with Ed Dumbill about software class for DOAP [recorded in http://www.w3.org/2011/07/27-er-minutes.html#action01]
<trackbot> Created ACTION-129 - Follow-up with Ed Dumbill about software class for DOAP [on Shadi Abou-Zahra - due 2011-08-03].
Kostas: examples in the guide would be ok
CarlosV: we need to clarify that
RESOLUTION: add one or two sentences to the schema document and some more examples and explanations to the EARL guide
<shadi> http://lists.w3.org/Archives/Public/public-earl10-comments/2011May/0016.html
<shadi> http://www.w3.org/TR/EARL10/#OutcomeValue
Shadi: OutcomeValue class has related instances
that could be used
... OutcomeValue class has also different subclasses
... same approach for TestSubject
... maybe add a sentence to clarify what "in addition" means
... again more examples in the guide
... second part of question will be discussed later
RESOLUTION: add one or two explaining sentences to the schema document and again more examples and explanations to the guide
Shadi: (1) would meet the conformance
requirement, (2) would not
... (3) would be a refinement of (1)
... conformance requirement says "testsubject has to be of type
TestSubject"
... (3) is ok as long as TestSubject and Software are not disjoint
RESOLUTION: add more explanations to the EARL guide
<shadi> http://lists.w3.org/Archives/Public/public-earl10-comments/2011May/0017.html
Shadi: conflict between schema and guide, because guide is out of date
RESOLUTION: accept comments and update EARL guide
<shadi> http://www.w3.org/WAI/ER/timeline
Shadi: publish candidate recommendation in
september
... most comments are editorial
Christophe: We would like to release the first version of the accessibility checker next month
Shadi: would that version implement EARL?
Christophe: yes, but EARL reports are only internal
Shadi: changes to EARL would mean changes to the tool
<kostas> Shadi i cannot partcipate on 10th of August
<samuelm> * lost connectivity
<carlosV> ... banana (Groucho)
Shadi: web based survey for review and
comments
... ...by maybe tuesday next week