n/a - no previous meeting

New Participant Intros

• new participants in FDC3 and new attendees to the meeting introduce themselves
  • organization and role
  • why is interoperability important to you / your organization?
  • what do you hope to accomplish with FDC3?

Leslie Spiro, CEO, Tick 42. Working on an enterprise desktop interop for 6 years now. FDC3 offers a great way for us to make our services available in a variety of environments. Interested in the app directory subjects.

Fabien Courdec, CTO, Axioma. Providing optimization performance and content. We're strong believers of data consistency. We see the opportunity to adopt that standard and are interested in intents and content and the API's.

Westpac Sydney, Responsible for workgroup optimization for financial markets. Interested in all to make the applications.

James Wooster, sales and marketing, Tick 42. Interested to see how both organizations can work together to promote the open source venture.

Xiang ye – Namara. We want to integrate Salesforce with the symphony.  Would like to check and see if there is anything we can benefit from here.

Working Group Updates

•  API WG
• App Directory WG
• Context Data WG
• Intents WG
• Use Cases WG

Nicholas Kolba

Espen Overbye

Tim Kolecke

Frank Tarsillo (Deactivated)

Jonathan Teper

• Intros and working group updates are going to be regular parts of this general meeting that happens every 4 weeks.  The we will be adding to the agenda items that people want to put onto this meeting. It could be a proposition, a general topic they want to raise, if it doesn't fit in anywhere else this is the place to do it.
• Currently there are five other working groups within the organization. The chair for each WG will talk about what the group does, what it's done to date, and take any questions. After working group updates there are no further agenda items so it will be open time.

• API WG @Nicholas Kolba:
  • Nick will schedule and post the next meeting date.
• We've had really great participation. Purpose is to define a Common standard set of API's for implementing FDC3 workflow within applications. The API's that what we call a desktop agent would expose to an application to interact with the other parts of FDC3 -broadcast content, raise an intent.
• Within Confluence there is the group page here: https://finosfoundation.atlassian.net/wiki/spaces/FDC3/pages/92963924/API+Working+Group There is also a public page on Github. There is an FDC3 API repository. https://github.com/search?utf8=%E2%9C%93&q=fdc3&type=
• Activities to date: Create a draft specification and then we also created a typescript definition for the API's (contribution by Colin Eberhardt) and you can see the API's here- There is also a source for them. Metadata interface
• Questions: Leslie asked about next meeting, there is nothing scheduled.
• App Directory WG @Frank Tarsillo:
  • we are starting to demonstrate what an app directory is, hoping to have something to demonstrate by the next meeting on the 14^th.
  • Hoping to update the proposal with the data from the schema itself.
• This group is about building and finding an app directory or the FDC3 world. If you go to the WG confluence site the schedule has been updated. We meet fortnightly, the next upcoming  dates are: 6/14; 6/28. FDC3-app-directory@finos.org Go to google groups in finos and request distribution list. Search for the mailing list in the FDC3 area within groups. Put your company name and intention so we know who you are and what you're looking for, this applies to all the working groups.
• Been working through proposals, it's settled how to approach discovery of the app directory server. It's a federated discovery mode and everyone can their own app directories on their own, as long as they have the specifications. The specifications still need to be created.
• We love when people comment, please comment within the pages and show up to the discussions and people will respond. We discussed all of Leslie's comments at the last meetings. We put actions on the particular orders within the proposals, so they can modify the data to clarify the missing points.
• No questions.
• @NK reiterating mailing list information

• Context Data WG @ Tim Kolecke:
  • Tim needs to get access to the mailing list.
  • Confirm first meeting schedule.
• The mission is to manage the taxonomy for FDC3 standard Context Data. The focus is on providing a standard envelope and a standard set of identifiers that can be used to set a lowest common denominator for interop.
• Has yet to meet. Does not have access to the mailing list. Tentatively scheduled meeting for later this week, when confirmed, will be posted to working group on confluence.
• Contact for membership. Tim.Kolecke@citadel.com

• Intents WG @Espen Overbye 
• FDC3 Intents define a standard set of verbs that can be used to put together common cross-application workflows on the financial desktop.
• Meeting 6/14
• There is an initial list of intents to go through
• Discuss intents with contexts, discovery with contents
• Naming – it's going to be visible by the end user
• Check website for information
• Comment from Leslie – there is no invite information on the confluence page for this group.
• Update the invite information for this working group
• (all chairs) Focus on general distribution list, to send invitations, reminders, schedules through that main list for FDC3.

• Use Cases WG @JT
  • Yes, we don't differentiate between internal/external apps. Direct controls are something we will be discussing in the future.
• Just recently formed
• Our intention is to submit proposals and review and provide feedback as much as possible offline, so during the meetings we can have a final review and sign off, rather than discussing cases on the call.
• The goal is to make sure we have set a foundation of use cases and requirements in place defined and validated by people of the program.
• This is the voice of the business we want to represent here.
• Be able to connect the use cases to all of the working groups, a set of standards and implementation.
• Next meeting is June 28, we are looking for participants.
• Setting up google groups. Not up on confluence page yet.
• Add a comment or email for an invitation.
• Question from Leslie: The use case we're most interested in is the enterprise internal applications. Manage discovery and interop between internal applications as well as external applications – would that be a valid use case?

• Intro – what Nick is showing is the open sourcing, the intents – hoping to use as a playground to see what works.
• Blotter, using API to find end point and launch application. Launch blotter app, now launch contacts, click on dial button, it raises an intent to dial the call. Will look for an application in the directory to raise the intent. It's unambiguous, it will resolve to that one dialer application. Two applications that don't know anything about each other working together. The dialer application looks for contact information. The purpose is to put things on the desktop and have meaningful interactions without lateral agreements between them. If there is ambiguity it has to be resolved. Charting app – different colors. Since there was ambiguity, choose what app you want to fulfill the intent.
• An intent was raised, the desktop agents created a resolver to allow the end user to pick the app they wanted, they app was launched and created the context to link the one application to another. An API to allow the application itself to query through the FDC3 directory to fulfill the request.
• Johan question/comment. The resolver has a typo in it.
• Saving them in local storage. Today that is not part of the FDC3 standard.