BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Sabre//Sabre VObject 4.5.8//EN
CALSCALE:GREGORIAN
LAST-MODIFIED:20210406T205008Z
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-MICROSOFT-CDO-TZID:13
BEGIN:STANDARD
DTSTART:20201101T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:STANDARD
DTSTART:20211107T090000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20210314T100000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:e04319d4-6887-4325-b02c-c4eff5814093
DTSTAMP:20210406T205008Z
SUMMARY:Immersive Web Group Calls
DTSTART;TZID=America/Los_Angeles:20210406T120000
DTEND;TZID=America/Los_Angeles:20210406T130000
DESCRIPTION:https://www.w3.org/events/meetings/e04319d4-6887-4325-b02c-c4ef
 f5814093/20210406T120000/\n\nCalls for discussing issues with WebXR and ot
 her Immersive Web techologies\n\nJoining Instructions\nMeeting number: 648
  395 336 Meeting password: w3c\n\nIRC: #immersive-web\n\nIRC and Scribing 
 Instructions\n\nAgenda: https://github.com/immersive-web/administrivia/blo
 b/main/meetings/wg/2021-04-06-Immersive_Web_Working_Group_Teleconference-a
 genda.md\n\nAgenda\n\n### Call Agenda\n\nThis agenda can be viewed and upd
 ated on [Github](https://github.com/immersive-web/administrivia/blob/main/
 meetings/wg/2021-04-06-Immersive_Web_Working_Group_Teleconference-agenda.m
 d).\n\nIf you would like to add an item to the agenda or volunteer to scri
 be please open a pull request against this agenda.\n\n* [administrivia#154
  Home for Raw Camera Access proposal / repository](https://github.com/imme
 rsive-web/administrivia/issues/154) [requested by bialpio](https://github.
 com/immersive-web/administrivia/issues/154#issuecomment-806276186)\n> This
  makes sense - we have been receiving requests for raw camera access API a
 nd were postponing working on it mostly due to privacy concerns\, but the 
 other side of the argument is that raw camera access allows for more rapid
  prototyping of solutions while UA vendors work on standardizing privacy-p
 reserving APIs. This was also something that was mentioned during yesterda
 y's call in the context of marker tracking API - I believe 8th Wall would 
 be interested in experimenting with JS-powered marker tracking from within
  WebXR. There are also use cases that are only possible with raw camera ac
 cess (and there may be more use cases that we don't even know we should be
  solving). I think Computer Vision is where those discussions & API incuba
 tions were supposed to happen so it'd seem to me that there was already a 
 need for such features - creating a new repository would only help with th
 e organizational aspect of the work.\n>\n>For now I should be able to proc
 eed in my private repository\, but I'm mostly worried that folks will be h
 esitant to participate due to IP concerns. @-ing people who may have some 
 opinion on this as well: @klausw\, @nbutko\, @thetuvix.\n>\n> In case we s
 till do not have a clear way forward by the time of the next meeting.\n\n*
  [webxr#1178 Use session's requested features instead of session device's 
 enabled features to check if a reference space is supported ](https://gith
 ub.com/immersive-web/webxr/issues/1178) [requested by Manishearth](https:/
 /github.com/immersive-web/webxr/issues/1178#issuecomment-805161134)\n> So 
 basically the existing design falls out of the following constraints:\n>\n
 > - We want people to be able to request permissions _before_ a session st
 arts to time prompts\n> - We want people to be able to request permissions
  _during_ a session so they need not overwhelm the user with prompts for f
 eatures that may not be needed unless the user performs certain actions (l
 ike clicking an in-ui "enable experimental hand tracking" button)\n> - We 
 wanted to use existing APIs as much as possible instead of inventing our o
 wn permissions system\n>\n>The second one is what's biting us in particula
 r here\, we want the following to work:\n>\n>```js\n>let sess = await navi
 gator.xr.requestSession("immersive-ar"\, { requiredFeatures: ["local-floor
 "]})\;\n>// ...\n>\n>navigator.permissions.query({name: "xr"\, mode: "imme
 rsive-ar"\, requiredFeatures: ["hand-tracking"]})\;\n>\n>sess.inputSources
 [0].hand.doSomething()\;\n>```\n>\n>\n>There are basically a couple paths 
 forward for us here:\n>\n>## Keep it as is\n>\n>The status quo is _fine_\,
  but it does have the weird pitfall that consecutive sessions (or cached p
 ermissions) may lead to code working in some cases but not in others. It's
  a good way to induce "works on my machine" if the permission caching for 
 your setup leads to code just working\, but other people have sessions get
  rejected.\n>\n>There can also be perf implications on implementations tha
 t do not spin up system resources when the relevant features are not yet e
 nabled\; e.g. ideally sessions without hand-tracking do not need to set up
  hand tracking until needed.\n>\n>## Add a mid-session feature request API
 \n>\n>We can add a `requestAdditionalFeatures({required:\, optional:})` AP
 I. This is unfortunate\, we built the permissions API stuff to avoid doing
  this. But it's probably a minor API\, and the permissions API is still us
 eful for controlling when permissions are _prompted_ vs when they are used
 .\n>\n>## Add an optional `session` parameter to `XRPermissionDescriptor`\
 n>\n>We can continue to use the permissions API\, but add a way to "tag" p
 ermissions onto existing sessions by giving it a nullable `session` parame
 ter. This makes it possible for the permissions API to still be used pre-s
 ession to control prompt times\, but will still be useful during the sessi
 on to enable new features.\n>\n>## Add an `optionalFeaturesIMayAskForLater
 ButDontPromptForThemYet` parameter to `requestSession()`\n>\n>Lets a sessi
 on declare all features it _may_ rely on. Imperfect\, but works. Likely to
  be confusing even if we can come up with a better name for it.\n>\n> to d
 iscuss this next meeting\n\n### Immersive Web Working Group Teleconference
  - 2021-04-06\n\n<table>\n<tr><td> San Francisco (U.S.A. - California) <td
 > Tuesday\, April 6\, 12:00 PM PDT\n<tr><td> Boston (U.S.A. - Massachusett
 s) <td> Tuesday\, April 6\, 3:00 PM EDT\n<tr><td> London (United Kingdom -
  England) <td> Tuesday\, April 6\, 8:00 PM GMT+1\n<tr><td> Paris (France) 
 <td> Tuesday\, April 6\, 9:00 PM GMT+2\n<tr><td> Tokyo (Japan) <td> Wednes
 day\, April 7\, 4:00 AM GMT+9\n<tr><td> Corresponding UTC (GMT) <td> Tuesd
 ay\, April 6\, 7:00 PM UTC\n</table>\n\n### Logistics\n\nChair: Ada Rose C
 annon\n\nScribe:\n\nIRC: [irc.w3.org](http://irc.w3.org/):6667 #immersive-
 web [Instructions](https://github.com/immersive-web/administrivia/blob/mai
 n/IRC.md)\n\nCall Details can be found on the [Internal Mailing List](http
 s://lists.w3.org/Archives/Member/internal-immersive-web/2019Feb/0002.html)
 \n\nIf you are unable to login to view the call details please ask on the 
 IRC before the call.\n\nFor assistance go to https://mit.webex.com/mit/mc 
  and on the left navigation bar\, click "Support".\n\n### Help Wanted\n\nH
 ere are some issues which are good issues to get involved in\, if you have
  taken responsibility for one leave a comment in the issue:\n\n- [webvr-po
 lyfill-dpdb#34 Create a helper script/web page for generating values for a
  new device](https://github.com/immersive-web/webvr-polyfill-dpdb/issues/3
 4)\n- [webxr-input-profiles#69 Resizing the window changes the model viewe
 r's aspect ratio](https://github.com/immersive-web/webxr-input-profiles/is
 sues/69) [<small>[Future]</small>](https://api.github.com/repos/immersive-
 web/webxr-input-profiles/milestones/4)\n- [webxr-gamepads-module#16 Add li
 nk to the registry](https://github.com/immersive-web/webxr-gamepads-module
 /issues/16) [<small>[Pre-CR]</small>](https://api.github.com/repos/immersi
 ve-web/webxr-gamepads-module/milestones/1)\n- [webxr#953 Typescript defini
 tions](https://github.com/immersive-web/webxr/issues/953) [<small>[Pre-REC
 ]</small>](https://api.github.com/repos/immersive-web/webxr/milestones/16)
 \n- [webxr#1115 Explicitly spec when inline animation frame loops are susp
 ended](https://github.com/immersive-web/webxr/issues/1115) [<small>[Pre-RE
 C]</small>](https://api.github.com/repos/immersive-web/webxr/milestones/16
 )\n- [webxr-samples#80 Example 17: "Hands Test" is missing](https://github
 .com/immersive-web/webxr-samples/issues/80)\n- [administrivia#147 Platform
 /Framework Feedback](https://github.com/immersive-web/administrivia/issues
 /147)
STATUS:CONFIRMED
CREATED:20210406T054159Z
LAST-MODIFIED:20210406T205008Z
SEQUENCE:2
ORGANIZER;CN=W3C Calendar;PARTSTAT=ACCEPTED;ROLE=NON-PARTICIPANT:mailto:nor
 eply@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Immersive Web Comm
 unity Group:mailto:public-immersive-web@w3.org
ATTENDEE;CUTYPE=GROUP;ROLE=OPT-PARTICIPANT;RSVP=FALSE;CN=Immersive Web Work
 ing Group:mailto:public-immersive-web-wg@w3.org
LOCATION:Teleconference
RECURRENCE-ID;TZID=America/Los_Angeles:20210406T120000
END:VEVENT
END:VCALENDAR
