Comprehensive schemas, ontologies, and specifications powering unified metadata across the data ecosystem
OpenMetadata Standards is the official repository for comprehensive metadata schemas, ontologies, and specifications that power the OpenMetadata platform and ecosystem. It provides a unified, open-source framework for representing, validating, and exchanging metadata across the entire data landscape.
Built with open standards and designed for interoperability, OpenMetadata Standards enables organizations to:
- 📊 Unify metadata across databases, data warehouses, data lakes, ML models, dashboards, and APIs
- 🔍 Discover and catalog data assets with rich, structured metadata
- 🎯 Govern data with policies, classifications, and glossaries
- 🔗 Track lineage from source to consumption across multi-platform data pipelines
- ✅ Ensure quality with comprehensive data validation and profiling schemas
- 🌐 Build knowledge graphs using RDF/OWL ontologies and semantic web standards
- 🔄 Integrate seamlessly with existing tools through JSON Schema, OpenAPI, and JSON-LD
|
700+ comprehensive schemas covering:
|
Semantic standards for linked data:
|
|
Comprehensive guides including:
|
Resources for developers:
|
Comprehensive metadata models for all data assets:
| Databases | Tables, Columns, Schemas, Views, Stored Procedures, Queries |
| Storage | Containers, Directories, Files, Spreadsheets, Worksheets |
| Pipelines | Data Pipelines, Tasks, Workflow Definitions, Scheduling |
| Messaging | Topics, Message Schemas, Partitions, Consumer Groups |
| Dashboards | Dashboards, Charts, Data Models, Reports |
| ML Models | Models, Features, Hyperparameters, Metrics, Experiments |
| APIs | Collections, Endpoints, Request/Response Schemas, Authentication |
| Search | Search Indexes, Fields, Mappings |
Enterprise-grade governance schemas:
- 📖 Glossaries - Business terminology with hierarchies and relationships
- 🏷️ Classifications & Tags - Automated and manual classification systems
- 📋 Policies - Access control, data policies, and compliance rules
- 📏 Metrics - Business metrics and KPI definitions
- 📝 Data Contracts - Schema contracts and SLAs
Comprehensive quality and monitoring:
- 🧪 Test Definitions - 50+ built-in test types (schema, freshness, completeness, etc.)
- 📊 Test Suites - Organized test collections with execution history
⚠️ Incidents - Issue tracking and resolution workflows- 📈 Data Profiling - Statistical profiles and distribution analysis
- 🔔 Alerts - Configurable alerting and notification rules
End-to-end data lineage tracking:
- Column-level lineage with transformation logic
- Cross-platform lineage across databases, pipelines, and dashboards
- Manual lineage editing and augmentation
- Impact analysis for upstream and downstream dependencies
- Provenance tracking using W3C PROV-O standard
People and organizational metadata:
- Users & Teams - Hierarchical team structures
- Roles & Policies - Fine-grained access control
- Personas - User personas for targeted experiences
- Domains - Business domain organization
- Ownership - Asset ownership and stewardship
84+ connector schemas for data sources:
- Databases: PostgreSQL, MySQL, Oracle, SQL Server, Snowflake, BigQuery, Redshift, etc.
- Warehouses: Databricks, Synapse, Teradata, Vertica, etc.
- Lakes: S3, GCS, Azure Data Lake, HDFS, etc.
- Messaging: Kafka, Pulsar, RabbitMQ, Kinesis, etc.
- Dashboards: Tableau, PowerBI, Looker, Superset, Metabase, etc.
- Pipelines: Airflow, dbt, Dagster, Fivetran, etc.
- ML Platforms: MLflow, SageMaker, Kubeflow, etc.
|
Build comprehensive, searchable data catalogs with rich metadata, automated discovery, and collaborative documentation. |
Implement enterprise governance with automated classification, policy enforcement, and compliance tracking. |
Enable self-service data discovery with semantic search, recommendations, and popularity metrics. |
|
Define, monitor, and enforce data quality rules with automated testing and incident management. |
Track complete data lineage from source to consumption with column-level granularity and impact analysis. |
Build semantic knowledge graphs using RDF, OWL, and SPARQL for advanced analytics and AI applications. |
|
Standardize metadata exchange across tools and platforms using open standards (JSON Schema, OpenAPI, RDF). |
Ensure regulatory compliance (GDPR, CCPA, HIPAA) with metadata-driven policies and audit trails. |
Manage ML model metadata including features, experiments, versioning, and deployment tracking. |
Visit openmetadatastandards.org for comprehensive documentation, including:
- Introduction & Core Concepts
- Quick Start Guide
- Complete Schema Reference
- RDF & Ontologies
- Real-World Examples
# Clone the repository
git clone https://github.com/open-metadata/OpenMetadataStandards.git
cd OpenMetadataStandards
# Install Python dependencies
pip install -r requirements.txt
# Serve documentation locally at http://localhost:8000
mkdocs servePython Example:
import json
import jsonschema
# Load the table schema
with open('schemas/entity/data/table.json') as f:
table_schema = json.load(f)
# Load your table metadata
with open('my_table_metadata.json') as f:
table_data = json.load(f)
# Validate
try:
jsonschema.validate(instance=table_data, schema=table_schema)
print("✓ Valid metadata!")
except jsonschema.ValidationError as e:
print(f"✗ Validation error: {e.message}")JavaScript/TypeScript Example:
const Ajv = require('ajv');
const fs = require('fs');
const ajv = new Ajv();
// Load schema and data
const schema = JSON.parse(fs.readFileSync('schemas/entity/data/table.json'));
const data = JSON.parse(fs.readFileSync('my_table_metadata.json'));
// Validate
const validate = ajv.compile(schema);
const valid = validate(data);
if (valid) {
console.log('✓ Valid metadata!');
} else {
console.log('✗ Validation errors:', validate.errors);
}OpenMetadata Standards power the OpenMetadata platform:
# Try OpenMetadata with Docker
docker run -d -p 8585:8585 \
--name openmetadata \
openmetadata/server:latestVisit docs.open-metadata.org for full installation guide.
OpenMetadataStandards/
├── 📁 schemas/ # 700+ JSON Schema files
│ ├── entity/
│ │ ├── data/ # Data entities (tables, topics, etc.)
│ │ ├── services/ # Service configurations
│ │ ├── governance/ # Governance entities (glossaries, policies)
│ │ ├── teams/ # Teams and users
│ │ └── ...
│ ├── type/ # Type system definitions
│ ├── api/ # API specifications
│ ├── events/ # Event schemas
│ └── configuration/ # Configuration schemas
│
├── 📁 rdf/ # RDF/OWL Ontologies
│ ├── ontology/ # OpenMetadata OWL ontology
│ ├── shapes/ # SHACL validation shapes
│ └── contexts/ # JSON-LD contexts
│
├── 📁 docs/ # Documentation source (MkDocs)
│ ├── getting-started/ # Tutorials and guides
│ ├── data-assets/ # Entity documentation
│ ├── governance/ # Governance docs
│ ├── examples/ # Usage examples
│ └── reference/ # API reference
│
└── 📁 examples/ # Example metadata files
├── basic/ # Simple examples
├── advanced/ # Complex scenarios
└── integration/ # Integration patterns
OpenMetadata Standards is built on industry-standard specifications:
 JSON Schema Draft 07 & 2020-12 |
