WebKit is working on `<model>`. Let's figure out how that proposal could work with `<map>` for progression from 2D -> 3D

[prushforth]

It seems that WebKit is proposing a <model> HTML element. It would be ideal if we could join forces to persuade that team that spatial data is a keystone for XR, and their <model> might be made to work well with <map> .

Let's discuss use cases for how to conceptually integrate the two proposed elements, and how they could share real-world coordinate systems.

/cc @cperey @lieberjosh @janerivi @hober @othermaciej

[prushforth]

For one thing, <feature> could of course contain a <model> in its <properties> element, allowing a feature to be interrogated in the standard fashion (popup/ toast / sliding drawer / sidebar) and the model content presented therein.

But perhaps it could be even more tightly integrated via feature links that we've recently implemented

<feature>
  <featurecaption>Model of a floor of a high-rise building</featurecaption>
  <properties>
    <h1>Model of a floor of a high-rise building></h1>
  </properties>
  <geometry>
    <a href="link to a model source">
      <polygon>...</polygon><!-- for example -->
    </a>
  </geometry>
</feature>

where, because the model is georeferenced, the browser could provide the AR experience, augmented by linked map content from within the building. I think a killer feature that allows MapML to play nicely here is the fact that map content from across the web, that was georeferenced via mapml, could be presented in the same augmented space that the user is actually in. In other words, it's the location of the user and that content that relates them, not just explicit links. Assuming a crawler was able to understand location / space, of course.