[tvcontrol-api] More flexible presentation restrictions requirement?

tidoust has just created a new issue for 
https://github.com/w3c/tvcontrol-api:

== More flexible presentation restrictions requirement? ==
I obviously do not qualify as content publisher but I wonder whether 
the [Presentation 
restrictions](https://www.w3.org/wiki/TV_Control/Use_Cases#Presentation_restrictions)
 use case could be loosened a bit. As described, it suggests that an 
arbitrary Web app may not be able to see any channel at all.

A possible rephrasing: "In order to ensure a consistent user 
experience, as a content publisher I want to allow TV content to be 
rendered on any web application but only allow access and manipulation
 of content on web domains that are authorised to do so."

The resulting requirement would then be slightly different: "The API 
allows presentation of audio and video media on all web domains. 
However, the API only allows access to and modification of the content
 of media tracks to some web domains."

[Isolated Media 
Streams](https://w3c.github.io/webrtc-pc/#isolated-media-streams), 
defined in WebRTC, would typically match the first part of the 
requirement, allowing arbitrary web applications to render a 
MediaStream in a `video` or `audio` tag without having access to any 
of its internals (essentially, the MediaStream is considered CORS 
cross-origin content)

The `peerIdentity` concept would need to be adjusted to the tuner case
 to meet the second part of the requirement, of course. I'm not sure a
 whitelisting mechanism is possible on the Web, but if there's a way 
to associate an origin with a MediaStream coming from a tuner, the 
usual same-origin policy could work (e.g. if the MediaStream is 
identified as "bbc.co.uk", then "bbc.co.uk" web applications fully can
 manipulate it, while others can only render the stream.


Please view or discuss this issue at 
https://github.com/w3c/tvcontrol-api/issues/13 using your GitHub 
account

Received on Tuesday, 9 August 2016 13:45:51 UTC