FDC3 for Web Browsers Discussion group 21st Nov 2024

[kriswest]

Group overview

Group convened to work on proposals to enable FDC3 use in a web browser, without the use of a browser extension.

The main proposal is now part of the current draft of FDC3 2.2 on the mina branch of the FDC3 repo and website (main/unreleased version), see:

• https://fdc3.finos.org/docs/next/api/ref/GetAgent
• https://fdc3.finos.org/docs/next/api/specs/browserDesktopAgents

Open Pull Requests:

• FDC3 For Web Browsers Implementation DON'T REVIEW YET #1309
• Updates from impl review #1424
• Get docusaurus building #1434
• Updating SessionStorage data format to additionally scope data #1442

Relevant issue tags

Current open issues that relate to the above concepts with the label:

Meeting Date

Thursday 21st November 2024 - 11am (US eastern timezone EST) / 4pm (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 [email protected] 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.

• A Discussion Group has no direct decision-making power regarding the FDC3 standard - rather it is intended that anything they propose or work on will result in proposals (via Github issues and PRs) for the Standards Working Group participants to consider and vote on for inclusion in the standard.

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)
  • FDC3 for Web Browsers Discussion group 17th October 2024 #1391
• Address Session Storage issue in FDC3 for the web for same domain iframes in a parent window #1430
  • Updating SessionStorage data format to additionally scope data #1442
• Update on the current status of implementation & discussion of how to get involved
  • PRs merged recently:
    • Make window.fdc3 optional #1386
    • Use TS Morph to generate type predicates #1387 was incorporated into the implementation PR (and provides useful TypeGuard functions)
    • fix an incorrect $id in bridging/common.schema.json #1438 and Fixing another reference error in the bridging schemas #1439 addressed minor errors introduced into the bridging schemas
    • Remove ChartIQ and AG-Grid from FDC3 for Web demo implementation #1427 and Move addon package to toolbox/fdc3-for-web/reference-ui #1428 adjusted the reference UIs and removed some apps from the demos
    • Deprecating functions in Methods.ts #1403
• AOB & Adjourn

Minutes

• Session Storage proposal (Updating SessionStorage data format to additionally scope data #1442) was reviewed.
  • The proposal was accepted by the meeting, subject further review for clarity.
  • A deep link was added to simplify review.
• Recent activity and merged PRs were reviewed with attendees and the current status of the implementation project discussed.
  • @kriswest stated that: the FDC3 community will ultimately have to take ownership of the additions to the codebase to support getAgent. Up until now @robmoffat has carried the implementation project. We only get his support (shared with other projects) as FDC3 is strategic initiative this year.
  • @robmoffat It is likely that FINOS will have different priorities next year which may not include FDC3 as a startegic initiative again. @kriswest Hence, it is doubly important that the community take over maintenance and onward development.
  • @kriswest: I'm currently working in the project to:
    • improve the use of typing (replacing type overrides and the use of any),
    • align the implementation with the connection flow in the documentation, and
    • improve the separation between the WCP and DACP implementations.
  • @robmoffat Content has been added to the top-level README file in the fdc3-for-web-impl branch to describe the new layout of the repository and to help developers working on it get started.
  • @robmoffat also a number of issues have been created to track implementation tasks, see: https://github.com/finos/FDC3/issues?q=is%3Aopen+is%3Aissue+milestone%3A2.2+label%3A%22FDC3+for+Web+Browsers%22
• AOB
  • @Roaders' TSMorph PRs were discussed: They post-process the generated schemas and produce:
    • Unions of the different message types by type (RequestMessage, ResponseMessage, EventMessage), which enables better typing in code based on them: Use TS Morph to generate type predicates #1387 (comment)
    • TypeGuard predicates (e.g. isContextListenerUnsubscribeRequest) that again help with typing.
  • An updated version was just raised as Modify generate-type-predicates to only include interfaces that have … #1444 based on previous feedback
    • Some duplicated generated code was identified during the meeting, to be corrected
    • @robmoffat had already merged the PR into fdc3-for-web-impl and started using the generated code, adding in a set of constants for message type names.
      • The constants were discussed and (perhaps) considered to be duplicating the types...
    • The performance of the type guards was discussed - they currently involve stringifying messages and then reparsing them using the quicktype generated convert functions, which validate against the schemas. This is potentially costly - but we are unsure as to how costly.
    • An alternative faster implementation would be to just check the type name without validating content - there are merits to both approaches.
      • It was resolved to create fast is* functions and rename the existing ones (that perform validation) to isValid*
  • @kriswest recommended that we replace the quicktype generated AppRequestMessage, AgentResponseMessage and AgentEventMessage with the unions as they simply do a better job of typig the same objects.

Action Items

• ALL review SessionStorage docs PR for clarity Updating SessionStorage data format to additionally scope data #1442
• @Roaders to incorporate feedback on TS Morph PR into Modify generate-type-predicates to only include interfaces that have … #1444, @robmoffat and @kriswest to review and merge into fdc3-for-web-impl

Untracked attendees

Full name	Affiliation	GitHub username

[paulgoldsmith]

Paul Goldsmith / Morgan Stanley

[Davidhanson90]

David Hanson / Morgan Stanley 🚀

[Roaders]

Giles Roadnight / Morgan Stanley

[robmoffat]

Rob mOfFaT / fINoS

[pvoznyuk]

Pavlo Vozniuk @ RBC CM

[watson-ew]

Chris Watson / Elgin White 👋

[novavi]

Derek Novavi / S&P Global

[VedPrakashJha-FMR]

Ved Jha / Fidelity Investments