The element uiCombat97to2003 is a construct which is intended to "disable UI function that is not compatible with word 97-2003"
Since the only company who have the actual knowledge about, which UI function isn’t compatible with Microsoft Word 97 is the owner of the application, this element only make sense for that owner.
Since Word97-2003 is not clearly defined, i guess this means Microsoft Word 97, since the introduction declare, that backward compatibility with Microsoft Office application is one of the intended goals of the ECMA.376 Office Open XML specification.
This means that the element uiCombat97to2003 is a specific element, which only purpose is to let Microsoft, the owner of Microsoft office, build features in the specification, which can’t be delivered by any other application developer.
If this is correct, then Microsoft is the only company who can provide a complete and correct implementation of the ECMA-376 Office Open XML specification
Since the only company who have the actual knowledge about, which UI function isn’t compatible with Microsoft Word 97 is the owner of the application, this element only make sense for that owner.
Since Word97-2003 is not clearly defined, i guess this means Microsoft Word 97, since the introduction declare, that backward compatibility with Microsoft Office application is one of the intended goals of the ECMA.376 Office Open XML specification.
This means that the element uiCombat97to2003 is a specific element, which only purpose is to let Microsoft, the owner of Microsoft office, build features in the specification, which can’t be delivered by any other application developer.
If this is correct, then Microsoft is the only company who can provide a complete and correct implementation of the ECMA-376 Office Open XML specification
The intended behaviour / semantic of the tag should be defined in an unambiguously way in the specification or removed from the specification.
Also insert information used in other compability settings, eg:
[Guidance: To faithfully replicate this behavior, applications must imitate the behavior of that application, which
involves many possible behaviors and cannot be faithfully placed into narrative for this Office Open XML
Standard. If applications wish to match this behavior, they must utilize and duplicate the output of those
applications. It is recommended that applications not intentionally replicate this behavior as it was deprecated
due to issues with its output, and is maintained only for compatibility with existing documents from that
application. end guidance]
Typically, applications shall not perform this compatibility. This element, when present with a val attribute value of true (or equivalent), specifies that applications shall attempt to mimic that existing word processing application in this regard.
Also insert information used in other compability settings, eg:
[Guidance: To faithfully replicate this behavior, applications must imitate the behavior of that application, which
involves many possible behaviors and cannot be faithfully placed into narrative for this Office Open XML
Standard. If applications wish to match this behavior, they must utilize and duplicate the output of those
applications. It is recommended that applications not intentionally replicate this behavior as it was deprecated
due to issues with its output, and is maintained only for compatibility with existing documents from that
application. end guidance]
Typically, applications shall not perform this compatibility. This element, when present with a val attribute value of true (or equivalent), specifies that applications shall attempt to mimic that existing word processing application in this regard.
Page 1469 Part 4
section 2.15.3.54
te
Proposed Disposition of DIS 29500 Comment DK-0017 (Modified: 2008-01-13) Agreed; this property is not part of the legacy binary document format and only affords for the settings of a specific vendor. Accordingly, the following changes will be made: This property will be removed from the specification An affordance will be created for individual applications, such as OpenOffice or WordPerfect, to create custom compatibility settings Part 4, §2.15.3.54, page 1,469: This subclause will be deleted. Part 4, §2.15.3, as a new subclause: 2.15.3.x compatSetting (Custom Compatibility Setting) This element specifies a custom compatibility setting. The semantics for this element are implementation-defined. [Example: Consider the following markup: <w:compatSetting w:name="cooper" w:uri="http://www.example.com/exampleSetting" w:val="1"/> This custom compatibility setting specifies that: It is defined under the http://www.example.com/exampleSetting namespace. Its name is cooper . Its value is 1 . Beyond this, the properties of this setting are implementation-defined by the creator of the http://www.example.com/exampleSetting namespace. end example] Parent Elements compat (§2.15.3.9) Attributes Description Attributes Description name (Name of Setting) Specifies the name of a custom compatibility setting. [Example: Consider the following markup: <w:compatSetting w:name="cooper" w:uri="http://www.example.com/exampleSetting" w:val="1"/> The name of this custom compatibility setting is cooper . end example] The possible values for this attribute are defined by the ST_String simple type (§2.18.89). uri (Namespace of Setting) Specifies the namespace under which the compatibility setting is defined. [Example: Consider the following markup: <w:compatSetting w:name="cooper" w:uri="http://www.example.com/exampleSetting" w:val="1"/> The namespace of this custom compatibility setting is http://www.example.com/exampleSetting . end example] The possible values for this attribute are defined by the ST_String simple type (§2.18.89). val (Value of Setting) Specifies the value of a custom compatibility setting. [Example: Consider the following markup: <w:compatSetting w:name="cooper" w:uri="http://www.example.com/exampleSetting" w:val="1"/> The value of this custom compatibility setting is 1 . This value is interpreted using the implementation-defined behavior published by the creator of this property. end example] The possible values for this attribute are defined by the ST_String simple type (§2.18.89). The following XML Schema fragment defines the contents of this element: <complexType name="CT_CompatSetting"> <attribute name="name" type="CT_String" use="required"/> <attribute name="uri" type="CT_String" use="required"/> <attribute name="value" type="CT_String" use="required"/> </complexType> As well, the corresponding schema files will be updated to include compatSetting as a child element of the compat element. Similar Comments: CL-0101 , CO-0110 , CZ-0025 , FR-0194 , GB-0235 , GR-0036 , IN-0033 , IR-0023 , KR-0012 , PT-0050 , US-0064
