@torgo and myself did a review pass at this proposal during our "Kronos" VF2F. We found the answers to the privacy & security considerations section a bit small. This API claims to allow access to the camera image for use in compositing while ensuring the web site doesn't have access to it. This is a very important point to be made explicitly and normatively. The section about why the web site doesn't get access could use such clarity and the requirement ought to be normative (perhaps link to the XR Compositor section). The terminology section defines types such as opaque, pass through and additive light but it is hard to tie these to real-world scenarios or devices. Which of these defines a phone or computer with camera, headsets etc.? In particular, what is an example of Opaque AR? Section 2.5 of the spec can benefit greatly from a more complete motivational code example. Also, please clarify the use of the word Content - is this Site Content or Virtual Content? -- 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/462#issuecomment-769251938
Received on Thursday, 28 January 2021 17:34:51 UTC