1. Shared. 1
1.1.
Additional Parts. 1
1.1.1.
Embedded Control Persistence Binary Data Part 1
1.1.2. Quick
Access Toolbar Customizations Part 2
1.1.3.
CustomUI Part 3
1.1.4.
CustomUI2 Part 4
This section contains additional information used to more
fully describe how Office implements Office Open XML File Formats[ISO/IEC-29500:2008].
The subclauses subordinate to this one describe in detail
each of the shared part types in addition to those listed in Office Open XML
File Formats ("[ISO/IEC-29500-1] §15").
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 ("[ISO/IEC-29500-1]
§15.2.9") part-relationship item in a WordprocessingML package; a
Worksheet part ("[ISO/IEC-29500-1] §12.3.24") in a SpreadsheetML
package; or a Handout Master ("[ISO/IEC-29500-1]
§13.3.3"), Notes Master ("[ISO/IEC-29500-1]
§13.3.4"), Notes Slide ("[ISO/IEC-29500-1]
§13.3.5"), Slide ("[ISO/IEC-29500-1]
§13.3.8"), Slide Layout ("[ISO/IEC-29500-1]
§13.3.9"), or Slide Master ("[ISO/IEC-29500-1]
§13.3.10") 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 Office
Open XML File Formats[ISO/IEC-29500:2008].
|
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-CUSTOMUI2])
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:
<Relationships xmlns="…">
<Relationship Id="rId2"
Type="http://…/2006/relationships/ui/userCustomization"
Target="/userCustomization/customUI.xml" />
</Relationships>
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 Office Open XML
File Formats[ISO/IEC-29500:2008].
|
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 CustomUI 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 CustomUI
part, which is stored in the ZIP item /customUI/customUI.xml:
<Relationships xmlns="…">
<Relationship Id="rId5"
Type="http://…/2006/relationships/ui/extensibility"
Target="/customUI/customUI.xml" />
</Relationships>
end example]
The root element for a part of this content type shall be customUI.
[Example: The
following CustomUI content markup would specify that the ribbon tab with ID TabHome should be hidden for the containing
package:
<customUI xmlns="http://schemas.microsoft.com/office/2006/01/customui">
<ribbon>
<tabs>
<tab idMso="TabHome" visible="false" />
</tabs>
</ribbon>
</customUI>
end example]
A CustomUI part shall be located within the package
containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship
element shall be Internal).
A CustomUI part is permitted to have explicit relationships
to the following parts defined by Office Open XML File Formats[ISO/IEC-29500:2008]:
·
Image Part ("[ISO/IEC-29500-1]
§15.2.14")
|
Content Type:
|
application/xml
|
|
Root Namespace:
|
http://schemas.microsoft.com/office/2007/10/customui
|
|
Source Relationship:
|
http://schemas.microsoft.com/office/2007/relationships/ui/extensibility
|
An instance of this part type contains information about the
Ribbon and Backstage(TM) view customizations ([MS-CUSTOMUI2])
specific to this package.
[Example: A
SpreadsheetML document that is part of a document management system could
contain Backstage controls to guide the user in the document workflow process. end example]
A package is permitted to contain at most one CustomUI2
part, and that part shall be the target of a relationship in the
package-relationship item for the document. If a package contains both a
CustomUI and CustomUI2 part then only the CustomUI2 part is applied. If a
package contains a CustomUI part and does not contain a CustomUI2 part then the
CustomUI part is applied.
[Example: The
following package part-relationship item contains a relationship to a CustomUI2
part, which is stored in the ZIP item /customUI/customUI2.xml:
<Relationships xmlns="…">
<Relationship Id="rId6"
Type="http://…/2007/relationships/ui/extensibility"
Target="/customUI/customUI2.xml" />
</Relationships>
end example]
The root element for a part of this content type shall be customUI.
[Example: The
following CustomUI2 content markup would specify that the print tab in the
Backstage view with ID PlacePrint should be
hidden for the containing package:
<customUI
xmlns="http://schemas.microsoft.com/office/2007/10/customui">
<outSpace>
<place idMso="PlacePrint" visible="false" />
</outSpace>
</customUI>
end example]
A CustomUI2 part shall be located within the package
containing the source relationship (expressed syntactically, the TargetMode attribute of the Relationship
element shall be Internal).
A CustomUI2 part is permitted to have explicit relationships
to the following parts defined by Office Open XML File Formats[ISO/IEC-29500:2008]:
·
Image Part ("[ISO/IEC-29500-1]
§15.2.14")