[Bug 21333] consequences of requirement in section 8 on initialisation segments

https://www.w3.org/Bugs/Public/show_bug.cgi?id=21333

Kevin Streeter <kstreete@adobe.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kstreete@adobe.com

--- Comment #14 from Kevin Streeter <kstreete@adobe.com> ---


> I think this is a bad idea. Ad providers won't do this if we don't let them.
> I don't think this will simplify things. You would still have to provide
> mappings for how the selected tracks change over time. This mapping would be
> particularly fragile if the application allowed any sort of access to the
> video element xxxTracks lists. Allowing track count & type changes within a
> SourceBuffer also open a can of worms with reguard to how to map tracks with
> eachother across these boundaries. 
> 

Unfortunately a publisher doesn't always have a lot of control over the ad
provider.  

While often a publisher will use "1st party" ads that they encode (meaning they
can make sure its matches their content), almost all publishers have a lot of
unsold ad inventory in their streams.  Publishers will use ad networks and
other 3rd-party sources of ad content to fill the remnant inventory.

When using a 3rd-party source for ads the publisher has no connection to the ad
provider, and no way to enforce that the ad content matches the primary
content.  These restrictions will essentially make it impossible to use
3rd-party sources for ads.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Sunday, 31 March 2013 16:44:20 UTC