2023.08.08/09 IGRTF Meeting Notes
Zoom Meeting Link / Recording
- Recording Aug 9 Meeting
- Transcript (captured by zoom, edited for clarity)
Attendees
- Aug 8 - Call included Neil Thomson, and Sankarshan, who had general discussions and closed the call without capturing notes, deferring to the NA/EU call on Aug 9
- Aug 9 - Neil Thomson, Sankarshan, Karla McKenna, Philip Feairheller, Steven Milstein
Main Goal of this Meeting
Agenda
- Review Assignments (Karla McKenna, Phil Feairheller) GLEIF - review Issuer Requirements Related Documents from the perspective of GLEIF’s experience as an Issuer and developing governance for Issuers (and the Ecosystem supporting an Issuer)
- Discussion of the above, plus the Issuer Requirements Documents and next steps/action items:
- Minimum Viable Credential Policy Template for Verifiable Credentials.docx
- Nov 2020 template for overall credential policy, imported into Issuer Req TF folder April 2023
- There is a problem with this document - a search revealed that there are two versions in the ToIP folder space; one is marked as a Scott Perry Document, which is also marked as Shared, which, particularly from looking at the comments (which are different in each) that this shared version is a separate copy from the one in the Issuer Requirements TF folder of the same name. The Shared Copy (to which most of the comments were made, including the work in today’s NA/EU meeting) has been copied to the ToIP/GSW/Issuer Requirements folder as:
- Minimum Viable Credential Policy Template for Verifiable Credentials.docx
- ToIP Issuer Requirements.docx
- Aug 1, 2023 draft of ToIP Issuer Requirements
- Issuer Requirements Suggested ToC outline (Sankarshan, Neil Thomson, John Phillips, Jo Spencer)
- Suggested organization, outline and additional sections for ToIP Issuer Requirements Spec
- Tabled, but not discussed: Attraction Pass TF - What allows Bob to trust an Attraction Pass Sales Agent?
- Exploring Issuer and Trust Registry approaches to establishing trust for an Event Consumer interacting with a ToIP-based Attraction Pass Ecosystem
Agenda Items and Notes (including all relevant links)
Time | Agenda Item | Lead | Notes |
5 min |
| Chairs |
|
APAC Call | All | As only two attended (Sankarshan, Neil Thomson) only general discussion then close the meeting in deference to attending the NA/EU call | |
NA/EU Call | All | The meeting was in adding GLEIF comments (and group discussion) to the MVC “shared” document (see notes above as to the most current MVC document in the ToIP Issuer Requirements Folder - the “formerly Shared Copy” version). See the recording and transcript for details. While reviewing each comment, there was a discussion on the MVC and ToIP Iss Req 1st draft document, some of which is captured here. The MVC and ToIP Iss Req documents are substantially different documents. It is understood that the ToIP Iss Req (is different from the MVC) as it leveraged an existing x509 certificate issuance document. They are also highly prescriptive and detailed. Specific comments, from the meeting transcript: Philip Feairheller: Yeah, I think that I'm missing the scope of what an Issuer requirement specification was intended to be, because as I'm looking at the newest working group draft (ToIP Issuer Requirements), dated Aug 1, 2023, there are very specific actual requirements for issuers, where some of which I completely disagree with, like referencing W3C verifiable credential stuff, as opposed to a specification that explains to people how to write requirements, issue requirements for an ecosystem governance framework. That's the model that Karla and I took when approaching these comments. Not that this group should be documenting requirements for Issuers, but that this group should be helping people guide people in how they create issuer requirements for their ecosystem. Karla McKenna: and what topics and aspects of requirements should be covered? Sankarshan: And we need to be more lightweight than a 50-page requirements document (template) which potential adopters may choose to disregard. | |
Suggested Actions/Next Steps |
| ||
Screenshots/Diagrams (numbered for reference in notes above)
#1
Decisions
- Sample Decision Item
Action Items
- Sample Action Item