AsyncAPI Community, 9 Jul 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: AsyncAPI SIG meeting 11 (July 9, 2019)

Description

This is the recording for the AsyncAPI Special Interest Group (SIG) meeting #11.

Attendees:
- Abel Cal
- Andrew Snodgrass
- Fran Méndez
- Łukasz Gornicki
- Marc DiPasquale
- Raisel Melián
- Rubén Hervás

Moderation:
- Fran Méndez

Agenda:
- Contributions from Kyma (Converter and REST service) — Łukasz Gornicki
- WebAssembly PoC — Łukasz Gornicki
- Issues review
- Q&A

A

If you watch the outcome, okay, just so you know it's, it's recording, okay, yeah.

B

Yeah sure um I will sure right. That's gonna be the best I guess.

B

B

Can you see a empty browser window yeah.

B

So, just to give a context for others. um We have this as an API react component. That is a react component for rendering as an API, and it supports one zero. We want its, of course, the support to zero and it's yeah.

B

One of the use cases for this component is, of course, to work on on the client-side applications any server-side applications, so we need to have a parser to support rendering and for now, as you know, there's only go parser, so we wanted to check out webassembly how we could, because it's really mature at the moment- and we wanted to check how much you go is mature if it comes to a personally and if it really works and we can use it.

B

So, the all the details are in this issue, but I think the most important is what marching from our kima project. Did he created a really simple example: repositories also linked into the into the issue, what he did. He simply provided really simple instructions: how to set up an engineer's hosting the the web assembly file, and then you use it to showcase that.

B

It's really working that you can really parse and VPI spec in the UI, so just to show you quickly, I have it running with docker and the the main outcome of the POC is that go is not much enough. The the default go. P-- compiler compiles into really big size packages, so the the go parser for us, an api, the size of the of the compiled file, a wasn't vial is 14 megabytes, and even if you enable like in this showcase, we have a gzipping enabled on the server side for nginx.

B

Even then, the package is 3.5 megabytes. So, even though you can nicely.

B

Just take an example: put it here and see that really parsing works, so we have to say everything is realized. The parsing is realized with the go parser for us, an api. You can clearly see that having a three point. Five megabytes file is rather a temporary solution. You.

A

B

For us, it's super cool because we can, with with this pop, we proofed it works. So we can start working on the on the react component without waiting for a for other parser, so it unlocks the work we can yeah. We can do it, but long term yeah I would not say go is a good solution for now for using my blossomy yeah.

A

So just so you know I'm hoping you have the parser in native JavaScript working for the browser and from Algiers I'm hoping to have it like I, don't know like probably end of this month or something like that. Cuz, it's really people. You know it's well, I mean we. We are the lead with version one where they do it like this. It's just changing this schema to version two release candidate, one and and basically, since there is nothing else, I mean we can keep improving it.

A

But since it's JavaScript and it doesn't have types so parsing is basically the validator. Nothing else is just and given it's giving you the whole raw JSON object right. So the parsing is really easy. You didn't have to match the Jason structures to data types in Java, Script right because there are no data types.

A

So it's it's really easy, so I'm hoping to have it ready for the for the end of the month for sure after the conference or beginning of the next month, because left next month, because I'm taking holidays right after a day there San Francisco, which is next week and so yeah, but it shouldn't be hard. It shouldn't take long to be honest. I actually have a proof of concept of on my machine now and with JavaScript, and it works perfectly in browser. I mean OGS I'm, just not happy with the code quality, but it works.

A

B

So thank or think of protobuf and no.

A

No, no just the basics without proto power. For that for support. Just you know the basic suggestion schema and that's it, which is enough to unblock your work right as well so and for most of the cases, is gonna, be enough. So well for I. Forget thanks for this proof of concept with WebP assembly, because that proves that I mean it's cool. It's nice and it may be there in the future.

A

But it's not there yet I! Guess the problem ISM or the hard work is always on the side on the go compiler right, the faucet, your compiler might have to work harder into building smaller, smaller web assembly files and C++ files as well so yeah. So rice l suggested to why? Don't we? Why don't we use frost right?

A

