Differentiation between Queries and Views/Responses about domain-message-flow-modelling

[NTCoding]

Hey @alexlawrence. This is a good point, thanks for raising. The docs need a bit of a refresh and I was planning to make some updates when I get time. I'm just a bit busy during this period.

Whenever I want to show the parameters of a request and the schema of a response I usually do something basic like this:

But there are no strict rules. If you have other ideas feel free to share them in here.

[NTCoding]

Sorry for the long delay in replying. I've been travelling a lot through May and June.

Basically, the arrow represents the flow from conversation initiator. So if you view a query message as a question, the arrow goes from the collaborator asking the question to the collaborator that receives the question and responds to it (as you suggested).

Again, sorry for the delay.

[alexlawrence]

Thanks for the response. I didn't think of this, that's a good idea. So basically Queries/Responses will appear as one element and the additional context describes the contents of both messages.

Which direction does the arrow go then? I assume from the issuer of a query to the part that receives it, or?

[yellowbrickc]

Thanks for this discussion @alexlawrence, @NTCoding. I added your proposal (and pic 😆 ) to the readme.

[alexlawrence]

Sorry for the long delay in replying. I've been travelling a lot through May and June.

No need to apologize. Thanks for the answer!