If you want Apple involved they don’t like working under Khronos. IP disputes in the past. See also WebGPU
API started as WebVR, was renamed to WebXR since now accommodates more than VR (AR, MR…)
I worked with Vlad at Mozilla in the early WebVR days (I co-design while at Mozilla and now maintain A-Frame)
I think this is the wrong post
I'm talking about WebXR, which is for some reason the name of the standard developed by W3C.
"As such it may seem like WebXR and OpenXR have a relationship like WebGL and OpenGL, where the web API is a near 1:1 mapping of the native API. This is not the case with WebXR and OpenXR, as they are distinct APIs being developed by different standards bodies."
from https://github.com/immersive-web/webxr/blob/master/explainer...
Re:WebXR
by moron4hire on Saturday May 27, 2023 @03:59PM
(#36097700)
There are many other browser APIs named "WebSomething". WebAudio, WebUSB, WebBluetooth. This is a really silly complaint to have.
Re:WebXR
by foolswisdom on Sunday May 28, 2023 @07:33AM
(#36103136)
The complaint wasn't about the web prefix, it's the ambiguity of the name.
Re:WebXR
by moron4hire on Sunday May 28, 2023 @10:45AM
(#36104424)
Alright, fine. WebVR predates OpenXR by about 3 years. When WebVR was renamed to WebXR, OpenXR existed in name only, and nobody knew if, once the spec even came out, it would get adopted. It wasn't a well-known name at large by that point, and there was significant concern from the W3C to avoid confusion with creating separate WebVR and WebAR APIs. So, "they should have been careful to avoid confusion with OpenXR" gets it backwards, over-assigning the ownership of "XR"-named things to Khronos.
Source: I was there for the discussions.
The name choice is interesting. If one of the first things in your FAQ is "the name probably made you think this is thing X. it's not", then maybe there was a flaw in your naming process.