Page History

Agenda 

Overview of Purpose of Meeting
- Judith Fleenor, Director of Strategic Development

Review of Origins and Purpose of ToIP
- John Jordan, Executive Director

Discussions of the Strategic Imperatives of ToIP

Open Discussion of next steps

...

• 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.
  • 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”.
• 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.