Add the Ad Context Protocol (AdCP) amendment for tdl labelling - #9
Open
jwrosewell wants to merge 2 commits into
Open
Add the Ad Context Protocol (AdCP) amendment for tdl labelling#9jwrosewell wants to merge 2 commits into
jwrosewell wants to merge 2 commits into
Conversation
Applies the Data Labels approach to the agentic advertising protocols, where autonomous agents exchange hashed identifiers, audience segments and attribution identifier sets in JSON documents over MCP and A2A. Any object in a task request or response can carry a tdl array with the usual inheritance, replacement and filtering rules, and because AdCP signs messages with RFC 9421 the labels arrive with proof of who attached them. Includes the one shared JSON Schema definition needed, and notes the same field serves the IAB Tech Lab AAMP protocols. Drafted with AI assistance and needs human review before merging.
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
1 participant
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.
Adds AdCP.md, applying the Data Labels approach to the agentic advertising protocols, and links it from the README beside the other dependent standards.
AdCP tasks move exactly the data whose terms matter most, with sync_audiences carrying hashed emails and identity-graph tokens, get_signals returning segments offered for activation, and log_event carrying attribution identifier sets, all as JSON documents over MCP and A2A (AdCP documentation). The amendment follows the OpenRTB deployment exactly, any object can carry a tdl array, ancestors apply to descendants, a descendant tdl replaces the ancestor, and recipients filter by masks. Two additions specific to AdCP, the labels compose with the protocol's RFC 9421 message signatures so they arrive with proof of who attached them, and one shared JSON Schema definition covers every task including future ones. The closing section notes the same field serves the IAB Tech Lab AAMP protocols, whose Agentic Audiences component already contemplates permissible uses and a time-to-live for consented data.
Drafted with AI assistance from the AdCP 3.1 documentation and schemas, and needs human review before merging.