Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 7 Next »

8AM PT, 11AM ET, 16:00 UK, 17:00 CET

APAC xxxxx2021 - 0500h ET / 1530h India

See the ToIP Calendar for meeting info. Send email to technical-stack-wg@lists.trustoverip.org to request a calendar invite (you can subscribe to the mailing list at lists.trustoverip.org).

Attendees

RECORDING 

Goals

  • Assign action items for next meeting
  • Establish work plan for WG deliverables and ensure action items have owners
  • Gather agenda suggestions for next meeting

Agenda Items

TimeItemWhoNotes
5 min

Welcome
Antitrust Policy Notice
Introductions

Chairs


2 mins

Review / Approve minutes from last meeting ()

Chairs
  • Approval: By Consensus
5 mins

Announcements

All
  • Good Health Pass
15 minsProposed new Task Force - Trust Registry Protocol TF - responsible for developing the Trust Registry Protocol spec (below)Drummond Reed
  • Trust Registry spec bubbled out of GHP WG and ToIP TSWG is a logical place to develop this TSS
  • Call for Consensus
5 minsProposed new Draft Deliverable - ToIP Trust Registry Protocol TSS
  • Call for Consensus
15 minsTask Force SOS (Scrum of Scrums)TF Leads
5 minsDecision PointsChairs
10 minsOpen Discussion TopicsChairs
10 minsReview Action and Open ItemsChairs

Notes

  • Darrell O'Donnell summarized recent decisions by the TSWG to simplify a description of the four-level model
  • Oskar van Deventer explained that he has written a blog post that discussed renaming Layer 2
    • He included nine requirements
    • We had a discussion about layer naming and agreed that it was a good time to rename the layers to be more descriptive of their requirements
    • "Privacy routing layer" was suggested 
    • We had a long discussion about requirement #9 on Oskar's list: "The communication channel shall enable compliance with legal requirements, like legal intercept."
    • Oskar described the "trapezium" that telcos deal with
    • Karl Kneis pointed out that we need to be very careful about the designed of this layer
    • Drummond Reed pointed out this blog post on "Reciprocal Negotiated Acccountability" from Daniel Hardman
    • Karl Kneis warned about our not getting too deep on this topic
    • Oskar van Deventer  asked for feedback about the requirements. He noted that no current technology addressed all nine of the requirements.
    • Drummond Reed asked about whether this included DIDComm V2, which is still not complete.
  • We moved to the topic of the EU Digital Identity Wallet announcements made on June 3
  • Darrell O'Donnell announced that the Trust Registry Task Force will begin meeting on Thursdays at 10AM Eastern Time. 
  • Karl Kneis asked about the status of the Saturn V TIP (ToIP Interoperability Profile).
    • Darrell O'Donnell suggested that the TIP may need a new name as the current name is too associated with American culture.
    • Darrell also suggested that the TIP needs some adjustments for greater alignment with different Hyperledger Aries implementations.
    • Karl Kneis would like to see this TIP putting out a clear spec and interoperability requirements, which is not yet the case, given the differences between Saturn V and the Aries Interoperability Profile.
  • Kaliya Young suggested that the TSWG should open a conversation with the DIF Interoperability Working Group that she co-chairs.
    • And I think it is important to acknowledge that there is active work going on trying to get a real working bridge of communication between Airies based agents and the other cluster of real working interoperability SVIP - with WACI PEx (which is called for in the Good Health Pass Interoperability Blueprint)
    • Kaliya would like to see that by summer we are testing on this - exchanging JSON-LD ZKP with BBS+ credentials.
    • Darrell O'Donnell would like to see a more formal relationship

CLEANUP

  • Take table, clean up (D&D), copy up to TSWG main page.

Announcement Details

  • Reminders
    • Task Force Activities
    • Events
      • Planned: None
    • Education Meetings
      • Planned: None
    • Resources - will be added to the TSWG Resources page:

TSWG APAC Interlock

APAC meetings not happening discretely at this time.

Task Force SOS (Scrum of Scrums)

<TODO: DARRELL clean table up - TF Name and the TF Deliverables>

TF NameMissionMembersStatus
Privacy by DesignSubmit a ToIP Design Principles Deliverable.

2021-05-31 ACTION DARRELL - find status (git, Google Doc, etc.) to prepare for CLOSEOUT


Laws of IdentitySubmit a ToIP Design Principles Deliverable.

DRAFT HERE (Google Docs)

2021-05-31 ACTION DARRELL - find status (git, Google Doc, etc.) to prepare for CLOSEOUT

SSI Principles

(DP0031)

Submit community work from Sovrin SUGF TF ad SEGF TF


