DAAST-1.0-mediafile-id
DAAST-1.0-mediafile-id
DAAST `<MediaFile>` should have an `id` attribute (required by the DAAST XSD)
WarningDAASTIAB DAAST 1.0 XSDDAAST 1.0 and 1.1 (all DAAST documents)
Short answer
The DAAST XSD marks the id attribute on <MediaFile> as required. Omitting it may cause strict schema validators to reject the document.
Why this matters in production
This rule is a strong risk signal. Tags with this issue often still parse, but they become brittle across SDKs, SSAI resolvers, and CTV environments. 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-mediafile-id 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>`