POST
This is how Myrl works: a visual description of Outeroperability
When we designed Myrl we had two goals in mind:
1) Integrating virtual worlds and the web, making virtual worlds more visible on the web
2) Connnecting worlds to create an integrated immersive playground.
We designed Myrl as a layer built on top of each virtual world, and we are now developing the integrations between each virtual world and our web platform.We work on a three levels Integration: SIGNUPS / AVATARS / CONTENT. Each level is independent from the others and can be deployed separately.
By integrating each virtual world with a common web based gateway/hub, we are then able to run cross-world applications (identity management, content management, messaging and so on) and ultimately to activate data exchanges between the various worlds, always passing through the same web-hub.
Right now we are working on cross-world messaging, but future releases of the platform will implement cross-world gaming, currency exchange, assets and appearance management. And this is what Kzero defined as Outeroperability as opposed to Interoperability.
Here’s a simple graph with a nice old fella on the phone that provides a visual explanation of our model. As you know we are experimenting here, so we are always up for a chat to discuss, improve, glorify, dismiss, destroy or bury this ;-)



