Remove `$ref` field from `Channel Item Object` in next breaking change version (3.0.0)

[char0n]

This is continuation of https://github.com/asyncapi/spec/issues/607. Changes for AsyncAPI 2.3 has already been issued.

AsyncAPI 2.3

The aim here is to limit complexity and bring more flexibility.

• [x] Deprecate the use of $ref fixed field in Channel Item Object
• [x] Introduce new fixed field called channels in Components Object with type of Map[string, Channel Item Object]

AsyncAPI 3.0.0

The aim here is to have single referencing mechanism within AsyncAPI 3.x spec (reducing complexity) - Reference Object

• [x] Remove $ref from Channel Item Object fixed fields
• [x] Change Channels Object patterned field type to Reference Object | Channel Item Object
• [x] Components Object.channels field type will change to Map[string, Channel Item Object | Reference Object]

[char0n]

PR has been issued for next-major-spec branch.

[github-actions[bot]]

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

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 :heart:

[jonaslagoni]

As I can see we can close this issue as it's completed both for version 2 and 3. Or are we waiting for some implementations?

cc @char0n @fmvilas @derberg @dalelane

[char0n]

@jonaslagoni sure, fine with me.

[derberg]

I don't think we should close as long as 3.0 is not yet merged and released. We should rather make sure it is linked in description of https://github.com/asyncapi/spec/pull/759 with info that it will be solved after the merge

[github-actions[bot]]

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

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 :heart:

[char0n]

Be patient @github-actions ;]

[github-actions[bot]]

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

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 :heart:

[char0n]

Reopening due to https://github.com/asyncapi/spec/issues/699#issuecomment-1273650238