OpenProposal (AAMP 3.0) is in public comment. This document explains how to comment, what we do with your comment, and the terms you are agreeing to when you file one.
You do not need to be an IAB Tech Lab member to comment. Anyone with a GitHub account may file an issue or a pull request. By doing so you agree to the Contribution Terms in section 6.
- Read the current draft: spec/openproposal-3.0.md.
- Search existing issues. Someone may already have raised it; add to their thread rather than opening a duplicate, so the disposition covers one discussion, not five.
- Check docs/open-questions.md. If your point lands on one of the seven questions the draft explicitly asks, comment there.
| Route | Use it for | Where it lands |
|---|---|---|
| Comment issue | Something is unclear, wrong, internally inconsistent, or missing. You are not proposing wording. | Triaged, dispositioned, logged |
| Change request issue | You are proposing specific normative wording, a new field, a changed marker, or a removal. | Triaged, dispositioned, logged |
| Open question comment | You are answering one of the 7 questions in § 8. | Feeds the resolution of that question |
| Implementation feedback issue | You built against the draft and hit something. This is the most valuable kind of comment we receive. | Triaged with priority |
| Pull request | You want to supply the exact diff for a change already discussed. | Reviewed against its issue |
| Discussion | You have a question, or want to think out loud before filing. | No disposition; not part of the formal record |
Only issues and pull requests form the formal comment record. Discussions do not. If a discussion produces a real point, file it as an issue so it gets a disposition.
The comments that change the spec have these in common. The issue forms ask for them, but the short version:
- Cite the section. § 5.6.1 commitment, not "the commitment bit".
- Say what breaks. A concrete scenario (a seller, a buyer, a field, and the wrong outcome) beats a general objection. "A seller offering the same inventory as both PG and PMP cannot express different floors per mechanism, because pricing[] sits above transaction_mechanism" is actionable. "The pricing model is too simple" is not.
- Say what you'd do instead, even roughly. A rejected alternative is more useful to the working group than an unanswered complaint.
- Declare your interest. Tell us whether you are commenting as a buyer, seller, SSP, DSP, ad server, measurement vendor, agency or individual. It does not weight your comment, but it tells us where the draft is being read from.
Editorial fixes (typos, broken links, table formatting, a marker in Appendix A that disagrees with the body): send the PR directly, no issue needed.
Normative changes: open an issue first. A PR that changes what the spec requires, without a discussion behind it, will be asked to back up into one. The working group has to be able to show why a requirement changed.
Rules for any spec PR:
- One logical change per PR.
- If you touch a field, update both the body section and Appendix A and Appendix B. The body is normative; the appendices are generated from it and must not drift.
- If you touch a field that appears in an example, update examples/ too.
- Use RFC 2119 keywords deliberately. MUST, SHOULD and MAY are not synonyms.
- Tick the Contribution Terms checkbox in the pull request template.
Every issue filed during the comment period gets a disposition. See docs/comment-process.md for the timeline, who adjudicates, and what each disposition means.
Read this before filing.
By submitting a contribution to this repository (including a pull request, issue, comment, or other material intended for inclusion in the OpenProposal Specification), you agree, on behalf of yourself and any entity you represent, that:
(a) Copyright. Your contribution is licensed to IAB Tech Lab under the Creative Commons Attribution 3.0 License (or, for code in the repository, the Apache License 2.0), and may be used, modified, and made available to the public under that license.
(b) Patents. You grant IAB Tech Lab and each implementer of the OpenProposal Specification a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable license under any patent claims owned or controlled by you or your affiliates that are necessarily infringed by implementing the portions of the Specification that incorporate your contribution, to make, have made, use, sell, offer to sell, import, and otherwise distribute implementations of the Specification. This license terminates as to any party that asserts a patent infringement claim against an implementation of the Specification.
(c) Authority. You have the right to submit the contribution and grant these licenses, including, if you are contributing on behalf of your employer, your employer's authorization.
(d) IAB Tech Lab members. If you are an IAB Tech Lab member, your contributions remain subject to the IAB Tech Lab IPR Policy, which controls in the event of any conflict with these terms.
If you cannot agree to these terms, please do not submit a contribution and contact agentic@iabtechlab.com instead.
Licensing of the repository itself: the specification is licensed under CC BY 3.0. Code in scripts/ and .github/workflows/ is licensed under Apache-2.0 (LICENSE-CODE). Full terms are in LICENSE.
Do not file anything you consider confidential. This repository is public. Rate cards, deal terms, client names and inventory data filed here are public the moment you press submit. Anonymise your examples.
Participation is governed by CODE_OF_CONDUCT.md. Debate the specification, not the people commenting on it.