This page has agendas, notes, and action items from each meeting of the UFWG in reverse chronological order.
Tuesday, July 7 — 18:00-19:00 UTC / 11:00-12:00 PDT / 20:00-21:00 CET / 03:00-04:00 JST (=next day)
Suggested Prep Work
- READ the Utility Foundry Workflow Proposal
- READ the Sample Story
- CONSIDER a real or hypothetical Utility story that you would be willing to document (for the 7/21 mtg).
- Provide updates to or issues against our Utility List.
If anyone has suggestions/concerns/issues for the proposed workflow, please open an issue.
Proposed Agenda
(-Meeting recording here-)
- Welcome and Linux Foundation antitrust policy (André)
- Introduction of new members
- Revisiting call for chairs & vice chairs
- Address priority ("get to work") items
- Review Terms and Concepts
- Review Utility Foundry Workflow Proposal
- Discuss process for gathering user stories
- Discuss open source decision tree rendering tools (i.e.: PlanetUML Activity Diagram)
- Update on Utility project liaisons
- Topics for Future Meetings
Tuesday, July 7 — 06:00-07:00 UTC / 23:00-00:00 PDT (=prior day) / 08:00-09:00 CET / 15:00-16:00 JST
Agenda and Notes
(-Meeting recording here-)
- Welcome and Linux Foundation antitrust policy (André)
- Introduction of new members
- Vinod Panicker
- Sankarshan
- Recap for new members
- Participants of this call did also participate in earlier call
- Jointly reviewing the suggested "get to work" items
- Vinod suggested a Sample Story serves as a governance template formulating collaborative interaction and best practice
- Sankarshan will prepare a sample for the upcoming meeting in two weeks
- Vinod provided an update on the crowd-source and open source project in Kochi in the state Kerala, India to facilitate decision taking for Hyperledger Indy/Aries, working with Cyber Dome police initiative
- Michael Shea provided info that in Italy there is another network driven by InfoCert named "DizMe"
- Michael Shea provided info about other ID initiatives: "BankID" Norway, "Its.me" Belgium, "NEM ID" Denmark, all driven from financial sector - relevant for ToIP?
- André Kudra stated that it is worthwhile looking into official EU activities (EBSI - European Blockchain Services Infrastructure and ESSIF - European SSI Framework)
- Benny Jung is interested in interoperability among DID platforms global. (I am working for "Korea DID Council")
- Benny Jung suggested to look into payment capabilities related to ID networks at some point
- Revisiting call for chairs & vice chairs
- Vinod Panicker volunteered for Chair position
- Topics for Future Meetings
- Ajay Jadhav suggested to look at governance aspects of networks forming in Europe - how can we leverage for ToIP
- Michael Shea suggested to get an update from DHS on interoperability initiatives
Tuesday, June 23 — 11:00-12:00 PT / 18:00-19:00 UTC
Agenda and Notes
Meeting recording
- Welcome and Linux Foundation antitrust policy (André)
- Introduction of new members
- Richard Esplin—Director of Product at Evernym, very active in Hyperledger Indy, Ursa, Aries
- Cameron Boozarjomehri, Mitre
- Further call for chairs & vice chairs
- Chair volunteers: Dan Gisolfi, André Kudra, others?
- Vice Chair volunteers:
- Cameron Boozarjomehri
- Mathieu Glaude
- Karl mentioned that we want to more broadly socialize this WG to new members
- Drummond confirmed that this is a priority for all the WGs as we have many new members (over 100 total now)
- There was consensus to keep nominations open for one more meeting cycle
- ACTION: André to send an email to the all-members list inviting new members and nominations
- WIP initial work items—leads, updates, working mode, next steps
- Workflow decision tree—Dan Gisolfi as lead (tbc)
- Dan explained that the Steering Committee is working on a description of the standard ToIP work products / deliverables (specs, templates, recommendations, white papers, etc.)
- Dan and team are working on capturing the stages in the lifecycle of a utility project
- He proposes a team that defines the stages in the flow —building on examples of existing or planned projects like Sovrin, Bedrock, etc.
- This will help us collectively define the major elements of a utility project
- Dan invites anyone who wants to pair with him on this work, just ping him on Slack in the #utility-foundry-wg channel (or DM)
- Karl agreed that identifying the stages of a lifecycle is something that also applies to the Ecosystem Foundry WG
- ToIP Utility projects liaison—André Kudra as lead (tbc)
- André reported that he is in contact with the three potential utility projects underway in Germany
- He is encouraging them to join the ToIP Foundation to collaborate to advance their efforts
- Karl asked about what definition we currently have of a ToIP Layer One utility?
- Drummond said that the most "official" definition is the current ToIP stack defintion in Hyperledger Aries RFC 0298.
- Dan pointed out that any ToIP Foundation member could contribute a definition of a term for the ToIP Glossary: https://github.com/trustoverip/concepts-and-terminology-wg/issues/new/choose
- Dan suggested that this work item could involve creating a markdown list of the utility candidates
- Dan is fearful of the ToIP Foundation becoming a "dumping ground" of projects that may not be qualified
- His view is that our list should be utility project who are directly contributing or seeking guidance from this WG about participating
- André explained one example: LISSI (Let's Initiate SSI) project lead to follow-up project in Germany, "SSI for Germany" (SSI4DE)
- SSI4DE is co-funded by the German Federal Ministry of Economic Affairs
- Currently in the 6 months competition phase
- The next phase will filter it down to 3 projects that will each have 15M€ funding for 3 years
- He believes it has a very good chance to be a successful ToIP Layer One utility
- Company that is the consortium lead is Main Incubator (Commerzbank subsidiary for digitalization initiatives)
- Project description (German) under https://www.digitale-technologien.de/DT/Redaktion/DE/Standardartikel/SchaufensterSichereDigIdentProjekte/sdi-projekt_ssi.html
Google translate:
https://translate.google.com/translate?hl=&sl=auto&tl=en&u=https%3A%2F%2Fwww.digitale-technologien.de%2FDT%2FRedaktion%2FDE%2FStandardartikel%2FSchaufensterSichereDigIdentProjekte%2Fsdi-projekt_ssi.html
- André explained a second example initiated by German "ECO Association"
- They have assembled several members who are interested in forming a network
- Want to be fully aligned with ToIP right away
- André has encouraged them to become Contributor Members ASAP
- The third one is govdigital
- Driven from the public sector for the public sector
- They are also contributing a little to the ECO Association
- Only public sector orgs will be able to run a node
- Also planning to use Hyperledger Indy
- André shared this link about all the German projects funded by the German Federal Ministry of Economic Affairs
- https://www.digitale-technologien.de/DT/Navigation/DE/ProgrammeProjekte/AktuelleTechnologieprogramme/Sichere_Digitale_Identitaeten/Projekte_Wettbewerbsphase/projekte_wettbewerbsphase.html
- Google translate: https://translate.google.com/translate?sl=auto&tl=en&u=https%3A%2F%2Fwww.digitale-technologien.de%2FDT%2FNavigation%2FDE%2FProgrammeProjekte%2FAktuelleTechnologieprogramme%2FSichere_Digitale_Identitaeten%2FProjekte_Wettbewerbsphase%2Fprojekte_wettbewerbsphase.html
- Findy (Finnish Indy) — https://www.findy.fi/
- Still recruiting members. Expect to join ToIP as both a utility, and as a group of
Project in Austria — https://meinesichereid.org
- Alastria in Spain
- ACTION: Dan will start creating a file for listing projects and drop it into Slack
- Workflow decision tree—Dan Gisolfi as lead (tbc)
- Selecting/prioritizing further initial work items—preferences, leads, contributors, task force mode — Dan suggests that we tackle these once we have the SC document on ToIP deliverables
- ToIP Utility RFP templates
- ToIP Utility Best Practices documents
- ToIP Utility website and utility directory
- White paper repository & opportunities
- Topics for Future Meetings
- DanG: Utility Project Workflow
- Richard: Presentation on Indy-based utilities and progress of Indy
- Richard: Discussion about the current state of Aries, it's future, and interoperability
- Adding an APAC call time
- André proposes to do this on alternative weeks to the US/EU call
Tuesday, June 09 — 11:00-12:00 PT / 18:00-19:00 UTC
Agenda and Notes
Meeting recording (https://zoom.us/rec/share/5MVZf7yv2XFIY7fk71zmB_88AIDJX6a81SFN_qALmE8DRIo5DLdOJyVdcbx-HPgj)
- Welcome and Introductions (André)
- André Kudra, esatus, Germany
- Dan Gisolfi, IBM, New York, USA
- Convener of the Bedrock Business Utility
- This is the WG that will enable interop between ToIP Layer One utilities
- We will "prime the pump" for other utilities
- Suggest we start off with a high-level workflow
- Drummond Reed, Evernym, Seattle, USA
- Chief Trust Officer at Evernym
- Darrell O'Donnell, CEO, Continuum Loop, Ottawa, Canada
- Want to see us build a very boring utility layer
- Matt Davies, CTO, Finicity, Utah
- Want to ensure a strong foundation for financial apps higher in the stack
- Wenjiing Chu, Futurewei, Santa Clara, CA, USA
- Wants to understand the structure and dimension of Layer One
- Goal is to build a stronger and more lasting foundation
- Mark Scott, San DIego, CA, USA
- Exploring all four of the initial WGs
- Generally more interested in the technical stack
- Steven Milstein, Ottawa, Canada
- Consultant, follower of SSI
- Interested in getting more deeply involved
- Arjun Govind, R3, typically in Philadelphia, currently in Bangalore
- Very interested in participating
- Sebastien Weidenbach, esatus AG, Technical Architect
- Markus Sabadello, co-founder, DanubeTech
- SSI architect
- Involved in the DHS Silicon Valley Innovation Program
- Sovrin Founding Steward
- Also operator of a Sovrin BuilderNet node
- Co-Chair of the Decentralized Identity Foundation Identifiers & Discovery (ID) Working Group
- Co-Editor, W3C Decentralized Identifier (DID) Specification
- Review of mission and scope
- André: we help as a community of practice for ToIP Layer One utility networks
- Drummond noted the ToIP Layer One utilities that are either existing or planned that may align with this mission
- Sovrin Network
- Bedrock Business Utility
- Findy (in Finland)
- Three forming in Germany—all are well aware of ToIP and aligned with interoperability with it—they are all interested in joining
- LISSI (Let's Initiate SSI), formally called SSI4DE (SSI for Deuscheland)
- govdigital—consortia of public data center providers in Germany that are planning a utility
- ECO Association of Internet companies in Germany
- Potential utility in Canada, possibly being incubated by the BC Gov Digital Trust Services team
- Austrian consortia that may be interested
- Banks, telcos, startups (DanubeTech has been an early participant)
- We broadly agreed that ToIP Layer One utilities are the foundational layer for decentralized PKI (DPKI)
- Proposed deliverables
- ToIP Utility RFP templates
- ToIP Utility Best Practices documents
- White papers
- ToIP Utility website including a directory of ToIP-compatible Utilities and Foundry Service Provider
- Workflow decision tree guidance <== proposed by DanG
- Potential Initial Work Items
- Develop ToIP Utility website and directory of ToIP-compatible Utilities
- Develop RFP templates and guides
- Develop ToIP Utility Best Practices documents and publishing process
- Initiate and maintain repository of relevant white papers and identify ToIP thought leadership white paper opportunities
- Build ToIP liaison with Utility projects and provide guidance
- eco German Association of the Internet Industry (in planning)
- Interop endeavors of govdigital and Findy
- Dan raised the liaison between a particular utility and a particular TIP (ToIP Interoperability Profile)
- Dan is interested in using this information to gauge market interest in particular Layer One technologies
- LF collaboration tools
- Github
- Github is our primary content repository
- https://github.com/trustoverip
- All deliverables (Markdown documents, other doc formats)
- Best practices content
- Research documents
- Overall github repo organizational proposal from Dan Gisolfi
- Should we convene a Task Force to design our particular branch(es)?
- Structure
- Github training sessions/tools
- WG Chairs
- Dan Gisolfi is willing to volunteer (seconded by Drummond due to Dan's leadership in convening the Bedrock consortia)
- André Kudra was nominated by Darrell and seconded by Drummond
- We agreed to open nominations to the mailing list and formally agree on chairs in the next meeting
- Meeting time and cadence
- We agreed to stick with this meeting time slot once every two weeks