...
Steering Committee member Andre Kudra agrees agrees with Dir. John Jordan.
Steering Committee member Wenjing mentioned the member Wenjing Chu mentioned the reason he joined ToIP, is that existing technology has limitations from a technical point of view. He said that a decentralized perspective is more efficient and that without a new system, future applications will hit limitations. He continued that If you look at financials, technology solutions can make that better. Digital domain will push privacy issues to a stronger position as a larger problem from the whole. Big players may not publicly say it, but we’re seeing it. What we’re working has technical stack but more importantly where a governance play into that. Great from migration and adoption point of view.
Steering Committee member McCown mentioned member Steve McCown mentioned an article by Andrew Tananbaum is that the best thing about standards is there’s so many to choose from. The world knows there needs to be decentralized identity and they need to be lead. There are a number of standards that fall under the toip stack. One is that ppl really want security with interoperability, illustrating how those standards can fit together is one of our strengths bc we’re superimposed over it all. The other thing is that larger companies will say they’re intestsed in the technology and that it’s going to stand the test of time. He’s also observed that jack dorsey started an effort that he’s written a white paper about moving finances around. It builds on verifiable credentials and steve will post the link in chat. We need to put into a framework that companies can adopt, but we also have large players that are pushing the technologies.
https://tbdex.io/whitepaper.pdf
Dir. John Jordan, what asked the Committee what are we trying to enable? Contractual relationships at large. Everything we do that has trust, is essentially a contractual relationship.
Dir Steering Committee member Marie Wallace mentioned there are 32 paper credentials that need to be verified to complete the process. Critical mass, challenge how can we co-exist with existing systems? How can we convince customers that benefits will increase, but it will happen overtime and it might be a long time. How do we co-exist with legacies that are in opposition with SSI?
Dir Steering Committee member Drummond Reed, i was just with Avast identity management team and now that we’re part of a larger group/company is how do we solve this in the immediate term. TCPIP and Desstar was established voice, great story why TCP went out. We are that global alliance that we believe can become the dominant design. Every step, we’re going to hit resistance and how will this work with what we have? I think the steering committee really understands and is brought into the idea of creating something that will be the dominant design. Most active architecture needs to get down to the protocol and details. High level spec by end of the year, but we have to make the decisions in order to get to the interoperability.
Dir Judith Fleenor, are you in agreement to move to being the dominant stack?
Dir. BrynSteering Committee member Bryn Robinson-Morgan , i want to build on what marie said Marie Wallace said with the legacy world. The idea of shifting to old way to new way, is a fallacy. What is important is how you integrate between the new/old. Governments want to maintain control. Here is where we separate the registries of systems but have a centralized way of connecting with their systems. We’re going to be a relevant org bc we’re going to bring something that works.
Dir Reed I do agree with Bryn that we should think about the evolutionary path for ToIP is 5, 10, 20, 30 years. My personal view is that it will “layer over” existing systems and integrate with them very much the way that the Web did (and even that TCP/IP did).
Dir. Buchanan first Steering Committee member Chris Buchanan first i think that technologists think of trust as unilateral and we need bilateral in whatever we build. In the real world, trust is usually unilateral, so how do we create this trust. We need to recognize that there will be casualties and we will improve some things while others might be worse too. We need to have expectations that there will be disenfranchised.
(1hr in) Dir Jordan cannon John Jordan cannon vs xerox and caterpillar example, it needs to be adaptable with social and technical systems that we have. How do we reduce uncertainty?
Kudra: Disruptive Innovation!
HOW?:
Dir John Jordan, the choices that we help make, an org looking to adopt this approach, learn to bring it in, along with their existing systems, a digital trust model that scales (tech and governance). Ultimately leads to software that is adoptable, open source software. This is how we will pave the way for adoption. Being compatible with the way we govern and the tools we use to do this, we can discuss next.
Dir Steering Committee member Wenjing Chu, adoption with technology migration, how does this happen? Companies have a choice, improbability. Needs to be easily adoptable, reducing the downside.
Dir. John Jordan, i think trust is interesting. Where does the trust need to occur? Helping ppl understand how this choice can help them realize the choices that they really want to make
Dir. Wallace the Steering Committee member Marie Wallace the problem is the middle man is the middle man. How can we repurpose what they’re currently doing as “middle man”, maybe we imagine a new model
Dir. Kudra are Steering Committee member Andre Kudra are we able to discuss what the narrowed scope is for ToIP?
Dir Reed yesSteering Committee member Drummond Reed Drummond yes, i’m optimistic about the opportunity for us to get into…maybe it s future SC meeting about the big picture, this is what we’re trying to get to. Design principles document helped us make progress.
Dir John Jordan, that discussion is the main objective for the year. This can help us formulate our communication strategy to help ensure we’re engaging the right audience. We need public sector voices in the conversation. We need to have more principle discussions in gov. More challenging in a biz setting.
...
- Design the stack within stack, have discussion of how are we tackling destructive path and when are we intentionally designing in the stack, this is how we connect with the legacy system.
- Drummond Reed, 1. What is the optimal design of stack? 2. What is the body of work on how to optimize/simply for integration?
- I would go so far as to say that “it is the power — and market value — of the trusted data ToIP Core will unlock that will drive adoption”.
- Steve McCown, built an interface to dropbox that would encryption and description on the way down. That allowed me to integrate with major systems with his own touch to it. I believe we need to integrate with what’s there but we need to stay focused on what the stack is and how it works. Also reach out to folks who are working with current/legacy systems and show them how they can implement
- John Jordan , be careful of false dichotomy, decentralized vs centralized. That’s not going away and it’s not at odds with Self sovereign identity. We need to be clear about this overall
- Bryn Robinson-Morgan, Agree that ToIP stack is the ToIP stack - it is the points of integration with legacy and future stacks that is important
- Chris Buchanan, agree with Drummond Reed, we have to start with reverence architecture
- Wenjing, comparison of our stack vs existing stack, we are trying to do the minimum possible to achieve our principles. We want to do the very minimum to achieve the goals, so that everyone can adopt and put work on top so that enables easy adoption.