From 1eac5af092ee9040322103333ef6fa3d677aed9a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 19:10:51 +0100
Subject: [PATCH 01/58] Update connected-network-type-subscriptions.yaml
---
.../API_definitions/connected-network-type-subscriptions.yaml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/code/API_definitions/connected-network-type-subscriptions.yaml b/code/API_definitions/connected-network-type-subscriptions.yaml
index d300f008..9ea7d2f7 100644
--- a/code/API_definitions/connected-network-type-subscriptions.yaml
+++ b/code/API_definitions/connected-network-type-subscriptions.yaml
@@ -102,14 +102,14 @@ info:
license:
name: Apache 2.0
url: https://www.apache.org/licenses/LICENSE-2.0.html
- version: wip
+ version: 0.1.0
x-camara-commonalities: 0.5
externalDocs:
description: Product documentation at Camara
url: https://github.com/camaraproject/DeviceStatus
servers:
- - url: "{apiRoot}/connected-network-type-subscriptions/vwip"
+ - url: "{apiRoot}/connected-network-type-subscriptions/v0.1"
variables:
apiRoot:
default: http://localhost:9091
From b501cca3c85c8c6c4f444c2f47cb6faeb6dac46f Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 19:11:20 +0100
Subject: [PATCH 02/58] Update connected-network-type.yaml
---
code/API_definitions/connected-network-type.yaml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/code/API_definitions/connected-network-type.yaml b/code/API_definitions/connected-network-type.yaml
index 0bbb59bd..bf9a8d97 100644
--- a/code/API_definitions/connected-network-type.yaml
+++ b/code/API_definitions/connected-network-type.yaml
@@ -73,14 +73,14 @@ info:
license:
name: Apache 2.0
url: https://www.apache.org/licenses/LICENSE-2.0.html
- version: wip
+ version: 0.1.0
x-camara-commonalities: 0.5
externalDocs:
description: Product documentation at CAMARA
url: https://github.com/camaraproject/DeviceStatus
servers:
- - url: "{apiRoot}/connected-network-type/vwip"
+ - url: "{apiRoot}/connected-network-type/v0.1"
variables:
apiRoot:
default: http://localhost:9091
From c0e7794deea43241e9be32f306b530021e865e6d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 19:11:52 +0100
Subject: [PATCH 03/58] Update device-reachability-status-subscriptions.yaml
---
.../device-reachability-status-subscriptions.yaml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/code/API_definitions/device-reachability-status-subscriptions.yaml b/code/API_definitions/device-reachability-status-subscriptions.yaml
index d1812d52..4140f295 100644
--- a/code/API_definitions/device-reachability-status-subscriptions.yaml
+++ b/code/API_definitions/device-reachability-status-subscriptions.yaml
@@ -111,14 +111,14 @@ info:
license:
name: Apache 2.0
url: https://www.apache.org/licenses/LICENSE-2.0.html
- version: wip
+ version: 0.7.0
x-camara-commonalities: 0.5
externalDocs:
description: Product documentation at CAMARA
url: https://github.com/camaraproject/DeviceStatus
servers:
- - url: "{apiRoot}/device-reachability-status-subscriptions/vwip"
+ - url: "{apiRoot}/device-reachability-status-subscriptions/v0.7"
variables:
apiRoot:
default: http://localhost:9091
From 8738c9387d218d6fcee8e2befc36da830bf9f847 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 19:12:26 +0100
Subject: [PATCH 04/58] Update device-reachability-status.yaml
---
code/API_definitions/device-reachability-status.yaml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/code/API_definitions/device-reachability-status.yaml b/code/API_definitions/device-reachability-status.yaml
index 24cf17d8..8261812e 100644
--- a/code/API_definitions/device-reachability-status.yaml
+++ b/code/API_definitions/device-reachability-status.yaml
@@ -70,14 +70,14 @@ info:
license:
name: Apache 2.0
url: https://www.apache.org/licenses/LICENSE-2.0.html
- version: wip
+ version: 1.0.0
x-camara-commonalities: 0.5
externalDocs:
description: Product documentation at CAMARA
url: https://github.com/camaraproject/DeviceStatus
servers:
- - url: "{apiRoot}/device-reachability-status/vwip"
+ - url: "{apiRoot}/device-reachability-status/v1"
variables:
apiRoot:
default: http://localhost:9091
From edfc7cdd997f7d1ac5c33c78fb854c1a32c98256 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 19:13:01 +0100
Subject: [PATCH 05/58] Update device-roaming-status-subscriptions.yaml
---
code/API_definitions/device-roaming-status-subscriptions.yaml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/code/API_definitions/device-roaming-status-subscriptions.yaml b/code/API_definitions/device-roaming-status-subscriptions.yaml
index 0ed6e436..736e3af4 100644
--- a/code/API_definitions/device-roaming-status-subscriptions.yaml
+++ b/code/API_definitions/device-roaming-status-subscriptions.yaml
@@ -131,14 +131,14 @@ info:
license:
name: Apache 2.0
url: https://www.apache.org/licenses/LICENSE-2.0.html
- version: wip
+ version: 0.7.0
x-camara-commonalities: 0.5
externalDocs:
description: Product documentation at CAMARA
url: https://github.com/camaraproject/DeviceStatus
servers:
- - url: "{apiRoot}/device-roaming-status-subscriptions/vwip"
+ - url: "{apiRoot}/device-roaming-status-subscriptions/v0.7"
variables:
apiRoot:
default: http://localhost:9091
From 0526a83247352196db79cc9871b7c8f2c6974355 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 19:13:27 +0100
Subject: [PATCH 06/58] Update device-roaming-status.yaml
---
code/API_definitions/device-roaming-status.yaml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/code/API_definitions/device-roaming-status.yaml b/code/API_definitions/device-roaming-status.yaml
index 62c783a7..60b846f9 100644
--- a/code/API_definitions/device-roaming-status.yaml
+++ b/code/API_definitions/device-roaming-status.yaml
@@ -78,14 +78,14 @@ info:
license:
name: Apache 2.0
url: https://www.apache.org/licenses/LICENSE-2.0.html
- version: wip
+ version: 1.0.0
x-camara-commonalities: 0.5
externalDocs:
description: Product documentation at CAMARA
url: https://github.com/camaraproject/DeviceStatus
servers:
- - url: "{apiRoot}/device-roaming-status/vwip"
+ - url: "{apiRoot}/device-roaming-status/v1"
variables:
apiRoot:
default: http://localhost:9091
From cfdac685ca7eb6e22c46a290b3e306ae12761f49 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 19:15:43 +0100
Subject: [PATCH 07/58] Update connected-network-type-subscriptions.feature
---
.../connected-network-type-subscriptions.feature | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/code/Test_definitions/connected-network-type-subscriptions.feature b/code/Test_definitions/connected-network-type-subscriptions.feature
index 251233b9..bc183aca 100644
--- a/code/Test_definitions/connected-network-type-subscriptions.feature
+++ b/code/Test_definitions/connected-network-type-subscriptions.feature
@@ -1,5 +1,5 @@
@Connected_Network_Type_Subscription
-Feature: CAMARA Connected Network Type Subscriptions API, vwip - Operations createConnectedNetworkTypeSubscription, retrieveConnectedNetworkTypeSubscriptionList, retrieveConnectedNetworkTypeSubscription and deleteConnectedNetworkTypeSubscription
+Feature: CAMARA Connected Network Type Subscriptions API, v0.1.0 - Operations createConnectedNetworkTypeSubscription, retrieveConnectedNetworkTypeSubscriptionList, retrieveConnectedNetworkTypeSubscription and deleteConnectedNetworkTypeSubscription
# Input to be provided by the implementation to the tester
#
@@ -15,7 +15,7 @@ Feature: CAMARA Connected Network Type Subscriptions API, vwip - Operations crea
# References to OAS spec schemas refer to schemas specifies in connected-network-type-subscriptions.yaml
Background: Connected Network Type Subscriptions setup
- Given the resource "{apiroot}/connected-network-type-subscriptions/vwip" as base-url
+ Given the resource "{apiroot}/connected-network-type-subscriptions/v0.1" as base-url
And the header "Authorization" is set to a valid access token
And the header "x-correlator" is set to a UUID value
From 23a7d16484ed80124f96f023aae29a6611da23c2 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 19:16:21 +0100
Subject: [PATCH 08/58] Update connected-network-type.feature
---
code/Test_definitions/connected-network-type.feature | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/code/Test_definitions/connected-network-type.feature b/code/Test_definitions/connected-network-type.feature
index 10a8d35a..e149a3cf 100644
--- a/code/Test_definitions/connected-network-type.feature
+++ b/code/Test_definitions/connected-network-type.feature
@@ -1,5 +1,5 @@
@Connected_Network_Type
-Feature: CAMARA Connected Network Type API, vwip - Operation getConnectedNetworkType
+Feature: CAMARA Connected Network Type API, v0.1.0 - Operation getConnectedNetworkType
# Input to be provided by the implementation to the tester
#
# Implementation indications:
@@ -13,7 +13,7 @@ Feature: CAMARA Connected Network Type API, vwip - Operation getConnectedNetwork
# References to OAS spec schemas refer to schemas specifies in connected-network-type.yaml
Background: Common Connected Network Type setup
- Given the resource "{api-root}/connected-network-type/vwip/retrieve" set as base-url
+ Given the resource "{api-root}/connected-network-type/v0.1/retrieve" set as base-url
And the header "Content-Type" is set to "application/json"
And the header "Authorization" is set to a valid access token
And the header "x-correlator" is set to a UUID value
From 5314a27be7e94084b478eeea273ebc09199e47df Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 19:16:50 +0100
Subject: [PATCH 09/58] Update device-reachability-status-subscriptions.feature
---
.../device-reachability-status-subscriptions.feature | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/code/Test_definitions/device-reachability-status-subscriptions.feature b/code/Test_definitions/device-reachability-status-subscriptions.feature
index f8af2e0a..ffa28c26 100644
--- a/code/Test_definitions/device-reachability-status-subscriptions.feature
+++ b/code/Test_definitions/device-reachability-status-subscriptions.feature
@@ -1,5 +1,5 @@
@Device_Reachability_Status_Subscription
-Feature: Device Reachability Status Subscriptions API, vwip - Operations createDeviceReachabilityStatusSubscription, retrieveDeviceReachabilityStatusSubscriptionList, retrieveDeviceReachabilityStatusSubscription and deleteDeviceReachabilityStatusSubscription
+Feature: Device Reachability Status Subscriptions API, v0.7.0 - Operations createDeviceReachabilityStatusSubscription, retrieveDeviceReachabilityStatusSubscriptionList, retrieveDeviceReachabilityStatusSubscription and deleteDeviceReachabilityStatusSubscription
# Input to be provided by the implementation to the tester
#
@@ -15,7 +15,7 @@ Feature: Device Reachability Status Subscriptions API, vwip - Operations createD
# References to OAS spec schemas refer to schemas specifies in device-reachability-status-subscriptions.yaml
Background: Common Device Reachability Status Subscriptions setup
- Given the resource "{apiroot}/device-reachability-status-subscriptions/vwip" as base-url
+ Given the resource "{apiroot}/device-reachability-status-subscriptions/v0.7" as base-url
And the header "Authorization" is set to a valid access token
And the header "x-correlator" is set to a UUID value
From 6fa5ee6d82e09867675b1fb5145b2a13d80a6984 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 19:17:22 +0100
Subject: [PATCH 10/58] Update device-reachability-status.feature
---
code/Test_definitions/device-reachability-status.feature | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/code/Test_definitions/device-reachability-status.feature b/code/Test_definitions/device-reachability-status.feature
index fb1620e6..77192bb4 100644
--- a/code/Test_definitions/device-reachability-status.feature
+++ b/code/Test_definitions/device-reachability-status.feature
@@ -1,5 +1,5 @@
@Device_Reachability_Status
-Feature: CAMARA Device reachability status API, vwip - Operation getReachabilityStatus
+Feature: CAMARA Device reachability status API, v1.0.0 - Operation getReachabilityStatus
# Input to be provided by the implementation to the tester
#
# Implementation indications:
@@ -12,7 +12,7 @@ Feature: CAMARA Device reachability status API, vwip - Operation getReachability
# References to OAS spec schemas refer to schemas specifies in device-reachability-status.yaml
Background: Common getReachabilityStatus setup
- Given the resource "{api-root}/device-reachability-status/vwip/retrieve" set as base-url
+ Given the resource "{api-root}/device-reachability-status/v1/retrieve" set as base-url
And the header "Content-Type" is set to "application/json"
And the header "Authorization" is set to a valid access token
And the header "x-correlator" is set to a UUID value
From 35bb9b46760f72822660d1375b7b1bdf011ed193 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 19:17:54 +0100
Subject: [PATCH 11/58] Update device-roaming-status-subscriptions.feature
---
.../device-roaming-status-subscriptions.feature | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/code/Test_definitions/device-roaming-status-subscriptions.feature b/code/Test_definitions/device-roaming-status-subscriptions.feature
index 79595184..545e15cf 100644
--- a/code/Test_definitions/device-roaming-status-subscriptions.feature
+++ b/code/Test_definitions/device-roaming-status-subscriptions.feature
@@ -1,5 +1,5 @@
@Device_Status_Roaming_Subscription
-Feature: Device Roaming Status Subscriptions API, vwip - Operations createDeviceRoamingStatusSubscription, retrieveDeviceRoamingStatusSubscriptionList, retrieveDeviceRoamingStatusSubscription and deleteDeviceRoamingStatusSubscription
+Feature: Device Roaming Status Subscriptions API, v0.7.0 - Operations createDeviceRoamingStatusSubscription, retrieveDeviceRoamingStatusSubscriptionList, retrieveDeviceRoamingStatusSubscription and deleteDeviceRoamingStatusSubscription
# Input to be provided by the implementation to the tester
#
@@ -14,7 +14,7 @@ Feature: Device Roaming Status Subscriptions API, vwip - Operations createDevice
# References to OAS spec schemas refer to schemas specified in device-roaming-status-subscriptions.yaml
Background: Common Device Roaming Status Subscriptions setup
- Given the resource "{apiroot}/device-roaming-status-subscriptions/vwip" as base-url
+ Given the resource "{apiroot}/device-roaming-status-subscriptions/v0.7" as base-url
And the header "Authorization" is set to a valid access token
And the header "x-correlator" is set to a UUID value
From 4516deddfff249701a33e583b4535a70361336f7 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 19:18:38 +0100
Subject: [PATCH 12/58] Update device-roaming-status.feature
---
code/Test_definitions/device-roaming-status.feature | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/code/Test_definitions/device-roaming-status.feature b/code/Test_definitions/device-roaming-status.feature
index 5b9ebb92..176493f7 100644
--- a/code/Test_definitions/device-roaming-status.feature
+++ b/code/Test_definitions/device-roaming-status.feature
@@ -1,5 +1,5 @@
@Device_Roaming_Status
-Feature: CAMARA Device Roaming Status API, vwip - Operation getRoamingStatus
+Feature: CAMARA Device Roaming Status API, v1.0.0 - Operation getRoamingStatus
# Input to be provided by the implementation to the tester
#
# Implementation indications:
@@ -12,7 +12,7 @@ Feature: CAMARA Device Roaming Status API, vwip - Operation getRoamingStatus
# References to OAS spec schemas refer to schemas specifies in device-roaming-status.yaml
Background: Common getRoamingStatus setup
- Given the resource "{api-root}/device-roaming-status/vwip/retrieve" set as base-url
+ Given the resource "{api-root}/device-roaming-status/v1/retrieve" set as base-url
And the header "Content-Type" is set to "application/json"
And the header "Authorization" is set to a valid access token
And the header "x-correlator" is set to a UUID value
From 8681b92f6f6c03d093e027a618ae6613284b6071 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 20:33:50 +0100
Subject: [PATCH 13/58] Update
connected-network-type-API-Readiness-Checklist.md
---
.../connected-network-type-API-Readiness-Checklist.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/API_documentation/connected-network-type-API-Readiness-Checklist.md b/documentation/API_documentation/connected-network-type-API-Readiness-Checklist.md
index ce965d56..e15b837b 100644
--- a/documentation/API_documentation/connected-network-type-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/connected-network-type-API-Readiness-Checklist.md
@@ -1,6 +1,6 @@
# API Readiness Checklist
-Checklist for connected-network-type 0.1.0-rc.1 in r2.1.
+Checklist for connected-network-type 0.1.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
@@ -10,7 +10,7 @@ Checklist for connected-network-type 0.1.0-rc.1 in r2.1.
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
| 6 | User stories | O | O | O | M | N | |
-| 7 | Basic API test cases & documentation | O | M | M | M | N | /code/Test_definitions/connected-network-type.feature |
+| 7 | Basic API test cases & documentation | O | M | M | M | Y | /code/Test_definitions/connected-network-type.feature |
| 8 | Enhanced API test cases & documentation | O | O | O | M | N | |
| 9 | Test result statement | O | O | O | M | N | |
| 10 | API release numbering convention applied | M | M | M | M | Y | |
From 468aaa28154ba82d1cb0f89bb942a972a3a2ed50 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 20:34:16 +0100
Subject: [PATCH 14/58] Update
connected-network-type-subscriptions-API-Readiness-Checklist.md
---
...cted-network-type-subscriptions-API-Readiness-Checklist.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/API_documentation/connected-network-type-subscriptions-API-Readiness-Checklist.md b/documentation/API_documentation/connected-network-type-subscriptions-API-Readiness-Checklist.md
index 4db363d9..3434246e 100644
--- a/documentation/API_documentation/connected-network-type-subscriptions-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/connected-network-type-subscriptions-API-Readiness-Checklist.md
@@ -1,6 +1,6 @@
# API Readiness Checklist
-Checklist for connected-network-type-subscriptions 0.1.0-rc.1 in r2.1.
+Checklist for connected-network-type-subscriptions 0.1.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
@@ -10,7 +10,7 @@ Checklist for connected-network-type-subscriptions 0.1.0-rc.1 in r2.1.
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
| 6 | User stories | O | O | O | M | N | |
-| 7 | Basic API test cases & documentation | O | M | M | M | N | /code/Test_definitions/connected-network-type-subscriptions.feature |
+| 7 | Basic API test cases & documentation | O | M | M | M | Y | /code/Test_definitions/connected-network-type-subscriptions.feature |
| 8 | Enhanced API test cases & documentation | O | O | O | M | N | |
| 9 | Test result statement | O | O | O | M | N | |
| 10 | API release numbering convention applied | M | M | M | M | Y | |
From 2e7ff36b36ca34d11e0c738598cb223bf9dc9cb9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 20:36:59 +0100
Subject: [PATCH 15/58] Update
device-reachability-status-API-Readiness-Checklist.md
---
.../device-reachability-status-API-Readiness-Checklist.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md b/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
index b66d0f7b..849a56b7 100644
--- a/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
@@ -1,6 +1,6 @@
# API Readiness Checklist
-Checklist for device-reachability-status 1.0.0-rc.1 in r2.1.
+Checklist for device-reachability-status 1.0.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
@@ -9,10 +9,10 @@ Checklist for device-reachability-status 1.0.0-rc.1 in r2.1.
| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.2 |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
-| 6 | User stories | O | O | O | M | N | In progress, will be merged after RC1 |
+| 6 | User stories | O | O | O | M | Y | TODO |
| 7 | Basic API test cases & documentation | O | M | M | M | Y | /code/Test_definitions/device-reachability-status.feature |
-| 8 | Enhanced API test cases & documentation | O | O | O | M | N | In progress, will be merged after RC1 |
-| 9 | Test result statement | O | O | O | M | N | In progress, will be merged after RC1 |
+| 8 | Enhanced API test cases & documentation | O | O | O | M | Y | /code/Test_definitions/device-reachability-status.feature |
+| 9 | Test result statement | O | O | O | M | Y | TODO |
| 10 | API release numbering convention applied | M | M | M | M | Y | |
| 11 | Change log updated | M | M | M | M | Y | /CHANGELOG.md |
| 12 | Previous public release was certified | O | O | O | M | Y | |
From 280d1f9d01efeac26f89bded99177b4169de94f8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 20:37:41 +0100
Subject: [PATCH 16/58] Update
device-reachability-status-subscriptions-API-Readiness-Checklist.md
---
...reachability-status-subscriptions-API-Readiness-Checklist.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/API_documentation/device-reachability-status-subscriptions-API-Readiness-Checklist.md b/documentation/API_documentation/device-reachability-status-subscriptions-API-Readiness-Checklist.md
index af51fe48..a9b56d55 100644
--- a/documentation/API_documentation/device-reachability-status-subscriptions-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-reachability-status-subscriptions-API-Readiness-Checklist.md
@@ -1,6 +1,6 @@
# API Readiness Checklist
-Checklist for device-reachability-status-subscriptions 0.7.0-rc.1 in r2.1.
+Checklist for device-reachability-status-subscriptions 0.7.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
From 5830073eaa84276ec4ccd43bf28543f58a57c5af Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 20:38:24 +0100
Subject: [PATCH 17/58] Update device-roaming-status-API-Readiness-Checklist.md
---
.../device-roaming-status-API-Readiness-Checklist.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md b/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
index 87210291..5bcd2fd4 100644
--- a/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
@@ -1,6 +1,6 @@
# API Readiness Checklist
-Checklist for device-roaming-status 1.0.0-rc.1 in r2.1.
+Checklist for device-roaming-status 1.0.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
@@ -9,10 +9,10 @@ Checklist for device-roaming-status 1.0.0-rc.1 in r2.1.
| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.2 |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
-| 6 | User stories | O | O | O | M | N | In progress, will be merged after RC1 |
+| 6 | User stories | O | O | O | M | Y | TODO |
| 7 | Basic API test cases & documentation | O | M | M | M | Y | /code/Test_definitions/device-roaming-status.feature |
-| 8 | Enhanced API test cases & documentation | O | O | O | M | N | In progress, will be merged after RC1 |
-| 9 | Test result statement | O | O | O | M | N | In progress, will be merged after RC1 |
+| 8 | Enhanced API test cases & documentation | O | O | O | M | Y | /code/Test_definitions/device-roaming-status.feature |
+| 9 | Test result statement | O | O | O | M | Y | TODO |
| 10 | API release numbering convention applied | M | M | M | M | Y | |
| 11 | Change log updated | M | M | M | M | Y | /CHANGELOG.md |
| 12 | Previous public release was certified | O | O | O | M | Y | |
From f506f220e05821db3bf5e5f5f18f48867b31eb3d Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 20:38:58 +0100
Subject: [PATCH 18/58] Update
device-roaming-status-subscriptions-API-Readiness-Checklist.md
---
...vice-roaming-status-subscriptions-API-Readiness-Checklist.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/API_documentation/device-roaming-status-subscriptions-API-Readiness-Checklist.md b/documentation/API_documentation/device-roaming-status-subscriptions-API-Readiness-Checklist.md
index 12159d6e..d0291d28 100644
--- a/documentation/API_documentation/device-roaming-status-subscriptions-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-roaming-status-subscriptions-API-Readiness-Checklist.md
@@ -1,6 +1,6 @@
# API Readiness Checklist
-Checklist for device-roaming-status-subscriptions 0.7.0-rc.1 in r2.1.
+Checklist for device-roaming-status-subscriptions 0.7.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
From 5034ff9d130a2512f34ace7b7c58982dcd6469db Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 20:42:08 +0100
Subject: [PATCH 19/58] Update CHANGELOG.md
---
CHANGELOG.md | 132 +++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 132 insertions(+)
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 99c55f22..6f0173e0 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,6 @@
# Changelog DeviceStatus
## Table of Contents
+- [r2.2](#r22)
- [r2.1](#r21)
- [r1.3](#r13)
- [r1.2](#r12)
@@ -19,6 +20,137 @@ The below sections record the changes for each API version in each release as fo
- for the first release-candidate, all changes since the last public release
- for subsequent release-candidate(s), only the delta to the previous release-candidate
- for a public release, the consolidated changes since the previous public release
+# r2.2
+## Release Notes
+
+This pre-release contains the definition and documentation of
+* device-roaming-status v1.0.0
+* device-roaming-status-subscriptions v0.7.0
+* device-reachability-status v1.0.0
+* device-reachability-status-subscriptions v0.7.0
+* connected-network-type 0.1.0
+* connected-network-type-subscriptions 0.1.0
+
+The API definition(s) are based on
+* Commonalities v0.5.0
+* Identity and Consent Management v0.3.0
+
+## device-roaming-status v1.0.0
+
+- API definition **with inline documentation**:
+ - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-roaming-status.yaml&nocors)
+ - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-roaming-status.yaml)
+ - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.1/code/API_definitions/device-roaming-status.yaml)
+
+### Added
+
+### Changed
+* Update documentation with handling of access token and multi-SIM scenarios by @eric-murray in https://github.com/camaraproject/DeviceStatus/pull/228
+* Update device error model by @fernandopradocabrillo in https://github.com/camaraproject/DeviceStatus/pull/232
+
+### Fixed
+
+### Removed
+
+## device-roaming-status-subscriptions v0.7.0
+
+- API definition **with inline documentation**:
+ - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-roaming-status-subscriptions.yaml&nocors)
+ - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-roaming-status-subscriptions.yaml)
+ - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.1/code/API_definitions/device-roaming-status-subscriptions.yaml)
+
+### Added
+
+### Changed
+* Update documentation with handling of access token and multi-SIM scenarios by @eric-murray in https://github.com/camaraproject/DeviceStatus/pull/228
+* Update documentation with clarification for initialEvent by @bigludo7 in https://github.com/camaraproject/DeviceStatus/pull/237
+* Alignment with Commonalities Subscription Model - APIs Subscription by @sachinvodafone in https://github.com/camaraproject/DeviceStatus/pull/250
+
+### Fixed
+* Fix example for SUBSCRIPTION_ACTIVE by @sachinvodafone in https://github.com/camaraproject/DeviceStatus/pull/231
+* Fix dateTime literals by @sachinvodafone in https://github.com/camaraproject/DeviceStatus/pull/240
+
+### Removed
+* remove `allOf` in `sinkCredential` by @dfischer-tech in https://github.com/camaraproject/DeviceStatus/pull/226
+
+## device-reachability-status v1.0.0
+
+- API definition **with inline documentation**:
+ - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-reachability-status.yaml&nocors)
+ - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-reachability-status.yaml)
+ - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.1/code/API_definitions/device-reachability-status.yaml)
+
+### Added
+
+### Changed
+* rework reachability-status to support reachability with multiple connectivity-types by @maxl2287 in https://github.com/camaraproject/DeviceStatus/pull/221
+* Update documentation with handling of access token and multi-SIM scenarios by @eric-murray in https://github.com/camaraproject/DeviceStatus/pull/228
+* Update device error model by @fernandopradocabrillo in https://github.com/camaraproject/DeviceStatus/pull/232
+
+### Fixed
+
+### Removed
+
+## device-reachability-status-subscriptions v0.7.0
+
+- API definition **with inline documentation**:
+ - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-reachability-status-subscriptions.yaml&nocors)
+ - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-reachability-status-subscriptions.yaml)
+ - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.1/code/API_definitions/device-reachability-status-subscriptions.yaml)
+
+### Added
+
+### Changed
+* Update documentation with handling of access token and multi-SIM scenarios by @eric-murray in https://github.com/camaraproject/DeviceStatus/pull/228
+* Update documentation with clarification for initialEvent by @bigludo7 in https://github.com/camaraproject/DeviceStatus/pull/237
+* Alignment with Commonalities Subscription Model - APIs Subscription by @sachinvodafone in https://github.com/camaraproject/DeviceStatus/pull/250
+
+### Fixed
+* Fix example for SUBSCRIPTION_ACTIVE by @sachinvodafone in https://github.com/camaraproject/DeviceStatus/pull/231
+* Fix dateTime literals by @sachinvodafone in https://github.com/camaraproject/DeviceStatus/pull/240
+
+### Removed
+* remove `allOf` in `sinkCredential` by @dfischer-tech in https://github.com/camaraproject/DeviceStatus/pull/226
+
+## connected-network-type v0.1.0
+
+- API definition **with inline documentation**:
+ - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/connected-network-type.yaml&nocors)
+ - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/connected-network-type.yaml)
+ - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.1/code/API_definitions/connected-network-type.yaml)
+
+### Added
+* Create connected-network-type.yaml by @gmuratk in https://github.com/camaraproject/DeviceStatus/pull/158
+
+### Changed
+* Update documentation with handling of access token and multi-SIM scenarios by @eric-murray in https://github.com/camaraproject/DeviceStatus/pull/228
+* Update device error model by @fernandopradocabrillo in https://github.com/camaraproject/DeviceStatus/pull/232
+
+### Fixed
+
+### Removed
+
+## connected-network-type-subscriptions v0.1.0
+
+- API definition **with inline documentation**:
+ - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/connected-network-type-subscriptions.yaml&nocors)
+ - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/connected-network-type-subscriptions.yaml)
+ - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.1/code/API_definitions/connected-network-type-subscriptions.yaml)
+
+### Added
+* Create connected-network-type-subscriptions.yaml by @VijayKesharwani in https://github.com/camaraproject/DeviceStatus/pull/171
+
+### Changed
+* Update documentation with handling of access token and multi-SIM scenarios by @eric-murray in https://github.com/camaraproject/DeviceStatus/pull/228
+* Update documentation with clarification for initialEvent by @bigludo7 in https://github.com/camaraproject/DeviceStatus/pull/247
+* Alignment with Commonalities Subscription Model - APIs Subscription by @sachinvodafone in https://github.com/camaraproject/DeviceStatus/pull/250
+
+### Fixed
+* Fix dateTime literals by @sachinvodafone in https://github.com/camaraproject/DeviceStatus/pull/240
+
+### Removed
+
+**Full Changelog**: https://github.com/camaraproject/DeviceStatus/compare/r1.3...r2.2
# r2.1
## Release Notes
From 882248f16de03a87c15129611edb18ea6c221ef4 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 20:45:04 +0100
Subject: [PATCH 20/58] Update CHANGELOG.md
---
CHANGELOG.md | 36 ++++++++++++++++++------------------
1 file changed, 18 insertions(+), 18 deletions(-)
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 6f0173e0..8cd399f6 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -38,9 +38,9 @@ The API definition(s) are based on
## device-roaming-status v1.0.0
- API definition **with inline documentation**:
- - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-roaming-status.yaml&nocors)
- - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-roaming-status.yaml)
- - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.1/code/API_definitions/device-roaming-status.yaml)
+ - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.2/code/API_definitions/device-roaming-status.yaml&nocors)
+ - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.2/code/API_definitions/device-roaming-status.yaml)
+ - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.2/code/API_definitions/device-roaming-status.yaml)
### Added
@@ -55,9 +55,9 @@ The API definition(s) are based on
## device-roaming-status-subscriptions v0.7.0
- API definition **with inline documentation**:
- - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-roaming-status-subscriptions.yaml&nocors)
- - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-roaming-status-subscriptions.yaml)
- - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.1/code/API_definitions/device-roaming-status-subscriptions.yaml)
+ - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.2/code/API_definitions/device-roaming-status-subscriptions.yaml&nocors)
+ - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.2/code/API_definitions/device-roaming-status-subscriptions.yaml)
+ - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.2/code/API_definitions/device-roaming-status-subscriptions.yaml)
### Added
@@ -76,9 +76,9 @@ The API definition(s) are based on
## device-reachability-status v1.0.0
- API definition **with inline documentation**:
- - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-reachability-status.yaml&nocors)
- - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-reachability-status.yaml)
- - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.1/code/API_definitions/device-reachability-status.yaml)
+ - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.2/code/API_definitions/device-reachability-status.yaml&nocors)
+ - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.2/code/API_definitions/device-reachability-status.yaml)
+ - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.2/code/API_definitions/device-reachability-status.yaml)
### Added
@@ -94,9 +94,9 @@ The API definition(s) are based on
## device-reachability-status-subscriptions v0.7.0
- API definition **with inline documentation**:
- - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-reachability-status-subscriptions.yaml&nocors)
- - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/device-reachability-status-subscriptions.yaml)
- - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.1/code/API_definitions/device-reachability-status-subscriptions.yaml)
+ - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.2/code/API_definitions/device-reachability-status-subscriptions.yaml&nocors)
+ - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.2/code/API_definitions/device-reachability-status-subscriptions.yaml)
+ - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.2/code/API_definitions/device-reachability-status-subscriptions.yaml)
### Added
@@ -115,9 +115,9 @@ The API definition(s) are based on
## connected-network-type v0.1.0
- API definition **with inline documentation**:
- - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/connected-network-type.yaml&nocors)
- - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/connected-network-type.yaml)
- - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.1/code/API_definitions/connected-network-type.yaml)
+ - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.2/code/API_definitions/connected-network-type.yaml&nocors)
+ - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.2/code/API_definitions/connected-network-type.yaml)
+ - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.2/code/API_definitions/connected-network-type.yaml)
### Added
* Create connected-network-type.yaml by @gmuratk in https://github.com/camaraproject/DeviceStatus/pull/158
@@ -133,9 +133,9 @@ The API definition(s) are based on
## connected-network-type-subscriptions v0.1.0
- API definition **with inline documentation**:
- - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/connected-network-type-subscriptions.yaml&nocors)
- - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.1/code/API_definitions/connected-network-type-subscriptions.yaml)
- - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.1/code/API_definitions/connected-network-type-subscriptions.yaml)
+ - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.2/code/API_definitions/connected-network-type-subscriptions.yaml&nocors)
+ - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r2.2/code/API_definitions/connected-network-type-subscriptions.yaml)
+ - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r2.2/code/API_definitions/connected-network-type-subscriptions.yaml)
### Added
* Create connected-network-type-subscriptions.yaml by @VijayKesharwani in https://github.com/camaraproject/DeviceStatus/pull/171
From 730d7fb5689b35474d5658ed0779d37f9135bc67 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Sun, 2 Mar 2025 20:51:45 +0100
Subject: [PATCH 21/58] Update CHANGELOG.md
---
CHANGELOG.md | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 8cd399f6..96fe30ac 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -65,6 +65,7 @@ The API definition(s) are based on
* Update documentation with handling of access token and multi-SIM scenarios by @eric-murray in https://github.com/camaraproject/DeviceStatus/pull/228
* Update documentation with clarification for initialEvent by @bigludo7 in https://github.com/camaraproject/DeviceStatus/pull/237
* Alignment with Commonalities Subscription Model - APIs Subscription by @sachinvodafone in https://github.com/camaraproject/DeviceStatus/pull/250
+* Change event notification sink format from url to uri by @eric-murray in https://github.com/camaraproject/DeviceStatus/pull/260
### Fixed
* Fix example for SUBSCRIPTION_ACTIVE by @sachinvodafone in https://github.com/camaraproject/DeviceStatus/pull/231
@@ -104,6 +105,7 @@ The API definition(s) are based on
* Update documentation with handling of access token and multi-SIM scenarios by @eric-murray in https://github.com/camaraproject/DeviceStatus/pull/228
* Update documentation with clarification for initialEvent by @bigludo7 in https://github.com/camaraproject/DeviceStatus/pull/237
* Alignment with Commonalities Subscription Model - APIs Subscription by @sachinvodafone in https://github.com/camaraproject/DeviceStatus/pull/250
+* Change event notification sink format from url to uri by @eric-murray in https://github.com/camaraproject/DeviceStatus/pull/260
### Fixed
* Fix example for SUBSCRIPTION_ACTIVE by @sachinvodafone in https://github.com/camaraproject/DeviceStatus/pull/231
@@ -123,8 +125,6 @@ The API definition(s) are based on
* Create connected-network-type.yaml by @gmuratk in https://github.com/camaraproject/DeviceStatus/pull/158
### Changed
-* Update documentation with handling of access token and multi-SIM scenarios by @eric-murray in https://github.com/camaraproject/DeviceStatus/pull/228
-* Update device error model by @fernandopradocabrillo in https://github.com/camaraproject/DeviceStatus/pull/232
### Fixed
@@ -141,12 +141,8 @@ The API definition(s) are based on
* Create connected-network-type-subscriptions.yaml by @VijayKesharwani in https://github.com/camaraproject/DeviceStatus/pull/171
### Changed
-* Update documentation with handling of access token and multi-SIM scenarios by @eric-murray in https://github.com/camaraproject/DeviceStatus/pull/228
-* Update documentation with clarification for initialEvent by @bigludo7 in https://github.com/camaraproject/DeviceStatus/pull/247
-* Alignment with Commonalities Subscription Model - APIs Subscription by @sachinvodafone in https://github.com/camaraproject/DeviceStatus/pull/250
### Fixed
-* Fix dateTime literals by @sachinvodafone in https://github.com/camaraproject/DeviceStatus/pull/240
### Removed
From daa71c48934ff09b775d5dd6c2c48a6d2b2f93cb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Mon, 3 Mar 2025 10:27:33 +0100
Subject: [PATCH 22/58] Create device-roaming-status-User-Story.md
---
.../API_documentation/device-roaming-status-User-Story.md | 1 +
1 file changed, 1 insertion(+)
create mode 100644 documentation/API_documentation/device-roaming-status-User-Story.md
diff --git a/documentation/API_documentation/device-roaming-status-User-Story.md b/documentation/API_documentation/device-roaming-status-User-Story.md
new file mode 100644
index 00000000..1333ed77
--- /dev/null
+++ b/documentation/API_documentation/device-roaming-status-User-Story.md
@@ -0,0 +1 @@
+TODO
From cbf7944074151b092261f20134389d486dbb9c35 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Mon, 3 Mar 2025 10:27:56 +0100
Subject: [PATCH 23/58] Create device-reachability-status-User-Story.md
---
.../API_documentation/device-reachability-status-User-Story.md | 1 +
1 file changed, 1 insertion(+)
create mode 100644 documentation/API_documentation/device-reachability-status-User-Story.md
diff --git a/documentation/API_documentation/device-reachability-status-User-Story.md b/documentation/API_documentation/device-reachability-status-User-Story.md
new file mode 100644
index 00000000..1333ed77
--- /dev/null
+++ b/documentation/API_documentation/device-reachability-status-User-Story.md
@@ -0,0 +1 @@
+TODO
From ed767159cd12c0f8f5a290f9743b4b6d19c62831 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Mon, 3 Mar 2025 10:31:05 +0100
Subject: [PATCH 24/58] Update device-reachability-status-User-Story.md
---
.../device-reachability-status-User-Story.md | 38 ++++++++++++++++++-
1 file changed, 37 insertions(+), 1 deletion(-)
diff --git a/documentation/API_documentation/device-reachability-status-User-Story.md b/documentation/API_documentation/device-reachability-status-User-Story.md
index 1333ed77..55e8ce46 100644
--- a/documentation/API_documentation/device-reachability-status-User-Story.md
+++ b/documentation/API_documentation/device-reachability-status-User-Story.md
@@ -1 +1,37 @@
-TODO
+# User Story Template
+This document specifies the template for documenting user stories related to API families in CAMARA project.
+
+| Item | Description | Support Qualifier |
+|---------------------------|-------------|-------------------|
+| Summary | | M |
+| Roles, Actor(s) and scope | | M |
+| NF Requirements | | O |
+| Pre-conditions | | M |
+| Begins when | | M |
+| Step 1 | | (M/O/CM) |
+| Step 2 | | (M/O/CM |
+| ... | | (M/O/CM) |
+| Step N | | (M/O/CM) |
+| Ends when | | M |
+| Post-conditions | | M |
+| Exceptions | | M |
+
+
+Some notes related to the above template:
+
+- The **Support Qualifier** column allows capturing the need for specifying the item. _Options -> M (Mandatory); O (Optional); CM (Conditional Mandatory)_.
+- The **Summary** item provides a user story description as a user persona, following the same syntax structure -> "**As a** (Persona), **I want** (Need), **so that** (Goal)".
+ - A user story based on _user persona_ focuses on expectations from the Point-of-View of an end-user. This is contrary to a user story based on _system persona_, which is designed to represent background system functions that do not require interaction from the end-user (i.e., elaborate on the behind-the-scenes integration tasks that are not user-centric).
+- The **Roles, Actor(s) and scope** item allows linking a user story with existing Cloud/NaaS reference architectures. The architectures that are within the scope of the CAMARA project are detailed in this document: [Reference.Architectures.pptx](/documentation/SupportingDocuments/Reference.Architectures.pptx)
+ - Roles: specifies the role(s) that the CAMARA API customer plays for the user story. _Options -> customer:user; customer:administrator; customer:business manager_.
+ - Actor(s): API usage should not be restricted to a particular actor (e.g., application service provider, hyperscaler, application developer, or end user where e.g. consent is required). Examples may use a particular actor to perform a role in the API flow, but that does not exclude other Actors from performing the role.
+ - Scope: specifies the service lifecycle area(s) that the user story impacts on. _Options -> Design time; Prospect to Order (P2O); Usage to Cash (U2C); Order to Activate (O2A); Trouble to Resolution (T2R)_.
+
+# Linking a user story to API design
+
+Once we have the user story, the next step is to clarify the **data journey** in the context of the target and source systems we are integrating:
+- Think about triggers for workflows: how and when does data need to be moved between the application and the service?
+- Think about dependencies of data objects: does the data in underlying objects need to be regularly kept in sync with another system?
+- Think about any parameters the user might need to configure or change. This is particularly important when building self-serve integrations for non-technical end users.
+- Think about privacy by design: does any data represent sensitive information, and how can this be safely shared/stored according to regulation (e.g., anonymisation, tokenisation, zero-trust principles)
+
From 5ec6486d28f3864d57ef0689937bf77294dc79ed Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Mon, 3 Mar 2025 10:31:26 +0100
Subject: [PATCH 25/58] Update device-roaming-status-User-Story.md
---
.../device-roaming-status-User-Story.md | 38 ++++++++++++++++++-
1 file changed, 37 insertions(+), 1 deletion(-)
diff --git a/documentation/API_documentation/device-roaming-status-User-Story.md b/documentation/API_documentation/device-roaming-status-User-Story.md
index 1333ed77..55e8ce46 100644
--- a/documentation/API_documentation/device-roaming-status-User-Story.md
+++ b/documentation/API_documentation/device-roaming-status-User-Story.md
@@ -1 +1,37 @@
-TODO
+# User Story Template
+This document specifies the template for documenting user stories related to API families in CAMARA project.
+
+| Item | Description | Support Qualifier |
+|---------------------------|-------------|-------------------|
+| Summary | | M |
+| Roles, Actor(s) and scope | | M |
+| NF Requirements | | O |
+| Pre-conditions | | M |
+| Begins when | | M |
+| Step 1 | | (M/O/CM) |
+| Step 2 | | (M/O/CM |
+| ... | | (M/O/CM) |
+| Step N | | (M/O/CM) |
+| Ends when | | M |
+| Post-conditions | | M |
+| Exceptions | | M |
+
+
+Some notes related to the above template:
+
+- The **Support Qualifier** column allows capturing the need for specifying the item. _Options -> M (Mandatory); O (Optional); CM (Conditional Mandatory)_.
+- The **Summary** item provides a user story description as a user persona, following the same syntax structure -> "**As a** (Persona), **I want** (Need), **so that** (Goal)".
+ - A user story based on _user persona_ focuses on expectations from the Point-of-View of an end-user. This is contrary to a user story based on _system persona_, which is designed to represent background system functions that do not require interaction from the end-user (i.e., elaborate on the behind-the-scenes integration tasks that are not user-centric).
+- The **Roles, Actor(s) and scope** item allows linking a user story with existing Cloud/NaaS reference architectures. The architectures that are within the scope of the CAMARA project are detailed in this document: [Reference.Architectures.pptx](/documentation/SupportingDocuments/Reference.Architectures.pptx)
+ - Roles: specifies the role(s) that the CAMARA API customer plays for the user story. _Options -> customer:user; customer:administrator; customer:business manager_.
+ - Actor(s): API usage should not be restricted to a particular actor (e.g., application service provider, hyperscaler, application developer, or end user where e.g. consent is required). Examples may use a particular actor to perform a role in the API flow, but that does not exclude other Actors from performing the role.
+ - Scope: specifies the service lifecycle area(s) that the user story impacts on. _Options -> Design time; Prospect to Order (P2O); Usage to Cash (U2C); Order to Activate (O2A); Trouble to Resolution (T2R)_.
+
+# Linking a user story to API design
+
+Once we have the user story, the next step is to clarify the **data journey** in the context of the target and source systems we are integrating:
+- Think about triggers for workflows: how and when does data need to be moved between the application and the service?
+- Think about dependencies of data objects: does the data in underlying objects need to be regularly kept in sync with another system?
+- Think about any parameters the user might need to configure or change. This is particularly important when building self-serve integrations for non-technical end users.
+- Think about privacy by design: does any data represent sensitive information, and how can this be safely shared/stored according to regulation (e.g., anonymisation, tokenisation, zero-trust principles)
+
From fe44605ffdd45daecd0ea460e63951498401240e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Mon, 3 Mar 2025 16:05:03 +0100
Subject: [PATCH 26/58] Update device-roaming-status-User-Story.md
---
.../device-roaming-status-User-Story.md | 34 +++++--------------
1 file changed, 9 insertions(+), 25 deletions(-)
diff --git a/documentation/API_documentation/device-roaming-status-User-Story.md b/documentation/API_documentation/device-roaming-status-User-Story.md
index 55e8ce46..2f197a64 100644
--- a/documentation/API_documentation/device-roaming-status-User-Story.md
+++ b/documentation/API_documentation/device-roaming-status-User-Story.md
@@ -1,31 +1,15 @@
-# User Story Template
-This document specifies the template for documenting user stories related to API families in CAMARA project.
+# Device Roaming Status User Story
| Item | Description | Support Qualifier |
|---------------------------|-------------|-------------------|
-| Summary | | M |
-| Roles, Actor(s) and scope | | M |
-| NF Requirements | | O |
-| Pre-conditions | | M |
-| Begins when | | M |
-| Step 1 | | (M/O/CM) |
-| Step 2 | | (M/O/CM |
-| ... | | (M/O/CM) |
-| Step N | | (M/O/CM) |
-| Ends when | | M |
-| Post-conditions | | M |
-| Exceptions | | M |
-
-
-Some notes related to the above template:
-
-- The **Support Qualifier** column allows capturing the need for specifying the item. _Options -> M (Mandatory); O (Optional); CM (Conditional Mandatory)_.
-- The **Summary** item provides a user story description as a user persona, following the same syntax structure -> "**As a** (Persona), **I want** (Need), **so that** (Goal)".
- - A user story based on _user persona_ focuses on expectations from the Point-of-View of an end-user. This is contrary to a user story based on _system persona_, which is designed to represent background system functions that do not require interaction from the end-user (i.e., elaborate on the behind-the-scenes integration tasks that are not user-centric).
-- The **Roles, Actor(s) and scope** item allows linking a user story with existing Cloud/NaaS reference architectures. The architectures that are within the scope of the CAMARA project are detailed in this document: [Reference.Architectures.pptx](/documentation/SupportingDocuments/Reference.Architectures.pptx)
- - Roles: specifies the role(s) that the CAMARA API customer plays for the user story. _Options -> customer:user; customer:administrator; customer:business manager_.
- - Actor(s): API usage should not be restricted to a particular actor (e.g., application service provider, hyperscaler, application developer, or end user where e.g. consent is required). Examples may use a particular actor to perform a role in the API flow, but that does not exclude other Actors from performing the role.
- - Scope: specifies the service lifecycle area(s) that the user story impacts on. _Options -> Design time; Prospect to Order (P2O); Usage to Cash (U2C); Order to Activate (O2A); Trouble to Resolution (T2R)_.
+| Summary | As an enterprise application developer, I want to query the roaming status of a user's device, so that I can determine if a device is in a foreign network and in which country it is located. This API can be used to identify fraud, ensure regulatory compliance, or enforce territorial restrictions on video and audio content. | M |
+| Roles, Actor(s) and scope | **Roles:** Customer:Developer
**Actors:** Application service providers (ASP), hyperscalers, application developers.
**Scope:** Order To Activate (OTA) - Get roaming status of a device | M |
+| NF Requirements | - | O |
+| Pre-conditions | - The customer:developer has been successfully onboarded to the API platform of the service provider
- The customer application has requested and received an access token with the required scope for the API | M |
+| Begins when | The customer application server makes a POST request to retrieve the roaming status of a user's device | M |
+| Ends when | The service provider returns the roaming status of the device with a timestamp when the status information was updated. In case of a roaming situation also the roaming country name and code shall be returned. | |
+| Post-conditions | - | M |
+| Exceptions | Several exceptions might occur during the API operations:
- Unauthorized: Invalid credentials (e.g., expired access token).
- Incorrect input data (e.g., malformed phone number).
- Not found: The phone number is not associated with a CSP customer account | M |
# Linking a user story to API design
From 87f06a6b1e99dc2939cace1377d86ab0835e1d27 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Mon, 3 Mar 2025 16:17:45 +0100
Subject: [PATCH 27/58] Update device-reachability-status-User-Story.md
---
.../device-reachability-status-User-Story.md | 35 +++++--------------
1 file changed, 9 insertions(+), 26 deletions(-)
diff --git a/documentation/API_documentation/device-reachability-status-User-Story.md b/documentation/API_documentation/device-reachability-status-User-Story.md
index 55e8ce46..dc997f2c 100644
--- a/documentation/API_documentation/device-reachability-status-User-Story.md
+++ b/documentation/API_documentation/device-reachability-status-User-Story.md
@@ -1,31 +1,15 @@
-# User Story Template
-This document specifies the template for documenting user stories related to API families in CAMARA project.
+# Device Reachability Status User Story
| Item | Description | Support Qualifier |
|---------------------------|-------------|-------------------|
-| Summary | | M |
-| Roles, Actor(s) and scope | | M |
-| NF Requirements | | O |
-| Pre-conditions | | M |
-| Begins when | | M |
-| Step 1 | | (M/O/CM) |
-| Step 2 | | (M/O/CM |
-| ... | | (M/O/CM) |
-| Step N | | (M/O/CM) |
-| Ends when | | M |
-| Post-conditions | | M |
-| Exceptions | | M |
-
-
-Some notes related to the above template:
-
-- The **Support Qualifier** column allows capturing the need for specifying the item. _Options -> M (Mandatory); O (Optional); CM (Conditional Mandatory)_.
-- The **Summary** item provides a user story description as a user persona, following the same syntax structure -> "**As a** (Persona), **I want** (Need), **so that** (Goal)".
- - A user story based on _user persona_ focuses on expectations from the Point-of-View of an end-user. This is contrary to a user story based on _system persona_, which is designed to represent background system functions that do not require interaction from the end-user (i.e., elaborate on the behind-the-scenes integration tasks that are not user-centric).
-- The **Roles, Actor(s) and scope** item allows linking a user story with existing Cloud/NaaS reference architectures. The architectures that are within the scope of the CAMARA project are detailed in this document: [Reference.Architectures.pptx](/documentation/SupportingDocuments/Reference.Architectures.pptx)
- - Roles: specifies the role(s) that the CAMARA API customer plays for the user story. _Options -> customer:user; customer:administrator; customer:business manager_.
- - Actor(s): API usage should not be restricted to a particular actor (e.g., application service provider, hyperscaler, application developer, or end user where e.g. consent is required). Examples may use a particular actor to perform a role in the API flow, but that does not exclude other Actors from performing the role.
- - Scope: specifies the service lifecycle area(s) that the user story impacts on. _Options -> Design time; Prospect to Order (P2O); Usage to Cash (U2C); Order to Activate (O2A); Trouble to Resolution (T2R)_.
+| Summary | As an enterprise application developer, I want to query the connectivity status of a user's device, so that I can determine whether the device is reachable via SMS, data (mobile internet), or both, enabling better communication or service management decisions based on real-time device availability. | M |
+| Roles, Actor(s) and scope | **Roles:** Customer:Developer
**Actors:** Application service providers (ASP), hyperscalers, application developers.
**Scope:** Order To Activate (OTA) - Get roaming status of a device | M |
+| NF Requirements | - | O |
+| Pre-conditions | - The customer:developer has been successfully onboarded to the API platform of the service provider
- The customer application has requested and received an access token with the required scope for the API | M |
+| Begins when | The customer application server makes a POST request to retrieve the roaming status of a user's device | M |
+| Ends when | The service provider returns the roaming status of the device with a timestamp when the status information was updated. In case of a roaming situation also the roaming country name and code shall be returned. | |
+| Post-conditions | - | M |
+| Exceptions | Several exceptions might occur during the API operations:
- Unauthorized: Invalid credentials (e.g., expired access token).
- Incorrect input data (e.g., malformed phone number).
- Not found: The phone number is not associated with a CSP customer account | M |
# Linking a user story to API design
@@ -34,4 +18,3 @@ Once we have the user story, the next step is to clarify the **data journey** in
- Think about dependencies of data objects: does the data in underlying objects need to be regularly kept in sync with another system?
- Think about any parameters the user might need to configure or change. This is particularly important when building self-serve integrations for non-technical end users.
- Think about privacy by design: does any data represent sensitive information, and how can this be safely shared/stored according to regulation (e.g., anonymisation, tokenisation, zero-trust principles)
-
From 7bd94766442ca12a60977927028818341df34cf0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Mon, 3 Mar 2025 16:18:09 +0100
Subject: [PATCH 28/58] Update device-roaming-status-User-Story.md
---
.../API_documentation/device-roaming-status-User-Story.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/API_documentation/device-roaming-status-User-Story.md b/documentation/API_documentation/device-roaming-status-User-Story.md
index 2f197a64..f3c0c1c7 100644
--- a/documentation/API_documentation/device-roaming-status-User-Story.md
+++ b/documentation/API_documentation/device-roaming-status-User-Story.md
@@ -2,7 +2,7 @@
| Item | Description | Support Qualifier |
|---------------------------|-------------|-------------------|
-| Summary | As an enterprise application developer, I want to query the roaming status of a user's device, so that I can determine if a device is in a foreign network and in which country it is located. This API can be used to identify fraud, ensure regulatory compliance, or enforce territorial restrictions on video and audio content. | M |
+| Summary | As an enterprise application developer, I want to query the roaming status of a user's device, so that I can determine whether a device is in a foreign network and in which country it is located. This API can be used to identify fraud, ensure regulatory compliance, or enforce territorial restrictions on video and audio content. | M |
| Roles, Actor(s) and scope | **Roles:** Customer:Developer
**Actors:** Application service providers (ASP), hyperscalers, application developers.
**Scope:** Order To Activate (OTA) - Get roaming status of a device | M |
| NF Requirements | - | O |
| Pre-conditions | - The customer:developer has been successfully onboarded to the API platform of the service provider
- The customer application has requested and received an access token with the required scope for the API | M |
From 82bbb76b8c7391604513ca46b84c28180cdea41c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Mon, 3 Mar 2025 16:23:05 +0100
Subject: [PATCH 29/58] Update device-reachability-status-User-Story.md
---
.../device-reachability-status-User-Story.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/documentation/API_documentation/device-reachability-status-User-Story.md b/documentation/API_documentation/device-reachability-status-User-Story.md
index dc997f2c..758aff37 100644
--- a/documentation/API_documentation/device-reachability-status-User-Story.md
+++ b/documentation/API_documentation/device-reachability-status-User-Story.md
@@ -2,12 +2,12 @@
| Item | Description | Support Qualifier |
|---------------------------|-------------|-------------------|
-| Summary | As an enterprise application developer, I want to query the connectivity status of a user's device, so that I can determine whether the device is reachable via SMS, data (mobile internet), or both, enabling better communication or service management decisions based on real-time device availability. | M |
-| Roles, Actor(s) and scope | **Roles:** Customer:Developer
**Actors:** Application service providers (ASP), hyperscalers, application developers.
**Scope:** Order To Activate (OTA) - Get roaming status of a device | M |
+| Summary | As an enterprise application developer, I want to query the reachability status of a user's device, so that I can determine whether the device is reachable via SMS, data (mobile internet), or both, enabling better communication or service management decisions based on real-time device availability. | M |
+| Roles, Actor(s) and scope | **Roles:** Customer:Developer
**Actors:** Application service providers (ASP), hyperscalers, application developers.
**Scope:** Order To Activate (OTA) - Get connectivity status of a device | M |
| NF Requirements | - | O |
| Pre-conditions | - The customer:developer has been successfully onboarded to the API platform of the service provider
- The customer application has requested and received an access token with the required scope for the API | M |
-| Begins when | The customer application server makes a POST request to retrieve the roaming status of a user's device | M |
-| Ends when | The service provider returns the roaming status of the device with a timestamp when the status information was updated. In case of a roaming situation also the roaming country name and code shall be returned. | |
+| Begins when | The customer application server makes a POST request to retrieve the reachability status of a user's device | M |
+| Ends when | The service provider returns the reachability status of the device with a timestamp when the status information was updated. In case of the device is reachable, additionally, the type of the connectivity (data, sms or both) is returned as well. | |
| Post-conditions | - | M |
| Exceptions | Several exceptions might occur during the API operations:
- Unauthorized: Invalid credentials (e.g., expired access token).
- Incorrect input data (e.g., malformed phone number).
- Not found: The phone number is not associated with a CSP customer account | M |
From 190d9a2dd733e4a466d35d16e9c9267fa189da5a Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Mon, 3 Mar 2025 16:24:31 +0100
Subject: [PATCH 30/58] Update
device-reachability-status-API-Readiness-Checklist.md
---
.../device-reachability-status-API-Readiness-Checklist.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md b/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
index 849a56b7..e81bc976 100644
--- a/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
@@ -9,7 +9,7 @@ Checklist for device-reachability-status 1.0.0 in r2.2.
| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.2 |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
-| 6 | User stories | O | O | O | M | Y | TODO |
+| 6 | User stories | O | O | O | M | Y | /documentation/API_documentation/device-reachability-status-User-Story.md |
| 7 | Basic API test cases & documentation | O | M | M | M | Y | /code/Test_definitions/device-reachability-status.feature |
| 8 | Enhanced API test cases & documentation | O | O | O | M | Y | /code/Test_definitions/device-reachability-status.feature |
| 9 | Test result statement | O | O | O | M | Y | TODO |
From d3671f59da0f1fba15b598048eac410d46623c25 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Mon, 3 Mar 2025 16:25:04 +0100
Subject: [PATCH 31/58] Update device-roaming-status-API-Readiness-Checklist.md
---
.../device-roaming-status-API-Readiness-Checklist.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md b/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
index 5bcd2fd4..f00eb804 100644
--- a/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
@@ -9,7 +9,7 @@ Checklist for device-roaming-status 1.0.0 in r2.2.
| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.2 |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
-| 6 | User stories | O | O | O | M | Y | TODO |
+| 6 | User stories | O | O | O | M | Y | /documentation/API_documentation/device-roaming-status-User-Story.md |
| 7 | Basic API test cases & documentation | O | M | M | M | Y | /code/Test_definitions/device-roaming-status.feature |
| 8 | Enhanced API test cases & documentation | O | O | O | M | Y | /code/Test_definitions/device-roaming-status.feature |
| 9 | Test result statement | O | O | O | M | Y | TODO |
From 274aa75078fedbcac7c2e362c2178ff954fef608 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Mon, 3 Mar 2025 16:26:51 +0100
Subject: [PATCH 32/58] Update device-roaming-status-API-Readiness-Checklist.md
---
.../device-roaming-status-API-Readiness-Checklist.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md b/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
index f00eb804..0c0b49b2 100644
--- a/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
@@ -12,7 +12,7 @@ Checklist for device-roaming-status 1.0.0 in r2.2.
| 6 | User stories | O | O | O | M | Y | /documentation/API_documentation/device-roaming-status-User-Story.md |
| 7 | Basic API test cases & documentation | O | M | M | M | Y | /code/Test_definitions/device-roaming-status.feature |
| 8 | Enhanced API test cases & documentation | O | O | O | M | Y | /code/Test_definitions/device-roaming-status.feature |
-| 9 | Test result statement | O | O | O | M | Y | TODO |
+| 9 | Test result statement | O | O | O | M | Y | [Test result statement](https://github.com/camaraproject/DeviceStatus/issues/258) |
| 10 | API release numbering convention applied | M | M | M | M | Y | |
| 11 | Change log updated | M | M | M | M | Y | /CHANGELOG.md |
| 12 | Previous public release was certified | O | O | O | M | Y | |
From 69fa122f2c981d0659905c8174089651dc6602fc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Mon, 3 Mar 2025 16:27:14 +0100
Subject: [PATCH 33/58] Update
device-reachability-status-API-Readiness-Checklist.md
---
.../device-reachability-status-API-Readiness-Checklist.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md b/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
index e81bc976..333a74ad 100644
--- a/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
@@ -12,7 +12,7 @@ Checklist for device-reachability-status 1.0.0 in r2.2.
| 6 | User stories | O | O | O | M | Y | /documentation/API_documentation/device-reachability-status-User-Story.md |
| 7 | Basic API test cases & documentation | O | M | M | M | Y | /code/Test_definitions/device-reachability-status.feature |
| 8 | Enhanced API test cases & documentation | O | O | O | M | Y | /code/Test_definitions/device-reachability-status.feature |
-| 9 | Test result statement | O | O | O | M | Y | TODO |
+| 9 | Test result statement | O | O | O | M | Y | [Test result statement](https://github.com/camaraproject/DeviceStatus/issues/258) |
| 10 | API release numbering convention applied | M | M | M | M | Y | |
| 11 | Change log updated | M | M | M | M | Y | /CHANGELOG.md |
| 12 | Previous public release was certified | O | O | O | M | Y | |
From 75043da4f53fcd3b217bcf8fd904a00e3657bef8 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 16:17:25 +0100
Subject: [PATCH 34/58] Update
connected-network-type-API-Readiness-Checklist.md
---
.../connected-network-type-API-Readiness-Checklist.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/API_documentation/connected-network-type-API-Readiness-Checklist.md b/documentation/API_documentation/connected-network-type-API-Readiness-Checklist.md
index e15b837b..97665979 100644
--- a/documentation/API_documentation/connected-network-type-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/connected-network-type-API-Readiness-Checklist.md
@@ -5,8 +5,8 @@ Checklist for connected-network-type 0.1.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
| 1 | API definition | M | M | M | M | Y | /code/API_definitions/connected-network-type.yaml |
-| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.2 |
-| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.2 |
+| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.3 |
+| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.3 |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
| 6 | User stories | O | O | O | M | N | |
From f58cc344eaa7f414023f5b8b367410ab7f21b373 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 16:17:54 +0100
Subject: [PATCH 35/58] Update
connected-network-type-subscriptions-API-Readiness-Checklist.md
---
...cted-network-type-subscriptions-API-Readiness-Checklist.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/API_documentation/connected-network-type-subscriptions-API-Readiness-Checklist.md b/documentation/API_documentation/connected-network-type-subscriptions-API-Readiness-Checklist.md
index 3434246e..823b1fd3 100644
--- a/documentation/API_documentation/connected-network-type-subscriptions-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/connected-network-type-subscriptions-API-Readiness-Checklist.md
@@ -5,8 +5,8 @@ Checklist for connected-network-type-subscriptions 0.1.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
| 1 | API definition | M | M | M | M | Y | /code/API_definitions/connected-network-type-subscriptions.yaml |
-| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.2 |
-| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.2 |
+| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.3 |
+| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.3 |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
| 6 | User stories | O | O | O | M | N | |
From ee575cdb1dc1990c3a9bd55b9371c0c5acba9ff3 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 16:18:11 +0100
Subject: [PATCH 36/58] Update
device-reachability-status-API-Readiness-Checklist.md
---
.../device-reachability-status-API-Readiness-Checklist.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md b/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
index 333a74ad..42222a2b 100644
--- a/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
@@ -5,8 +5,8 @@ Checklist for device-reachability-status 1.0.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
| 1 | API definition | M | M | M | M | Y | /code/API_definitions/device-reachability-status.yaml |
-| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.2 |
-| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.2 |
+| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.3 |
+| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.3 |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
| 6 | User stories | O | O | O | M | Y | /documentation/API_documentation/device-reachability-status-User-Story.md |
From 16ff3c11c21dcf93ef54fdbc64585d603155ca25 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 16:18:36 +0100
Subject: [PATCH 37/58] Update
device-reachability-status-subscriptions-API-Readiness-Checklist.md
---
...achability-status-subscriptions-API-Readiness-Checklist.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/API_documentation/device-reachability-status-subscriptions-API-Readiness-Checklist.md b/documentation/API_documentation/device-reachability-status-subscriptions-API-Readiness-Checklist.md
index a9b56d55..fde49cd2 100644
--- a/documentation/API_documentation/device-reachability-status-subscriptions-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-reachability-status-subscriptions-API-Readiness-Checklist.md
@@ -5,8 +5,8 @@ Checklist for device-reachability-status-subscriptions 0.7.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
| 1 | API definition | M | M | M | M | Y | /code/API_definitions/device-reachability-status-subscriptions.yaml |
-| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.2 |
-| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.2 |
+| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.3 |
+| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.3 |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
| 6 | User stories | O | O | O | M | N | |
From d8ca8febe1dcf4d0406d0278bad44e2c1ecb1115 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 16:18:52 +0100
Subject: [PATCH 38/58] Update device-roaming-status-API-Readiness-Checklist.md
---
.../device-roaming-status-API-Readiness-Checklist.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md b/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
index 0c0b49b2..67546953 100644
--- a/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
@@ -5,8 +5,8 @@ Checklist for device-roaming-status 1.0.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
| 1 | API definition | M | M | M | M | Y | /code/API_definitions/device-roaming-status.yaml |
-| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.2 |
-| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.2 |
+| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.3 |
+| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.3 |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
| 6 | User stories | O | O | O | M | Y | /documentation/API_documentation/device-roaming-status-User-Story.md |
From 6f5cd2c1a594b79b1f152233aff73339e369cddc Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 16:19:07 +0100
Subject: [PATCH 39/58] Update
device-roaming-status-subscriptions-API-Readiness-Checklist.md
---
...ce-roaming-status-subscriptions-API-Readiness-Checklist.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/API_documentation/device-roaming-status-subscriptions-API-Readiness-Checklist.md b/documentation/API_documentation/device-roaming-status-subscriptions-API-Readiness-Checklist.md
index d0291d28..2e30f4b7 100644
--- a/documentation/API_documentation/device-roaming-status-subscriptions-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-roaming-status-subscriptions-API-Readiness-Checklist.md
@@ -5,8 +5,8 @@ Checklist for device-roaming-status-subscriptions 0.7.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
| 1 | API definition | M | M | M | M | Y | /code/API_definitions/device-roaming-status-subscriptions.yaml |
-| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.2 |
-| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.2 |
+| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.3 |
+| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.3 |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
| 6 | User stories | O | O | O | M | N | |
From 602af0a619dc384f2d8c2583cfc5be49904229ae Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 16:54:27 +0100
Subject: [PATCH 40/58] Update connected-network-type-subscriptions.yaml
---
code/API_definitions/connected-network-type-subscriptions.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/code/API_definitions/connected-network-type-subscriptions.yaml b/code/API_definitions/connected-network-type-subscriptions.yaml
index 9ea7d2f7..c1f5642f 100644
--- a/code/API_definitions/connected-network-type-subscriptions.yaml
+++ b/code/API_definitions/connected-network-type-subscriptions.yaml
@@ -670,7 +670,7 @@ components:
SubscriptionId:
type: string
- description: The unique identifier of the subscription in the scope of the subscription manager. When this information is contained within an event notification, this concept SHALL be referred as `subscriptionId` as per [Commonalities Event Notification Model](https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#122-event-notification).
+ description: The unique identifier of the subscription in the scope of the subscription manager. When this information is contained within an event notification, this concept SHALL be referred as `subscriptionId` as per [Commonalities Event Notification Model](https://github.com/camaraproject/Commonalities/blob/r2.3/documentation/API-design-guidelines.md#122-event-notification).
example: qs15-h556-rt89-1298
Device:
From 0092df8d3aedd1dcee5e58f7652cdaa7d7559e78 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 16:55:05 +0100
Subject: [PATCH 41/58] Update device-reachability-status-subscriptions.yaml
---
.../device-reachability-status-subscriptions.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/code/API_definitions/device-reachability-status-subscriptions.yaml b/code/API_definitions/device-reachability-status-subscriptions.yaml
index 4140f295..144dc3d4 100644
--- a/code/API_definitions/device-reachability-status-subscriptions.yaml
+++ b/code/API_definitions/device-reachability-status-subscriptions.yaml
@@ -764,7 +764,7 @@ components:
SubscriptionId:
type: string
- description: The unique identifier of the subscription in the scope of the subscription manager. When this information is contained within an event notification, this concept SHALL be referred as `subscriptionId` as per [Commonalities Event Notification Model](https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#122-event-notification).
+ description: The unique identifier of the subscription in the scope of the subscription manager. When this information is contained within an event notification, this concept SHALL be referred as `subscriptionId` as per [Commonalities Event Notification Model](https://github.com/camaraproject/Commonalities/blob/r2.3/documentation/API-design-guidelines.md#122-event-notification).
example: qs15-h556-rt89-1298
CloudEvent:
From a22827d3dba8f31ca133ea8c293153d706fee801 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 16:55:38 +0100
Subject: [PATCH 42/58] Update device-roaming-status-subscriptions.yaml
---
code/API_definitions/device-roaming-status-subscriptions.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/code/API_definitions/device-roaming-status-subscriptions.yaml b/code/API_definitions/device-roaming-status-subscriptions.yaml
index 736e3af4..011fca47 100644
--- a/code/API_definitions/device-roaming-status-subscriptions.yaml
+++ b/code/API_definitions/device-roaming-status-subscriptions.yaml
@@ -821,7 +821,7 @@ components:
SubscriptionId:
type: string
- description: The unique identifier of the subscription in the scope of the subscription manager. When this information is contained within an event notification, this concept SHALL be referred as `subscriptionId` as per [Commonalities Event Notification Model](https://github.com/camaraproject/Commonalities/blob/main/documentation/API-design-guidelines.md#122-event-notification).
+ description: The unique identifier of the subscription in the scope of the subscription manager. When this information is contained within an event notification, this concept SHALL be referred as `subscriptionId` as per [Commonalities Event Notification Model](https://github.com/camaraproject/Commonalities/blob/r2.3/documentation/API-design-guidelines.md#122-event-notification).
example: qs15-h556-rt89-1298
CloudEvent:
From a10554220092fbb44fdd36109b0dba30b4456eb6 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 17:03:05 +0100
Subject: [PATCH 43/58] Update connected-network-type.yaml
---
code/API_definitions/connected-network-type.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/code/API_definitions/connected-network-type.yaml b/code/API_definitions/connected-network-type.yaml
index bf9a8d97..43ea6866 100644
--- a/code/API_definitions/connected-network-type.yaml
+++ b/code/API_definitions/connected-network-type.yaml
@@ -51,7 +51,7 @@ info:
The "Camara Security and Interoperability Profile" provides details of how an API consumer requests an access token. Please refer to Identity and Consent Management (https://github.com/camaraproject/IdentityAndConsentManagement/) for the released version of the profile.
- The specific authorization flows to be used will be agreed upon during the onboarding process, happening between the provider of the application consuming the API and the operator's API exposure platform, taking into account the declared purpose for accessing the API, whilst also being subject to the prevailing legal framework dictated by local legislation.
+ The specific authorization flows to be used will be agreed upon during the onboarding process, happening between the API consumer and the API provider, taking into account the declared purpose for accessing the API, whilst also being subject to the prevailing legal framework dictated by local legislation.
In cases where personal data is processed by the API and users can exercise their rights through mechanisms such as opt-in and/or opt-out, the use of three-legged access tokens is mandatory. This ensures that the API remains in compliance with privacy regulations, upholding the principles of transparency and user-centric privacy-by-design.
From 41fc160713fc711aae453c9dacaa16771d27e97e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 17:03:44 +0100
Subject: [PATCH 44/58] Update device-reachability-status.yaml
---
code/API_definitions/device-reachability-status.yaml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/code/API_definitions/device-reachability-status.yaml b/code/API_definitions/device-reachability-status.yaml
index 8261812e..0e489210 100644
--- a/code/API_definitions/device-reachability-status.yaml
+++ b/code/API_definitions/device-reachability-status.yaml
@@ -47,7 +47,7 @@ info:
The "Camara Security and Interoperability Profile" provides details of how an API consumer requests an access token. Please refer to Identity and Consent Management (https://github.com/camaraproject/IdentityAndConsentManagement/) for the released version of the profile.
- The specific authorization flows to be used will be agreed upon during the onboarding process, happening between the provider of the application consuming the API and the operator's API exposure platform, taking into account the declared purpose for accessing the API, whilst also being subject to the prevailing legal framework dictated by local legislation.
+ The specific authorization flows to be used will be agreed upon during the onboarding process, happening between the API consumer and the API provider, taking into account the declared purpose for accessing the API, whilst also being subject to the prevailing legal framework dictated by local legislation.
In cases where personal data is processed by the API and users can exercise their rights through mechanisms such as opt-in and/or opt-out, the use of three-legged access tokens is mandatory. This ensures that the API remains in compliance with privacy regulations, upholding the principles of transparency and user-centric privacy-by-design.
From 318389a2cfefe922869182d5e750163d060a0cf0 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 17:05:45 +0100
Subject: [PATCH 45/58] Update device-roaming-status-subscriptions.yaml
---
.../device-roaming-status-subscriptions.yaml | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/code/API_definitions/device-roaming-status-subscriptions.yaml b/code/API_definitions/device-roaming-status-subscriptions.yaml
index 011fca47..df34b924 100644
--- a/code/API_definitions/device-roaming-status-subscriptions.yaml
+++ b/code/API_definitions/device-roaming-status-subscriptions.yaml
@@ -96,11 +96,11 @@ info:
## Authorization and authentication
- The "Camara Security and Interoperability Profile" provides details on how a client requests an access token. Please refer to Identify and Consent Management (https://github.com/camaraproject/IdentityAndConsentManagement/) for the released version of the Profile.
+ The "Camara Security and Interoperability Profile" provides details of how an API consumer requests an access token. Please refer to Identity and Consent Management (https://github.com/camaraproject/IdentityAndConsentManagement/) for the released version of the profile.
- Which specific authorization flows are to be used will be determined during onboarding process, happening between the API Client and the Telco Operator exposing the API, taking into account the declared purpose for accessing the API, while also being subject to the prevailing legal framework dictated by local legislation.
+ The specific authorization flows to be used will be agreed upon during the onboarding process, happening between the API consumer and the API provider, taking into account the declared purpose for accessing the API, whilst also being subject to the prevailing legal framework dictated by local legislation.
- It is important to remark that in cases where personal user data is processed by the API, and users can exercise their rights through mechanisms such as opt-in and/or opt-out, the use of 3-legged access tokens becomes mandatory. This measure ensures that the API remains in strict compliance with user privacy preferences and regulatory obligations, upholding the principles of transparency and user-centric data control.
+ In cases where personal data is processed by the API and users can exercise their rights through mechanisms such as opt-in and/or opt-out, the use of three-legged access tokens is mandatory. This ensures that the API remains in compliance with privacy regulations, upholding the principles of transparency and user-centric privacy-by-design.
## Identifying the device from the access token
From f7d1b1df7bbaeb1ed2b64b555a4970725f381eea Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 17:07:07 +0100
Subject: [PATCH 46/58] Update device-roaming-status.yaml
---
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 60b846f9..7a0153d2 100644
--- a/code/API_definitions/device-roaming-status.yaml
+++ b/code/API_definitions/device-roaming-status.yaml
@@ -55,7 +55,7 @@ info:
The "Camara Security and Interoperability Profile" provides details of how an API consumer requests an access token. Please refer to Identity and Consent Management (https://github.com/camaraproject/IdentityAndConsentManagement/) for the released version of the profile.
- The specific authorization flows to be used will be agreed upon during the onboarding process, happening between the provider of the application consuming the API and the operator's API exposure platform, taking into account the declared purpose for accessing the API, whilst also being subject to the prevailing legal framework dictated by local legislation.
+ The specific authorization flows to be used will be agreed upon during the onboarding process, happening between the API consumer and the API provider, taking into account the declared purpose for accessing the API, whilst also being subject to the prevailing legal framework dictated by local legislation.
In cases where personal data is processed by the API and users can exercise their rights through mechanisms such as opt-in and/or opt-out, the use of three-legged access tokens is mandatory. This ensures that the API remains in compliance with privacy regulations, upholding the principles of transparency and user-centric privacy-by-design.
From 451fc32be49228e0f7d811cabbf459ff6c970587 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 17:08:36 +0100
Subject: [PATCH 47/58] Update connected-network-type-subscriptions.yaml
---
.../connected-network-type-subscriptions.yaml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/code/API_definitions/connected-network-type-subscriptions.yaml b/code/API_definitions/connected-network-type-subscriptions.yaml
index c1f5642f..201de1eb 100644
--- a/code/API_definitions/connected-network-type-subscriptions.yaml
+++ b/code/API_definitions/connected-network-type-subscriptions.yaml
@@ -67,11 +67,12 @@ info:
# Further info and support
## Authorization and authentication
- The "Camara Security and Interoperability Profile" provides details on how a client requests an access token. Please refer to Identify and Consent Management (https://github.com/camaraproject/IdentityAndConsentManagement/) for the released version of the Profile.
- Which specific authorization flows are to be used will be determined during onboarding process, happening between the API Client and the API Provider, taking into account the declared purpose for accessing the API, while also being subject to the prevailing legal framework dictated by local legislation.
+ The "Camara Security and Interoperability Profile" provides details of how an API consumer requests an access token. Please refer to Identity and Consent Management (https://github.com/camaraproject/IdentityAndConsentManagement/) for the released version of the profile.
- It is important to remark that in cases where personal user data is processed by the API, and users can exercise their rights through mechanisms such as opt-in and/or opt-out, the use of 3-legged access tokens becomes mandatory. This measure ensures that the API remains in strict compliance with user privacy preferences and regulatory obligations, upholding the principles of transparency and user-centric data control.
+ The specific authorization flows to be used will be agreed upon during the onboarding process, happening between the API consumer and the API provider, taking into account the declared purpose for accessing the API, whilst also being subject to the prevailing legal framework dictated by local legislation.
+
+ In cases where personal data is processed by the API and users can exercise their rights through mechanisms such as opt-in and/or opt-out, the use of three-legged access tokens is mandatory. This ensures that the API remains in compliance with privacy regulations, upholding the principles of transparency and user-centric privacy-by-design.
## Identifying the device from the access token
From 03dcee19cff4f8873e92e514ea548d127e5972b9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 17:11:28 +0100
Subject: [PATCH 48/58] Update CHANGELOG.md
Co-authored-by: Herbert Damker
---
CHANGELOG.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 96fe30ac..8dec8221 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -23,7 +23,7 @@ The below sections record the changes for each API version in each release as fo
# r2.2
## Release Notes
-This pre-release contains the definition and documentation of
+This public release contains the definition and documentation of
* device-roaming-status v1.0.0
* device-roaming-status-subscriptions v0.7.0
* device-reachability-status v1.0.0
From a9c07477dc9b3fe016b23532d4339340fb910115 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 20:56:40 +0100
Subject: [PATCH 49/58] Update
device-reachability-status-API-Readiness-Checklist.md
---
...hability-status-API-Readiness-Checklist.md | 19 ++++++++++---------
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md b/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
index 42222a2b..5f02173b 100644
--- a/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
@@ -4,19 +4,20 @@ Checklist for device-reachability-status 1.0.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
-| 1 | API definition | M | M | M | M | Y | /code/API_definitions/device-reachability-status.yaml |
-| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.3 |
-| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.3 |
+| 1 | API definition | M | M | M | M | Y | [/code/API_definitions/device-reachability-status.yaml](/code/API_definitions/device-reachability-status.yaml) |
+| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | [r2.3](https://github.com/camaraproject/Commonalities/releases/tag/r2.3) |
+| 3 | Guidelines from ICM applied | O | M | M | M | Y | [r2.3](https://github.com/camaraproject/IdentityAndConsentManagement/releases/tag/r2.3) |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
-| 6 | User stories | O | O | O | M | Y | /documentation/API_documentation/device-reachability-status-User-Story.md |
-| 7 | Basic API test cases & documentation | O | M | M | M | Y | /code/Test_definitions/device-reachability-status.feature |
-| 8 | Enhanced API test cases & documentation | O | O | O | M | Y | /code/Test_definitions/device-reachability-status.feature |
-| 9 | Test result statement | O | O | O | M | Y | [Test result statement](https://github.com/camaraproject/DeviceStatus/issues/258) |
+| 6 | User stories | O | O | O | M | Y | [/documentation/API_documentation/device-reachability-status-User-Story.md](/documentation/API_documentation/device-reachability-status-User-Story.md) |
+| 7 | Basic API test cases & documentation | O | M | M | M | Y | [/code/Test_definitions/device-reachability-status.feature](/code/Test_definitions/device-reachability-status.feature) |
+| 8 | Enhanced API test cases & documentation | O | O | O | M | Y | [/code/Test_definitions/device-reachability-status.feature](/code/Test_definitions/device-reachability-status.feature) |
+| 9 | Test result statement | O | O | O | M | Y | [see issue #258](https://github.com/camaraproject/DeviceStatus/issues/258) |
| 10 | API release numbering convention applied | M | M | M | M | Y | |
-| 11 | Change log updated | M | M | M | M | Y | /CHANGELOG.md |
-| 12 | Previous public release was certified | O | O | O | M | Y | |
+| 11 | Change log updated | M | M | M | M | Y | [/CHANGELOG.md](/CHANGELOG.md) |
+| 12 | Previous public release was certified | O | O | O | M | Y | see (1) |
+(1) GSMA certified implementation of previous version by AT&T and China Telecom, multiple implementation by other operators (source: https://open-gateway.gsma.com/map as of 2025-03-11)
Note: the checklists of a public API version and of its preceding release-candidate API version can be the same.
From da31f5d2f15a18e8b895ce496c1ae5898dc42099 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 21:01:13 +0100
Subject: [PATCH 50/58] Update device-roaming-status-API-Readiness-Checklist.md
---
...-roaming-status-API-Readiness-Checklist.md | 20 ++++++++++---------
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md b/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
index 67546953..e49563ae 100644
--- a/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
@@ -4,18 +4,20 @@ Checklist for device-roaming-status 1.0.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
-| 1 | API definition | M | M | M | M | Y | /code/API_definitions/device-roaming-status.yaml |
-| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.3 |
-| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.3 |
+| 1 | API definition | M | M | M | M | Y | [/code/API_definitions/device-roaming-status.yaml](/code/API_definitions/device-roaming-status.yaml) |
+| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | [r2.3](https://github.com/camaraproject/Commonalities/releases/tag/r2.3) |
+| 3 | Guidelines from ICM applied | O | M | M | M | Y | [r2.3](https://github.com/camaraproject/IdentityAndConsentManagement/releases/tag/r2.3) |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
-| 6 | User stories | O | O | O | M | Y | /documentation/API_documentation/device-roaming-status-User-Story.md |
-| 7 | Basic API test cases & documentation | O | M | M | M | Y | /code/Test_definitions/device-roaming-status.feature |
-| 8 | Enhanced API test cases & documentation | O | O | O | M | Y | /code/Test_definitions/device-roaming-status.feature |
-| 9 | Test result statement | O | O | O | M | Y | [Test result statement](https://github.com/camaraproject/DeviceStatus/issues/258) |
+| 6 | User stories | O | O | O | M | Y | [/documentation/API_documentation/device-roaming-status-User-Story.md](/documentation/API_documentation/device-roaming-status-User-Story.md) |
+| 7 | Basic API test cases & documentation | O | M | M | M | Y | [/code/Test_definitions/device-roaming-status.feature](/code/Test_definitions/device-roaming-status.feature) |
+| 8 | Enhanced API test cases & documentation | O | O | O | M | Y | [/code/Test_definitions/device-roaming-status.feature](/code/Test_definitions/device-roaming-status.feature) |
+| 9 | Test result statement | O | O | O | M | Y | [see issue #258](https://github.com/camaraproject/DeviceStatus/issues/258) |
| 10 | API release numbering convention applied | M | M | M | M | Y | |
-| 11 | Change log updated | M | M | M | M | Y | /CHANGELOG.md |
-| 12 | Previous public release was certified | O | O | O | M | Y | |
+| 11 | Change log updated | M | M | M | M | Y | [/CHANGELOG.md](/CHANGELOG.md) |
+| 12 | Previous public release was certified | O | O | O | M | Y | see (1) |
+
+(1) GSMA certified implementation of previous version by AT&T and China Telecom, multiple implementation by other operators (source: https://open-gateway.gsma.com/map as of 2025-03-11)
Note: the checklists of a public API version and of its preceding release-candidate API version can be the same.
From 864019a8df63a012febeb4d8c03bb73ca65678ed Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 21:03:09 +0100
Subject: [PATCH 51/58] Update
connected-network-type-API-Readiness-Checklist.md
---
.../connected-network-type-API-Readiness-Checklist.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/documentation/API_documentation/connected-network-type-API-Readiness-Checklist.md b/documentation/API_documentation/connected-network-type-API-Readiness-Checklist.md
index 97665979..d1779626 100644
--- a/documentation/API_documentation/connected-network-type-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/connected-network-type-API-Readiness-Checklist.md
@@ -4,17 +4,17 @@ Checklist for connected-network-type 0.1.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
-| 1 | API definition | M | M | M | M | Y | /code/API_definitions/connected-network-type.yaml |
-| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.3 |
-| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.3 |
+| 1 | API definition | M | M | M | M | Y | [/code/API_definitions/connected-network-type.yaml](/code/API_definitions/connected-network-type.yaml) |
+| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | [r2.3](https://github.com/camaraproject/Commonalities/releases/tag/r2.3) |
+| 3 | Guidelines from ICM applied | O | M | M | M | Y | [r2.3](https://github.com/camaraproject/IdentityAndConsentManagement/releases/tag/r2.3) |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
| 6 | User stories | O | O | O | M | N | |
-| 7 | Basic API test cases & documentation | O | M | M | M | Y | /code/Test_definitions/connected-network-type.feature |
+| 7 | Basic API test cases & documentation | O | M | M | M | Y | [/code/Test_definitions/connected-network-type.feature](/code/Test_definitions/connected-network-type.feature) |
| 8 | Enhanced API test cases & documentation | O | O | O | M | N | |
| 9 | Test result statement | O | O | O | M | N | |
| 10 | API release numbering convention applied | M | M | M | M | Y | |
-| 11 | Change log updated | M | M | M | M | Y | /CHANGELOG.md |
+| 11 | Change log updated | M | M | M | M | Y | [/CHANGELOG.md](/CHANGELOG.md) |
| 12 | Previous public release was certified | O | O | O | M | N | |
Note: the checklists of a public API version and of its preceding release-candidate API version can be the same.
From b43733fa7465f0e449b40a6a54ab56b4e7cf031e Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 21:04:41 +0100
Subject: [PATCH 52/58] Update
connected-network-type-subscriptions-API-Readiness-Checklist.md
---
...twork-type-subscriptions-API-Readiness-Checklist.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/documentation/API_documentation/connected-network-type-subscriptions-API-Readiness-Checklist.md b/documentation/API_documentation/connected-network-type-subscriptions-API-Readiness-Checklist.md
index 823b1fd3..7941985f 100644
--- a/documentation/API_documentation/connected-network-type-subscriptions-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/connected-network-type-subscriptions-API-Readiness-Checklist.md
@@ -4,17 +4,17 @@ Checklist for connected-network-type-subscriptions 0.1.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
-| 1 | API definition | M | M | M | M | Y | /code/API_definitions/connected-network-type-subscriptions.yaml |
-| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.3 |
-| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.3 |
+| 1 | API definition | M | M | M | M | Y | [/code/API_definitions/connected-network-type-subscriptions.yaml](/code/API_definitions/connected-network-type-subscriptions.yaml) |
+| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | [r2.3](https://github.com/camaraproject/Commonalities/releases/tag/r2.3) |
+| 3 | Guidelines from ICM applied | O | M | M | M | Y | [r2.3](https://github.com/camaraproject/IdentityAndConsentManagement/releases/tag/r2.3) |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
| 6 | User stories | O | O | O | M | N | |
-| 7 | Basic API test cases & documentation | O | M | M | M | Y | /code/Test_definitions/connected-network-type-subscriptions.feature |
+| 7 | Basic API test cases & documentation | O | M | M | M | Y | [/code/Test_definitions/connected-network-type-subscriptions.feature](/code/Test_definitions/connected-network-type-subscriptions.feature) |
| 8 | Enhanced API test cases & documentation | O | O | O | M | N | |
| 9 | Test result statement | O | O | O | M | N | |
| 10 | API release numbering convention applied | M | M | M | M | Y | |
-| 11 | Change log updated | M | M | M | M | Y | /CHANGELOG.md |
+| 11 | Change log updated | M | M | M | M | Y | [/CHANGELOG.md](/CHANGELOG.md) |
| 12 | Previous public release was certified | O | O | O | M | N | |
Note: the checklists of a public API version and of its preceding release-candidate API version can be the same.
From 30a334469ecc854f0e1efdeeb7f362b2b7b59748 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 21:06:15 +0100
Subject: [PATCH 53/58] Update
device-reachability-status-subscriptions-API-Readiness-Checklist.md
---
...ity-status-subscriptions-API-Readiness-Checklist.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/documentation/API_documentation/device-reachability-status-subscriptions-API-Readiness-Checklist.md b/documentation/API_documentation/device-reachability-status-subscriptions-API-Readiness-Checklist.md
index fde49cd2..afbe8302 100644
--- a/documentation/API_documentation/device-reachability-status-subscriptions-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-reachability-status-subscriptions-API-Readiness-Checklist.md
@@ -4,17 +4,17 @@ Checklist for device-reachability-status-subscriptions 0.7.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
-| 1 | API definition | M | M | M | M | Y | /code/API_definitions/device-reachability-status-subscriptions.yaml |
-| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.3 |
-| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.3 |
+| 1 | API definition | M | M | M | M | Y | [/code/API_definitions/device-reachability-status-subscriptions.yaml](/code/API_definitions/device-reachability-status-subscriptions.yaml) |
+| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | [r2.3](https://github.com/camaraproject/Commonalities/releases/tag/r2.3) |
+| 3 | Guidelines from ICM applied | O | M | M | M | Y | [r2.3](https://github.com/camaraproject/IdentityAndConsentManagement/releases/tag/r2.3) |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
| 6 | User stories | O | O | O | M | N | |
-| 7 | Basic API test cases & documentation | O | M | M | M | Y | /code/Test_definitions/device-reachability-status-subscriptions.feature |
+| 7 | Basic API test cases & documentation | O | M | M | M | Y | [/code/Test_definitions/device-reachability-status-subscriptions.feature](/code/Test_definitions/device-reachability-status-subscriptions.feature) |
| 8 | Enhanced API test cases & documentation | O | O | O | M | N | |
| 9 | Test result statement | O | O | O | M | N | |
| 10 | API release numbering convention applied | M | M | M | M | Y | |
-| 11 | Change log updated | M | M | M | M | Y | /CHANGELOG.md |
+| 11 | Change log updated | M | M | M | M | Y | [/CHANGELOG.md](/CHANGELOG.md) |
| 12 | Previous public release was certified | O | O | O | M | N | |
Note: the checklists of a public API version and of its preceding release-candidate API version can be the same.
From afef9ad88ded2cbc4f8066d391dbe578e3b872f9 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 21:07:52 +0100
Subject: [PATCH 54/58] Update
device-roaming-status-subscriptions-API-Readiness-Checklist.md
---
...ing-status-subscriptions-API-Readiness-Checklist.md | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/documentation/API_documentation/device-roaming-status-subscriptions-API-Readiness-Checklist.md b/documentation/API_documentation/device-roaming-status-subscriptions-API-Readiness-Checklist.md
index 2e30f4b7..853d62e4 100644
--- a/documentation/API_documentation/device-roaming-status-subscriptions-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-roaming-status-subscriptions-API-Readiness-Checklist.md
@@ -4,17 +4,17 @@ Checklist for device-roaming-status-subscriptions 0.7.0 in r2.2.
| Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Reference information |
|----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:|
-| 1 | API definition | M | M | M | M | Y | /code/API_definitions/device-roaming-status-subscriptions.yaml |
-| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | r2.3 |
-| 3 | Guidelines from ICM applied | O | M | M | M | Y | r2.3 |
+| 1 | API definition | M | M | M | M | Y | [/code/API_definitions/device-roaming-status-subscriptions.yaml](/code/API_definitions/device-roaming-status-subscriptions.yaml) |
+| 2 | Design guidelines from Commonalities applied | O | M | M | M | Y | [r2.3](https://github.com/camaraproject/Commonalities/releases/tag/r2.3) |
+| 3 | Guidelines from ICM applied | O | M | M | M | Y | [r2.3](https://github.com/camaraproject/IdentityAndConsentManagement/releases/tag/r2.3) |
| 4 | API versioning convention applied | M | M | M | M | Y | |
| 5 | API documentation | M | M | M | M | Y | inline in YAML |
| 6 | User stories | O | O | O | M | N | |
-| 7 | Basic API test cases & documentation | O | M | M | M | Y | /code/Test_definitions/device-roaming-status-subscriptions.feature |
+| 7 | Basic API test cases & documentation | O | M | M | M | Y | [/code/Test_definitions/device-roaming-status-subscriptions.feature](/code/Test_definitions/device-roaming-status-subscriptions.feature) |
| 8 | Enhanced API test cases & documentation | O | O | O | M | N | |
| 9 | Test result statement | O | O | O | M | N | |
| 10 | API release numbering convention applied | M | M | M | M | Y | |
-| 11 | Change log updated | M | M | M | M | Y | /CHANGELOG.md |
+| 11 | Change log updated | M | M | M | M | Y | [/CHANGELOG.md](/CHANGELOG.md) |
| 12 | Previous public release was certified | O | O | O | M | N | |
Note: the checklists of a public API version and of its preceding release-candidate API version can be the same.
From 39bdb8ab5f183b6025449425c65df2c08e012b45 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Tue, 11 Mar 2025 21:22:34 +0100
Subject: [PATCH 55/58] Update README.md
---
README.md | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/README.md b/README.md
index bdc08c84..ebd5f934 100644
--- a/README.md
+++ b/README.md
@@ -7,7 +7,10 @@
# DeviceStatus
-Repository to describe, develop, document and test the DeviceStatus APIs
+Incubating API Repository to evolve and maintain the definitions and documentation of DeviceStatus Service API(s) within the Sub Project [Device Status](https://lf-camaraproject.atlassian.net/wiki/x/6wApBQ)
+
+* API Repository wiki page: https://lf-camaraproject.atlassian.net/wiki/x/AgDe
+* Sub Project home page: https://lf-camaraproject.atlassian.net/wiki/x/fzLe
## Scope
* Service APIs for “Device Status” (see [APIBacklog.md](https://github.com/camaraproject/APIBacklog/blob/main/documentation/APIbacklog.md))
@@ -15,8 +18,9 @@ Repository to describe, develop, document and test the DeviceStatus APIs
- check if a device is reachable or is not connected to the network
- check if a device is roaming, and in which country
- receive notifications if the connectivity or roaming status of the device changes
-* Describe, develop, document and test the APIs (with 1-2 Telcos)
-* Started: July 2022
+* Describe, develop, document and test the APIs (with 1-2 Telcos)
+* Started: July 2022
+* Incubating stage since: February 2025
## Release Information
From 231b656f135951d2317cc771d026175fd096b467 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Wed, 12 Mar 2025 13:59:29 +0100
Subject: [PATCH 56/58] Update
device-reachability-status-API-Readiness-Checklist.md
---
.../device-reachability-status-API-Readiness-Checklist.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md b/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
index 5f02173b..48efe460 100644
--- a/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-reachability-status-API-Readiness-Checklist.md
@@ -17,7 +17,7 @@ Checklist for device-reachability-status 1.0.0 in r2.2.
| 11 | Change log updated | M | M | M | M | Y | [/CHANGELOG.md](/CHANGELOG.md) |
| 12 | Previous public release was certified | O | O | O | M | Y | see (1) |
-(1) GSMA certified implementation of previous version by AT&T and China Telecom, multiple implementation by other operators (source: https://open-gateway.gsma.com/map as of 2025-03-11)
+(1) GSMA certified implementations of previous version by multiple operators (source: https://open-gateway.gsma.com/map as of 2025-03-11)
Note: the checklists of a public API version and of its preceding release-candidate API version can be the same.
From be03247160e0d4ba604ebc1b2f106e8d6628f888 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Wed, 12 Mar 2025 14:00:22 +0100
Subject: [PATCH 57/58] Update device-roaming-status-API-Readiness-Checklist.md
---
.../device-roaming-status-API-Readiness-Checklist.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md b/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
index e49563ae..db31fcd7 100644
--- a/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
+++ b/documentation/API_documentation/device-roaming-status-API-Readiness-Checklist.md
@@ -17,7 +17,7 @@ Checklist for device-roaming-status 1.0.0 in r2.2.
| 11 | Change log updated | M | M | M | M | Y | [/CHANGELOG.md](/CHANGELOG.md) |
| 12 | Previous public release was certified | O | O | O | M | Y | see (1) |
-(1) GSMA certified implementation of previous version by AT&T and China Telecom, multiple implementation by other operators (source: https://open-gateway.gsma.com/map as of 2025-03-11)
+(1) GSMA certified implementations of previous version by multiple operators (source: https://open-gateway.gsma.com/map as of 2025-03-11)
Note: the checklists of a public API version and of its preceding release-candidate API version can be the same.
From a5f1e45f25948871bbf625e600399c78addbfe90 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C3=81kos=20Hunyadi?=
<67875049+akoshunyadi@users.noreply.github.com>
Date: Wed, 12 Mar 2025 16:00:33 +0100
Subject: [PATCH 58/58] Update README.md
Co-authored-by: Herbert Damker
---
README.md | 1 +
1 file changed, 1 insertion(+)
diff --git a/README.md b/README.md
index ebd5f934..52a3cba0 100644
--- a/README.md
+++ b/README.md
@@ -5,6 +5,7 @@
+
# DeviceStatus
Incubating API Repository to evolve and maintain the definitions and documentation of DeviceStatus Service API(s) within the Sub Project [Device Status](https://lf-camaraproject.atlassian.net/wiki/x/6wApBQ)