15.2.10 Embedded Object Part

Content Type:

Any content type is allowed

Root Namespace:

not applicable

Source Relationship:

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

An instance of this part type can contain an embedded object produced by any embedded object server.

A package is permitted to contain zero or more Embedded Object 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), Header (11.3.9), or Main Document (11.3.10) part in a WordprocessingML package; a Worksheet part (12.3.24) 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), Slide Master (13.3.10) part in a PresentationML package.

A WordprocessingML document package is permitted to contain zero or more Embedded Object parts, each of which shall be the target of a relationship in a Main Document part-relationship item. Each Embedded Object part shall have an associated image, which appears in the document as a placeholder for the corresponding embedded object.

[Example: Consider the case in which a WordprocessingML document has embedded in it one video object and one audio object. The following Main Document part-relationship item contains relationships to two Embedded parts (one each for the video and audio), which are stored in the ZIP items embeddings/embeddedObjectN.bin:

<Relationships xmlns="…">
  <Relationship Id="rId5"
    Type="http://…/oleObject" Target="embeddings/embeddedObject1.bin"/>
  <Relationship Id="rId7"
    Type="http://…/oleObject" Target="embeddings/embeddedObject2.bin"/>
  <Relationship Id="rId4"
    Type="http://…/image" Target="media/image1.png"/>
  <Relationship Id="rId6"
    Type="http://…/image" Target="media/image2.png"/>
</Relationships>

example]

A SpreadsheetML document package is permitted to contain zero or more Embedded Object parts, each of which shall be the target of a relationship in a Worksheet part-relationship item.

[Example: Consider the case in which a SpreadsheetML document has embedded in it one video object and one audio object on one worksheet, and another audio object embedded in another worksheet. The following Worksheet Document part-relationship item contains relationships to two Embedded Object parts (one each for the video and audio), which are stored in the ZIP items ../embeddings/embeddedObjectN.bin:

<Relationships xmlns="…">
  <Relationship Id="rId2"
    Type="http://…/oleObject" Target="../embeddings/embeddedObject1.bin"/>
  <Relationship Id="rId3"
      Type="http://…/oleObject" Target="../embeddings/embeddedObject2.bin"/>
</Relationships>

end example]

A PresentationML document package is permitted to contain zero or more Embedded Object parts, each of which shall be the target of a relationship in a Slide part-relationship item.

[Example: Consider the case in which a PresentationML document has embedded in it one video object and one audio object on one slide, and another audio object embedded on another slide. The following Slide part- relationship item contains relationships to two Embedded Object parts (one each for the video and audio), which are stored in the ZIP items ../embeddings/embeddedObjectN.bin:

<Relationships xmlns="…">
  <Relationship Id="rId6"
    Type="http://…/oleObject"
    Target="../embeddings/embeddedObject1.bin"/>
  <Relationship Id="rId7"
    Type="http://…/oleObject"
    Target="../embeddings/embeddedObject2.bin"/>
</Relationships>

end example]

An Embedded Object part can be located within or external to the package containing the relationships part (expressed syntactically, the TargetMode attribute of the Relationship element can be Internal or External).

An Embedded Object part is permitted to have an explicit relationship to the following parts defined by ISO/IEC 29500:

• Hyperlink (15.3)

An Embedded Object part shall not have any implicit or explicit relationships to other parts defined by ISO/IEC 29500.