Standard WG Meeting - May 26, 2022

[kriswest]

Date

Thursday 26th May 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 - April 28, 2022 #683
• Report on formal specification project and outstanding work (5mins)
  • Compliance #484
  • Provide details about support for optional API features in ImplementationMetadata #636
• Review PRs for inclusion in FDC3 2.0 (40mins)
  • AppD consolidated update PR #668
    • Resolves issues:
      • Add categories metadata to AppD application definitions #369
      • Improve the AppD's search function and documentation #370
      • 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
      • Correct "trusted identity" statements in AppD overview, consider whether app authentication properties are needed #558
      • 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
      • 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
      • Add language metadata to AppD for accessibility #622
    • Preview links:
      • AppD Overview
      • API introduction
      • Full OpenAPI specification
  • Context Data and Intents consolidated update PR #724
    • Resolves issues:
      • StartChat and SendChatMessage #574
      • Intent Proposal: ViewResearch #587
      • Intent Proposal: ViewOrders #588
      • Intent Proposal: ViewInteractions #589
      • Intent Proposal: StartEmail #590
      • Intent Proposal: View Profile #600
      • How to submit a new intent #624
      • Standardize recommended formats for 'primitive' Context fields #645
      • Standardize a context type representing a range of time: TimeRange #646
      • Standardize a context type representing a Currency #651
      • Standardize a context type representing a Valuation #652
      • Standardize a context type representing a Chart #654
      • Intent naming conventions #681
    • Preview links:
      • Intents Overview
        • Intent naming conventions
      • Context Overview
        • Field type conventions
      • New intents
        • StartChat
        • ViewHoldings
        • ViewInteractions
        • ViewOrders
        • ViewProfile
        • ViewResearch
      • New contexts:
        • Chart
        • ChatInitSettings
        • Currency
        • TimeRange
        • Valuation
  • 506 deprecate name field in API calls #722
    • Preview links:
      • New AppIdentifier type used for target parameters
      • AppMetadata extends AppIdentifier and is used for returns
      • open, raiseIntent & raiseIntentForContext updated signatures
      • Deprecated versions of open, raiseIntent & raiseIntentForContext
  • 520 expose originating app identity #725
    • Preview links:
      • New ContextMetadata type
      • Updated ContextHandler and IntentHandler types
      • Comments about optional exposure of originating app metadata on raised intents and on channels
  • 603 Allow an App to retrieve its own metadata through getInfo() #726
    • Preview links:
      • Updated ImplementationMetadata type
      • Updated detail in overview
  • 717 Add a recommended set of user channels to the Standard #727
    • Preview link
    • Typescript export
  • 247 appd use of interop #731
    • Preview Link
• FINOS - Open Source in Finance Forum London
• AOB & Adjourn (5mins)

Minutes

• Compliance #484 & Provide details about support for optional API features in ImplementationMetadata #636
  • Approved to raise and merge PR prior to next meeting, with changes as described in the issues
• AppD consolidated update PR #668
  • Approved to merge (silent consensus)
• Context Data and Intents consolidated update PR #724
  • Approved to merge (silent consensus)
• 506 deprecate name field in API calls #722
  • Approved to merge (silent consensus)
• 520 expose originating app identity #725
  • @nkolba suggested a number of changes, including:
    • Upgrading from a recommended, but optional feature (SHOULD) to required (MUST)
      • @kriswest proposed that we do this and open an email vote to include the revised PR - this proposal was superseded by a later one
    • Switch from AppMetadata to AppIdentifier for reasons of developer ergonomics and to avoid variation in implementations based on what fields Desktop Agents choose to return in AppMetadata
      • Requires the additional of a further API call to retrieve AppMetadata for an AppIdentifier
      • @kriswest pointed out that this is inconsistent with the rest of the API and that this could also result in variations
    • @kriswest proposed that we apply the experimental label to this feature (in the ContextMetadata type introduced to handle this metadata), merge it and seek to refine it in a new issue
      • @nkolba offered to raise the issue
  • Approved to merge (silent consensus) - after application of the experimental label
• 603 Allow an App to retrieve its own metadata through getInfo() #726
  • Approved to merge (silent consensus)
• 717 Add a recommended set of user channels to the Standard #727
  • A query was raised about whether an expert on color and UIs for the colorblind had been or could be consulted on the chosen colors
    • @kriswest explained how the colors were chosen, aiming for as much contrast as possible ( although this is challenging with a set of 8) and that our primary mechanism for supporting the colorblind is the use of the glyphs included in the display metadata
  • A query was raised about using HEX colors
    • @kriswest clarified that the keywords are from CSS3 and do imply specific hex values, also that it was requested that we use keywords to allow some small variation where it is deemed necessary, with goal being that it is still recognized as the same color.
  • @kriswest demonstrated the updated channel ids, to which namespacing was added to avoid collision with existing channels, on a suggestion from @openfin-johans
  • @lspiro-Tick42 suggested that we also consider a standard mapping to Bloomberg and Eikon channels
    • @kriswest acknowledged the value of doing so, but requested that this be raised as a separate issue
  • Approved to merge (silent consensus)
• 247 appd use of interop #731
  • @kriswest provided an overview of the PR and clarified the use cases (find apps to interop with in an appD browser, document FDC3 interface to an app for developers) and that the all additional metadata (other than intents listened for) is optional
  • The end of the meeting curtailed discussion and consensus checking.
  • @kriswest to summarize issue via email and request approval to merge

Action Items

• @finos/fdc3-maintainers & @finos/fdc3-editors to complete review tasks and merge approved PRs into FDC3 2.0 pre-draft.
• @kriswest apply the experimental label to 520 expose originating app identity #725 prior to merging
• @nkolba raise an issue to discuss refining 520 expose originating app identity #725 and introducing an API call to retrieve AppMetadata for an AppIdentifier
• @lspiro-Tick42 & @ggeorgievx raise an issue to consider how the recommended channel list can be mapped to Bloomberg and Eikon channel lists
• @kriswest summarize 247 appd use of interop #731 and open a vote via email for inclusion in the FDC3 2.0 predraft.

Untracked attendees

Full name	Affiliation	GitHub username

[kriswest]

Kris West / Cosaic

[mistryvinay]

Vinay / Symphony

[pauldyson]

Paul Dyson / Singletrack

[timjenkel]

Tim / Wellington

[robmoffat]

Rob / FINOS

[Julia-Ritter]

Julia / FINOS

[jgavronsky]

Jane / FINOS

[RandallDang-Citi]

Randall Dang / Citi

[ggeorgievx]

Georgi / Tick42

[lspiro-Tick42]

Leslie / Glue42

[milindchidrawar]

Milind Chidrawar / Singletrack

[sarahaislinnstone]

Sarah Stone / Cosaic

[openfin-johans]

Johan / OpenFin

[mattjamieson]

👋

[hughtroeger]

Hugh Troeger / FactSet

[Qiana-Citi]

Qiana / Citi