15.2.4 Content Part

Content Type:

Any supported XML content.

[Note: Some example content types are: image/svg+xml http://www.w3.org/TR/SVG11/

application/smil

http://www.w3.org/TR/REC-smil/

http://www.w3.org/TR/MathML2/

text/xml end note]

If no explicit MIME type exists for a specific XML format, text/xml shall be used. Consumers who read a value of text/xml should determine the contents by the root namespace of the contents of the part.

Root Namespace:

Various, as defined by the content type used.

Source Relationship:

[Example: MathML has a root namespace of http://www.w3.org/1998/Math/MathML. end example]

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

An instance of this part type can contain XML markup of a format not defined by ISO/IEC 29500.

A package is permitted to contain zero or more Content parts, and each such part shall be the target of an explicit relationship from a Comments (11.3.2), Endnotes (11.3.4), Footer (11.3.6), Footnotes (11.3.7), Glossary Document (11.3.8), Header (11.3.9), or Main Document (11.3.10) part in a WordprocessingML package; a Drawings (12.3.8) part in a SpreadsheetML package; or a Handout Master (13.3.3), Notes Slide (13.3.5), Notes Master (13.3.4), Slide (13.3.8), Slide Layout (13.3.9), or a Slide Master (13.3.10) part in a PresentationML package.

[Example: The following Main Document part-relationship item contains a relationship to a Content part containing SVG markup, which is stored in the ZIP item svg1.xml:

<Relationships xmlns="…">
  <Relationship Id="rId1"
    Type="http://…/customXml" Target="../customXML/svg1.xml"/>
</Relationships>

end example]

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

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

If a producer that wants interoperability supports equations, it should use one of the following standard formats:

• Office Open XML Math (22.1
• W3C MathML 2.0

If a producer that wants interoperability supports ink annotations, it should use an ink annotation in this element in the following reference standard format:

• InkML http://www.w3.org/TR/inkregs