The video codecs allowed for the "video" element are not specified. There are many propietary and non-portable codecs which would break portability of a document.

Define a set of patent-free portable video codecs as base. Whenever other codecs are used, the document must be marked as "extended" (see comment for Part 1, Section 2.6)

03/06/93 te

3159(3166)

Proposed Disposition of DIS 29500 Comment CO-0211 (Modified: 2008-01-03) The video element does not specify the actual video file that is used by the animation; as such, we do not believe that it needs a list of potential codecs. To clarify the semantics of this element, the following changes will be made in Part 4, §4.6.93, pages 3,159­3,160, lines 29­30, 1­8: This element specifies video information in an animation sequence. This element specifies that this node within the animation tree triggers the playback of a video file; the actual video file used is specified by the videoFile element (§4.6.70). [Example: Consider a slide with an animated video content. The <video> element should be is used as follows: <p:cSld> <p:spTree> <p:pic> <p:nvPicPr> <p:cNvPr id="4"/> ... <p:nvPr> <a:videoFile r:link="rId1" contentType="video/ogg"/> </p:nvPr> </p:nvPicPr> ... </p:pic> </p:spTree> </p:cSld> ... <p:childTnLst> <p:seq concurrent="1" nextAc="seek"> ... </p:seq> <p:video> <p:cMediaNode> ... <p:tgtEl> <p:spTgt spid="4"/> </p:tgtEl> </p:cMediaNode> ... </p:video> </p:childTnLst> The video element specifies the location of the audio playback within the animation sequence; its child spTgt element specifies that the shape which contains the video to be played has a shape ID of 4. If we look at the shape with that ID value, its child videoFile element references an external video file of content type video/ogg located at the target of the relationship with ID rId1 . E e nd E e xample]