A Verifiable Trust Community's member directory: the card a member keeps about themselves, the projection of it another caller is shown, and the identifiers and audiences both are built from. Not itself a Trust Task specification (the `_shared` folder is skipped by the registry build and the codegen). THREE OWNERS. The community owns the field schema (`field-definition.schema.json`). The member owns their card: its values, a visibility per field, and their discoverability. The viewer owns what they think of others — stars, personal lists, private notes, petnames — and none of that is defined here, because none of it is stored by the community. PROJECTION. Another caller never reads a card; they read a projection of it. A field leaves the community only where all three hold: the visibility the MEMBER chose covers the viewer, the community's CEILING for the field covers the viewer, and the community's directory policy permits it. The three are intersected, never unioned. A withheld field is ABSENT from a projection, never present-and-null, and a subject with nothing visible is indistinguishable from no subject. NO DID IS NEEDED. Entries are addressed by `EntryId`, which is not derived from and does not reveal any DID of the member. Showing the member's DID is a field (`did`) like any other.
https://trusttasks.org/spec/vtc/directory/_shared/0.1/directory-cardTrust 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.