@openvtc/trust-tasks 0.28.8 → 0.28.10

package/dist/notifications/_shared/0.1/notification.d.ts

@@ -0,0 +1,22 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/notifications/_shared/0.1/notification.schema.json
+ */
+/**
+ * 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).
+ */
+export interface NotificationsSharedDefinitions {
+    [k: string]: unknown | undefined;
+}
+/**
+ * The definitions this shared schema publishes, hoisted to one declaration each.
+ * See "../../../_shared/components.js".
+ */
+export type { Did_NotificationsV0_1 as Did, Kind_NotificationsV0_1 as Kind, Notification, NotificationId, Status, Subject } from "../../../_shared/components.js";
+//# sourceMappingURL=notification.d.ts.map

package/dist/notifications/_shared/0.1/notification.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"notification.d.ts","sourceRoot":"","sources":["../../../../src/notifications/_shared/0.1/notification.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH;;;;;;;;GAQG;AACH,MAAM,WAAW,8BAA8B;IAC7C,CAAC,CAAC,EAAE,MAAM,GAAG,OAAO,GAAG,SAAS,CAAC;CAClC;AAED;;;GAGG;AACH,YAAY,EAAE,qBAAqB,IAAI,GAAG,EAAE,sBAAsB,IAAI,IAAI,EAAE,YAAY,EAAE,cAAc,EAAE,MAAM,EAAE,OAAO,EAAE,MAAM,gCAAgC,CAAC"}

package/dist/notifications/_shared/0.1/notification.js

@@ -0,0 +1,6 @@
+/**
+ * Generated by scripts/build-ts-bindings.mjs — DO NOT EDIT BY HAND.
+ * Source: specs/notifications/_shared/0.1/notification.schema.json
+ */
+export {};
+//# sourceMappingURL=notification.js.map

package/dist/notifications/_shared/0.1/notification.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"notification.js","sourceRoot":"","sources":["../../../../src/notifications/_shared/0.1/notification.ts"],"names":[],"mappings":"AAAA;;;GAGG"}