Re: Heads-up: Summary of the Web-Based Signage WG Charter discussion so far

Dear Shigeya,

Thank you for summarizing the current situation!

Could you clarify when we need to conclude the discussion as you mentioned?

For example, is it alright to discuss the use cases for remote prompting  
and clock management in new WG?

Best regards,
Kiyoshi
---
Kiyoshi Tanaka, Ph.D.
   NTT Service Evolution Laboratories
   mailto:tanaka.kiyoshi@lab.ntt.co.jp


On 2016/07/12 18:34, Shigeya Suzuki wrote:
> Dear Web-Based Signage Business Group Attendees,
>
> I have created this summary of the discussion so far, to present the current state of the charter. Please read and comment. We want to finalize the charter quickly, to have the first face-to-face meeting at TPAC.
>
>
> * Introduction
>
> This summary of the discussion summarizes the discussions after we started sharing Web-Based signage Draft Charter on Github[G], compiled by Shigeya Suzuki, one of the W3C Team staff.
>
> After the draft Web-Based Signage Charter was uploaded on GitHub[DG] and the announcement by Tanaka-san was posted[D5], we got several comments from the W3C Management and the Web Accessibility Initiative Team. Now we have updated the draft Charter based on those comments, and would like to let you all know about the updated draft.
>
> Please note that even though most of the comments are editorial ones, some of them require us a bit detailed discussion to clarify our position.
>
> The following is the list of topics we want to make sure:
>
> * Chronological order of the events related to the Charter
>
> On BG Mailing list, following drafts are announced:
>
> - 2015/10/23 Draft 1 [D1]
> - 2015/12/17 Draft 2 [D2]
> - 2015/1/26 Draft 3 [D3]
> - 2016/2/8 Draft 4 [D4]
> - 2016/3/3 Draft 5 [D5]
>
> On the draft 5, we moved the draft to W3C's charter draft page on the Github's[DG].
>
> On 2016/3/30, W3M approved to send the "advance notice". Also, reviews by W3M and WAI group has provided. We have changed draft due to the reviewers' comments.
>
> Followings are the fixes we have made after draft 5. Fixes are Github pull-request consists of multiple git commits so that you can find the modification history from GitHub.
> .. Followings are the list showing commits each of fixes includes:
>
> - 2016/5/10 [FIX1]
>   - Removing some groups from Coordination list (*1)
>
>   (*1) To limit to closely related group
>
> - 2016/5/31 [FIX2]
>   - Editorial fix
>   - Updating team contact (*2)
>
>   (*2) Shigeya Suzuki appointed by W3M
>
>
> - 2016/6/1 [FIX3]
>   - Web-based Signage: Update chair name (*3)
>   - Web-based Signage: removing todo tag from team contact description
>   - Web-based Signage: Eliminating all of empty links on deliverables
>   - Web-based Signage: removing reference to Second Screen Presentation WG (*4)
>   - Web-based Signage: removing clock configuration related discussion/deliverables (*5)
>
>   (*3) Kiyoshi Tanaka picked as a chair
>   (*4) See item (c) below on "Coordination."
>   (*5) See item (b) below on "Clock Management API."
>
> (Note: the "advance notice" sent to AC on 2016/5/16.)
>
> Now, [FIX1] and [FIX2] are editorial fixes, but [FIX3] includes non-editorial changes. Of course, these changes reflect some thoughts among the group who drafted the charter, but not a consensus among BG.
>
>
> * Issues need to be resolved within BG
>
> The issues we want to discuss here are:
> a) Discussion on deliverables "Remote Prompting."
> b) Discussion on "Clock Management API."
> c) "Coordination" section
>
>
> In the draft, there were four Web Remote Management API as deliverables in Draft 1 through 5. They are:
>     1) Power Management
>     2) Clock Management
>     3) Remote Prompting
>     4) Other Contextual Information
>
> On the Power Management and Other Contextual Information, we have not gotten any review comments, yet.
>
>
> Following are description of these three issues:
>
> (a) "Remove Prompting" API
>
> We need to find the use cases of this API.
>
> In the charter, we wrote: "In a case of malfunctions or other signage terminal prompts requiring user interaction, an API needs to define to where the prompt needs to be shown because audiences of the signage terminal device cannot answer for the dialog. This function will be consulted with use case discussion."
>
> Also, in the scope section, we wrote: "The operators want to manage the signage UA via their web console of the controlling device. Operators want to use the following functions:
> - Start/Stop the UA
> - Open/Close a page
> - Reboot the UA
> - Accept/Reject when the UA prompts for a user confirmation required for security reasons."
>
> Reviewer commented that those same functionalities could be achievable using Web Driver, [WD1][WD2][WD3][WD4][WD5][WD6], or possibly with Browser Testing and Tools.
>
> We have discussed locally and found that we need to find/agree on the use cases for this deliverable. Depends on the use cases, we may use, or possibly add glue to achieve the needed functionality on top of Web Driver. Alternatively, we want to define completely independent API.
>
> Additionally, the discussion of this deliverable may require security considerations. For example, in the scope, we stated 'required for security reasons' as above. (Note that, the original text was 'required under the standard security model' in earlier drafts, modified for clarification)
>
>
> (b) "Clock Management" API
>
> We need to define what we want to implement with this Clock Management API. We probably want to find use cases.
>
>>From the use cases and requirements of clock management for Web-based signage, our consensus was that we are focusing on "configuration", such as NTP, and not on "inter-device/screen timing control", as we discussed in the F2F BG on TPAC 2015.
>
> However, later, we found that there are conflicting opinions whether a browser should have configuration API for NTP. For reflecting the W3M review comments, I have decided to remove "Clock Management" deliverable on [FIX3] for the time being.
>
> Please refer [FIX3DIFF] for actual change on [FIX3].
>
>
> (c) "Coordination" section
>
> We need to see whether current coordination section is well enough or not. We may need to modify this section according to the discussion on above two deliverables.
>
> Until Draft 5[DG], there was a long list of W3C Groups in the Coordination section. We have removed weakly related groups in [FIX1]. Moreover, also, removed "Second Screen", since we envisioned to have smartphone links, but eliminated this because we have not (and can't easily) define deliverables.
>
> Please refer [FIX1DIFF] for actual change on [FIX1].
>
>
> * Schedule
>
> Followings are milestones towards working group creation. Please refer to the latest "How to Create a Working Group or Interest Group"[CWG] for further reference.
>
> 1. W3M approval
> 2. Advisory Committee Review of the Charter
> 3. Director Decision
>
>
> After resolving all issues stated here, and there are no further issues raised by W3M, the charter will be approved by W3M.
>
> We hope to initiate Advisory Committee Review by the middle of July. AC review duration is usually four weeks. If all goes well, we will see director's decision by the end of the August, and we hope to have the first F2F meeting of Web-based Signage WG in TPAC 2016!
>
>
> * References
>
> [DG] http://w3c.github.io/charter-drafts/web-based-signage-2016.html
> [E1] tanaka.kiyoshi@lab.ntt.co.jp
> [E2] futomi.hatano@newphoria.co.jp
> [E3] ashimura@w3.org
> [E4] shigeya@w3.org
> [E5] public-websignage@w3.org
>
> [D1] https://lists.w3.org/Archives/Public/public-websignage/2015Oct/0019.html
> [D2] https://lists.w3.org/Archives/Public/public-websignage/2015Dec/0000.html
> [D3] https://lists.w3.org/Archives/Public/public-websignage/2016Jan/0000.html
> [D4] https://lists.w3.org/Archives/Public/public-websignage/2016Feb/0010.html
> [D5] https://lists.w3.org/Archives/Public/public-websignage/2016Mar/0005.html
>
> [FIX1] https://github.com/w3c/charter-drafts/pull/73
> [FIX2] https://github.com/w3c/charter-drafts/pull/76
> [FIX3] https://github.com/w3c/charter-drafts/pull/77
> [FIX1DIFF] https://github.com/w3c/charter-drafts/pull/73/files
> [FIX2DIFF] https://github.com/w3c/charter-drafts/pull/76/files
> [FIX3DIFF] https://github.com/w3c/charter-drafts/pull/77/files
>
> [AN] https://lists.w3.org/Archives/Member/w3c-ac-members/2016AprJun/0043.html
>
> [WD1] https://www.w3.org/TR/webdriver/#new-session
> [WD2] https://www.w3.org/TR/webdriver/#delete-session
> [WD3] https://www.w3.org/TR/webdriver/#go
> [WD4] https://www.w3.org/TR/webdriver/#close-window
> [WD5] https://www.w3.org/TR/webdriver/#accept-alert
> [WD6] https://www.w3.org/TR/webdriver/#dismiss-alert
>
> [CW] http://www.w3.org/Guide/Charter
>
>
> Shigeya Suzuki, Ph.D
> Keio University / WIDE Project / W3C
> = / shigeya@wide.ad.jp / shigeya@w3.org

Received on Wednesday, 20 July 2016 06:29:41 UTC