- From: Shadi Abou-Zahra <shadi@w3.org>
- Date: Mon, 25 Sep 2006 10:40:56 +0200
- To: public-wai-ert@w3.org
Dear Group, During last weeks' teleconference we briefly discussed refining the cardinality constrains on the properties of the assertion class (by defining appropriate min/maxCardinality restriction). There are currently two proposals as follows: PROPOSAL 1: * exactly 1 assertedBy property per assertion class * exactly 1 subject property per assertion class * exactly 1 test property per assertion class * exactly 1 result property per assertion class * at most 1 mode property per assertion class PROPOSAL 2: * exactly 1 assertedBy property per assertion class * at least 1 subject property per assertion class * at least 1 test property per assertion class * exactly 1 result property per assertion class * at most 1 mode property per assertion class The advantage of proposal 1 is that it is simple, crisp, and clear. The advantage of proposal 2 is that it allows for slightly more compact reports (for example when different tests are run by the same tool, and all tests share the same result). However, this comes at the price of slightly more complex reports and overhead for the parsers (as well as potential ambiguity). During this weeks' teleconference we should take a decision on these proposals. Please send your comments to the list by then. Regards, Shadi -- Shadi Abou-Zahra Web Accessibility Specialist for Europe | Chair & Staff 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, 25 September 2006 08:41:06 UTC