- The Working Group will deliver the following W3C normative specifications:
+ The Working Group will deliver the following W3C normative specifications and WebXR Living Standards as noted
+ under the module deliverables section:
This specification defines a mechanism for showing interactive 2D web content during an immersive WebXR
session.
- - WebXR Raw Camera Access Module
- -
-
This feature would enable predictable access to camera frame data for AR devices.
- Draft state: Adopted from the Immersive Web CG
- Expected completion: Q4 2023
- Adopted Working Draft: Adopted from the
- Immersive Web CG
-
+ - Depth/Occlusion
+ API
+ -
+
This feature would provide depth and occlusion data on AR devices.
+ Draft state: Candidate
+ Recommendation
+ Expected completion: Q4 2026
+ Adopted Working Draft: WebXR
+ Depth
+ Sensing Module (19
+ April 2022)
+ Exclusion Draft:
+ https://www.w3.org/TR/2021/WD-webxr-depth-sensing-1-20210831/
+ associated Call
+ for Exclusion on 2021-08-31 ended on 2022-01-28
+
+
- - Depth/Occlusion
- API
- -
-
This feature would provide depth and occlusion data on AR devices.
- Draft state: Working Draft
- Expected completion: Q4 2024
- Adopted Working Draft: WebXR Depth Sensing Module (31 August 2021)
- Exclusion Draft:
- https://www.w3.org/TR/2021/WD-webxr-depth-sensing-1-20210831/
- associated Call for Exclusion on 2021-08-31 ended on 2022-01-28
-
+
- Navigation
-
This feature would enable better control of experiences when users navigate from one XR experience to
another.
- Draft state: Adopted from the Immersive Web CG
- Expected completion: Q4 2024
- Adopted Working Draft: Adopted from the Immersive Web CG
-
-
- - Model Element
-
- -
-
This feature is to add a new HTML element to handle displaying 3D
- This may become a recommendation to the WhatWG rather than being published under the Immersive Web Working Group
- Draft state: No draft yet
- Expected completion: Q4 2024
+ Draft state: Adopted from the Immersive Web CG
+ Expected completion: Q4 2027
+ Adopted Working Draft: Adopted from the
+ Immersive Web CG
-
-
- The Working Group also intends to work on the following Recommendation-Track deliverables, although it
- recognizes these
- Recommendations may not be completed before the end of this charter period. All work is expected to be
- incubated in the
- Immersive Web Community Group first. These deliverables are in rough priority order as of the start of the
- charter
- period, although the Chairs may reprioritize based on the consensus of the Working Group during the
- charter period.
-
-
+
- WebXR Real World Geometry
Module
@@ -491,24 +501,81 @@
Draft state: Adopted from the
Immersive Web CG
- Expected completion: Q4 2024
+ Expected completion: Q4 2026
Adopted Working Draft: WebXR
Real
World Geometry Proposal
+
+ - WebXR Raw
+ Camera Access Module
+ -
+
This feature would enable predictable access to camera frame data for AR devices.
+ Draft state: Adopted from the
+ Immersive Web CG
+ Expected completion: Q4 2026
+ Adopted Working Draft: Adopted from the
+ Immersive Web CG
+
-
- The Working Group also may choose to deliver normative specifications for the following features, if there
- is consensus
- in the Working Group that they are ready to move to the Recommendation track after sufficient incubation in
- the
- Immersive Web CG.
+
+ The Working Group also intends to work on the following Recommendation-Track deliverables, although it
+ recognizes these
+ Recommendations may not be completed before the end of this charter period. All work is expected to be
+ incubated in the
+ Immersive Web Community Group first. These deliverables are in rough priority order as of the start of the
+ charter
+ period, although the Chairs may reprioritize based on the consensus of the Working Group during the
+ charter period.
+
+
+
+ - Model
+ Element
+
+ -
+
This feature is to add a new HTML element to handle displaying 3D
+ This may become a recommendation to the WhatWG rather than being published under the Immersive Web
+ Working Group
+ Draft state: No draft yet
+ Expected completion: Q4 2028
+
+
+ - WebXR Anchors
+ Module - Level 2
+ -
+
This specification enables users of the WebXR Device API Anchors to have persistent Anchors between
+ sessions.
+ Draft state: No Draft
+ Expected completion: Q4 2027
+
+
-
+
+ - Body
+ Tracking
+ Module
+ -
+
The WebXR Body Tracking module expands the WebXR Device API with the functionality to track articulated
+ body poses.
+
+
+
+
+ The Working Group also may choose to deliver normative specifications for the following features, if there
+ is consensus
+ in the Working Group that they are ready to move to the Recommendation track after sufficient incubation in
+ the
+ Immersive Web CG.
+
+
+
- XR Capture
Module
-
@@ -522,7 +589,8 @@
This feature would enable access to image detection support on AR devices.
- - Marker Detection
+ - Marker
+ Detection
-
This feature would enable access to QR code marker detection support on AR devices.
@@ -536,9 +604,11 @@
This feature would provide data tracking the user's gaze, for example to provide foveal-rendering
improvement features.
- - Geo-alignment
+ - Geo-alignment
+
-
-
This feature would facilitate geo-spatial AR data in the context of immersive web, to utilize geo alignment using coordinate system with geospatial orientation.
+ This feature would facilitate geo-spatial AR data in the context of immersive web, to utilize geo
+ alignment using coordinate system with geospatial orientation.
@@ -575,27 +645,37 @@
Success Criteria
possible alternate text for keeping CR/CRS
- In order to advance to Candidate Recommendation
- and to add features after reaching Candidate Recommendation,
- each feature is expected to be supported by at least two independent interoperable implementations,
- which may be judged by factors including existing implementations, expressions of interest, and lack of opposition.
+ In order to advance to Candidate Recommendation
+ and to add features after reaching Candidate Recommendation,
+ each feature is expected to be supported by at least two independent interoperable
+ implementations,
+ which may be judged by factors including existing implementations, expressions of interest, and lack of
+ opposition.
- In order to advance to Proposed Recommendation, each normative specification is expected to have at least two independent interoperable implementations of every feature defined in the specification, where interoperability can be verified by passing open test suites, and two or more implementations interoperating with each other.
+ In order to advance to Proposed Recommendation, each normative specification is expected to have
+ at least two independent
+ interoperable implementations of every feature defined in the specification, where interoperability can be
+ verified by passing open test suites, and two or more implementations interoperating with each other.
[delate this sentence? dup to others]
- In order to advance to Proposed Recommendation, each normative specification must have an open test suite of every feature defined in the specification.
+ In order to advance to Proposed Recommendation, each normative specification must have an open test suite of
+ every feature defined in the specification.
- There should be testing plans for each specification, starting from the earliest drafts.
+ There should be testing plans for each specification, starting from the earliest drafts.
-
- To promote interoperability, all changes made to specifications
- in Candidate Recommendation
- or to features that have deployed implementations
- should have tests.
- Testing efforts should be conducted via the Web Platform Tests project.
+
+ To promote interoperability, all changes made to specifications
+ in Candidate Recommendation
+ or to features that have deployed implementations
+ should have tests.
+ Testing efforts should be conducted via the Web Platform
+ Tests project.
-
+
Each specification should contain sections detailing all known security and privacy implications for
implementers, Web authors, and end users.
@@ -604,19 +684,21 @@ Success Criteria
ways specification features can be used to address them, and
recommendations for maximising accessibility in implementations.
-
- This Working Group expects to follow the
- TAG Web Platform Design Principles.
-
-
-
- All new features should have expressions of interest from at least two potential implementors before being incorporated in the specification.
-
+
+ This Working Group expects to follow the
+ TAG Web Platform Design Principles.
+
-
- [dup to new test section?]
- To promote interoperability, all changes made to specifications should have tests.
+
+ All new features should have expressions of interest from at least two potential implementors before being
+ incorporated in the specification.
+
+
+
+ [dup to new test section?]
+ To promote interoperability, all changes made to specifications should have tests.
+
@@ -652,8 +734,10 @@ W3C Groups
-
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 Immersive Web Working
- Group will happen in the Community Group, and then be followed by future Immersive Web Working Group rechartering to include them in
+ incubate new features - in particular, incubation of features that are out of current scope for the
+ Immersive Web Working
+ Group will happen in the Community Group, and then be followed by future Immersive Web Working Group
+ rechartering to include them in
scope.
-
@@ -680,7 +764,8 @@
W3C Groups
-
The APA Working Group will review deliverables for accessibility
- implications and help develop solutions, noting the following XR Accessibility User Requirements resource.
+ implications and help develop solutions, noting the following XR
+ Accessibility User Requirements resource.
- Audio Working Group
- The Audio Working group develops the Web Audio
@@ -691,17 +776,18 @@
W3C Groups
- GPU For The Web Working Group
-
- The GPU for the Web Working Group develops the WebGPU
+ The GPU for the Web Working Group develops the WebGPU
Specification and the WebGPU Shading Language Specification,
both of which might apply to the features provided by the WebXR
Device API and modules.
- - Web Platform Incubator Community Group
+ - Web Platform Incubator Community Group
+
-
- The Web Platform Incubator Community Group provides a lightweight venue for proposing, incubating,
- and discussing new web platform features.
- The Immersive Web Working Group will incubate and work on new model element proposal that are within
- scope of WICG.
+ The Web Platform Incubator Community Group provides a lightweight venue for proposing, incubating,
+ and discussing new web platform features.
+ The Immersive Web Working Group will incubate and work on new model element proposal that are within
+ scope of WICG.
@@ -717,7 +803,8 @@
The group also welcomes non-Members to contribute technical submissions for consideration upon their agreement
- to the terms of the W3C Patent Policy.
+ to the terms of the W3C Patent
+ Policy.
This group will seek to make decisions through consensus and due process, per the W3C Process Document (section 5.2.1, Consensus3). Typically, an
+ href="https://www.w3.org/Consortium/Process/#Consensus"> W3C Process Document (section 5.2.1, Consensus3).
+ 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.