Meeting Date
The GSWG meets bi-weekly on Thursdays at 11:00-12:00 PT / 19:00-20:00 UTC. Check the ToIP Calendar for meeting dates.
Zoom Meeting Link / Recording
Attendees
@Wendy Seltzer
Main Goal of this Meeting
Bi-weekly Plenary reviewing Task Force updates.
Agenda Items and Notes (including all relevant links)
| Time | Agenda Item | Lead | Notes |
| 5 min |
| Chairs |
|
| 5 min | Review of action items from the previous meeting | Chairs | |
| 5 min | Announcements | TF Leads | News or events of interest to Governance Stack WG members: |
| 5 min | Task Force Updates | Chairs | Attraction Pass Neil Thomson Attraction Pass updates, including profile information sharing between participants, where info resides and moving from centralized to decentralized systems Scott Perry Is it possible to get feedback from DIF Hospitality Group? Neil Thomson Yes... Governance Architecture Carly Huitema A lot of discussion has been on the Governance Stack Scott Perry Looking towards the next generation Governance Stack diagram where the focus is initially, based on the Governance side without technology requirements and come back to tech side afterwards |
| 10 mins | Discuss and vote on the Issuer Requirements Guide | The Issuer Requirements Guide is now ready after addressing comments from the ToIP community. | |
| 15 mins | Identify and set goals for this year for GSWG | Scott Perry | Proposals
|
| 5 min | Any other business | ||
| 5 min |
|
Notes
Prompt: Please list the key takeaways from the meeting and then provide as much detail about each of them
Key Takeaways from the Meeting:
1. Progress on Ecosystem Foundry Working Group:
- The group has been working on identifying the key components that make a trust ecosystem.
- A model is being developed to help understand and evaluate trust ecosystems.
- Resources and discussions are available on the Slack channel for the Ecosystem Foundry Working Group.
2. Governance Architecture Task Force:
- The task force is addressing the challenge of representing the complexity of the Trust over IP (ToIP) stack for different audiences.
- There is an effort to create tailored presentations of the ToIP stack for governance experts, technology professionals, and business stakeholders.
3. Issuer Requirements Guide:
- The Governance Stack Working Group has approved the Issuer Requirements Guide for Governance Frameworks of Verifiable Credentials.
- The guide is intended to be compliant with the Governance Meta Model and will be presented to the ToIP Steering Committee for consideration.
- The guide can serve as a template for developing requirements for other roles within an ecosystem, such as verifiers.
4. Inclusion of New Topics and Task Forces:
- Suggestions were made to explore topics such as governance processes, verifier requirements, and holder responsibilities.
- There is interest in developing a governance architecture template and addressing the need for human-readable governance documentation.
5. Collaboration with Other Industry Groups:
- The Attraction Pass task force has been working on trust mechanisms and is looking to get feedback from industry players in the IoT and travel sectors.
- There is potential for collaboration with the Diff Hospitality and Travel Special Interest Group on travel profiles and related trust issues.
6. Concepts and Terminology Work:
- The Concepts and Terminology group has been working on establishing a robust glossary for verifiable credentials and decentralized identity.
- The Issuer Requirements Guide will need to align with the terminology established by this group before final approval.
7. Future Meetings and Objectives:
- The next plenary session of the Governance Stack Working Group is scheduled for four weeks later.
- The group aims to publish the Issuer Requirements Guide and solicit interest in exploring new task force ideas.
Detailed Discussion:
During the meeting, participants discussed the ongoing efforts of various working groups and task forces within the Trust over IP Foundation. The Ecosystem Foundry Working Group has been breaking down ecosystem presentations to identify the essential elements of a trust ecosystem. They are working on a model to assist in evaluating and building trust ecosystems, with resources and ongoing discussions available on Slack.
The Governance Architecture Task Force is tackling the challenge of how to represent the ToIP stack's complexity in a way that is accessible to different audiences. The task force is considering creating different versions of the stack diagram to cater to governance experts, technologists, and business people.
The Issuer Requirements Guide has been approved by the Governance Stack Working Group and is now awaiting consideration by the ToIP Steering Committee. The guide is designed to be compliant with the Governance Meta Model and could potentially serve as a template for developing requirements for other roles, such as verifiers.
Participants also suggested exploring new topics for discussion and potentially setting up new task forces. These topics include governance processes, verifier requirements, and holder responsibilities. There was also a call for creating a governance architecture template and addressing the need for human-readable governance documentation.
The Attraction Pass task force has been working on trust mechanisms for ticketing systems and is looking to get feedback from industry players in the IoT and travel sectors. There is potential for collaboration with the Diff Hospitality and Travel Special Interest Group on travel profiles and related trust issues.
The Concepts and Terminology group has been working on a glossary for verifiable credentials and decentralized identity. The Issuer Requirements Guide will need to align with the terminology established by this group before it can receive final approval.
The next plenary session of the Governance Stack Working Group is scheduled for four weeks later, where the group aims to publish the Issuer Requirements Guide and solicit interest in exploring new task force ideas.
Prompt: Please list the action items or to-do's
Based on the context provided, here are the potential action items or to-do's that can be derived from the conversation:
1. **Approval of Issuer Requirements Guide**:
- Present the Issuer Requirements Guide to Judith for consideration by the ToIP Steering Committee.
- Coordinate with Drummond and others to ensure terminology and concepts are aligned with the Trust over IP (ToIP) glossary and other foundational documents.
- Post a blog and disseminate the document to the repository once approved by the Steering Committee.
2. **Development of Verifier Requirements Guide**:
- Set up a task force to explore the need for a Verifier Requirements Guide.
- Determine the scope and content of the guide, considering the different trust tasks that verifiers may perform.
3. **Holder Responsibilities Document**:
- Explore the potential need for a document outlining holder responsibilities in an ecosystem.
- Discuss the legal and practical implications of holder agreements and terms of use.
4. **Governance Architecture Representation**:
- Continue discussions on how to represent the governance architecture effectively for different audiences.
- Consider creating different versions of governance diagrams tailored to specific stakeholder needs.
5. **Outreach to Industry for Attraction Pass Feedback**:
- Coordinate with the Diff hospitality and travel groups to gather feedback on the Attraction Pass use case.
- Extend invitations to the broader ToIP community for presentations on the architecture and industry outreach efforts.
6. **Governance Stack Working Group Leadership**:
- Confirm the roles and responsibilities of the co-chairs for the upcoming year.
- Plan for meetings to be run by different co-chairs to distribute workload.
7. **Engagement with IoT Community**:
- Follow up with IoT community members interested in verifiable credentials and decentralized identifiers (DIDs).
- Explore potential partnerships and joint efforts to advance the use of ToIP technologies in the IoT space.
8. **Governance Meta Model Review**:
- Review the current Governance Meta Model to ensure its relevance and effectiveness.
- Discuss potential updates or revisions that may be needed based on the latest understanding and industry needs.
- The discussion about the next version of the Governance Meta model revolved around reviewing its relevance and how it fits into the workflow of creating governance documents, DID documents, and their interrelation. Scott Perry mentioned the need to explore the Governance Meta Model to ensure it still works as intended and to understand the flow of how a governance document is created, linked to a DID document, and how this process facilitates the intended functionality of the Governance Meta Model. He suggested that this exploration should be added to their list of objectives to ensure that the model is still relevant and functional.
9. **Trust over IP Stack Specification**:
- Work towards developing the next generation of the Trust over IP stack specification.
- Gather input and feedback from various stakeholders to inform the development process.
10. **Enhancement of ToIP Glossary**:
- Contribute to the enhancement of the ToIP glossary to ensure clarity and consistency across documents and discussions.
These action items should be captured, assigned to responsible parties, and tracked for progress in subsequent meetings.
Prompt: What was the most popular topic of discussion?
The most popular topic of discussion seemed to be around the challenges of representing and presenting the complexity of the new version of the Trust Over IP (ToIP) stack, particularly in the context of the Governance Architecture Task Force. The conversation focused on how to effectively communicate the details of the ToIP stack to different audiences, such as governance experts, technology professionals, and business stakeholders. There was an emphasis on the need to create different versions or "flavors" of the governance side of the stack diagram to cater to these varied audiences, as opposed to the traditional approach of trying to combine both the technology stack and the governance stack in one diagram. This approach was seen as a way to unblock progress and facilitate a deeper understanding of governance within the ToIP framework.
Screenshots/Diagrams (numbered for reference in notes above)