Closed ddorwin closed 4 years ago
here here. Let's create this repo!
There's an agenda item on tomorrow's call to discuss the new modules in which we're working and I'll tack this topic on to that.
I suspect that the majority of the near-term work mentioned above will happen in their respective modules and then we'll continue to work in proposals
for features that are farther ahead in terms of shipping hardware or consensus.
I agree that there are commonalities that are foundational to how specific world understanding APIs should be designed (separate from the designs themselves) and perhaps we need a place for that discussion similar to how we use the privacy and security repo to discuss, distill, and share those topics.
That said, we haven't seen much cross-org collaboration in that and other feature repos (all PRs from one org, the great majority of Issues from one org, etc) but we do see more of that in proposals
, so that will be a part of the discussion.
After recent discussions it seems pretty clear (as David suggested) that we have a number of foundational AR discussions before us so I'm in support of this proposal.
David's suggestion of using the name ar-common
works for me so unless I hear objections in the meantime I'll go ahead and create the repo on Wednesday.
Let's wait to see how tomorrow's call works out. I think a bunch of these things will end up in the AR core module, and some are already decided, and some should be incubations (e.g. some of these might go in performance repo)
Taking into account Tuesday's call I've created a new ar-common repo for discussion and communication of cross-API ideas related to augmented reality.
Summary
There are a number of items related to imperative AR that need to be worked out and defined that are independent of specific AR APIs (e.g., hit-test, Real World Geometry, anchors, camera access). While the CG has been incubating those specific APIs, there is no central place for these common dependencies. Rather than picking a single API’s incubation repository, we propose to create a common repository where we can work out the details independent of any single other incubation.
The work in this repository should feed into the core WebXR Device API spec and be a prerequisite for exposing specific AR APIs.
The repository name might be something like
ar-common/
orimperative-ar-common/
.Example topics
Potential topics include: