search

w3c / tvcontrol-api

TV Control API specification - https://w3c.github.io/tvcontrol-api/
10 stars 11 forks source link

Parallel with WebRTC model #20

Open tidoust opened 7 years ago

tidoust commented 7 years ago

The TAG notes:

The spec envisions two scenarios: Controlling a TV/DVR and controlling TV playback through a <video> tag

  • The WebRTC model has many parallels in regards to the objects/structures used to both find media and consume the media. Unlike RTC end-points, TV controllers do not need to negotiate for discovery because a client can know whether a local TV tuner is installed. However, from the POV of the Tuner, there is still an entire channel/program/stream discovery that must take place--and that's where we start to see many parallels. If we consider integrating the TVTuner (and related interfaces) into an object that is obtained from a negotiation with something on the server that is producing the media, then that object becomes a central control point from which APIs can be defined that configure/constrain that stream. (It also allows ambiguity for the TVTuner to be either a local or remote/network based source--in a similar way to how RTC MediaStreams represent either local camera/mic control sources or over-the-network remote streams). https://github.com/w3ctag/spec-reviews/issues/111#issuecomment-257746605