Why reinvent the wheel? What does this add to the current state of the art? I can't even find a "Related Work" section on their site.
The types of diagrams you listed above are great for describing software in useful ways, but none of them are rigid enough to spec out an async API.
I still need to review this spec to fully understand it, so I'm not promoting AsyncAPI. I like the motivation behind it.
edit: typo
I see the YAML example completed here: https://www.asyncapi.com/docs/getting-started/servers/
asyncapi: 2.0.0
info:
title: Hello world application
version: '0.1.0'
servers:
production:
url: broker.mycompany.com
protocol: amqp
description: This is "My Company" broker.
channels:
hello:
publish:
message:
payload:
type: string
pattern: '^hello .+$'
Where do you define what to do as a subscriber?
above example already tells you what to do as a subscriber, as the document you shared describes an application that publishes a message
What would be really cool is if this could serve as a front-end to e.g. SPIN model checker ( https://en.wikipedia.org/wiki/SPIN_model_checker https://en.wikipedia.org/wiki/Promela )