However, this exists for other protocols and theoretically, all devices has such a limit. Failing to comply with this limit from the Consumer side will result in errors or misbehavior of the Thing. Even if the device cannot limit itself, a gateway can pick up this information and limit the northbound requests.
An early analysis brings the requirement of a keyword to indicate this limit in a protocol-agnostic way. However, there should be also guidance or assertions for the Consumer to follow.
Once we agree on the use case submission process, I can reword this in that template but for now this is fine from our point of view.
Many devices have a limit of how many requests can be sent per second or minute. In Modbus, it is defined with the polling rate: https://w3c.github.io/wot-binding-templates/bindings/protocols/modbus/#form-terms
However, this exists for other protocols and theoretically, all devices has such a limit. Failing to comply with this limit from the Consumer side will result in errors or misbehavior of the Thing. Even if the device cannot limit itself, a gateway can pick up this information and limit the northbound requests.
An early analysis brings the requirement of a keyword to indicate this limit in a protocol-agnostic way. However, there should be also guidance or assertions for the Consumer to follow.
Once we agree on the use case submission process, I can reword this in that template but for now this is fine from our point of view.