Is there a special reason you want to use rest I mean I'm, saying this because I remember you worried the conversation in the beginning.

A

We did it dressed because the community is not so big and and and the packages that you can find in res are much less than even in go, which is already a problem.

A

So switching to rest may make the bundles smaller, but the developer, those developing harder right so and so I don't know if it fits really because good idea or or it's preferable to just create a single parser pair language right instead of having just one and transpile to all the languages.

A

You want to say something: I said you wanted to say.

C

Something he was thinking about. The resources facing API will all make sense to you. If we could do what we are trying to do it with code and then Russ does it perfectly I mean when you, when you compile anything from rose to you to where an assembly is ridiculous. Small yeah.

A

C

A

What about this, it.

C

Doesn't have to compile any Congress collector, oh yeah,.

B

C

Is pouring into there? That's, why shall be, but about about the community? That could be an issue. Remember my.

A

Concern is, for instance, I mean Reuben can tell you better because he's been fighting against the dollar breath. You know resolving all of the oldest dollar prayers in respect and going to the remote file download and it's parsing it.

A

You know and put it into the into the spec and go it's being already a problem, like he's been doing a proof of concept, but it's really three key and in JavaScript you already have it you have you really have libraries that test that right, but and then for instance, you have libraries that may convert from Avro I if I remember correctly from Avro to JSON schema or getaway around I. Don't remember so there's this there's something in go please or something right, but I don't know about the rest.

A

I mean that the thing whenever I try to find something we dressed like support for proto buffers or for a draw or for JSON schema. For instance, the support is really you know it's in early days or in existence. Basically, so it's hard to is happen. It's not! For that reason we cool I mean anyone could argue that if we created for this project, then we contributed to communities right. So we contribute to have it basically, but that's like a huge word around. That will be amazing over the over time.

A

That will be amazing, but speaking the other day with don't remember who what I was speaking, someone think about the parser and and I realized this another problem. We haven't think I think it was with you a bit with the dis another pro with the person and it's like if we're gonna make it pluggable. So we want to plug a parcel for protobuf and for extensions and all this stuff.

A

If you cried this tension, for instance, in JavaScript and the parser is in go, how do you use a JavaScript extension with a cold person or I mean one cool cool? Say it yeah, but you use the JavaScript, but you have a script partially, not to go perfect, but you may be using the person in your go code, so you can do that. You cannot do it so that takes us to a point that may be.

A

The only way to go is to create a parser for each language and repeat the job in each language and maintain all the packages, all the parsers for every language so becoming native in every language right, which is scary, because it's it's a huge work, I'm sure we can do something kind of boilerplate or automation around it, but ultimately we have to we need to have.

A

If we want to make things pluggable, we need to have eight parts that are only on each language right, so you'll get what I'm saying like we understand or am I just throwing ideas and doesn't make sense. If someone doesn't understand what I'm talking about just please raise your hand I'm happy to okay, so I would say so before I continue look at. What is that that you don't understand? I was.

B

Already lost with, why would I even butter that I want to use my today s extension in a go parser? Yes,.

A

So imagine that you have an extension that parses a Twitter account, for instance like the one on the examples that we have and you want to use- and this extension, this part of the extension is written in JavaScript but you're using the go parser for your project or a java, parser or whatever right, and you want to tell the Java parser, hey uses extension for the Twitter account, but you can't on the code because it's not a go cold or it's not Java code, it's JavaScript code.

A

So how do you plug it to a another type of language? You know what I mean so imagine if you have to passing it all in a call to the parse method you want to pass at the at the end of the of the method you want to pass. An array of parsers of extension, bar tips, right or extension, validator city wants. Not part is.

A

A coding in the language, you know what I mean it's impossible right now, so that.

C

Means that you, you want to create a precision.

A

Yeah, but because the thing is the the support for proto buffers Avro, you know another and another ski mask schema languages like xst for xml. The idea is to make all of them pluggable because there are other. There are other internal and external as well. Languages are schema formats that we're not going to support natively in each language right, because that will be insane so imagine that, for instance, I use the example of flatbuffers, for instance. Flatbuffers is it's really it's highly adopted in in the game industry right?

