P65 — AIEP — Schema Extension Framework for Web Artefacts
Publication Date: 2026-02-26 Status: Open Source Prior Art Disclosure Licence: Apache License 2.0 Author/Organisation: Phatfella Ltd Schema: AIEP_OS_SPEC_TEMPLATE v1.0.1 — https://aiep.dev/schemas/aiep-os-spec-template/v1.0.1
Field of the Invention
[0001] The disclosure relates to schema governance for machine-ingestible web artefacts.
[0002] More particularly, the disclosure concerns a schema extension framework defining rules for creating, versioning, and deprecating domain-specific schema extensions for AIEP web artefacts, enabling third parties to publish new machine mirror schemas without modifying core protocol definitions.
Framework Context
[0003] This invention operates within an Architected Instruction and Evidence Protocol (AIEP) environment as defined in United Kingdom patent application number GB2519711.2, filed 20 November 2025, the entire contents of which are incorporated herein by reference.
[0004] The present invention extends deterministic canonicalisation, governance, and execution integrity mechanisms defined in the AIEP environment while remaining independently implementable as described herein.
Background
[0005] The AIEP web layer defines a core machine mirror page envelope (P60) with a base schema. Different publishing domains — commerce, healthcare, legal, scientific — require domain-specific structured data fields beyond the base envelope.
[0006] Without a governed extension framework, third-party schema additions are uncoordinated, produce naming collisions, lack backward compatibility declarations, and cannot be deterministically versioned or deprecated.
[0007] Existing schema extension mechanisms do not provide:
(a) namespaced schema identifiers preventing collision; (b) semantic versioning with defined compatibility guarantees; (c) mandatory backward compatibility declarations; or (d) structured deprecation metadata enabling agents to handle obsolete schemas deterministically.
Summary of the Disclosure
[0011] A schema extension framework is disclosed defining rules for creating new web-domain schemas extending the AIEP base envelope.
[0012] All extension schema identifiers must be namespaced using reverse-domain notation, producing identifiers of the form aiep.{domain}.{type}.v{N} — for example aiep.commerce.product.v1.
[0013] Schema versions follow semantic versioning: MAJOR version increments indicate breaking changes; MINOR version increments indicate backward-compatible additions; PATCH version increments indicate backward-compatible corrections.
[0014] Each published schema version must include a backward compatibility declaration stating the minimum schema version with which it is compatible.
[0015] Deprecated schemas must include structured deprecation metadata comprising:
{
"deprecated": true,
"deprecated_at": "ISO8601",
"replacement_schema": "aiep.{domain}.{type}.v{N+1}"
}
[0016] A SchemaExtensionHash is computed as:
SchemaExtensionHash = H(CanonicalSchemaDefinition || schema_id || schema_version)
[0017] Agents encountering a deprecated schema must treat it as non-admissible unless the agent declares explicit support for deprecated schema processing, in which case the deprecation must be recorded in the processing trace.
[0018] The technical effect is governed, deterministic extensibility of the AIEP web layer enabling domain-specific schema evolution without breaking core protocol invariants or producing naming collisions.
Brief Description of the Drawings
[0019] Figure 1 illustrates the namespaced schema identifier structure and examples.
[0020] Figure 2 illustrates the semantic versioning rules and compatibility declarations.
[0021] Figure 3 illustrates the deprecation metadata structure and agent handling.
[0022] Figure 4 illustrates the SchemaExtensionHash computation and registry entry structure.
ASCII Drawings
Figure 1 — Namespaced Schema Identifier Structure
Pattern: aiep.{domain}.{type}.v{N}
Examples:
+----------------------------------+
| aiep.commerce.product.v1 |
| aiep.healthcare.record.v2 |
| aiep.legal.contract.v1 |
| aiep.science.dataset.v3 |
+----------------------------------+
Reverse-domain prefix prevents collision.
Domain and type segments are lowercase.
Version suffix is integer, starting at 1.
Figure 2 — Semantic Versioning and Compatibility
MAJOR.MINOR.PATCH
MAJOR increment: breaking change
- Agents must not assume backward compat.
MINOR increment: backward-compatible addition
- Agents processing v1.0.0 can process v1.1.0
PATCH increment: backward-compatible correction
- No field changes
Backward compatibility declaration required:
{
"min_compatible_version": "1.0.0"
}
Figure 3 — Deprecation Metadata and Agent Handling
Deprecated Schema Entry:
+------------------------------------------+
| { |
| "deprecated": true, |
| "deprecated_at": "ISO8601", |
| "replacement_schema": |
| "aiep.{domain}.{type}.v{N+1}" |
| } |
+------------------------------------------+
Agent behaviour:
+------------------+ +------------------+
| Deprecated schema| | Agent supports |
| encountered | | deprecated |
| | Yes | processing? |
+--------+---------+ -----> +--------+---------+
| |
No Record in trace
| Process with flag
v
NON-ADMISSIBLE
Fail-closed
Figure 4 — SchemaExtensionHash and Registry Entry
CanonicalSchemaDefinition ----+
schema_id ----+--> H(CanonicalSchema ||
schema_version ----+ schema_id ||
schema_version)
|
v
+------------------------------------+
| Schema Registry Entry |
|------------------------------------|
| schema_id |
| schema_version |
| SchemaExtensionHash |
| backward_compat_declaration |
| deprecated (if applicable) |
+------------------------------------+
Detailed Description
1. Namespaced Schema Identifiers
[0023] All extension schema identifiers must use reverse-domain namespacing of the form aiep.{domain}.{type}.v{N}. The namespace prevents collision between independently developed domain schemas.
2. Semantic Versioning
[0024] Schema versions follow semantic versioning. MAJOR increments indicate breaking changes incompatible with prior versions. MINOR increments indicate backward-compatible additions. PATCH increments indicate backward-compatible corrections.
[0025] Each schema version must declare min_compatible_version identifying the earliest schema version with which it is compatible.
3. Deprecation Metadata
[0026] Deprecated schemas must include structured deprecation metadata comprising deprecated: true, deprecated_at ISO 8601 timestamp, and replacement_schema identifier.
[0027] Agents encountering deprecated schemas must treat them as non-admissible unless explicit deprecated processing support is declared, in which case deprecation is recorded in the processing trace.
4. SchemaExtensionHash
[0028] A SchemaExtensionHash is computed as H(CanonicalSchemaDefinition || schema_id || schema_version) and recorded in the schema registry entry.
Claims
-
A schema extension framework for AIEP web artefacts comprising: (a) namespaced schema identifiers of the form
aiep.{domain}.{type}.v{N}preventing naming collision; (b) semantic versioning with MAJOR, MINOR, and PATCH increments carrying defined compatibility guarantees; (c) mandatory backward compatibility declarations specifying minimum compatible schema version; (d) structured deprecation metadata comprising deprecated flag, deprecated_at timestamp, and replacement_schema identifier; and (e) a SchemaExtensionHash computed as H(CanonicalSchemaDefinition || schema_id || schema_version) recorded in the schema registry. -
The framework of claim 1 wherein agents encountering deprecated schemas treat them as non-admissible unless explicit deprecated processing support is declared and recorded in the processing trace.
-
A computing system implementing schema governance conforming to the framework of any of claims 1 to 2.
-
A non-transitory computer-readable medium storing instructions which, when executed, implement schema governance conforming to the framework of any of claims 1 to 2.
Licence
Any person is granted a perpetual, irrevocable, worldwide, royalty-free licence to make, use, implement, modify, or distribute any system or method described in this disclosure for any purpose, without restriction, under the Apache License 2.0.
A copy of the Apache License 2.0 is available at https://www.apache.org/licenses/LICENSE-2.0
Abstract
A schema extension framework is disclosed for AIEP web artefacts enabling governed domain-specific schema creation without modifying core protocol definitions. Extension schema identifiers use reverse-domain namespacing of the form aiep.{domain}.{type}.v{N}. Versions follow semantic versioning with defined compatibility guarantees. Each version includes a backward compatibility declaration. Deprecated schemas carry structured deprecation metadata including replacement schema identifier. Agents encountering deprecated schemas without declared support must treat them as non-admissible. A SchemaExtensionHash is computed as H(CanonicalSchemaDefinition || schema_id || schema_version) and recorded in the schema registry.