- From: mark a. foltz <mfoltz@google.com>
- Date: Wed, 7 May 2014 16:53:01 -0700
- To: "Kostiainen, Anssi" <anssi.kostiainen@intel.com>
- Cc: Philipp Hoschka <ph@w3.org>, "public-webscreens@w3.org" <public-webscreens@w3.org>, Daniel Davis <ddavis@w3.org>
- Message-ID: <CALgg+HHGwruqg99QaNSq6BDH_PJY9AF3Kz7wFGGFckVEc9K_vg@mail.gmail.com>
Hi Anssi, Thank you for drafting the Webscreens WG charter. I have spoken with colleagues at Google and we have the following feedback: (1) The scope of the charter does not specifically mention the following scenarios: one page controlling the content on multiple displays, or multiple pages controlling content on a remote display (possibly across multiple user agents). We also want to ensure that the presentation can be controlled across page navigations in the same UA given some scope (e.g., origin scope). We feel these are necessary to have a usable and complete specification. (2) In the two-UA case, the charter hints that the software controlling the remote screen is capable of displaying arbitrary Web content. However, this is not always the case; there are a large number of devices (e.g., smart TVs, digital picture frames, set-top boxes) that can display a fixed set of "apps" or Web media types. As there are millions of these devices deployed, we feel the charter should be written so as not leave these out. (3) We want to ensure that the language does not restrict the method of screen discovery or control, which could be a variety of implementations, including the use of cloud services or the use of application specific screen discovery mechanisms. (4) The phase 2 scope - the definition of open network protocols for discovery, control, media streaming - is really an *implementation* specification and would be better handled in a different forum such as the IETF. Although the parties in the WG would likely have a direct interest, separating the two processes would result in a W3C spec that is focused on the API and requirements, and a network protocol suite that could interoperate across software platforms (including native desktop and mobile apps). There are prior models for a similar spec process such as WebRTC and Push API. I plan to send a pull request with a set of suggested edits based on the above (after hearing any feedback you might have). Yours, Mark On Mon, May 5, 2014 at 7:19 AM, Kostiainen, Anssi < anssi.kostiainen@intel.com> wrote: > Hi All, > > On 23 Apr 2014, at 11:33, Philipp Hoschka <ph@w3.org> wrote: > > > There was big interest in enabling second screen applications at the > recent Web+TV workshop > > http://www.w3.org/2013/10/tv-workshop/ > > > > Given this, and the good progress in the Second Screen Presentation CG, > we seem to have enough momentum to bring the work of this CG into W3C > standardization, that is, form a Working Group. > > > > I discussed this idea with some of you, and received very positive > feedback, including a volunteer for charter writing :) > > As promised, the initial draft of the proposed Second Screen Presentation > Working Group Charter is now available for your review at: > > http://webscreens.github.io/charter/ > > All - your comments and contributions are welcome. > > As you can see, there is a bunch of TBDs especially looking for your input > and contributions. To help frame the discussion, the Scope and Deliverables > sections are further split into Phase 1 and Phase 2 subsections. We do not > need to maintain this separation, it is an aide to help us separate the > concrete CG deliverables used as a starting point for the WG’s work (“Phase > 1”), from the work that have been discussed in the Community Group, but for > which no concrete deliverables exists yet (“Phase 2”). > > The Charter draft is on GitHub (https://github.com/webscreens/charter) to > allow people to make direct contributions to the Charter using pull > requests. Of course, you can also suggest changes by replying to this > thread. > > Thanks, > > -Anssi > -- http://wiki/Main/OnlyCheckEmailTwiceADay
Received on Wednesday, 7 May 2014 23:53:49 UTC