According to the text this element is not expected to be used, since the recommendation is to use the element LISTNUM (2.16.5.40),
for this reason there should be no need to include the element in the specification, as the field is just a "place holder" for legacy reason to older version of Microsoft Office file formats
for this reason there should be no need to include the element in the specification, as the field is just a "place holder" for legacy reason to older version of Microsoft Office file formats
It appears that LISTNUM includes the same as AUTONUM why the latter seems superfluous.
Page 1512
line 11-12 Part 4
section 2.16.5.5
Ed
Proposed Disposition of DIS 29500 Comment DK-0120 (Modified: 2008-01-02) Ideally, the standard should not contain deprecated parts; however, we believe that removing this field is not in the best interests of compatibility with existing legacy documents (as documents with these fields already exist). Accordingly, we will remove the field in question from its current location (Part 4, ยง2.16.5.5, page 1512), and place it into a new annex for deprecated features. Following the precedent set by other ISO standards (such as SQL’s ISO 9075:2003 Part 1 and C++’s ISO/IEC 14882:1998), we will make use of a new Annex that contains normative descriptions of all deprecated features. The intent of this Annex is to enable a transitional period during which existing binary documents being migrated to DIS 29500 can make use of those deprecated features to preserve their fidelity, while noting that new documents should not use them. Accordingly, the Conformance clause will also be changed to state that newly created documents (those not created by migrating existing binary documents) should not use deprecated features. All deprecated features will be removed from their current locations in the standard, but will be fully defined in this new Annex. Similar Comments: CL-0123 , CO-0122 , DE-0040 , FR-0168 , GB-0246 , GR-0049 , KE-0030 , US-0107
