Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

22, June

...

2020 — 9:30

...

AM IST, 11:00 AM Thailand, Noon Singapore, 1:00 PM JST, 2:00 PM Sydney, AUS, 4:00 PM Auckland, NZ, 9:00 PM US PT, 12:00 AM US ET 

Send an email to technical-stack-wg@lists.trustoverip.org to request a calendar invite (you can subscribe to the mailing list at lists.trustoverip.org).

Agenda

Guiding Goal: Organize Organise the working group.

  • Welcome from the conveners (Dan, Matt—5 minDaniel Bachenheimer)
  • Introductions (WG, 15 min)<< TO BE COMPLETED>>
  • Logistics discussion
    • Wiki, meeting time, mailing list
  • Other topics

Attendees


The meeting presentation is attached to this page. <<TODO>>:

View file
nameTOIP Working Group 2020-06-22.pptx
height250

Meeting Notes

Recording:   https://zoom.us/rec/share/4c8oLZbc-0xIZp3h81j4c_E_R5vJX6a8g3NIq6EJzGIBVTSGrMDP36Rs4HRhDcs

DanB shared TSS Concept:

This meeting was not recorded

...

  • ToIP Technology Stack Specification (TSS) . This specification includes:
  • A technical description of each of the layers and their scope
  • The required, recommended, and optional functionality at each layer
  • The required, recommended, and optional dependencies on the layer below
  • The interoperability certification testing standards for each layer
View file
nameTOIP Working Group 2020-06-15.pdf
height250
  • & Task Over IP Interoperability Profile (TIP) discussion
  • Abilash question about alignment with ISO or other SDOs
    • There are technical components in each ToIP layer, which are already standardized (or being) under different SDOs suchas W3C, IETF, etc. using the work under DIF
    • Another questions was about cross-ledger interoperability which can be discussed under Utility Foundry WG
    • Question about writing whitepaper - Ajay suggested that a specific Task Force can be formed under TSWG, where the Task Force group can build and release white paper on specific topic. 
  • Benny's question about interoperability among DID ecosystems
    • Alignment scheme for verifying the verifiable credential
    • How to make payment  while a DID holder will verifying on other DID ecosystems - a DID ecosystem has their own payment structure
    • I am looking for a person for developing about what I said. 
  • Daniel or Matt will reach out to Linux Foundation (Todd) to schedule the APAC meeting calendar with revised time