A

So what happens is if we don't add support for flatbuffers? They have to create a flatbuffers message. Parser, like the idea, the person was there like. Ok, you create a flat buffer message, parser and you plug it into our pattern. But if someone wrote it on JavaScript the flatbuffers parser, you cannot plug it into the go parser or into the java parser into the Python person. You can only plug it into the JavaScript parser and you may not be running your code in JavaScript. You may be running it in Java or Python or whatever.

A

So that creates an inconsistency and impossibility to have all these parcels in a single in every language. Unless you repeat, the work in every language in any case, is that the thing is that this situation remains the same.

A

If someone, if we create a parser for each language and someone has it done in JavaScript, only it's the same problem right, I'm, not sure how to proceed with there to be honest, like if we still have just a single one in go for instance, or in another language and then compile to mobile languages or not I mean the thing I, don't know.

A

To be honest, it's a hard decision, because in any case, what I'm seeing here is that we can probably not make the parser tribal, maybe in extensible so, which is I, mean it's fine, but it loses a lot of power. Right, like flex, is the the first. The first idea of the of the parser was to make it playable, so it's easily, or maybe we can help other people. I, don't know, write their extensions in in a language that can be compiled down to other languages like like over interests or something else. Oh.

A

Is it more or less clear now the concern with this.

B

Yeah, maybe I just simply didn't get it at first, because for me, it's I would not consider this a concern right because at the end, if you just have let's say, go parser and JavaScript parser and they're all prepared in the way that you can plug in your custom code into it. And then somebody is having everything in Java and they have some parser for some specific protocol written in Java, then I mean what else can you do? You simply have to tell them write it in the.

D

B

Other language or just write your own Java parser, or simply, let's work together on providing another parser and I, don't think you can satisfy everyone.

A

Yeah, no, no, no I'm, just trying to I'm putting all the examples. You know all the situations in areas, so we pick one you know and we make sure that we pick one wisely before continuing work on that's right, so yeah I, guess maybe in that case I'm just thinking about, maybe just in this case you have to just yeah. So the part that is pluggable, but you only can plug code in your own language.

A

So obviously right and not all the extensions are gonna be available in all languages like like the parse it right, okay, okay! So in any case, coming back to the to the topic of using breast yeah, you know problem is it was slow down development, starting because starting from that, the fact that none of us know rest- but some of us do know ego so so yeah I'll stick to go and just create a separate parcel for JavaScript, which is a like a special case because of the browser right over time.

A

Maybe we get, we get some news from the go folks and they improve the completion process and we can get rid of the other one who knows, and there.

B

Is already a tiny got any goal project which you say, yeah I, said a different compiler that community works on to make go embeddable in really miss tiny devices? Yes, but it's yeah and we tried it with this: go parser for passing API, so the generated by bus and if I did not fully work work, because not everything is yet fully supported there, but maybe even in few months and the story will be totally different with what I see photo.

A

So to be realistic and move forward and not blocking anyone, most of our tooling is written in JavaScript right now, in no GS and when I when I say most of our tooling I mean distinct API doing right, not not the code in your companies, but most of our tuning is for generating documentation or generating curl and all this stuff.

A

So it doesn't really matter if you don't have a parser for Java, for instance in the beginner right, because the code will be generated using the node.js parser or the JavaScript parser will be generating job that you can use like a cell. So it's still, it's still fine right.

A

What else you also had something Lucas, yeah.

B

So we it's about the converter and they, sir, so just I wanted to align how we should proceed with that. So we for our use case for kima. We need not only we're not only building front end, but also we lay back end for that will validate this pack and convert it for the customers from old version into the new one and the whole stack for us. We, it always is go length, so we need to provide a.

B

We know that you have this node.js converter, but we need a gold one and we will so we will work on the converter.

B

We actually starts this week and- and we will also work on the service that will be a rest service with two endpoints, that one will be available responsible for validation and the other one will be, of course responsible for pro conversion, so you will provide a spec and then in return, you're gonna get a converted version and my question would be because for us, I think that the best would be if it goes like, with the a sink.

B

