fmvilas opened a new issue #716: URL: https://github.com/apache/incubator-eventmesh/issues/716
### Search before asking - [X] I had searched in the [issues](https://github.com/apache/eventmesh/issues?q=is%3Aissue) and found no similar issues. ### Documentation Related There seem to be a few typos in [this document](https://github.com/apache/incubator-eventmesh/blob/master/docs/en/features/eventmesh-workflow-design.md) regarding AsyncAPI. If I'm understanding it correctly, you want to define the microservices using AsyncAPI. If that's the case, then `subscribe` and `publish` verbs must be exchanged in the following 4 places: - https://github.com/apache/incubator-eventmesh/blob/master/docs/en/features/eventmesh-workflow-design.md?plain=1#L62 - https://github.com/apache/incubator-eventmesh/blob/master/docs/en/features/eventmesh-workflow-design.md?plain=1#L77 - https://github.com/apache/incubator-eventmesh/blob/master/docs/en/features/eventmesh-workflow-design.md?plain=1#L97 - https://github.com/apache/incubator-eventmesh/blob/master/docs/en/features/eventmesh-workflow-design.md?plain=1#L117 I know it can be confusing at first (and still is for me! 😅) but AsyncAPI operation verbs (publish and subscribe) represent operations the described application **accepts** instead of the operations it performs. So, for instance, when you say "publish" it means others can publish to this microservice (therefore the microservice should subscribe). Here's a good article explaining the meaning: https://www.asyncapi.com/blog/publish-subscribe-semantics Needless to say, we're working on changing this for version 3 of the spec which we want to release this year. Here you can track progress regarding this publish/subscribe meaning: https://github.com/asyncapi/spec/issues/520. Happy to submit a PR :) ### Are you willing to submit PR? - [X] Yes I am willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
