App Directory Discussion group - Feb 08, 2022

[kriswest]

Group overview

Discussion group to develop proposals for the improvement of the App Directory as part of the FDC3 standard. The group will examine the role/value/necessity of the AppD as part of the FDC3 specification and a compliance requirement for use of the FDC3 API, in addition to working on proposals to improve the description and functionality of the App Directory.

Relevant tags

Current open issues and PRs that relate to the above concepts with the label:

Meeting Date

Tuesday 8th Feb 2022 - 9am EST / 2pm GMT

WebEx info

• Meeting Link
  Meeting number: 2559 815 9161
  Password: JHw9MQbbD35

More ways to join

• Join by video system:
  • Dial 25598159161@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: 2559 815 9161

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.

• A Discussion Group has no direct decision-making power regarding the FDC3 standard - rather it is intended that anything they propose or work on will result in proposals (via Github issues and PRs) for the Standards Working Group participants to consider and vote on for inclusion in the standard. As such, participation in a Discussion group is not required for contributing to any particular issue or FDC 2.0 as a whole.

Agenda

• Convene & roll call, review meeting notices (5mins)
• Review issues list and discuss group goals (15mins)
  • All open AppD issues can be found at: https://github.com/finos/FDC3/issues?q=is%3Aissue+is%3Aopen+label%3Aapp-directory
    • Recently merged:
      • Introduce a general, host independent, fdc3.general.app.manifest manifest type describing an application #314
        • Update the Application schema #437
    • Existing issues:
      • Extend AppD application definition to support describing an app's use of interop (App Channels, User Channels & Intents) #247
      • Add categories metadata to AppD application definitions #369
      • Improve the AppD's search function and documentation #370
      • Extend AppD application definition to support describing app channels and their purpose #371
    • Recently raised:
      • Support any App Definition so long has it has an 'fdc3' property #550
      • Remove the Application Directory from The FDC3 Specification #551
      • Add backwards compatibility support for the App Directory #553
      • Improve the description of AppD, its role and value. #555
      • Better describe relationship between AppD definitions and other manifests #556
      • Add pagination support to AppD APIs #557
      • Correct "trusted identity" statements in AppD overview, consider whether app authentication properties are needed #558
      • Provide better documentation and examples for AppD auth support #559
      • Define a term in the FDC3 glossary that can be used to refer to the application definition format used by the App Directory #560
      • Better align Application definition to Web Application Manifest and supplementary application information #561
      • Add vendor-agnostic properties to the AppD application definition format for launching native apps #562
      • Create an AppD reference implementation #563
      • Add vendor agnostic default window size and position settings to the App Directory app definition format #564
      • Make it possible to retrieve all applications in an AppD #565
      • Endpoints for adding an app to an appD will often be implementation dependent and should not be required for compliance #566
      • Add details of where to get more details about an app and where to create an account #567
• Examine role/value/necessity of the AppD as part of the FDC3 specification and a compliance requirement for use of the FDC3 API (35mins)
• Arrange next meeting & Adjourn (5mins)

Minutes

• Discussion was entirely focused on
  • Remove the Application Directory from The FDC3 Specification #551
  • Discussion was contentious and unproductive.

Action Items

• None recorded

Untracked attendees

Full name	Affiliation	GitHub username

[kriswest]

Poll for first meeting appointment (expected to repeat fortnightly):

• 😄 Fri 4th Feb 3pm GMT / 10am ET
• 🎉 Mon 7th Feb 4pm GMT / 10am ET
• ❤️ Tues 8th Feb 2pm GMT / 9am ET
• 🚀 Wed 9th Feb 2pm GMT / 9am ET
• 👀 Fri 11th Feb 3pm GMT / 10am ET
• 👎 none of these work for me

[Poll closed: Tues 8th Feb 2pm GMT / 9am ET]

[Julia-Ritter]

Julia / FINOS

[ggeorgievx]

Present ✅

[kriswest]

Kris / Cosaic

[bertrand-s]

Bertrand / Symphony

[openfin-gavin]

Gavin / OpenFin

[sarahaislinnstone]

Sarah Stone / Cosaic

[mazydar]

Mazy | OpenFin

[thorsent]

Terry Thorsen / Cosaic

[ferguskeenan]

Fergus / Adaptive

[pbaize]

Pierre / OpenFin

[hughtroeger]

Hugh Troeger / FactSet

[openfin-johans]

Johan / OpenFin 🎁

[opoupeney]

Olivier Poupeney / Symphony

[jgavronsky]

Jane @ FINOS here

[pgn-vole]

Yacine Zalouani @ UBS