§ 5.2, § 5.9 — Video and audio: programs, break position, and the audio feed (#99, #100, #101) by KonstantinMirin · Pull Request #150 · IABTechLab/OpenProposal

KonstantinMirin · 2026-11-04T14:47:14Z

What this changes

Draft 1 can't say where in a break an ad plays, or which show or game it runs in. Nor can it name the audio feed, or say if the ad is recorded into the content.

placement gets a Placement key table (§ 5.2.2), with feed and ssai. It is REQUIRED on a video or audio line item, and plcmt on video.
New § 5.2.3 sells pre-roll, mid-roll, and pod slots as priced break_position options, which availability recomputes against (§ 3.3).
New § 5.2.9 makes programs and live events selectable, with AdCOM Content and a LEAP EventSchedule. It says what happens when an event doesn't air.
content_detail is removed. episodes is its own field, REQUIRED on a podcast or catch-up radio feed.
§ 5.9 defines dai, scheduled, and embedded for every channel, and the rules for an embedded line item.
creative_delivery.protocols[] takes AdCOM Creative Subtypes codes, and other_protocols[] takes terms. They replace protocol and third_party_tags.
ProductionOption loses cost, since deltas prices a build, and build_owner becomes built_by.
§ 1.1 maps a ctv line item that carries plcmt to adtypes 2. New § 6.10 and § 6.11 show an embedded podcast and a live event series.

Related issue

Closes #99. Closes #100. Closes #101.

Refs #89, #120, and #121.

Builds on

This PR builds on our placement PR (#120), which merges first, and our DOOH PR. It builds on our settlement PR, our pricing PR, our handoff PR, our post-agreement PR, and our holds PR. Those build on our signing PR, buyer writes PR, lifecycle PR, parties PR, errors and extensions PR, and shared types PR. Through them it carries #18, #70, #71, and #72 by @Sirajmx, #73 to #76 by @Kishore-2572, and #117 and #118 by @aleksUIX. Review "Define video and audio placement, programs, and break position" and the podcast example fix.

Type

Editorial — no normative effect
Normative — changes what the spec requires
Breaking — would break an implementation already built to this draft
Examples / schema / docs only

Checklist

The body section is updated — § 1.1, § 2.1, § 2.6, § 3.3, § 4.1.1, § 5.2, § 5.2.2, new § 5.2.3, new § 5.2.9, § 5.4, § 5.6.4, § 5.7, § 5.7.1, § 5.9, § 6.3, § 6.4, § 6.7, new § 6.10 and § 6.11, and § 7
Appendix A (field index) matches the body — rows for programs, episodes, break_position, and retention; content_detail and third_party_tags removed; placement and controlling_measurement rows updated. scripts/check_appendix.py passes
Appendix B (fields by marker, and the counts) matches the body. selectable goes from 14 to 16, and the field count from 97 to 99. seller-set stays 47: episodes and retention in, content_detail and third_party_tags out.
Any affected example in examples/ is updated and still parses — new line-item-podcast-embedded.yaml (§ 6.10) and line-item-ctv-live-series.yaml (§ 6.11). line-item-rewarded-video.yaml (§ 6.7) uses the current field names. The CTV examples gain placement.ssai and serving_mode: dai, § 6.3 gains priced break_position options, and the audio example gains placement.feed. Both record_digest values are recomputed, and manifest.json is regenerated. scripts/check_examples.py checks tentative events and the embedded rules, and passes. scripts/check_pricing_fixtures.py passes 60 of 60
RFC 2119 keywords used deliberately — MUST / SHOULD / MAY are not synonyms
The no-inheritance rule (§ 2) still holds — every new field sits on the line item
Anything selectable declares available[] and included[]; anything settable declares bounds (§ 3.1, § 3.2) — programs and break_position declare both; no new settable fields
No confidential or commercially sensitive content

Knock-on effects

Breaking. A record with content_detail, third_party_tags, creative_delivery.protocol, production.available[].cost, build_owner, serving_mode client_side or ssai, or source_type 0 no longer conforms. A video or audio line item needs placement, with plcmt on video and feed on audio. An embedded line item needs retention and controlling_measurement.
Filings this answers. @esteininger on #101 supports feed and episodes. Here episodes leaves free-text content_detail. Their per-episode categories stay with [Change] § 5.2, § 5.5: Structured content categories (taxonomy_ref) on inventory, and a contextual targeting bound #48.
Changes from the filed text.
- [Change] § 5.2 — Make programs and live events selectable, and say what happens when one doesn't air #100: AdCOM keys nest under content, and schedule takes Instant times. Over OpenRTB 2.6, content values take OpenRTB key names, such as livestream. episodes stands alone, answering [Change] § 5.2 — Make programs and live events selectable, and say what happens when one doesn't air #100 question 5 and [Change] § 5.2, § 5.9 — Audio: name the feed, and say when an ad is recorded into the content #101 question 3.
- [Change] § 5.2, § 5.9 — Audio: name the feed, and say when an ad is recorded into the content #101: serving_mode has three core terms, and placement.ssai states server-side insertion. An embedded line item omits markets.
- § 2.1, § 5.2 — Placement: what each impression is (#89) #120: plcmt is REQUIRED only on video. On ctv its presence states video, answering its question 7. placement moves to § 5.2.2, and the OM SDK rule reads measured_by. reward, instl, and skip take IntegerFlag, and § 6.5 becomes § 6.7.
- [Impl] A schema can't be derived from the tables yet: seven authoring rules and a CI lint would fix that #121: placement and refresh gain key tables, as its rule 2 asks.
Sibling and later PRs. Our property option PR adds § 5.2.4 to § 5.2.8, so programs is § 5.2.9. Our formats PR reconciles the two with our audience PR.

Open questions

[Change] § 5.2 — Sell break position and pod slot as priced options: pre-roll, mid-roll, first in pod #99 questions 1 to 5, [Change] § 5.2 — Make programs and live events selectable, and say what happens when one doesn't air #100 questions 1 to 4, and [Change] § 5.2, § 5.9 — Audio: name the feed, and say when an ad is recorded into the content #101 questions 1, 2, 4, 6, and 7 stay open. § 6.4 answers [Change] § 5.2, § 5.9 — Audio: name the feed, and say when an ad is recorded into the content #101 question 5 as proposed, with Music streaming service (1).
final_after is OPTIONAL. Without it, § 5.9 sets no end to post-flight counting on an embedded line item, and § 5.7.1 leaves that to terms_refs[]. Should embedded require final_after? This extends [Change] § 5.2, § 5.9 — Audio: name the feed, and say when an ad is recorded into the content #101 question 4.
Without placement.feed, as on a video line item, every copy the seller distributes counts toward delivery under retention. Should an embedded video line item name which copies count?
What does a seller promise by writing ssai: 0, which AdCOM defines as status unknown?

By opening this pull request I agree my contribution may be published under this
repository's licence, as set out in CONTRIBUTING.md.

Analyzed and generated with the help of Claude, fully reviewed by me.

§ 5.6 defines floor as the seller's offer floor at proposal time, not the downstream auction floor and not a guarantee that bids will clear. Editorial: the meaning of the field is unchanged. Refs IABTechLab#16

A proposal can say its line items must be bought together (linked_execution, § 4.1), and a line item can name the line items or spend that must be in the same commitment (requires, § 5.6.3). A bonus line is a line item with requires and its own price. The § 2 "binding terms" hook now points at a field, and the Summary Representation carries has_requires and linked_execution. Adds a CTV bonus line example (§ 6.5) and linked_execution: none to the proposal example. Refs IABTechLab#23

The seller declares which exclusion types it accepts and how it enforces each (exclusions_accepted); the buyer supplies its lists (exclusions). Blocked apps carry their store, { platform, bundle }, so one store id is never applied across stores. Exclusions are recompute inputs (§ 3.3) and are never disclosed to other parties (§ 5.8). The display example declares and supplies lists. Refs IABTechLab#25

A line item whose rate differs by market can declare geo with the selectable structure of § 3.1: available[], included[], pricing deltas and max_select. A geo that declares only allowed[] stays settable, so existing payloads are unchanged. When several priced markets are selected, the highest delta applies. The audio example is priced by market. Refs IABTechLab#14

A commitment names the proposal and version it was priced against (§ 5.6.1). The seller rejects a new attempt on a stale version, or past valid_until or price_valid_until, and returns the current version. An authenticated replay with the same idempotency_key and terms returns the stored result without re-running those checks; the same key with different terms is a conflict. Keys are opaque and scoped to one buyer and seller pair. § 4.1 states that each revision while published increments version. The display, CTV and audio examples carry proposal_id and version. Refs IABTechLab#24

§ 4.1 adds an optional, immutable proposal_template_id linking an issued proposal to the seller's template. Each issued proposal has its own status, version and negotiation_history[], and buyers never need the template id to transact. § 7 adds a non-normative note separating seller-side templates from the issued proposals buyers commit against. Appendix A gains one row; Appendix B counts immutable 6 → 7 and 72 fields. The proposal example carries a proposal_template_id. Refs IABTechLab#26

§ 5.8 adds terms_ref ({ url, sha256, version }), REQUIRED when terms_acceptance_required is true, hash-pinned and frozen at agreed, so assent binds to an exact document. § 5.10 adds agreement_ref, an informative pointer to the master or annual agreement a line item is priced under, and documents the io and agreement roles on external_references[]. IO generation is stated to be a connector concern, and § 7 adds a non-normative note on relationships. agreement_ref is seller-set; a buyer-held agreement id travels as an external_references[] entry with role: agreement, so the field keeps one marker (§ 3). Appendix A gains two rows; Appendix B counts seller-set 29 → 31 and 73 fields. The display example carries terms_ref. Refs IABTechLab#27

A new § 2.3 lets a seller publish its public standard line items at /.well-known/openproposal.json: seller_id, generated_at, spec_version and, per proposal, proposal_id, version, the Summary Representation of each line item and a full_url. ETag / Last-Modified are required, only line items with visibility public appear, and entries must match the current version. Buyers discover from the manifest, then fetch the Full Representation of shortlisted line items. Adds examples/manifest.json (§ 6.5) and visibility: public to the CTV and audio examples; the registry_gated display line item is not listed. Refs IABTechLab#29

The specification does not define authentication yet (WS1; see IABTechLab#62), so the replay rule now applies to a replay from the same buyer rather than an authenticated replay. Refs IABTechLab#24

agreement_ref.parties used buyer_id, which the specification does not define. parties[] now names the seller by its seller_id and the buyer by the id it holds in eligible_bidders[] (section 5.8). Refs IABTechLab#27

The rule that a hold on a linked_execution: all proposal uses hold_scope: proposal came from a comment on IABTechLab#23, not the change request as filed. It moves to the PR description as a point for the working group, so this PR carries only the filed change. Refs IABTechLab#23

IABTechLab#25 names the content-category list iab_content_category[], a list of IAB Content Taxonomy ids. The earlier commit renamed it content_category with a version-pinned taxonomy_ref, which nobody proposed. This restores the filed name and shape; which taxonomy version to reference is left to the working group. Refs IABTechLab#25

IABTechLab#14 doesn't say how deltas combine when a buyer selects more than one priced market, and neither did any comment on it. The earlier commit said the highest delta applies; that is a design choice nobody proposed, so it moves to the PR description as a question. Refs IABTechLab#14

Read the media condition from the ad served when an impression accepts several media, name the seller as the party that serves, place linear TV outside the table, and state environments as (distribution channel, device type) pairs. Insert environments.available[] into the summary list without rewrapping it, shorten the changelog entry and drop audio_streaming from OQ-7 in docs/open-questions.md. Refs IABTechLab#90

Move the summary rule out of the § 2.1 key list, drop skip from the CTV example, and mark the CHANGELOG entry as breaking.

time_zone is the line item's clock for daypart windows and frequency_cap.period: an IANA time zone name or viewer_local. A window is { days[], start, end } in civil time with an exclusive end later than start, up to 24:00; a window that crosses midnight is two windows.

List the `days[]` values once in the `daypart` row, as `monday` | ... | `sunday`. Write HH:MM, America/New_York, and UTC as plain text, since they're a format and examples, not field names. The meaning is unchanged.

"At least one of" an empty list is never satisfied, so the bonus line would fail a literal check. An absent key sets no condition. Only the examples change; the any_of[] row and the rules stay as filed in IABTechLab#23. Refs IABTechLab#23

The floor row now says it "neither constrains nor describes the downstream auction floor", as IABTechLab#16 asked, and names that floor: the per-impression floor the exchange applies at auction time (OpenRTB 2.6 Imp.bidfloor). Refs IABTechLab#16

From the Postindustria review on IABTechLab#73: - a replay matches on the same body, every value the buyer sent except idempotency_key, and returns the stored result whether an acceptance or a rejection; a retry against a new version uses a new key; - version increments on each revision of the proposal, not only while published, so a counter under review also moves it; - "deterministic" now says what the checks depend on: the stored proposal and the time the seller receives the attempt; - the price check names the pricing[] entry the commitment is priced against. Refs IABTechLab#24

Refs IABTechLab#146

…ntract No IAB Tech Lab document defines the AAMP wire and lifecycle contract yet. The pre-release iab-agentic-primitives library's OpenAPI file and JSON Schemas define the messages the reference agents exchange, so an implementer can use them as the binding until the contract is published. Refs IABTechLab#59

…hey differ Refs IABTechLab#59

The manifest's hold_limits states the most holds a seller grants at once, per buyer domain and per advertiser. A seller declines a request over a declared limit, and under a per-advertiser limit may decline one that names no advertiser.

Where a value whose Type cell is String conflicts with a typed field of the same version in the binding record, the typed field governs. Identifiers and codes are excluded, and an Enum or shared-type value is a typed field.

A line item's preemption MAY state a remedy, from an open vocabulary with the core terms makegood, credit, and none. It settles the delivery a preemption takes on any delivery_type, in place of shortfall_remedy, so a preempted share-of-voice buyer knows what it gets before committing.

When a line item's preemption states a remedy, the delivery a preemption takes, less any replacement within the flight, is a shortfall on any delivery_type. It settles as though that remedy were the only option in effect at commit, under the remedy_terms of shortfall_remedy. When none is in effect in shortfall_remedy, it must be the only option. Section 8 question 10 adds how much delivery a preemption takes.

Sirajmx and others added 30 commits October 6, 2026 16:28

Clarify that pricing[].floor is the offer floor

ff53dc5

§ 5.6 defines floor as the seller's offer floor at proposal time, not the downstream auction floor and not a guarantee that bids will clear. Editorial: the meaning of the field is unchanged. Refs IABTechLab#16

Scope the replay rule to the same buyer

74a2544

The specification does not define authentication yet (WS1; see IABTechLab#62), so the replay rule now applies to a replay from the same buyer rather than an authenticated replay. Refs IABTechLab#24

Name agreement_ref parties with defined identifiers

b88e9a0

agreement_ref.parties used buyer_id, which the specification does not define. parties[] now names the seller by its seller_id and the buyer by the id it holds in eligible_bidders[] (section 5.8). Refs IABTechLab#27

Add discussion fixtures for pricing alternatives and seller fees

6573e9c

Separate creative inspection from production notifications

7ab6d2b

Keep floor eligibility outside the pricing arithmetic profile

841c9c8

Close inspection URL and notification-observation gaps

8fde92c

Define channel and environments in AdCOM terms

49ad2e2

Add placement to say what each impression is

0bc3f7e

Define placement matching and value types

81de4d8

Move the summary rule out of the § 2.1 key list, drop skip from the CTV example, and mark the CHANGELOG entry as breaking.

Clarify fee basis and allow zero-rate unit commitments

e51ee17

Narrow creative inspection wording and separate fixture tooling

395ca83

Write the daypart day names as one value list

9783ec8

List the `days[]` values once in the `daypart` row, as `monday` | ... | `sunday`. Write HH:MM, America/New_York, and UTC as plain text, since they're a format and examples, not field names. The meaning is unchanged.

Merge IABTechLab#119, channel and environment definitions

c102a50

Merge IABTechLab#118, creative inspection

ecc0ae5

KonstantinMirin added 29 commits November 6, 2026 18:38

Merge the settlement change

9c5950e

Merge the DOOH change

01d7fcf

Say what the preemption carve-out covers with no notice period

16fa566

Refs IABTechLab#146

Merge the pricing change

351f9f4

Merge the settlement change

a6493aa

Merge the DOOH change

b0e0afa

Merge the post-agreement change

70d8fce

Merge the handoff change

c32ae70

Merge the pricing change

1fce5cb

Merge the settlement change

53bd459

Merge the DOOH change

53bcb09

Say what the primitives cover, and that this document governs where t…

a8a7bb4

…hey differ Refs IABTechLab#59

Merge the post-agreement change

8c680e5

Merge the handoff change

173a99f

Merge the pricing change

93798fa

Merge the settlement change

d6eeafa

Merge the DOOH change

0d20912

Let a seller declare hold limits in the manifest

ed74d0c

The manifest's hold_limits states the most holds a seller grants at once, per buyer domain and per advertiser. A seller declines a request over a declared limit, and under a per-advertiser limit may decline one that names no advertiser.

State that typed fields govern free text

e9ac2ce

Where a value whose Type cell is String conflicts with a typed field of the same version in the binding record, the typed field governs. Identifiers and codes are excluded, and an Enum or shared-type value is a typed field.

Merge the signing change

915f709

Merge the post-agreement change

fc9afb6

Merge the handoff change

1a491a8

Merge the holds change

c94e763

Merge the pricing change

db40dc0

Merge the settlement change

89f0c3d

Merge the DOOH change

f8fd2bd

unreconciled mentioned this pull request Nov 7, 2026

OQ-7 — environments[] needs validation against real inventory #8

Open

Navigation Menu

Repository navigation

§ 5.2, § 5.9 — Video and audio: programs, break position, and the audio feed (#99, #100, #101) - #150

§ 5.2, § 5.9 — Video and audio: programs, break position, and the audio feed (#99, #100, #101)#150
KonstantinMirin wants to merge 129 commits into
IABTechLab:mainfrom
KonstantinMirin:op30-video-audio

KonstantinMirin commented Nov 4, 2026 •

edited

Loading

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

KonstantinMirin commented Nov 4, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What this changes

Related issue

Builds on

Type

Checklist

Knock-on effects

Open questions

Uh oh!

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

KonstantinMirin commented Nov 4, 2026 •

edited

Loading