Re: Requirements for Techniques: Draft 0.2

Here is another round of comments from me.
Michael Cooper writes:
 > 
 > Techniques must be structured in such a way that multiple views can be
 > achieved, including in particular: 
 > 
 > - Checklists
 > 
 > - Test files
 > 
 > - Techniques by conformance level
 > 
 > - Others?
Techniques by technology version and/or implementation status

Unabridged techniques documents (should be inserted after "checklists"
in the above list)
 > 
 > 
 > Techniques should be testable whenever possible and must declare whether
 > they are considered testable. Guidance about testing methods may be
 > provided.
 > 
 > Techniques must [should?] include or link to test cases showing positive and
 > negative implementations of the technique. [This implies the creation of a
 > test suite that exists at a layer below the Techniques layer.]
Some techniques related to the "additional ideas" sections may not be
 > testable, in which circumstances it may not be possible to provide
 > test cases. Perhaps we should say that examples of (positive and,
 > optionally, negative)
 > implementations of the technique must be provided and that if the
 > technique is regarded as testable, these examples must be adequate
 > to serve as test cases.
I wouldn't insist on this change, however, though it does make the
 > requirement a little more precise.