"Normative content is the prescriptive part of the specification, whereas 
informative content is for informational purposes and assists in the 
understanding and use of the specification. Content includes all sorts of 
different forms  not only descriptive prose, but illustrations, examples, 
use cases, formulae and other formalisms. ....
Conformance of implementations is defined by and measured against normative 
content."

I do not think the Rationales are testable; they aid in understanding of 
the specification, and therefore, should be informative, if one follows
the Good Practice C mentioned previously.

Also, it needs to be mentioned explicitly in Section 3 what it means to 
"meet a checkpoint" in Section 3.    I thought it meant satisfying the 
success criteria associated with that checkpoint as prescribed by Section 3 
(passing all the relevant tests associated with that success criteria?)

  Perhaps Section 3 material should be moved to before the Guidelines, 
since it mentions priorities and a reader might want to know this
material before accessing the Guidelines, and conformance is an important 
subject that should be "up front"

*** This bug has been marked as a duplicate of 1009 ***