Versions Compared

Key

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

...

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.

...

As with all layers of the ToIP stack, the purpose of 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 

...

Trust Registry Protocol v2 Scoping

The v1 protocol provides answers for three main questions

  • Is this Issuer Authoritative to issue a particular credential type under a governance framework.
  • Is a Verifier Authorized to request a presentation under a governance framework.
  • Does the answering Trust Registry acknowledge another Trust Registry under a governance framework.

The v2 efforts are exploring:

DISCUSSION AREA

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

TODO: 

  •  ACTION to Darrell: Move the EU Train and input from Daniel Hardman into Github.

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:

...