Canonical AclEntry 0.2 and its component $defs, referenced by the 0.2 acl/* specifications and by any family that reuses the capability shape (vtc/roles). Not itself a Trust Task specification (the `_shared` folder is skipped by the registry build and the codegen). See CONVENTIONS.md beside this file for the rules a consumer applies across tasks. What 0.2 changes over 0.1: authority is STATED, never inferred from a shape. 0.1's `scopes` — a list whose emptiness meant `everywhere` for one role and `nowhere` for another, depending on a maintainer convention the wire could not carry — is replaced by `act`, an explicit act scope that is one of `all`, `none`, or a non-empty list of contexts. 0.1's `approve {all, scopes}` is replaced by the same explicit three-shape scope. 0.1's `allowedKeys` — where absent meant every key and empty meant none — is replaced by an explicit, REQUIRED `keys` scope. Capability-level authority is new and equally explicit: `capabilities` is REQUIRED and states `ceiling`, `none` or a listed set; `approveCapabilities` states the same three or is absent, which means none. No member's absence, and no collection's emptiness, ever confers authority. Delegation provenance (`delegatedBy`) is new. CONVENTIONS.md §8 documents how a maintainer maps a 0.1 entry onto 0.2. Role and capability identifiers are OPAQUE to this family: the acl/* tasks are used by maintainers with different vocabularies (a VTA's context administrators, a VTC's administrative roles). A maintainer publishes its own role set and capability registry; the vtc/roles family is one such vocabulary. Timestamp invariants (SHOULD-level, prose — not expressible in JSON Schema): when both `createdAt` and `updatedAt` are present, `updatedAt >= createdAt`; when both `createdAt` and `expiresAt` are present, `expiresAt > createdAt`. Consumers SHOULD reject documents that violate either.
https://trusttasks.org/spec/acl/_shared/0.2/acl-entryTrust 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.