forked from w3c/immersive-web-wg-charter
-
Notifications
You must be signed in to change notification settings - Fork 0
/
immersive-web-wg-charter.html
648 lines (639 loc) · 24.6 KB
/
immersive-web-wg-charter.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
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
<!DOCTYPE html>
<html lang="en-US">
<head>
<meta charset="utf-8">
<title>
[DRAFT] Immersive Web 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;
}
footer {
font-size: small;
}
</style>
</head>
<body>
<header id="header">
<aside>
<ul id="navbar">
<li>
<a href="#background">Background</a>
</li>
<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=
"https://www.w3.org/Icons/w3c_home" width="72"></a>
</p>
</header>
<main>
<h1 id="title">
[DRAFT] Immersive Web Working Group Charter
</h1>
<p>
<em>Status: this is a draft charter for a possible W3C Immersive Web Working
Group, provided for discussion, without any formal
standing.</em>
</p>
<p class="mission">
The <strong>mission</strong> of the Immersive Web Working Group is to help
bring high-performance Virtual Reality (VR) and Augmented Reality (AR) (collectively known as XR) to the open Web via APIs to interact with XR devices and sensors in browsers.
</p>
<div class="noprint">
<p class="join">
<a>Join the Immersive Web 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>
1 October 2019
</td>
</tr>
<tr>
<th>
Charter extension
</th>
<td>
See <a href="#history">Change History</a>.
</td>
</tr>
<tr>
<th>
Chairs
</th>
<td>
Ada Rose Cannon (Samsung), Chris Wilson (Google)
</td>
</tr>
<tr>
<th>
Team Contacts
</th>
<td>
<a href="mailto:dom@w3.org">Dominique Hazael-Massieux</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, usually no more
than 3 per year.
</td>
</tr>
</table>
</section>
<section id="background">
<h2>
Background
</h2>
<p>
A new generation of head-mounted displays and environment sensing
capabilities on mobile devices are enabling augmented and virtual reality
(collectively known as XR) to emerge as a critical field of evolution for
human-machine interactions.
</p>
<p>
Due to its inherent low friction and support for ephemeral experiences,
the Web provides a promising ecosystem for the creation,
distribution, and experiencing of XR content, applications, and
services.
</p>
<p>
The <a href=
"https://www.w3.org/2016/06/vr-workshop/report.html">October 2016 W3C
Workshop</a> explored that potential, relying on browsers to display and
interact with content using available head-mounted displays and handheld
devices providing a window into virtual space. The <a href=
"https://www.w3.org/community/immersive-web/">Community-Group incubated</a>
<a href="https://immersive-web.github.io/webxr/">WebXR Device API</a> has
already gained interest from a number of implementors. This Working Group
will build on that momentum to standardize the WebXR Device API as part of
the Open Web Platform.
</p>
</section>
<section id="scope" class="scope">
<h2>
Scope
</h2>
<p>
The Immersive Web Working Group will develop standardized APIs to provide
access to input and output capabilities commonly associated with
XR hardware such as Google’s Daydream, the Oculus Rift,
the Samsung GearVR, the HTC Vive, and Windows Mixed Reality
headsets and sensors as well as mobile handheld devices and standalone
headsets such as the Oculus Go and Lenovo Mirage Solo.
The WG will develop APIs to enable the creation of XR web experiences
that are embeddable in the Web of today, enabling progressive enhancement
of existing sites.
</p>
<p>
The <strong>scope</strong> of the Immersive Web Working Group charter is to
define APIs which:
</p>
<ul>
<li>Detect available XR devices and sensors.
</li>
<li>Query XR devices for device-specific capabilities.
</li>
<li>Receive updated information about the device's position and orientation over time.
</li>
<li>Receive updated information about the device's environment.
</li>
<li>Present imagery to the device at the device's native frame rate, using the device’s position and orientation over time to provide an immersive experience.
</li>
<li>Provide information about XR specific input, including tracked controller state and hand gesture.
</li>
<li>For augmenting reality on devices which support AR, enable XR sessions that provide real-world display, and provide the ability to hit-test surfaces in the real world.
</li>
</ul>
<p>
<strong>Out of scope</strong>:
</p>
<ul>
<li>Defining browser user experience inside virtual or augmented reality,
aside from navigating between XR sites.
</li>
<li>Defining mechanisms for global-scale AR browsing.
</li>
</ul>
<div>
<h3>
Success Criteria
</h3>
<p>
In order to advance to <a href=
"https://www.w3.org/2017/Process-20170301/#RecsPR" title=
"Proposed Recommendation">Proposed Recommendation</a>, each
specification is expected to have <a href=
"https://www.w3.org/2017/Process-20170301/#implementation-experience">
at least two independent implementations</a> of each feature
defined in the specification.
</p>
<p>
Each specification should contain a section detailing any known
security or privacy implications and considerations for implementers,
Web authors, and end users.
</p>
<p>
Each specification will have an associated testing plan developed
in parallel, and will be completed when the specification reaches
Candidate Recommendation.
</p>
<p>
Each specification will contain a section describing known
impacts on accessibility to users with disabilities, ways the
specification features address them, and recommendations for
minimizing accessibility problems in implementation.
</p>
</div>
</section>
<section id="deliverables">
<h2>
Deliverables
</h2>
<p>
More detailed milestones and updated publication schedules for the deliverables detailed below in this charter are
available on the <a class="todo" href=
"http://example.org">group publication
status page</a>.
</p>
<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="webxr" class="spec">
<a href="#">WebXR Device API</a>
</dt>
<dd>
<p>
This specification describes support for accessing virtual
reality (VR) and augmented reality (AR) devices,
including sensors and head-mounted displays on the Web.
</p>
<p class="draft-status">
<a href="https://immersive-web.github.io/webxr/">Draft
adopted from Immersive Web CG</a>
</p>
<p class="milestone">
<b>Expected completion:</b> Q4 2019
</p>
</dd>
</dl>
</div>
<div id="ig-other-deliverables">
<h3>
Other Deliverables
</h3>
<p>
Other non-normative documents may be created such as:
</p>
<ul>
<li>Use case and requirement documents;
</li>
<li>Test suite and implementation report for the specification;
</li>
<li>Primer or Best Practice documents to support web developers
when designing applications.
</li>
</ul>
</div>
<div id="timeline">
<h3>
Timeline
</h3>
<ul>
<li>Oct 2018: First teleconference
</li>
<li>Oct 2018: FPWD for WebXR Device API
</li>
<li>Oct 2018: First face-to-face meeting
</li>
<li>Dec 2018: Wide Review of WebXR Device API
</li>
<li>Q2 2019: CR for WebXR Device API
</li>
<li>Q4 2019: Rec for WebXR Device API
</li>
</ul>
</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/2017/Process-20170301/#RecsWD"
title="First Public Working Draft">FPWD</a> and <a href=
"https://www.w3.org/2017/Process-20170301/#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/2017/Process-20170301/#WGCharter">W3C Process
Document</a>:
</p>
<div>
<h3 id="w3c-coordination">
W3C Groups
</h3>
<dl>
<dt>
<a href="https://www.w3.org/community/immersive-web/">Immersive Web Community
Group</a>
</dt>
<dd>
The Immersive Web Community Group will provide the WebXR Device API seed specification to begin the standards process. In addition, the Immersive Web Working Group plans to partner closely with the IWCG to incubate new features - in particular, incubation of features that are out of current scope for the working group will happen in the Community Group, and then be followed by future WG rechartering to include them in scope.
</dd>
<dt>
<a href="https://www.w3.org/2009/dap/">Devices and Sensors Working Group</a>
</dt>
<dd>
The Devices and Sensors Working Group develops the Generic Sensor
framework, which may provide valuable integration point with
sensors that integrate with XR devices.
</dd>
<dt>
<a href="https://www.w3.org/2011/webappsec/">Web Application
Security Working Group</a>
</dt>
<dd>
The Web Application Security Working Group develops the
Permissions API as well as guidance on the definition of powerful
features, both of which might apply to the features provided by
the WebXR Device API.
</dd>
<dt>
<a href="https://www.w3.org/WAI/APA/">Accessible Platform
Architectures (APA) Working Group</a>
</dt>
<dd>
The APA Working Group will review deliverables for accessibility
implications and help develop solutions.
</dd>
</dl>
<h3 id="external-coordination">
External Organizations
</h3>
<dl>
<dt>
<a href="https://khronos.org/">Khronos Group</a>
</dt>
<dd>
The Khronos Group is in charge of the WebGL specification on
which the WebXR Device API heavily relies for its operations. The Working Group
will coordinate its roadmap with planned evolutions of WebGL. The
group will also track and coordinate with <a href=
"https://www.khronos.org/openxr">Khronos OpenXR standard initiative</a>.
</dd>
</dl>
</div>
</section>
<section class="participation">
<h2 id="participation">
Participation
</h2>
<p>
To be successful, this Working Group is expected to have 6 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 upon their agreement to the terms of
the <a href="https://www.w3.org/Consortium/Patent-Policy/">W3C Patent
Policy</a>.
</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/2017/Process-20170301/#confidentiality-levels">
public</a>: the 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. The
meetings themselves are not open to public participation, however.
</p>
<p>
Information about the group (including details about deliverables,
issues, actions, status, participants, and meetings) will be
available from the <a class="todo" href="http://example.org">Immersive Web Working Group home page.</a>
</p>
<p>
Most Immersive Web 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 in <a id="public-github" href="https://github.com/immersive-web/webxr/issues">GitHub issues</a> and
on the public mailing list <a href=
"mailto:public-immersive-web-wg@w3.org">public-immersive-web-wg@w3.org</a> (<a href=
"http://lists.w3.org/Archives/Public/public-immersive-web-wg/">archive</a>). The public is invited to review, discuss and contribute to this work.
</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/2017/Process-20170301/#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-software">W3C Software
and 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</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 id="history">
<h3>
Charter History
</h3>
<p>
The following table lists details of all changes from the initial
charter, per the <a href=
"https://www.w3.org/2017/Process-20170301/#CharterReview">W3C
Process Document (section 5.2.3)</a>:
</p>
<table class="history">
<tbody>
<tr>
<th>
Charter Period
</th>
<th>
Start Date
</th>
<th>
End Date
</th>
<th>
Changes
</th>
</tr>
<tr>
<th>
<a href="">Initial Charter</a>
</th>
<td>
<i class="todo">[dd monthname yyyy]</i>
</td>
<td>
31 August 2019
</td>
<td>
N/A
</td>
</tr>
</tbody>
</table>
</section>
</section>
</main>
<hr>
<footer>
<address>
<a href="mailto:dom@w3.org">Dominique Hazael-Massieux</a>
</address>
<p class="copyright">
<a href=
"https://www.w3.org/Consortium/Legal/ipr-notice#Copyright">Copyright</a>
© 2017 <a href="https://www.w3.org/"><abbr title=
"World Wide Web Consortium">W3C</abbr></a><sup>®</sup> ( <a href=
"https://www.csail.mit.edu/"><abbr title=
"Massachusetts Institute of Technology">MIT</abbr></a>, <a href=
"https://www.ercim.eu/"><abbr title=
"European Research Consortium for Informatics and Mathematics">ERCIM</abbr></a>,
<a href="https://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>