Integration Profiles Overview

Purpose of Integration Profiles

Integration profiles provide standardized metadata schemas for specific asset types and use cases. Each profile defines:

• Required properties
• Optional properties
• Validation rules
• Implementation patterns

Profiles ensure consistent metadata across platforms while addressing domain-specific requirements.

Available Profiles

MVMD includes the following integration profiles:

Profile	Purpose	Status
Attachable	Items that can be attached to avatars (wearables, equipment)	Proposed
Avatar	Virtual character metadata	Proposed
Basic	Core metadata for all assets	Proposed
Composable 3D NFT	Composable NFT metadata	Proposed
Digital Twin	Physical-digital representation	Proposed
Equipable	Equipment system metadata	Proposed
Future Profiles	Planned developments	In planning
Identity	Identity information	Proposed
Interactable	Interactive object metadata	Proposed
Royalty	Revenue and rights metadata	Proposed
Scene	Virtual environment metadata	Proposed
Vehicle	Vehicle asset metadata	Proposed
Wearable	Wearable item metadata	Proposed

Profile Structure

Each integration profile follows a consistent structure:

1. Purpose and Use Cases: Description and intended applications
2. Profile Overview: General description of what the profile covers
3. Required Properties: Essential metadata properties
4. Optional Properties: Additional metadata enhancements
5. Standards Integration: How the profile works with technical standards
6. Examples: Basic, standard, and complete examples showing usage
7. Validation: How to validate against profile requirements
8. Implementation Considerations: Best practices and tips
9. Common Issues: Troubleshooting guidance
10. Related Profiles: Links to related profiles

Schema Validation

Each profile has a corresponding JSON Schema validation file that can be used to validate your metadata:

• Schema Validation Documentation
• Available Schema Files

Implementation Approach

When implementing integration profiles:

1. Start with the Basic Profile
2. Add domain-specific profiles as needed
3. Validate against profile schema files
4. Focus on required properties first
5. Add optional properties based on your specific needs

Use Case-Based Selection

Select profiles based on your specific use cases:

• Avatar Customization: Avatar + Attachable
• Virtual Stores: Basic + Attachable + Royalty
• Interactive Environments: Scene + Interactable
• Virtual Items with Utility: Attachable + Interactable
• Digital Ownership: Basic + Composable 3D NFT

Cross-References to Implementation Guides

For practical implementation guidance, see these related resources:

• Cross-Platform Assets Implementation
• Interactive Assets Implementation
• Discovery Optimization

Next Steps

• Review the Basic Profile for fundamental implementation
• Identify the profiles most relevant to your assets
• Implement the minimum required properties
• Extend with optional properties as needed
• Validate your implementation using the Schema Validation Tools

Related Standards

Profiles integrate with these technical standards:

• Schema.org: Core vocabulary for all profiles
• glTF: 3D model format for visual assets
• USD: Universal Scene Description for complex assets
• OpenXR: XR-specific implementation patterns
• C2PA: Authentication and verification

Contributing

The MVMD community welcomes contributions to existing profiles and proposals for new profiles:

1. Fork our GitHub repository
2. Create a new branch for your profile changes
3. Follow the standard profile structure
4. Include examples and validation rules
5. Submit a pull request

Related Resources

• Types of Assets: Core asset classifications
• Namespaces: Standard-specific metadata properties
• Implementation Best Practices: General metadata guidance
• Profile Specifications (JSON Schema)
• Schema Validation Documentation
• Available Schema Files

Related Namespaces

• Schema.org: Core vocabulary for integration profiles
• 3D Standards: Implementation patterns for 3D assets
• Geospatial Standards: Location data patterns
• Trust & Provenance: Authentication and verification
• OpenXR Standards: XR-specific implementation patterns