New rationale for checkpoint 3.3

Howdy,
Here's a stab at a new rationale for checkpoint 3.3.
I'm not sure it's perfect but I think it's better or at least clearer 
than what's there now.
Peter


WAS:
Rationale: a profile places requirements on each class of product that 
is affected by the profile's definition. @@@ so ?


FIX:
Rationale: because profiles place explicit requirements on classes of 
products that have specific and often limited operating environments 
these requirements must be defined for each class of product that is 
affected.

Received on Monday, 4 November 2002 13:12:34 UTC