- From: Tim Boland <frederick.boland@nist.gov>
- Date: Fri, 26 Aug 2005 09:34:01 -0400
- To: Patrick.Curran@Sun.COM
- Cc: www-qa-wg@w3.org
Thanks for the clarification - I will try to find some additional specific examples for Testcase Metadata [1], to go in the "Example" box for each term, given the broadening of elgibility you mention. In the meantime, here are some additional CSS examples (and one WCAG example) that "very quickly" come to mind, for some of the metadata terms. given the expansion of elegibility.. Thanks and best wishes Tim Boland NIST ------------------------ IDENTIFIER: In the "about the test suites" portion of the CSS test suite site [1], there is URL "formatting" (identification in the URL) information for tests for profiles and modules. ---------------------- DESCRIPTION: The CSS2.1 test suite directory [2] has a "description" column, giving short descriptions of each test. ----------------------- PURPOSE: The CSS Mobile Profile Test Suite [3] has short "purpose" (and "role") statements. The CSS1 Test Suite [8] also has a purpose written as an introduction to the test suite. The Introduction section of the HTML Test Suite for WCAG2.0 document [9] gives an indication of purpose. -------------------------- STATUS: The CSS2.1 test suite directory [2] has a "last updated" column, indicating when the tests were last updated (gives an indication of "status" or "versioning"). NOTE: Does STATUS information relate to VERSION information, particularly given the earlier "versions" of the "same" tests referenced from the CSS test suite site [1] (see information for VERSION following)? The WCAG HTML Test Suite Status Document [4] tracks which specific tests are next to be reviewed, and which specific tests have been rejected and approved. The "Status of This Document" section of the HTML Test Suite for WCAG2.0 document [9] gives an indication of status of the test suite as a whole. ---------------------------- PRECONDITIONS: The CSS test suite documentation Section 4.1 [5] mentions that tests should be able to pass the CSS validator (first pass validator as precondition for then testing CSS feature in the test?). The "prologue" of the CSS1 test suite [6] mentions "configuring your system" to run the CSS1 tests. NOTE: Would information in the prologue also qualify under the "INPUT" term? ----------------------------- INPUTS: The CSS test suite documentation Section 6 [5] lists support files for tests. -------------------------------- VERSION: The CSS test suite site [1] has version information and histories for CSS1 test suite, CSS2.1 test suite, Mobile Profile 1.0 Test Suite, and Selectors Test Suite. -------------------------------- RIGHTS: There is information in the "about the test suites" portion of the CSS test suite site [1] about how test contributors could grant W3C a license for publishing and modification of such tests. --------------------------------------- GROUPING: In the CSS Mobile Profile test suite [3], the "mobile" designation is used in the URL identifier. In the CSS Selectors Profile test suite [7], the "selectors" designation is used in the URL identifier. In the CSS2.1 test suite directory [2], the "CSS2.1" designation is used in the URL identifier. In the CSS1 test suite [8], the "CSS1" designation is used in the URL identifier. These different URL designations provide a filtering mechanism for CSS tests, according to the profile/application? ----------------------------------------- SEEALSO: There is an email list referenced on the CSS test suite site [1], called "public-css-testsuite" to report bugs. ------------------------------------------- [1]: http://www.w3.org/Style/CSS/Test/ [2]: http://www.w3.org/Style/CSS/Test/CSS2.1/current/ [3]: http://www.w3.org/Style/CSS/Test/Mobile/1.0/current/ [4]: http://www.w3.org/WAI/GL/WCAG20/tests/checkstatus.html [5]: http://www.w3.org/Style/CSS/Test/testsuitedocumentation.html [6]: http://www.w3.org/Style/CSS/Test/CSS1/current/sec01.htm [7]: http://www.w3.org/Style/CSS/Test/CSS3/Selectors/current/ [8]: http://www.w3.org/Style/CSS/Test/CSS1/current/ [9]: http://www.w3.org/WAI/GL/WCAG20/tests/
Received on Friday, 26 August 2005 13:34:36 UTC