IAB Tech Lab today set out its move to publish technical specifications as Markdown on GitHub rather than as static PDF documents, a shift the standards body ties directly to the rise of software agents that read specifications and need to establish which text is current.

In Short

The organisation that writes the technical rulebooks for digital advertising is moving those rulebooks from downloadable documents to GitHub, the platform developers use to host and review code. That matters because a document cannot be corrected without issuing a new version number, while a repository page can be fixed the same day and shows exactly what changed. Formal releases will still be published for implementation, but the repository now carries the current text, and anyone can raise a question or propose an edit against it.

A format change with a stated cause

The post, written by Barnaby Edwards, senior director of product marketing at IAB Tech Lab, describes a transition already under way rather than a plan for later. According to the organisation, the portable document format is a familiar and official-looking container that has stopped serving the pace of the work: "the static nature of the PDF has become a bottleneck rather than a benefit."

The reasoning has two halves. The first is mechanical. A specification distributed as a file begins ageing the moment it is downloaded, and correcting a typographical error or clarifying an ambiguous sentence forces a full version increment, producing v1.1 and v1.2 releases whose differences are invisible without a manual comparison of two long documents. According to the post, that pattern "leads to version confusion across the ecosystem."

The second half is newer and more specific. Language models and autonomous agents now consult these documents directly as part of automated trading workflows, and according to IAB Tech Lab those systems "need to confirm quickly that they are using the latest final specification." A PDF hosted behind a download link answers that question poorly. A repository with tagged releases, commit history and a machine-readable page answers it well.

That argument sits on top of a body of work the organisation has been assembling for eighteen months. The agentic roadmap published on January 6, 2026 committed to extending OpenRTB, AdCOM, OpenDirect, VAST and the Deals API with execution protocols including Model Context Protocol, Agent2Agent and gRPC, rather than replacing them. Extending established specifications rapidly is difficult when each extension requires a document reissue.

What moves, and what does not

Formal versioning survives the change. According to the organisation, final snapshots will continue to be provided for implementation, with the repository carrying the primary reference text between those snapshots. The distinction matters for anyone whose contracts, certifications or vendor assessments cite a numbered version: the numbered version still exists, but it is now a tag rather than the document of record.

Four operational changes follow from the hosting move, as described in the post.

Real-time updates. Small corrections and clarifications can be applied immediately rather than queued for the next release.

Version control. GitHub releases and tags expose what changed between versions without the manual comparison of two long files.

Search and accessibility. Repository content is indexed by search engines and searchable inside the repository itself, and a reader can be pointed at a specific section by URL rather than by page and paragraph number. The post also notes that web-based content works better with screen readers than a document where a keyword may sit inside an image or a complex table.

Issues and pull requests. Questions that previously required an email to a contact address or a wait for a working group meeting can be raised as public issues, with the discussion and its resolution visible to everyone. Proposed improvements to code samples or definitions arrive as pull requests for working group review. According to the post, the effect is to turn "the industry from passive consumers of standards into active participants."

The repository as it stands

The organisation's GitHub account, IAB TechLab, carries 77 public repositories, 443 followers and six listed members. Top languages across the account are JavaScript, Java, HTML, Python and Swift.

Engagement is heavily concentrated. The GDPR Transparency and Consent Framework repository holds 952 stars and 372 forks, the largest counts on the account. The OpenRTB repository follows with 519 stars and 216 forks, ahead of VAST_Samples at 232 and 218, openrtb2.x at 168 and 77, the iabtcf-es toolkit for consent management platforms at 153 and 98, AdCOM at 134 and 83, the VAST repository at 130 and 65, the Global Privacy Platform at 119 and 49, and the Open Measurement JavaScript clients at 74 and 48. At the other end of the distribution, the Accountability Platform repository shows zero stars, zero forks, zero open issues and zero pull requests, and the VAST4.x repository shows two stars and two forks.

