- From: Francois Daoust <fd@w3.org>
- Date: Fri, 27 Nov 2015 12:32:57 +0100
- To: <public-tvapi@w3.org>, "Sangwhan Moon" <sangwhan@iki.fi>
[Re-sending as I forgot to include Sangwhan in the recipients list] > -----Original Message----- > From: Francois Daoust [mailto:fd@w3.org] > Sent: Friday, November 27, 2015 12:30 PM > To: 'public-tvapi@w3.org' <public-tvapi@w3.org> > Subject: WG draft charter and Phase 2 proposals > > Hello TV Control API CG participants, > > The CG is currently working in parallel on technical use cases for a Phase 2 > [1] and on a draft charter for a possible TV Control Working Group [2]. > > The timeline proposed in the draft WG charter is very tight, aiming at a final > Recommendation early 2017. Experience suggests that it would be > unrealistic to expect that the scope of the current spec may change > drastically within that time frame: if it gets created, the working group will > only have time to "finalize" the spec (add missing bits, fine-tune the API > based on implementation feedback, create the test suite). > > So, the question is: which of the phase 2 proposals should be included in the > draft WG charter and which should remain topics that the CG would want to > explore? > > Looking at Phase 2 proposals: > > > Handling of non-TV "channels" (such as HDMI inputs). > ----- > This is currently in scope of the draft WG charter. > However, it does not map directly to the notion of tuner, channel and > program currently defined in the spec. > I wonder if it could not be addressed in a future revision of the spec and/or > perhaps even in a separate spec that the CG could define. > > Sangwhan, I think this feature was added based on your feedback, what is > your take on this? > > > Security and privacy requirements > ----- > This is in scope of the draft WG charter, and a common expectation for > Working Groups at W3C. > I note that the draft charter leaves the possibility to define a second > conformance level in the spec for features that might perhaps be more > specific to tuner-centric devices and that could perhaps run under a different > security model. > > > Broadcast radio > ----- > This is currently in scope of the draft WG charter. > This may require some changes to the API, although hopefully restricted to a > few adjustments. > There have been discussions with the Media Tuner Task Force of the > Automotive BG in the past which shows interest to address radios as well, so > I would leave it in. > > > Interactive application signalling > ----- > The draft WG charter is not really clear on this. That's an important topic to > address. However, it does not seem trivial to me as it touches on the notion > of application lifecycle. > Is there any preliminary proposal that would describe how it could be > addressed in a Web application? > If not, I would suggest to leave it out of the charter for the time being. > > > Thanks, > Francois. > > [1] > https://www.w3.org/community/tvapi/wiki/Main_Page/Phase2_Technical_U > se_Cases > [2] http://w3c.github.io/charter-drafts/tvcontrol-2015.html
Received on Friday, 27 November 2015 11:33:08 UTC