This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 1042 - Scope also helps reviewers determine when the specification is over-stepping its mandate
Summary: Scope also helps reviewers determine when the specification is over-stepping ...
Status: RESOLVED REMIND
Alias: None
Product: QA
Classification: Unclassified
Component: QASpec-GL (show other bugs)
Version: LC-2004-11-22
Hardware: All All
: P2 minor
Target Milestone: ---
Assignee: Karl Dubost
QA Contact: Karl Dubost
URL: http://lists.w3.org/Archives/Public/w...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-21 09:38 UTC by Dominique Hazael-Massieux
Modified: 2005-04-28 11:53 UTC (History)
0 users

See Also:

Attachments

Description Dominique Hazael-Massieux 2005-01-21 09:38:41 UTC 
"2.1 Requirement A: Define the scope" -- another good reason to define
the scope is it helps reviewers determine when the specification is
over-stepping its mandate. Sometimes a specification veers away from
its original goals and scope; on occasion this is due to evolving
goals and thus the scope needs to be updated, but sometimes it is
because the working group has strayed outside the boundaries of what
the specification should be addressing, and the spec itself needs
revising instead.
Comment 1 Dominique Hazael-Massieux 2005-03-04 02:12:47 UTC 
The WG agrees and will add the suggestion to the relevant section (resolved at
F2F in Boston, Mar 3rd PM)
Comment 2 Dominique Hazael-Massieux 2005-04-28 11:53:50 UTC 
setting version to LC in case of future use