15.2.14 Image Part

Content Type:

Any supported image type.

[Note: Some example content types are: image/gif http://www.w3.org/Graphics/GIF/spec-gif89a.txt

image/png

ISO/IEC 15948:2003

http://www.libpng.org/pub/png/spec/

image/tiff

http://partners.adobe.com/public/developer/tiff/index.html#spec

image/pict

http://developer.apple.com/documentation/mac/QuickDraw/QuickDraw- 2.html

http://www.w3.org/Graphics/JPEG/

image/jpeg end note]

Root Namespace:

Not applicable

Source Relationship:

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

An image can be stored in a package as a ZIP item. Image ZIP items shall be identified by an image part relationship and the appropriate content type.

A package is permitted to contain zero or more Image 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), Drawing (12.3.8), or Main Document (11.3.10) part in a WordprocessingML 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 Slide Master (13.3.10 part in a PresentationML package.

[Example: The following PresentationML’s package-relationship item contains one relationship, for the slide template jpeg image stored in the ZIP item ../media/image1.jpeg:

<Relationships xmlns="…">
  <Relationship Id="rId8"
    Type="http://…/image" Target="../media/image1.jpeg"/>
</Relationships>

end example]

An Image 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 Image part shall not have implicit or explicit relationships to other parts defined by ISO/IEC 29500.

A producer that wants interoperability should use one of the following standard formats:

• image/png ISO/IEC 15948:2003, http://www.libpng.org/pub/png/spec/
• image/jpeg, http://www.w3.org/Graphics/JPEG