Update on use case presentations to other working groups

Each FDC3 use case representative provided an update on engagement with other working groups (to share the Accepted Use Cases with them).  

During the upcoming OSSF, there will be an opportunity to present the FDC3 Use Cases in person to representatives from various FDC3 working groups. Kat will present if Saori is unable to attend. The expectation is that this is informative and discursive rather than approval seeking. There will also be a cross-program session (Plexus, FO, FDC3) to identify any implied or explicit interactions/responsibilities, including FO/Context.

Saori noted that there are only two use cases with context data called out as relevant, which doesn’t seem correct. The group was request to review this.

As a reminder: There is a section at the bottom of each use case (before comments) called "Interoperability Points" and this is where relevance to other working groups should be flagged.

FDC3 API: Kat joined the last meeting and has item on agenda for next week to present, but was also considering holding off to the following week and presenting in person. Kat to confirm with Nick. Kat thought tagging on the majority of use cases was okay but hadn’t looked through each one and would take that as a task.

FDC3 AppD: Leslie noted that the AppDirectory working group had recently approved a first version of their specification and that there were no dependencies on context data. Leslie had not yet presented use cases to the AppD WG. 

FDC3 Context Data: To be presented at OSSF during the use case session.

FDC3 Intents: Espen noted that the agreed plan is to wait for other parts of FDC3 to be more clearly defined so only as of today are they resuming scheduling meetings. Will pick this up in London at OSSF.

Financial Objects: Johann was not on the call.

Voice: Tom was not on the call.

People should feel free to introduce new use cases but the group won't start reviewing them until the current presentation round has been completed and feedback received from that process.

The group agreed that as part of the overall FDC3 documentation/site review the following should be addressed:

• there should an obvious place on the website for people to see how/where to add use cases
• there should also be clear links between the different FDC3 WG and deliverables (like specs/standards) and relevant use cases
• There should be a clear overview of the process for adding new use cases and there should be a "New" folder for new use cases. (Saori to action.)

The group briefly discussed recent activity in the Plexus Program and the statement that Plexus can handle things that the FDC3 API can not. The particular relevance for the group is to understand if there are use cases that Plexus can cover that the FDC3 API can not and how to address that. Other discussion items and actions included:

• Example of a use case where the FDC3 API does not appear to meet the requirements, how is this handled? Confirm that Version 1 does or does not address the needs; if rejected at this stage why; understand the plan for it to be addressed in API in the future.
• Tim asked if the expectation was for Plexus to be FDC3 API compliant. Leslie noted that  Tick42 has released a PR of a JS APi that allows type data. It an be used with Plexus but is not tied to Plexus.
• Example of Use Case 4 was given where request response is needed but this was dropped from the FDC3 API.
• Is it or is it not okay to look outside FDC3 to meet those use cases that Version 1 of the API does not meet. As a group do we just highlight them or do we look outside FDC3 for a solution?

• The group discussed whether the Use Cases WG should exist outside of FDC3 and sit across all working groups, with general consensus that this was a good idea. If the WG does move “up” then it may make sense for technical use cases to come back.

• Rob took an action to look into where Use Cases belongs within FDC3 programs, or at least identify next steps in the discussion.
• The WG agreed to explicitly call out where the FDC3 API does not meet the needs of the Use Case.

The next scheduled WG would be cancelled, due to OSSF, so the next meeting to take place in 4 weeks.