How vastlint's Validation Rules Were Extracted from the VAST PDF Specs and XSD Schemas

1 / 2

DEV Community·Aleksander Sekowski·6 months ago

Reading 0:00

15s threshold

VAST-2.0-root-element Root element must be <VAST>

VAST Spec

VAST-2.0-root-version

<VAST> must have a version attribute VAST Spec

VAST-2.0-root-version-value VAST version attribute must be a recognised version string VAST XSD

VAST-2.0-root-has-ad-or-error

<VAST> must contain at least one <Ad> or <Error>

VAST Spec

VAST-4.0-wrapper-root-error

<VAST> root contains both <Ad> and <Error> elements (invalid per VAST 4.0) VAST Spec

VAST-2.0-ad-has-inline-or-wrapper Each <Ad> must contain exactly one <InLine> or <Wrapper>

VAST Spec

VAST-2.0-inline-adsystem

<InLine> must contain <AdSystem>

VAST Spec

VAST-2.0-inline-adtitle

<InLine> must contain <AdTitle>

VAST Spec

VAST-2.0-inline-impression

<InLine> must contain at least one <Impression>

VAST Spec

VAST-2.0-inline-creatives

<InLine> must contain <Creatives> with at least one <Creative>

VAST Spec

VAST-4.1-adservingid-present

<InLine> must contain <AdServingId> (VAST 4.1+) VAST Spec

VAST-4.0-universaladid-present

<Creative> must contain…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.

Menu