---
# System prepended metadata

title: OMI meeting VI

---

# OMI meeting VI 
### June 2, 2021

## Introduction
- Introduced some new members
- Proposed agenda
- Chair election is today [Github](https://github.com/omigroup/OMI/discussions/17)
- Evo shared [this](https://www.uvm.edu/sites/default/files/working-agreements-defined.pdf) best practices reference for forming working agreements. **(+1 to working agreements)**

## Nominations: 
- Robert: 14 Yes
- Jesse: 13 Yes, 1 abstained
- Evo: 11 Yes, 3 abstained 

## Election complete

Robert, Evo, and Jesse to serve as OMI's chairs for 3 month term. 

## Virtual World URIs Discussion

Ref: [this github discussion](https://github.com/omigroup/OMI/discussions/23)

Nova:
> In order for OMI to succeed we need to get started. Break the ice. Fail faster. And keep it dead simple. 

> We want to get an initial spec out there, identify the pitfalls, and then refine our process as we go. 

They are calling for a specification for a standard Virtual World URI format.

In VR Chat, and others, you have a number of different worlds which are isolated from each other. These worlds are often  using a World ID. However, you may also have different instances of a World. Like a private version of the world with just your friends. 

WorldID -> InstanceID 

It gets trickier when you get into coordinates. I believe cryptovoxels and webaverse do this... One unified world with coordinates in the URL. 

Questions started popping up in [discord chat](https://discord.com/channels/770382203782692945/835221348443095070/849690048198213662)

**Q: What would be the mechanism for that?**
**A: On one or multiple servers somewhere, it would have method to convert your World URI into a URL.**

It could be decentralized or on Blockchain. We are not restricting ourselves to just blockchain, and we are not restricting ourselves to just the Fediverse. 

Can we uniquely identify platforms on a ledger? 

`{platform}://{x}/{y}/{z}`

Many platforms have their own defined URL system.

Tylo:
> so when creating a world in VRChat, if they adopted this spec, they would have to have a way to map the URI you're proposing to their internal world ID system

aksyn:
> and the inverse, so that a friend could send you this Virtual World URI

### URI Metadata Discussion

bengo:
> Instead of creating requirements about the syntax of the URI, I wonder if we could work out protocols about how to discover metadata about an arbitrarily-shaped world URI (an opaque http URI or DID), e.g. a 'preview that URI' as an embed, find related resources about where to send messages to 'jump to a location' in that world, etc.(edited)

> I'm kind of thinking we could use any URI syntax and support getting world-related metadata about them via something like webfinger (https://datatracker.ietf.org/doc/html/rfc7033#section-4.2) that lets you get metadata about an arbitrarily-shaped URI. (but without requiring a certain syntax for that URI).

> (for world embeds) -> arbitrary world uri -> link[rel=world-embed] -> 3d models of that world uri

> could also have link[rel=world-entrypoints] that would be links to all the resources that describe 'points I could jump into' to join the world.

Then the group discussed [Webfinger](https://docs.joinmastodon.org/spec/webfinger/) as a piece of infrastructure for the URI concept

bengo:
> I'm a big fan of what I'm hearing as a use cases for interop standards about 'indicating a world', 'seeing a preview of the world', 'discovering the ways I can join a world'. Thanks @Nova
Related "Follow your nose", a pattern I often think about https://patterns.dataincubator.org/book/follow-your-nose.html

aksyn:
> @bengo I was alluding to this early on as well, more than just static previews..  ultimately,I'd like to see portals in the local world, with realtime previews into that remote world, that you can then walk through
> @bengo so there may be multiple types of previews

bengo:
> all for that! Each 'type' could have a different link relation, or even a single link relation to 'world preview' and do content negotiation (e.g. HTTP 'Accept' header) to get the desired content-type of the world preview resource
> resolve world URI metadata via webfinger to something like
{ preview: 'https://world.xyz/0/preview' }
> Then use content-negotiation or mimetype when fetching that 'preview resource' to choose whether you prefer an equirectangular, video stream mimetype or something fallback like image/png

Nova's minimal set of metaverse URI metadata:
- A flat image or equirectangular image is needed for the world 
    - VR Chat uses flat 
    - NEOs uses equirectangular 
        - Wherever the portal goes out, you'd want to capture a screenshot of the World, to help bridge the transfer. 
- Pretty printed platform name, world name, and if applicable world instance 

For coordinate based ones the only things that should be required are the name, the pretty printed name and location (like how in Webaverse you can go off and enter a webxr experience so if it knows the name of that experience it should put that pretty printed), a flat image, or equirectangular. 

evo:
> Let me see if I understand. A sample WebXR immersive web experience is like a house on a street, and every platform is like a different country where their addressing format system may vary and differ. We'd ideally have the 3D view like a Google Map of each "address" to see previews of those addresses (not portals for now) but many worlds will only be able to support a 2D photograph of that screenshot location.

Robert:
> Two questions about uris from native apps:
> 1. How would you resolve a WebFinger route from a uri like vrchat://launch?id=wrld_{UUID}
> 2. Should a download link for the application needed to access a given URL be required?
> 
> One question about privacy:
> Is it ok that all of this info would be public? Or would this require auth tokens like @codenamedmitri was talking about?

bengo:
> wrt auth, I'd expect that if I http fetch some world-resource URI, I may get a 401/403, but that 4xx response could include a response header indicating how to procure/prove authorization.

The conversation then switched to 360 image thumbnail details.

For more of that conversation start here: https://discord.com/channels/770382203782692945/835221348443095070/849701093125914665