Issue and pull request activity is similarly uneven. The Global Privacy Platform repository carries 29 open issues against six pull requests. OpenRTB shows 22 issues and 10 pull requests, VAST shows 16 and nine, the Open Measurement clients show 15 and one, and the Data Deletion Request Framework repository shows two issues and none. Those counts describe the public feedback channel that the transition now makes the default route for the whole catalogue.

Update recency varies by an order of magnitude. VAST4.x was updated in the week before the capture and three repositories, including the consent management toolkit and the Open Measurement clients, within a fortnight. AdCOM was last updated a month earlier. The dated entries cluster in the first half of August: the Data Deletion Request Framework on August 11, OpenRTB on August 10, the consent framework on August 7, the Global Privacy Platform on August 6 and the Accountability Platform on August 5. Relative timestamps of the kind GitHub displays cannot be pinned to exact dates from a page capture, which is a limitation of the source rather than of the repositories.

A catalogue that ages at different speeds

The organisation's own standards directory shows why a living format matters more for some documents than others. Recent entries carry 2026 dates: the Deals API was marked final on February 6, 2026, the Agentic Advertising Management Protocols umbrella initiative on February 26, 2026, and the Content Monetization Protocols initiative at version 1.0 on March 10, 2026. The Agentic Real Time Framework sits at version 1.0 in public comment.

Other entries have not moved in years. The mobile rich media interface definitions specification, MRAID, is listed at version 3.0 from June 2018. The OpenRTB Dynamic Native Ads API is listed at version 1.2 from July 2017, the same month as the advertising creative guidelines in the New Ad Portfolio. The Common Ad Transport Standard is listed at version 1.0 from June 2020, buyers.json and the DemandChain object at version 1.0 from June 2021, and the authenticated connections component of ads.cert from January 2022. OpenRTB itself is listed at version 2.6.x with a September 2024 release date, alongside OpenDirect 2.1.

The directory also carries internal inconsistencies of exactly the type a version-controlled catalogue is meant to surface. The Safe Ad Container entry states that it replaced the SafeFrames and MRAID standards, while MRAID remains listed as a supported specification in the same table. Open Private Join and Activation is marked deprecated and replaced by the Publisher Advertiser Identity Reconciliation protocol, which is listed as final at version 1.1 from July 2025. Earlier privacy frameworks built around the California Consumer Privacy Act are marked deprecated as of January 2024 and replaced by the Global Privacy Platform. The page's roadmap line still points readers to the 2025 roadmap announced in January, in a table that already lists releases dated 2026.

Taxonomies show the same spread. The Audience Taxonomy sits at version 1.1 from April 2020 and the Content taxonomy at version 3.0 from June 2022, while the Privacy Taxonomy remains at version 1.0 in public comment from September 2024.

GitHub was already the delivery route

Today's post formalises a practice that had been spreading through the organisation's newer work for most of the year. The Event and Conversion API specification was finalised at version 1.0 on May 3, 2026 and published in full on GitHub, with a working group drawing contributors from Meta, Google, Walmart, TikTok, Roku, NBCUniversal and Paramount. Three months later, the clean room extension to that standard was opened for comment inside the same repository, with the draft file, a changelog, an examples file and a public comment issue all living together and comments closing on September 4, 2026.

The agentic work followed the same path. When version 2.3 of the Agentic Advertising Management Protocols arrived in July 2026, the organisation attributed the content of the release to activity inside the AAMP GitHub repository, where developers had submitted use cases, flagged bugs found during testing and requested capabilities the previous version lacked. That release added a pricing provenance field intended to stop buying agents from fabricating bid prices when real market data is unavailable.

Read against that record, the transition is less a departure than a decision to stop running two publication models at once. The specifications written for agentic AI were already born in repositories. The older catalogue was not.

What changes for implementers

