Standard WG Meeting - March 27th, 2025 #1548
Description
Date
Thursday 27th March 2025 - 10am (US eastern timezone EDT) / 2pm (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)
- Update on Adoption vote and release
- FDC3 General meeting with overview: General Meeting - March 18th, 2025 #1534
- How do you vote?
- NPM Beta module for testing: https://www.npmjs.com/package/@finos/fdc3/v/2.2.0-beta.3
- Known issue with external channel selectors to be resolved by User channel change issue #1541
- Issue in FDC3 Workbench for DA's that implement 1.2 to be resolved by fix: better support 1.2 DAs by not requiring appMetadata in getInfo responses #1550
- pending PRs to review:
- Help wanted!
- Update issue templates #1554
- Simplify publication of prerelease packages to NPM #1528
- PRs on external forks don't run right in GitHub actions. #1519
- Clarify that Context types are defined in JSON and may be handled differently in specific API bindings #1486
- Define and use standardized language for the conformance tests #1470
- Add an
fdc3.rfqcontext type to handle defining RFQ's over FDC3 #1461 - Use of the Common Domain Model (CDM) in FDC3?
- FDC3 2.2 Conformance Implementation #1455
- Create more FDC3 developer tools #1393
- Question: Documentation or Types for Desktop Agent implementation of App Directory #1382
- Support better identity validation in Preload Desktop Agents #1339
- Standardize the representation of currency pairs by fdc3.instrument #1291
- Merge api/ref/types and api/ref/metadata pages and correct links, including from generated context docs #1282
- Understanding the FDC3 End-User Personas #1173
- Improve OpenAPI (REST) documentation for the website with a docusaurus plugin #1001
- Adopting the Go language binding as @experimental
- Should the desktop agent support both unqualified appIds and fully qualified ones? #1475
- The question of metadata vs. context data and its relevance to current proposals:
- New issues:
- Adjourn
Minutes
- Update on Adoption Vote and Release
- Overview of FDC3 General Meeting held on March 18th, 2025 (General Meeting - March 18th, 2025 #1534)
- Discussion on voting procedure
- Help Wanted
- Assistance needed on various tasks and issues
- Adopting the Go Language Binding as @experimental
- @kemerava gave an overview of the proposed binding and differences from TS
- @kriswest asked for and received consent to merge the proposed Go binding as @experimental
- Should the desktop agent support both unqualified appIds and fully qualified ones? #1475
- Compliance requirement, attempt to match exactly. If it doesn't work, try to qualify or unqualify as appropriate and match then.
- No impact on bridging, but KW will make a comment in the spec on that.
- Should we require DAs to fully-qualify apps? This would be forcing them into breaking changes.
- @robmoffat asked whether people constructing app records shouldn't be advised to make the appId globally unique (uuids, classpath-like names e.g. com.company.app). Some discussion - full-qualification already tries to achieve that via addition of appD domain name.
- @kriswest said this sounds like an alternative proposal, but @robmoffat responded that actually, this should just be a recommendation around appIds.A
- Metadata vs. Context Data Discussion
- Relevant issues:
- Proposal to add properties for supporting analytics across apps (Add property to support analytics across apps #1290)
- Ensuring secure communication with signed and encrypted contexts (Communicating Securely with signed and encrypted contexts #1492)
- @kriswest gave an overview the two proposed methods of passing context metadata (in the context object, or alongside in in the (currently optional) ContextMetadata).
- Lots of those present said it's worth taking the time to getting this right - indicating that the proposal to update the API signatures to accommodate a separate metadata object was preferable to adding metadata to the context object itself.
- @robmoffat said he liked the API changes but was worried about backwards compatibility.
- @kriswest flagged that proposed API overloads might cause issues for the .NET bindings and should be referred to @bingenito for comment.
- Relevant issues:
- New Issues
- A brief introduction to Support changes to the set of User Channels in the Desktop Agent API #1543 and the other new issues was provided
Action Items
- @kriswest to update PR Resolving Fully-qualified and unqualified AppId values #1523 to add a comment in the specification regarding the non-impact of qualified/unqualified AppIds on bridging.
- @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
Rolled over from previous meetings:
- @kriswest implement a PR for No defined behaviour when incorrect arguments are passed to API calls #1490
- @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 |
|---|---|---|