-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create EXPLAINER.md #13
Conversation
Create the initial file for the explainer. This PR addresses two repo issues: Structure of the overall document (immersive-web#2) Accessing real-world geometry data (immersive-web#4)
|
||
<span style="color:#24292e;">The approach that a user agent takes will likely depend upon the mechanisms offered by the underlying AR system. For example, a subsystem may have mechanisms for sandboxing real-world geometry between app sessions.</span> | ||
|
||
### Object or Image Identification |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note: Subsequent sections to be filled in, but headers are included to show proposed document structure.
##### Precision of Real-World Geometry | ||
|
||
Even a little real-world geometry data poses a potential security risk. For example, exposing a simple API such as hit-testing real-world objects with a ray can be used quickly to identify the floor plane and user height, and with enough data points can be used to build a point cloud in space from which real-world geometry can be inferred. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@blairmacintyre and i have spoken about designing an experiment to determine at what point (expressed in time + user gesture + device) hit-testing becomes 'equivalent' to a world point cloud
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is that experiment something where the results can be available in the next week? If not we can add results later in a subsequent PR
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just wanted to toss it out there in case anyone else was interested actually...
Do we need any more discussion on this? I'm inclined to say that having a partial explainer.md would be good to have sooner rather than later |
I have a few off-list comments to add, plus some changes to incorporate
feedback comments in the doc. I'll do those Monday, then unless anyone
objects I'd like to commit this PR, close out the related issues, and move
to the next section in the explainer.
…On Fri, Sep 28, 2018 at 1:06 PM, Diane Hosfelt ***@***.***> wrote:
Do we need any more discussion on this? I'm inclined to say that having a
partial explainer.md would be good to have sooner rather than later
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#13 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXSP1CbCLjNOAtkXltNfmow9Pu-W6GOwks5ufoFUgaJpZM4W1A1R>
.
--
Thanks,
John
|
Create the explainer file
This PR addresses two repo issues:
Structure of the overall document (#2)
Accessing real-world geometry data (#4)