RE: [webvr-internal] WebXR call agenda, Jan 9th 2018

I’ve taken some [redundant] notes as well from the meeting.  Copying here in case they are useful.

2018-01-09 WebXR Community Group Call
• Brandon (Google)
o meet.google.com is not ideal because it doesn't work with every browser. May switch to alternative.
o First call of new year
o Ask if any vendors have updates - None, on holidays
o Would like to set up another immersive web repo
• Talked about it as an incubator / ideas repo
• need name. "Ideas", "incubation" , "proposed work", "playground", "sandbox", "Emerging Concepts", "Work Proposals", "RFCs"
• Will be a place to bootstrap ideas
• Brandon prefers to be more along purpose of "proposals"
• Vote for name offline
• readme in repro to contain explainer of process
o Code of conduct for entire org would be good
• Maybe a separate repo, that individual repos can point to
o Over the christmas/new years break Brandon spent time working on input proposal
• 30% of spec text in place.
• Figuring out what verbiage would come along the spec
• Would like feedback on how spec is shaping up.
• Trevor (Mozilla)
o WebXR Polyfill
o Should make repo under the w3c.org?
o Should split repos that convert between different versions? (1.1 => 2.0, 2.0 => 1.1, fallback to "cardboard", fallback to "fake webxr" etc)
o Should move to immersive web repo?
o Have a single polyfill repo?
• Two trains: VR and AR experimental features
• Fork or separate repo?
• Will have common code between each polyfill type, so should be single repo.
• Consensus: Use one repo.
o Brandon and Jordan collaborating after call to coordinate moving polyfill under immersive web repo
o Jordan: Branches may work well
• Brandon
o Short term input proposals
o Related to another API that has not yet been released, can't talk too much yet
o Backing off on earlier input proposal until we find out what the unreleased API will be
o Would like something short term to ship earlier with WebXR
o Subset of input proposal, "select" and pointing, can be used earlier
o Allow use of "gamepad extensions" until other unreleased API is finished
o Nell / Microsoft: Existing gamepad API extension would need to be modified due to coordinate systems if used before unreleased API is ready
o Ada: Implement something that could be polyfilled later
o Joshua: Should show that API is not being abandoned, let people know that there will be a future even with transition plan needed.
o Kip:
• Perhaps we can implement a higher level API that compliments rather than replaces the future lower-level API
• 3 options:
• 1. Browser raycast against depth buffer from last submitted frame, returns hit in the screen space coordinate system
• 2. Describe location of targets in the webvr API, get events with target identified back, rather than specific coordinate (could be vertex information or pick-buffer)
• 3. Add ability to display DOM elements composited with WebXR scene, allow events to fire on those DOM elements using regular click events
• Brandon likes the direction, but needs thought to determine what could be done in shorter timeline
• Rafael
o Do we have everything we need from WebGL 2 for WebXR?
o ie. Multiview
o Can we maybe expose this in WebGL 2 as an actual texture array?
o Maybe eliminate opaque framebuffers?
o Once using multiview, must be used everywhere
o Multiview limits antialiasing
o Artem:https://www.khronos.org/registry/OpenGL/extensions/OVR/OVR_multiview_multisampled_render_to_texture.txt
o Proposal is that you render to your texture arrays. Specific indexes would be used for left, right eyes.
o Support WebGL 1 with Side-by-side and require texture arrays for WebGL 2?
o Brandon: Drop multiview for WebGL 1?
o Rafael: If we do WebGL 1, then do it well.
• Next meeting in two weeks


Cheers,
  Kearwood “Kip” Gilbert

From: 'Brandon Jones' via webvr-internal
Sent: January 8, 2018 2:41 PM
To: public-webvr@w3.org
Subject: [webvr-internal] WebXR call agenda, Jan 9th 2018

First call of the new year! We've had a long break due to the holidays, so I expect there will be a fair amount that people want to cover. As usual, please respond with any items you would like to have added to the agenda.

Call date: Tuesday Jan 9th (and every other Tuesday thereafter)
Call time: 1:00 PM PST for one hour
‎Call in number: +1 319 332 7047‬
PIN: ‪9744#‬

Call Agenda Items:
• Details of "Ideas" repo creation (Including name, explainer, code of conduct, etc.)
• Progress on WebXR Device API spec
• WebXR polyfill
• Short-term input solutions
As this is only the second call to use a new call-in system (Google Meet) we'd continue to appreciate any feedback on difficulties joining the call.

Thanks!
--Brandon Jones
-- 
You received this message because you are subscribed to the Google Groups "webvr-internal" group.
To unsubscribe from this group and stop receiving emails from it, send an email to webvr-internal+unsubscribe@googlegroups.com.
To post to this group, send email to webvr-internal@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/webvr-internal/CAEGwwi3Xc7aJSFzt%3Dq%2BbiQM07VsAkNxHOOxSyc7uj2R8HjMeDA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.