You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Identifying timestamps and other time related data, e.g. via semantic tagging.
Need to discuss data formats for timestamps, time intervals, align with Web API.
Time series data also needs to be considered for historical data management.
See also time ontology W3C standard.
The text was updated successfully, but these errors were encountered:
We discussed the security risk mentioned in the geolocation use case (timing attacks, SPECTRE, etc) in the Security call and realized that beside geolocation, another use case where timing shows up is media. You need it for frame timing, audio synchronization, and other purposes. But if the timestamps are TOO accurate you run some security risks. Here are some links... note that this is about executing untrusted code, which may or may be applicable to the WoT context, and other mitigations are also possible besides lowering the resolution of timers.
Identifying timestamps and other time related data, e.g. via semantic tagging.
Need to discuss data formats for timestamps, time intervals, align with Web API.
Time series data also needs to be considered for historical data management.
See also time ontology W3C standard.
The text was updated successfully, but these errors were encountered: