W3C

ERT WG

9 Jan 2008

Agenda

See also: IRC log

Attendees

Present
Shadi, Johannes, CarlosV, CarlosI
Regrets
Chair
Shadi
Scribe
CarlosI

Contents


New comments on EARL 1.0 Schema

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

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

SAZ: think we drop heuristic

JK: we need a document that reflects last changes

SAZ: there was a proposal for a InferredTest class
... the decision was that this is something related to test cases not to results

RESOLUTION: ERT WG has considered representing relationships between tests and decided not to implement it at this version as it is something related to test casess and not to results

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

SAZ: next issue about restrictions on properties in the schema
... it must be precisely one constraint per restriction

RESOLUTION: accept the comment about properties restrictions

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

SAZ: next about test summary properties

CV: the summary class is not so straightforward

CI: think the summary is useful but agree is not so straightforward
... We would need a container class
... The interesting thing for me is the grouping, not the summary

RESOLUTION: Comment rejected as summary is associated with aggregation mechanism and the ERT WG has decided not to implement results aggregation on this version

SAZ: following point is about use of dct:hasVersion

http://dublincore.org/documents/dcmi-terms/#hasVersion

<shadi> <rdf:Property rdf:about="http://purl.org/dc/elements/1.1/relation">

<shadi> <rdfs:label xml:lang="en-US">Relation</rdfs:label>

<shadi> <rdfs:comment xml:lang="en-US">A related resource.</rdfs:comment>

<shadi> <dc:description xml:lang="en-US">Recommended best practice is to identify the

<shadi> related resource by means of a string conforming

<shadi> to a formal identification system. </dc:description>

<shadi> <rdfs:isDefinedBy rdf:resource="http://purl.org/dc/elements/1.1/"/>

<shadi> <dcterms:issued>1999-07-02</dcterms:issued>

<shadi> <dcterms:modified>2006-12-04</dcterms:modified>

<shadi> <dc:type rdf:resource="http://dublincore.org/usage/documents/principles/#element"/>

<shadi> <dcterms:hasVersion rdf:resource="http://dublincore.org/usage/terms/history/#relation-005"/>

<shadi> </rdf:Property>

SAZ: it refines dct:relation

JK: definition of hasVersion "The described resource has a version, edition, or adaptation, namely, the referenced resource"
... is the opposite of isVersionOf
... think he is right

SAZ: me too

+1

SAZ: looking for version in previous versions

<shadi> http://www.w3.org/TR/2005/WD-EARL10-Schema-20050909/

SAZ: this is first time version appeared
... accept as is or look at other vocabularies?
... e.g. DOAP
... not sure if there's something in FOAF
... we had stability problems with DOAP before

RESOLUTION: Acknowledgement of the issue and look for an EARL made substitute or something from other vocabularies

Updated "Content-in-RDF"

SAZ: take this back again for the next week

Review of WCAG 2.0

SAZ: worth reading
... not time know, take back again next week

JK: a few editorial comments but nothing really interesting

F2F Planning

SAZ: tentative 20th and 21st February

CI: can't say anything until next week

SAZ: if there are issues about WCAG on mailing list we could meet next week
... otherwise no meeting next week

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.128 (CVS log)
$Date: 2008/01/09 15:37:49 $