- From: mg4news via GitHub <sysbot+gh@w3.org>
- Date: Sat, 01 Oct 2016 17:24:30 +0000
- To: public-tvcontrol@w3.org
The notion of exposing underlying resources always surprises me. I would assume one of the goals of this working group would be to be aligned with video tag syntax. My organisation has taken the position that you need to know the answer to two questions: - is it possible for the system to play this content (broadcast origin tuner type x, codec type y, etc), i.e. pure capability - can it be played now Either tuners are irrelevant, OR all possible types of resources are relevant, in which case exposing tuner APIs is simply the start of a long trip down the rabbit hole. The approach we take is to expose a simple play( SRC, DST ) command. The URI of the SRC & DST defines what needs to happen, the underlying system manages the allocation, yielding, locking, unlocking, etc of resources, and the application remains logically simple. Priority rules are applied [configurably] in the system (application hierarchy, most recent wins, etc) and request types themselves become the resources (i.e. LIVE, HN share, PLAYBACK, etc) This ends up with a system completely compatibly with video tags, and something that does not start from the perspective of trying to wrap a legacy STB in W3C syntax. -- GitHub Notification of comment by mg4news Please view or discuss this issue at https://github.com/w3c/tvcontrol-api/issues/3#issuecomment-250924890 using your GitHub account
Received on Saturday, 1 October 2016 17:24:37 UTC