Shared shapes for NOTIFICATIONS: a signed statement by an ORIGINATOR, addressed to one DID — an individual, a group, a community or a network — that a THING exists which the addressee, or the parties it stands for, may act on or take part in. THE MODEL. A notification names the thing by where it is held (`subject.heldBy`), its identifier there (`subject.id`) and the Trust Task that opens it (`subject.openWith`), and names the AUDIENCE: the DID whose holders or members the thing concerns. It carries nothing of the thing's content. It confers no authority and is no evidence of eligibility: whether a recipient may take part is decided by the holder when the thing is opened, as if no notification had been sent (VTI-NTF-003, VTI-NTF-004). IDENTITY AND DEDUPLICATION. A notification is identified by its originator's DID (the `issuer` of the notifications/notify document — for a node, its durable identity, which a key rotation does not change) together with `notificationId`, which the originator chooses and keeps unique among the notifications it issues. Every delivery attempt, every re-issued document and every relayed copy of one notification carries the same `notificationId` and `revision`, so a recipient holds at most one record per originator and `notificationId` (VTI-NTF-021, VTI-NTF-022). An originator changes or withdraws a notification by issuing a higher `revision`. KINDS. `kind` names what the thing is: a name registered in the notification kind registry of the VTI specification (Appendix G), or a name under a domain its definer controls (`org.example:meetingInvite`). The registry is kept outside this schema, which fixes only the form of a name, so registering a kind needs no new version of any task. Each kind's definition states what `subject` and `audience` mean for it, whether it may be relayed and what a relay discloses (VTI-NTF-010, VTI-NTF-011).
https://trusttasks.org/spec/notifications/_shared/0.1/notificationTrust 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.