Cleanup/simplify this repo

[derberg]

We finally want this repo to provide some value to the community by doing this MVP with @Sihamtahi

But in current repo there are some concepts that are bigger than MVP, aiming for super future. I think we should remove them.

• remove any mention of binding extensions: IMHO bindings are experiments, non yet under major release, so promoting any extensions there is not good and I do not think we should do it now. So I would remove the example extensions for sqs and http bindings
• I suggest we simplify things and get rid of this yaml format and follow markdown like for main spec and bindings
• json schemas like in case of spec and bindings will go to spec-json-schema

Why? I just believe we need super simple approach for now, instead of super complex solution that is there of very long and not taken further.

Also some details you can find in requirements in #78

@fmvilas you are the only code owner with me here so far, so please have a look

[fmvilas]

I completely agree. This repo was just an experiment so let's take it from scratch and build something simple.

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