Standard WG Meeting - July 28th, 2022

[kriswest]

Date

Thursday 28th July 2022 - 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 23rd, 2022 #757
• Maintainers update (5 mins)
  • FDC3 2.0 release progress and timeline
    • https://github.com/finos/FDC3/milestones
    • 484 compliance info #753
  • Adoption of Community Specification License
    • (WIP) 412 Community spec license adoption #775
  • FDC3 Workbench update plans
    • FDC3 workbench: add support for app channels #785
    • FDC3 Workbench: Fix minor issues and improve design #786
    • FDC3 Workbench: Create a separate version of Workbench for FDC3 2.0 #787
    • FDC3 Workbench: Add Support for FDC3 2.0 features #788
  • FDC3 Conformance Framework
    FDC3 Software Conformance Framework #583
• Discussion groups update (10 mins)
  • Desktop Agent Bridging
    • [WIP] 544 desktop agent bridging proposal #634
  • Context & Intents
    • 'ChatRoom' and 'SendChatMessage' #765
    • Chat Message Container #766
    • 'View Chat' intent #767
    • 'View Messages' intent #768
    • Intent Proposal: Create Interaction #592
    • Context Proposal: TransactionResult #771
    • Context Proposal: Order #644
    • Standardize a context representing a Trade #655
    • Improve the definition of the Position context type #656
    • Provide Notification API's #387
    • Release Frequency
  • AppD discussion group (some outstanding issues from App Directory Discussion group - Monday 16th May 2022 #718)
• FDC3 2.1 scope discussion (30 mins)
  • Open issues:
    • Project infrastructure
      • Proposal for the FDC3 project to adopt the new FINOS Standards Governance model (including the Community Specification License) #412
      • Update FDC3 master branch to main #579
      • Update microsite to docusaurus v2 #762
      • Ensure types are generated when new contexts are merged into master branch #749
    • AppD issues:
      • The AppIntent interface incorrectly describes an intent #312
      • Provide better documentation and examples for AppD auth support #559
      • Revive and update or replace AppD reference implementation #563
      • Add vendor agnostic default window size and position settings to the App Directory app definition format #564
      • 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
    • API issues:
      • Reset context  #301
      • Allow Desktop Agent To Join Multiple Channels #242
      • Introduce a new fdc3.applications() method #311
      • Add save and restore state API calls - so FDC3 apps can fully participate in save and restore layout #386
      • Provide Notification API's #387
      • Upgrade exposure of originating app identity to a requirement (MUST) from recommended (SHOULD) #735
    • Context & Intents issues
      • See discussion group update above
    • Proposal For Identity Discussion Group / Work Stream #684
• AOB & Adjourn (5mins)

Minutes

• Discussion groups:
  • AppD: There was no consensus that the appD discussion group should be revived to deal with the remaining issues, hence these will be dealt with through SWG meetings.
  • Desktop Agent bridging: the group is closing in on a first complete draft which may be ready to share at one of the next couple of SWG meetings
  • The Context & Intents group remains active and will continue to manage its own scope and bring back a batch or batches of issues for inclusion in the next FDC3 draft.
    • The group is still seeking a way to release its work faster (than the typical cadence for FDC3 releases, which is about once a year) - API changes etc. are not needed for new Contexts & Intents to go into use.
      • FDC3 maintainers to discuss options for a solution:
        • Introduce a third tier to version numbers for Context & Intents releases and do them quarterly?
        • Release an updated NPM module on merges to trunk (version: "next")
        • Separate versioning on Intents and Contexts from the API standards (Desktop Agent and AppD).
• FDC3 2.1 scope discussion
  • Context & Intents issues to stay with that group until ready
  • Desktop Agent Bridging issues to stay with that group until ready
  • Project infrastructure issues to be handled by maintainers - volunteers to assist most welcome!
  • All other open issues were briefly reviewed - most warrant further discussion.
  • Rough ordering by interest expressed in discussion by meeting participants:
    • Add /intents and /contexts endpoints to the AppD API #719
    • Provide Notification API's #387
      • @kriswest believes this could be dealt with through Intents & Contexts + FDC3 2.0's ability to return results from intents and suggested that brief PoC is sketched out for discussion at a future meeting.
    • The AppIntent interface incorrectly describes an intent #312
    • Allow an AppD application record to reference other apps that are *required* for it to run #674
    • Allow Desktop Agent To Join Multiple Channels #242
    • Reset context  #301
    • Provide better documentation and examples for AppD auth support #559
    • Revive and update or replace AppD reference implementation #563
    • Upgrade exposure of originating app identity to a requirement (MUST) from recommended (SHOULD) #735
    • Add save and restore state API calls - so FDC3 apps can fully participate in save and restore layout #386
    • Introduce a new fdc3.applications() method #311
    • Add vendor agnostic default window size and position settings to the App Directory app definition format #564
  • The end of the meeting curtailed discussion before we reached:
    • Proposal For Identity Discussion Group / Work Stream #684
• All were invited to raise new issues for issues they would like to see discussed and/or addressed in a future FDC3 version.

Action Items

• @hampshan Review appD 2.0 record properties and raise an issue to add a link to an app's help documentation (if the moreInfo link is not sufficient). This might be used, for example, to add a help link to window chrome in a desktop agent.
• @kriswest Plan agendas for future SWG meetings
  • base the plan on a queue of issues that we can maintain, ordered using the input given at this meeting
• @robmoffat further the discussion of Proposal For Identity Discussion Group / Work Stream #684 outside of SWG meetings - then request adding to an agenda when ready.

Untracked attendees

Full name	Affiliation	GitHub username

[bingenito]

Brian Ingenito / Morgan Stanley
👋

[milindchidrawar]

Milind Chidrawar / Singletrack

[Julia-Ritter]

Julia / FINOS

[pierreneu]

Pierre Neu / Symphony

[jgavronsky]

Jane / FINOS

[mistryvinay]

Vinay / Symphony

[ggeorgievx]

Georgi / Tick42

[kriswest]

Kris / Cosaic

[hampshan]

Andrew Hampshire @ UBS

[Qiana-Citi]

Qiana / Citi

[tpina]

Tiago Pina / Cosaic

[hughtroeger]

Hugh Troeger / FactSet

[rikoe]

Riko Eksteen / Adaptive

[kriswest]

Minutes for yesterday's meeting have now been posted.

Please do raise issues or (github) discussions for anything you'd like to see discussed at future meetings!

[Qiana-Citi]

Thanks Kris. Will take a careful look. From: [github.com] Kris West ***@***.***> Sent: Saturday, July 30, 2022 1:00 AM To: finos/FDC3 Cc: Chen, Qia Qiana [ICG-IT]; Comment Subject: Re: [finos/FDC3] Standard WG Meeting - July 28th, 2022 (Issue #784) This Message is From an External Sender This message came from outside of your organization. Minutes for yesterday's meeting have now been posted. Please do raise issues or (github) discussions for anything you'd like to see discussed at future meetings! — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/finos/FDC3/issues/784*issuecomment-1199751649__;Iw!!Jkho33Y!gjqIeM4z9SuDytDTJsAVnC_L7Bv1TaVsfEIuyZKYuT1r5sXvls-gBjJjSTeS1F69cjPQ0HA5ImP4x_RL0EWydllqlAU$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AVCUVSPGSHC3E3N4PDCVQHDVWQEXFANCNFSM544XFGKA__;!!Jkho33Y!gjqIeM4z9SuDytDTJsAVnC_L7Bv1TaVsfEIuyZKYuT1r5sXvls-gBjJjSTeS1F69cjPQ0HA5ImP4x_RL0EWyMxIu-oU$>. You are receiving this because you commented.Message ID: ***@***.***>