Skip to content

Schemas

VTC — shared community-owned room definitions

Shared types for rooms a community owns rather than merely hosts: the vtc/rooms/community/* tasks an administrator runs them with, and the vtc/rooms/offers/* tasks a member collects and accepts an admission with. The community is the room's owner; the community's own VTA holds the room's signing key and, on a sealed tier, the community's place in its MLS group. The community holds no room key and no group secret. What it records here is the owner's own record of whom it admitted — never read when the community serves the room as its host, where authorization is the room's credential chain and nothing else. Version 0.3 changed nothing here but where `HostedRoom` comes from: `room` resolves to vtc/_shared/0.3/room-storage, whose `HostedRoom` instants are RFC 3339 strings; every other referenced definition stays at 0.1. Version 0.4 renames `Renewal.renews` to `renewsAt` (type unchanged), for the registry's naming consistency; nothing else changes. Version 0.5 adds a room's own state as its owner keeps it — archived read-only or with no access, scheduled for removal, being purged, removed — in `RoomState`, `ArchiveAccess`, `RoomStatus` and `PurgeProgress`; `CommunityRoomV3`, which is `CommunityRoomV2` with that `status` and a `suspended` count; and `MemberStateV2`, `RoomMemberV2` and `RoomMembershipV2`, which add the member state `suspended` for an admission a room closed to every member has withdrawn and will restore. Every 0.4 definition is unchanged. Not itself a Trust Task specification (the `_shared` folder is skipped by the registry build and the codegen).

Schema ID
https://trusttasks.org/spec/vtc/_shared/0.5/community-room
Kind
shared
Used by
12 specification versions

Trust 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.