This is a living draft and we are actively migrating the conversations to github discussions.

• Recap Video I 04/01/21
• OMI Meeting I 04/11/21
• Notes for recap video II 04/08/21
• Video Balancing Feasibility, Viability, and Usability (we need more than devs)
• Notes for blog: Working together, and balancing expertise 04/09/21
• OMI Meeting II 04/23/21
• A note about this notion

💡a quoted tweet that started this iteration of the conversation

🔗 https://twitter.com/mrmetaverse/status/1377233593106305024

With the accelerated creation of Metaverses and video games, I want to build an open inventory system that allows users to take their gear/loot with them.

Users can travel across worlds and level up their gear. When you buy a skin in a game, you can use it in other similar games. When you mint a starship you can use it in space themed games, etc.

We all love our loot. Sometimes that's 80% of the fun.

I'd like the repo to be open. Indy devs could run a simple npm i AngellXR/metaloot (or something like that) to access an open repo of assets for their games. Devs can set tags of what is and isn't allowed in their world.

This could really scale. Imagine owning your gear, and yes this works with NFTs but it could also be simpler than that for more generic items (like Assets you don't have to own)

🚨 Important Callouts 🚨

There is a difference between the OMI protocol and products that could be built using the Protocol. When we talk about an ownerless standard for connecting the Metaverse, we are talking the protocol. However, when we talk about UI, how the end user may interact with it, or ways of using the protocol (crafting apps, marketplace, plugins, etc.) that is separate from this initiative.

I'd like us to test the OMI work on experimental products like UI's, and crafting, as user stories for implementing the OMI. Therefore, I am all for these concepts, but will encourage everyone to push back when scope gets muddled. It would be a dream to continue working together, discovering and delivering value after value together.

💡To Roberts point, we may want to break this up into smaller standards / protocol:

*I think there's got to be a variety of smaller standards/protocols:

• Identity (Public and private details for a user. Access control for private details)
• Social Graph (friends or follower model)
• Chat/Notifications (I personally like Matrix for this, idk if this is so much of the protocol as much as a way to directing users to chat with each other across apps and a channel for notifications for friend requests/invites/trading/etc.)
• Scenes/Objects/Avatars (glTF + component extensions, VRM glTF extensions for avatars)
• Verifiable Credentials (Used for asset ownership, identity verification, etc)
• User Collections (Used for inventories, avatars, etc. probably name-spaced for apps with access control. Linked from identity or actions)
• Action Protocols (trading, adding/removing friends, invites. Client-Server, and Server-Server protocol)

Things I wouldn't cover would be:

• Game/App specific mechanics
• Realtime networking (outside of chat/push notifications)*