#550: WebXR Depth API

Visit on Github.

Opened Aug 19, 2020

Saluton TAG!

I'm requesting a TAG review of WebXR Depth API.

As Augmented Reality becomes more common on the smartphone devices, new features are being introduced by the native APIs that enable AR-enabled experiences to access more detailed information about the environment in which the user is located. Depth API is one such feature, as it would allow authors of WebXR-powered experiences to obtain information about the distance from the user’s device to the real world geometry in the user’s environment.

Further details:

  • I have reviewed the TAG's API Design Principles
  • The group where the incubation/design work on this is being done (or is intended to be done in the future): Immersive Web CG
  • The group where standardization of this work is intended to be done ("unknown" if not known): Immersive Web WG (planned)
  • Existing major pieces of multi-stakeholder review or discussion of this design: https://github.com/immersive-web/depth-sensing/issues
  • Major unresolved issues with or opposition to this design: No issues exist yet, this is an early stage proposal that has not been fully reviewed.
  • This work is being funded by: N/A.

You should also know that...

N/A.

We'd prefer the TAG provide feedback as (please delete all but the desired option):

🐛 open issues in our GitHub repo for each point of feedback

Discussions

2021-09-20

Minutes

Rossen: drafts closing comment

CLOSED

2021-09-20

Minutes

Dan: A response from Piotr... doesn't think it'd be controversial to add more text.. similar conversation around raw camera access, he's getting a lot of feedback about fingerprinting and privacy issues.. I want to say we'll review it when there's a PR

Rossen: yeah.. a lot of squishy language, UAs 'could'.. prefer to see more normative

Dan: yeah

Rossen: if this is a note that'd be fine. if this is a spec they need to work more on the language, but right direction

Dan: in your note about fingerprinting he did talk about the S&P questionnaire. I'm wondering if there's anything else we can point him to, unsactioned web tracking finding or something, that would underscore the issue. Great feedback that there needs to be more normative text.

Rossen: can leave a comment, schedule for next week. Outside of fuzzing, once this is done, we should consider closing it?

Dan: I think so.

2021-09-Gethen

Minutes

Dan/Rossen: writes proposed comment