15.2.2 Audio Part

Content Type:

Any supported audio type.

[Note: Some example content types are: audio/aiff http://developer.apple.com/documentation/QuickTime/INMAC/SOUN

D/imsoundmgr.30.htm

audio/midi

audio/ogg

audio/mpeg end note]

Root Namespace:

not applicable

Source Relationship:

http://www.midi.org/about-midi/specinfo.shtml

http://xiph.org/vorbis/doc/Vorbis_I_spec.html

ISO/IEC 11172-3

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

An instance of this part type contains an audio file.

A PresentationML package is permitted to contain zero or more Sound parts, each of which shall be the target of a relationship in 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-relationship item. [Example: The following Slide part- relationship item contains a relationship to a Sound part, which is stored as the file E:\Beethoven’s Symphony No. 9.wma:

<Relationships xmlns="…">
  <Relationship Id="rId1"
    Type="http://…/audio/x-ms-wma"
    Target="file:///E:/Beethoven's%20Symphony%20No.%209.wma"
    TargetMode="External"/>
</Relationships>

end example]

An Audio 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 Audio part is not stored as XML; instead, it involves a relationship target that is an audio clip.

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

A producer that wants interoperability should use the following standard format:

  • audio/mpeg ISO/IEC 11172-3
Last updated on