Specification

Schemas

Nested specification entry for IOTA-1 public message, registry, validation, and package schemas.

  • Record JAI-SPEC-18147
  • Path /es-us/specification/schemas/
  • Use Canonical public record

Document status

Public standards page Published on JustAnIota.com as part of the current public standards record
Code
JAI-SPEC-18147
Surface
Specification
Access
Public and linkable

How to use this page

Use this page as part of the current Specification public record, then follow its linked standards pages for the next step.

Proof path

Validator-backed proof path

Keep the public reading order tied to one evidence trail: profile, schema, example, validator result, and release record.

  1. 1Pick a message profile.Start with a published UAI-1 profile and the record family that matches the exchange you need to prove.
  2. 2Compare it with schemas and examples.Resolve the schema, registry entry, and one fixture before writing or mapping your candidate packet.
  3. 3Run validator evidence.Validate keyed, minified-keyed, or keyless JSON against the current public UAI-1 records.
  4. 4Attach the result to implementation or handoff records.Carry the exported result into implementation notes, changelog entries, or Project Handoff evidence.

Plain English

Schemas define the public record shapes before compact payloads travel.

Technical summary

IOTA-1 schema files cover public message envelopes, registry records, validation results, converter results, and package manifests.

Deep spec

Schema validation is necessary but not sufficient: registry evidence, examples, canonicalization, and safety notes still define usable meaning.

Schema families

  • Public message envelope.
  • Public seed registry record.
  • Validation result.
  • Converter result.
  • Public projection package manifest.