Proposal for the creation of an FDC3 / Interoperability training

[mindthegab]

Given the current uptake in adoption of FDC3, and in order to further grow the awareness / readiness of the industry to adopt and contribute to the standard, now that FINOS is part of the Linux Foundation, we have a large scale training delivery platform we can leverage - which can also integrate with firms learning management systems and learning paths.

FINOS is proposing to build (and fund) a training curriculum for FDC3 and we'd like to validate the idea with the existing Community and leadership. The target audience would be FDC3 application developers and generally technologists who could benefit from the standard.

As some of you might remember, @rikoe had proposed a potential outline for an instructor led course last year, which I'd like to use as a starting point for gathering feedback / validation.

So here's my asks:

1. Add a 👍 or comment to this issue if you support the idea of a FINOS + LF powered FDC3 training program
2. Add comments below to provide feedback on the outline proposed below and / or to include additional topics you'd like to be covered.
3. Let us know if you think a self paced (non instructor led) training would be useful and which topics that would ideally cover.

I would appreciate your comments by the March 12th COB.

Potential FDC3 course (instructor led) outline:

Session 1

• Welcome (10 mins)
• Concepts of Desktop Interoperability and FDC3 (30 mins)
• Q & A (20 mins)

Session 2

• Creating an FDC3 App Directory (10 mins)
• Hands-on coding (40 mins)

Session 3

• FDC3 context sharing (10 mins)
• Hands-on coding (40 mins)

Session 4

• FDC3 intents (10 mins)
• Hands-on coding (30 mins)

Let us know your thoughts!

[lspiro-Tick42]

Gab, I think this is a great idea.

IMO this proposal does not give enough importance to Context data, I think that the focus on Session 3 should be on defining the shared context data types, in particular the types we have defined, the community sharing (defined not used yet) and most importantly how context data can be extended for application or site specific features.

One could then move Context sharing aka channels into the same session as Intents, since you could say that both Channel and Intents are way to move/share a Context from one to others; Channels to all apps listening to the channel and Intents to a single app instance (with the added start and/or bring to front functionality).

