Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Standard WG Meeting - Oct 28th, 2021 #481

Closed
2 of 11 tasks
kriswest opened this issue Oct 22, 2021 · 15 comments
Closed
2 of 11 tasks

Standard WG Meeting - Oct 28th, 2021 #481

kriswest opened this issue Oct 22, 2021 · 15 comments
Labels
meeting Standard WG Meeting

Comments

@kriswest
Copy link
Contributor

kriswest commented Oct 22, 2021 •
edited
Loading

Date

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

WebEx info

More ways to join

  • Join by video system:
  • 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

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

Action Items

Untracked attendees

Full name Affiliation GitHub username
@kriswest kriswest mentioned this issue Oct 22, 2021
Closed
@kriswest
Copy link
Contributor Author

🚀 Kris West // Cosaic

@ggeorgievx
Copy link
Member

Present ✅

@mattjamieson
Copy link
Contributor

👋

@copiesofcopies
Copy link
Contributor

Aaron Williamson, FINOS

@agitana
Copy link
Member

agitana commented Oct 28, 2021

Aitana Myohl / FINOS

@pierreneu
Copy link

Pierre Neu, Symphony

@pbaize
Copy link

pbaize commented Oct 28, 2021

Pierre Baize, OpenFin

@jgavronsky
Copy link

Jane Gavronsky @ FINOS here

@Julia-Ritter
Copy link
Contributor

Julia // FINOS

@bertrand-s
Copy link
Contributor

bertrand-s commented Oct 28, 2021 •
edited
Loading

Bertrand Laporte / Symphony

@hughtroeger
Copy link
Contributor

Hugh Troeger, FactSet

@symphony-adnane
Copy link

Adnane T. from Symphony here

@lspiro-Tick42
Copy link

Leslie from Tick42

@kriswest
Copy link
Contributor Author

Minutes posted - please contact me or fdc3-maintainers for any additions or corrections.

This was referenced Oct 29, 2021
Closed
Closed
Open
Open
@kriswest kriswest mentioned this issue Nov 15, 2021
Closed
10 tasks
@Julia-Ritter
Copy link
Contributor

Untracked attendees:

  • Saurabh Gupta / Natwest Markets
  • Andrew Hampshire / UBS

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
meeting Standard WG Meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests