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 5 Current »

DRAFT - PENDING APPROVAL AT NEXT WG MEETING on 11/1

Table of Contents

Date/Time

 


Attendees

NameOrganisation
Refinitiv
Former user (Deleted)Refinitiv
Adam LancasterTick42
Ben GoldWellington
David Jonesipushpull
Espen OverbyeOpenFin
Johan SanderssonFactSet
Leslie SpiroTick42
Sean McQuaySaggezza
Tom SchadyGreenKey
Rob Underwood (Deactivated)FINOS
Tosha EllisonFINOS


Action Items

Tasks Identified and Assigned

  • All Use Case Owners: Update use cases with dependent FDC3 WGs

Task Report from Last Meeting

(In the task report select the meetings notes from the LAST meeting in the 'Space(s) and page(s)' field to auto-populate this table– remove this note before publishing)

Task report

Looking good, no incomplete tasks.


Decisions Made

  • The group assigned individuals from the FDC3 Use Cases WG to present the accepted use cases to the other FDC3 as well as FO working groups. 
  • <Decision>


Agenda and Discussion items

TimeItemWhoNotes
1 minSelect Scribe for meetinggroupTosha Ellison volunteered to be scribe.
1 minRoll callgroup

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
1 minReview MinutesgroupKat made a motion to approve minutes for the last two meetings (Sep 6 and Sep 20). Saori seconded the motion. There being no objections minutes were approved.
3 minHousekeeping - Next mtg locationgroupThere is an option to hold the next WG meeting in person in NY. Refinitiv can host for anyone who can make it. The date might also be adjusted to accommodate schedules (and a conference). Saori will send an email to the group on this topic.
5FDC3 Backgroundgroup

Kat 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.
30 minDiscussion of what's next for the accepted use casegroup

A main purpose of the meeting 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.

3 minReviewing open action itemsgroup
5 minAOBgroupNo other business to note.
  • No labels