[khazhoux]

I was tinkering in that space in the mid-90s, and always felt the file format was a missed opportunity, and wasn't taking any of the lessons of HTML.

What I wanted (but never built) was a semantic file format, something like:

    <room style="square" id="room1">
      <wall direction=north>
        <picture frame="modern" src="http://foo.com/fancycat.jpg" />
      </wall>
      <wall direction=south>
        <door room="room2" />
      </wall>
    </room>

[JayStavis]

Sounds like you are looking for react-three-fiber, which looks just like this!

The examples, demos, and development experience are great, but since it's based on web tech hasn't made a big splash yet with the bigger 3D content businesses.

You can actually render a gltf as a JSX tree too with gltfjsx: https://github.com/pmndrs/gltfjsx

[sien]

There was a company in Sweden that built a system that used VRML and extended like that where you could define what the nodes were and reference and re-use them. The system also enable Python to script behaviour.

It also used the PHANToM for haptic feedback and used a 3D stereoscopic display

https://www.researchgate.net/figure/A-Reachin-Display-equipp...

The company H3D has built something similar.

https://h3d.org/

[cubefox]

That's way too high level and ambiguous. Something could look okay in one browser and totally crap in another.

[johnnyanmac]

>look okay in one browser and totally crap in another.

We're talking about 3d model formats where the current industry standard is a close sourced Autodesk nightmare. This is already the default situaton.

There's not much incentive to change either because animation and game studios tend to roll their own tech.

[datavirtue]

<surface orientation=x name="south wall" rotation=-125 .../>