How openrtb/examples works
Main Components
• OpenRTB Examples Repository (as the central hub)
• Brandscreen: Contains multiple JSON files that serve as example requests and responses for mobile and PC ad scenarios.
• Rubicon Project: Includes various JSON examples (for Android apps, web on IE8, iPhone, Safari) illustrating different request scenarios.
• Spotxchange: Features Markdown files that provide examples of video requests and responses with single and multiple impressions.
Relationships & Interactions
• Three distinct branches stemming from the central component:
b. Rubicon Project branch with its various example JSON files.
Architectural Patterns & Design Choices
• That the repository is organized by vendor/platform. This represents a form of modular organization where each module (directory) is self-contained.
• The files reflect consistency in naming (e.g., “example-request” and “example-response”) which aligns with documentation best practices for sample code.
• Although it’s not a running application, treat each component as an independent module that could be tested or referenced individually, showcasing separation of concerns.
Relevant Technologies & Purposes
• JSON: Used as the primary data format for request and response examples.
• Markdown: Present in the Spotxchange directory for more readable examples and additional notes.
• OpenRTB Specification: This is the underlying standard guiding the formatting of these examples.