docs(spec): add RFC for Message Example Object

[char0n]

This is formal proposal for introducing new Message Example Object as originally proposed by a strawman in #606. Champion of this RFC proposal is me (@char0n).

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[fmvilas]

👍 LGTM

[jonaslagoni]

LGTM 👍

[smoya]

LGTM!! 🚀 🌔

[derberg]

@fmvilas linked proposal is at stage 1. Is this really docs: like change? There is also no implementation in the Parser atm (asyncapi/parser-js#321). This change would introduce Parser 2.0 release.

I'm all in with pushing it to the Parser and having 2.0 release, my feeling is that we have here a kind of unofficial fear of major releases, but I say I do not care that 2.0 will only have one new model, we should do it and improve UX and not look back (Jest.js had already 27 releases, React 17 and this is one of their strong points).

anyway, before we merge it, the proposal needs to reach stage 3 imho 🤷🏼

[char0n]

@derberg how can I help to push this to stage 3?

[fmvilas]

@derberg I don't think this proposal should be linked to the one on the parser. To be honest, this is just a docs reorganization. I understand they're related but IMHO parser implementation of types shouldn't be a blocker for this one. Am I missing something?

[derberg]

@fmvilas I think you are right 👍🏼

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[asyncapi-bot]

🎉 This PR is included in version 2.2.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