Should move discussion and API for "creating anchor from hitTestResult" to hit-test API

[blairmacintyre]

Because the hit-test API was considered before the Anchor API, the overlapping detail ("create anchor from hit test result") is in the Anchor explainer.

It should be in the hit test API explainer, and the hit-test API should depend on Anchor API. The reverse of what we have now.

The reason for this is one of future clarity: as more APIs (image recognition, persistence, plane/geometry recognition and tracking) possibly use Anchors as a way of associating "stuff" with the physical world, the particular details of how anchors are created and used should be in those API discussions.

The Anchor explainer should describe the generic behavior of anchors, and keep the "create an Anchor from a pose relative to a space."

[avadacatavra]

+1 to this. Currently the security/privacy considerations in anchors reduce to hit testing. This will evolve based on how anchors are created and the capabilities of the anchors. I'd like to remove the confounding variable from anchors and keep it in the API of the creation method.

[avadacatavra]

/agenda