The Open Advertising Protocol defines the standards for electronically buying and selling advertising inventory. Although the initial application is in digital advertising, it has potential application in offline advertising as well.
For a high-level view of the protocol, see the Open Advertising Protocol Diagram (PDF). In reviewing the diagram, you'll notice there are two sides to the protocol: (1) a buy side and (2) a sell side. Each side has it's own API.
The OAP Buyer API is the interface sellers use to connect with buyers. Sellers can use this to publish information about their advertising programs in the buyer's system. They can use it to download orders and to update the status of those orders.
The OAP Seller API is the interface buyers use to connect with sellers. Buyers can use this to get up-to-the-minute information on advertising programs, inventory, and pricing. Buyers can use it to place orders witn the seller, to modify orders, and to get current status of orders.
The OAP Model describes the electronic documents that are passed back and forth between buyers and sellers such as insertion orders. The model is described using XML Schema Language because of its expressiveness and widespread availability of tools to work with XML schemas. Beyond obvious application with XML documents, the model is also intented to represent JSON documents.
As of December 18, 2013, the OAP is still in development. The plan is to finalize the minimum viable product protocol (as shown in the overview diagram) January 2014 and to complete initial reference implementations in March 2014.
Beyond that, we plan to complete the invoice and other parts of the protocol in stages.
... and growing! Please let us know if you want to participate.
Follow Github's recommended workflow for contributing to this project.
- Fork it
- Create your feature branch (
git checkout -b your-new-feature) - Commit your changes (
git commit -am 'Add some feature') - Push to the branch (
git push origin your-new-feature) - Create new Pull Request