Validate Open Data Products standards instantly. Paste YAML or JSON below.
ODPS 4.1ODPS 4.0ODPC 1.0ODPG 1.0ODPV 1.0
Your Document
Validation Results
Paste an ODPS-family document on the left to see validation results here.
Supported standards
The validator auto-detects the document kind (ODPS, ODPC, ODPG, or ODPV) and reads the rootversion field to select the matching bundled JSON Schema. Unknown versions fall back to the latest schema for that standard with a warning.
| Standard | Versions | Detect by | Status |
|---|---|---|---|
| ODPS | 4.1, 4.0 | product root object | 4.1 latest |
| ODPC | 1.0 | kind: Catalog | Latest |
| ODPG | 1.0 | kind: Graph | Latest |
| ODPV | 1.0.0 | id: ODPV | Latest |
Frequently asked questions
What is the Open Data Products standards family?
It is a set of Linux Foundation open specifications for data products: ODPS defines a single data product, ODPC organizes catalogs and portfolios, ODPG connects value relationships as graphs, and ODPV provides shared vocabulary. Together they support discovery, governance, and AI-ready metadata.
What ODPS versions does this validator support?
ODPS 4.1 (latest production) and 4.0. Older ODPS versions (3.x, 2.x) are not supported. The validator reads the root version field and selects the matching schema automatically.
How does the validator know which standard to use?
ODPC documents have kind: Catalog, ODPG has kind: Graph, ODPV has id: ODPV, and ODPS documents have a product root object. If the kind cannot be detected, validation cannot proceed.
Can I use JSON instead of YAML?
Yes. Both formats are supported equally. The validator auto-detects JSON or YAML from the pasted content.
Is my document sent to a server?
No. All validation runs entirely in your browser. Official JSON Schemas are bundled with the page. Your document never leaves your machine.
What is the difference between version and productVersion?
version identifies the specification version your file follows (e.g. 4.1 for ODPS). productVersion is the data product's own semver in product.details, tracking changes to the product metadata over time.
How is ODPS different from ODCS?
ODPS describes a data product as a business asset (metadata, SLA, quality, pricing, strategy). ODCS (Open Data Contract Standard) formalizes the agreement between data producers and consumers (schema, quality rules, team, IAM). ODPS can reference ODCS contracts via the contract object.
Where can I learn more?
Official documentation: https://opendataproducts.org/. ODPS 4.1 spec: https://opendataproducts.org/v4.1/. Examples: https://github.com/Open-Data-Product-Initiative/odps-examples.