[KonstantinMirin]

What this changes

In draft 1, a schema can't be derived from the field tables. One concept has several written forms, and many rows give no type or presence. This PR gives each repeated concept one type, and states the rules tables follow.

• § 2.2 defines the shared types, including VocabularyTerm with one rule for an unknown term.
• § 2.6 states the table, type, presence, key, and value conventions.
• Every field and key row has Type and Required columns, and the inline objects this PR owns get key tables.
• § 3 adds four markers and moves the fields they fit.
• The proposal lists its line_items[] (§ 4.1).
• § 2.1 makes the Summary a strict path subset of the Full Representation, and § 2.3 gives the manifest key tables.
• catalog_ref is removed.
• Fields are renamed to follow § 2.2 and § 2.6; the CHANGELOG lists each.
• Headings are numbered, and normative text cites no issue.
• scripts/check_examples.py checks the examples against the tables, in CI.

Related issue

Closes #121, an implementation report from Postindustria (IAB Tech Lab member).

Refs #31, #33, #2, #3, #36, #90, #118, #119, #76, #70.

Builds on

This PR carries #118 by @aleksUIX, #70 by @Sirajmx, and #76 by @Kishore-2572, at their heads. The merge of #76 renumbers its example § 6.6, after #70's § 6.5. Our channel definitions PR (#119), which refs #90, folds into this one. Review the last commit; earlier ones are the PRs it builds on.

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 — § 2, § 2.1, § 2.2, § 2.3, § 2.6, § 3, § 4, § 5, § 6, § 7, § 8
• Appendix A (field index) matches the body — it gains a Required column; scripts/check_appendix.py passes
• Appendix B (fields by marker, and the counts) matches the body — 73 → 74 fields with line_items[]; supplied 3 → 0, requestable 3 → 2; fields the buyer touches 23 → 19; lifecycle, recorded, and asserted added, mixed 2 → 5
• Any affected example in examples/ is updated and still parses — five examples updated, manifest.json regenerated; scripts/check_examples.py passes
• RFC 2119 keywords used deliberately — MUST / SHOULD / MAY are not synonyms
• The no-inheritance rule (§ 2) still holds — reworded, same rule
• Anything selectable declares available[] and included[]; anything settable declares bounds (§ 3.1, § 3.2) — every selectable field is a Selectable[T]; every settable field is a Settable[T], except frequency_cap and commitment, whose bounds § 3.2 names
• No confidential or commercially sensitive content

Knock-on effects

• Breaking. Renamed fields, catalog_ref removed, and transaction_mechanism values in lower snake case. Terms compare byte for byte, and cost_method: flat is written FLAT.
• Filings this answers.
  • line_items[] answers the container half of @VJAlkimi's #31, with @EvgenyAndroid's implementation evidence.
  • Removing catalog_ref takes the inline side of OQ-2 on @Sirajmx's #3. OQ-2 — Do seller catalogs (catalog_ref) belong in 3.0? #3 keeps tracking § 8 question 2, on whether a fetchable reference is needed.
  • The unknown-term rule covers values for @VJAlkimi's #33; our errors and extensions PR covers keys.
  • SeatRef names a seat with its DSP's domain, as @dtbarne asks on #2.
• What later PRs of ours complete. Some rows name types that later PRs define, such as HistoryEntry and Delta. scripts/check_appendix.py lists each as pending until its PR lands. The audience option, buyer_supplied, buyer_requirements, and buying_route keep their filed form until then. Our PR on what is signed types DocumentRef.url as an HttpsUrl.
• Merging with other open PRs.
  • This PR renames § 2, § 4.1, § 5.6 — Line-item dependencies and bonus lines (#23) #70's min_commitment[] to min_commitments[], and recasts § 2.3 — Static manifest at a well-known URL for standard proposals (#29) #76's text as key tables.
  • Whichever of this PR and #120 merges later gives § 2.1, § 5.2 — Placement: what each impression is (#89) #120's rows Type and Required cells and renumbers its section § 5.2.2. Its example becomes § 6.7.
  • Account for seller fees after selecting one price #117 by @aleksUIX has a vector whose cost_method is cpm. Under § 2.2, cpm is an unknown term.
• Maintainers' docs. README.md and docs/ give the 2026-11-10 close date.

---

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.