You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Meeting Date & Time

This Task Force meets three out of every four Wednesdays (the fourth Wednesday is the Technology Stack WG plenary meeting). There are two meetings each Wednesday to serve different time zones:

  • NA/EU meeting: 08:00-09:00 PT / 16:00-17:00 UTC
  • APAC meeting: 18:00-19:00 PT / 02:00-03:00 UTC

See the Calendar of ToIP Meetings for exact meeting dates, times and Zoom links.

Zoom Meeting Links / Recordings

NOTE: These Zoom meeting links will be replaced by links to recordings of the meetings once they are available.

Attendees

NA/EU:

APAC:

Agenda Items and Notes (including all relevant links)

TimeAgenda ItemLeadNotes
3 min
  • Start recording
  • Welcome & antitrust notice
  • New member introductions
  • Agenda review
Leads
  • 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.
  • New Members:
2 minReview of previous action itemsLeads
  • ACTION: Drummond Reed to start a GitHub discussion on the question of TSP Workshops and also add it to the agenda for our March 22 meeting.
  • ACTION: Drummond Reed to send an email to the Technology Stack WG mailing list and post to the ToIP Slack with a Last Call for Proposals.
5 minsLAST CALL FOR PROPOSALS & prep for TSP WorkshopsDrummond Reed 

After today's Proposal #3 Part B from Wenjing Chu, we need to know if there are any other proposals in our proposal stage. If so, please speak up now.

Secondly, Neil Thomson and others have suggested that as we move into our consolidation stage, we are going to need one or more "Special TSP Workshops" of at least 2-3 hour duration.

40 minsProposal #3 Part B: Wenjing ChuWenjing Chu 

Wenjing will present Part B of his Proposal #3. A handful of screenshots from his presentation are shown below.

10 minsQ&A on the aboveAll

NA/EU:

Daniel Hardman asked what Wenjing meant by "backwards compatibility" for ITDP.

  • Wenjing clarified that all of his examples were about compatibility with legacy technologies with an eye to making adoption of ITDP as easy as possible. He does not mean that those technologies would not need any change at all.
  • Wenjing explained that his examples of how ITDP could fit with existing protocols like Aries, KERI, DWN, and OIDC would all evolve evolutionary paths for those protocols.

Clare asked about the mobile use case on slide 63 — would that include the mobile device? And how would that be implemented?

  • Wenjing gave an explanation of how the mobile device could speak existing protocols to supporting systems.

Darrell O'Donnell: Are we looking for backwards compatibility now (compatible to what?) Or are we planning for backwards compatibility?

Neil Thomson: "Observation - a large part of interop is likely to be on governance and verifiable authority (initially) vs technical compatibility. For example, OIDC provides a non-DID identifier that OIDC is prepared to provide a verifiable authority (signing of the identifier) to providing backing -> VID"

APAC: 



  • Review decisions/action items
  • Planning for next meeting 
Leads

Screenshots/Diagrams (numbered for reference in notes above)

#1


#2


#3


#4


#5


#6


#7

Decisions

  • Sample Decision Item

Action Items

  • Sample Action Item


  • No labels