Theme Part

Content Type:

application/vnd.openxmlformats-officedocument.theme+xml

Root Namespace:

http://schemas.openxmlformats.org/drawingml/2006/main

Source Relationship:

http://schemas.openxmlformats.org/officeDocument/2006/relationships/theme

An instance of this part type contains information about a document's theme, which is a combination of color scheme, font scheme, and format scheme (the latter also being referred to as effects). For a WordprocessingML document, the choice of theme affects the color and style of headings, among other things. For a SpreadsheetML document, the choice of theme affects the color and style of cell contents and charts, among other things. For a PresentationML document, the choice of theme affects the formatting of slides, handouts, and notes via the associated master, among other things.

A WordprocessingML or SpreadsheetML package shall contain zero or one Theme part, which shall be the target of an implicit relationship in a Main Document (§11.3.10) or Workbook (§12.3.23) part. A PresentationML package shall contain zero or one Theme part per Handout Master (§13.3.3), Notes Master (§13.3.4), Slide Master (§13.3.10) or Presentation (§13.3.6) part via an implicit relationship.

example: 
<Relationships xmlns="…">
  <Relationship Id="rId4" 
    Type="http://…/theme" Target="theme/theme1.xml"/>
</Relationships>

The root element for a part of this content type shall be< officeStyleSheet>.

example: 
<a:officeStyleSheet xmlns:a="…">
  <a:baseStyles>
    <a:clrScheme name="…">
      …
    </a:clrScheme>
    <a:fontScheme name="…">
      …
    </a:fontScheme>
    <a:fmtScheme name="…">
      …
    </a:fmtScheme>
  </a:baseStyles>
  <a:objectDefaults/>
</a:officeStyleSheet>

A Theme part shall be located within the package containing the source relationship (expressed syntactically, the @TargetMode attribute of the <Relationship> element shall be Internal).

A Theme part is permitted to contain explicit relationships to the following parts defined by this Standard:

A Theme part shall not have any implicit or explicit relationships to other parts defined by this Standard.