...
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.
...
Leadership
The leads of the second-generation TRTF are:
...
- Drummond Reed, Gen
- sankarshan
- Vitor Pamplona, PathCheck Foundation
- Ken Adler
- Jim St.Clair
- John Walker
- michael boyd
- Eric Drury
- Mike Richardson
- Daniel Bachenheimer
- Savita Farooqui
- Antti Kettunen
- Vikas Malhotra
- Jacques Latour , CIRA
- Sumabala Nair
- Thomas Besore
- Christine Martin
- Scott Whitmire
- Neil Thomson
- Steve McCown , Anonyome Labs
- Judith Fleenor
- Mathieu Glaude , Northern Block
- Taner Dursun , TUBITAK BZLab
- Samuel Rinnetmäki, Findynet
- Fabrice Rochette, 2060
- Marcus Ubani
- Salvatore DAgostino
- Jon Bauer
- Andrew Escobar
Deliverables
- ToIP Trust Registry Protocol TSSSpecification. This is a formal specification of a protocol for interactions with a ToIP-compliant trust registry service. Note that this specification is initially being drafted as a Google doc which will then migrate to this wiki and finally move into GitHub for final publication.
- OpenAPI 3.0 API - (managed in GitHub).
- X.509 DID Interop concept guidance.
...
GitHub Repository
Intellectual Property Rights (Copyright, Patent, Source Code)
As a Task a Task Force (TF) of the Technical the Technology Stack WG (TSWG), the GSWG P&R TF inherits TRTF inherits the IPR terms from the the TSWG JDF Charter. These include:
- Copyright mode: Creative Commons Attribution 4.0. OWFa 1.0 (available at https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owfa-1-0)
- Patent mode: W3C Mode (based on the W3C Patent Policy). OWFa 1.0 (available at https://www.openwebfoundation.org/the-agreements/the-owf-1-0-agreements-granted-claims/owfa-1-0)
- Source code: Apache 2.0 , (available at at http://www.apache.org/licenses/LICENSE-2.0.html. )
- This Task Force is not currently expected to produce source code.
...
- Publication of the first Draft Deliverable via a GitHub repo.
- Publication of the final Draft Deliverable.
- Approval of the Draft Deliverable as a Working Group Approved Deliverable.
The work of the this Task Force will be complete when the Working the Working Group Approved Deliverable is approved by the TSWG.
...
- Slack: #tswg-trust-registry-tf <== This channel encouraged for regular comms.
- Mailing List: There is currently no separate mailing list; TBD if we will need one.this task force uses the main TSWG mailing list: technical-stack-wg@lists.trustoverip.org.
FAQ
- Q: Why can't we simply use VCs instead of a TR? A: At some point you MUST step out of a VC to say “and who says you are the authority”