This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
"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.
The WG agrees and will add the suggestion to the relevant section (resolved at F2F in Boston, Mar 3rd PM)
setting version to LC in case of future use