@@ -170,7 +170,8 @@ Scope
access to input and output capabilities commonly associated with
XR hardware such as tethered headsets and sensors as well as mobile handheld devices and standalone
headsets.
- The group will also investigate compatibility with non head-worn, multi-view displays. Examples include Looking Glass or zSpace displays.
+ The group will also investigate compatibility with non head-worn, multi-view displays. Examples include
+ Looking Glass or zSpace displays.
The group 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.
@@ -226,14 +227,16 @@
More detailed milestones and updated publication schedules are available on the group publication status page.
+ href="https://www.w3.org/groups/wg/immersive-web/publications" target="_blank">group publication status
+ page.
text for keeping CR/CRS
- The group will advance its other documents to Candidate Recommendation (with Snapshots) and,
- when they are sufficiently mature, to Recommendation.
- As noted below, some documents (XXXX) have particular milestones for being published as Candidate Recommendations.
+ The group will advance its other documents to Candidate Recommendation (with Snapshots) and,
+ when they are sufficiently mature, to Recommendation.
+ As noted below, some documents (XXXX) have particular milestones for being published as Candidate
+ Recommendations.
Draft state indicates the state of the deliverable at the time of the charter approval. Expected
@@ -245,7 +248,7 @@
Normative Specifications
- The Working Group will deliver the following W3C normative specifications:
+ The Working Group will deliver the following W3C normative specifications based on WebXR Living Standards:
@@ -258,18 +261,25 @@
changes.
This specification defines support for accessing virtual reality (VR) and augmented reality (AR) devices,
including sensors and head-mounted displays, on the Web.
- Draft state: Candidate Recommendation
- Expected completion: Q3 2023
- Adopted Working Draft: WebXR Device API (31 March 2022)
+ Draft state: WebXR
+ Living
+ Standard
+
+ Expected W3C Recommendation: yearly basis
+
+ Adopted Working Draft: WebXR Device API (16 April 2024)
Produced under Working Group Charter: Previous charter period
+ href="https://www.w3.org/2022/07/immersive-web-wg-charter.html" target="_blank">Previous charter period
of the Immersive
Web Working Group
Exclusion Draft:
- https://www.w3.org/TR/2022/CR-webxr-20220331/
- associated Call for Exclusion on 2022-03-31, opportunity until 2022-05-30
+ https://www.w3.org/TR/2024/CRD-webxr-20240416/
+ associated Call
+ for Exclusion on 2024-04-TODO, opportunity until 2024-06-TODO
+
-
This specification defines support for accessing button, trigger, thumbstick, and touchpad data
associated with virtual reality (VR) and augmented reality (AR) devices on the Web.
Draft state: Working Draft
- Expected completion: Q4 2023
- Adopted Working Draft: Working Draft
+ Expected completion: Q4 2026
+ Adopted Working Draft: WebXR Gamepads
- Module - Level 1 (24 August 2021)
+ Module - Level 1 (16 April 2024)
Produced under Working Group Charter: Previous charter period
of the Immersive
Web Working Group
Exclusion Draft:
- https://www.w3.org/TR/2019/WD-webxr-gamepads-module-1-20191010/
- associated Call for Exclusion on 2019-10-10 ended on 2020-03-08
+ https://www.w3.org/TR/2024/WD-webxr-gamepads-module-1-20240409/
+ associated Call
+ for Exclusion on 2019-10-10 ended on 2020-03-08
+
-
This specification defines an expansion module of the WebXR Device API with the functionality available
on AR hardware.
Draft state: Candidate Recommendation
+ target="_blank">Candidate Recommendation
Expected completion: Q2 2024
- Adopted Working Draft: Adopted Working Draft: WebXR
Augmented Reality
- Module - Level 1 (24 August 2021)
+ Module - Level 1 (2 November 2022)
Produced under Working Group Charter: Previous charter period of the Immersive
Web Working Group
Exclusion Draft:
- https://www.w3.org/TR/2022/CR-webxr-ar-module-1-20221101/
- associated Call for Exclusion on 2019-10-10 ended on 2020-03-08
+ https://www.w3.org/TR/2022/CR-webxr-ar-module-1-20221101/
+ associated
+ Call for Exclusion on 2019-10-10 ended on 2020-03-08
+
- WebXR
@@ -329,15 +345,18 @@
This specification defines a method for performing hit tests against real world geometry to be used with
the WebXR Device API.
Draft state: Working Draft
- Expected completion: Q3 2024
- Adopted Working Draft: Working Draft
+ Expected completion: Q4 2026
+ Adopted Working Draft: WebXR
Hit Test
- Module (31 August 2021)
+ Module (19 April 2022)
Exclusion Draft:
- https://www.w3.org/TR/2021/WD-webxr-hit-test-1-20210831/
- associated Call for Exclusion on 2021-08-31 ended on 2022-01-28
+ https://www.w3.org/TR/2021/WD-webxr-hit-test-1-20210831/
+ associated Call
+ for Exclusion on 2021-08-31 ended on 2022-01-28
+
@@ -349,14 +368,17 @@
This specification defines a mechanism for showing interactive 2D web content during an immersive WebXR
session.
Draft state: Working Draft
- Expected completion: Q4 2024
- Adopted Working Draft: Working Draft
+ Expected completion: Q4 2026
+ Adopted Working Draft: WebXR DOM Overlays
- Module (31 August 2021)
+ Module (17 November 2022)
Exclusion Draft:
- https://www.w3.org/TR/2021/WD-webxr-dom-overlays-1-20210831/
- associated Call for Exclusion on 2021-08-31 ended on 2022-01-28
+ https://www.w3.org/TR/2021/WD-webxr-dom-overlays-1-20210831/
+ associated Call
+ for Exclusion on 2021-08-31 ended on 2022-01-28
+
This specification enables developers to render augmented reality content that reacts to real world
lighting with the WebXR Device API and the WebXR AR Module.
- Draft state: Working Draft
- Expected completion: Q4 2024
+ Draft state: Working Draft
+ Expected completion: Q4 2026
Adopted Working Draft: WebXR Lighting Estimation API Level 1 (9 September 2021)
+ href="https://www.w3.org/TR/2022/WD-webxr-lighting-estimation-1-20220603/" target="_blank">WebXR
+ Lighting Estimation API Level 1 (3 June 2022)
Exclusion Draft:
- https://www.w3.org/TR/2021/WD-webxr-lighting-estimation-1-20210909/
- associated Call for Exclusion on 2021-09-09 ended on 2022-02-06
+ https://www.w3.org/TR/2021/WD-webxr-lighting-estimation-1-20210909/
+ associated Call
+ for Exclusion on 2021-09-09 ended on 2022-02-06
+
This specification defines a method for enabling hand input to be used with the WebXR Device API.
Draft state: Working Draft
- Expected completion: Q4 2024
- Adopted Working Draft: WebXR Hand Input Module - Level 1 (24 August 2021)
+ target="_blank">Working Draft
+ Expected completion: Q4 2026
+ Adopted Working Draft: WebXR Hand Input Module - Level 1 (7 February 2024)
Exclusion Draft:
- https://www.w3.org/TR/2020/WD-webxr-hand-input-1-20201022/
- associated Call for Exclusion on 2020-10-22 ended on 2021-03-21
+ https://www.w3.org/TR/2020/WD-webxr-hand-input-1-20201022/
+ associated Call
+ for Exclusion on 2020-10-22 ended on 2021-03-21
+
WebXR Anchors
@@ -397,91 +427,68 @@
that need to be updated to correctly reflect the evolving understanding of the world, such that the poses
remain aligned with the same place in the physical world. These poses will persist inside sessions, but
not across sessions.
-
Draft state: Editor's Draft
- Expected completion: Q4 2024
+ Draft state: Editor's
+ Draft
+ Expected completion: Q4 2026
Adopted Working Draft: Adopted from the
Immersive Web CG
- 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 2024
-
- WebXR Layers API Level 1
+
+ WebXR
+ Layers API Level 1
This specification defines methods for manipulating composition layers used with the WebXR Device API.
Draft state: Working Draft
+ target="_blank">Working Draft
Expected completion: Q2 2024
Adopted Working Draft: WebXR Layers API Level 1 (7 December 2021)
Exclusion Draft:
- https://www.w3.org/TR/2020/WD-webxrlayers-1-20201203/
- associated Call for Exclusion on 2020-12-03 ended on 2021-05-02
+ https://www.w3.org/TR/2020/WD-webxrlayers-1-20201203/
+ associated Call
+ for Exclusion on 2020-12-03 ended on 2021-05-02
+
-
- - 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
+ Draft state: Adopted from the Immersive Web CG
Expected completion: Q4 2024
+ 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
@@ -497,18 +504,75 @@
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 2023
+ 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 2026
+
+
+ - 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 2026
+
+
+
+
+ - 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 +586,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 +601,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 +642,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 +681,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 +731,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 +761,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 +773,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 +800,8 @@ External Organizations
The Khronos Group is in charge of the WebGL specification on
which the WebXR Device API heavily relies for its operations. The Immersive Web Working Group
will coordinate its roadmap with planned evolutions of WebGL. The
- Immersive Web Working Group will also track and coordinate with Khronos
+ Immersive Web Working Group will also track and coordinate with Khronos
OpenXR standard
initiative.
@@ -730,9 +814,18 @@ External Organizations
and version 4.1 will add Mixed Augmented Reality capabilities for diverse
virtual and augmented reality devices.
- Open Geospatial Consortium
+ Open Geospatial Consortium
+
- The Open Geospatial Consortium creates free, publicly available geospatial standards that enable new technologies. OGC also manages an agile and collaborative research and development process that anticipates and solves real-world geospatial challenges experienced by its members. One of the OGC working groups that is most relevant for Immersive Web focuses on development of GeoPose, an encoding specification to seamlessly express, record, and share the geographically-anchored position and 6 DOF orientation of objects in an entirely consistent manner across different applications, users, devices, services, and platforms which adopt the standard or are able to translate/exchange the GeoPose into another CRS. The Immersive Web Working Group will coordinate its roadmap with planned evolutions of relevant OGC standards, including but not limited to GeoPose.
+ The Open Geospatial Consortium creates free, publicly available geospatial standards that enable new
+ technologies. OGC also manages an agile and collaborative research and development process that anticipates
+ and solves real-world geospatial challenges experienced by its members. One of the OGC working groups that
+ is most relevant for Immersive Web focuses on development of GeoPose, an encoding specification to
+ seamlessly express, record, and share the geographically-anchored position and 6 DOF orientation of objects
+ in an entirely consistent manner across different applications, users, devices, services, and platforms
+ which adopt the standard or are able to translate/exchange the GeoPose into another CRS. The Immersive Web
+ Working Group will coordinate its roadmap with planned evolutions of relevant OGC standards, including but
+ not limited to GeoPose.
@@ -755,7 +848,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.
Participants in the group are required (by the W3C Process) to follow the
@@ -809,7 +903,8 @@
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.
@@ -835,7 +930,8 @@
This charter is written in accordance with the W3C
- Process Document (Section 5.2.3, Deciding by Vote) and includes no voting procedures beyond what the Process Document
+ Process Document (Section 5.2.3, Deciding by Vote) and includes no voting procedures beyond what the
+ Process Document
requires.
@@ -857,125 +953,129 @@
href="https://www.w3.org/groups/wg/immersive-web/ipr">licensing information.
-
+
-
-
- About this Charter
-
-
- This charter has been created according to section
- 3.4 of the Process Document. 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.
-
+
+
+ About this Charter
+
+
+ This charter has been created according to section
+ 3.4 of the Process Document. 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.
+
-
-
- Charter History
-
-
-
-
- |
- Charter Period
- |
-
- Start Date
- |
-
- End Date
- |
-
- Changes
- |
-
-
- |
- Initial Charter
- |
-
- 24 September 2018
- |
-
- 1 March 2020
- |
-
- none
- |
-
-
- |
- Charter
- Extension
- |
-
- 9 March 2020
- |
-
- 30 April 2020
- |
-
- none
- |
-
-
- |
- Rechartered
- |
-
- 12 May 2020
- |
-
- 1 June 2022
- |
-
- Added: WebXR Gamepads Module, WebXR Augmented Reality Module, WebXR Hit Test Module, WebXR DOM Overlays
- Module, WebXR Lighting Estimation Module, WebXR Hand Input Module, WebXR Real World Geometry Module,
- WebXR Anchors Module, WebXR Layers
- |
-
-
- |
- Charter
- Extension
- |
-
- 1 June 2022
- |
-
- 1 September 2022
- |
-
- none
- |
-
-
- |
- Rechartered
- |
-
- 8 July 2022
- |
-
- 7 July 2024
- |
-
- Added: Raw Camera Access, Depth/Occlusion API, Navigation, WebXR Anchors Proposal Module - Level 2, Model Element
- Expanded Scope with new type of devices, handling of 3D models, and navigation to follow emering industrial needs.
- |
-
+
+
+ Charter History
+
+
+
+
+ |
+ Charter Period
+ |
+
+ Start Date
+ |
+
+ End Date
+ |
+
+ Changes
+ |
+
+
+ |
+ Initial Charter
+ |
+
+ 24 September 2018
+ |
+
+ 1 March 2020
+ |
+
+ none
+ |
+
+
+ |
+ Charter
+ Extension
+ |
+
+ 9 March 2020
+ |
+
+ 30 April 2020
+ |
+
+ none
+ |
+
+
+ |
+ Rechartered
+ |
+
+ 12 May 2020
+ |
+
+ 1 June 2022
+ |
+
+ Added: WebXR Gamepads Module, WebXR Augmented Reality Module, WebXR Hit Test Module, WebXR DOM
+ Overlays
+ Module, WebXR Lighting Estimation Module, WebXR Hand Input Module, WebXR Real World Geometry Module,
+ WebXR Anchors Module, WebXR Layers
+ |
+
+
+ |
+ Charter
+ Extension
+ |
+
+ 1 June 2022
+ |
+
+ 1 September 2022
+ |
+
+ none
+ |
+
+
+ |
+ Rechartered
+ |
+
+ 8 July 2022
+ |
+
+ 7 July 2024
+ |
+
+ Added: Raw Camera Access, Navigation, WebXR Anchors Proposal Module - Level 2,
+ Model Element
+ Expanded Scope with new type of devices, handling of 3D models, and navigation to follow emering
+ industrial needs.
+ |
+
Rechartered
@@ -987,26 +1087,28 @@
[dd monthname yyyy]
|
- [description of change to charter, with link to new deliverable item in charter] Note: use the class new for all new deliverables, for ease of recognition.
+ [description of change to charter, with link to new deliverable item in charter]
+ Note: use the class new for all new deliverables, for ease of recognition.
+
|
|
-
-
-
+
+
+
-
- Change log
+
+ Change log
-
- Changes to this document are documented in this section.
-
+ Changes to this document are documented in this section.
+
+
-
@@ -1016,14 +1118,17 @@ Change log
Atsushi Shimono
-Copyright © [yyyy] World Wide Web Consortium.
- W3C®
- liability,
- trademark and
- permissive document license rules apply.
-
- Yes, it's on GitHub!.
-
+ Copyright © [yyyy] World Wide Web
+ Consortium.
+ W3C®
+ liability,
+ trademark and
+ permissive document license rules apply.
+
+
+ Yes, it's on GitHub!.
+