Scope: The scope statement of DIS 29500 has caused much confusion due to its lack of specificity. Moreover, a clearer scope statement could demonstrate that DIS 29500 is not concerned with the same activities as ISO/IEC 26300. As stated, the scope statement is inaccurate and misleading.
Break DIS 29500 up into a true multi-part standard, in which case, each part has its own scope, definitions, conformance, and so on. For example, there might be separate parts for OPC, WordprocessingML, SpreadsheetML, PresentationML, DrawingML, and so on. (See Directives Part 2, §5.1.1.) During the process of refactoring into parts, please also consider conformance at the subpart level.
See Weir #2-002. If the multi-part approach is not used, have the OPC spec contain a note that WordprocessingML, SpreadsheetML, and PresentationML place constraints on OPC usage.
See Weir #2-002. If the multi-part approach is not used, have the OPC spec contain a note that WordprocessingML, SpreadsheetML, and PresentationML place constraints on OPC usage.
Part 1, 1. Scope
te
Proposed Disposition of DIS 29500 Comment US-0046 (Modified: 2008-01-08) Agreed; in the response to AU-0005, CL-0039, CZ-0002, DE-0120, DK-0059, DK-0060, DK-0061, DK-0062, DK-0063, ECMA-0037, FI-0003, IN-0052, IN-0054, JP-0039, JP-0079, KE-0003, NO-0002, NO-0007, PT-0008, PT-0033, US-0021, US-0253 and ZA-0006, we have proposed restructuring DIS 29500 as a multi-part standard, which will result in a new scope clause for each part. In addition, we propose changing the scope clause in Part 1 to read as follows: This International Standard defines a set of XML vocabularies for representing word-processing documents, spreadsheets and presentations. The goal of this standard is to be capable of faithfully representing the pre-existing corpus of word-processing documents, spreadsheets and presentations that had been produced by the Microsoft Office applications at the date of the creation of this standard. It also specifies requirements for consumers and producers of Office Open XML. Similar Comments: NO-0001 ,
