BUILDING THE USER OWNED METAVERSE

The scope of the asset transfer working group ("ATWG" or the "Working Group") is to monitor, analyze, and assess the asset transfer environment surrounding Web 3.0 products, services and solutions; and develop and maintain asset transfer specifications.

Within the boundaries of its scope, the working group will:

• Specify requirements for (and possibly lead implementation of) infrastructure for transferring digital assets between virtual worlds;
• Specify metadata for describing assets;
• Develop general guidance, and suggested best practices, and certification programs;
• Engage in shared research and analysis; Remain appraised and provide periodic reports to the Board on developments in the relevant asset transfer environment;
• Produce supporting documentation.

‍

The scope of the Ecosystem Working Group ("EWG" or the "Working Group") is to establish, foster and maintain relationships and explore and develop avenues for cooperation with similar organizations, such as, in particular, without limitation:

• Metaverse Standards Forum
• Crypto Valley Association

Within the boundaries of its purpose, the Working Group shall:

• Reach out to organizations relevant to its purpose;
• Attend and participate in events organized by, in collaboration with or under the or patronage of such relevant organizations;
• Directly engage with such organizations and/or the key parties within; maintain a view and understanding of their initiatives and activities within the areas relevant to OMA3;
• Explore and develop avenues to cooperate with the relevant actors.

The scope of the Legal and Participant Safety Working Group ("LPSWG" or the "Working Group") is to monitor, analyze and assess the legal and regulatory environment surrounding Web 3.0 products, services and solutions, as well as to foster the formation of best practices in the relevant legal areas, in particular regarding:

• The protection and fair use of intellectual property in the area of Web 3.0; the implementation of and compliance with data protection laws with regard to blockchain solutions;
• Liability for the exercise of control over a Web 3.0 environment (or lack thereof);
• The design, implementation and enforcement of contractual terms and conditions within a Web 3.0 environment;
• General legal and regulatory developments relevant to the area of Web 3.0;
• The definition of best practices for platform operators with respect to vulnerable metaverse users, namely children;
• The development of best practices for moderating user generated content that may be graphic, illicit or incite violence, or to delimit areas as being non-moderated and warn users accordingly, while remaining mindful of preventing censorship wherever possible;
• The definition of demarcations, whereas information and content entered onto public blockchains is not the responsibility of platform operators.

Within the boundaries of its scope, the Working Group will:

• Develop general guidance, suggested best practices (but not individual legal advice), and standardized legal language;
• Remain appraised and provide periodic updates to the Board on developments in the relevant legal and regulatory environment;
• Engage in shared research and analysis;
• Produce supporting documentation;
• Explore and develop avenues to cooperate with the relevant actors.

The scope of the Portaling and Mapping Working Group (PMWG) is the development and maintenance of portaling and mapping specifications, and related deliverables, as assigned by the Board of Directors.

The PMWG activities are:

• Specify and develop solutions that allow the creation of two-way portals between each other's worlds to enable rapid travel of users and/or avatars between content-dense world experiences. Such solutions may include portaling animation;
• Specify and develop the spatial information highway, including two-way passing of spatial information, discovery/exploration/indexing of experiences and related solutions;
• Specify the construction of "embassies" of partner worlds in each other's experiences;
• Specify or recommend best practices for an API that could be tested on multiple virtual worlds.

‍