I also think that it would be useful to have a session about how to get started, this could cover testing FDC3 apps (Nick's chromium add-in and Glue42 Core are one open source Platforms that allow you to run FDC3 Apps), and how to follow and participate in the FDC3 community,

[kriswest]

I agree with Leslie's points:

• Its a great idea!
• Context data should be more heavily weighted and should be introduced in the same session as intents
  • These are far more heavily used concepts than the App Directory at present.
  • The App Directory spec is also set to receive some significant changes in FDC 2.0 as it's not yet fully fit for purpose and introducing too much fragmentation (relies on vendor-specific manifests).
  • Creating types, sharing them with the community (through the community types initiative we're kicking off) and standardizing your use of channels are topics worthy of an additional session.
• Add more on getting started up-front.
  • Consider introducing the commercial, but freely available commercial containers that implement the standards - these (and fragmentation caused by 3 different proprietary APIs) were the reason for the creation of the standard in the first place.
    • N.B. Using the standard in a native (non-HTML/Javascript) app currently requires you to pick a vendor.
  • es6 style use of the standard in any container supported by the new FDC3 NPM package
  • Cover participation in the FDC3 community and governance

Given we're about to start on the 2.0 standard scope, will be resisting the AppD and launching a community types initiative, I think timing is important. We've opted to not be a focus project this quarter but have indicated interest for next time in the hopes that it can coincide with the aforementioned initiative being up and running. Creating such a program would tie in with this very well.

K

On Wed, 10 Mar 2021 at 07:16, Leslie Spiro @.***> wrote:

Gab, I think this is a great idea.

IMO this proposal does not give enough importance to Context data, I think that the focus on Session 3 should be on defining the shared context data types, in particular the types we have defined, the community sharing (defined not used yet) and most importantly how context data can be extended for application or site specific features.

One could then move Context sharing aka channels into the same session as Intents, since you could say that both Channel and Intents are way to move/share a Context from one to others; Channels to all apps listening to the channel and Intents to a single app instance (with the added start and/or bring to front functionality).

I also think that it would be useful to have a session about how to get started, this could cover testing FDC3 apps (Nick's chromium add-in and Glue42 Core are one open source Platforms that allow you to run FDC3 Apps), and how to follow and participate in the FDC3 community,

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/finos/FDC3/issues/342#issuecomment-795006260, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAM7PBFII3P7WN2NQNFEZI3TC4MGXANCNFSM4Y4N2YVA .

-- Kris West Director of Solutions Engineering [image: Cosaic] +1 (800) 821-8147 @.*** Cosaic.io: https://cosaic.io/ ChartIQ http://cosaic.io/ChartIQ + Finsemble http://cosaic.io/Finsemble Roundtable Event: Next Generation Workflow with FDC3 Guests include NatWest, Charles River, and FactSet March 25th @ 11:00am EDT / 3:00pm GMT REGISTER NOW → https://cosaic.io/webinars/upcoming-webinar/

[michalbelka]

Love the idea! Just similar to others, I think more focus on context sharing would be great.

[sean-ciq]

Echoing all comments above. Especially minimizing the emphasis on App Directory as much work needs to be done to make that part of the standard more robust.

[kerriganb]

Training would be wonderful. I know when i first saw the spec, i then said - ok now what... There doesn't seem to be much information on how to go ahead and create a FDC3 desktop agent. Seems more focused on being FDC3 complaint app - which is fine. But how about.

1. hello world type - compliant app (basic intents, communication)
2. hello world type - desktop agent

I know FDC3 is still young - but any thoughts on adding platform specific topics? (layout, notifications etc?)

Also thoughts on inter - desktop agent communication? (specs seems to brush over this a bit)

[mindthegab]

Thanks everyone for the amazing and timely feedback. Let me see how best we can integrate all this feedback into a consolidated proposal for final review so we can move forward.

[rikoe]

If I summarise the above feedback, would the following seem like a good outline:

• Session 1 Intro to FDC3, including motivation, open source and vendor frameworks and tools, how the FDC3 standard & community works, how to get involved, and where to start
• Session 2 Context data, including using standardised types, defining your own types through composition, and how to share/contribute your types
• Session 3 Intents and context sharing, including how to either raise intents or broadcast data based on application use case, and how to listen to these
• Session 4 Desktop agents and service discovery/orchestration, including the role of the app directory, and how you would go about writing your own desktop agent

Ideally, it would be great to pick an example use case/workflow and carry it through all four sessions

[kerriganb]

I think that would be great. Also maybe a roadmap on notifications as well.

Get Outlookhttps://aka.ms/qtex0l for iOS

---

From: Riko Eksteen @.> Sent: Monday, March 29, 2021 9:56:42 AM To: finos/FDC3 @.> Cc: Kerrigan Burgess @.>; Comment @.> Subject: Re: [finos/FDC3] Proposal for the creation of an FDC3 / Interoperability training (#342)

If I summarise the above feedback, would the following seem like a good outline:

• Session 1 Intro to FDC3, including motivation, open source and vendor frameworks and tools, how the FDC3 standard & community works, how to get involved, and where to start
• Session 2 Context data, including using standardised types, defining your own types through composition, and how to share/contribute your types
• Session 3 Intents and context sharing, including how to either raise intents or broadcast data based on application use case, and how to listen to these
• Session 4 Desktop agents and service discovery/orchestration, including the role of the app directory, and how you would go about writing your own desktop agent

Ideally, it would be great to pick an example use case/workflow and carry it through all four sessions

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://github.com/finos/FDC3/issues/342#issuecomment-809542830, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABNDZQTC2UHZQKB4UJE2B2TTGC5NVANCNFSM4Y4N2YVA.

[rikoe]

I think that would be great. Also maybe a roadmap on notifications as well.

@kerriganb what do you mean by notifications?

[mindthegab]

To close the loop here - thanks to the fantastic input from @rikoe, we are now in the process of building an introductory training for FDC3 which is targeted to be completed by mid Q4. We decided to start with an introductory training and then, based on feedback and uptake, take next steps (e.g. produce an advanced training).

We will keep this issue open (assigning to you @rikoe) and we can close it with the details later in the year when the training is produced.

[rikoe]

Thanks @mindthegab - the current high-level outline is shaping to look as follows (subject to change):

• Introduction to Interoperability
• Introduction to the FDC3 Standard
• Context Data
• Intents and Context Channels
• App Directories
• Desktop Agents and the FDC3 API
• Workflow-driven Design
• The FDC3 Community

Such an online course would be aimed at both technical and business professionals (read: not overly technical), and we believe it is a strong set of content.

Depending on uptake, we could then follow up with a more technical, developer-oriented course that explains how to use FDC3 in detail, with practical exercises.

[agitana]

Thank you @rikoe, @sebmos and @ivanfalanga from Adaptive for developing FDC3: Interoperability for the Financial Desktop (LFS177x)!

Read more about the FDC3 course in this FINOS Blogpost: FDC3 course simplifies learning open standards for financial desktops and join the Adaptive team at the New York FINOS member meeting (today) and OSSF (tomorrow) tomorrow!