• Start recording
• Welcome & antitrust notice
• Introduction of new members
• Agenda review

• 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:
  • None

• Judith Fleenor Tomorrow is the All Members working group - update the slides ASAP. In the working group update the KERI suite slide to say old task force is closed, point to the KERI suite working group.

News or events of interest to members:

• Sam Smith: vLEI ISO spec published: GLEIF Newsroom announcement
  • PDF of announcement
  • Charles Lanahan: For those who have access to the ISO spec linked above and are involved in the process, can we discuss what that means? 
    • Is it accurate to say now that KERI/ACDC/CESR et al are ISO specs? 
      • Answer: No, KERI and ACDC are not ISO specs yet.
    • Are they in the review period?  How long does that last?
      • Answer: We do not yet know.
    • Trivia: Japan's objection was the reason vLEI was not approved last year as an ISO spec. Once they removed their objection then this process moved forward
  • We acknowledge Karla McKenna's skillful efforts in the ISO community getting the vLEI ISO spec pushed through and published.
• Lance Byrd: new vLEI Developers Weekly Meeting:
  • GLEIF, NordLEI, Provenant and other vLEI developers are evolving the ‘vLEI Top 10’ developer discussion as a new GitHub prioritized backlog project and weekly meetings on Thursdays at 1pm UTC.
  • Details (and adjustments) can be found here https://github.com/GLEIF-IT/vLEI-dev-community
    
    
  • Proposal:
    • Review PRs weekly, combine the dev meeting with the community meeting since we don't have a lot of spec work left.
      • We have a weekly meeting so we don't have a 2 week period to approve pull requests.
      • Changed proposal: Have a weekly developer meeting and have an as-needed spec call to move the ToIP specs along.
      • Good feedback from Judith: Where do people go now that we have a new KERI Stack Working Group?
        • Compromise from Sam: Let's do a once-a-month spec call.
        • Nov 12 meeting is next task force meeting
• The DICE conference in Zurich where KERI was brilliantly represented, the dates for 2025 have been announced.

  • Dates announced for this years Digital Identity unConferences Europe (DICE)

    
    

    March 4th & 5th, Zurich

     Building Capacity & Capability for Ecosystem Adoption of Verifiable Credentials and Authentic Data

    
    

    September 2nd & 3rd, Zurich

    Annual gathering for the companies and individuals working on developing and deploying digital identity systems in Europe.

• Switzerland is looking at KERI

Reports

• Got a response from Juri:
  • No need to have people accept the OWFa - Upon working group participant's execution of the working group charter they are subject to the agreements set forth in the working group's charter, applying to all deliverables for that working group.
    • Ensure all working group participants are notified that the work is an approved deliverable.

• meeting cancelled during IIW
• OWFa

  • Thanks for your email question. There is no need to have contributors sign the OWFa - they have already agreed to the OWFa when they signed the ToIP Membership Agreement and joined the ToIP Technical Stack Working Group – 2:

    
    

    1. Open Web Foundation Final Specification Agreement 1.0 (“OWFa 1.0”). Upon the Working Group Participant’s execution of the

    Working Group Charter, that Working Group Participant will be subject to the obligations set forth in the Open Web Foundation

    Final Specification Agreement 1.0 (available at http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0,

    “OWFa 1.0”) with respect to the current and one immediately prior version of all Approved Deliverables from that Working

    Group.

  • 2. Open Web Foundation CLA 1.0 (“OWF CLA 1.0”). Each Working Group Participant will be deemed to have executed the OWF

    CLA 1.0 for its Contributions (as defined in the OWF CLA 1.0) to the Working Group (available at

    http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owf-contributor-license-agreement-1-0---copyright-andpatent).

    3. For Exclusion. Prior to the adoption of a Draft Deliverable as an Approved Deliverable, a Working Group Participant may exclude

    Granted Claims from its licensing commitments under the OWFa 1.0 by providing written notice of that intent to the Working Group

    chair (“Exclusion Notice”).

  • The Exclusion Notice for issued patents and published applications must include the patent number(s) or

    title and application number(s), as the case may be, for each of the issued patent(s) or pending patent application(s) that the

    Working Group Participant wishes to exclude from the licensing commitment set forth in Section 4 of this patent policy. If an issued

    patent or pending patent application that may contain Granted Claims is not set forth in the Exclusion Notice, those Granted Claims

    will continue to be subject to the licensing commitments under the Agreement. The Exclusion Notice for unpublished patent

    applications must provide either: (i) the text of the filed application; or (ii) identification of the specific part(s) of the Draft

    Deliverable whose implementation makes the excluded claim an Essential Claim. If (ii) is chosen, the effect of the exclusion will be

    limited to the identified part(s) of the Draft Deliverable. The Project Chair will publish Exclusion Notices.

  • 4. Approved Deliverables. Upon a Draft Deliverable being declared an Approved Deliverable by the Steering Committee, Working

    Group Participants will, without further action, be subject to the obligations set forth in the Open Web Foundation Final

    Specification Agreement (OWFa 1.0) with respect to that Approved Deliverable, except for any Granted Claims set forth in an

    Exclusion Notice. The OWFa 1.0 is available at http://www.openwebfoundation.org/legal/the-owf-1-0-agreements/owfa-1-0.

  • This applies to the contributions made to the work after it was moved to TSWG-2 (as earlier contributions were made in TSWG-1 the W3C policy). You will want to ensure that all Working Group participants have been properly notified that you are coming up to the point of declaring the work an Approved Deliverable.

  • https://cdn.platform.linuxfoundation.org/agreements/ToIP.pdf
• Follow up question: What does she mean by exclusion notice?
• Also, it's not just a steering committee approved deliverable, it's a Technical Stack approved deliverable.
• From Sam on OWFa, language from the OWFa:

  • Once a final Specification is ready to be published, contributors and supporters of the Specification will be asked to sign an OWFa to formalize their copyright licenses and patent promises to the entire Specification.

    • This is what should be happening right now with 0.9, that is how it should be used.

• Review decisions/action items
• Planning for next meeting