Definitions shared by the person-to-person direct-message tasks (chat/direct/*). Not itself a Trust Task specification (the `_shared` folder is skipped by the registry build and the codegen). THE CONTAINER IS THE PAIRWISE RELATIONSHIP. A direct conversation is the exchange between two pairwise identifiers, the document's `issuer` and `recipient`. There is no conversation identifier: the relationship is the conversation. THE CONTENT VOCABULARY IS THE ROOMS ONE. `kind`, `body`, `inReplyTo`, `writtenAt` and `editedAt` mean what they mean in `rooms/_shared/0.1` (`SealedRecordBody`), so one renderer serves a direct message and a room message. The payloads `$ref` the rooms `RecordKind`, `RecordWrittenAt` and `RecordEditedAt` directly; the definitions here are the ones whose container differs: a direct message is named by an author-minted `messageId` rather than a host-located record `key`, and ordered by an author-set `revision` rather than a host-assigned `version`.
https://trusttasks.org/spec/chat/direct/_shared/0.1/direct.schema.jsonTrust 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.