Source of truth for implementation is the canonical schema host:
https://schemas.meta-aiml.org/v3.0.0/. If any page text conflicts with canonical schema files, follow canonical files. Documentation home.Schema Relationships
META-AIML v3.0.0
Relationship model in v3: ontology + archetype + components + entity contract + filled instance.
Use canonical schema URLs from
https://schemas.meta-aiml.org/ as source of truth. Legacy v2 base-oriented chains are not canonical in v3.Canonical Topology
Published structure and versioning model.
Version root:
https://schemas.meta-aiml.org/v3.0.0/
Contract families:
- /ontology/
- /archetypes/
- /components/
- /entity/
- /examples/
- /sdk/
Latest alias:
https://schemas.meta-aiml.org/Composition Pattern
Entity contract composition with absolute canonical refs.
{
"$id": "https://schemas.meta-aiml.org/v3.0.0/entity/marketplace.json",
"allOf": [
{ "$ref": "https://schemas.meta-aiml.org/v3.0.0/ontology/digital_entity.json" },
{ "$ref": "https://schemas.meta-aiml.org/v3.0.0/archetypes/mediated_exchange.json" }
],
"properties": {
"capabilities": {
"properties": {
"commerce": {
"$ref": "https://schemas.meta-aiml.org/v3.0.0/components/capability_groups.json#/$defs/CommerceCapabilities"
}
}
}
}
}Contract vs Instance
Different responsibilities, linked by validation.
Contract file:
- defines allowed structure and constraints
- canonical URL: /v3.0.0/entity/<entity>.json
Example instance file:
- contains concrete business values
- canonical URL: /v3.0.0/examples/<entity>_example_schema_v3.json
Rule:
- instances must satisfy contract constraints
- schema-only constructs stay in contractsValidation Sequence
1. Select contract at https://schemas.meta-aiml.org/v3.0.0/entity/<entity>.json.
2. Fill instance based on https://schemas.meta-aiml.org/v3.0.0/examples/<entity>_example_schema_v3.json.
3. Validate in /playground or by SDK from https://schemas.meta-aiml.org/v3.0.0/sdk/.
4. Publish JSON-LD instance in website head and keep source links for dynamic data.