-
Notifications
You must be signed in to change notification settings - Fork 4
/
Copy pathindex.html
454 lines (454 loc) · 18.1 KB
/
index.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
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
<!DOCTYPE html>
<html lang="en-US">
<head>
<title>
Second Screen Community Group Charter
</title>
<meta name="viewport" content="width=device-width">
<link rel="stylesheet" href="https://www.w3.org/StyleSheets/TR/base" type=
"text/css">
<style type="text/css">
body {
max-width: 60em;
margin: auto;;
}
*:target {
background-color: yellow;
}
li {
margin-bottom: 9pt;
}
/* Note formatting taken from HTML5 spec */
.note { border-left-style: solid; border-left-width: 0.25em; background: none repeat scroll 0 0 #E9FBE9; border-color: #52E052; }
.note em, .warning em, .note i, .warning i { font-style: normal; }
p.note, div.note { padding: 0.5em 2em; }
span.note { padding: 0 2em; }
.note p:first-child { margin-top: 0; }
.note p:last-child { margin-bottom: 0; }
.note:before { content: 'NOTE: '; }
.issue { border-left-style: solid; border-left-width: 0.25em; background: none repeat scroll 0 0 #fbe9e9; border-color: #e05252; }
.issue em, .warning em, .issue i, .warning i { font-style: normal; }
p.issue, div.issue { padding: 0.5em 2em; }
span.issue { padding: 0 2em; }
.issue p:first-child { margin-top: 0; }
.issue p:last-child { margin-bottom: 0; }
.issue:before { content: 'ISSUE: '; }
</style>
</head>
<body>
<h1>
Second Screen Community Group Charter
</h1>
<dl>
<dt>
This Charter:
</dt>
<dd>
<a href=
"https://webscreens.github.io/cg-charter/">https://webscreens.github.io/cg-charter/</a>
</dd>
<dt>
Start Date:
</dt>
<dd>
2 September 2016
</dd>
<dt>
Last Modified:
</dt>
<dd>
3 May 2022
</dd>
</dl>
<h2 id="leadership">
Chairs
</h2>
<p>
The Chairs of the Second Screen Community Group are:
</p>
<ul>
<li>Anssi Kostiainen (Intel Corporation)
</li>
<li>Louay Bassbouss (Fraunhofer FOKUS)
</li>
</ul>
<h2 id="goals">
Goals
</h2>
<p>
The mission of the <a href=
"https://www.w3.org/community/webscreens/">Second Screen Community Group
(CG)</a> is to explore, incubate, and define interfaces that enable new
form factors and usages for multi-display and multi-window computing user
experiences on the Web.
</p>
<p>
The scope of work for this Community Group extends beyond the current
scope of the <a href="http://www.w3.org/2014/secondscreen/">Second Screen
Working Group (WG)</a>. Given wider support and adequate stability, we
plan to migrate the proposals generated in this Community Group to an
appropriate <a href=
"https://www.w3.org/Consortium/activities#Working">W3C Working Group</a>
for further contributions and formal standardization.
</p>
<p>
Membership of the group is open to everybody. Upon joining the group,
participants agree to the terms of the <a href=
"https://www.w3.org/community/about/agreements/cla/">W3C Community
Contributor License Agreement (CLA)</a>.
</p>
<h2 id="background">
Background
</h2>
<p>
The Second Screen Community Group (CG) incubated the <a href=
"https://w3c.github.io/presentation-api/">Presentation API</a> in
2013-2014, migrated to the Second Screen Working Group (WG) in 2014.
</p>
<p>
The CG incubated the <a href=
"https://w3c.github.io/remote-playback/">Remote Playback API</a> in
2015-2016, migrated to the WG in 2016.
</p>
<p>
The CG incubated the <a href=
"https://github.com/webscreens/openscreenprotocol/">Open Screen
Protocol</a> in 2016-2019, migrated to the WG in 2020.
</p>
<p>
The CG adopted the <a href=
"https://github.com/webscreens/screen-enumeration/blob/master/EXPLAINER.md">
Screen Enumeration</a>, <a href=
"https://github.com/webscreens/window-placement/blob/master/EXPLAINER.md">
Window Placement</a>, and <a href=
"https://github.com/webscreens/window-segments/blob/master/EXPLAINER.md">Window
Segments Enumeration</a> APIs as its new incubations in 2020.
</p>
<p>
The Screen Enumeration and Window Placement APIs merged to form a new
<a href="https://webscreens.github.io/window-placement/">Multi-Screen
Window Placement API</a>.
</p>
<p>
The CG adopted the <a href=
"https://webscreens.github.io/form-factors/">Form Factors Explained</a>
document as a new non-normative report in 2020.
</p>
<p>
The CG incubated the <a href=
"https://webscreens.github.io/window-placement/">Multi-Screen Window Placement</a> in
2020-2022, migrated to the WG in 2022.
</p>
<h2 id="scope-of-work">
Scope of Work
</h2>
<h3 id="presentation-api-v2">
Presentation API v2 features
</h3>
<ul>
<li>A <a href=
"https://github.com/markafoltz/local-presentation-api/blob/gh-pages/explainer.md">
Local Presentation Mode</a> is a <a href=
"https://w3c.github.io/presentation-api/">Presentation API</a>
extension that removes the restriction on presentations to use a
separate storage area and allows the controlling browsing context and
the receiving browsing context have access to each other's document
context. Use cases include e.g. offline usage, cookie-based
authentication, and sharing of application state across the controller
and presentation.
</li>
<li>Other extensions identified as <a href=
"https://github.com/w3c/presentation-api/issues?q=is%3Aissue+is%3Aopen+label%3Av2">
v2 features</a> by the WG.
</li>
</ul>
<h3 id="remote-playback-v2">
Remote Playback API v2 features
</h3>
<ul>
<li>Remote buffer state for Remote Playback to enhance Media Source
Extensions use cases
</li>
<li>Other extensions identified as <a href=
"https://github.com/w3c/remote-playback/issues?q=is%3Aissue+is%3Aopen+label%3Av2">
v2 features</a> by the WG.
</li>
</ul>
<h3 id="window-segments-enumeration">
Window Segments Enumeration
</h3>
<ul>
<li>The <a href=
"https://github.com/webscreens/window-segments/blob/master/EXPLAINER.md">
Window Segments Enumeration API</a> proposes a new concept of Window
Segments that represent the regions (and their dimensions) of the
window that reside on separate (adjacent) displays. Window Segment
dimensions are expressed in CSS pixels and will be exposed via a
JavaScript API that allows developers to enumerate segments where
logically separate pieces of content can be placed.
</li>
</ul>
<h3 id="form-factors">
Form Factors Explained (Non-Normative Report)
</h3>
<ul>
<li>The <a href="https://webscreens.github.io/form-factors/">Form Factors
Explained</a> is a non-normative report that proposes a naming scheme for
new device form factors referred to as foldable devices to be able to use
these terms and concepts consistently in related web specifications. This
explainer also discusses multi-monitor setups that extend the overall
visual workspace of a device.
</li>
</ul>
<h2 id="out-of-scope">
Out of Scope
</h2>
<p>
For this Community Group, the following tasks are out of scope:
</p>
<ul>
<li>Any additions to the APIs defined in the Second Screen WG not
explicitly listed in <a href="#scope-of-work">Scope of Work</a>.
</li>
<li>Defining media codecs or new specifications for transmitting media
codecs.
</li>
<li>Developing specifications for use of the Presentation API with
proprietary presentation display network protocols such as DIAL, DLNA,
Google Cast, MiraCast, or Airplay.
</li>
</ul>
<h2 id="deliverables">
Deliverables
</h2>
<p>
<strong>The group will only produce Specifications listed in this
section</strong>.
</p>
<h3 id="specifications">
Specifications
</h3>
<dl>
<dt>
Local Presentation Mode extension for the Presentation API
</dt>
<dd>
Adopted from the <a href=
"https://github.com/markafoltz/local-presentation-api/blob/gh-pages/explainer.md">
Local Presentation Mode</a> explainer. See <a href=
"#presentation-api-v2">Scope of Work</a>.
</dd>
<dt>
Window Segments Enumeration API
</dt>
<dd>
Adopted from the <a href=
"https://github.com/webscreens/window-segments/blob/master/EXPLAINER.md">
Window Segments Enumeration API</a> explainer. See <a href=
"#window-segments-enumeration">Scope of Work</a>.
</dd>
</dl>
<p>
To add any additional specifications, this Charter must be amended by the
process described in the <a href="#charter-change">Amendments to the
Charter</a> section. All deliverables for which the CLA <a href=
"https://www.w3.org/community/about/agreements/cla/#id3">Patents</a>
section applies must be designated as such here.
</p>
<h3 id="non-normative-reports">
Non-Normative Reports
</h3>
<dl>
<dt>
Form Factors Explained
</dt>
<dd>
See <a href="#form-factors">Scope of Work</a>.
</dd>
</dl>
<p>
The group may produce other Community Group Reports within the scope of
this charter but that are not Specifications, for instance use cases,
requirements, or white papers.
</p>
<h2 id="liaisons">
Dependencies or Liaisons
</h2>
<p>
It is anticipated that the group will collaborate with appropriate W3C
Working Groups in order to transition specification proposals to the
Recommendation Track.
</p>
<ul>
<li>This group works closely with the <a href=
"http://www.w3.org/2014/secondscreen/">W3C Second Screen Working
Group</a>.
</li>
<li>There are no external specifications that must be created before the
Specification(s) to be developed in this group can be completed.
</li>
</ul>
<h2 id="process">
Community and Business Group Process
</h2>
<p>
The group operates under the <a href=
"https://www.w3.org/community/about/agreements/">Community and Business
Group Process</a>. Terms in this Charter that conflict with those of the
Community and Business Group Process are void.
</p>
<p>
As with other Community Groups, W3C seeks organizational licensing
commitments under the <a href=
'http://www.w3.org/community/about/agreements/cla/'>W3C Community
Contributor License Agreement (CLA)</a>. When people request to
participate without representing their organization's legal interests,
W3C will in general approve those requests for this group with the
following understanding: W3C will seek and expect an organizational
commitment under the CLA starting with the individual's first request to
make a contribution to a group <a href="#deliverables">Deliverable</a>.
The section on <a href="#contrib">Contribution Mechanics</a> describes
how W3C expects to monitor these contribution requests.
</p>
<h2 id="worklimit">
Work Limited to Charter Scope
</h2>
<p>
The group will not publish Specifications on topics other than those
listed under <a href="#specifications">Specifications</a> above. See
below for <a href="#charter-change">how to modify the charter</a>.
</p>
<h2 id="contrib">
Contribution Mechanics
</h2>
<p>
Substantive Contributions to Specifications can only be made by Community
Group Participants who have agreed to the <a href=
"http://www.w3.org/community/about/agreements/cla/">W3C Community
Contributor License Agreement (CLA)</a>.
</p>
<p>
Specifications created in the Community Group must use the <a href=
"http://www.w3.org/Consortium/Legal/2015/copyright-software-and-document">
W3C Software and Document License</a>. All other documents produced by
the group should use that License where possible.
</p>
<p>
Community Group participants agree to make all contributions in the
GitHub repo the group is using for the particular document. This may be
in the form of a pull request (preferred), by raising an issue, or by
adding a comment to an existing issue.
</p>
<p>
All Github repositories attached to the Community Group must contain a
copy of the <a href=
"https://github.com/w3c/licenses/blob/master/CG-CONTRIBUTING.md">CONTRIBUTING</a>
and <a href=
"https://github.com/w3c/licenses/blob/master/CG-LICENSE.md">LICENSE</a>
files.
</p>
<h2 id="transparency">
Transparency
</h2>
<p>
The group will conduct all of its technical work in public. All technical
work will occur in its GitHub repositories (and not in mailing list
discussions). This is to ensure contributions can be tracked through a
software tool.
</p>
<p>
Meetings may be restricted to Community Group participants, but a public
summary or minutes must be posted to the group's public mailing list and
<a href=
"https://www.w3.org/community/webscreens/wiki/Main_Page">Wiki</a>.
</p>
<h2 id="decision">
Decision Process
</h2>
<p>
This group will seek to make decisions where there is consensus. Groups
are free to decide how to make decisions (e.g. Participants who have
earned Committer status for a history of useful contributions assess
consensus, or the Chair assesses consensus, or where consensus isn't
clear there is a Call for Consensus [CfC] to allow multi-day online
feedback for a proposed course of action). It is expected that
participants can earn Committer status through a history of valuable
contributions as is common in open source projects. After discussion and
due consideration of different opinions, a decision should be publicly
recorded (where GitHub is used as the resolution of an Issue).
</p>
<p>
If substantial disagreement remains (e.g. the group is divided) and the
group needs to decide an Issue in order to continue to make progress, the
Committers will choose an alternative that had substantial support (with
a vote of Committers if necessary). Individuals who disagree with the
choice are strongly encouraged to take ownership of their objection by
taking ownership of an alternative fork. This is explicitly allowed (and
preferred to blocking progress) with a goal of letting implementation
experience inform which spec is ultimately chosen by the group to move
ahead with.
</p>
<p>
Any decisions reached at any meeting are tentative and should be recorded
in a GitHub Issue for groups that use GitHub and otherwise on the group's
public mail list. Any group participant may object to a decision reached
at an online or in-person meeting within 10 days of publication of the
decision provided that they include clear technical reasons for their
objection. The Chairs will facilitate discussion to try to resolve the
objection according to the <a href="#decision">decision process</a>.
</p>
<p>
It is the Chairs' responsibility to ensure that the decision process is
fair, respects the consensus of the CG, and does not unreasonably favour
or discriminate against any group participant or their employer.
</p>
<h2 id="chairs">
Chair Selection
</h2>
<p>
Participants in this group choose their Chair(s) and can replace their
Chair(s) at any time using whatever means they prefer. However, if 5
participants, no two from the same organisation, call for an election,
the group must use the following process to replace any current Chair(s)
with a new Chair, consulting the Community Development Lead on election
operations.
</p>
<ol>
<li>Participants announce their candidacies. Participants have 14 days to
announce their candidacies, but this period ends as soon as all
participants have announced their intentions. If there is only one
candidate, that person becomes the Chair. If there are two or more
candidates, there is a vote. Otherwise, nothing changes.
</li>
<li>Participants vote. Participants have 21 days to vote for a single
candidate, but this period ends as soon as all participants have voted.
The individual who receives the most votes, no two from the same
organisation, is elected chair. In case of a tie, a process requested
from the Community Development Lead is used to break the tie. An elected
Chair may appoint co-Chairs.
</li>
</ol>
<p>
Participants dissatisfied with the outcome of an election may ask the
Community Development Lead to intervene. The Community Development Lead,
after evaluating the election, may take any action including no action.
</p>
<h2 id="charter-change">
Amendments to this Charter
</h2>
<p>
The group can decide to work on a proposed amended charter, editing the
text using the <a href="#decision">Decision Process</a> described above.
The decision on whether to adopt the amended charter is made by
conducting a 30-day vote on the proposed new charter. The new charter, if
approved, takes effect on either the proposed date in the charter itself,
or 7 days after the result of the election is announced, whichever is
later. A new charter must receive 2/3 of the votes cast in the approval
vote to pass. The group may make simple corrections to the charter such
as deliverable dates by the simpler group decision process rather than
this charter amendment process. The group will use the amendment process
for any substantive changes to the goals, scope, deliverables, decision
process or rules for amending the charter.
</p>
</body>
</html>