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

Compare with Current View Page History

« Previous Version 4 Next »

Meeting Date & Time

  •  
    • NA/EU 07:00-8:00 PT / 14:00-15:00 UTC 
    • APAC 18:00-19:00 PT / 01:00-02:00 UTC <== NOTE THE NEW TIME!!!

Zoom Meeting Links / Recordings

Attendees

Main Goal of this Meeting

Continue review and discussion of the working draft of the ToIP Technical Architecture Spec.

Agenda Items and Notes (including all relevant links)

TimeAgenda ItemLeadNotes
4 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.
  • New Members:
    • Mattia Zago from Monokee
5 minAnnouncementsAll

Updates of general interest to TATF members.

  • Drummond Reed shared that the ToIP session at the European Identity Conference was very successful as the EU digital identity community is "starved" for interoperability solutions.
  • Rodolfo Miranda shared that the DIF DIDComm Working Group will vote on the DIDComm V2 specification next Monday.
1 minReview of previous action itemsChairs
  • ACTION: Wenjing Chu Will continue to fill in sections of the document in section order. The weekly schedule going forward will be reviewing both new work and comments as sections are completed.
40 minsReview progress and next steps on the ToIP Technology Architecture SpecWenjing Chu

See comments and suggestion on the ToIP Technical Architecture Spec - Working Draft.

  • Wenjing Chu went over the structure of the spec.
  • The question of terminology definitions came up in depth
  • Neil Thomson said that most of last week's APAC meeting was taken up by terminology discussions.
    • Drummond Reed said the the Concepts and Terminology WG tooling for terms wikis would be perfect to use here. There was a general consensus that it was indeed a good tool, but in the short term the glossary definitions being created for this spec will go into a glossary at the end of the doc for now.
    • ACTION: Neil Thomson will consolidate the terms being defined for purposes of this spec into a glossary at the end of the spec.
    • ACTION: Drummond Reed will work with the Concepts and Terminology WG members to set up a terms wiki for the Technology Stack WG that we can begin using immediately with this spec.
  • Wenjing continued to go through the sections of the spec and the goals and open issues with each.
  • The term “party" came up. It is a very well-defined term in the eSSIF-Lab glossary. https://essif-lab.github.io/framework/docs/terms/pattern-party-actor-action
  • Vlad Zubenko asked whether there was a separation between hardware and software systems. Wenjing share that there was intentionally not a difference in the overall design; they are all treated as nodes participating in the overall system.
5 mins
  • Review decisions/action items
  • Planning for next meeting 
Chairs

Agenda items for the next meeting:

  • Allan Thomson will present on use cases.
  • We also need to have a discussion about moving the draft over from Google docs to GitHub so we can begin using GitHub issues for issue management.
  • ACTION: Drummond Reed to add two items to next week's agenda: 1) Allan Thomson presenting on use cases, 2) Moving the spec from Google docs to GitHub.

Decisions

  • None

Action Items

  • ACTION: Neil Thomson will consolidate the terms being defined for purposes of this spec into a glossary at the end of the spec.
  • ACTION: Drummond Reed will work with the Concepts and Terminology WG members to set up a terms wiki for the Technology Stack WG that we can begin using immediately with this spec.
  • ACTION: Drummond Reed to add two items to next week's agenda: 1) Allan Thomson presenting on use cases, 2) Moving the spec from Google docs to GitHub.


  • No labels