Document Interop Initiative

Table of Contents

1.1.1. Embedded Control Persistence Binary Data Part 1

1.1.2. Quick Access Toolbar Customizations Part 2

1. Shared

This section contains additional information used to more fully describe how Office implements ECMA-376 Office Open XML File Formats[ECMA-376].

1.1. Additional Parts

The subclauses subordinate to this one describe in detail each of the shared part types in addition to those listed in ECMA-376 Office Open XML File Formats ("[ECMA-376] Part 1 §15; Shared").

1.1.1. Embedded Control Persistence Binary Data Part

Content Type:

Binary data representing various properties of an ActiveX control, a standard COM picture object, or a standard COM font object which are persisted using persistStorage, persistStream, or persistStreamInit, as indicated by the persistence attribute of the corresponding Embedded Control Persistence part ("[ECMA-376] Part 1 §15.2.8; Embedded Control Persistence Part").

[Note: The content of the binary data shall be solely determined by the corresponding object. end note]

Root Namespace:

not applicable

Source Relationship:

http://schemas.microsoft.com/office/2006/relationships/activeXControlBinary

An instance of this part contains information about an embedded control in the package. This information is provided by the specified control when asked to persist.

A package is permitted to contain one or more Embedded Control Persistence Binary Data parts, and each such part shall be the target of an explicit relationship in an Embedded Control Persistence ("[ECMA-376] Part 1 §15.2.8; Embedded Control Persistence Part") part-relationship item in a WordprocessingML package; a Worksheet part ("[ECMA-376] Part 1 §12.3.24; Worksheet Part") in a SpreadsheetML package; or a Handout Master ("[ECMA-376] Part 1 §13.3.3; Handout Master Part"), Notes Master ("[ECMA-376] Part 1 §13.3.4; Notes Master Part"), Notes Slide ("[ECMA-376] Part 1 §13.3.5; Notes Slide Part"), Slide ("[ECMA-376] Part 1 §13.3.8; Slide Part"), Slide Layout ("[ECMA-376] Part 1 §13.3.9; Slide Layout Part"), or Slide Master ("[ECMA-376] Part 1 §13.3.10; Slide Master Part") part-relationship item in a PresentationML package.

The content type of this part shall determine the internal format and contents of the embedded control.

[Example: The following example shows the persistence that could be used for an embedded ActiveX control within a WordprocessingML document:

<ax:ocx ax:classid="{C74190B6-8589-11D1-B16A-00C0F0283628}" ax:license="9368265E-85FE-11d1-8BE3-0000F8754DA1" ax:persistence="persistStorage" r:id="rId1" xmlns:ax="http://schemas.microsoft.com/office/2006/activeX" xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships"/>

The relationship type for rId1 is: http://schemas.microsoft.com/office/2006/relationships/activeXControlBinary

The content of the part referenced by rId1 could be any binary data that can be interpreted by the corresponding control. end example]

An Embedded Control Persistence Binary Data part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

An Embedded Control Persistence Binary Data part shall not have any implicit or explicit relationships to other parts defined by ECMA-376 Office Open XML File Formats[ECMA-376].

1.1.2. Quick Access Toolbar Customizations Part

Content Type:	application/xml
Root Namespace:	http://schemas.microsoft.com/office/2006/01/customui
Source Relationship:	http://schemas.microsoft.com/office/2006/relationships/ui/userCustomization

An instance of this part type contains information about the quick access toolbar customizations ([MS-CUSTOMUI]) specific to this package.

[Example: A user customized the quick access toolbar for his WordProcessingML document to contain the UI controls that they commonly use. end example]

A package is permitted to contain at most one Quick Access Toolbar Customizations part, and that part shall be the target of a relationship in the package-relationship item for the document.

[Example: The following package part-relationship item contains a relationship to a Quick Access Toolbar Customizations part, which is stored in the ZIP item /userCustomization/customUI.xml:

end example]

The root element for a part of this content type shall be customUI.

[Example: The following Quick Access Toolbar Customizations content markup would specify that the control with ID SpellingAndGrammar should be added to the quick access toolbar for the package:

<mso:customUI xmlns:mso="http://schemas.microsoft.com/office/2006/01/customui">
<mso:ribbon>
<mso:qat>
<mso:documentControls>
<mso:control idQ="mso:SpellingAndGrammar" visible="true" />
</mso:documentControls>
</mso:qat>
</mso:ribbon>
</mso:customUI>

end example]

A Quick Access Toolbar Customizations part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Quick Access Toolbar Customizations part shall not have implicit or explicit relationships to any other part defined by ECMA-376 Office Open XML File Formats[ECMA-376].

1.1.3. Ribbon Extensibility Part

Content Type:	application/xml
Root Namespace:	http://schemas.microsoft.com/office/2006/01/customui
Source Relationship:	http://schemas.microsoft.com/office/2006/relationships/ui/extensibility

An instance of this part type contains information about the ribbon customizations ([MS-CUSTOMUI]) specific to this package.

[Example: A SpreadsheetML document that represents a timecard could contain custom UI controls to guide the user in filling out the timecard. end example]

A package is permitted to contain at most one Ribbon Extensibility part, and that part shall be the target of a relationship in the package-relationship item for the document.

[Example: The following package part-relationship item contains a relationship to a Ribbon Extensibility part, which is stored in the ZIP item /customUI/customUI.xml:

end example]

The root element for a part of this content type shall be customUI.

[Example: The following Ribbon Extensibility content markup would specify that the ribbon tab with ID TabHome should be hidden for the containing package:

end example]

A Ribbon Extensibility part shall be located within the package containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Ribbon Extensibility part is permitted to have explicit relationships to the following parts defined by ECMA-376 Office Open XML File Formats[ECMA-376]:

· Image Part ("[ECMA-376] Part 1 §15.2.13; Image Part")