search

OpenMobileAlliance / OMA_LwM2M_for_Developers

OMA LightweightM2M public resources.
http://openmobilealliance.github.io/OMA_LwM2M_for_Developers/
Other
239 stars 52 forks source link

Extend or clarify use cases for SenML timestamped values #567

Open cw8466 opened 1 year ago

cw8466 commented 1 year ago

As written, the specification leads to believe that the use case for SenML timestamped values is limited to stored notifications:

which allows for multiple versions of representations to be sent in the same payload

Historical version of notifications are typically generated when "Notification Storing When Disabled or Offline" resource of the LwM2M Server Object is set to true

which leads to interoperability issues as some implementations assume that it doesn't make sense to receive SenML timestamped values from arbitrary operations (ex.: ReadResponse, Send) and entirely reject those.

I believe it would make sense to extend the use cases to address the need to precisely timestamp values, not only store notifications.

sbernard31 commented 1 year ago

This is relative to : https://github.com/OpenMobileAlliance/OMA_LwM2M_for_Developers/issues/538#issuecomment-1034026449.

sbernard31 commented 5 months ago

Some clarification about what I think of timestamp usage in LWM2M : https://github.com/eclipse-leshan/leshan/issues/1623