org.hypercerts.context.acknowledgement
Acknowledges a record (subject) or its relationship in a context. Created in the acknowledging actor's repo to form a bidirectional link. Examples: a contributor acknowledging inclusion in an activity, an activity owner acknowledging inclusion in a collection, or a record owner acknowledging an evaluation.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | context.hypercerts.org |
| Indexed |
Record
record · key tidProperties
Whether the relationship is acknowledged (true) or rejected (false).
comment
stringOptional plain-text comment providing additional context or reasoning.
maxLength: 10000maxGraphemes: 1000
context
unionContext for the acknowledgement (e.g. the collection that includes an activity, or the activity that includes a contributor). A URI for a lightweight reference or a strong reference for content-hash verification.
Client-declared timestamp when this record was originally created.
signatures
refOptional cryptographic signatures attesting to this record's content.
The record being acknowledged (e.g. an activity, a contributor information record, an evaluation).
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
id.sifa.confirmation
recordConfirmation that a record naming you is accurate. Lives in the PDS of the confirming person, which for most relations is the person who was named and for the colleague relation is a colleague or the organization, never the record owner. One record type serves every people-link Sifa supports: co-speaker credits on a presentation delivery, membership of a project, and further relations as they are added. The claim itself is public in the claimer's repository from the moment it is written, before
-
A directional claim from this repository's holder about another party or record: 'we exhibited this', 'I performed on this', 'this is my work'. One-way and unapproved by default — the counterparty is never asked to accept anything. When two parties independently point at each other, any reader can compute a verified relationship from the closed loop; this is the mutual-mint primitive at professional scale. Pointing at a record with a CID pins the exact content attested to: if the target is silen
-
app.certified.badge.response
recordRecipient response to a badge award.
-
Acceptance record created by an invitee, acknowledging a collaboration invite. Lives in the invitee's PDS. The combination of an existing invite and a matching acceptance — both non-deleted — is what grants the invitee's writes to be surfaced against the subject record.
-
An evaluation of a hypercert record (e.g. an activity and its impact).