◈︎

Current Version

  • v0.5.6: Technical Review, published 2026-06-08

Key changes:

  • Extension Registry (§17.5) and licensed vendor registration (§6.1)
  • Extension size limit 4KB (§6.3)
  • AI declaration extension with Article 50 fields (§11.1)
  • HTML JSON-LD example (§11.2)
  • C2PA integration direction clarified (§7.1)
  • JSON Schema typed extensions and “0.5.6” added to version enum (Appendix A)
  • Registry governance consolidated (§17.4)
  • public_key moved to extension field (§11.3)
  • manifest_signature covers core + extensions (§5.8)
  • Multi-hash support (§5.5)
  • .NET zero-dependency C# implementation
  • Test vectors TV-01 through TV-25

Planned: v0.6

Feature additions:

  • DID-based creator_id mode: decentralized identifier alternative to UUID and Ed25519 fingerprint
  • UUID v8 support: for asset_id and creator_id
  • rights field: structured rights and permissions for AI usage declarations, robots.txt/llms.txt-style signals
  • Reference anchor service: AIOSchema-hosted RFC 3161 and OTS anchor service for easy integration
  • anchor_reference array support: multiple anchor references per manifest

Planned: v1.0

Stability milestone:

  • All Core Block fields architecturally frozen (frozen as of March 2026, per §4 design principles)
  • Full backward compatibility guarantee
  • Formal governance charter published
  • Foundation operational

Regulatory Timeline

August 2, 2026: Compliance deadline for:

  • EU AI Act Article 50: AI-generated content labeling and transparency
  • California SB 942: AI-generated content disclosure requirements

AIOSchema is designed to provide a compliant provenance layer ahead of this deadline. The standard is available today for early adoption and integration testing.

Principles

This roadmap describes direction, not commitments. The KISS principle governs all additions: every feature added to the standard must justify its complexity cost. Minimalism is mathematically necessary: any addition adds dependency, any dependency adds attack surface.