13.3.4 Notes Master Part

Content Type:

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

Root Namespace:

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

Source Relationship:

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

An instance of this part type contains information about the content and formatting of all notes pages.

A package shall contain at most one Notes Master part, and that part shall be the target of an implicit relationship from the Notes Slide (13.3.5) part, as well as an explicit relationship from the Presentation (13.3.6) part.

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

<Relationships xmlns="…">
  <Relationship Id="rId4"
    Type="http://…/notesMaster" Target="notesMasters/notesMaster1.xml"/>
</Relationships>

end example]

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

[Example:

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

end example]

A Notes 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 Notes 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 Notes 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)

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