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
Timestamps for actions and events in the gateway API are currently in the format 2022-01-20T17:21:12+00:00.
The latest draft of the W3C WoT Profile specification constrains the date format so that it must end in "Z".
If and when w3c/wot-profile#119 and w3c/wot-profile#127 land, I suggest changing action.ts and event.ts to use Date().toISOString() directly rather than Utils.timestamp(), which should output the expected date format.
The latest draft of WoT Profile only requires that timestamps conform to RFC3339, which does allow both numerical timezone offsets and "Z". As I understand it that means the timestamps used by the gateway do now comply with the specification.
However, I think we should still change the gateway to use Date().toISOString() directly to allow millisecond precision timestamps.
Timestamps for actions and events in the gateway API are currently in the format
2022-01-20T17:21:12+00:00
.The latest draft of the W3C WoT Profile specification constrains the date format so that it must end in "Z".
If and when w3c/wot-profile#119 and w3c/wot-profile#127 land, I suggest changing action.ts and event.ts to use Date().toISOString() directly rather than Utils.timestamp(), which should output the expected date format.
See WebThingsIO/gateway-addon-node#106 for more information.
The text was updated successfully, but these errors were encountered: