id.sifa.meeting
Attestation of a face-to-face meeting with another user. Both participants create this record in their own PDS. The meeting is only displayed when both records exist (mutual confirmation). Either party can delete their record to remove the meeting. Like every record in a repository, it is public, including the optional event.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | sifa.id |
| Indexed |
Record
record · key tidProperties
event
refOptional reference to the community.lexicon.calendar.event where the meeting took place. Each participant decides whether their own record carries it, so consumers show the event only when both records reference the same event AT-URI. Resolve and match by AT-URI; the CID is an optional integrity hint, since organizers can edit event records. The event is chosen when the meeting code is shown and committed to in meetingToken: consumers that can verify the token ignore an event that does not match it. Omit the field to record the meeting without an event.
Server-issued JWT proving both parties were authenticated at the time of meeting. Contains both DIDs, timestamp, and server signature. When the meeting code was shown for an event, the token also commits to that event.
maxLength: 512
DID of the other participant in the meeting.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
One appointment, written into the invitee's own repo and linked back to the host's meeting type. The invitee owns the record (and may cancel it); the host aggregates bookings through the back-link index on `eventType.uri`.
-
id.sifa.authMeet
permission-setOAuth permission set for recording verified face-to-face meetings.