Rather than focusing on what the metaverse means in a future-prediction sort of way, the Metaverse Standards Forum is designed to focus on the building blocks of what developers need today. Other people (like me) can bicker about the nomenclature.
What Virtual Worlds Need
When designing virtual worlds—and especially those worlds that are meant to interact with the real one—dealing with huge amounts of data is inevitable. Every object or character in a videogame is made up of geometry data (that is, the shape of the object), textures, physics traits like weight and mass, behaviors, animations, sounds, and so much more.
Khronos hopes that MSF’s standards will make much of that data as easily interoperable as, say, a JPEG is today. Famously, JPEGs are so easily transferrable and so widely supported that no amount of cryptography can stop someone from right-clicking and saving one. For comparison, 3D objects often don’t even know which way is up. Move an object from one game engine to another and—if you can import it at all—it may come in broken.
This is where one Khronos project, GLTF, aims to help. This open standard, initially released in 2015, competes with other 3D formats like OBJ and FBX files. Allegorically, you can think of OBJ as a bit like old BMP files: They’re technically pictures, but the format is extremely limited, inefficient, and clunky. Meanwhile, FBX is a bit like PSDs. They’re more powerful, but it’s a proprietary format owned by a single company.
In this painfully strained metaphor, GLTF would be a bit like the JPEG of the 3D world. Or at least Khronos hopes it will be. Part of what made the JPEG format so crucial is that it was an open standard that was lightweight and useful enough to gain widespread adoption. GLTF may become just as popular, or it could end up just another item in the long list of file types you can import into Blender, but never use.
But the need for interoperable standards will always exist, if only as a check on proprietary technology. “If there’s a big lag between the technology becoming available and the standard that makes it openly available,” Trevette explains, “then there’s a danger that proprietary technologies are going to get baked into the infrastructure of the metaverse, and I don’t think anyone really wants that.”
“But if there’s no standard available, you don’t have a choice.”
Selling the Boring Stuff
If it’s difficult to wrap your head around the idea of developing standards for a virtual world that might not ever exist, don’t worry. You’re not alone. Despite Khronos calling it the Metaverse Standards Forum—which, as Khronos is careful to note, it’s helping to bootstrap but will not be running in the future—the MSF isn’t overly concerned with defining what the metaverse means. Or even whether the term continues to be used at all.
“And that texturing, ‘metaverse,’ might get replaced. I don’t think that matters actually. You know, it might go the way of ‘information superhighway.’ We don’t use that texturing much more anymore,” Trevette says. Indeed, while no one uses the word “cyberspace” anymore, we still use the internet that it once described.
But the idea of a fantasy virtual world, no matter how impractical or even undesirable, is more exciting than sitting people down and explaining the importance of interoperable, nonproprietary data exchange formats. And in the meantime, a wide array of exciting tech, from virtual film productions to photogrammetry to augmented reality, is changing how we interact with the internet.
Will that manifest as Ready Player One? Or will it be just a collection of disparate industries doing a lot of really cool stuff, but not necessarily coalescing into a singular fantasy world? Hard to say. Well, maybe not that hard. But no matter what the future ends up being, someone’s gotta build it.