The notation "[M1.1]" has not been introduced before its first use here and becomes only clear in Annex H.
Introduce clause notation.
Page 12, line 11 Part 2, section 8.1.1
ed
Proposed Disposition of DIS 29500 Comment DE-0154 (Modified: 2008-01-02) The notation [Mx.x] is discussed in Part 2, §Annex H, page 88, lines 613, “Conformance Requirements”. However, we will add an example to make it clearer and move that text to a new clause in Part 2. Also, we will make a note In Part 2, §8.1.1, page 12, line 11, to reference the new clause. Part 2, §Annex H, page 88, lines 614 This annex summarizes all conformance requirements for producers and consumers implementing the Open Packaging Conventions. It is intended as a convenience; the text in the referenced clause or subclause is considered normative in all cases. Conformance requirements are divided into tables based on their general topic below. The tables contain the requirements that producers and consumers shall follow, those that they should follow, and those that are optional. Each conformance requirement is given a unique ID comprised of a letter (M MANDATORY; S SHOULD; O OPTIONAL), an identifier for the topic it relates to, and a unique ID within that topic. Mandatory requirements are those stated with the normative terms "shall," "shall not," or any of their normative equivalents. Should items are those stated with the normative terms "should," "should not," or any of their normative equivalents. Optional requirements are those stated with the normative terms "can," "cannot," "might," "might not," or any of their normative equivalents. Producers and consumers might use these IDs to report error conditions. Part 2, §2, page 2 (new clause) 2. Conformance Each conformance requirement is given a unique ID comprised of a letter (M MANDATORY; S SHOULD; O OPTIONAL), an identifier for the topic it relates to, and a unique ID within that topic. (Producers and consumers might use these IDs to report error conditions.) Mandatory requirements are those stated with the normative terms "shall," "shall not," or any of their normative equivalents. Should items are those stated with the normative terms "should," "should not," or any of their normative equivalents. Optional requirements are those stated with the normative terms "can," "cannot," "might," "might not," or any of their normative equivalents. [Example: Package implementers shall not map logical item name(s) mapped to the Content Types stream in a ZIP archive to a part name. [M3.11] end example] Part 2, §8.1.1, page 12, line 11 A part name shall not be empty. [M1.1] [Note: The Mx.x notation is discussed in Part 2, §2 end note]
