Re: Charter: please review!

The "scope" section feels like it could be expanded a bit to better
encompass the deliverables. For example, it currently calls out hit testing
explicitly but none of the scope bullet points feel like they cover
lighting, occlusion, real world geometry, anchors, etc.

I'd suggest maybe changing the line:

For augmenting reality on devices which support AR, enable XR sessions that
provide real-world display, and provide the ability to hit-test surfaces in
the real world.

To something like this:

 - On devices which support AR, enable XR sessions that provide real-world
display.
 - On devices which support AR, provide information needed to allow virtual
imagery to feel like a natural part of the real-world display, such as
surface, lighting, and object tracking data.

On Wed, Feb 12, 2020 at 3:58 AM Ada Rose Cannon <ada@ada.is> wrote:

> Seeing it all written out makes me very excited for the next two years.
>
> Ada
>
> On Wed, 12 Feb 2020 at 00:19, Chris Wilson <cwilso@google.com> wrote:
>
>> I have updated the proposed recharter from our conversation at the face
>> to face meeting: please take a look at
>> https://w3c.github.io/immersive-web-wg-charter/immersive-web-wg-charter.html and let
>> me know what you think; comment here or file issues on the charter repo
>> <https://github.com/w3c/immersive-web-wg-charter/issues>.
>>
>> Comments from the commit
>> <https://github.com/w3c/immersive-web-wg-charter/commit/d1c0f08b7586b99724c1979ffe510307062ffbca>
>> :
>>
>> added "Potential Normative Specifications":
>> Access to Raw Camera FramesImage Detection
>> Face Detection
>> Depth/Occlusion APIGaze tracking (Diane)
>> Navigation
>>
>> Stated all specs are still expected to be incubated.
>>
>> Stated in RWG that it may turn into multiple deliverables.
>>
>> Changed wording in Anchors - "in the world" -> "in local coordinate
>> systems"
>>
>> Anchors only inside a session, not across sessions.
>>
>> Remove list of "such as..." devices.
>>
>> Put in estimates for completion dates.
>>
>