-
Notifications
You must be signed in to change notification settings - Fork 164
Description
Date
Thursday 26th June 2025 - 10am (US eastern timezone EDT/EST) / 3pm (London, GMT/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)
- OSFF 2025 recap
- Classification field to refine 'type' for contexts #1615
- Add property to support analytics across apps #1290
- Context Clearing #1197
- 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
- AOB & Adjourn (5mins)
Minutes
-
Convene & Roll Call, Review Meeting Notices
- Meeting opened with introductions from new attendees @Albert-Herd-LSEG and @Bruno-LSEG, both addressing PR permissions.
-
Review Action Items from Previous Meeting
- PR addressing fully qualified apps completed.
- PR Support specifying supported context when registering an intent listener #1545 remains in progress; @Roaders has a PR, with @robmoffat requesting (conformance) test cases.
- Destructuring issue deferred.
- Date and Date Objects documentation not advanced by @kriswest or @Roaders.
- Context clearing work by @kemereva completed, pending editor review.
- Source maps issue deferred.
- Placement options querying discussed at OSFF; summary posted by @Roaders.
-
OSFF 2025 Recap
- @julianna-ciq presented an introduction to FDC3 for the Web.
- Security and Identity work presented by external contributors.
- SubAgent proposal discussed by @novavi and @kriswest.
- Voice agent with FDC3 presented by @SeeWhatsOn.
- @Albert-Herd-LSEG, @Bruno-LSEG, and @openfin-johans presented on legacy migration.
- Videos to be posted within two weeks.
- Discussion on stylisation pattern for UI; @kriswest recommended @SeeWhatsOn start a working group.
-
Classification Field to Refine 'type' for Contexts (Classification field to refine 'type' for contexts #1615)
- Proposal discussed to add a classification (e.g. instrument type) to contexts for further refinement.
- Consensus that while flexibility is beneficial (properties), standardisation (ENUM) may be preferable long-term.
- Use cases recognised by @Bruno-LSEG and @hughtroeger; no objections to progressing.
- @hughtroeger to draft PR.
-
Add Property to Support Analytics Across Apps (Add property to support analytics across apps #1290, PR [WIP] Expand broadcast, raise*, and open methods to include metadata #1595)
- @julianna-ciq summarised PR to expand context metadata, including use cases and documentation improvements.
- @kriswest advised further definition and TSDoc comments, as well as expanding use cases.
- Discussion on enabling custom metadata versus strict standardisation.
- Issue raised regarding missed function
getCurrentContext(). - Discussion on instrument vs instrumentList context types (Question: Strategy for Latest Context between two types:
fdc3.instrumentandfdc3.instrumentListwhile ignoring others #1616):- @Bruno-LSEG recapped the requirements for handling both types.
- @kriswest proposed expanding
addContextListenerand discussed implications. - @julianna-ciq supported a
getAllCurrentContextproposal and volunteered to pursue it. - @Albert-Herd-LSEG and @Bruno-LSEG offered feedback on possible solutions and risks of method proliferation.
-
Context Clearing (Context Clearing #1197, PR Context Clearing #1379)
- Work completed by @kemereva, pending review from editors (notably @novavi).
-
Support Specifying Supported Context When Registering an Intent Listener (Support specifying supported context when registering an intent listener #1545)
- PR by @Roaders is ready, awaiting review and vote.
-
Support the Ability to Specify Where a New App Should Open (Support the ability to specify where I would like a new app to open #1546)
- Not discussed, to be carried over to next meeting.
-
AOB & Adjourn
- Meeting adjourned before final two agenda items were discussed and will be included in the next meeting.
Action Items
- Extend Support specifying supported context when registering an intent listener #1545 with conformance test case definitions (text definition rather than implementation) @Roaders
- Review and vote on PR Support specifying supported context when registering an intent listener #1545 (@robmoffat, @kriswest, @Roaders).
- Editors to review and finalise Context Clearing PR Context Clearing #1379 (@novavi @hughtroeger).
- Progress querying methods for placement options based on OSFF discussions (@Roaders).
- Draft and submit PR for classification field in contexts (Classification field to refine 'type' for contexts #1615) (@hughtroeger).
- Expand context metadata PR [WIP] Expand broadcast, raise*, and open methods to include metadata #1595 as advised, including use cases and documentation (@julianna-ciq).
- Prepare proposal for
getAllCurrentContextor alternative for instrument/instrumentList issue (@julianna-ciq, @Albert-Herd-LSEG, @Bruno-LSEG). - Carry over and discuss Support the ability to specify where I would like a new app to open #1546 (app open location) at next meeting.
Rolled over from the previous meeting:
- @julianna-ciq Raise the destructuring issue.
- @julianna-ciq Implement removal of source maps from output with help from @kziemski.
- @kriswest @Roaders Update documentation for Dates and Date Objects Clarify that Context types are defined in JSON and may be handled differently in specific API bindings #1486.
Untracked attendees
| Full name | Affiliation | GitHub username |
|---|---|---|