The Advertising WG Call focused on developing a common ad interface for video players. Casey Occhialini discussed the need for a standardized API to handle ad playback, drawing on experiences with Google, FreeWheel, and custom in-house solutions. The group explored terminology consistency, such as using “pods” or “slots” for ad units, and the importance of supporting both linear and non-linear ad formats. David Hassoun presented a proposal for overlay presentations in DASH and HLS, emphasizing the need for custom layout control and addressing challenges like aspect ratio scaling. The team plans to refine the proposal and seek feedback from IAB.
- Prepare and share research and initial design documents for the Common Ad Interface, including consolidated findings from analysis of existing player APIs, and distribute drafts to the group on roughly a two-week cadence, with the first concrete version available before the next meeting.
- Review the initial Common Ad Interface design draft with Christian to gather feedback and identify any issues with the chosen approach.
- Check the SVTA Drive for any existing ad terminology and diagrams documents and consult with Zack to see if anything useful exists for the Common Ad Interface work.
- Send Casey example implementations or samples of in-scene ads from the existing Ivy system so he can better understand that use case for the Common Ad Interface design.
- Arrange and hold a meeting with the DASH group to align on the proposed overlay/concurrent presentation layout changes, including how default layouts versus custom layouts and related attributes (such as z-depth) should be specified.
- Update the SVTA DASH/HLS layout proposal documentation to reflect the newer IAB layout specification and its improved breakdown of default layout values.
- Revise the proposed layout and scale behavior in the SVTA concurrent presentation model and update the layout tester application to support the new viewport-based layout approach and correct handling of different aspect ratios.
- Continue efforts to bring IAB involvement into SVTA by engaging the relevant IAB contacts and inviting appropriate IAB representatives into this working group and the metadata working group.
- Antitrust Statement and WG Discussion
Advertising WG Call Introduction and Agenda
- David Hassoun opens the meeting, mentioning the SVTA antitrust statement and the usual housekeeping items.
- David notes the absence of Olivier, who is on vacation before NAB, and wishes everyone a happy tax day in the US.
- The agenda includes discussions on the common ad interface and ad creative signaling.
- David mentions the next meeting on April 29 and the ongoing work with the DASH work group.
Common Ad Interface Discussion
- Casey Occhialini introduces the concept of a common ad interface, inspired by the video.js 10 player.
- Casey explains the need for a set of APIs to expose UI elements, events, and state tracking for ad playback.
- Casey compares the common ad interface to the CMAF Ham interfaces, which provide a common model for video manifests.
- Casey seeks input from the group on current ad player interfaces and common terminology, such as slots, pods, and SSI.
Exploring Ad Interface Terminology and Standards
- David Hassoun and Casey discuss the terminology used by different ad providers and the need for common terms.
- Casey mentions the dash HLS interop spec as a reference for common terminology.
- David and Casey discuss the importance of not reinventing the wheel and leveraging existing standards.
- Casey highlights the need for a normalized ad interface that can handle both linear and non-linear use cases.
Ad Format and Trigger Types
- David Steinacher shares his experience with implementing SGI with HLS interops and the challenges of concurrent ad formats.
- David Hassoun suggests terms like “ad period” and “interstitial” for describing ad breaks.
- Casey and David discuss the need for a trigger type property to differentiate between time-based and external asset-triggered ads.
- Casey mentions the importance of keeping the API surface minimal and flexible for different ad formats.
IAB Involvement and Research Documents
- Sarge Sargent mentions efforts to get IAB involved in SVTA and the potential for IAB members to join the working group.
- Casey is working on research documents to gather commonality across player APIs and provide a concrete design for the common ad interface.
- Christian Pillsbury emphasizes the importance of normalizing around IAB standards to avoid deviations.
- David Hassoun suggests providing a list of questions or feedback to IAB for further input and alignment.
Layout Control and Custom Ad Formats
- David Hassoun presents a proposal for layout control in DASH and HLS, including new overlay and replace presentations.
- The proposal includes preset positioning configurations defined by IAB and a custom layout option for full control.
- David discusses the challenges of handling different ad formats and the need for a flexible layout system.
- Casey suggests using a viewport property with four coordinates to describe both position and size for ad and content viewports.
Feedback and Next Steps
- Christian Pillsbury and David Steinacher provide feedback on the layout proposal, highlighting the need for clear definitions and handling of different aspect ratios.
- Casey and David discuss the potential for using CSS box model properties for layout control.
- David plans to update the Tester app and gather feedback on the proposed layout system.
- The meeting concludes with a commitment to continue working on the common ad interface and layout control, with the next update expected in two weeks.
Next Meeting: Wednesday, April 29, 2026 8am PDT
Links shared in Zoom Chat:
https://videojs.org/
https://docs.google.com/document/d/11NzcMHA8c1dLRnXhXRvMZaokTOB5gR14EXJnDAlpySI/edit?tab=t.0#heading=h.nto1f0dzmfo3
IAB VMAP spec defines it as AdBreak
https://www.IAB.com/wp-content/uploads/2015/06/VMAP.pdf
https://docs.google.com/document/d/1QkQVy1GCQz9kmKlcb1vNRbDyzwv6IEHLcydLGwnndRA/edit?tab=t.0#heading=h.ibspq3gxqtio
https://docs.google.com/document/d/1CWm1BP65h45iJ5RwCAQkUAZ6lz7f-w3qJRGMdH8DDdQ/edit?tab=t.x2hudn1ltnpd
https://docs.google.com/document/d/16CZO5Q2WXwXOK7pVQm03crS0W20l8LxP/edit?pli=1#heading=h.gjdgxs
You were thinking about CSS position (https://developer.mozilla.org/en-US/docs/Web/CSS/Reference/Properties/position )