Re: [techs] examples for techniques requirements document

> 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.

Indeed. We would then be producing a performance spec rather than a design 
spec, to use the terminology. Performance specs are generally preferable.

-- 

     Joe Clark | joeclark@joeclark.org
     Accessibility <http://joeclark.org/access/>
       --This.
       --What's wrong with top-posting?