1. Part Overview
From OOXML-Wiki
Contents |
[edit] General comment
It is unclear what the term "interoperability" means within the proposed standard. The standard needs to differentiate between issues that affect interoperability between different implementations of OOXML (i.e. implementations which make different choices in areas where options are provided, or make different interpretations of ambiguous text) and interoperability between applications based on different standards and specifications (e.g. interoperability between OOXML Maths and MathML).
[edit] General comment
It should not be necessary to read any informative text to implement a function defined in a normative section of this standard. Normative text should describe all requirements and not rely on informative examples to identify requirements.
[edit] 1. Part Overview [p1]
The use of 'Part' for different things is confusing. Line 1 (title) it refers to Part 4 as a subpart of OOXML. Line 3 it implicitly refers to WordprocessingML, SpreadsheetML, etc.
Proposed change: Use another word like 'subpart' when referencing WordprocessingML etc., or else use their full names.
[edit] 1.1 [p1, 5]
Table row 'Alternative Format Import' is deemed to have no root element and no reference. The value of this row is unclear.
Proposed change: Clarify the table purpose.
[edit] 1.2 [p1, 6]
Table row 'Custom Property' is deemed to have no root element and no reference. The value of this row is unclear.
Proposed change: Clarify the table purpose.
[edit] 1.5 [p3, 1]
Eleven table rows are deemed to have no root element and no reference. The value of these rows is unclear.
Proposed change: Clarify the table purpose.