A sink API react component into the a sink FG organization, but it's up to you to decide if you prefer it that we contribute to your organization or we keep adding kima, because if we will keep it in kima, it means it's gonna end up in our huge mono, repo somewhere hidden between the components. So nobody know.

A

B

Then we just need a wrapper for that.

E

B

So then we just need a ripoff, so we need to create a report for another.

A

You should be able to propose if I'm, not I, think.

F

A

Yeah, you have to power.

B

A

We just remember that you, you were able to add some other people to the orc from kima and so.

B

But I'm I, don't think I'm able to actually add to the orc, because I wanted to have one person recently and I could not okay.

A

We'll figure out so does anyone wanted to bring some topic or something questions not really okay, so before I continue. I would like to to welcome to the group.

A

You want to introduce yourself, maybe I'm gonna make you speak in English great.

D

Well, my bad I mean from a date hmm from Spain and well I met with GU band and he contact with travel and it's this project. I spent the last few years from defending the sea cappy's api's, because I was working for a media company and the only way that I phone to solve some issues. So big issues was the in the same way and really excited about this display, because I think it has a very long want to vary. It will be very interested way to solve most of the most issues.

D

A lot of companies are already shaving with big data. Things like that, so I can contribute with documentation with our. During this week, I was trying to make an illumination of great QL with the with the SUBSCRIBE action.

D

Deployer will implemented with the async ABA specs and I'm just for now, I'm, just playing with the the edit of the line editor and try and I'm using an example about quarantine and I'm. Trying to to make it work with the front on the front that I'm doing with angular is the most the way. That is the language that I really know so.

A

That you can share afterwards, no.

D

A

Afterwards, when you, when you finish it, you can.

A

D

The Rosetta for the blow you know.

A

Something that I was thinking and then some people when many people are asking, is about use cases and examples right. So we're lacking a lot of examples and useful examples, not the one. You know the ones.

D

A

Do we have in the grade book right now, but the useful us I mean you know representing could be the real news cases so yeah, so that that would be really amazing. So working.

D

A

I hope you we have. We.

D

Have him for longer here.

A

Yeah, so for those of you who don't know I started another meeting, that's why there was a lot of confusion and in the beginning, which is for people who want to regularly contribute to a sink API, because this one is public meeting for people who just want to attend, maybe ask some questions and because they have some, they have interest and I created another one for contributors. So we keep at we first of all, we know each other and we can share the progress or questions about the development of certain features right.

A

So if anyone to be in just let me know and I'll, send an invite okay, but remember that this line, which is by the way happening at the same time this one, every it's gonna, be every Tuesday.

A

This one is gonna, be about development. It's not gonna, be about like this one, which is usually to expose to the public or to answer questions to people that might join and don't join anymore because they don't really care so much about the development of the project. They're, just curious right, so so yeah just so you know, and I was thinking I'm doing something easy to review, but.

A

What do you think, maybe it's too late or or because we just we just have twenty twenty minutes to go?

A

There were some people picking some issues last the last meeting two weeks ago, so maybe it will be nice to have some feedback from you on. How is it going and if, if you, if you started doing something, I, don't know because I know that some people call them work yet, but.

A

I'd like to know from you so, for instance, I I know I've seen that Lucas, if being working on the.

B

A

B

Was a bug with the resolving references to fights as far as I remember.

A

I mean this installation, one word with version 0.7 an app. It's a sign to you. Oh.

G

B

But it's this one but is dependent on the NFF low note. I FF e FF this one right.

D

B

Discussed that we are blocked waiting for them to enable support for nodes, 12 you're right so.

A

I'm gonna I'm gonna move it to to the icebox okay that'll. No, that will not be an issue anymore. When we have the genius, the native James Parsons yeah,.

B

But the pre-quiz on the note on this dependency, I I, so that one person already approved it and I just probably need to fix, failing see, I and yeah, maybe soon they will enable support. For the latest note, nice.

A

B

One ticket and the other one I had was the failing in the in the generator repo. There was a issue files that you cannot generate Park down. If you have references to files and I only made it made it possible to kind of set up an environment where I can reproduce it. Okay, but didn't worry yet work on the fix, because I first wanted to set up a goals for this converter and II and the service. That's what I continued working on it.

