Skip to main content

Validator

At present, the primary tool for validating MVMD metadata is the Schema.org Validator (https://validator.schema.org/). This guide explains how to use the validator effectively with MVMD metadata.

Note: In the future, MVMD will provide dedicated validation tools that handle namespaced properties, file attachments, and cross-references between files. This guide will be updated when those tools become available.

Using the Schema.org Validator​

Step 1: Prepare Your Metadata​

Before validation, ensure your metadata:

  • Has a properly defined @context
  • Uses valid Schema.org types
  • Includes all required properties
  • Uses proper JSON-LD formatting

Example of properly formatted metadata:

{
  "@context": {
    "@vocab": "https://schema.org/",
    "gltf": "https://www.khronos.org/gltf/"
  },
  "@type": "ImageObject",
  "name": "Asset Preview",
  "description": "Preview image of 3D asset",
  "contentUrl": "https://example.com/preview.jpg",
  "encodingFormat": "image/jpeg"
}

Step 2: Visit the Validator​

  1. Go to https://validator.schema.org/
  2. Choose the "Validate" tab
  3. Select JSON-LD as the format

Step 3: Validate Your Metadata​

  1. Paste your metadata into the validator
  2. Click "Validate"
  3. Review the results
  4. Address any validation errors

Common Validation Issues​

1. Missing Required Properties​

Error:

{
  "@context": "https://schema.org/",
  "@type": "ImageObject"
}

Fix:

{
  "@context": "https://schema.org/",
  "@type": "ImageObject",
  "name": "Asset Name",
  "contentUrl": "https://example.com/image.jpg"
}

2. Invalid Type Values​

Error:

{
  "@context": "https://schema.org/",
  "@type": "3DAsset",
  "name": "Example Asset"
}

Fix:

{
  "@context": "https://schema.org/",
  "@type": "3DModel",
  "name": "Example Asset"
}

3. Incorrect Property Types​

Error:

{
  "@context": "https://schema.org/",
  "@type": "ImageObject",
  "name": "Asset Name",
  "contentUrl": 12345
}

Fix:

{
  "@context": "https://schema.org/",
  "@type": "ImageObject",
  "name": "Asset Name",
  "contentUrl": "https://example.com/image.jpg"
}

Handling Namespaced Properties​

The Schema.org validator will ignore properties from other namespaces. For example:

{
  "@context": {
    "@vocab": "https://schema.org/",
    "gltf": "https://www.khronos.org/gltf/"
  },
  "@type": "3DModel",
  "name": "Example Model",
  "gltf:asset": {
    "version": "2.0"
  }
}

The gltf:asset property will be ignored during validation. This is expected behavior until MVMD's dedicated validation tools are available.

Best Practices​

  1. Validate Core Properties First

    • Start with basic Schema.org properties
    • Ensure all required fields are present
    • Use correct property types
    • Fix any validation errors

  2. Document Namespaced Properties

    • Keep track of non-Schema.org properties
    • Document their requirements
    • Plan for future validation
    • Follow standard specifications

  3. Regular Validation

    • Validate during development
    • Check after updates
    • Monitor for changes
    • Keep documentation current

Future MVMD Validation​

The upcoming MVMD validation tools will provide:

  1. Complete Validation

    • Schema.org compliance
    • Namespace validation
    • File attachment verification
    • Cross-reference checking

  2. Extended Features

    • Profile-specific validation
    • Custom rule sets
    • Batch validation
    • Automated testing

  3. Integration Support

    • API access
    • CI/CD integration
    • Development tools
    • Validation reports

Next Steps​

  1. Review Metadata Fundamentals
  2. Check Best Practices
  3. Explore Profile Requirements