13.3.3 Handout Master Part

Content Type:

application/vnd.openxmlformats-officedocument.presentationml.handoutMaster+xml

Root Namespace:

http://purl.oclc.org/ooxml/presentationml/main

Source Relationship:

http://purl.oclc.org/ooxml/officeDocument/relationships/handoutMaster

An instance of this part type contains the look, position, and size of the slides, notes, header and footer text, date, or page number on the presentation’s handout.

A package shall contain at most one Handout Master part, and it shall be the target of an explicit relationship from the Presentation (13.3.6) part.

[Example: The following Presentation part-relationship item contains a relationship to the Handout Master part, which is stored in the ZIP item handoutMasters/handoutMaster1.xml:

<Relationships xmlns="…">
  <Relationship Id="rId5"
    Type="http://…/handoutMaster"
    Target="handoutMasters/handoutMaster1.xml"/>
</Relationships>

end example]

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

[Example:

<p:handoutMaster xmlns:p="…">
  <p:cSld name="">
    …
  </p:cSld>
  <p:clrMap … />
</p:handoutMaster>

end example]

A Handout Master part shall be located within the package containing the relationships part (expressed syntactically, the TargetMode attribute of the Relationship element shall be Internal).

A Handout Master part is permitted to have implicit relationships to the following parts defined by ISO/IEC 29500:

• Additional Characteristics (15.2.1)
• Bibliography (15.2.3)
• Custom XML Data Storage (15.2.4)
• Theme (14.2.7)
• Thumbnail (15.2.16)

A Handout Master part is permitted to have explicit relationships to the following parts defined by ISO/IEC 29500:

• Audio (15.2.2)
• Chart (14.2.1)
• Content Part (15.2.4)
• Diagrams: Diagram Colors(14.2.3), Diagram Data(14.2.4), Diagram Layout Definition(14.2.5) and
• Diagram Styles (14.2.6)
• Embedded Control Persistence (15.2.9)
• Embedded Object (15.2.10)
• Embedded Package (15.2.11)
• Hyperlink (15.3)
• Image (15.2.14)
• Video (15.2.15)

A Handout Master part shall not have implicit or explicit relationships to any other part defined by ISO/IEC 29500.