Initial thoughts on EARL Requirements document

All:

I've attached a draft of the EARL 1.0 Requirements Document with 
modifications to resolve the actions assigned to Shadi at the F2F on 
11/05/2009.

http://www.w3.org/2008/11/06-er-minutes.html

I also made minor edits for correcting typographical and grammatical 
problems. Notice that this file has been renamed to 
EARL10-requirements_mas.html.


More substantive comments/questions follow, which we can discuss on 
tomorrow's call:

0. In the F2F minutes there is the following:

RESOLUTION: need to split between overall requirements for the "evaluation 
and reporting framework", and requirements for the EARL 1.0 Schema 
document itself

Is the requirements document not meant to address the entire EARL 1.0 
document suite (EARL 1.0 Schema, Pointers in RDF, Representing Content in 
RDF, HTTP in RDF, EARL 1.0 Guide)? If so, why the need for a "split?" This 
question was always in the back of my mind as I read through the document 
and should be clarified in the introduction.

1. In Abstract, what does the last sentence, ""It will also provide 
reusable vocabulary for generic Web
quality assurance and validation purposes," mean? Is it meant as an 
example of the previous sentence, as a way that EARL might be used?

2. S02-S03 might be read as limiting us to the web. is that what we want? 
Is there room for an additional requirement about the generic nature of 
the test subject?

3. Removed "computational" from D03 but do we need to have "in a 
reasonable time?"

4. F03 concerning persistency and F04 concerning aggregation need work and 
are mentioned in the minutes with no particular resolution.

--> Mike Squillace
IBM Human Ability and Accessibility Center

W:512.286.8694
M:512.970.0066

External: http://www.ibm.com/able
Internal: http://w3.ibm.com/able