A

And then, when I know, you have many things in progress, I'm curious. If this is true because you'll be crazy, it will become crazy. If you have too many things in projects well,.

F

Actually I was working in the same backers, Lucas I, think or if it's it seems to be related, at least maybe it was a duplicated back and then and then I was also deprecating. The Northcote gen are nothing.

E

F

Generator but I haven't finished, I mean.

A

So maybe maybe you can both coordinate I, don't know. Let's.

B

Go friends to see.

F

I have the a bro examples that I'm working on I mean yeah, but I'm.

A

Working on it or or you have it like some day, I'll work in it. No.

F

So I I'm working on it like really slow and really okay, but I.

A

Just want to know, because in case you're blocked or something or you've, nothing to move or whatever put it back, and someone will pick it and you go already and you want to share it. Just share it. I think I mean actually.

F

A

F

A person it's working for simple cases, but I wanted to test it with more.

A

F

Examples and that's what I'm working on okay, yeah.

A

Yeah, so maybe if you want to share just push this go to a branch, so alright, it start I mean helping, maybe not just reviewing, but maybe we can just synchronize and say: hey I have some fixes for this case this case in this application, and we can. We can all contribute right or maybe just create a draft pull request. Now that think it happens. Yeah after this yeah clear that this is a draft that this is. This is just a key code. Maybe I know.

E

You and it's gonna be city code.

E

F

I'll push the changes, then, okay,.

E

A

What else, oh you have more you have. This can't refer to a key that has a dot in it. Yeah.

F

I mean that's it, it was fix me I'm, not sure, because.

A

Yeah and since I'm, seeing aunt applicated into here, there is another one called reference to local file doesn't work exactly.

F

A

And it's the same as oh crap: this is him as a Lucas, one I think.

F

That the dot thing it's done, I think.

A

God by a pull request from someone from the.

F

Russian guy yeah.

A

E

Can try quickly.

A

A

E

Playground now.

F

It could happen, yes,.

A

No, but it doesn't work, I, don't know why doesn't work, but it doesn't fail. It's really strange and I'm trying and playing on the playground and it doesn't update, but it doesn't break or it doesn't show any error or anything. Just yeah.

D

A

So yeah, so it's nothing easier anymore. So we can adult.

F

A

So I'm gonna move.

E

A

E

F

Know if you remember that we talked about the reference to a local file, but the file was a yeah man file, not a gem file ah yeah, because that was that's one issue. Maybe yeah.

A

F

Can discuss it here with.

A

For instance, I know or I think I know and in the open API case, if you reference a young'n file, it's not gonna work. You have to reference all the JSON files. So so you can have this back. Your spec can be in general, but reference files cannot be in Yemen. It has been in Jason, but.

F

There's that back that it doesn't work referencing a file, it's because the file, it's in Yemen, exactly.

F

So watch that problem sure.

A

F

I'm quite sure, but I will double-check, but there is a test just with that example. So.

A

The thing is that when you have a dollar red and then pointing to a local file or a remote file wherever and it's a general one, the one that's in the draft, the question is: will it work or not because it might seem if your documents in general and reference is another llamo? The feeling is like it will work right. It's referencing another piece of yellow that wood will be converted to Jason, and then you know and evaluate it at so as we do with the documents but they're thinking about it.

A

This, like mmm I, don't know because we have these schema formats in in person too, and with respecting. We are expecting JSON schema, JSON schema, stuff, Jana is Jason, so I don't know. Maybe we can. We sue allow this, but only if you specify in the schema format that you suspect in JSON schema plus yeah Mel. You know in the in the in the Mima type that you can specify with a plus. You can specify that the content type or something like this I don't know, doesn't make sense. What I?

A

What I'm saying to all of you like? Are you getting what I'm saying or or sly there my screen, maybe, and so an example.

B

So it makes sense, but then there wouldn't be some default right so that you don't specify it so yeah, okay and and the issue that is assigned to me. There's the reverse situation. So the file is in llamo and it references they Jason yeah.

