 Rhaid i chi, rhaid i chi. Fel ydych chi'n gweld a'n gweithio'r fawr o'r rhaid i chi'n gweithio. Rwy'n meddwl yw'n gweithio'r ddefnyddio'r FTC3, ond Robin a Yw Jean byddai i'n bobl o'r drwg o'r ddweud o'r ddweud. Felly am y ddweudio, rwy'n gobeithio'r FTC3, a'r ddechrau i ddweud o'r ddechrau Rhaidio, gan y ddenydd o'r ddechrau o'r ddechrau FTC3 2.0. fel y gallwn yn ystyried i'ch gweithio eich pryd yn ystod, dyna'n ychydig o gyntaf ar y dyfodol yma, ac wrth gwrthodd yma'n ymlaen i chi'n fwy fwy o'r leirau. Felly, ti'n rhaid i'r gennych, rwy'n meddwl ei wneud y ffion FPC 3, ond rwy'n meddwl ei wneud yw'r ddechrau, a'r hynny'n ddim yn rhan. FPC 3 yma eich ystod yn ystod yn y dyfodol, fel yw'r cyfnod, mae'n rhaid i'r pwbl i'ch pryd yn y ddechrau. I don't just mean containers of desktop agents like Lester Eugene gave, but I also mean like messaging buses and other integration tools for dot net frameworks, Java frameworks, et cetera. Anything that is used to enable apps to talk to each other, directly. By the way, FPC3's term for thing that helps apps talk to each other is desktop agent. I think you've heard it a few times but we're going to use it quite a lot. Ac mae'r dystod yn bwysig yng nghymru, a'r FBC3 dystod dystod yn hwn. Y cwysig yn ddod o bobl, y dystod dwi'n ddiddordeb gyda phleson... ... assaultel yn gyfrifol sydd hwn yn yn ôl. Ac mae'r ddiddell yn ddiogel nhw'n ei gallu. Mae'n gweithio cyndi gwleol ac maen nhw'n ddwych chi. Felly, mae'r ddwylog Ogäs epiwyd i'r ddod. Cymreig oherwydd i fforsig. Mae'n dých yn mynd i cwc y bydd angen cwc. whether you're buying one in and using it, or whether you're designing and building it yourself, by using the standard, don't have to reinvent the wheel. I think Matt Barrett from Adaptive spoke about that last year, just how much they're seeing it speed people up and you're not having to have the arguments about how you approach it including the microphone. But just getting on and doing it. So, you can also avoid the vendor lock-ins. Ym argyrchu'n ddechrau a ddaethau. Mae'r ydw i yn ei ddweud, mae'r ddweud yn gofyn arall. Mae'r ddweud yn gofyn arall, mae'r adegau yn gofyn yn gofyn i ddweud, a'r sgwrs rydyn i'r ddafodol ar hyn o'r cyfrifwyr y cyfrifwyr. Mae'r ddweud yn gofyn i'r cyfrifwyr ar gyfer y cyfrifwyr, i'r ddweud ar y ddechrau. Mae hwn o'r cyfrifwyr sy'n gofyn i'r ddweud, i'r ddweud â'r cyfrifwyr. rhai iaith i'r clyw ymlaen a'r ddweud hwn i'r ddweud hwn. Mae hwn yn ddigonol iaith ei wneud allwch chi'n cael ei wneud gan'r ddyliau wahanol, mae'r ddweud hynny yn dweud hynny, mae'n dweud hynny'n rhai wneud, a mae'n dweud hynny'n dweud hynny, mae'n dweud hynny'n dweud hynny'n dweud hynny. Felly mae'n rhaid i'r dweud eto'i ddweud a'r ddweud â'r ddweud hynny, fel o'r ystafell hefyd yn ni, ac mae'n mynd i'n mynd i'r gwybod yma'r ddechrau'r dweud. Felly, mae'n mynd i'n dda i'n meddwl ffrifau'r FDC 3 i chi ei bod yn sgwb ar gyfer gweithio'r reffordd, a fyddwn i'n meddwl reffordd, rydyn ni'n dod o'r rhan i'r digid yng nghymru, wrth gwrs, rydyn ni'n meddwl i'r gweithio'r gweithio. am faf yma o'n cyn draws. Mae'r gwybod yw gysylltu ar gyfer y gweithio a'r sloffer o hwn. Mae'r gwybod yn ffordd i'w gweithio ein bod yn ei chael. Onw ei wneud am fwy rhes weithio ar hyn o'r amser, ac rywch yn helpu ar gyfer ar hyn yn y fuddion o'r cyfrannu, byddai'n gwheithio'r cyfrannu o'r gweithio ffTC3 ac oherwydd argoed o'r dweud. Mae'r ddiwrsreb gyflanzen o'r gweithio, iawn gwag yanhraith dy blread rhai oed yn ymlaen. There's a lot of different people involved. Everyone has to agree, so there are lots of different opinions, there's compromises to be made, etc. And with any design project, anything that you're building for the first time, you're going to learn things about it when you try and use it and you're going to want to end up changing it, refining it, honing it. FDC3 is no different. So, knowing all of this, the FDC3 community has taken a relatively conservative approach to building that standard. And we're pretty conservative about both additions to it and changes to it. We kept the standard simple with a very tight focus on app interop, not every different function that you need in a desktop container to put an app on a desktop. We could have gone there, but it wouldn't have been feasible to try and standardise every possible thing. So it's very tightly focused on just how the applications launch and talk to each other. That's ensured that the creation and the maintenance of the thing is actually feasible. And it has also been a key part, I think, of it succeeding in its main goal, which is delivering that vendor independence in those desktop workflows. The strategy has been successful. I mean, this is not the first of these logo slides you've seen today, and it probably won't be the last. But basically, as the guy showed a minute ago, it's being used across the industry by lots of different people. To start with, it was very heavily focused on the sell side. Organisations had big app development teams, et cetera, that could afford to invest in that interop. But we're working with a number of different buy sides. We're getting really interested in it. Lots of vendors have been popping up the last year. I can see several of you here today. So all of these different groups are starting to work together to actually cooperate to do what they need to do. And as I said, it's making life easier for them doing that. So much so that it's clear that the FTC3 has a strong chance of becoming ubiquitous on a financial services desktop. You will see it on all of them, we hope, in the next year or two. And as I said earlier, all this exciting usage founded on FTC3 strengths revealed a few places where the standard could go further, could be better. And with it rapidly approaching that critical mass where everybody's going to use it, making breaking changes is going to just get harder and harder for us to do. Hence, we needed to seize the opportunity to change things before it got too difficult, which resulted in a 2.0 this year. So before we get into what changed, I'm going to hand you over to Rico, who has been an FTC3 maintainer for a hell of a lot longer than I have, has helped birth this thing and carry it through its first few years while I've picked it up as a teenager and tried to help it along into adulthood. But he's going to tell you a bit more about how we got here and what we needed to do. Hi, everyone. Do I need this mic or can you hear me on this one? That one's good. Okay, cool. I'm going to put it down then, without... Yeah, okay, cool. So, yeah, I'm Rico Eckstein. I am the head of desktop strategy at Adaptive Financial Consulting. I was also the lead maintainer of FTC3 before they fired me. And Chris is now doing a much better job than I could, so it was the right decision. I'm still a maintainer though. I'm still involved. And I love FTC3 and I love being involved. Do you want to go to my next slide? Okay, cool. So, who here loves XKCD? It's one of my favourite webcomics, right? So, I'm going to... Like so many... Well, like almost all innovations, FTC3 started out of problems and frustrations that people had, right? And this is, I think, probably one of the most well-known XKCDs when it comes to standards, right? This idea that, you know, like you notice there's lots of different ways to do things. And, okay, let's standardise it. And now you've got another different way to do something, right? And that's how people tend to think about standards. But FTC3 is trying to be a little bit better than that. And this is my other favourite comic in the context of FTC3, which kind of explains a bit more about the interoperability side of it. And it's called the sandboxing cycle. And it's this idea that, you know, we've got lots of different things that can't talk to each other. Wouldn't it be great if I did the same thing as Chris if they could, right? And then everybody's like, oh, now we've got lots of security issues and bugs, so we need to separate everything. And we've already had questions here today about security, right? So it keeps going around like that, right? But I, in preparing for this talk, I've now found a different XKCD comic, which is now my favourite way to describe FTC3, and it's this one, right? So this is like the universal converter box, right? And this reminds me so much of the finance industry, right? Because we've got the buy side, we've got the sell side, we've got all of the vendors. And everybody is doing things in different ways, right? And what we hear from everyone is we want a universal converter box so that we can bring all of these things together, right? And that is what FTC3 is trying to do. So for the universal converter box, see FTC3 desktop agent, right? Because that's it, okay? So looking a bit at the history, in 2017, Nick Holba from OpenFin, he created and had the vision to start FTC3 as an open way for this type of collaboration to happen. And then in 2018, the Symphony Software Foundation became Finos, and a month after that, OpenFin donated FTC3 to Finos. And it was one of the starting projects of Finos. So we've been sort of part of that from that point. Chris mentioned that I'm part of the furniture. I got involved in 2018 at that point as well when we started forming working groups to create FTC3, right? And when we started FTC3, like there was four separate, well actually five separate working groups. One was for APIs, one was for context data, one was for intents, one was for app directory, and then we also had a use case working group. So these were sort of separate groups working together on separate standards, in a way, for all of those various aspects of interoperability. And if you've used FTC3 and you've wondered about why there's four separate specifications, but there's one standard, that's why. It's purely for that historical reason. And I was involved in shaping the 1.0 release of those four specifications. And in June of 2019, we first realised like, actually this context and intense stuff is actually all related. So people are working across purposes. Let's throw it together. And that's also when we started hearing about people like, we need proper communication channels between applications, and that became a very big part of the scope and roadmap for FTC3 1.1, which was released in 2020. And after that release, there was the further realisation that actually we've got lots of different meetings, lots of different groups, and it's kind of the same people involved in all of them. Let's bring it together into one standard working group. Let's all work together with the same goals, make sure things don't overlap or confuse between different parts. And that's what we did then, and that's when we started working on the next version of FTC3. And we very quickly realised that there were some smaller things and some bigger things that people were asking for and needed. And we needed to tackle the big things, but before we can do that, we should do some of the smaller things that were quick wins, and that's what went into FTC3 1.2, including our NPM package, which was something that I was quite passionate about, that we should have to make it easier for people to adopt, and we released that. And then we started working on FTC3 2.0, and we found out it was really hard, because there was lots of big things, lots of discussion, contradiction, different opinions about how we should do things, and that is when we realised we need to start these discussion groups for different topics in FTC3 to tackle all of them, but then it comes back to the standard working group to make the decisions. And we also started a spec rewrite, which I'll say something about in a moment, Chris will mention it as well, but long story short, we're at the point now where we have the 2.0 draft. There's loads of work. It's by far our biggest release ever, so that's just a bit of where we came from, and I'm going to breeze through these. This is like what went into the previous releases. I've kind of talked about it already, but I think the important thing is, after that first four specifications, we started getting people adopting it and giving us feedback about what they need right from the start. We standardised some types, we made it easier to consume those types, we added channels, and then in FTC3 1.2 we added some new functionality, we had better support for applications in figuring out when FTC3 is ready how to deal with metadata and things like that. I mentioned the NPM package, so I want to stress this is by far not the only way that people consume FTC3. FTC3 is a standard, it's technology-agnostic, you don't have to use JavaScript or NPM or anything like that, but looking at that graph gives me a nice warm fuzzy feeling in my stomach, because it shows people are using it. In May of this year we had 500 people download the package in one day. It's a sign that we're doing something right and that we can continue building it and continue making that graph point upwards. What were people asking us about? What were some of these big things that we had to tackle? Well, they were saying, how can I have intents that return data back? How can I target a particular app instance? What context and intents should I use? There aren't enough. How can I publish my app easily? How can I make it work over across different containers? Lots of people, including Chris and myself, were like, there's lots of ambiguities in the standard. This thing that there were four and now there's one and it's confusing, we need to fix that. People were saying we need to clean up some of the APIs. How can we ensure each desktop agent will work the same? We need more examples and tools. All of these things we were hearing from people and it was daunting to figure out how to cover all of them. That's where the discussion groups came in. I've tried to draw over there how we brought all of these different groups together into one standard working group. If nothing else, it's a great window on how developing a standard works and how dividing and conquering doesn't help in terms of actually getting somewhere. Since version 1.2, we've really focused in on the specific things we've been hearing from people. We had a channels and feeds discussion group. That's in 2.0. Chris will mention more about that. For the up-directory improvements we needed to make, the context data and intents we needed to add, all of these things was what enabled us to get to version 2.0. Over to Chris, who will share more on that. I'm happy to report that through those discussion groups, the standard working group meetings, of which there have been a lot, to all of them, there have been a lot of them this year, we've achieved the roadmap and then some. In fact, it went so well towards the end of the process. One of my colleagues who's been involved with FDC3 since the beginning got in touch to share their feelings about the standard and how we've been doing, the work we've been doing in those meetings. They did so by sending me this image, which is often referred to as the Technology Adoption Life Cycle, or Innovation Diffusion Life Cycle. It illustrates a key challenge for adoption of any technology, which is crossing what they call the credibility gap, or the chasm. The chasm results from basically your mainstream market, not necessarily trusting references from the early market. People have just tried it out. The mainstream market often needs to hear from members of their own cohort who are actually trying out and using things. My colleague marked out FDC3 as having very much crossed that chasm, as evidence throughout this year's work with lots of main market participants coming along to the meetings, working with us, getting engaged with the changes we're making, coming to us outside the meetings and asking questions about when things would be ready. So it's a much larger and more diverse group than was observed during the earlier versions of FDC3, I think it's fair to say. Making now quite an exciting time to be involved in the standard or starting to use it. Right, let's go on to the detail, and I'll rattle through this as quickly as I can. I know a stand between this whole room full of people and lunch, which is a dangerous position to be in. But we'll start with the desktop agent where FDC3 from version one makes it pretty easy to send requests over to other applications to do a thing. You do it by raising an intent, which the desktop agent will resolve. It will send it on to another app. It might be just there's one app available or it might show up a resolver allowing the user to pick an app, but ultimately it will deliver the intent and context over there, and at the same time it's going to send back an intent resolution to your app so you know where it went, that you actually found something and who's dealing with it. It's very effective for triggering actions with context data in other apps, but as you heard from Eugene and Robert earlier, building workflows that involve retrieving data or reference back to the created object is difficult. It's not impossible, but it's difficult. So we needed to create transactions. We needed to be able to request a thing and get something back. So FDC3.2 improves on earlier versions by giving you support for that. It's achieved by allowing that intent handler from our last flow to also return a result. So your application receives back your intent resolution and then you can wait for a result to arrive. That other application is probably not going to send it through straight away. It might be that they need to pop something up for a user to confirm like Symphony might want a human being to look at the message before it gets sent or an order form might pop up pre-filled but human beings got to be in the loop to actually process it. So we've had to design a system where you can get your deferred result back, find out what the order ID was or the reference to the chat room that just got created. If rather than a single response, you needed a stream of them, your app can also return a channel as its result. So on the other side, the desktop agent makes that channel immediately available to the app. Here's what they've sent you back. And then as soon as you connect to it, either side can start streaming messages at the other. So they've got a nice private link between them to exchange some data. It's for, you know, some form of data feed and quite often you need some sort of life cycle support for data feed so you don't necessarily want to start streaming stuff to something until there's somebody listening on the other end. So we had to introduce a new channel type that allowed you to synchronise that feed, start it up, clean it up when the person has gone away so you're not just streaming data at an empty room. It also comes with a requirement that it's a private conversation. Unless the app decides to give that channel out to another application, something else can't break in and start listening to it. Now, enabling real data exchanges mediated by the desktop agent allows FDC3 to tackle loads of new use cases. For example, you can now create real API transactions just on the desktop. So creating an order in an OOS or a new room in a chat app and receiving the details is a useful thing to do. Essentially you can now automate any form of CRUD operation that you need to do from one application to another. You can send it over there, get back the updated details. If you've just updated a record, you can have the updated record back and see it all merged and you can carry on your workflow with that data. You can also create APIs to deliver data feeds such as pricing streams, streams of trades, streams of order details, updates, et cetera, customer activity that can then be handed on to other applications to use. So a use case that's quite close to our hearts at Cosec which also builds chart IQ is plotting stuff on a chart. If it's easier for us to get a stream of trades or a stream of orders, et cetera, they can all be displayed alongside the pricing stream. And we don't necessarily even need to know what other application or what standard it's coming from. Other key changes in the API include making FDC3 aware of individual instances of applications. If you open an app or raise an intent with FDC3, it will now give you a reference to the one that you've opened so you can start targeting it. Again, for example, pricing charts on a sales traders desktop, they're going to have three, four, five at the same thing open. They're working three, four, five different orders. It needs to be able to go to the relevant one without having to pop up a UI for somebody to drive it all the time. We've also added the optional ability for intent and context messages to come with metadata for the app or instance that sent them. As I said, when something resolves an intent for you, you find out who it is, but it's quite nice for those applications to know who's asking them to do something. So you now can have those details as an optional feature, which means, again, they can target new workflows, new messages right at the relevant people. Finally, we've also dealt with a huge amount of cleanup in the FDC3 API, such as standardising on the app ID field rather than the nonunique name field that people ran into some trouble with. We've standardised on acing function calls for consistency and better developer experience. We've got better errors, descriptions of what they should be used for, along with a bunch of other clarifications that people have asked for and how to go about using the API. The channel support has also been improved. We've got a new name for system channels. This is one of those bits that we needed the experience of using it for. I've explained how channels work to dozens of developers, dozens of different companies, and they still want to know why is it called a system channel? I don't understand. So we've renamed it a user channel because it's the user who sets these things. It's just a little bit more intuitive. We got rid of some older things like the global channel that was there for compatibility with FDC3 1.0, and we've added a recommended set of channels as well, which will be important for the future when we're starting to bridge desktop agents together and them having different channel sets, different colours will be a little bit confusing. Moving on to the app directory, we have spent some time reconfirming its role in desktop interop and the FDC3 ecosystem, and doing so has allowed us to get on with significantly refining both the API and the application records it serves. The goal was basically to make it fit for purpose for the next few years for vendors to publish applications out to the rest of the industry, and that's a fairly critical thing for us to have got done when FDC3 is achieving such strong uptake amongst the industry. We're expecting to see a lot more of them soon. At the same time, we trimmed the API calls down to just what really was needed to standardize. More in there than we needed, and we did that on the assumption, on the intention that desktop agents should be connecting to multiple app directories. For example, a search endpoint wasn't necessarily a sensible thing to have if you were going to be searching across lots of different directories, and they all did it in a different way. But we're expecting people to connect to multiple app directories. They're in-house applications, ones they've got from two or three different vendors, perhaps some aggregated by a third party, I know Finos harbors an ambition to host its own directory of FDC3-enabled apps that people will be able to pull from. Finally, we've significantly improved those application records, the things that describe the apps. They now have support for multiple desktop agents, where previously they only really gave you the setup for one of them, or you can go completely without the vendor-specific manifest and use some vendor agnostic launch details that have been added to it with the aim of ensuring that one record really works for everybody. We've better aligned with other standards. For example, the web application manifest, there are other people doing similar things. Web application manifest wasn't right for what we needed to do, but they've done a lot of work there, and we can draw from their best practices. We can even reference a web app manifest now. We have added support for browsing and search use cases. If you've got great big app catalogs powered by app directories, it's nice to be helpful to navigate them with categories or other metadata that just wasn't in our records beforehand. We now support native apps as well. FDC3 has always supported native apps, but you don't always launch a native app with a URL. It can be a path on disk or a protocol handler or various other ways, so we've added lots of things that you need to support those. We can now do localisation and accessibility. You can have translations of the app derecords. They've got lots of free text in them describing an app, so if you deliver it to French, Spanish and Italian clients, you can put it in there. Also, language was really important to accessibility. If something has a name that should be pronounced in a different language, it's important to know what language that is for a screen reader. Screen readers use a pronunciation dictionary. If they try and read French in English, it sounds worse than I do in French. Lastly, and probably my favourite change, is you can now use the app directory to describe how your app actually uses Interop. Now, I've spent time integrating apps for people. They've implemented FDC3, but you have to go and get their documentation, dig through it, assuming they wrote it. If we put that in the records, your developers can just pick that up and go, oh, I need to send that intent with this context. It works. It also means we can build app directory viewers and say, well, this app works with that app, sends that intent and context, and this one receives that one, so you can pick up this application to do what you need to do. Now that it's ready, we're really hoping to see app Ds pop up all over the place across the industry as an easier way for people to deploy the software such that you can pull it down and weld it into a desktop. Now, after the two APIs, context data and intents makes up pretty much the rest of the FDC3 standard. They are what's used to implement specific workflows, basically specific use cases. Anyone can make up an intent name. Anyone can define a context type. However, standardisation of these is what's important. It prevents each firm having to do it themselves, create their own one, and it ensures that the apps are actually interchangeable. So if you've used the same type of somebody else, you know, on either end of the interop, you can then connect to them without having to do that standard, you know, having to do that integration work. So we have created a whole bunch of new workflows, or we've created standard types to support those workflows, to help you do things like visualising data, so you can now provide more detailed configuration to charts. You can find and share research with a view research intent. You can interact with an OMS, you know, view quotes, view orders, and initiate communications with various applications, chat apps, your email clients, et cetera. You can interact with a CRM. You can view somebody's profile, view some interactions, or you can go ahead and initiate those communications as well. They'll log it in the CRM, and they, in turn, will use that intent to pass it on and actually start the chat for you. So the group has also improved the building blocks that are used to create those contexts and intents. So, for example, we've got some context field type conventions. If you're putting dates, currencies, countries in, et cetera, there's a convention for you to follow, so we will do it in the same way. We've expanded the intent name conventions, which helps to promote consistency between the named intents. It makes them a little bit more intuitive for users, so they've got an idea of what's going to happen based on its name. Okay, I'm going to view a chart. It's going to pop up. I'm going to get a price. It's going to send me some data back. We've also created a bunch of new context types for the smaller things, countries, currencies, time ranges, valuations. So they can be used directly or to compose other types. Actually, before I head off this one, we've also got a brand new maintainer who's joined us this year, Vinay. I'm going to pick out and embarrass him in front of here. He's running this group, which is a huge relief to me, but he's going to be our longest-running discussion group. This one's going to keep going between versions of the standard because we can propose types between releases. You can start using them quite happily. So if you're starting to build workflows, come along, either talk to Vinay or our colleagues at Finos, who can invite you along to the meetings, and you can come and access some of the hive mind on how to go about building your context types and intents, how to make them successful, how to make them useful to other people who are going to pick them up. Finally, we ran a Finos-supported project to improve just the standard of the standard. So we're improving the documentation. We had the help of a distinguished consultant editor that Vinos hired in for us, Rex Jesky, who has been involved in numerous standards. I think he edited the C-Shop specification until just this month. He's been doing that for about 17 years. With his help, we finally addressed some of the integration of the separate parts of the FTC3 standard into a single set of documents. We've done some long overdue consolidation of the individual specifications and improved them. It's a lot easier to read, so if you've been in there in 1.0, 1.1, trying to find your way around, hopefully you'll find it a lot easier now. We've better defined all of our terminology. It's backed by glossary, making sure we're being consistent about it. We've clarified compliance requirements for people implementing or using the standard, both the desktop agents and the app vendors. We've de-duplicated the docs. We've crossed this code base that forms the website. We were saying things three or four times, so they're now a lot more dry, easier to maintain, easier to find your way around. We've included formal references to external standards and trademarks and all the other things that you would normally do. We've also better documented our governance procedures so people can find their way around it. We've done a fair bit of work on that governance, which is going to enable us to adopt a new licence for FTC3, the community specification licence, which defines its governance model, which we will be doing pretty much as soon as we get out of the conference. With 2.0 adopted as of the 1st of July, we're now looking ahead to 2.1. We have the actual release to happen 45 days after the adoption, but obviously there's a bit more time after that as people have actually got to implement the standard 2.0. But there is a huge amount of work that's already ongoing for FTC3 2.1, not least of which is the desktop agent bridging that a couple of people have mentioned connecting those whole desktop agents. If you're a vendor with a lot of applications and you're producing a desktop suite, you may want to ship that onto somebody's desktop who may also have their own desktop agent. So the goal of that group is for those two to be able to seamlessly connect to each other, authenticate each other so they know they're allowed to talk, but then for their apps that they manage just to be able to talk to each other without actually knowing anything else that's going on. So it's a job for the desktop agents, hopefully making life easy for anyone using all of the different applications. So if you're interested in that, if you've got a desktop agent implementation, you're going to want to plug into another one, come along and talk to us at the group. We've also got, I've already mentioned, context data and intense group, expanding the lexicon. So this currently meets monthly, but we have some breakout meetings as well as we're working on particular things. So I know at the moment we're working on context types for order, trade, position and instrument. I can pick out some faces here. I know doing some of that work. So we're looking to see hopefully to have those up and available for people to start using in the short term. It doesn't actually have to wait for 2.1, but they will be there. We're also working more intensively for chat, CRM and OMS, EMS interactions, and also just straight Q&A for people who are trying to do this stuff, as I mentioned, come along and talk about what you need to do or what we should be doing for you, what workflows that you need to see standardised, what vendors you need to be able to interchange. There's also a whole range of other issues open. I'm not going to go into them all, but a couple of highlights. People have been talking to us about notification APIs, lots of apps and notifications, and you want to action them, and that might not even be in the app that you sent you the notification. So that's a natural thing for FDC3 to do. As a desktop agent vendor, we also put lots of apps and layouts in the work spaces, and they save this state. That's a key part of apps actually working together being part of the desktop, so we'll be looking at saving and restoring state calls, hopefully. Whether the exposed, originating app identity metadata, finding out where messages came from, was something we were asked for late in the game, but a number of people think it should be required. It's a key part of working with another application, so we'll be looking at that. Lastly, there is conversation just getting going about doing things with identities, both for apps and for individuals. Not just validating logging somebody in, but also passing around a validatable identity for them. So they pass you something to say, I want to place this order, you want to pass it on to another application, you carry that identity with it so that it can be authenticated. So, with that, I'll pass you back to Rico, hopefully he's going to tell you a bit more about how you can get involved. I've been willing Chris on, because I'm very scared of that lady with the big red stop sign coming in and me not being able to do my bit. So, just to make sure you're not scared of this, I'm not going to talk for much longer. We'll all be able to go and have some lunch in a few minutes. This part of the talk is the call to action, right? Getting FTC 3.0 out, context data and intents, I want to call out specifically. At OSFF last year, there was a bunch of us who started talking. I think the guys from RBC, Dom from ISH's market, and a few others of us, and it was like, we need more context data, we need more intents. We started a discussion group, we started talking, everybody started getting together, and now almost all of those things, the use cases that they want in around analytics, things like that, are in this release of the standard, right? So, all of this stuff happens by the community coming together. And now with Vinae from Symphony, taking over with the context data and intents group and really willing that onwards, that just shows how we can gather momentum, how people in the industry can work together. So, there's lots of different ways to get involved. The first and most important way is, use FTC 3. Like what workflows do you have at your organisation that FTC 3.0 can help you deliver, right? You can go to GitHub, everything we do is in the open, our meeting minutes are in the open, like we've got no secrets, we're all about collaboration, everybody in the industry, working together. The quarterly general meeting is on the 2nd of August. If you want to dip your toes in, that's a great place to start. That's usually where people come and show demos, talk about what's going on at a more, like a high level without you being maybe asked to actually do something. So, if you just want to come and find out, that's a great place to do so. Our next standard working group meeting is around the corner, we have those once a month. You know, do come along to that if you're interested. The context and intense discussion group, as Chris explained, will be running probably from now into the future. We need to continue adding those use cases to really leverage the momentum that we've gathered so far. I think on stage today, the community page was called out, this is brand new, we're putting all of the resources together, all of the companies involved together, the example apps, the talks that people did where you can go and find out how to use FTC3. If you go to ftc3.finals.org slash community, go and look through there, the vendors are there, the solution providers are there, the training on FTC3 specifically that Linux Foundation created recently is on there. There's loads of resources. You can be on there as well. If your company is using FTC3 or if you have apps that you want to highlight, if you have workflows you want to advertise, please get in touch with Finals or with the FTC3 maintainer team and we'll gladly add you on there. Or do a PR yourself, even better. I'm going to close on this. I'm going to... Now we're going to practice getting involved with FTC3, right? So you need to go on your phone to... You can use the keyword code or you can just go to menti.com and put in that code over there. And it's going to ask you like three words that you want to put in like what should FTC3 tackle next? I think you'll all agree we there's a whole bunch of stuff that's going into 2.0. Almost that whole list that I had up about what people were asked for, we were able to put into FTC3 and now we need to know what do we need next, right? So I'm slightly ambitious because I've now got to go out of my slide deck and hope that works. So let's see. Oop. Oop. It's no longer there. OK. So I'm going to just exit out of that and see if I can bring it up. I had it earlier. So you just give me a moment. This is going to be interesting. So how do I make me go to menti.com? That one I think. Hopefully we'll do the trick. Right. So has everybody put in some words? You know, I put in some of my own. Right. I put in lunch. Right. That's certainly important. OK. So as you add more things, you'll see all of them showing up there. So I think lunch is looking particularly attractive to everyone right now. And trading is a big one that stands out for me. Data standard for objects. Discoverability. I don't know. Homelessness. If this helps with that. But we can try. Add an API to get intense. Open telemetry. That's an interesting one. Yeah. Containers. Mobile app directory. Cool. I think we'll also use this. You know, we could use this at our next discussion group to think about more things that we can do. Right. And with that, that's the end of our talk. So, yeah. I don't know. Do we still have time for questions? Or are we done? We're done. OK, good. Yeah, no, no. I don't want to either. Thanks, everyone.