The Metaverse Standards Forum Use Case Repository

In order to assist standards development organizations (SDOs) in their mission to create interoperability for an open Metaverse, the Metaverse Standards Forum has formed a Use Case Taskforce. This task force will focus on the creation of use cases and requirements for Metaverse topics that require attention and reflection.

Presented below is the current collection of Use Cases, organized by Working Group.

Please direct any questions to the #use-cases channel on our Discord server, or email the Use Cases Task Force directly.

Addition information regarding the Use Case Task Force’s objectives, methodology, and use case requirements is listed below.

Use Cases

3D Web Interoperability

• 3D Web Field Trips for Remote Learning
• Consistency of Experience
• Metaverse Bookmarks
• Portable Personal Content

Digital Asset Management

• Interoperability
  • Metaverse Universal Manifest
• NFT Royalties
  • NFT Metadata – Avatar Use Case
  • NFT Metadata – General Use Case
  • NFT Wearables
  • NFT Wrapping
  • NFT Swapping
  • NFT Renting
  • Internal Wallet Transfer
  • Fractionalized NFTs
  • Loyalty Catalog
  • Low Frequency Trading
  • Loans
  • High Frequency Trading
• Reputation in the Metaverse
  • ID Verification for Creators
  • Shared KYC AML Verification
  • Licensing of Reputation Data for LLMs
  • User Agreement Compliance
  • Cybersecurity Reputation Data Storage
  • Unified Reputation Management
  • Humanity Attestation
  • Avatar Ownership Change
  • Decentralized Credit Scores

Industrial Metaverse Use Case

• Remote Assistance for Autonomous Robots
• Power Transformers and Reactors – Quality Testing, Training, and Preventive Maintenance
• Medical Device Assembly Technician Training

End-user Troubleshooting

• Carousel Social Dancing across the Metaverse

What is the Use Case Task Force

1.   Background

• The Use Case Taskforce of MSF’s Standards Register work group was established in 2024 to enable the Pre-standardization Objective 3 of MSF’s mission, which focuses on the creation of broad consensus on use cases and requirements.
• The Use Case Taskforce also works to support the overall objective of MSF, which is to assist standards organizations in their mission to create interoperability for an open metaverse.

2.   Objectives

To create broad consensus on use cases and requirements, the Use Case Taskforce oversees the execution of the following objectives:

• Engagement of work group (WG) members to collectively ideate around metaverse topics (relevant to WG mandate and charter) that require attention and reflection.
• Sourcing of applicable industry standards, reports, and benchmarks to support the development of the identified metaverse topics.
• Shortlisting of use cases for further discussion and buy-in amongst WG members.
• Assignment of roles/champions to develop Use Case(s).

3.   Methodology

The Use Case development methodology at the MSF comprises four key steps to convert ideas into conceptualized requirements:

• Brainstorm using tried and tested tools to depict the initial Use Case(s) narrative.
• Assess WG capacity and ability to develop the shortlisted Use Case(s).
• Document Use Case(s) in the respective template to conceptualize requirement.
• Report Use Case(s) for internal review, following MSF’s Use Case submission protocols.

4.   Requirements

Our purpose at the MSF is to delineate use case requirements in a business-friendly and balanced manner, avoiding detailed specifications. It is in our best interest to provide base-level requirements to support concerned parties, including SDOs, to undertake detailed reviews and perform necessary uplifts and enhancements to transform those Use Cases into standards and detailed specifications for adoption by the industry.

In addition, our Use Case requirements documentation acknowledges the need for the following conditions to be met:

• Accuracy, clarity, and detailed understanding of what requires standardization across various domains.
• Positioning of Use Cases to act as conversation starters with concerned parties, including SDOs, while acknowledging the need for continuous improvement.
• Adoption of a Use Case template with a consistent and uniform set of fields to help capture necessary details and allow for easier comparison amongst use cases.
• Adequate articulation of challenges, benefits, and opportunities to guide SDOs’ and concerned parties’ efforts on the most impactful areas for further development.