The practical consequence is a change in where authority sits. Under the document model, the file was the artefact and the working group was the only body that could alter it. Under the repository model, the text is a branch, the release is a tag, and the queue of open issues is visible to competitors, regulators and customers alike.

That visibility cuts in more than one direction. A publisher or demand-side platform can now see which ambiguities others have raised against a specification before committing engineering time. It can also see how long those ambiguities have gone unanswered. The 29 open issues on the Global Privacy Platform repository are a public record of questions asked, whatever their individual merit or status.

Contribution raises a second question, which the post addresses only partly. Pull requests are reviewed by working groups, so the governance layer remains, but a standards catalogue that accepts community edits has to reconcile open contribution with the membership structure that funds and staffs the groups. The organisation has been willing to enforce specification boundaries in the past: it publicly challenged Prebid over transaction identifier changes in August 2025, stating that the modifications materially violated OpenRTB. Enforcement of that kind does not become easier when the specification text is editable by proposal.

There is also the matter of what a living document means for compliance. Certification programmes, vendor contracts and regulatory filings tend to cite fixed versions. A specification that can be corrected the same day is more accurate and less stable, and reconciling those two properties falls to the implementers rather than to the format.

Why this matters for the industry

Standards bodies rarely make news with a hosting decision. This one lands in the middle of a year in which the organisation has shipped an unusual volume of new technical work: the Agentic RTB Framework opened for public comment in November 2025, the Deals API followed in December, programmatic auction definitions went to comment on January 29, 2026, the Content Monetization Protocol followed on March 10, bot and crawler management guidance opened on May 27, and the conversion API standard was finalised in May. Each of those documents will be read by systems as well as people.

The agentic layer sharpens the point. The Agent Registry reached ten entries on March 11, 2026, all of them Model Context Protocol servers. In August, the organisation's chief operating officer counted thirteen functions where its own agentic framework overlaps with the rival Ad Context Protocol, a span covering most of a media buy. Where two competing protocol families describe the same functions, the ability of a machine to fetch the current, canonical definition of a field becomes a competitive property of the standard itself, not a publishing detail.

Distribution format is also a proxy for something harder to measure, which is whether a specification is maintained at all. A catalogue in which some entries were last touched in 2017 and others three times in a fortnight tells implementers where the work is happening. Under the document model, that signal was buried in a release date column. In a repository, it is the commit history, and it cannot be edited into looking better than it is.

None of this resolves the adoption problem that has followed interoperability standards for a decade. A specification hosted in Markdown is no more adopted than the same specification hosted as a file. What changes is the cost of finding out what the specification currently says, for a developer, for an auditor, and now for an agent executing a media buy without a person watching.

Timeline

Summary

Who: IAB Tech Lab, the technical standards body for digital advertising, in a post by Barnaby Edwards, senior director of product marketing. The change affects publishers, advertisers, demand-side and supply-side platforms, consent management providers and measurement vendors who implement the organisation's specifications, along with the working groups that write them.

What: A transition of technical standards and documentation from static PDF files to Markdown hosted on GitHub, making the repository the primary reference text between formal releases. Corrections can be applied immediately, version differences are exposed through releases and tags, questions are raised as public issues, and community edits arrive as pull requests for working group review. Final snapshots for implementation continue to be published.

When: Set out today. The GitHub account currently holds 77 public repositories with 443 followers, with dated updates across five specification repositories falling between August 5 and August 11, 2026.

Where: The organisation's GitHub account, IAB TechLab, which hosts repositories including OpenRTB, VAST, AdCOM, the GDPR Transparency and Consent Framework, the Global Privacy Platform, the Accountability Platform and the Data Deletion Request Framework.

Why: According to IAB Tech Lab, files frozen at download force full version increments for minor corrections and produce version confusion, a problem that becomes acute when language models and agents consult specifications during automated trading and need to establish which final version applies. Repository hosting also makes specifications searchable, linkable at section level and open to public feedback without an email or a working group meeting.