Skip to content

[Comment] § 1 — Two documents define the Proposal; say which governs what #59

Open

Description

@KonstantinMirin

Which section?

1 — Preamble and scope

Your comment

Two IAB Tech Lab documents define a Proposal and its statuses, and neither cites the other. We ask for a § 1.2 that says which governs what. Our post-agreement PR carries it.

The opening paragraph calls OpenProposal "the canonical object a seller manages alongside its OMS and ad server". IABTechLab/iab-agentic-primitives v0.5.1 is pre-release and not listed on the AAMP hub, but the hub-listed Seller Agent and Buyer Agent pin it. Its Proposal.json disagrees on basics:

  • status: draft|published|under_review|agreed|withdrawn|expired here; draft|sent|countered|accepted|rejected|expired there.
  • Money: Number here; amount_micros there.

Their Proposal has no transitions, and booking runs on their Deal machine.

Ask: add § 1.2, condensed here:

1.2 Relationship to other AAMP artifacts

OpenProposal is normative for the proposal and line-item object, its lifecycle to terminal statuses, and what this document says a request or response carries.

It is not normative for message envelopes or bindings, any lifecycle after agreed, or the mapping of its values to the AAMP wire and lifecycle contract (provisional name). These belong to that contract.

The AAMP hub maintains the value correspondence. Until that contract is published on an IAB Tech Lab standards track, the correspondence is informative and this document governs. Once it is published, each document governs the concerns this section assigns to it.

Settle this before the JSON Schema ships.

Concrete scenario

A programmatic_guaranteed line item reaches agreed, and the Seller Agent fails to book it as a primitives Deal. As drafted, OpenProposal has no transition out of agreed, Deal has no correlation_id, and neither document says which record is in error.

Under § 1.2, the failure is the contract's state. The join @franks33 asked for is the baseline VersionRef plus external_references[], which replace correlation_id.

You are commenting as

Other — IAB Tech Lab member (Postindustria).

Before you submit

  • I have read CONTRIBUTING.md and agree my contribution may be published under this repository's licence.
  • This comment contains no confidential or commercially sensitive information.

Details and examples: Normative boundary: full rationale and examples

Revised 2026-11-03: Rewritten against the § 1.2 PR. The contract's provisional name replaces the brackets; the baseline and external_references[] replace correlation_id.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions