Standard WG Meeting - April 27, 2023

[kriswest]

Date

Thursday 27 April 2023 - 10am EST / 3pm BST

WebEx info

• Meeting Link
  Meeting number: 665 568 411

More ways to join

• Join by video system:
  • Dial 665568411@finos.webex.com
  • You can also dial 173.243.2.68 and enter your meeting number
• Join by phone
  • +1-415-655-0003 US Toll
  • +44-20319-88141 UK Toll
• Access code: 665 568 411

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.

Agenda

• Convene & roll call, review meeting notices (5mins)
• Review action items from the previous meeting (5mins)
  • Standard WG Meeting - March 23, 2023 #934
• Announcements (10mins)
  • FINOS Interoperability and Regtech hackathon
  • FINOS members meeting
  • Recent FDC3 maintenance work
  • FDC3 Workbench 2.0 update (in review)
  • Training and Certification update
• FDC3 2.1 (15mins)
  • PRs ready and/or merged
  • PRs outstanding (opportunities to contribute)
  • Desktop Agent Bridging proposal
  • Context Data & Intents
• Changing the governance of Contexts & Intents (15mins)
  • ...and changing the definition of Context to better handle extension?
• AOB & Adjourn (5mins)

Minutes

• Meeting deck: FDC3 Standards Working Group Meeting - 27th April 2023.pdf
• An overview of progress towards and work remaining to deliver FDC3 2.1 was provided
• FDC3 Desktop Agent Bridging was proposed as a 5th part of the FDC3 standard
  • PR is need of review: 544 Desktop Agent Bridging #968
  • Docs preview: https://deploy-preview-968--fdc3.netlify.app/
  • As this is a large addition to FDC3 an email vote is proposed

Action Items

• @kriswest Open an email vote on the inclusion of Desktop Agent Bridging as part of the FDC3 Standard
• Maintainers to discuss/agree topics for the FINOS members meeting roundtable and talks
  • Overview of Desktop Agent bridging requested + demo
• Context Data & Intents to discuss:
  • governance changes for specific Contexts & Intents (proposal: move to a repository format, rather than standard versions)
  • Changing the definition of the context type to provide an area for extensions to encourage use of the standardized type first, extension of it, then later standardization of the extensions.

Rolled over from previous meetings:

• Question: customConfig vs hostManifests in v2 #900
  • @kriswest or a volunteer to update the issue with the discussion outcome and raise a PR deprecating customConfig
• Proposal to add .NET interfaces and context declarations #931
  • Review of the proposed .NET interfaces by firms that will benefit from them is needed - along with a commitment to help with the update of the FDC3 documentation to include them.
• @kriswest Refer questions about the need for more 'authentication' in FDC3 to FDC3 for Web Browsers group
  • referred but not yet discussed
• @kriswest Raise a PR to resolve AppD v2 routes don't define error response samples #827
  • Add error response samples to appD v2 API routes to make them more obvious in the Swagger spec for appD.
• @kriswest @nkolba @pierreneu to work on proposals/PRs demonstrating possible solutions to Question: App-specific context metadata #829. These should include example use-cases demonstrating the need for and utility of the revision
• @finos/fdc3-maintainers to investigate adding code coverage scanning to repo and to propose a unit testing policy/raise a PR to add to governance and resolve Unit Test Policy #832.
• @kriswest or volunteer: raise PR to resolve Add /intents and /contexts endpoints to the AppD API #719
  • Add optional/recommended API endpoints for /intents and /contexts to the appD API.
• @kriswest or a volunteer, Raise a PR to resolve Are you ready yet? Adding defined (or at least bounded) timeouts to the FDC3 Desktop Agent API #866
  • Add:
    • a recommended maximum time after start-up within which apps SHOULDadd context and intent listeners
    • a required maximum time after start-up within which apps MUST add context and intent listeners
    • statement that Desktop Agents MAY be configured to extend timeouts applied to open or raiseIntent functions.
• @kriswest or volunteer: raise PR to resolve Clarify differences between App and User Channel behaviour (in docs for FDC3 versions 1.1, 1.2, 2.0 and next) #871
• @kriswest or volunteer: raise PR to resolve Clarify handling of malformed context objects by Desktop Agents #872

Untracked attendees

Full name	Affiliation	GitHub username

[novavi]

Derek Novavi / S&P Global

[robmoffat]

Rob / FINOS 🥪

[kriswest]

Kris West / Finsemble 🚀

[hampshan]

Andrew Hampshire @ UBS

[tpina]

Tiago Pina / Finsemble

[psmulovics]

Peter Smulovics / Morgan Stanley

[timjenkel]

Tim / Wellington

[mattjamieson]

Matt / WhiteDog

[openfin-johans]

Johan / OpenFin 🎁

[mistryvinay]

Vinay Mistry / Symphony 🎵

[hughtroeger]

Hugh Troeger / FactSet