D-032 How are the creative inspection statements of § 5.4 checked?

What the schemas do

Each is an obligation of any implementation that inspects creative: what it may fetch and what it must not fire.

Options

• obligations Chosen

  Each is an obligation of any implementation that inspects creative: what it may fetch and what it must not fire.

• informative

  The statements are guidance

Why

The statements say what an inspecting implementation sends, fetches, requests, and reports, which no proposal or line item shows, and they use MUST and MAY, so they are conformance content. They bind any implementation that inspects, not one party. § 6.3 only points the CTV example to § 5.4, with no statement of its own.

What we ask the specification to state

Say whether creative inspection belongs to the object model or to a separate inspection specification that the AAMP messages reference.

The specification lines it rests on

Each line is quoted as the record pins it. Expand an item to read the quote.

With the open PRs

• § 5.4/creative-inspection-and-previews, a requirement L258 in #118

  An implementation performing inspection MUST NOT send any production notification.

• § 5.4/creative-inspection-and-previews, a requirement L263 in #118

  An implementation MAY retrieve creative documents, follow VAST wrappers and inspect referenced media as needed for its checks.

• § 5.4/creative-inspection-and-previews, a requirement L270 in #118

  The inspector MUST NOT request a destination or redirect that sends a production notification; it MAY use a separate inspection URL or the receiving service's documented test mode under the conditions below.

• § 5.4/creative-inspection-and-previews, a requirement L269 in #118

  A preview that executes creative or verification code MUST prevent that code from sending production notifications.

• § 5.4/creative-inspection-and-previews, a requirement L270 in #118

  Synthetic events MAY be sent to test endpoints, or through a test mode that the receiving service documents as excluding those events from production measurement and delivery diagnostics.

• § 5.4/creative-inspection-and-previews, a requirement L282 in #118

  Inspection failures MUST be reported through diagnostics, without firing a production VAST <Error> or verificationNotExecuted URL.

• § 5.4/creative-inspection-and-previews, a requirement L283 in #118

  An implementation MUST NOT report a check that was skipped or could not finish as passed.