Do you have any thoughts on this? Good idea or not?
From the README:
We propose adding a <model> element to HTML that displays 3D content using a renderer built-in to the browser.Introduction
HTML allows the display of many media types through elements such as <img>, <picture>, or <video>, but it does not provide a native manner to directly consume 3D content. Embedding such content within a page is comparatively cumbersome and relies on scripting the <canvas> element. We believe it is time to put 3D models on equal footing with other, already supported, media types.
There is a variety of prior art here: For example, three.js and Babylon JS are WebGL frameworks that can process many different formats. Then there is the model-viewer project which shows models inline in a web page, and also allows users on some devices to see the 3D object in augmented reality. And iOS Safari has the ability to navigate directly to an augmented reality view with its [AR Quick Look feature] (https://webkit.org/blog/8421/viewing-augmented-reality-assets-in-safari-for-ios/
However, there are cases where these current options cannot render content. This might be due to security restrictions or to the limitations of <canvas> (see below for more details on motivation).
The HTML <model> element aims to allow a website to embed interactive 3D models as conveniently as any other visual media. Models are expected to be created by 3D authoring tools or generated dynamically, but served as a standalone resource by the server.
Additionally, besides the simple display of a 3D model, the <model> element should have support for interactivity and animations while presented within the page, and also support more immersive experiences, such as augmented reality.
This proposal does not aim to define a mechanism that allows the creation of a 3D scene within a browser using declarative primitives or a programmatic API.