...

This the home page for a draft of the ToIP Trust Registry Protocol TSS (ToIP Standard Specification)Protocol Specification, a proposed Draft Deliverable of the TSWG developed by the Trust Registry Task Force. The Working Draft of this specification will proceed through three stages:

1. Google doc: For ease of drafting and commenting during the early Draft Deliverable stage, the spec is initially starting as this Google doc. <== THIS IS THE CURRENT DRAFT FOR REVIEWS AND CONTRIBUTIONS
2. Wiki page: Once the Google doc version of the spec is reasonably stable, it will move here to this page for final review and approval as a Working Group Approved Deliverable.
3. GitHub Markdown file: Once we reach a call for consensus on a Working Group Approved Deliverable, the spec will be converted into a Markdown document and moved into a ToIP GitHub repo.

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 that they meet this requirement:

...

Other contributors MUST also add their name and membership affiliation to the Google doc or wiki page version of the spec as it proceeds through development.

Terminology

In this document, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this document , when appearing in ALL CAPITALS, are to be interpreted as described in RFC 2119.

All other terms in bold will be defined in one or more of the ToIP glossaries in a process being defined by the ToIP Concepts and Terminology Working Group.

Purpose

The purpose of this TSS this specification is to specify a standard interoperable protocol for interactions with any ToIP-compliant trust registry. 

Motivations

A core role within ToIP Layer 4 is a trust registry (previously known as a member directory). This is a network service that enables a governing authority for an ecosystem governance framework (EGF) to specify what governed parties are authorized to perform what actions under the EGF. For example:

1. What issuers are authorized to issue what types of verifiable credentials.
2. What verifiers are authorized to request what types of verifiable presentations.
3. What other governing authorities are trusted to authorize these same parties and actions within their own trust registriesother trust registries are trusted by this trust registry.

As with all layers of the ToIP stack, the purpose of a TSS a ToIP specification is to enable the technical interoperability necessary to support transitive trust across different trust communities implementing the ToIP stack. In this case, the desired interoperability outcome is a common protocol that works between any number of decentralized trust registries operated by independent governing authorities representing multiple legal and business jurisdictions. One specific example of this need is the digital trust ecosystem defined by the Interoperability Working Group for Good Health Pass (GHP). The GHP Trust Registries Drafting Group produced an extensive set of recommended requirements for a GHP-compliant trust registry.

PLACEHOLDER for Working Draft Specification 

Once the Google doc version of the specification is sufficiently complete, the specification will move here for final review.

DISCUSSION AREA

This area is for posting and discussing topics relevant to this Task Force.

EU TRAIN Project

TRAIN stands for "TRust mAnagement INfrastructure". It is a subproject run by Fraunhofer-Gesellschaft within the EU eSSIF-Labs Project. This quote is from a recent post to the W3C Credentials Community Group (CCG) mailing list by David Chadwick:

...

Note that the TRAIN source code can be run by anyone, so there can be multiple distributed copies of this service running on the Internet, and verifiers only need to keep pointers to one or more of them to provide them with backup services (much like the dozen or so root DNS name servers).

Credential Chaining

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

...