[FEATURE] Updated NATS bindings

[YannickMeeus]

Why do we need this improvement?

We are evaluating AsyncAPI as a means to document our services, our message schemas, and any relevant NATS topology information. I initially got excited in seeing a specific NATS binding within the specification but found it outdated, and lacking in breadth and depth.

It specifies a queue field, which in and off itself is already a secondary artifact within NATS instead of a first-class citizen and rarely if ever useful unless an implied meaning is attached to it within the organization itself.

For example, if using Jetstream streams one could associate an outbound stream name with the queue field and that could suit our purpose. But that feels opaque.

Are there any plans to expand the NATS binding in the near future?

How will this change help?

1. Clarity and ease of use for NATS documentation
2. Expanding the bindings design should help broader industry adoption

Screenshots

No response

How could it be implemented/designed?

The approach would be one of consistency. Evaluating the level of detail that is documentable for other, more mature bindings, and applying the same rigor or approach to NATS seems the most sensible approach.

We would be open to contribute a draft. We are early on in our event-driven architectural pivot, and are not yet adopters of AsyncAPI so there will be a gap in understanding that we would need maintainers to help us bridge.

🚧 Breaking changes

No

👀 Have you checked for similar open issues?

• I checked and didn't find a similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue?

Yes I am willing to submit a PR!

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[derberg]

@jonaslagoni can you have a look please

[jonaslagoni]

@YannickMeeus if you start using bindings for NATS, you can add extensions with the ones you feel fit the most, and then backtrack it here to make it official.

They are definitely lacking.

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