W3C home > Mailing lists > Public > public-immersive-web-wg@w3.org > January 2019

Call for Consensus (CfC): First Published Working Draft of WebXR Device API

From: Chris Wilson <cwilso@google.com>
Date: Wed, 23 Jan 2019 14:52:26 -0500
Message-ID: <CAJK2wqWtHUF0cVfGfa-jZcMF09Raf=d5z0L+p63dNkhrFfGSiA@mail.gmail.com>
To: public-immersive-web-wg@w3.org
Cc: Ada Rose Edwards <ada@ada.is>
This is a Call for Consensus (CfC) to publish the WebXR Device API as a
First Public Working Draft (FPWD) of the Immersive Web Working Group.

The LT (aka the Chairs and Editors) have concluded that now is a good time
to issue a First Published Working Draft
<https://www.w3.org/2018/Process-20180201/#first-wd> [1].  Publication of a
FPWD is a signal to the broader community that we are seeking review of the
specification in its early stages, although the specification is
specifically not being declared as complete at this time.

We would like to invite responses on this thread (privately or publicly)
from each Member company in the Working Group to declare their support for
or statement against issuing the current draft in Github
<https://immersive-web.github.io/webxr/> [2] as a First Published Working
Draft.

Silence will be taken to mean there is no Formal Objection
<https://www.w3.org/2018/Process-20180201/#def-Consensus> [3], but positive
responses are encouraged. Publication as a FPWD does NOT indicate that a
document is complete or represent Working Group consensus.  If there are no
Formal Objections by *January 30th, 2019 *(1pm PDT), the proposal will
carry and the Chairs will request that the Director approve publication as
FPWD.

The W3C Director takes Formal Objections seriously, and therefore they
typically require significant time and effort to address. Therefore, please
limit any Formal Objections to issues related to the scope of these
documents rather than technical content where the Working Group has not yet
made a decision, or where the specification may not be complete or correct.
Please include substantive arguments or rationale for consideration by the
Director in any Formal Objection.

If there are Formal Objections, the Chairs will contact the individual(s)
who made the Formal Objection to see whether there are changes that would
address the concern and increase consensus to publish. Depending on the
number and nature of the Formal Objections, the Chairs will either make a
decision either to pursue FPWD and report the Formal Objections to the
Director (as required by W3C Process), or to postpone publication until
there is greater consensus to publish.

- Chris and Ada

[1] https://www.w3.org/2018/Process-20180201/#first-wd
[2] https://immersive-web.github.io/webxr/
[3] https://www.w3.org/2018/Process-20180201/#def-Consensus
Received on Wednesday, 23 January 2019 19:53:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:11:53 UTC