Date

Thursday 5th December 2024 - 10am (US eastern timezone EST) / 3pm (London, GMT)

Zoom info

• Join Zoom Meeting
• Meeting ID: 969 4029 4948
• Passcode: 636931
• Dial-in:

  Country	International Dial-in	Toll-free Dial-in
  US	+1 929 205 6099 (New York)	877 853 5247
  UK	+44 330 088 5830	0800 031 5717
  France	+33 1 8699 5831	0 800 940 415
  Find your local number	https://zoom.us/u/ad2WVnBzb8

Meeting notices

• FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

• All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

• FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.

• FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Participation Requirements

Note: Meeting participants are expected to accept the terms of the FDC3 license (Community Specification License), understand the governance process and have a CLA in place.

Please click the following links at the start of the meeting if you have not done so previously.

• View the CSL
• View the GOVERNANCE of the Project
• Click here to start a PR.
  • Edit the page to add your details.
  • Hit the save button.
  • Click "Create Pull Request".
  • Click "Accept" on the EasyCLA dialog in the PR's discussion section.
• Click here to send email to become a voting participant on the FDC3 Project

Tracking Attendance

Note: Meeting participants are expected to add a comment to this GitHub issue in order that we can track attendance of FDC3 project meetings. Please do this at the start of the meeting.

Agenda

• Convene & roll call, review meeting notices (5mins)
• Review action items from previous meeting (5mins)
  • Standard WG Meeting - October 24th, 2024 #1400
• Announcements and PRs under review
  • fdc3-dotnet 2.1.0 release: https://github.com/finos/fdc3-dotnet/releases/tag/v2.1.0
  • FDC3 for Web implementation progress update
  • Add conformance tests into docs #1417
  • Conformance additions for 2.2 (second attempt) #1426
  • (WIP) Adding .NET docs for Events to API reference #1441
• FDC3 for Web
  • Progress on implementation:
    • FDC3 For Web Browsers Implementation #1309
    • Fdc3 for web impl commonjs #1452 (help wanted!)
    • Fdc3 web impl prettier + eslint #1456
    • Complete implementation of SessionStorage retrieval in FDC3 for the Web implementation #1433
  • Approve small corrections to FDC3 for Web schemas:
    • Updating SessionStorage data format to additionally scope data #1442
    • Correcting privateChannelAddEventListenerRequest to include null as a valid listenerType #1446
    • Match event listener names to event type names in fdc3 for web schemas #1459
  • Question: Clarification on FDC3 Web Communication Flow and Resilience #1457
• Discussion of issues in scope for 2.3
  • Suggestions: Context Translation Middleware #1419
  • Add additional parameters to getOrCreateChannel to allow broadcast to be received by app that makes the broadcast #1407
  • Clarify: What should happen on repeated listener addition for the same contextType/intent #1390
    • Clarification re repeated addContextListener and addIntentListener calls #1394
  • Identity and Security proposals
  • Support better identity validation in Preload Desktop Agents #1339
  • Contexts
    • Add a notes field to trade, order and product types #1373
    • Add product type field to Product #1374
    • Standardize the representation of currency pairs by fdc3.instrument #1291
    • Improve the definition of the Position context type #656
  • Support for Multiple Application Scopes (Agents) within a single window process #1250
• AOB & Adjourn

Minutes

• Announcements

  • fdc3-dotnet 2.1.0 release: https://github.com/finos/fdc3-dotnet/releases/tag/v2.1.0
  • @bingenito reports that .NET 2.2 work has begun
    • proposed signatures (non-intent/context) event listeners (#1441)
    • Other work will be guided by the FDC3 CHANGELOG
  • API conformance test definitions are to be added to the documentation (#1417)
    • When adding to the API in future, PRs should ideally include any updates to conformance tests that are needed
    • Draft 2.2 conformance test additions are open for review (#1426)
  • FDC3 for Web Browsers implementation work is ongoing and active, a complete draft will soon be open for review and testing
    • The deprecation of the fdc3Ready() function from methods.ts and replacement by getAgent() was noted
    • ES6/Common.js: Whether to continue publishing is still an open question.
    • ES6 is still problematic when running tests with Jest (ES6 support is experimental), applications with legacy builds and legacy backend systems
    • One way to proceed would be to publish separate ES6 and Common.js modules - that will provide us with statistics on usage to compare - allowing the common.js version to be retired when it is no longer in use. The mono-repo structure introduced in the fdc3-for-web-impl PRs makes that easier to do.

• FDC3 for Web Browsers

  • Implementation work
    - Fair bit of implementation work is happening.
    - Giles is working on typescript types, type guards, validation function, better unions. This has been merged into the implementation PR.
    - Implementation is being aligned with the spec.
    - Prettier/ESLint need to be added.
    - Julianna has added reference UIs. Rob has also worked on the reference UIs.
    - Remaining work is to make this a well-documented, high-quality code base.
    - Implementers agreed that once more PRs go in (Kris'), it will be ready for code review.
    - We may not get Rob's time starting next year.
    - Upcoming: looking to recruit reviewers for the typescript code base.
    - Expect an announcement soon
    - The PR also refactors the FDC3 repository to be a monorepo to better support current and future component projects.

• minutes TBC

Action Items

• ...

Rolled over from previous meetings:

• FDC3 maintainers and interested contributors to revisit CommonJs vs ES6 #1351 as it should continue to be possible to publish a combined CommonJS and ES6 module, or to raise an alternative proposal.
• @finos/fdc3-maintainers Update the proposal for Support for Multiple Application Scopes (Agents) within a single window process #1250 to include a tear-down function for 'subAgents'.
• @kriswest add Add property to support analytics across apps #1290 to a future meeting agenda to determine what solution to select for the 2.3 scope
• @bingenito create an issue and PR to add the advice about consistent use of pascal case in enums in the API (implementation language and context docs (The Context Interface section after advice on union types).

Untracked attendees