ORTB
Volume navigation

Compliance overview

Group overview
On this page

Position

Compliance has two sides: ad servers keep to the schema and cross-origin retrieval; players presuppose VAST 3.0 and the Ad Pod format, supporting the three break types to the limit of their capabilities.

Spec section
§3
Compliance sides
广告服务器 · 播放器

Player behaviour

  • 1Ad server side: adhere to the VMAP 1.0 schema; support cross-origin retrieval of VMAP responses
  • 2Player side: must be VAST 3.0 compliant, must comply with the VAST 3.0 Ad Pod format, and must support the three break types to the fullest extent of its capabilities
  • 3A player whose technology precludes a break type (e.g. nonlinear) can still be considered VMAP compliant

Invalid forms

  • A player claiming VMAP compliance while supporting only VAST 2.x
This chapter's body is data-driven from the IAB VMAP 1.0.1 official PDF and the official repository XSD, cross-checked against each other.