docs: align text about send receive and publisher and subscriber

[derberg]

• it is mainly to align definitions with current actions. So instead of Producer and Consumer we have Sender and Receiver. Later in docs we can have more details with diagrams, that receiver can be, that it can be processor, or consumer and what is the difference. So basically Sender and Receiver are more generic and match the new action prop
• application can also be a broker
• operations are not mandatory really

---

some more context https://youtu.be/7urTb207V-8?t=229

[fmvilas]

I don't think this change applies. This consumer has nothing to do with producer/consumer stuff.

Suggested change

	- default - The default value represents what would be assumed by the receiver of the input as the value of the schema if one is not provided. Unlike JSON Schema, the value MUST conform to the defined type for the Schema Object defined at the same level. For example, of `type` is `string`, then `default` can be `"foo"` but cannot be `1`.
	- default - The default value represents what would be assumed by the consumer of the input as the value of the schema if one is not provided. Unlike JSON Schema, the value MUST conform to the defined type for the Schema Object defined at the same level. For example, of `type` is `string`, then `default` can be `"foo"` but cannot be `1`.

[derberg]

but in the end it related to schema of message,

The default value represents what would be assumed by the consumer

I think consumer here means the consumer of the message described with the schema

[fmvilas]

But "consumer" of the JSON Schema may just be a code generation tool for the producer. So the "consumer" here would really be the producer, actually 😅

[derberg]

to be honest, in general The default value represents what would be assumed by the receiver of the input as the value of the schema if one is not provided sentence is complicated, but the concept is easy.

chatGPT gave me this as better option and I love it: It acts as a standard value to be assumed in case no specific value is provided. or Use it to specify that property has a predefined value if no other value is present

no receiver, subscriber, producer, or whatever

thoughts?

[fmvilas]

Love this one:

Use it to specify that a property has a predefined value if no other value is present

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[dalelane]

not as bad as the can of worms I feared when I saw the title about "publisher/subscriber" "send/receive" ;-)

[derberg]

@smoya @fmvilas @char0n all good from your side?

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[derberg]

one small sentence change

@dalelane wanna have a look?

@fmvilas 🙏🏼

[fmvilas]

👍

[smoya]

LGTM! 🚀🌔 Thanks for the changes @derberg 🙌

As a side note, I had to think about why we moved from Subscribe/Publish to Send/Receive.

Even though I actively participated in the original discussion and I completely agreed with that.

That means It could make sense to add a line in the docs clarifying why we do not use the words Subscribe/Publish anymore. WDYT? Obviously, all in a separate issue and PR.

[derberg]

@smoya good point, issue created asyncapi/website#1873

/rtm

[asyncapi-bot]

🎉 This PR is included in version 3.0.0-next-major-spec.13 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