Add official Protobuf schema format

[jonaslagoni]

Description

We discussed this in the following meeting: https://www.youtube.com/watch?v=8Yjles2pEHo

It would be nice to have official schemaFormat types for Protobuf, in order for all tooling to understand when protobuf is in use instead of each having their own understandable value.

https://github.com/GreenRover/proto-schema-parser uses the following:

• application/vnd.google.protobuf;version=2
• application/vnd.google.protobuf;version=3

Which makes sense to use.

[jonaslagoni]

@GreenRover was this something you would like to champion?

[GreenRover]

Yes i like

[GreenRover]

Waiting for: https://github.com/orgs/asyncapi/discussions/643
to be migrated

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[GreenRover]

@jonaslagoni

• I got now the schema parser done
• the react ui is supporting protobuff in next release

What else do you think needs to be done before add protobuff official to spec?

[jonaslagoni]

Technically, I would not even see that as required before adding it as official schemaFormat values 😄

But as v3 is locked down, I would wait for the next spec release to add it to the table 🙂

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[smoya]

But as v3 is locked down, I would wait for the next spec release to add it to the table 🙂

We can resume the work then!

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[smoya]

@jonaslagoni @GreenRover Are we gonna do this then? is this what we wanted to achieve? : https://www.asyncapi.com/docs/reference/specification/v3.0.0#multiFormatSchemaObject:~:text=Protocol%20Buffers,protobuf%3Bversion%3D3

[jonaslagoni]

Yep, already done ✌️