This Task Force meets every Wednesdays at 09:00-10:00 ET / 15:00-16:00 CET (see the Calendar of ToIP Meetings for full meeting logistics including Zoom links)
Agenda Items and Notes (including all relevant links)
Time
Agenda Item
Lead
Notes
3 min
Start recording
Welcome & antitrust notice
Introduction of new members
Agenda review
Chairs
Antitrust Policy Notice:Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role.
Review list of criteria and ensure definitions allow for objective responses
Brainstorming functional properties
Hakan Yildiz Architecture dependencies (e.g., on layer 2 transport mechanisms) (e.g., client-server architectures vs p2p)
@Subhasis - Look at features (e.g., online/offline), architectures, support of credentials (e.g., mDL isn't W3C), regulatory compliance (eIDAS 2.0)
Judith Fleenor - once technical analysis done, possibility to create more high-level artifacts (e.g., infographics) targeted to less technical/business decision makers
Hakan Yildiz - need to come up with terminology (e.g., what does 'maturity' mean?, maybe there's a need to define nested standards within specification and implementation level)
Hakan Yildiz - logical operations and/or XOR (being able to make a cred request for 2 different credentials - e.g., show me a covid pass and national id in one cred exchange request)
@Subhasis - Rigidity and flexibility of protocol (e.g., how you can construct a proof request or issuance - comparing predicate proofs vs age proofs in mDL - mDL is rigid as issuer predefines the predicates - vs in Aries presentation exchange I can do greater than 1 or 2)
@Subhasis & Drummond Reed - Do any of these protocols have implementation standards to help people adopting (e.g., best practices, test suites, certification programs which are signs of maturity)
Vladimir Simjanoski - combining protocols - such as creating a DIDComm connection and then using OpenID4VCI for an issuance flow
Drummond Reed - Identifiers supported (classic web ids vs decentralize ids, or AIDs as a sub-class of DIDs)