Yeah, there are a lot of VRML replacements coming out right now. X3D[0] is the official VRML 2.0, but I believe it requires a plugin (well, there is a THREE.js importer, but at that point you really should be using glTF[1] or THREE.js's own JSON format). There is GLAM by Tony Parisi[2], who actually did a lot of work on the original VRML. And very recently, Mozilla released A-Frame[3], which is trying to also build an ecosystem of reusable Web Components. All interesting in their own right. I think A-Frame has the best chance of succeeding, in that it has the most high-profile backing right now.

That said, they're all pretty low level. I specifically do not want users doing wholesale scene design in a hand-written script format. For the work I want to do, that's what a 3D modeling package like Blender is for, and as hard was Blender is to use, it's a lot easier to get a non-trivial scene working with it than hand-writing XML code. My Live-Editable 3D Environment demo is more of a stop-gap for a much more drag-and-drop experience I'm planning for the future.

The goal (and I'm certainly not there yet, but I've been making pretty fast progress) is to make something more akin to a Window Manager for VR. In the same way that DWM on Windows or X on Unix provide a higher level of abstraction for GUI elements beyond raw graphics primitives, I want to be able to provide a set of GUI elements that are useful for adapting HTML forms in VR. With Primrose, you shouldn't have to model a button that a user can click unless you have a specific need to completely redesign a button. There should be a button already that you can place on your scene/form with the same ease you would an HTML button in the DOM.

Long-story short, I'm trying to make the VB6 of WebVR.

[0] http://www.web3d.org/

[1] https://github.com/KhronosGroup/glTF

[2] http://tparisi.github.io/glam/

[3] https://aframe.io/