Supporting Sleepy Devices

[egekorkan]

Note: This should be formulated as a user story on use cases repo once the template is ready. This was a plugfest outcome presented by @mkovatsc

• Who (As a...): Consumer Application developer
• What (I need...): Indication that a device is sleepy and cannot be always communicated with. Ideally how often can the device be communicated with (every 10 mins etc)
• Why (so that I can...): Handle request timeout differently and communicate only when the device is available
  • Details: Without this, an Consumer implementation simply thinks that the device is not available. It will be available at some point and the request should be sent only at that time.

See: https://github.com/w3c/wot/blob/main/PRESENTATIONS/2024-11-wot-week/Plugfest/plugfest-summary-mkovatsc.pptx

[chachamimm]

I think it is important for the Use Cases. I think we should clarify the typical process of sleepy devices.