for discussion: earl:Report class

Hi,

Was wondering if others also think an earl:Report class would be useful to have in the Schema. Basically it is mere a container to group assertions that are logically connected. It could have properties to describe the intent and usage of this report. For example:

<earl:Report rdf:ID="someID123">
  <dc:title>Evaluation of example.org</dc:title>
  <dc:description>This report contains the results of the Web accessibility evaluation for example.org done by vendor on date</dc:description>
  <dc:date>dd-mm-yyyy</dc:date>
  <earl:Assertion rdf:resource="assertion1"/>
  <earl:Assertion rdf:resource="assertion2"/>
  <earl:Assertion rdf:resource="assertion3"/>
  ...
</earl:Report>

<earl:Report rdf:ID="someID666">
  <dc:title>Results to be Checked Manually</dc:title>
  <dc:description>Automated results for checkpoints A, B, C that need to be checked by an evaluator</dc:description>
  <dc:date>dd-mm-yyyy</dc:date>
  <earl:Assertion rdf:resource="assertion1"/>
  <earl:Assertion rdf:resource="assertion7"/>
  <earl:Assertion rdf:resource="assertion9"/>
  ...
</earl:Report>


Regards,
  Shadi


-- 
Shadi Abou-Zahra,     Web Accessibility Specialist for Europe 
Chair and Team Contact for the Evaluation and Repair Tools WG 
World Wide Web Consortium (W3C),           http://www.w3.org/ 
Web Accessibility Initiative (WAI),    http://www.w3.org/WAI/ 
WAI-TIES Project,                 http://www.w3.org/WAI/TIES/ 
Evaluation and Repair Tools WG,     http://www.w3.org/WAI/ER/ 
2004, Route des Lucioles -- 06560, Sophia-Antipolis -- France 
Voice: +33(0)4 92 38 50 64           Fax: +33(0)4 92 38 78 22 

Received on Monday, 29 August 2005 09:24:54 UTC