Schema Relationships

Understanding the architecture and relationships between schemas, components, and data in META-AIML v2.0.1

Critical Understanding: Schema vs Data Relationships - Schemas define structure using $ref references, but actual data is inserted directly into entity instances. Components provide validation rules and type definitions, while real implementations contain the concrete values inline.

META-AIML v2.0.1 Schema Architecture

Hierarchical structure showing how schemas, components, and data interact

Schema Layer

Structure Definition

Base Schemas (6)

Foundation schemas for entity categories: organization, product_offering, service, creative_work, community, financial_product

Entity Schemas (31)

Specific business entity types inheriting from base schemas via allOf

Components (8)

Reusable validation rules and type definitions referenced via $ref

Modules (15)

Functional capability templates for auth, enhanced-auth, payments, location, etc.

Data Layer

Implementation

Instance Data

Concrete business information embedded directly in entity instances

Module Data

Functional capabilities like auth, payments, location with specific configurations

Capability Data

entityCapabilities and siteCapabilities with boolean features and action lists

schemas.meta-aiml.org Structure

Complete structure available to users on the schemas subdomain:

schemas.meta-aiml.org/
├── base/                           # 6 current base schemas
│   ├── organization.json           # Base for hotels, restaurants, clinics
│   ├── product_offering.json       # Base for marketplaces, ecommerce
│   ├── service.json                # Base for AI platforms, web apps
│   ├── creative_work.json          # Base for blogs, streaming platforms
│   ├── community.json              # Base for social networks, dating
│   └── financial_product.json      # Base for banking platforms
├── entity/                         # 31 current entity schemas
│   ├── restaurant.json             # References ../base/organization.json
│   ├── marketplace.json            # References ../base/product_offering.json
│   └── ... (29 more entities)
├── components/                     # 8 reusable components
│   ├── entity-capabilities-format.json    # v2.0.1 capabilities format
│   ├── site-capabilities-format.json      # v2.0.1 site features format
│   ├── multilingual-format.json           # i18n data format
│   └── ... (5 more components)
├── templates/                      # Template library
│   ├── module/                     # 15 functional modules
│   │   ├── auth.json              # Authentication module
│   │   ├── enhanced-auth.json     # Advanced authentication
│   │   ├── payments.json          # Payment processing
│   │   ├── location.json          # Geographic features
│   │   └── ... (11 more modules)
│   └── subcategory/               # Business subcategory templates
├── examples/                       # Complete implementation examples
├── sdk/                           # JavaScript parser & TypeScript definitions
├── v2.0.0/                        # Full v2.0.0 schema archive
│   ├── base/ components/ entity/ templates/ examples/
│   └── context/ (cultural, geographical, regulatory contexts)
├── v2.0.1/                        # Full v2.0.1 schema archive
│   └── base/ components/ entity/ templates/ examples/
├── context.jsonld                 # Current JSON-LD context
├── registry.json                  # Schema registry metadata
└── relationship-schema.json       # Schema relationship definitions

Total Count: 60 schemas available (31 entities + 6 base + 15 modules + 8 components) covering 95% of the internet's business models.

Key Relationship Principles

Schema Layer (schemas.meta-aiml.org)

• Uses $ref to define structure
• Provides validation rules via components
• Inherits via allOf from base schemas
• Contains no actual data values
• Available in current + versioned formats

Data Layer (Implementation)

• Contains concrete business values
• Embeds data inline (no $ref)
• Validates against schema definitions
• 15 modules provide functionality
• v2.0.1 adds capability mappings