- From: Ada Rose Cannon <notifications@github.com>
- Date: Thu, 08 Aug 2019 02:40:28 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3ctag/design-reviews/issues/403@github.com>
こんにちはTAG! I'm requesting a TAG review of: - Name: WebXR Device API - Specification URL: https://immersive-web.github.io/webxr/ - Explainer: https://github.com/immersive-web/webxr/blob/master/explainer.md - GitHub issues: https://github.com/immersive-web/webxr/issues - Primary contacts: @NellWaliczek, editor @toji, editor @cwilso, WG co-chair @AdaRoseCannon, WG co-chair @TrevorFSmith, CG chair Further details: The WebXR device API has recently reached the point where it is considered a feature complete replacement for the deprecated WebVR API. We have also switched the work mode to be based around modules where the current "vr complete" WebXR device API acts as a core with other modules such as 'webxr-ar-module' and 'webxr-gamepad-module' building on that, we are not requesting a review for these modules yet. We are also working on a polyfill for the WebXR device API, https://github.com/immersive-web/webxr-polyfill/ In addition there are multiple browsers vendors working on implementations in their browsers. - Relevant time constraints or deadlines: [please provide] - [x] I have read and filled out the [Self-Review Questionnare on Security and Privacy](https://www.w3.org/TR/security-privacy-questionnaire/). Since the WebXR device API is working in a very different domain to the usual Web APIs we have put together a privacy explainer: https://github.com/immersive-web/webxr/blob/master/privacy-security-explainer.md - [x] I have reviewed the TAG's [API Design Principles](https://w3ctag.github.io/design-principles/) - The group where the work on this specification is: Immersive Web Working Group We recommend the explainer to be in [Markdown](https://github.github.com/gfm/). On top of the [usual information expected in the explainer](https://w3ctag.github.io/explainers), it is strongly recommended to add: - Links to major pieces of multi-stakeholder review or discussion of this specification: - Links to major unresolved issues or opposition with this specification: You should also know that... [please tell us anything you think is relevant to this review] We'd prefer the TAG provide feedback as (please select one): - [x] open issues in our GitHub repo for each point of feedback - [ ] open a single issue in our GitHub repo for the entire review - [ ] leave review feedback as a comment in this issue and @-notify [github usernames] -------------------------- _Please preview the issue and check that the links work before submitting._ In particular, if anything links to a URL which requires authentication (e.g. Google document), please make sure anyone with the link can access the document. ¹ For background, see our [explanation of how to write a good explainer](https://w3ctag.github.io/explainers). -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3ctag/design-reviews/issues/403
Received on Thursday, 8 August 2019 09:40:52 UTC