DAAST-1.0-duration-format
DAAST-1.0-duration-format
DAAST `<Duration>` value does not match HH:MM:SS[.mmm] format
ErrorDAASTIAB DAAST 1.0 §3.2.1DAAST 1.0 and 1.1 (all DAAST documents)
Short answer
DAAST requires duration values in HH:MM:SS or HH:MM:SS.mmm format. A bare number or free-form string cannot be parsed and will cause the ad to be discarded.
Why this matters in production
This rule is usually a delivery blocker. Many players, SDKs, and ad servers will discard the response or skip the affected creative once this condition is hit. DAAST rules validate the structural and semantic requirements specific to digital audio ad serving. Audio-specific fields like Category, AdInteractions, and audio MediaFile attributes are required by the spec and are absent from standard VAST validation. Affected scope: DAAST 1.0 and 1.1 (all DAAST documents).
Check your VAST tag for
DAAST-1.0-duration-format and other issues instantly.Open the VAST tag validator →Other DAAST rules
DAAST-1.0-root-versionRoot `<DAAST>` element must have a version attributeDAAST-1.0-root-version-value`<DAAST>` version attribute must be a recognised version string (`1.0` or `1.1`)DAAST-1.0-root-has-ad-or-error`<DAAST>` must contain at least one `<Ad>` or `<Error>`DAAST-1.0-ad-has-inline-or-wrapperEach DAAST `<Ad>` must contain exactly one `<InLine>` or `<Wrapper>`DAAST-1.0-inline-adtitleDAAST `<InLine>` must contain `<AdTitle>`DAAST-1.0-inline-impressionDAAST `<InLine>` must contain at least one `<Impression>`DAAST-1.0-inline-categoryDAAST `<InLine>` must contain `<Category>` (required in DAAST, unlike VAST)DAAST-1.0-inline-creativesDAAST `<InLine>` must contain `<Creatives>` with at least one `<Creative>`