|
| 1 | +</main> |
| 2 | +<h2 id="conformance" class="no-ref no-num"> |
| 3 | +Conformance</h2> |
| 4 | + |
| 5 | +<h3 id="conventions" class="no-ref"> |
| 6 | +Document conventions</h3> |
| 7 | + |
| 8 | + <p>Conformance requirements are expressed with a combination of |
| 9 | + descriptive assertions and RFC 2119 terminology. The key words “MUST”, |
| 10 | + “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, |
| 11 | + “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this |
| 12 | + document are to be interpreted as described in RFC 2119. |
| 13 | + However, for readability, these words do not appear in all uppercase |
| 14 | + letters in this specification. |
| 15 | + |
| 16 | + <p>All of the text of this specification is normative except sections |
| 17 | + explicitly marked as non-normative, examples, and notes. [[!RFC2119]]</p> |
| 18 | + |
| 19 | + <p>Examples in this specification are introduced with the words “for example” |
| 20 | + or are set apart from the normative text with <code>class="example"</code>, |
| 21 | + like this: |
| 22 | + |
| 23 | + <div class="example"> |
| 24 | + <p>This is an example of an informative example.</p> |
| 25 | + </div> |
| 26 | + |
| 27 | + <p>Informative notes begin with the word “Note” and are set apart from the |
| 28 | + normative text with <code>class="note"</code>, like this: |
| 29 | + |
| 30 | + <p class="note">Note, this is an informative note.</p> |
| 31 | + |
| 32 | + <p>Advisements are normative sections styled to evoke special attention and are |
| 33 | + set apart from other normative text with <code><strong class="advisement"></code>, like |
| 34 | + this: |
| 35 | + |
| 36 | + <strong class="advisement"> |
| 37 | + UAs MUST provide an accessible alternative. |
| 38 | + </strong> |
| 39 | + |
| 40 | + <p>This specification defines a number of procedures. |
| 41 | + User agents are not required to implement these procedures as specified but |
| 42 | + may alter the steps and data structures freely provided the observable |
| 43 | + result is equivalent. |
| 44 | + |
| 45 | + <p>Some procedures <dfn>assert</dfn> an invariant condition. |
| 46 | + Such assertions are intended to clarify the expected behavior and do not |
| 47 | + constitute implementation requirements. |
| 48 | + |
| 49 | +</body> |
| 50 | +<script src="https://www.w3.org/scripts/TR/2016/fixup.js"></script> |
| 51 | +</html> |
0 commit comments