Agenda Items and Notes (including all relevant links)
Welcome & antitrust notice
Introduction of new members
Antitrust Policy Notice:Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role.
Callum Haslam: with the BC Gov Digital Mines team
Arun Suresh: from Wipro in India, on his first ToIP call
Vitor Pamplona: with the PathCheck Foundation. Representing the WHO work on trust registries.
Updates from TSWG members of general interest to the group.
Antti Kettunen shared that his company, TietoEvry, has been working on a project called a Verifiable eReceipt. In addition to a normal credential, they are proposing an extension to DID documents to have a service endpoint for a third party. This would allow individuals to have e-receipts sent to a third party such as expense receipts sent to their employer. They are currently evaluating it internally and when its ready, Antti hopes to share it publicly.
Drummond Reed shared how excited he was to see this approach applied to expense reports.
Judith Fleenor reminded everyone that if you are going to the Linux Foundation Open Source Summit Sept 12-14 in Dublin — or the Hyperledger Global Forum going on at the same time — the ToIP Summit 2022 is taking place Wednesday Sept 14 from 2:00-5:30PM UK.
It will include a ToIP pub night on Wednesday night.
Arun wanted to share the project his working on now called KochiOrgBook (https://github.com/hyperledgerkochi/KochiOrgBook). They are in the process of developing use cases right now, and developing for their local ecosystem. It is for associations inside their local jurisdictions.
Judith Fleenor also wanted to announce that the Governance Stack WG is starting up a Governance Architecture TF beginning on Sept 7 that will be working on governance framework templates and tools for governance framework components.
Review of Action Items from the previous meeting
ACTION:Drummond Reedto remindElisa Trevinoto add a wiki page with instructions about how to get a Confluence account (via an LF account).
ACTION:Darrell O'DonnellandDrummond Reedto send a note toJudith Fleenorthat biometrics should not be limited to the AIM Task Force—the TSWG (or the ToIP SC) should decide where the topic of biometrics should best be addressed by the ToIP stack.
ACTION:Darrell O'DonnellandDrummond Reedto meet offline to discuss how best to proceed with advancing the ToIP Technology Architecture Specification over the next two weeks (when Darrell,Wenjing Chu, and several other TATF members will be on vacation) in order to prepare it for a first Public Review Draft to present at the ToIP Summit 2022 on Sept 14 in Dublin.
Darrell again announced to restart the work on the ToIP Trust Registry Protocol Specification beginning in mid-Sept. He welcomes all new inputs and use cases. Darrell will be hosting a webinar in mid-September (21SEP2022 7am PT/10am ET/3pm) and welcomes folks to join to discuss where the early Trust Registry Spec was purposely limited and work is needed to get in much more detail. Reach out to Darrell to discuss - Slack or email (firstname.lastname@example.org).
Vitor Pamplona explained the requirements that he has been working on in the WHO work where health data needs to be able to be shared across borders—including across two countries who may be not friendly (or even at war).
This work began with the work on COVID credentials, but is now extending to all kinds of immunization records.
The approval by W3C of the W3C Decentralized Identifiers (DIDs) 1.0 specification has opened the opportunity for using DIDs and various DID methods.
Vitor's first task it to figure out how to represent very large collections of keys, e.g., thousands of keys. The need is how to share master lists of keys across multiple DID controllers.
One open question is: are DID documents the places to store such master lists of keys?
If so, how are those DID documents to be validated?
Are there additional specifications needed? Most of Vitor's work will be focused on moving forward any necessary draft specifications.
Vitor said that there are conversations happening in the FHIR community to make DIDs the standard for signing FHIR payloads. This could have a massive impact on adoption.
If we can help the community navigate through the different technology options.
Darrell pointed out that the trigger for WHO to move forward was the formal W3C recommendation. So this opens the question of what standards body we would want to take the ToIP Trust Registry Protocol Specification to, and how quickly that could be done.
Antti Kettunen said that it is an advantage to have a spec approved by an international standards org. ISO certainly qualifies.
Judith asked Vitor if this is an effort that should be publicized at the ToIP Summit 2022. Vitor believes the effort will be very useful. He said WHO is going to be separating the master list of keys from the rest of the metadata about the issuer. They are specifically focused on the key management portion for use of the ToIP Trust Registry Protocol Spec, while using ESSIF TRAIN for the rest.