Page 63

3.18

Extensions

TOC Schema Ad servers can use this XML node for custom extensions of VAST. When used, custom XML should fall under the nested <Extension> (singular) element so that custom XML can be separated from VAST elements. An XML namespace (xmlns) should also be used for the custom extension to separate it from VAST components. The following example includes a custom xml element within the <Extensions> element. <Extensions> <Extension> <CustomXML>â&#x20AC;Ś</CustomXML> <Extension> </Extensions>

The publisher must be aware of and be capable of executing any VAST extensions in order to process the content. Player Support

Optional

Required in Response

No

Parent

InLine or Wrapper

Bounded

0-1

Sub-elements

Extension

3.18.1

Extension

TOC Schema One instance of <Extension> should be used for each custom extension. The type attribute identifies the MIME type of any code provided in the extension. Player Support

Optional

Required in Response

No

Parent

Extensions

Bounded

0+

Content

Custom XML object

Attributes

Description

type

The MIME type of any code that might be included in the extension.

Š 2016 IAB Technology Laboratory

63

VAST_v4.0

VAST 4.0 - The test  

This is a good document. You should read it.

VAST 4.0 - The test  

This is a good document. You should read it.