This the home page for a draft of the ToIP Trust Registry Protocol Specification, a proposed Draft Deliverable of the TSWG developed by the Trust Registry Task Force (TRTF).

Status

...

and Links

Second Generation

The second generation specification is nearing Implementers Draft status. Here is a link to the current Working Draft.

First Generation

A first generation specification was developed by the first iteration of the TRTF:

...

This first generation version was published for public review in September 2021. It was not further advanced by the TRTF at that time as there was a consensus that other related specifications needed to be advanced first.In October 2022, a second generation of the TRTF began working on a second generation specification. Links will be provided here once there is a Working Draft.

Contributors

To comply with the intellectual property rights protections in the charter of the ToIP Foundation (as required by all Joint Development Foundation projects hosted the Linux Foundation), all contributors to this Pre-Draft Deliverable MUST be current members of the ToIP Foundation. The following contributors each certify have certified that they meet this requirement:

• Drummond Reed, Evernym
• Darrell O'Donnell, Continuum Loop
• Antti Kettunen
• Andor Kesselman 
• Drummond Reed
• Samuel Rinnetmäki, Findynet

...

In the same W3C CCG thread, Daniel Hardman made this point:

I feel like decentralization is running into a difficult tension here: we want to democratize issuance (anyone can do it), but we want to trust a limited set of issuers (or at least, a limited set on any given topic). Anybody can create a COVID test result credential, but we only want to accept them if they were issued by a lab that we have reason to trust. Etc...

One solution to this problem is registries: list trusted sources and have your software check whether the issuer is on approved/accredited list by querying. Of course this re-centralizes around the oracle.

...