Re: QASG last call comments: Addition to scope requirement

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Le 19 janv. 2005, à 09:53, Ian Hickson a écrit :
> "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.

Very good point :) the coolness factor effect. Let's add this and that. 
The scope section could be compared with the requirement doc which was 
given at the start (if any)




- -- 
Karl Dubost - http://www.w3.org/People/karl/
W3C Conformance Manager
*** Be Strict To Be Cool ***
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFB/kQK+dmsZnpx3tkRAgzvAKDfpeiKNWGufP3cX9kSFaGohoL2oQCfcH91
EJUBnr6WEGtljYJomuu51u0=
=OKsW
-----END PGP SIGNATURE-----

Received on Monday, 31 January 2005 14:43:23 UTC