EXPERIMENTAL SPECIFICATION / 0.1
A shared language for an adaptive web.
AIML (Adaptive Information Markup Language, working name) is a data-only JSON representation of publisher content and declared capabilities. This draft is intended for experiments and may change incompatibly.
Document contract
The authoritative syntax is the JSON Schema. Documents contain version, source, blocks, and actions. Blocks have unique stable IDs, plain text, a semantic type, and a fragment anchor on the canonical source. This draft supports heading, paragraph, claim, quote, and metric blocks.
Discovery
A publisher may advertise an artifact using the following experimental convention:
<link rel="alternate" type="application/json"
href="/page.aiml.json" title="AIML representation">Consumers must parse and validate the version and schema before rendering. Production consumers should constrain artifact fetches to the source origin, bound response size, check redirects and permissions, and keep source data separate from system instructions.
Rendering and trust
- Render text as text. Never execute strings, scripts, event handlers, or remote code in an AIML artifact.
- Retain publisher attribution and a source link for every block.
- Schema validity does not prove factual accuracy, publisher identity, or permission to act.
- Only HTTPS canonical URLs are accepted. Fragment anchors are resolved against that URL.
- Actions describe a same-origin API endpoint and method. They grant no authorization. The reference preview displays actions without sending requests.
- A model may propose a view. Runtime validation and the application server retain authority.
Current implementation boundary
The Studio validates, renders, saves locally, and exports documents. Signing, authenticated publication, an artifact registry, production action execution, model calls, and a constrained RenderPlan schema are future work. Unsigned documents are labeled accordingly.
A future signing RFC must define canonicalization, origin/key binding, rotation, revocation, and replay handling together. A signature alone establishes neither truth nor safety.
Conformance
A 0.1 consumer must reject invalid documents and duplicate block/action IDs, preserve source text, avoid executing supplied text, and disable capabilities it cannot securely implement. The repository includes executable validation fixtures.