Open Asset Standard Interchange Schema
Universal JSON Schema definitions for media asset management (MAM/DAM) operations.
OASIS provides platform-agnostic schema definitions for asset migration, metadata handling, and collection management across MAM/DAM systems. Think of it as an oasis in the desert of vendor lock-in—a universal interchange format that lets you migrate between CatDV, Dalet, EditShare, Iconik, and other media asset management platforms.
Used by the exodus migration tool.
See definitions/README.md for detailed documentation.
| Schema | Purpose |
|---|---|
asset.schema.json |
Individual asset structure with files and metadata |
asset_batch_import.schema.json |
Batch asset import format |
collection.schema.json |
Collection hierarchy structure |
collection_batch_import.schema.json |
Batch collection import format |
metadata_set.schema.json |
Metadata field definitions |
storage_location.schema.json |
Storage location references |
temporal_annotation.schema.json |
Time-based annotations for video/audio |
migration-report-output.schema.json |
Migration reporting format |
git submodule add https://github.com/NorthShoreAutomation/oasis.git schemascurl -L https://github.com/NorthShoreAutomation/oasis/archive/main.tar.gz | tar xz# Using jq to validate syntax
jq . definitions/asset.schema.json > /dev/null && echo "Valid JSON"We welcome contributions! Please:
- Fork this repository
- Create a feature branch (
git checkout -b feature/my-change) - Make your changes to schema files
- Validate JSON syntax:
jq . definitions/*.schema.json - Submit a pull request
- Follow JSON Schema Draft 7 specification
- Use descriptive field names and documentation
- Include examples in schema descriptions
- Maintain backward compatibility when possible
- Document breaking changes in PR description
- v1.0.0 (2026-01-24) - Initial release extracted from exodus repository
Apache 2.0
- Issues: GitHub Issues
- Main Project: exodus