[techs] examples for techniques requirements document

at today's techniques task force telecon [1] we discussed upcoming agenda 
items and one of them is to update the Requirements for WCAG 2.0 Checklists 
and Techniques  [2, 3].  I thought it would be helpful to look at other w3c 
requirements documents that list outcomes rather than how or what would be 
done to meet the requirements.  By stating outcomes rather than how do 
things, we might be able to simplify our requirements document.

Some examples to look at:
Requirements for EARL 1.0 [4]
XPath Requirements Version 2.0 [5]
Web Services Description Requirements [6]

Best,
--w

[1] <http://www.w3.org/2005/06/22-wai-wcag-minutes.html>
[2] <http://www.w3.org/TR/wcag2-tech-req/>
[3] <http://www.w3.org/WAI/GL/WCAG20/WD-wcag2-tech-req-20050426.html>
[4] <http://www.w3.org/WAI/ER/EARL10/WD-EARL10-Requirements-20050615.html>
[5] <http://www.w3.org/TR/2005/WD-xpath20req-20050603/>
[6] <http://www.w3.org/TR/2002/WD-ws-desc-reqs-20021028/>

-- 
wendy a chisholm
world wide web consortium
web accessibility initiative
http://www.w3.org/WAI/
/-- 

Received on Wednesday, 22 June 2005 16:51:25 UTC