forked from w3c/charter-drafts
/
web-based-signage-2016.html
429 lines (344 loc) · 21 KB
/
web-based-signage-2016.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8" />
<title>Web-based Signage Working Group Charter</title>
<link rel="stylesheet" href="https://www.w3.org/2005/10/w3cdoc.css" type="text/css" media="screen" />
<link rel="stylesheet" type="text/css" href="https://www.w3.org/Guide/pubrules-style.css" />
<link rel="stylesheet" type="text/css" href="https://www.w3.org/2006/02/charter-style.css" />
<style type="text/css">
ul#navbar {
font-size: small;
}
dt.spec {
font-weight: bold;
}
dt.spec new {
background: yellow;
}
ul.out-of-scope > li {
font-weight: bold;
}
ul.out-of-scope > li > ul > li{
font-weight: normal;
}
.issue {
background: cornsilk;
font-style: italic;
}
.todo {
color: red;
}
footer {
font-size: small;
}
</style>
</head>
<body>
<header id="header">
<aside>
<ul id="navbar">
<li><a href="#scope">Scope</a></li>
<li><a href="#deliverables">Deliverables</a></li>
<li><a href="#coordination">Coordination</a></li>
<li><a href="#participation">Participation</a></li>
<li><a href="#communication">Communication</a></li>
<li><a href="#decisions">Decision Policy</a></li>
<li><a href="#patentpolicy">Patent Policy</a></li>
<li><a href="#licensing">Licensing</a></li>
<li><a href="#about">About this Charter</a></li>
</ul>
</aside>
<p>
<a href="https://www.w3.org/"><img alt="W3C" height="48" src="http://www.w3.org/Icons/w3c_home" width="72" /></a>
<a class="domainlogo" title="domain:ubi" href="http://w3.org/UbiWeb/"><img src="http://www.w3.org/Icons/ubi212" alt="Ubiquitous Web Domain"></a>
</p>
</header>
<main>
<h1 id="title">Web-based Signage Working Group Charter</h1>
<p class="mission">The <strong>mission</strong> of the <a href="">Web-based Signage Working Group</a> is to provide methods to user agents embedded in digital signage terminal devices.</p>
<div class="noprint">
<p class="join"><a href="https://www.w3.org/2004/01/pp-impl/#####/join">Join the Web-based Signage Working Group.</a></p>
</div>
<section id="details">
<table class="summary-table">
<tr id="Duration">
<th>
Start date
</th>
<td>
<i class="todo">[dd monthname yyyy] (date of the "Call for Participation", when the charter is approved)</i>
</td>
</tr>
<tr id="Duration">
<th>
End date
</th>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
Kiyoshi Tanaka
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<a href="mailto:shigeya@w3.org">Shigeya Suzuki</a> (0.1 <abbr title="Full-Time Equivalent">FTE</abbr>)
</td>
</tr>
<tr>
<th>
Meeting Schedule
</th>
<td>
<strong>Teleconferences:</strong> topic-specific calls may be held
<br />
<strong>Face-to-face:</strong> we will meet during the W3C's annual Technical Plenary week; additional face-to-face meetings may be scheduled by consent of the participants, no more than 3 per year.
</td>
</tr>
</table>
</section>
<section id="scope" class="scope">
<h2>Scope</h2>
<p>The group will develop APIs for user agents (“UA”s hereafter) embedded in digital signage terminal devices (“devices” hereafter).</p>
<p>Two types of users exist. Device operators who remotely operate devices and Audiences who watch the devices. Device operators have access to UAs of devices. These operators typically do not have access to the devices physically. On the contrary, audiences, who are anonymous and in the general public, do not have control over devices.</p>
<p>The signage UA should provide Remote Management API to be controlled by device operators.</p>
<p>The operators want to manage the signage UA via their web console of the controlling device. Operators want to use the following functions:
<ul>
<li>Start/Stop the UA</li>
<li>Open/Close a page</li>
<li>Reboot the UA</li>
<li>Accept/Reject when the UA prompts for a user confirmation reuquired for security reasons</li>
</ul>
</p>
<p>These operations require protection mechanism to prevent unauthorized accesses.</p>
<p>In addition to above functions, the WG will develop functions which enable web applications to access a set of functions in the underlying operating system, such as:
<ul>
<li>Reboot the terminal device at operating system level</li>
</ul>
</p>
<p>Because, rebooting at the operating system level is useful for some trouble or emergency cases.</p>
<p>The specifications produced by this Working Group will address security and privacy considerations based on a security model different from the traditional browser security model, because the device UAs controlled by the device operators rather than the audiences watching the devices. The considerations need to address the combination of both the UAs and the controlling device.</p>
<p>Members of the Working Group should review other working groups' deliverables that identified as being relevant to the Working Group's mission.</p>
<div id="section-out-of-scope">
<h3 id="out-of-scope">Out of Scope</h3>
<p>The following features are out of scope, and will not be addressed by this working group.</p>
<ul class="out-of-scope">
<li>This Working Group will not define or mandate hardware specification of digital signage terminal devices.</li>
</ul>
</div>
<div>
<h3>Success Criteria</h3>
<p>In order to advance to <a href="https://www.w3.org/2015/Process-20150901/#RecsCR" title="Proposed Recommendation">Proposed Recommendation</a>, each specification is expected to have at least two independent implementations of each of feature defined in the specification.</p>
<p>Each specification should contain a section detailing any known security or privacy implications for implementers, Web authors, and end users.</p>
</div>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p><i>Draft state</i> indicates the state of the deliverable at the time of the charter approval. <i>Expected completion</i> indicates when the deliverable is projected to become a Recommendation, or otherwise reach a stable state.</p>
<div id="normative">
<h3>
Normative Specifications
</h3>
<p>
The working group will deliver the following W3C normative specifications:
</p>
<dl>
<dt id="web-foo" class="spec">Web Remote Management API</dt>
<dd>
<p>Remote Management API consists of following functions:</p>
<dl>
<dt id="web-rmapi-power-management" class="spec">Power Management</dt>
<dd><p>This function enables web applications to access the signage terminal device’s power management system. Restarting the underlying web runtime or rebooting the underlying operating system is useful for some use cases. Restarting the underlying operating system and rebooting the device can be used for the basic trouble shootings. By studying the use cases, the function will be consulted for enhancement. The protocol and data format for controlling the terminal would also be considered for the further discussion.<p></dd>
<dt id="web-rmapi-remote-prompting" class="spec">Remote Prompting</dt>
<dd><p>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.</p></dd>
<dt id="web-rmapi-other-contextual" class="spec">Other Contextual Information</dt>
<dd><p>The other functions besides the above are needed to enable web applications to get system-wide information of the digital signage terminal, such as screen state (power, brightness, colorimetry, color temperature) and memory information (RAM usage). Moreover, it is useful for web applications to prepare such functions as service workers which can interact with any windows (context/domains) or context with a privilege to access any windows and origins. These functions will be considered in further discussion with use cases.</p></dd>
</dl>
<p class="draft-status"><b>Draft state:</b> [No draft]</p>
<p class="milestone"><b>Expected completion:</b> <i class="todo">[Q1–4 yyyy]</i></p>
</dd>
</dl>
</div>
<div id="ig-other-deliverables">
<h3>
Other Deliverables
</h3>
<dl>
<dt>Use cases and requirements:</dt>
<dd><p>The Working Group is strongly encouraging the participants to create and maintain use cases and requirements document for each specification.</dd>
<dt>Implementation guidelines:</dt>
<dd><p>The group may provide informative guidelines for implementers to encourage its implementation.</dd>
</dl>
<p>
Other non-normative documents may be created such as:
</p>
<ul>
<li>Primers</li>
<li>Non-normative schema for language formats</li>
<li>Non-normative group notes</li>
</ul>
</div>
<div id="milestones">
<h3>
Milestones
</h3>
<table class="roadmap">
<caption>Milestones</caption>
<thead>
<tr>
<th>Specification</th>
<th><abbr title="First Working Draft">FPWD</abbr></th>
<th><abbr title="Candidate Recommendation">CR</abbr></th>
<th><abbr title="Proposed Recommendation">PR</abbr></th>
<th><abbr title="Recommendation">Rec</abbr></th>
</tr>
</thead>
<tbody>
<tr>
<th>Remote Management API</th>
<td>Q2 2016</td>
<td>Q4 2016</td>
<td>Q2 2017</td>
<td>Q4 2017</td>
</tr>
</tbody>
</table>
<p><em>Note: The actual production of some of the deliverables may follow a different timeline. The group documents any schedule changes on the <a href="@@">group home page</a></em>.</p>
</div>
</section>
<section id="coordination">
<h2>Coordination</h2>
<p>For all specifications, this Working Group will seek <a href="https://www.w3.org/Guide/Charter.html#horizontal-review">horizontal review</a> for accessibility, internationalization, performance, privacy, and security with the relevant Working and Interest Groups, and with the <a href="https://www.w3.org/2001/tag/" title="Technical Architecture Group">TAG</a>. Invitation for review must be issued during each major standards-track document transition, including <a href="https://www.w3.org/2015/Process-20150901/#RecsWD" title="First Public Working Draft">FPWD</a> and <a href="https://www.w3.org/2015/Process-20150901/#RecsCR" title="Candidate Recommendation">CR</a>, and should be issued when major changes occur in a specification.</p>
<p>Additional technical coordination with the following Groups will be made, per the <a href="https://www.w3.org/2015/Process-20150901/#WGCharter">W3C Process Document</a>:</p>
<div>
<h3 id="w3c-coordination">W3C Groups</h3>
<dl>
<dt><a href="http://www.w3.org/2002/mmi/">Multimodal Interaction Working Group</a></dt>
<dd><p>The Multimodal Interaction Working Group develops open standards that extend the Web to allow multiple modes of interaction which might be used by the Web-based Signage Working Group.</p></dd>
<dt><a href="http://www.w3.org/2011/webtv/">Web and TV Interest Group</a></dt>
<dd><p>The Web-based Signage Working Group intends to have its deliverables reviewed by the Web and TV Interest Group from the perspective of using TV as a Web-based signage terminal.</p></dd>
<dt><a href="http://www.w3.org/WoT/IG/">Web of Things Interest Group</a></dt>
<dd><p>The goal of the Web of Things Interest Group is to accelerate the development of open markets of applications and services based on the role of Web technologies for a combination of the Internet of Things (IoT) with the Web of data.</p></dd>
<dt><a href="https://www.w3.org/community/websignage/">Web-based Signage Business Group</a></dt>
<dd><p>The Web-based Signage Business Group studies profiles for web-based signage player as well as use cases and requirements of web-based signage.</p></dd>
</dl>
<h3 id="external-coordination">External Organizations</h3>
<dl>
<dt><a href="http://www.itu.int/en/ITU-T/studygroups/2013-2016/16/Pages/default.aspx">ITU-T SG16 Q14 (Q14/16)</a></dt>
<dd><p>ITU-T Q14/16 studies digital signage systems and services, and currently including the web-based architecture of digital signage.</p><dd>
<dt><a href="http://http://digital-signage.jp/">Digital Signage Consortium (DSC)</a></dt>
<dd><p>Digital Signage Consortium studies and develops the digital signage services and systems with its member companies including location owners (buildings, railways), content and service providers, and system integrators.</p><dd>
</dl>
</div>
</section>
<section class="participation">
<h2 id="participation">
Participation
</h2>
<p>
To be successful, this Working Group is expected to have 10 or more active participants for its duration, including representatives from the key implementors of this specification, and active Editors and Test Leads for each specification. The Chairs, specification Editors, and Test Leads are expected to contribute half of a day per week towards the Working Group. There is no minimum requirement for other Participants.
</p>
<p>
The group encourages questions, comments and issues on its public mailing lists and document repositories, as described in <a href='#communication'>Communication</a>.
</p>
<p>
The group also welcomes non-Members to contribute technical submissions for consideration, with the agreement from each participant to Royalty-Free licensing of those submissions under the W3C Patent Policy.
</p>
</section>
<section id="communication">
<h2>
Communication
</h2>
<p id="public">
Technical discussions for this Working Group are conducted in <a href="https://www.w3.org/2015/Process-20150901/#confidentiality-levels">public</a>. Meeting minutes from teleconference and face-to-face meetings will be archived for public review, and technical discussions and issue tracking will be conducted in a manner that can be both read and written to by the general public. Working Drafts and Editor's Drafts of specifications will be developed on a public repository, and may permit direct public contribution requests.
</p>
<p>
Information about the group (including details about deliverables, issues, actions, status, participants, and meetings) will be available from the <a href="">Web-based Signage Working Group home page.</a>
</p>
<p>
Most Web-based Signage Working Group teleconferences will focus on discussion of particular specifications, and will be conducted on an as-needed basis.
</p>
<p>
This group primarily conducts its technical work on the public mailing list <a class="todo" id="public-name" href="mailto:public-[email-list]@w3.org">public-<i class="todo">[email-list]</i>@w3.org</a> (<a class="todo" href="http://lists.w3.org/Archives/Public/public-[email-list]/">archive</a>). The public is invited to post messages to this list.
</p>
<p>
The group may use a Member-confidential mailing list for administrative purposes and, at the discretion of the Chairs and members of the group, for member-only discussions in special cases when a participant requests such a discussion.
</p>
</section>
<section id="decisions">
<h2>
Decision Policy
</h2>
<p>
This group will seek to make decisions through consensus and due process, per the <a href="https://www.w3.org/2015/Process-20150901/policies#Consensus"> W3C Process Document (section 3.3</a>). Typically, an editor or other participant makes an initial proposal, which is then refined in discussion with members of the group and other reviewers, and consensus emerges with little formal voting being required.</p>
<p>
However, if a decision is necessary for timely progress, but consensus is not achieved after careful consideration of the range of views presented, the Chairs may call for a group vote, and record a decision along with any objections.
</p>
<p>
To afford asynchronous decisions and organizational deliberation, any resolution (including publication decisions) taken in a face-to-face meeting or teleconference will be considered provisional.
A call for consensus (CfC) will be issued for all resolutions (for example, via email and/or web-based survey), with a response period from one week to 10 working days, depending on the chair's evaluation of the group consensus on the issue.
If no objections are raised on the mailing list by the end of the response period, the resolution will be considered to have consensus as a resolution of the Working Group.
</p>
<p>
All decisions made by the group should be considered resolved unless and until new information becomes available, or unless reopened at the discretion of the Chairs or the Director.
</p>
<p>
This charter is written in accordance with the <a href="https://www.w3.org/Consortium/Process/policies#Votes">W3C Process Document (Section 3.4, Votes)</a>, and includes no voting procedures beyond what the Process Document requires.
</p>
</section>
<section id="patentpolicy">
<h2>
Patent Policy
</h2>
<p>
This Working Group operates under the <a href="http://w3.org/Consortium/Patent-Policy-20040205/">W3C Patent Policy</a> (5 February 2004 Version). To promote the widest adoption of Web standards, W3C seeks to issue Recommendations that can be implemented, according to this policy, on a Royalty-Free basis.
For more information about disclosure obligations for this group, please see the <a href="https://www.w3.org/2004/01/pp-impl/">W3C Patent Policy Implementation</a>.
</p>
</section>
<section id="licensing">
<h2>Licensing</h2>
<p>This Working Group will use the <a href="https://www.w3.org/Consortium/Legal/copyright-documents">W3C Document license</a>> for all its deliverables.</p>
</section>
<section id="about">
<h2>
About this Charter
</h2>
<p>
This charter has been created according to <a href="https://www.w3.org/Consortium/Process/groups#GAGeneral">section 5.2</a> of the <a href="https://www.w3.org/Consortium/Process">Process Document</a>. In the event of a conflict between this document or the provisions of any charter and the W3C Process, the W3C Process shall take precedence.
</p>
</section>
</main>
<hr />
<footer>
<address>
<i class="todo"><a href="mailto:">[team contact name]</a></i>
</address>
<p class="copyright">
<a href="https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a> ©
<i class="todo">[yyyy]</i>
<a href="https://www.w3.org/"><abbr title="World Wide Web Consortium">W3C</abbr></a><sup>®</sup>
(
<a href="http://www.csail.mit.edu/"><abbr title="Massachusetts Institute of Technology">MIT</abbr></a>,
<a href="http://www.ercim.eu/"><abbr title="European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="http://www.keio.ac.jp/">Keio</a>,
<a href="http://ev.buaa.edu.cn/">Beihang</a>
), All Rights Reserved.
<abbr title="World Wide Web Consortium">W3C</abbr> <a href="https://www.w3.org/Consortium/Legal/ipr-notice#Legal_Disclaimer">liability</a>, <a href="https://www.w3.org/Consortium/Legal/ipr-notice#W3C_Trademarks">trademark</a> and <a href="https://www.w3.org/Consortium/Legal/copyright-documents">document use</a> rules apply.
</p>
<p>
<!-- $Date: 2015/04/30 16:53:49 $ -->
</p>
</footer>
</body>
</html>