 That's just mean. OK. OK, we'll tell you what. Why don't we go ahead and get started? It's unusual. We don't have the usual people or the people who are here from the last interop event. So we may not be able to make as good progress, but we'll see. So basically, I assume you guys can see my screen, right? Correct. Yes, OK, good. So basically, what I want to do is just to start some discussions around. Oops. Sorry. I'm going to hit the wrong spot. Just want to start a quick discussion around ideas for what we can do around the interop event. And just to refresh people's memory, for those of you who weren't part of last time, I'm trying to remember what we did. So last time, what we did was we had a event producer. Because I think we have more than one event producer, maybe. Generating events related to an image being uploaded into a data scale. And people then took that event that had, I believe, the URL to image. They then processed the image in some way. Some people did some sort of image analysis. Other people modified the image in some funny way. And then they ended up posting their results to that processing through Twitter. So for example, in the IBM case, we analyzed the image configuration of what was in it. And then we posted to Twitter a picture of the image itself along with what Watson thought it was. So I think we did that kind of image analysis. Other people, I think, for example, red hats might have modified the image in some funny way. And then posted that to Twitter. And so it was just an interesting way to show that, yes, everybody could receive a cloud event, process it correctly, and then do something fun with this image that they got. And so that was a very simple little demo. So this time around, I think we're just basically looking to do some sort of again, some sort of interop proving that we could all receive or possibly send cloud events. And it's going to be done in some interop fashion. So let me pause there. Has anybody had a chance to think about what they thought might be a good demo, either from a straight technical perspective in terms of this would be a really neat thing to demonstrate around cloud events or something that just think would be a good presentation type demo, to have a big wow factor kind of a thing? Has anybody given any real thoughts to this yet? I'll take a stab. So I think it'd be nice if you could show different transports being involved. Yeah, so my understanding of all of this is that I should be able to maybe take something over HTTP and then pass it on over NETs or something like that and show that stuff can move around across different transports without loss of data as well. I like that. That's a good idea. Especially since we have more than one transport spec, that'd be a really good idea. I like that. All right, any other ideas? Okay, what about the application itself? Has anybody given any thoughts of that? Part of me was trying to figure out is there's some way to leverage what we did before, meaning some of those image analysis type things or something completely different and completely wide open here. Obviously, there were some ideas that were mentioned in this 246 issue. Anybody had a chance to take a look at those and see if any of those looked interesting? I like your telephone one in a way. The first one that's listed. I haven't looked at any of the others, I have to say, but that first one looks interesting. But that might, I'm not sure if there's more work involved in that one. I don't know. Yeah, this one I thought was kind of interesting. What might be really interesting about that one is especially if it involves multiple transports, because let me show you something. I had an intern just do a quick mock-up, right? So from a graphical perspective, we could show the cloud event traversing through all the different platforms that want to be in there. And each one of these links could technically be a different transport, right? So we could in some way have it recognized what kind of transport is being used and display it in there. We'd also talk about how each one may be added or modified or property in there so we could have it have the dashboard, you know, recognize what properties were modified. So from a graphical perspective, I thought this was kind of interesting. I just wasn't sure whether it would make sense to also incorporate the image processing thing. So for example, perhaps, rather than sitting in the results of Twitter, there could be something displayed next to each one of these icons with the output of what would have been shown to Twitter, right? So for example, a picture of the image that was modified or the text that says, I think it's a dog, right, that kind of thing. So I think there could be lots of things we could do here in this kind of graphical thing, showing the interoperability between the various platforms involved. I don't know. Yeah, I mean, I'd like the, I watched the demo or the playback of the last demo you did and I think you got good audience engagement by having that sort of image processing and you know, almost sort of a random thing going on there. I don't wonder how you could, how you engage them, how you engage the crowd. Yeah, so that demo itself in terms of being in the crowd of Austin was up there on stage and it was a really, really nice job. He basically went through and I guess, I'm trying to remember, I think he initiated the generation of a new image being uploaded into the data store. And then he basically just switched over to Twitter to see the outputs, right? Yeah, I'm wondering if you can do, a lot of this depends on what capabilities are in those clouds but I mean, you could maybe do something along the lines of that telephone game where you send a phrase and then it keeps being translated into different languages and then eventually turns it back into the source language again. Almost like a game of Chinese whispers. So, you know, if I went from English to French to Spanish to Portuguese and back to English, would I end up with the same sentence again or would I have something comically interpretive? Yeah. I like that, that's a nice idea too. You're full of good ones today, I like this. It's probably what I'm gonna say. What's that? Actually, this is fine. I had assumed from reading the telephone one, which I like the best that I had assumed what was just described was what you were considering and I agree, I kind of like it as well. Okay. Yeah, actually to be honest, when I wrote that one up, I was just thinking of looking at the various properties and make sure that nothing gets lost and as it moves through it, right? To ensure that each one doesn't just add new properties, but also acts as a proper gateway and doesn't drop anything. But that's, I like this idea. Well, I think you can do both, yeah, because you can sort of accumulate that history of translation as you go. So, at the end, and I'm not sure how you would make sure that the last guy actually turned it back into, you know, the original target language, but you've got that audit trail of all the steps you went through and maybe that's what, which is similar to what you had, you know, in that initial description. Yeah, that's interesting. Yeah, you're right though. We would have to make sure that the last guy translated back to the original language, you know, English, we assume that's English. But I'm sure we could probably figure out some way to do that because obviously the dashboard could be told which one can handle, you know, which one can handle which inputs and which one can handle what outputs and make sure that they, you know, match up only around. I'm sure we could manage something like that. That's a neat idea. And actually, I guess that we did that. You could then also have each one display its translated outputs if you step along the way. And you can then obviously just compare the first and last. That's an interesting idea, I like that. I wonder how many people actually support language translation though. Well, yeah, if everybody ends up turning around and calling Google, then we've, that may not be the right. That would be so funny. That's a good question. Just let me probably ask though. Okay. Okay. I'm sure IBM and Watson could have fun with that one. You know what? I honestly don't really answer that question, to be perfectly honest. I'm gonna have to find out. Okay. Anything else? Any other ideas bouncing around your guys heads? Well, we, I like the idea of showing different transports. And there are also a few broker based ones or can at least be broker based like MQP. So instead of that ring we saw, there could also be events or message gateways in the middle, doing a fan out. And then this picture could form as something like flowers or something like this. So with each event gateway or broker in the middle of one flower. So an event comes in, the gateway distributed to all the British people. You have different gateways doing fan out to some functions. And those gateways would be in the middle of one flower. And then you had different centers. Okay. So almost move the CE into the middle as I think it's sort of a gateway. And then it can talk to each one of these guys. And would you, in your mind, are you assuming each one of these still does in essence that translation or whatever process and you were talking about? Yeah. For example, the, I think Azure event grid could be one other center of a flower, I suppose. And maybe each of them could use some different transport. I don't know. Interesting. Okay. So just to add on to that, if we're looking at a more of a pub sub rather than a point-to-point thing, is maybe you randomize the event source which then causes a publish, which then would pick a random set of consumers from that. So you don't get the same nodes every time you run the functions sort of thing. It's sort of, I'm curious to tell you, I mean, if you want to stick with this translation thing, I'm not quite sure how you would then maybe bring that those different things all back together. Because you really want a fan out and fan in sort of model, I guess, if you need to bring it all back to a point, yeah. So you lost me there for a second, Joe, I'm sorry. Sorry. No, it's fine because I was trying to take notes at the same time. So describe it again. So I'm just trying to couple the two ideas. So I like the notion of more of a broadcast and subscribe model so that event go can be handled with multiple subscribers or processors. I guess what I'm trying to understand is how you would then use that model in the model. If you wanted to do this sort of telephone game thing, how that would play into that sort of thing. So that my theory was if you could sort of somehow randomize the set of nodes that are gonna participate in each round of that conversation sort of thing, or maybe perform the initial translation. Yeah. Because at the moment you've got a, you diagrammatically showed it as a ring. Yeah, so I go from A to B to C to D. And I can't remember the other guy, the previous speaker was saying, wouldn't it be nice to do a publish and then maybe that event gets picked up by A, B and C in parallel, you know, processed in parallel and then emitting another thing which maybe goes to D and F in parallel. The problem then is how do you coerce that conversation back together again into a single output. Right. Interesting. So was that Heinz or Klaus that mentioned the idea of the fan out? That was me, Klaus. So do you have any comments what Jim was saying there in terms of how do you sort of tie it all back together or what were? I like the idea of randomizing it somehow. So in the demo you could start it several times and every time it would turn out to be somehow different. Yeah, but how are you... So once a node gets, say, a sentence and it does some translation on it, in your mind, what were you envisioning and doing with that sentence, just displaying it someplace or sending it off to another node to do something or what were you kind of thinking there? Actually, I didn't have an idea what each individual node could do with this. I just had this idea of this overall form of a flower or snowflake or something like this forming because of this broadcast model or approach. Okay. Yeah, because I'm trying to think from a demo perspective, if we do a fan or kind of thing, I can see that being looking really, really cool. Like you said, like a flower blooming, that'd be really neat. I'm just trying to then figure out if each one does some sort of translation or whatever possibly it does, if it displays it in some way, especially if we do a language translation thing, it'd be neat to see all these different languages pop up, but there's no way to know whether it's correct unless you speak all those various languages. So maybe use that mechanism to select the first translation or maybe the last translation. Yeah, so, because I think if you always send around the same loop, the outcome may well be affected by whoever does the first translation. So if you randomize that, and so it's not really, I guess, it's minimizing Cloud's use case a little bit, but it's still a pub sub function, but maybe instead of it going to multiple people, it would just end up at one subscriber. It's almost like a partitioned event topic or something. Well, I mean, in this particular model, obviously this is coded up too hard coded, but there's no reason why the dashboard couldn't randomize the order of these things, right? Right, okay. Yeah. So do people like the idea of, so okay, let me say my opinion, and I don't want to influence anybody, but based on what I've heard so far, I personally really like the idea of the translation thing. I think that's really cool. I think mainly what stands out to me about that is it's gonna be fun, especially if you could start out, like say English, go through a whole bunch of languages and end up back in English, and then you can have some humorous aspects to it, because obviously they're probably not gonna be the same. So there's gonna be some humor there, and I really like that aspect of the demo. I think that's gonna be really neat because it engages the audience, they'll laugh and be amused by it. So I really like that aspect of it. So I think, so what other people think, is that something you guys think is interesting enough that we should head down that path and then figure out the mechanism by which we hook everything up as a next step, or are there other ideas you guys are thinking about in terms of the application itself? This is Heinz again. We actually had done something similar for an app many years ago when I was working on a project where we did have a lot of different people. We did do language translation, but what made it funny is the initial text was a colloquialism. So that way, by the time you got to the end, it actually did become very funny. For example, the Swedish, they have an expression like I like that. The expression in Swedish was English translation was hug on you, right? So as you start going through these, the colloquialism might become very funny. The second is maybe a bit selfish because the company I work for does multi-protocol messaging. It would be kind of interesting where we might have multiple different vendors where it comes in AMQP, that points to a URL that goes, could grab it, translate it, and then point to maybe an MQTT that then comes and points to it that does HTTP and maybe show an interoperability of going from a JSON payload to a protocol binding to another protocol binding while each one is doing a translation. And you might be able to actually stick in the path as part of the user extension. So that every time it goes through one of these translations and different messaging transports to add that in. So when it gets back to the last one, which again, it could be a loop. You'd know where you started and where you went to actually see the path to show all the different protocols, that this was JSON versus a binding and what was the binding. Just a couple of ideas together there. Yeah, those are all good. I like those. So tell you what, talk a little bit like we could do. Was there anybody else on the call who had another idea or suggestion? Because it seems like we're sort of circling around this idea of the translation thing, but I don't wanna preclude other ideas if you guys have them, okay. So what I'm thinking is two things. One is I think we first need to figure out how many players can actually do translation, right? Because if we only have two, it's not nearly as exciting. So I think we first need to figure out who in the group has platform that can do some sort of translation and then figure out the various transports that people will be able to support in the timeframe. And then third is to figure out the best way we want to sort of connect at the various nodes, right? Is it a circle? Is it a star pattern or a flower blooming kind of thing? Figure out the best way to sort of connect up all the various nodes together. Is there something else in that sort of list of things to sort of figure out that you guys can think of that I'm forgetting, we're not thinking about? Okay, so what do we do this? What if we sort of ping the group, at least for those, I guess with all three, right? What I can do is I can send that a note to the group asking who has the various transports available or we know what transports he's person can support, find out who can do a translation at all and then start brainstorming ideas on the best way to connect with the nodes. And the two ideas we have so far is, some sort of circular kind of thing, start at one, work your way through up the other and then sort of a blooming flower kind of thing. We can throw out the right way to sort of bring it back at the end. What do you guys think about that? Having me send out the note asking for input. Seems a reasonable plan. One more idea just goes, if there's translation, I mean, if there are not enough providers who have translation, there is, I think on the internet, there are right now plenty of sites that offer something like buzzword generators or generating complete phrases. So if you do something like a distributed phrase generator that could also be fun if the right set of words is used to do random selection of words. So are you suggesting something along the lines of, we want to construct a sentence that has, noun verb, noun active verb kind of thing or just go to random websites? So I remember at Kupken and Copenhagen, there was also this keynote on the last day. He also had a generator of something like this for strategies. Interesting. So with that particular case, I'm trying to think, would each node be responsible for, almost like, I know it's probably an American thing. I don't know if you guys know this, but the mad libs games, right? Where there's a sentence with words missing, you say, give me an adjective and then you randomly fill in an adjective kind of thing. Yes. Would you, so each node, I guess, would be responsible for suggesting a word to fill in the blank, right? Yeah, so depending on the event it catches, it has to fill in a verb or an attribute, something like this. Interesting, okay. So if each function has a different set of words, it's randomly chooses from. But he'll think about that. Yeah, I mean, absolutely. I mean, I just had a look at the programmable web site and apparently there are over 150 translation APIs out there. I'm sure a lot of those are pay to play, but there could be stuff there that people can use. Okay. So it sounds like when I send out my note then, we have two different sort of applications then to put in front of the group. One is sort of the English, I'm sorry, not English, the sentence translation from one language to another and then we have the distributed phrase generator type of idea. Anything else you guys want me to put into the notes to get to solicit feedback on? You, do you have any ideas? You've been kind of quiet. Maybe you set it up, there we go. Hey. Hello. Yeah, I just kind of studying your guess ideas here. And yeah, I think that type of one looks more interesting to me. I'm sorry, which one? The first one, the type of one. Tiny. Got it. Okay. Yeah. Okay. Are there any other ideas that you had thought of that you might want us to consider? No, not right now. Okay. Okay. I'll tell you what, let me do what I said. I'll take the action item to send out a note with the two ideas that we're ever thinking of and see what the rest of the group thinks. Also then ask the question of who can do language translation. I assume the distributed phrase generator thing, I'm assuming everybody would be able to do that because it's really a matter of just going to the dictionary and grab a list of words that fit up with our category, right? Noun versus verb, something. I think you just randomly pick one of those or Heinz, I'm sorry, was that Heinz or Kloss came over? Were you thinking of something more complicated than that? No. I just, by the way, I just posted that example that was mentioned in the keynote. Oh, cool. Oh, they even call them mathlabs. Interesting. It's producing real, I mean, along. Oh, here we go. But it's still. Interesting. That could have some fun to it. Okay, so let me make sure I make a copy of that. Okay, whoops. Okay, anything else? All right, any other topics related to this you guys want to bring up at all? Otherwise we might as well let you guys in Europe go enjoy your weekend and I'll send out that note. All right, in that case, thank you guys. I'm trying to do anything that's what I mentioned. I think that's it. All right, cool. All right, thank you guys very much. We'll talk next time. Yep, good, bye-bye. Okay, bye-bye. Bye-bye. Bye-bye. Bye.