Compliance checklist

Position

A checkable compliance list: two items for ad servers, three for players (including the capability-limit exception).

Spec section

§3.1–3.2

Cross-origin

crossdomain.xml · ACAO · clientaccesspolicy.xml

Player behaviour

• 1Ad server ①: adhere to the VMAP 1.0 schema
• 2Ad server ②: support cross-origin retrieval by industry standard methods — crossdomain.xml for Adobe Flash, the Access-Control-Allow-Origin header for CORS-enabled user agents, clientaccesspolicy.xml for Microsoft Silverlight
• 3Player ①: must be VAST 3.0 compliant and need not implement any ad response template other than VAST 3.0
• 4Player ②: must be compliant with the VAST 3.0 Ad Pod format
• 5Player ③: must support the three break types to the fullest extent of its capabilities, matching its VAST 3.0 format compliance

Invalid forms

• ✕Responses not retrievable cross-origin (none of the three mechanisms present)
• ✕A player claiming compliance without Ad Pod format support

Related chapters

• Compliance overview
• Example response