Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The primary objective of this Task Force is to develop the ToIP Trust ToIP Trust Registry Query Protocol (TRQP) as a ToIP SpecificationToIP Specification. The purpose of this deliverable to enable interoperability between ToIPbetween ToIP-compliant trust registries.

Context

The mission One of the ToIP Foundation is to define a complete architecture for Internet-scale digital trust that combines cryptographic trust at the machine layer with human trust at the business, legal, and social layers. The ToIP stack has two parallel halves—a technical stack and a governance stack—operating at four layers 1) Utility (DLT Blockchain), 2) Agent/Wallet, 3) Credential Exchange (Issuer/Verifier/Holder) and 4) Ecosystem (Application).  See further details in the ToIP white paper.A core role within ToIP Layer 4 is a trust registry (previously known as a member directory). This is primary uses of decentralized digital trust infrastructure is digital wallets and digital credentials. The primary roles involved in a digital trust ecosystem focused on the exchange of digital credentials are shown in the diagram below (see further details in the ToIP white paper):

Image Added

As this diagram illustrates, the heart of this ecosystem is a trust registry: a network service that enables a governing authority for an body—typically the publisher of an ecosystem governance framework (EGF) to —to specify what 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 trust registries (and their governing authorities) are trusted by a host trust registry.

Image RemovedIn most case this means answering one of two main questions:

  • Does Entity X have Authorization Y under Governance Framework Z?
    • This question allows a system to ask about what rights (authorizations) a particular entity has, according to an authority (governed by a governance framework). For example, "Is hospital X authorized to issue vaccination credential Y under governance framework Z?"
  • Does this trust registry recognize another trust registry X? 
    • This question establishes peer relationships between trust registries (often called a "registry of registries" or "metaregistry" capability).

As with all layers of the ToIP stack, the purpose of a ToIP specification a ToIP specification is to enable the technical interoperability necessary to support transitive support transitive trust across different trust 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 of decentralized trust registries operated by independent governing authorities representing multiple bodies 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 registrybusiness jurisdictions.

Leadership

The leads of the second-generation TRTF are:

...