MOVED to SC for approval - will drop from TF SOS next meeting.

2021-05-31 ACTION DARRELL - find status (git, Google Doc, etc.) to prepare for CLOSEOUT

TSWG 4-Layer Model

Darrell O'Donnell (lead)

<< NEED MORE >>

Top-Down using HL-Aries and HL-Indy (+ other ledgers possibly) as the framework exemplar. The goal is to explain the various 

GOAL: Get something out. EARLY SKELETON DOC

how does this 4-layer support the needs that we see...


Saturn-V TIP Task ForceSubmit a TIP Recommendation  Deliverable.

Dan Gisolfi   (lead) Chris B

TSWG GlossaryCollaborate with CTWG on the process and delivery of a TSWG Glossary. RJ Reiser  (lead) 

Glossary is an ongoing effort. Any updates?

"Big 4" should be referencing and be consistent (use terms, introduce new terms if absolutely required).

Foundational RFC Whitepaper Task Force

(WP0010)

RFC 289 Conversion 
Layer 1 (2:1) Interop Spec (TSS0011) Submit a ToIP Specification Deliverable 

Working on a deliverable plan.

Spec outline concepts being discussed. 

Deliverables Repo TSS0011 ready for TF development.

Layer 2 (3:2)  Interop Spec (TSS0012)Submit a ToIP Specification Deliverable

Working on a deliverable plan.

Spec outline concepts being discussed. 

Deliverables Repo TSS0012 ready for TF development.

Layer 3 (4:3) Interop Spec (TSS0013)Submit a ToIP Specification Deliverable

Working on a deliverable plan.

Spec outline concepts being discussed. 

Deliverables Repo TSS0013 ready for TF development.

Decentralization Task Force

(DP0005)

Submit a ToIP Recommendation as a Design Principle.

Daniel Bachenheimer  (Cross Foundation TF Representative)


Dependency for Saturn-V proposal. 

DISCUSS AT 14JUN2021 - being handled elsewhere

W3C Rubric

Dan Gisolfito send a call-for-participation to all ToIP WG members to join DP0005 TF.
Daniel Bachenheimerto coordinate with Jessica Townsendon the leadership of this TF which effectively will be an extension of the UFWG TF mission.


Net result: This TWWG work will be captured as a representative of the TSWG in the proposed TF. 

Technology Stack Task Force


Deliver an approved specification RFC 289 Conversion (TSS0002)

NEED CLARITY Drummond Reed (Create Wiki page) & Darrell O'Donnell

Q1 Deliverable - as part of the "Big 4" documents. 

NEED: 

  • Lead
  • Participants

Start with TSS0001 as beginning.

CHALLENGE - Review TSS0001 to get a grounding in what is required here. 

Content will be extracted from current state of WP0010.

Goal here is to adapt Hyperledger Aries RFC289 into a Tech Spec.

ToIP Stack Design Principles Task Force

(DP0034)

Combined Principles doc for the ToIP Stack. Part of "Big 4" deliverables. 

See Wiki discussion draft as well as the Big 4 description. Please also see WIP Google Doc.

2021-05-31 works continues - should be getting attention soon

RAISE at next (14JUN2021) meeting Drummond Reed

Decision Points

  • None

Discussion Topics

Action items

  • Drumm & Darrell to clean this page up - goal is to move items OFF or UP (to TSWG page)
  • Define and communicate to ToIP SC our deliverables and process. 
  • Move SOS to Trello Boards for 2021 
    • Migration to Kanban tooling. 
      • Trello Account Setup; Board creation WIP. 
      • Goal is to improve WG reporting (scrum activity) and allow Task Forces to organize and manage activity.
      • Upon completion of KanBan boards: Convert TSWG Bi-monthy Meeting into a Monthly Scrum of Scrums (SOS); Allowing TFs to meet more frequently and to be more focused on actual deliverables than status updates.
  • Sam Smith - Task Force Proposal for a meeting to be scheduled for January. 
    • Verifiable Authorizations: Mapping vCreds spec to authorization semantics. Positioning this concept with respect to other industry activity. 
    • Drummond noted that this thread was ongoing in the GitHub for the W3C Verifiable Credentials Data Model 1.0 spec, and that it was highly relevant to this proposed TF
  • Set Agenda for next meeting

Open Items

Low priority items that failed to gain volunteers to champion cause.

  • Change TSWG Mtg slot.
  • ISO Interlock discussion : ToIP Liaison (Vicky Lemieux) to ISO TC 307 (Emily Dawson Secretariat)
  • Need to establish chair duration and cycle times
  • Possible library - collection of links 


  • No labels