<h1>Preface</h1>
<p>This document contains the test specification for the WAP June 2001 release of the:
</p>
<dl>
<dt><b>WAP Cascading Style Sheets</b></dt>
<dd>version WAP-236-WAESpec-20011109-a.pdf</dd>
<dd>version WAP-237-WAEMT-20010515-d.pdf</dd>
</dl>
<p>
This document contains the test specification for the WAP June 2001 release of the Wireless Application Environment specification version 2.0(WAP-236-WAESpec-20011109-a.pdf).
The specification is organized such that there is a section for each
WAP CSS Extension of the WAG CSS specification in which assertions can be found. For each assertion, a corresponding entry in this test specification contains the following elements:
<dl>
<dt><b>ID:</b></dt>
<dd>The name by which the test is known.</dd>
<dt><b>Class:</b></dt>
<dd>An assertion Class as defined in IEEE Std 1003.3. These types are:
<dl>
<dt><b>A</b></dt>
<dd>A mandatory, testable assertion.</dd>
<dt><b>B</b></dt>
<dd>A mandatory, but untestable assertion.</dd>
<dt><b>C</b></dt>
<dd>An optional, testable assertion.</dd>
<dt><b>D</b></dt>
<dd>An optional, but untestable assertion.</dd>
</dl>
</dd>
<dt><b>Scope:</b></dt>
<dd>If an assertion is type C or D, this entry describes the option that needs
to be supported in order to activate the test.</dd>
<dt><b>Text:</b></dt>
<dd>The text of the assertion and a reference to
the source specification from which the assertion is derived.</dd>
<dt><b>Note:</b></dt>
<dd>Any supplementary information associated with the assertion. For 
example, it may suggest a strategy for the test implementation of the 
assertion or it may propose rationale as to why a test is classified as 
untestable.</dd>
</dl>
<p>

