Repository navigation
§ 3, § 5.5, § 5.6 — Buyer writes: the selection, the settable value, and the agreed rate (#22, #30, #58) - #141
Open
KonstantinMirin wants to merge 43 commits into
Open
KonstantinMirin wants to merge 43 commits into
KonstantinMirin wants to merge 43 commits into
Conversation
§ 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
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
Give each repeated concept one type in section 2.2, and state the table, presence, type, key, and value rules in section 2.6. Add Type and Required columns to every field and key table. Add the lifecycle, recorded, asserted, and mixed markers, and a line_items[] field. Define the Summary as a strict path subset, with manifest key tables. Delete catalog_ref. Rename the time, reference, delta, cap, and path fields to use the shared types. Number every heading, and keep issue citations and edit history out of normative text. Update the examples, the manifest, the appendices, and the docs. Teach check_appendix.py the new columns and a closed layout list, and add check_examples.py, which checks the examples against the spec's tables.
# Conflicts: # examples/proposal.yaml # spec/openproposal-3.0.md
Separate shared and issued proposals, and add issued_from. Define the binding record, record_digest, and assent[] entries, freeze a version's offered terms, and state one staleness rule for asks and holds. Give each act one history action, name the status types, make the line-item transitions exhaustive, define a firm entry per pricing entry, and list the allowed decline grounds once. State agreed once. Remove buyer state from the shared examples, add an issued, partly agreed example, and recompute its record_digest in the checker.
Add selected[] as the complete set of options in effect and value as the one buyer key on a settable field, with an explicit default. An envelope's value narrows allowed[], and the bare-value fallbacks go. Every object option has an id, unique in its field. Name BuyerWrites, LineItemWrites, and the availability read. Give agreed_rate one formula, on the committed entry only, rounded once. Rename gross_rate to list_rate, floor to min_rate, a hint, and delta_pct to delta_fraction, a fraction. Make list_rate and commitment_bounds requestable, mark commitment mixed, and give transaction_mechanism max_select 1. Split geo into a settable geo and a selectable markets over GeoCode, type device as AdCOM codes and daypart as ClockWindow, and delete supported_formats. Update the examples, the issued record_digest, the appendices, and the example checker.
This was referenced Nov 4, 2026
Open
Open
Open
Open
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
Draft 1 names no key the buyer writes to, and no formula for
agreed_rate. This PR states both.selected[]is the complete set of options in effect. Object options have anid, and options combine freely. ADeltatable holdsdelta_cpm,delta_fraction, anddelta_flat.settablefield is aSettableor aSettableRange. The buyer writesvaluebeside an explicitdefault, with no bare-value fallback.BuyerWritesandLineItemWrites.agreed_ratehas one formula, on the committed entry, rounded once.list_rateandcommitment_boundsarerequestable, and a granted rate is the next version'slist_rate.min_rateis a hint that grants nothing.geoholdsGeoCodeentries, andmarketsis the form priced by market.deviceholds AdCOM 1.0 device types, anddaypartholdsClockWindowentries.transaction_mechanismdeclaresmax_select: 1.Related issue
Refs #22 and #30 by @VJAlkimi, and #58 by @dtbarne.
Refs #14, #16, #111, #133.
Builds on
This PR builds on our lifecycle PR, which builds on our parties PR, our errors and extensions PR, and our shared types PR. It carries #72 and #18 by @Sirajmx, at their heads. The #18 merge resolves to the
min_raterow. Our daypart clock PR (#123) folds into this one. Review the last commit and the #18 merge; the earlier ones belong to the PRs it carries.Type
Checklist
marketsandtime_zoneadded,list_rateandmin_raterenamed, andgeo,device, anddaypartretyped.list_rate,commitment_bounds, andcommitmentare re-marked, andagreed_rateis REQUIRED on the committed entry.scripts/check_appendix.pypassesselectable12 → 13,settable5 → 4, andrequestable2 → 4.mixed5 → 6 andseller-set39 → 38, for 87 fields, up from 85examples/is updated and still parses —proposal-issued.yamlshowsselected[]besideincluded[], avalueongeoandfrequency_cap, andagreed_rate27.54. Itsrecord_digestis recomputed.line-item-display.yamladdsdeviceanddaypart, and the audio example moves tomarkets.manifest.jsonis regenerated.scripts/check_examples.pyrecomputes eachagreed_rateand passesBuyerWritespath sits on the line itemselectabledeclaresavailable[]andincluded[]; anythingsettabledeclares bounds (§ 3.1, § 3.2) —marketsdeclares both, and everysettablefield also declaresdefaultKnock-on effects
gross_rate,floor, anddelta_pctbecomelist_rate,min_rate, anddelta_fraction. Adelta_fractionof0.02is 2 percent. Country codes are ISO 3166-1 alpha-2.deviceanddaypartchange shape, andsupported_formatsis removed.selected[]andvalueare the keys @VJAlkimi asked for in [Change] § 3 — Name the key the buyer writes its selection to:selected[]on selectable fields,valueon settable fields #22.defaultnames [Change] § 3 — Name the key the buyer writes its selection to:selected[]on selectable fields,valueon settable fields #22's declared default.requested_rate), state howagreed_rateis derived, and say who can readfloorandseller_rate#30. It answers @aleksUIX's question on #30: a request moveslist_rate, before options.GeoCode, device types, andClockWindowcarry @dtbarne's [Change] § 5.5 — Typed geo codes aligned with the OpenRTB 2.6 Geo object #58 and @dineshbhat's [Change] § 5.5 — Type the device and daypart envelopes: AdCOM device types, and dayparts with a time-zone basis #111.marketskeeps @fgranata's per-market deltas from [Change] § 5.6 — Per-geo pricing: selectablegeowith price deltas, andpricing[].guidancepercentiles alongsidefloor#14, and § 5.5 — Selectable geo with per-market price deltas (#14) #72's "MUST NOT declare both".min_ratekeeps § 5.6 — pricing[].floor is the offer floor, not the auction floor (#16) #18's point, from @fgranata's [Comment] § 5.6 — pricing[].floor is the offer floor, not the downstream auction floor #16: it isn't the downstream auction floor.requested_rate), state howagreed_rateis derived, and say who can readfloorandseller_rate#30:requested_rateisn't added; arequestonlist_ratereplaces it. Our reply read a granted rate as final. Here it becomes the next version'slist_rate, and deltas still add. The reply's composed floor isn't added.{ type, code }entries,max, andbasis. They becomeGeoCodestrings,count, andper, andendbecomesbefore.personisn't a coreperterm.min_rateno longer resolves a counter without a round trip.floordoesn't stay as a deprecated alias.min_rateout of the offered terms. Later PRs type the held terms, each mechanism'sdelivery_type,commitment_bounds, more option ids, andcombine.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.