Attendees introduced themselves including individuals new to the WG discussion:

• Shawn from Sagezza evaluating how they can

• engage with FINOS
• David Jones recently joined FDC3 and this working group

Kat walked through the wiki and explained why the use cases WG exists (define the use cases for the other WGs to build for)

• Kat: "Feel free to add use cases"
• Statuses show different states of the use cases

OSSF

Productization provided a brief background and introduction on the FDC3 Use Case WG including an overview of the wiki:

• The purpose of group is to put together use cases of what the community does and does not want to support in terms of FDC3 interoperability.
• The Group has gone through an initial set of 15 use cases assessing validity and usefulness.
• Moving forward this will be on an ad hoc basis so individuals are encouraged to propose new use cases.
• Criteria for what is a valid and useful can be found here.
• The existing use cases can be found here and are organised into categories: In Review, Accepted, Rejected and Deleted. The use case template can be found here.

This was the "A main purpose of the meeting "

Owner of the use case will identify the other working groups represented, and then we have a WG representation who will take the use cases to that WG, and will present them

Action item from Leslie: Can we an optional field to capture other working groups impacted?

Who will be the reps?

• API Reps: Kat and Leslie
• AppD: Leslie
• Intents: Espen
• Context: Saori

Saori: will there be any use cases that will have impact on voice?was to determine the best way to present the use cases to other relevant working groups and agree next steps to action this.

The following points were agreed:

• A representative will be assigned to present the accepted use cases to a specific WG. This individual is familiar with both the use cases and the WG to be presented to.
• Use case templates should be updated to reflect which working groups are relevant for that use case. This should be done in the section called Interoperability points. This field should be updated by the end of the week (19 Oct).
• Use Cases that are to be presented to a WG should be provided ahead of the WG meeting so that individuals can read the use cases ahead of the presentations.
• Presentations to WGs should be completed by the Use Case WG meeting on 15th November.
• The WGs are not required to "accept" the use cases but they should provide feedback if they don't find them valid or usable → "comply or explain"
• The agreed representatives are:
  • FDC3 API: Kat
  • FDC3 AppD: Leslie
  • FDC3 Context Data: Saori
  • FDC3 Intents: Espen (This will be presented later in the autumn when the WG resumes regular mtgs).
  • Financial Objects: Johan
  • For Voice, Tom Schady will present them as necessary.

The group, including new participants, was encouraged to submit use cases and also to read existing use cases first to avoid submissions being rejected for being duplicates. It was also pointed out that those use cases "under review" are still "live" and can be revisited following modifications.

Where use cases have been accepted all comments have been considered and incorporated (or not) as appropriate. Kat and Saori to consider how to make it clearer that these are final.