The outer structure of a Trust Task document, per SPEC.md §4.2. This is the schema SPEC §7.2 item 1 requires a conforming consumer to validate the outer document against, selected by the target framework version the Trust Task specification declares (§7.3 item 3) — not by the version in the document's own type member. A complete validation composes this schema with the task-specific payload schema obtained from the document's type (§6.3). Additive over 0.4, and this version adds no envelope member: every property, type and constraint here is 0.4's carried forward unchanged, and every document conforming to 0.4 conforms to 0.5. What 0.5 adds sits outside the envelope — consumer requirements (the document lifecycle of §4.12; the freshness bounds of §7.2 item 13 over the existing `issuedAt` and `expiresAt`), specification requirements (`retention`, `exposure.ingests`, `parties[].identifierScope`, and a `maxLength` on every free-text member — §7.3 items 5, 14, 17, 18 and 19), and prose. A version with no member change still needs its own schema because §7.2 item 1 selects the schema by the *declared target framework version* of the specification, not by anything in the document: a specification cannot declare 0.5 as its target unless a 0.5 envelope schema exists to validate its documents against. Publishing 0.5 here is what makes 0.5 targetable; it re-targets nothing on its own. Descriptive, not a tightening: `additionalProperties` is true because §4.2 states a document MAY carry additional top-level members, and §7.2 requires a consumer to preserve — while not acting on — members it does not recognize.
https://trusttasks.org/spec/trust-task/0.5.0Trust Tasks — the registry of Trust Task specifications.
Loading the registry… If this message stays, the page's scripts could not load or run. The site needs JavaScript and access to unpkg.com.
Every specification is also on GitHub: trustoverip/dtgwg-trust-tasks-tf/specs, and the framework specification at /SPEC.md.