Standard WG Meeting - May 23rd, 2024

[kriswest]

Date

Thursday 23rd May 2024 - 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 - April 25th, 2024 #1196
• Announcements
  • New look for FDC3 website
  • FDC3 2.1.0 npm module released
• Add event listeners (for non-context events) to the Desktop Agent API (e.g. for changes to the current User channel) #1136
  • Add event listener support to the Desktop Agent API #1207
• Context Clearing #1197
• AOB
  • Updates from Discussion group meetings
  • Contribution opportunities (issues in need of a PR) (5mins):
    • Add vendor agnostic default window size and position settings to the App Directory app definition format #564
    • Intent Proposal: Create or Update Profile #591
    • Allow an AppD application record to reference other apps that are *required* for it to run #674
    • Add /intents and /contexts endpoints to the AppD API #719
    • Improve OpenAPI (REST) documentation for the website with a docusaurus plugin #1001
    • Custom application config, retrievable via a standardized function #1006
    • FDC3 should avoid union types in contexts and other objects #1105
    • Understanding the FDC3 End-User Personas #1173
    • Vulnerability in axios found by CVE scan #1203
    • Get involved in the FDC3 for Web POC
    • Volunteer as an FDC3 Editor or Maintainer
  • Q&A
• Adjourn

Minutes

• Roll call and prior action items:
  • It was noted that the CSL link in the meeting minutes (and hence its template) is broken
  • The remaining docs work is underway on WIP: Adding .NET signatures to FDC3 documentation #1108
    • @kriswest and @bingenito agreed that we should 'get something out the door, then backfill in over time'.
  • Further discussion of Adding debugging information to help app developers trace broadcast storms #1142 will be rolled to the next meeting as the issue still needs to be reworked.
• Announcements
  • 2.1.0 npm package released
    • A participant reported a brief onboarding issue relating to the CSL license being bundled into the module, which is picked up by JFrog Xray and must be classified (but this was quick to achieve)
    • @kriswest mentioned a brief discussion with @robmoffat about reorganizing the FDC3 repo into a more formal monorepo to better separate the docs and software projects, which (amongst other things) would resolve that license bundling so that the module only includes the Apache 2.0 license.
    • This lead on to a short discussion about the mixing of Desktop Agent specifications, consumer documentation and governance info in the FDC3 site making it less accessible to adoptors. For example, the 'getting started' content relates to FDC3 governance rather than using FDC3. The maintainers might consider refactoring this as FDC3 continues to grow.
  • New look FDC3 homepage launched, which collects and presents more info on various aspects of FDC3 (What is it, Why use it, How is it structured, Who's using it, Get involved, Conformance, Training)
• Add event listeners (for non-context events) to the Desktop Agent API (e.g. for changes to the current User channel) #1136
  • A new contributor (@kemereva) raised the PR (Add event listener support to the Desktop Agent API #1207) to implement this proposal - many thanks!
  • A participant asked if the proposed event for 'user channel changed' gives you both the appId and channel details
    • @kriswest:
      • As proposed, the event is for the local app (i.e. the one that registered the listener) so the appId is implict and you can get it from getInfo()
      • The new channel id is given - but not the previous channel id. Participants couldn't immediately think of a use case for the previous channel details and there was consensus that this could be added later if a use case was found.
  • @kriswest asked for and received consent to merge the change once it clears reviews.
• Context Clearing #1197
  • @hellosmithy provided an overview of the use case for this issue:
    • selectively resetting context on a channel such that existing apps on the channel 'reset' AND those that join later don't receive the context that has been reset - which might be used to, for example, reset/release filters
    • e.g. You might have an instrument and timerange as context to filter a list of orders, then wish to release the timerange filter
    • The use case was recognized by a subset of other participants
  • Existing solutions to this based on fdc3.nothing are lacking:
    • Receiving fdc3.nothing can currently only tell you to release all context, and only for apps already listening to the channel, apps that join or getCurrentContext later can still pick up other types. Further channels can only tell you the most recent context received and most recent of each type, rather than the order in which each arrived (to reconstruct when the fdc3.nothing arrived in the sequence).
  • Meeting participants explored the solutions proposed in the ticket and brainstormed a variety of other solutions (e.g listening to an out-of-band channel for resets, sending context with null ids or a standardized id field for reset) - most of which have an undesirable property (like conflicting with required properties in context types, potentially forcing breaking changes to them and poor developer ergonmics).
  • There was consensus that the 'hybrid solution' proposed (an API call to reset context and an update to the fdc3.nothing type to be able to reference another type for selective reset messaging to apps) is the most viable solution proposed.
    • The API call indicates to the DA that it should remove the context (either identified type or all) from the channel AND issue an fdc3.nothing message to existing subscribers.
    • We might also consider allowing apps to send the fdc3.nothing messages and have the DA react to those...
  • @hellosmithy was asked to update the proposal issue with the result of the disucssion, with help from @kriswest, to be brought back for a vote on inclusion at the next meeting
  • There was also a short discussion of whether this was a breaking change for .NET as it changes the API interface - it may need to be adopted as optional or a solution to that found.

Action Items

• @robmoffat/@kriswest Fix the CSL link in the meeting agenda template
• @finos/fdc3-maintainers / @finos/fdc3-editors to complete review of Add event listener support to the Desktop Agent API #1207 and merge
• @hellosmithy & @kriswest update issue Context Clearing #1197 based on the discussion, before moving to a PR

Rolled over:

• @bingenito & @kriswest to complete PR WIP: Adding .NET signatures to FDC3 documentation #1108 and submit for review - to include at least a basic version of supported platforms content (to be improved later)
• @kriswest & @mistryvinay look at 1068 Generating context docs from schema files #1151 and consider taking over final changes (which include deleting existing context docs, hooking up script to auto-generate as part of build and making sure existing URLs do not break)
• @kriswest & @julianna-ciq rework issue Adding debugging information to help app developers trace broadcast storms #1142 to reflect the other use cases and update the proposed change based on the discussion

Untracked attendees

Full name	Affiliation	GitHub username

[hellosmithy]

@kriswest the meeting says Thursday 25th May 2024, will it be today - Thursday 23rd May?

[mistryvinay]

@kriswest the meeting says Thursday 25th May 2024, will it be today - Thursday 23rd May?

Great spot @hellosmithy !! I have just updated the issue.

[kriswest]

Oof, sorry about that! Thanks for correcting it @hellosmithy and @mistryvinay

[mistryvinay]

Vinay Mistry / Symphony 🎵

[Lecss]

Alex Dumitru / Citi

[bingenito]

Brian Ingenito / Morgan Stanley

[milindchidrawar]

Milind Chidrawar / Singletrack