Standard WG Meeting - July 23, 2023

[kriswest]

Date

Thursday 27 July 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 previous meeting (5mins)
  • Standard WG Meeting - June 22, 2023 #1013
• Announcements & updates (10 mins)
  • FDC3 Training & Certification progress update
  • @experimental Desktop Agent Bridging addition voted into FDC3 2.1 scope
  • Summary of recent changes and additions to FDC3 2.1 predraft
    • 544 desktop agent bridging proposal mk2 #898
    • Consolidated PR for Context Data & Intents (CD&I) updates for 2.1 #994
    • Order and trade experimental contexts #1021
    • Readme update #1026
    • App Directory schema contains errors #1033
      • Correct issue in appd details field's schema, error in example and improve test #1034
      • 1033 convert appd schema to json #1035
    • AppD schema does a poor job of validating icons and screenshots #1036
      • 1036 correct appd schema for images and screenshots #1037
• Proposal of current scope (and predraft once merges are complete) as FDC3 2.1 (10 mins)
  • See: https://fdc3.finos.org/docs/next/fdc3-standard for current predraft
  • Full scope (see: 2.1 milestone open issues & completed issues):
    • Agent Bridging
      • Question: customConfig vs hostManifests in v2 #900
      • 544 Desktop Agent Bridging #968
    • App Directory:
      • The AppIntent interface incorrectly describes an intent #312
      • Deprecate appD name field and make it optional #820
      • AppD v2 routes don't define error response samples #827
      • Tighter definition for "otherConfig" in fdc3.chart context type #856
      • appD interop.appChannels uses channel name instead of id #980
      • App Directory schema contains errors #1033
      • AppD schema does a poor job of validating icons and screenshots #1036
    • Context & Intents:
      • Intent Proposal: Create Interaction #592
      • Context Proposal: Order #644
      • Standardize a context representing a Trade #655
      • Improve the definition of Instrument context type - add MIC #707
      • 'ChatRoom' and 'SendChatMessage' #765
      • Chat Message Container #766
      • 'View Chat' intent #767
      • 'View Messages' intent #768
      • Context Proposal: TransactionResult #771
      • fdc3.ChatInitSettings is missing id and type is incorrectly defined #852 & Question: Should ChatInitSettings options have a exported interface #855
    • API
      • Are you ready yet? Adding defined (or at least bounded) timeouts to the FDC3 Desktop Agent API #866
      • Clarify handling of malformed context objects by Desktop Agents #872
      • API types use String rather than string #915
      • Clarify expected behaviour of IntentResolution.getResult() when IntentHandlers resolve to void #1003
    • Docs
      • Clarify differences between App and User Channel behaviour (in docs for FDC3 versions 1.1, 1.2, 2.0 and next) #871
      • Markdown linting and spell checking documentation #1002
• Call for participation in FDC3 Security Threats & Identity discussion group (5 mins)
• Call for proposal of new FDC3 maintainers to support: (5 mins)
  • Multiple Language Bindings #990
  • FDC3 Security Threats & Identity discussion group
• FDC3 Chrome Extensions in need of maintainers or retirement (short)
• Update the FDC3 Charter document #1023 (short)
• Multiple Language Bindings #990 (remaining time)
• Adjourn

Minutes

• Order and trade experimental contexts #1021
  • Consent was requested and received to merge this PR into the current predraft of FDC3 2.1 once it passes review
    • 2 minor issues were noted in the documentation of the Product type that should be corrected first
• Consent was requested and received for opening a vote on the adoption of the proposed scope as FDC3 2.1
  • Vote to be opened after the above merge is completed
  • Vote to remain open for a number of weeks in respect of holidays over August
• A brief discussion was held on the proposed FDC3 Security Threats & Identity discussion group
  • Yannick Malins @ Symphony has been put forward as a potential new maintainer to organize and run this group - formal proposal is expected at the September SWG meeting
  • We need to recruit participants with expertise in auth and security
  • @kriswest to meet with Yannick later in August to go over meeting organization etc.. and then to help issue a call for participation.
  • Group expected to meet from September onwards.
• The desire to recruit new maintainers was discussed
  • Multiple Language Bindings #990
    • @kriswest requested that @Julia-Ritter raise this with @bingenito and @timjenkel as they have been closely involved with drafting .NET and Java FDC3 bindings.
  • Other participants were asked to consider other candidates to put forward - the maintainers are currently working with two candidates.
• The FDC3 Chrome extension was briefly discussed - it's is in need of new maintainers or retirement.
  • @kriswest to issue an email notice about this to the community.
  • @hughtroeger to raise a PR to remove mention of it from the FDC3 website if it ends up being retired.
• The FDC3 Charter document was discussed
  • The current document (+ the copy of it in the root for the FDC3 repo SCOPE.md do a poor job of actually explaining FDC3's scope - although the SCOPE.md does actually include a key sentence from the FDC3 introduction.
  • The was consensus that it is time tup update the document(s)
  • There is no convention for charter documents on FINOS projects for us to follow - SCOPE.md is from the Community Specification License, but just says that you need to provide a description of the scope of the working group/standard (here).
  • It was proposed that @kriswest draft a revised document defining the current scope as understood by the FDC3 maintainers and that this is then discussed at a future meeting and any amendments to the scope proposed on that draft and agreed by the SWG
• Discussion of Multiple Language Bindings #990 was deferred (other than the discussion of recruitment of new maintainers) but should resume at the September meeting - with key participants invited.

Action Items

• @finos/fdc3-maintainers and @finos/fdc3-editors to complete review of Order and trade experimental contexts #1021 and merge
• @kriswest to open a vote on the adoption of FDC3 2.1 based on current scope
• @kriswest to meet with @Yannick-Symphony to cover meeting organisation
• @kriswest to send email notice about the need for new maintainers of https://github.com/finos/fdc3-desktop-agent or its retirement
• @Julia-Ritter to contact @bingenito and @timjenkel about the need for additional maintainers to look at Multiple Language Bindings #990 and indicate that the September SWG is when this will next be discussed.
• @kriswest September SWG meeting agenda to include:
  • Multiple Language Bindings #990
  • Proposal For Identity Discussion Group / Work Stream #684
  • Update the FDC3 Charter document #1023

Untracked attendees

Full name	Affiliation	GitHub username

[kriswest]

Kris West / Interop.io 🚀

[mattjamieson]

Matt / WhiteDog 🌉

[mistryvinay]

Vinay Mistry / Symphony 🎵

[hughtroeger]

Hugh Troeger / FactSet