<blair> that's what I get for being on time, was weird to only see a few people there! I'll fix that by going and grabbing tea
<bajones> For the agenda, I asked Mounir from Google to do a quick introduction today, since he'll likely be working with the group more going forward.
<cwilso> scribenick leonard
IMounir Lamouri intro -- leading the AR work at Google. Beendoing spec in multiple areas
\/IM/M/s
<NellWaliczek> https://github.com/immersive-web/webxr/issues/786#issuecomment-520656458
Chris: Scroll to bottom comment
in #786
... concern about providing multipel ways to create AR
content
... XR/AR core includes session creation, etc. Includes basic
session privacy/security concerns.
<cwilso> Environment blend mode will move to this AR core spec (from the WebXR core), enabling developers to differentiate between ‘additive’ and ‘alpha’ environment blend modes, and this is also where we will specify what environment blend modes will return for "immersive-vr" sessions.
Chris: Move environmentBlendMode out of WebXR core into ARcore. WG will define what the ebm . See comment from Chris.
If see-through AR h/w content may support (but not required) to handle immersive VR; then ebm must be set correctly.
Bradon: Changes do not prevent shipped implementations
Rik: Likes change. No more
objections. Resolves concern about having AR out of immersive
VR spec. Can close #786.
... &Nell: environmentBlendMode issue is separate and will
be handled, then closed.
Brandon: Requests explict comment from MS.
Alex: Agress with change
<cwilso> s/agress/agree
<Zakim> kip, you wanted to give support from Mozilla
Nell: Taking steps to make sure that Brandon and Nell do not cause time delays with spec
Kip: Mozilla supports change and offers help
Chris: Turn over to Nell
<NellWaliczek> https://github.com/immersive-web/webxr/issues?q=is%3Aissue+is%3Aopen+label%3Aar-module
Nell: A number of issues were
tagged for movement to other repos. See Nell's link.
... Looking at AR hit testing, a conversations needs to happen
with people working in various AR-related repos to make
sure
... the taget repos are correct.
... No objections, issue migration will proceed as
indicated
Chris: Other business?
<cwilso> https://github.com/immersive-web/webxr/issues?q=is%3Aissue+is%3Aopen+label%3Aagenda
Brandon: Manish worked with Nell and wrote ~6 PRs last night.
<NellWaliczek> https://github.com/immersive-web/webxr/issues/791
Nell: Issue #791: "XRSessionInit
has generic types and is not future proof"
... concern about future moduels breaking core because of
necessary changes as indicated in the above PR
Brandon: Would it make sense to make the changes with optional features?
Nell: Not possible to predict future requirements. Allow for additional permissions to be requested up front.
Rik: Optional feature for hand
motion that might require features that are more strings.
... Manish wanted features with DOM string.
Nell: Do a union of DOM string and object.
Manish: Against enums
Rik, Manish, Nell: Detailed discussion of DOM strings, dictionary, enums, etc.
Manish: Pretty standard because WebIDL does not allow certain structures. Proposed method is commonly done.
Mounir: <provided additional details and comments>
Nell: Very concerned about new
modules forcing a change to the Core spec. She believes that
current proposal is sufficient to prevent core changes.
... Asks Brandon to take point with usibility people to verify
proposal
... Requests poll for writing WG.
Chris: Non-first Working Draft does not require conscensous. 1st does.
<LocMDao> Nice seeing you all in my first time back in a while!
<cabanier> Manishearth: the permission API uses dictionaries. I think doing something exactly like it would work. https://github.com/immersive-web/webxr/issues/791#issuecomment-519934890
<cabanier> Manishearth: I think if your proposal works in the UAs, it will be very flexible
<Manishearth> cabanier: yeah so that could work with individual modules adding more optional fields
<Manishearth> so it's a single dictionary in the union
<Manishearth> multiple dicts would be iffy
<cabanier> yes
<cabanier> it would be a base "class"
<Manishearth> we already have a way of "extending" enums and dicts in bikeshed, see the AR module
<cabanier> and then others derive from
<cabanier> ok
<Manishearth> we want to stay away from actual dictionary inheritance though, that doesn't work the way you'd expect
<Manishearth> (we used to have some of this in XRSessionInit and we got rid of it because it's weird)
<cabanier> how did the permissions api do that?
<cabanier> for instance https://w3c.github.io/permissions/#midi
<Manishearth> cabanier: the permissions api is working on objects
<cwilso> title: Immersive Web WG
This is scribe.perl Revision: 1.154 of Date: 2018/09/25 16:35:56 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: Irssi_ISO8601_Log_Text_Format (score 1.00) FAILED: s/agress/agree/ Present: cwilso cabanier bajones NellWaliczek LocMDao alexturn No ScribeNick specified. Guessing ScribeNick: Leonard Inferring Scribes: Leonard WARNING: No date found! Assuming today. (Hint: Specify the W3C IRC log URL, and the date will be determined from that.) Or specify the date like this: <dbooth> Date: 12 Sep 2002 People with action items: WARNING: IRC log location not specified! (You can ignore this warning if you do not want the generated minutes to contain a link to the original IRC log.)[End of scribe.perl diagnostic output]