A

That's a work even even though, if you used y'know internally. What happens is that is that we used a Sarang this peg. It says that you can use Gemmell, but only the subset that can be converted to Jason. So it's like a nice. It's just like it's sugar. You know syntax sugar for for async API, but the real, let's say official format of facing API is not the a negotiation just use yellow for ease of reading for people right for humans.

A

But yeah so I don't know what do you think it will happen in this case, if you reference a yellow file, so it'd be converted or so it just it. Don't work like it's work only with Jason for it to work with. If you specify another schema format.

B

Let me share screen: it's coming the easiest, what me if it would work out of the box right, so we have a Jason awesome, VP, Gary filed you reference the um file and it just works. You don't have to be guess that you have to specify some different type or.

D

A

See the other playground right.

D

A

Okay, this is the thing is, for instance, I. Have this I have this channel here? Let's make it simple, alright and I have the message here and this ref imagine that this graph is pointing to a yellow file, whatever not here, I.

E

A

So strict we can I mean not this one. Sorry.

A

Quickly consider in the case, that's all the words that shouldn't work right, because that's Yemen and we work with Jason, but given that we're using yellow referencing another yellow needs to make sense right, then the thing is we could make. It explicit. Have something like this.

A

Application I think it's Jason schema whatever. If it doesn't exist, we invented plus whatever. So in this case, we're saying that we expect JSON schema general format.

A

If we, there are two cases, we either make the the parser, detect the format and converted to Jason to matically, or we make people have to specify this. Otherwise it won't. It will not work. So this one is like more I, don't know how to say it's a it's more like strict right, unless you specify it correctly right, they do not work. Okay, so.

A

It will be something like this right.

A

That will work right that that could be like okay. So we expect the the schema format of these reference. This paler is gonna, be YUM, so the ended the particle reacted this and say: okay, I expect llamo I know what to expect or we can make it automatic. What do you think.

D

Well, I think that people expect that the shaman is a superset of Jesus. So if it works with the past works with Jamal its we work with Jason. So if we have the capability to with Jana I, think Jason is already done so I see that the property of scheme format is not needed. If you are going to refer, make.

A

Sense, okay, I'm, just curious I mean I, have my own opinion on that and I think I. Think the saying I think that we should make it automatic instead of explicit, but then on the other side, I have the you know, feeling that this is Peck. Everything should be specified right. Every case will be specified and I mean we can put this specification as well. If your, if your reference of the file is a yellow parsers will convert it to Jason whatever we have it in the spec and that's it.

D

Maybe it's a possibility to add more language to this description, I mean, for example, you see an important but the waters.

A

When it's a product of format, for instance, maybe you have things proto Orson's like this right, so imagine like this yeah.

D

A

So in this case you have you know you have to specify this. Otherwise, this format can be anything right. We cannot be magical out of detecting because there there may be the case where two formats are compatible between each other and two files may look like to four different formats and you don't know which one to choose like I'm thinking, for instance a maverick Avro- and this is kima- some pieces are very similar. Both are Jason.

A

You may have a small piece of Avro that, if you, if you do it in JSON schema, it would be the same. So then the parser will think this is station, schema whatever I.

E

A

Know do you think I do about it.

G

Yeah I guess you need more specificity because well in this example, you could have different versions of protocol buffers and it'd be kind of nice to specify which version of protocol buffer. You expect yeah.

A

And in the case of the mo the one that before this one.

A

Do you think it should be also converted to adjacent over.

G

Oh yeah, if you specify the schema format, then it should be automatically converted to the JSON representation.

A

So you mean like this: it's a work right, even if it's yellow fine, it's.

A

G

Could support both you could if it's in the case of llamo, it could work like this, but also you can support specifying the schema for sure.

A

For sure I mean that.

G

A

A this is like it's like adding more specific, so this is like, if you had a schema format for sure you're making it clear this is yellow, so the parsers will not have any problem parsing it right.

G

Actually- and you can, you can have like a table with each file extension and the default scheme format specification for each file extension. So we.

A

Actually, don't look at the name of the file name, we look at the the contract, I. Imagine it's a URL and it doesn't have the demo.

