W3C home > Mailing lists > Public > www-qa-wg@w3.org > April 2005

Draft Proposed Answer to Ian Hickson: Scope also helps reviewers determine when the specificati...

From: Lynne S. Rosenthal <lynne.rosenthal@nist.gov>
Date: Fri, 29 Apr 2005 08:38:33 -0400
Message-ID: <60DE4C815920CA41AF6CC5CFDA9CC849BBBDB6@WSXG03.campus.nist.gov>
To: "'www-qa-wg@w3.org'" <www-qa-wg@w3.org>
Original comment (issue 1042 [1])

http://lists.w3.org/Archives/Public/www-qa/2005Jan/0007.html
<http://lists.w3.org/Archives/Public/www-qa/2005Jan/0007.html> 

 

Thank you for your comment, which the QA Working Group has accepted.  We
have reworded the affected section as you recommended and it now reads [2]

 

Requirement 02: Define Scope, Why Care.

"This is one of the first sections a reader reads, so it is important to
capture their attention and make sure they understand what the specification
is about. It helps to keep the specification content focused. It helps
reviewers determine when the specification is over-stepping its mandate and
then gives the possibility to revise the specification in development. It
also helps readers know the limits or boundaries of the specification and
whether it is of interest to them."

 

 

[1] http://www.w3.org/Bugs/Public/show_bug.cgi?id=1042
<http://www.w3.org/Bugs/Public/show_bug.cgi?id=1042> 

[2]
http://www.w3.org/TR/2005/WD-qaframe-spec-20050428/#define-scope-principle
<http://www.w3.org/TR/2005/WD-qaframe-spec-20050428/#define-scope-principle>


 
Received on Friday, 29 April 2005 12:38:40 GMT

This archive was generated by hypermail 2.2.0 + w3c-0.30 : Thursday, 9 June 2005 12:13:20 GMT