AdCOM 1.0 JSON Schema Unofficial

Decision records ·

D-011 List: Creative Subtypes - Audio/Video ends at VAST 4.3 Wrapper, 16, while VAST 4.4 is published. Is there a code for VAST 4.4?

Gap Cited on main and at the tag AdCOM1.0-202607.

What the schemas do

No: the vocabulary holds the 16 codes the list names, and no code is invented.

Options

  • no-code Chosen

    No: the vocabulary holds the 16 codes the list names, and no code is invented.

  • next-code

    Add 17 and 18 for VAST 4.4 and its wrapper.

Why

A code is AdCOM's to assign, and the registry holds the codes of its pinned main. AdCOM's develop branch has since assigned 17 to VAST 4.4 and 18 to VAST 4.4 Wrapper, with SIMID 1.2 as API Framework 10, but no tag or main carries them yet, so a sender writing 17 today cites a code no release holds. The registry takes them when they reach main or a tag.

What we ask the specification to state

Merge develop, which assigns VAST 4.4 and VAST 4.4 Wrapper the codes 17 and 18 and SIMID 1.2 the API Framework code 10, to main and tag the result, so that a placement can say it accepts them under a release implementers can name.

The specification lines it rests on

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

main

  • List: Creative Subtypes - Audio/Video, the row of 15 L3321 at 26c59ba
    15 | VAST 4.3
  • List: Creative Subtypes - Audio/Video, the row of 16 L3325 at 26c59ba
    16 | VAST 4.3 Wrapper

Tag AdCOM1.0-202607

  • List: Creative Subtypes - Audio/Video, the row of 15 L3321 at d67a6a8
    15 | VAST 4.3
  • List: Creative Subtypes - Audio/Video, the row of 16 L3325 at d67a6a8
    16 | VAST 4.3 Wrapper

The record's YAML file