Standard WG Meeting - Oct 28th, 2021

[kriswest]

Date

Thursday 28 Oct 2021 - 10am EST / 3pm GMT

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 - Sept 23, 2021 #459
• Other recent activity
  • [Open for review] Proposal for the FDC3 project to adopt the new FINOS Standards Governance model (including the Community Specification License) #412
    • Governance and licensing updates #485
  • [Open for review] Rename 'System Channels' 'User Channels' #430
    • 430 Rename System channels User channels to reflect usage #479
    • Renames getSystemChannels -> getUserChannels (getSystemChannels remains as a deprecated alias)
    • Renames joinChannel -> joinUserChannel (joinChannel remains as a deprecated alias)
  • [Open for review] Introduce a general, host independent, fdc3.general.app.manifest manifest type describing an application #314
    • Update the Application schema #437
  • [Open for review] FDC3 Explained - demo app for beginners? #165
    • Adding a toolbox directory and the FDC3 Explained app #367
  • [Recently merged] Clarify how apps should handle broadcast and receipt of multiple context types #434
    • Clarify broadcast of complex context types #464
  • [Recently merged] Documentation for raise intent only describes the case with a specified app #426
    • Improve the raiseIntent documentation #461
  • [Recently merged] FDC3 Workbench - developer example application #456
    • FDC3 workbench #457
  • [Recently merged] fdc3.joinChannel docs should explain expected behavior on joinChannel #418
    • Clarify existing behavior of joinChannel and addIntentListener when joining a channel #454
  • [Recently merged] Incorrect statement in FDC3 spec regarding fdc3.addContextListener being a no-op when not joined to a channel #448
    • Clarifying behaviour of fdc3.addContextListener when not joined to a channel #449
  • [Recently merged] Strengthen web access statements from SHOULD to MUST #328
    • Upgrading web access statements from SHOULD to MUST in the API specification and FDC3 compliance pages #440
• Create an **implementations** section in the FDC3 website #466
• Support the production of Desktop Agent Bridging #453
• Provide Notification API's #387
• Add save and restore state API calls - so FDC3 apps can fully participate in save and restore layout #386
• Next meeting agenda
  • To include:
    • Proposal for the FDC3 project to adopt the new FINOS Standards Governance model (including the Community Specification License) #412
      • Governance and licensing updates #485
    • Remove App Directory specification, restrict manifest concerns to FDC3 capabilities #468
• AOB & Adjourn (5mins)

Minutes

• Create an **implementations** section in the FDC3 website #466

  • Consensus achieved that we should proceed with this issue
  • Needs PR
  • Offer to help with implementation from @lspiro-Tick42 and @kriswest
  • Review/feedback requested on layout and content proposed (comment on the issue please)

• Support the production of Desktop Agent Bridging #453

  • Consensus achieved for proceeding with further discussion
  • Add to next meeting agenda (multiple firms to present work on this topic for discussion)

• Provide Notification API's #387

  • Divided opinions on whether to proceed with Provide Notification API's #387, with balance of opinion for proceeding
  • Objection to proceeding from one meeting attendee relates to whether the issue falls under the FDC3 Charter
    • opinions expressed for the issue being relevant to the charter (5 participants / firms)
    • opinions against for the issue being relevant to the charter (1 participant / firm).
  • Meeting attendees:
    • expressed the opinion that allowing actions associated with notifications to issue communications to other apps, or raiseIntents for them to be resolved puts this issue within the scope of the charter
    • expressed the opinion that Notifications are core to many user workflows (including between applications and platforms) and hence they warrant standardisation
    • reported that support for standardized notifications API and ability to route those notificaitons into a container was a feature regularly requested by their customers and that the lack of a standardized, cross platform API for doing so made it difficult for them to fulfill that request.
    • pointed out that the 3 commercial container vendors all support a notificaiton API and UI, with differing APIs (which also differ from the web standard), indicating that this issue does need standardisation
  • It was further discussed that standardisation could be handled via:
    • Additions to the Desktop Agent API (implementation would then be the province of the Desktop Agent provider)
    • A standardized intent and context standard (The intent could then be handled by applications registered as supporting that intent)
    • A hybrid approach, where a specific Desktop Agent API is used to submit notifications, but additional functions are also provided for subscribing to the notification data)
  • Consensus achieved that further discussion of this issue is warranted and that specific proposals should be raised for consideration.
    • Please comment on the issue in Github and/or raise proposals for further discussion - once there is further activity on the issue it can be brought back to a future meeting

• Add save and restore state API calls - so FDC3 apps can fully participate in save and restore layout #386

  • Clarified that this issue does not relate to 'windowing' or 'window management' but rather to the communication of application state, encoded as an FDC3 Context, to a Desktop Agent to be included in a saved workspace or layout.
  • Two meeting attendees indicated that their firms have done work in this area, had encountered problems implementing support for it using existing FDC3 concepts (e.g. Channels, which do not identify the source of context broadcasts) and would support further work on the topic
    • One meeting attendee pointed out that even if the technical issues are solved, transmission of state information will still be a proprietary or unstandardized use of FDC3 for a common feature of a desktop container - indicating that some form of standardisation is warranted
  • One meeting attendee objected to the idea of standardization
    • But was willing to reduce or withdraw that objection is this was recorded as an optional part of the standard (not required for compliance, but with a convention defined in the standard record that MAY be provided by an implementation).
  • One meeting attendee indicated that the technical issue are perhaps relevant to discussions at the Channels, Feeds & Transactions discussion group on the topic of 'feeds' or 'transactions' as these concepts have the potential to solve some of the issues

Decisions Made

• Create an **implementations** section in the FDC3 website #466 to be implemented
• Support the production of Desktop Agent Bridging #453 is within the charter and there is consensus that work should be undertaken to achieve it
  • Possible approaches to be presented at next meeting
• Provide Notification API's #387 balance of opinion is that its within charter and there is interest in proceeding
  • Proposals to be raised or further commentary on issue before adding to a future meeting agenda.
  • Can be raised at the Channels, Feeds and Transactions discussion group
• Add save and restore state API calls - so FDC3 apps can fully participate in save and restore layout #386 balance of opinion is that we should proceed with further discussion, but as an optional part of the specification (MAY)
  • Proposals to be raised or further commentary on issue before adding to a future meeting agenda.

Action Items

• next SWG agenda @kriswest
  • Proposal for the FDC3 project to adopt the new FINOS Standards Governance model (including the Community Specification License) #412
    • Governance and licensing updates #485
  • Remove App Directory specification, restrict manifest concerns to FDC3 capabilities #468
  • Support the production of Desktop Agent Bridging #453
• Implement PR for Create an **implementations** section in the FDC3 website #466 @lspiro-Tick42 @kriswest

Untracked attendees

Full name	Affiliation	GitHub username

[kriswest]

🚀 Kris West // Cosaic

[ggeorgievx]

Present ✅

[mattjamieson]

👋

[copiesofcopies]

Aaron Williamson, FINOS

[agitana]

Aitana Myohl / FINOS

[pierreneu]

Pierre Neu, Symphony

[pbaize]

Pierre Baize, OpenFin

[jgavronsky]

Jane Gavronsky @ FINOS here

[Julia-Ritter]

Julia // FINOS

[bertrand-s]

Bertrand Laporte / Symphony

[hughtroeger]

Hugh Troeger, FactSet

[symphony-adnane]

Adnane T. from Symphony here