Versions Compared

Key

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

...

TimeAgenda ItemLeadNotes
5 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:
    • Peter McCormick - Qui Identity
5 minsReview of action items from previous meetingChairsSchema repo CI
5 minsAnnouncementsTF Leads

News or events of interest to members:

5 mins

Reports

Open
  • W3C Update - continued discussions about PRs 1100, 1101.  Trying to negotiate  
  • Each type of ACDC defines its own transformation to W3CVC Data Model 2. So can be more specific.
  • VC-vLEI to W3CVC  with immutable @context`  for each type of credential more palatable to w3c.
  • GLEIF is moving forward with Large Euro Regulatory Agency to use vLEI for xBRL packages and for authorizing access to web portal to upload xBRL report package. Leverage SignifyTS client to access web portal. The AIDs for signing and access can be matched against role based access logic.ViRA acdc. may migrate to different XBRL international.
25 minsDiscussionOpen
  • Samuel Smith  IPEX spec and selective disclosure
    • Potential for moving this specification into ACDC instead of its own bespoke specification.
      • Daniel Hardman : Would versioning of the two specifications be fully dependent or could they need to be versioned indepentently?
    • 2 Party Model - Disclosee and Discloser.   
      • Either party can initiate the protocol
      • Negotiation can occur with repeated appy/spurn/offer message interactions.
      • Protocol interaction completes with a grant by the disclosure and subsequent admit by the disclosee
        • Nothing forces the use of admit message but the rules section could include a requirement to send the admit.
      • Disclosee messages: apply, spurn, agree, admit
      • Disclosure messages: spurn, offer, grant
    • All messages are signed
    • The normative SAID used in the IPEX message is the SAID of "most compact version" of the ACDC
    • Daniel Hardman : what does the request look like for requesting specific data?
      • It is all based on the JSON Schema
      • Requesting against specific values can be solved with bespoke schema using constants for value validation.
      • For example, requesting a credential with a specific issuer or specific role, those values would be constant values in the schema of the apply message.
    • Bespoke Credential Definition: https://github.com/trustoverip/acdc/wiki/bespoke-credential


5 minsAny other businessOpen
5 mins
  • Review decisions/action items
  • Planning for next meeting 

Chairs


  • Planning for Next Meeting
    • Kevin Griffin - Prune future topic list
    • Daniel Hardman - Discussion of SAID-ifying opaquely structured data.
    • Neil Thomson Discussion of requiring issuer intent to satisfy bespoke ACDC generation
    • Qui Identity Schema Review

...