From 1f9be26fa5536c8b7a6f71bbe6a8adf8e6bb131a Mon Sep 17 00:00:00 2001 From: Eric Murray Date: Fri, 21 Nov 2025 11:35:30 +0000 Subject: [PATCH 1/2] Clarify LastStatusTime description in YAML Updated the description of LastStatusTime to clarify its meaning and potential limitations. --- code/API_definitions/device-roaming-status.yaml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/code/API_definitions/device-roaming-status.yaml b/code/API_definitions/device-roaming-status.yaml index 6dfa10c..4c2a3b2 100644 --- a/code/API_definitions/device-roaming-status.yaml +++ b/code/API_definitions/device-roaming-status.yaml @@ -214,9 +214,8 @@ components: LastStatusTime: description: | - Last time that the associated device reachability status was updated. + The last time that the device roaming status was confirmed to be correct by the API provider. It might not be possible to provide the current status becuase, for example, the device may not be connected to any mobile network. It must follow [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) and must have time zone. - Recommended format is yyyy-MM-dd'T'HH:mm:ss.SSSZ (i.e. which allows 2023-07-03T14:27:08.312+02:00 or 2023-07-03T12:27:08.312Z) type: string format: date-time example: "2024-02-20T10:41:38.657Z" From 60fd99cb9c87a05cc18947ff70e6fe4ebaa8b370 Mon Sep 17 00:00:00 2001 From: Eric Murray Date: Fri, 21 Nov 2025 14:10:20 +0000 Subject: [PATCH 2/2] Fix typo in LastStatusTime description Corrected a typo in the LastStatusTime description. --- code/API_definitions/device-roaming-status.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/API_definitions/device-roaming-status.yaml b/code/API_definitions/device-roaming-status.yaml index 4c2a3b2..6270cca 100644 --- a/code/API_definitions/device-roaming-status.yaml +++ b/code/API_definitions/device-roaming-status.yaml @@ -214,7 +214,7 @@ components: LastStatusTime: description: | - The last time that the device roaming status was confirmed to be correct by the API provider. It might not be possible to provide the current status becuase, for example, the device may not be connected to any mobile network. + The last time that the device roaming status was confirmed to be correct by the API provider. It might not be possible to provide the current status because, for example, the device may not be connected to any mobile network. It must follow [RFC 3339](https://datatracker.ietf.org/doc/html/rfc3339#section-5.6) and must have time zone. type: string format: date-time