IBM MQ and JMS bindings make references to AsyncAPI v2.x that are not compatible with v3

[fmvilas]

The IBM MQ and JMS bindings make references to the server URL scheme but on v3, the URL field on the server object is gone so that's not applicable. Maintainers should decide how to proceed in this case.

As an idea, the protocol field could be composed by two protocols as follows: file+ibmmq and http+ibmmq. This way, we make it clear it's a combination of two protocols. We're already doing this (informally) with MQTT over WebSocket or STOMP over Websocket where the protocol is ws+mqtt and ws+stomp respectively.

In any case, I think this is a good opportunity to clarify the meaning of the + symbol in the protocol field. For instance, why ws+mqtt and not mqtt+ws? What's the order and why? Etc.

This, or completely come up with another solution. I'm all ears.

cc @derberg @dalelane @smoya @char0n @rcoppen

[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 ❤️

[fmvilas]

Any thoughts folks?

[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 ❤️