- From: Karl Dubost <karl@w3.org>
- Date: Tue, 3 May 2005 11:35:21 -0400
- To: www-qa@w3.org
- Cc: Ian Hickson <ian@hixie.ch>
Dear Ian, Thanks for your comments on the Last Call version of the QA Framework: Specification Guidelines[0] - 22 November 2004 After two weeks from now (on May 18, 2005), the lack of answer will be considered as if you had accepted the comment. Original comment (issue 1042 [1]) 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.” [0] http://www.w3.org/TR/2004/WD-qaframe-spec-20041122/ [1] 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 -- Karl Dubost QA Working Group Chair http://www.w3.org/QA/WG/
Received on Tuesday, 3 May 2005 15:35:26 UTC