General extensibility of binding configuration objects

[dpwdec]

I've noticed that generally the bindings that are currently supported might offer extensibility at their root level but not for further configuration objects. For example, the TopicConfigurationObject in the Kafka binding definition is not extensible.

Was there an intentional choice to lock down extensibility based on configuration objects for bindings?

Is there any objection to opening them up?

It doesn't seem to be explicitly stated in the Binding specifications on the AsyncAPI org repo about extensibility, and I personally know that we are heavily using extension properties on bindings like these to provide some drivers for internal properties on our Kafka clusters.

[dpwdec]

To follow up on this for any future people viewing this, the extensibility was added at the bindings definition level in the AsyncAPI bindings org definitions and the functionality for parsing extensible sub objects was added to the AsyncAPI.NET project.