A

It might happen so before.

F

A

A

Is a URL in the URL? You don't need to put the dot whatever and.

A

G

You look at the mime type, the HTTP line, type I, guess, there's, there's a mime type header right, mm-hmm, exactly.

A

Do you look at that header, this cool, being fair from the in the case of HTTP, the school being fair from the mime type, but in the case of a file, for instance, the local file? You don't have this right. Imagine that you have my system wherever my stuff and then you have I, don't know file damu or you just have file, and this file is a yellow file to work in a way right by sniffing the content and trying to parse the content and if it works with yellow. We assume this is channel right.

A

G

Know what I mean so using like magic bits to determine.

E

F

It's not exactly.

A

With just explode on exactly so currently what we're doing is we try to parse the the content destination if it doesn't work within, try sgml? If it doesn't work, it's mediation again, and so we fail. We would rest never but the more stuff that we add or not the more stuff, because this is only for the case of the default, where we don't have the schema format right. We only consider those two so thinking I, don't know. Maybe.

G

A

G

So if you plug in zap, as you add each additional plugin, you have to check it an additional format for if you have plug-in format, plugins yeah.

A

So this is the idea. The idea of this is it the default, which is like this without schema format right, the default will will only support JSON and Gamble, and if you want to support something else, you need to split eclis specify the schema for me. Otherwise it won't work, but we're talking now about the default, like you don't specify anything. What do we assume is this Jason? This is Yemen.

A

Is it we don't care, you know it's. We tried both there's a by the way. There is another I'm considering another change in spec for the final version, which is something like this right instead of schema format. You'll have something like this, so this becomes mandatory all the time the schema for one becomes mandatory. All the time you cannot, we will not have a default because you have to put it. Why is this? Because some people are asking for multiple formats like this I want to have the imagine I want to have my I won't.

E

A

My message defined in different schema and xst, and one will think why you want to define it in two different formats right. That's what I thought in the beginning and that's why I chose for the the other way of specifying it. But then someone told me you know what's what happens in old in old applications with legacy code?

A

What happens is that you're migrating from XML, for instance, to Jason okay, so you will share this file now for for two applications, for instance for the old and the new, or not this file, this definition for the old and the new right.

A

So what happens is that you want to have both the the the old application will just read this one and the new application will read this one, maybe I'm still considering it, because I think it's kind of a huge edge case, and in this case you can have this too I think API files where you just have one or the other, but not both because I don't know, there's really.

A

That really complicates a lot and makes the pic harder to read and to write as well, because flatbuffers, for instance, or open API, Francis, open, API I think they have a mind type but I'm, not sure if it's official ready or not. So you might use some format here that doesn't have a mind tag.

A

So what do you write here? You know and then all the things like this will work or not. So this work sorry draft 0-7 friends. So this work, so this work without the zero.

A

Then we, what happens if we accept this in schema, which draft is it is the seven is. The eight is the four ISM. You know what I mean, sir. This creates a lot of problems as well by itself, I'm, just I'm. Just thinking about so you don't know so I don't know.

G

20P under different channels, though, you should have like an action. / x, ml, / street light ID.

A

It might not be possible because the channel invariants Kefka topic- you only have one Kafka topic right and you you may receive the the the data adjacent, but you have it defined in orange, acting in XML, but you have a defining both XML and and XS d and is a schema. So this is again. This is not the content of the message. This is the definition of the content, so you can define JSON using x, SD and you can define XML using JSON schema.

A

You could, theoretically, you can do it so so yeah anyway, I, don't think I mean I just wanted to know your opinion. You know kiss.

A

This is I, think we're entering like. You know, dark areas where we may be complicating things, a lot for methan or for some edge cases that some people have I only had about this one's from someone not twice so maybe it's just a niche case. This person is having and that's it and then there are workarounds for this as well. Like I said, you can have two files to a sink a very fast while you are migrating legacy, kill to to new code.

A

B

For me, it sounds like super nice concept for us and he plays zero exactly.

E

Or even four already we're never, but.

A

A

So I'm gonna stop recording. So we can start saying nice things to each other.