Standard WG Meeting - April 24th, 2025

[kriswest]

Date

Thursday 24th April 2025 - 10am (US eastern timezone EDT) / 3pm (London, BST)

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 - March 27th, 2025 #1548
• Proposal of a new FDC3 Maintainer: @Roaders
• Revisit PRs for open issues
  • No defined behaviour when incorrect arguments are passed to API calls #1490
    • Add InvalidArguments to OpenError, ChannelError and ResolveError enums #1559
    • Check for consensus on approval to merge
  • Clarify: What should happen on repeated listener addition for the same contextType/intent #1390
    • Clarification re repeated addContextListener and addIntentListener calls #1394
    • Check for consensus on approval to merge, with minor corrections to conformance test
  • Should the desktop agent support both unqualified appIds and fully qualified ones? #1475
    • Resolving Fully-qualified and unqualified AppId values #1523
    • Check for consensus on approval to merge
  • Context Clearing #1197
    • Context Clearing #1379
    • Should we switch to using an event to announce context clearing?
• New issues under discussion
  • Support specifying supported context when registering an intent listener #1545
  • Support the ability to specify where I would like a new app to open #1546
  • Support changes to the set of User Channels in the Desktop Agent API #1543
  • Inconsistent naming standards on casing in schemas #1547
• AOB (if time) & Adjourn

Minutes

• Review Action Items from Previous Meeting

  • Action items from the previous meeting (Standard WG Meeting - March 27th, 2025 #1548) discussed:
    • Kris has updated Resolving Fully-qualified and unqualified AppId values #1523 on fully qualified and unqualified appId values; ready for review.
    • Kris and Rob discussed unique appIds.
    • Elizabeth added the @experimental label; it needs review before merging into the current draft.
    • No defined behaviour when incorrect arguments are passed to API calls #1490 was implemented by @KhurramJalil as Add InvalidArguments to OpenError, ChannelError and ResolveError enums #1559 and is set to merge as it has received all necessary reviews.
    • Giles is addressing the TypeScript/JSON conversions (issue Clarify that Context types are defined in JSON and may be handled differently in specific API bindings #1486) and will provide updates.

• Proposal of a New FDC3 Maintainer: @Roaders

  • Proposal to add Giles as a new FDC3 Maintainer; no objections raised.

• Revisit PRs for Open Issues

  • No defined behaviour when incorrect arguments are passed to API calls #1490

    • Discussed the proposal to add InvalidArguments to OpenError, ChannelError, and ResolveError enums (Add InvalidArguments to OpenError, ChannelError and ResolveError enums #1559).
    • Achieved consensus on approval to merge.

  • Clarify: What should happen on repeated listener addition for the same contextType/intent #1390

    • Lizaveta proposed clarifications regarding context listeners and intent listeners.
    • Clarification agreed upon; multiple context listeners are acceptable, but only one intent listener can be added at a time.

  • Should the desktop agent support both unqualified appIds and fully qualified ones? #1475

    • Review PRs Should the desktop agent support both unqualified appIds and fully qualified ones? #1475 and Resolving Fully-qualified and unqualified AppId values #1523; ready for maintainer reviews.
    • No objections to resolution logic for appId clarification.

  • Context Clearing #1197

    • Discussion on mechanisms to inform apps of context clearing (Context Clearing #1379).
    • Proposal to implement an event type, potentially named fdc3.nothing, to signal context clearance.
    • Alternative suggestion of allowing null as a value for context; consensus to explore further.

• New Issues Under Discussion

  • Support specifying supported context when registering an intent listener #1545

    • Discussion on maintaining consistent functionality for context registration.
    • Various options proposed, including overloading signatures and adding a backward compatibility option.
    • Action item for Giles to update the issue with proposed solutions and open it for team voting.

  • Support the ability to specify where I would like a new app to open #1546

    • Brief discussion; no specific conclusions noted.

  • Support changes to the set of User Channels in the Desktop Agent API #1543

    • Exploration of the impact of runtime changes to user channels; no actions specified.

  • Inconsistent naming standards on casing in schemas #1547

    • This issue noted for future review.

Action Items

• @kriswest: Merge the changes for No defined behaviour when incorrect arguments are passed to API calls #1490, and complete review process for Resolving Fully-qualified and unqualified AppId values #1523 and Support specifying supported context when registering an intent listener #1545.
• @Roaders: Update issue Support specifying supported context when registering an intent listener #1545 with potential solutions and initiate voting.
• @kemerava : Review the proposed changes linked to the @experimental label.
• @julianna-ciq : Raise the issue related to destructuring linked to fix: better support 1.2 DAs by not requiring appMetadata in getInfo responses #1550.

Rolled over from previous meetings:

• @kriswest & @robmoffat to consider further discussion on recommending globally unique appIds as a standard for app record constructors.
• @kemerava & @kriswest update Adding language binding for golang #1483 with @experimental labelling and merge into current draft for 2.3
• @Roaders and @kriswest to explore comparisons between string encodings of Dates and Date objects in JavaScript/TypeScript + any other deviations of the TypeScript binding from JSON and to report back on issue Clarify that Context types are defined in JSON and may be handled differently in specific API bindings #1486 - then propose clarifying language to be added to the FDC3 API and Context specifications.

Untracked attendees

Full name	Affiliation	GitHub username

[bingenito]

Brian Ingenito / Morgan Stanley

[Roaders]

Giles Roadnight / Morgan Stanley 🚀

[robmoffat]

Rob Moffat / FINOS

[paulgoldsmith]

Paul Goldsmith / Morgan Stanley

[kriswest]

Kris West / NatWest 🚀

[kemerava]

Elizabeth Kemerava / BlackRock

[openfin-johans]

Johan Sandersson / Here 🎁

[hughtroeger]

Hugh Troeger / FactSet

[SeeWhatsOn]

Chris Watson / Elgin White✨

[novavi]

Derek Novavi / S&P Global