RDF/OWL W3C RDF 1.1 & OWL 2 |
SHACL W3C Validation |
 JSON-LD Linked Data |
Additional Standards:
- OpenAPI 3.0 - API specifications
- PROV-O - W3C Provenance Ontology for lineage
- SKOS - Simple Knowledge Organization System
- DCAT - Data Catalog Vocabulary
|
Connect with the community, ask questions, and share ideas. |
Comprehensive documentation with guides, examples, and API reference. |
Found a bug or have a feature request? Let us know! |
We welcome contributions from the community! Here's how you can help:
- ⭐ Star this repository to show your support
- 🐛 Report bugs and suggest features via GitHub Issues
- 📝 Improve documentation by submitting pull requests
- 💡 Share use cases and examples in our community
- 🗣️ Spread the word about OpenMetadata Standards
- Slack: slack.open-metadata.org - Active community chat
- GitHub Discussions: Discussions - Q&A and announcements
- GitHub Issues: Issues - Bug reports and feature requests
- Twitter: @open_metadata - News and updates
- LinkedIn: OpenMetadata - Professional network
This documentation is automatically deployed to GitHub Pages with every commit to the main branch.
- Live Documentation: openmetadatastandards.org
- Deployment Workflow:
.github/workflows/deploy-docs.yml - Validation Workflow:
.github/workflows/docs-validation.yml - Deployment Guide: DEPLOYMENT.md
- Setup Checklist: SETUP_CHECKLIST.md
The documentation is accessible via multiple domains:
- Primary: openmetadatastandards.org
- Alternate: openmetadatastandards.com (redirects to .org)
- Alternate: openmetadatastandard.com (redirects to .org)
We love contributions! Whether you're fixing bugs, adding new schemas, improving documentation, or sharing examples, your help is appreciated.
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Make your changes in the appropriate directory:
- Schemas:
schemas/ - Documentation:
docs/ - Examples:
examples/ - RDF/Ontologies:
rdf/
- Schemas:
- Test your changes locally:
# Serve documentation locally mkdocs serve # Validate documentation (checks for broken links, 404s, build warnings) ./scripts/check-docs.sh
- Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
Please read our Code of Conduct before contributing.
- 700+ JSON Schemas covering all major metadata entities
- 200+ API Operations fully documented
- 100+ Entity Types with comprehensive properties
- 50+ Test Definitions for data quality
- 84+ Service Connectors schemas
- Full RDF/OWL Ontology with SHACL validation
OpenMetadata Standards is licensed under the Apache License, Version 2.0.
Copyright 2021-2025 OpenMetadata
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
See LICENSE for the full license text.
OpenMetadata Standards is built with love by the OpenMetadata Community and powered by:
 MkDocs |
 Material for MkDocs |
JSON Schema |
W3C RDF/OWL |
 GitHub Pages |
Special thanks to all our contributors and the organizations using OpenMetadata Standards in production.
|
The unified metadata platform powered by these standards. |
Complete documentation for the OpenMetadata platform. |
![@github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=64&v=4){kind=small}
![@github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=64&v=4){kind=small}