- From: Kostiainen, Anssi <anssi.kostiainen@intel.com>
- Date: Mon, 8 Jun 2015 09:11:48 +0000
- To: Francois Daoust <fd@w3.org>, "mark a. foltz" <mfoltz@google.com>
- CC: "public-secondscreen@w3.org" <public-secondscreen@w3.org>
Hi MarkFo, Francois, > On 08 Jun 2015, at 11:24, Francois Daoust <fd@w3.org> wrote: [...] >> As part of the process of exposing the API, the Chrome Web platform team >> usually wants to see a W3C TAG review of the specification requested or >> in progress. > > Side process note in case people are wondering: asking the TAG to review our spec is not required per process as such. [...] Francois - I think the trigger for this TAG review comes from the "Intent-to-Ship" process of Blink, see [1]. Mark - correct? The W3C Process itself does not require a TAG review, although conducting such a review is recommended as Francois explained. I guess we should expect these Blink initiated TAG reviews to happen earlier than those (optionally) triggered by the W3C Process at wide review since there's tendency to ship things early to the developer channel. I agree that the list of tasks proposed by Francois would make the spec easier to digest for someone not actively following the work (e.g. a TAG member). However, given the spec is still relatively fresh, this TAG review would be more about asking for TAG input and thus open questions should be highlighted in the spec to set the expectations right. I agree a good procedural milestone to reach before requesting the TAG review would be to publish a new snapshot of the spec in the "TR space". Thanks, -Anssi (WG chair) [1] https://lists.w3.org/Archives/Public/www-tag/2015Apr/0019.html
Received on Monday, 8 June 2015 09:12:33 UTC