From 02738d167f1aa6a0d9e162741dbdcf1422f88ce7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Sat, 5 Oct 2024 17:45:23 +0200 Subject: [PATCH 01/29] 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 3cd7493..a23941d 100644 --- a/code/API_definitions/device-reachability-status-subscriptions.yaml +++ b/code/API_definitions/device-reachability-status-subscriptions.yaml @@ -68,7 +68,7 @@ info: license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html - version: wip + version: 0.6.1 x-camara-commonalities: 0.4.0 externalDocs: description: Product documentation at CAMARA From 8956352a1afeef8e91c6963a16cbc432009e02f7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Sat, 5 Oct 2024 17:45:53 +0200 Subject: [PATCH 02/29] 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 099b77f..948fbcf 100644 --- a/code/API_definitions/device-reachability-status.yaml +++ b/code/API_definitions/device-reachability-status.yaml @@ -69,7 +69,7 @@ info: license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html - version: wip + version: 0.6.1 x-camara-commonalities: 0.4.0 externalDocs: description: Product documentation at CAMARA From 8e4afa3feb0a96bae93dcb1eba548d5205a96271 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Sat, 5 Oct 2024 17:46:37 +0200 Subject: [PATCH 03/29] 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 96066d9..ff1e6f6 100644 --- a/code/API_definitions/device-roaming-status-subscriptions.yaml +++ b/code/API_definitions/device-roaming-status-subscriptions.yaml @@ -70,7 +70,7 @@ info: license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html - version: wip + version: 0.6.1 x-camara-commonalities: 0.4.0 externalDocs: description: Product documentation at CAMARA From 35d4a1ea88127e0c05a9a0d85134cc8342d0757c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Sat, 5 Oct 2024 17:49:36 +0200 Subject: [PATCH 04/29] 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 f289e3f..0d486ac 100644 --- a/code/API_definitions/device-roaming-status.yaml +++ b/code/API_definitions/device-roaming-status.yaml @@ -76,7 +76,7 @@ info: license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html - version: wip + version: 0.6.0 x-camara-commonalities: 0.4.0 externalDocs: description: Product documentation at CAMARA From 8beaf1b0da8c46d5d7eb16e0e28577786f600200 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Sat, 5 Oct 2024 18:39:17 +0200 Subject: [PATCH 05/29] Update CHANGELOG.md --- CHANGELOG.md | 84 ++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 84 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 4d15442..8f5e320 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,6 @@ # Changelog DeviceStatus ## Table of Contents +- [r1.3](#r13) - [r1.2](#r12) - [r1.1](#r11) - [r0.6](#r06) @@ -17,6 +18,89 @@ The below sections record the changes for each API version in each release as fo * for subsequent alpha or release-candidate API versions, the delta with respect to the previous pre-release * for a public API version, the consolidated changes since the release of the previous public API version +# r1.3 +## Release Notes + +This release contains the definition and documentation of +* device-roaming-status v0.6.0 +* device-roaming-status-subscriptions v0.6.1 +* device-reachability-status v0.6.1 +* device-reachability-status-subscriptions v0.6.1 + +The API definition(s) are based on +* Commonalities v0.4.0 +* Identity and Consent Management v0.2.0 + +Note: the previous device-status API with roaming and connectivity endpoints has been split into 4 specific APIs + +## device-roaming-status v0.6.0 + +- API definition **with inline documentation**: + - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r1.3/code/API_definitions/device-roaming-status.yaml&nocors) + - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r1.3/code/API_definitions/device-roaming-status.yaml) + - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r1.3/code/API_definitions/device-roaming-status.yaml) + +### Added + +### Changed + +### Fixed + +### Removed + +## device-roaming-status-subscriptions v0.6.1 + +- API definition **with inline documentation**: + - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r1.3/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/r1.3/code/API_definitions/device-roaming-status-subscriptions.yaml) + - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r1.3/code/API_definitions/device-roaming-status-subscriptions.yaml) + +### Added + +### Changed + +### Fixed +* Add missing `protocol`-components for device-roaming-status-subscriptions by @maxl2287 in https://github.com/camaraproject/DeviceStatus/pull/208 +* Correct the examples for sub - initialEvent and error MULTIEVENT_SUBSCRIPTION_NOT_SUPPORTED by @dfischer-tech in https://github.com/camaraproject/DeviceStatus/pull/210 + +### Removed + + +## device-reachability-status v0.6.1 + +- API definition **with inline documentation**: + - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r1.3/code/API_definitions/device-reachability-status.yaml&nocors) + - [View it on Swagger Editor](https://editor.swagger.io/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r1.3/code/API_definitions/device-reachability-status.yaml) + - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r1.3/code/API_definitions/device-reachability-status.yaml) + +### Added + +### Changed +* Update description of the reachability types by @akoshunyadi in https://github.com/camaraproject/DeviceStatus/pull/215 + +### Fixed + +### Removed + +## device-reachability-status-subscriptions v0.6.1 + +- API definition **with inline documentation**: + - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r1.3/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/r1.3/code/API_definitions/device-reachability-status-subscriptions.yaml) + - OpenAPI [YAML spec file](https://github.com/camaraproject/DeviceStatus/blob/r1.3/code/API_definitions/device-reachability-status-subscriptions.yaml) + +### Added + +### Changed +* Update description of the reachability types by @akoshunyadi in https://github.com/camaraproject/DeviceStatus/pull/215 + +### Fixed +* Correct the examples for sub - initialEvent and error MULTIEVENT_SUBSCRIPTION_NOT_SUPPORTED by @dfischer-tech in https://github.com/camaraproject/DeviceStatus/pull/210 + +### Removed + +**Full Changelog**: https://github.com/camaraproject/DeviceStatus/compare/r1.2...r1.3 + # r1.2 ## Release Notes From 4c782ced51e604fa1fa5afa93f859ba2f2e8513e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Thu, 10 Oct 2024 20:54:52 +0200 Subject: [PATCH 06/29] 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 8f5e320..141376f 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -21,7 +21,7 @@ The below sections record the changes for each API version in each release as fo # r1.3 ## Release Notes -This release contains the definition and documentation of +This patch release contains the definition and documentation of * device-roaming-status v0.6.0 * device-roaming-status-subscriptions v0.6.1 * device-reachability-status v0.6.1 From 8b981e294c815016b66add7a4820797a773e65ad Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Thu, 10 Oct 2024 20:55:43 +0200 Subject: [PATCH 07/29] 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 141376f..d618c71 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -31,7 +31,7 @@ The API definition(s) are based on * Commonalities v0.4.0 * Identity and Consent Management v0.2.0 -Note: the previous device-status API with roaming and connectivity endpoints has been split into 4 specific APIs +Note: these patch release notes are listing only the change compared to the [r1.2](https://github.com/camaraproject/DeviceStatus/releases/tag/r1.2) release. For the full list of changes of the 0.6.0 API versions compared to 0.5.x see [r1.2](#r12). ## device-roaming-status v0.6.0 From 66fb17e99226877de6fa89845eeef68304776e40 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Thu, 10 Oct 2024 23:16:30 +0200 Subject: [PATCH 08/29] 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 3d6cbb8..a2d3100 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.6.0 in r1.2. +Checklist for device-reachability-status-subscriptions 0.6.1 in r1.3. | Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Comments | |----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:| From b137d0a5c9ae614a3f100cb0dfe6d19cd787efcf Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Thu, 10 Oct 2024 23:16:57 +0200 Subject: [PATCH 09/29] 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 686142a..07a80c6 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 0.6.0 in r1.2. +Checklist for device-reachability-status 0.6.1 in r1.3. | Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Comments | |----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:| From 12be6b7c5a9132b8030a2b9685fda56c9801b35a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Thu, 10 Oct 2024 23:17:17 +0200 Subject: [PATCH 10/29] 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 977e8d2..bdeb2d8 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.6.0 in r1.2. +Checklist for device-roaming-status-subscriptions 0.6.1 in r1.3. | Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Comments | |----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:| From 4294b42acd51fdf9b1a51c4fd65a99856d1c415e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 17:37:49 +0100 Subject: [PATCH 11/29] update ICM version --- CHANGELOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index d618c71..f0ac26e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -29,7 +29,7 @@ This patch release contains the definition and documentation of The API definition(s) are based on * Commonalities v0.4.0 -* Identity and Consent Management v0.2.0 +* Identity and Consent Management v0.2.1 Note: these patch release notes are listing only the change compared to the [r1.2](https://github.com/camaraproject/DeviceStatus/releases/tag/r1.2) release. For the full list of changes of the 0.6.0 API versions compared to 0.5.x see [r1.2](#r12). From 9ed421551873f9efe83f9797ec5757e31f0186bd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 17:49:33 +0100 Subject: [PATCH 12/29] Update device-roaming-status-subscriptions.yaml --- .../device-roaming-status-subscriptions.yaml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/code/API_definitions/device-roaming-status-subscriptions.yaml b/code/API_definitions/device-roaming-status-subscriptions.yaml index ff1e6f6..1ded505 100644 --- a/code/API_definitions/device-roaming-status-subscriptions.yaml +++ b/code/API_definitions/device-roaming-status-subscriptions.yaml @@ -2,7 +2,7 @@ openapi: 3.0.3 info: title: Device Roaming Status Subscriptions description: | - This API provides the customer with the ability to subscribe to Roaming status events. + This API provides the API consumer with the ability to subscribe to Roaming status events. # Introduction @@ -14,7 +14,7 @@ info: # Relevant terms and definitions * **Device**: A device refers to any physical entity that can connect to a network and participate in network communication. - At least one identifier for the device (user equipment) out of four options: IPv4 address, IPv6 address, Phone number, or Network Access Identifier assigned by the mobile network operator for the device. + At least one identifier for the device (user equipment) out of four options: IPv4 address, IPv6 address, Phone number, or Network Access Identifier (not supported for this API version) assigned by the mobile network operator for the device. # API Functionality @@ -59,13 +59,13 @@ info: (FAQs will be added in a later version of the documentation) - # Authorization and authentication + ### Authorization and authentication - [Camara Security and Interoperability Profile](https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-Security-Interoperability.md) provides details on how a client requests an access token. + 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 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. + 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. - 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. + 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. license: name: Apache 2.0 From a8fbd25f27bf2a9b27ca58dbc1dac01c03f31833 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 17:52:37 +0100 Subject: [PATCH 13/29] Update device-reachability-status-subscriptions.yaml --- .../device-reachability-status-subscriptions.yaml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/code/API_definitions/device-reachability-status-subscriptions.yaml b/code/API_definitions/device-reachability-status-subscriptions.yaml index a23941d..682fad7 100644 --- a/code/API_definitions/device-reachability-status-subscriptions.yaml +++ b/code/API_definitions/device-reachability-status-subscriptions.yaml @@ -2,7 +2,7 @@ openapi: 3.0.3 info: title: Device Reachability Status Subscriptions description: | - This API provides the customer with the ability to subscribe to Reachability status events. + This API provides the API consumer with the ability to subscribe to Reachability status events. # Introduction @@ -14,7 +14,7 @@ info: # Relevant terms and definitions * **Device**: A device refers to any physical entity that can connect to a network and participate in network communication. - At least one identifier for the device (user equipment) out of four options: IPv4 address, IPv6 address, Phone number, or Network Access Identifier assigned by the mobile network operator for the device. + At least one identifier for the device (user equipment) out of four options: IPv4 address, IPv6 address, Phone number, or Network Access Identifier (not supported for this API version) assigned by the mobile network operator for the device. # API Functionality @@ -56,10 +56,10 @@ info: ## Further info and support (FAQs will be added in a later version of the documentation) + + ### Authorization and authentication - # Authorization and authentication - - [Camara Security and Interoperability Profile](https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-Security-Interoperability.md) provides details on how a client requests an access token. + 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 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. From af9718513b9eca3512e3b2241583e6a0c310bbba Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 17:55:21 +0100 Subject: [PATCH 14/29] Update device-reachability-status.yaml --- code/API_definitions/device-reachability-status.yaml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/code/API_definitions/device-reachability-status.yaml b/code/API_definitions/device-reachability-status.yaml index 948fbcf..07243a2 100644 --- a/code/API_definitions/device-reachability-status.yaml +++ b/code/API_definitions/device-reachability-status.yaml @@ -2,7 +2,7 @@ openapi: 3.0.3 info: title: Device Reachability Status description: | - This API provides the customer with the ability to query device reachability status. + This API provides the API consumer with the ability to query device reachability status. # Introduction @@ -13,7 +13,7 @@ info: ## Relevant terms and definitions * **Device**: A device refers to any physical entity that can connect to a network and participate in network communication. - At least one identifier for the device (user equipment) out of four options: IPv4 address, IPv6 address, Phone number, or Network Access Identifier assigned by the mobile network operator for the device. + At least one identifier for the device (user equipment) out of four options: IPv4 address, IPv6 address, Phone number, or Network Access Identifier (not supported for this API version) assigned by the mobile network operator for the device. * **Reachability** : Reachability status. - `CONNECTED_SMS`, if device is connected to the network only via SMS usage @@ -30,14 +30,14 @@ info: The endpoint `POST /retrieve` allows to get current connectivity status information synchronously. - # Authorization and authentication + ### Authorization and authentication - [Camara Security and Interoperability Profile](https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-Security-Interoperability.md) provides details on how a client requests an access token. + 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 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. 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. - + # Identifying a device from the access token This specification defines the `device` object field as optional in API requests, specifically in cases where the API is accessed using a 3-legged access token, and the device can be uniquely identified by the token. This approach simplifies API usage for API consumers by relying on the device information associated with the access token used to invoke the API. From 5c61f798d22f885a4c1120cfa49c9cfd39136335 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 17:57:22 +0100 Subject: [PATCH 15/29] Update device-roaming-status.yaml --- code/API_definitions/device-roaming-status.yaml | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/code/API_definitions/device-roaming-status.yaml b/code/API_definitions/device-roaming-status.yaml index 0d486ac..ca219fc 100644 --- a/code/API_definitions/device-roaming-status.yaml +++ b/code/API_definitions/device-roaming-status.yaml @@ -2,7 +2,7 @@ openapi: 3.0.3 info: title: Device Roaming Status description: | - This API provides the customer with the ability to query device roaming Status + This API provides the API consumer with the ability to query device roaming Status # Introduction @@ -21,7 +21,7 @@ info: ## Relevant terms and definitions * **Device**: A device refers to any physical entity that can connect to a network and participate in network communication. - At least one identifier for the device (user equipment) out of four options: IPv4 address, IPv6 address, Phone number, or Network Access Identifier assigned by the mobile network operator for the device. + At least one identifier for the device (user equipment) out of four options: IPv4 address, IPv6 address, Phone number, or Network Access Identifier (not supported for this API version) assigned by the mobile network operator for the device. * **Roaming** : Roaming status - `true`, if device is in roaming situation - `false` else. @@ -37,14 +37,14 @@ info: The endpoint `POST /retrieve` allows to get roaming status and country information (if device in roaming situation) synchronously. - # Authorization and authentication + ### Authorization and authentication - [Camara Security and Interoperability Profile](https://github.com/camaraproject/IdentityAndConsentManagement/blob/main/documentation/CAMARA-Security-Interoperability.md) provides details on how a client requests an access token. + 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 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. 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. - + # Identifying a device from the access token This specification defines the `device` object field as optional in API requests, specifically in cases where the API is accessed using a 3-legged access token, and the device can be uniquely identified by the token. This approach simplifies API usage for API consumers by relying on the device information associated with the access token used to invoke the API. @@ -76,7 +76,7 @@ info: license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html - version: 0.6.0 + version: 0.6.1 x-camara-commonalities: 0.4.0 externalDocs: description: Product documentation at CAMARA From da7bd6b0b5f951fdb5e2747e228350b147980ef7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 17:57:55 +0100 Subject: [PATCH 16/29] 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 44e3dae..2abe08e 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 0.6.0 in r1.2. +Checklist for device-roaming-status 0.6.1 in r1.3. | Nr | API release assets | alpha | release-candidate | initial
public | stable
public | Status | Comments | |----|----------------------------------------------|:-----:|:-----------------:|:-------:|:------:|:----:|:----:| From cd4340f56debcacf19adae5cc7c20af4045f8393 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 17:59:06 +0100 Subject: [PATCH 17/29] Update README.md --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 27cdc0f..324e836 100644 --- a/README.md +++ b/README.md @@ -7,12 +7,12 @@ # DeviceStatus -Repository to describe, develop, document and test the DeviceStatus API family +Repository to describe, develop, document and test the DeviceStatus APIs ## Scope * Service APIs for “Device Status” (see [APIBacklog.md](https://github.com/camaraproject/APIBacklog/blob/main/documentation/APIbacklog.md)) -* It provides the customer with the ability to: - - check if a device is reachable or has lost connectivity to the network +* It provides the API consumer with the ability to: + - 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) From b7ffa80173aa0ffa7a0990a7e17b95ad4bf5f920 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 20:51:06 +0100 Subject: [PATCH 18/29] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 324e836..bdc08c8 100644 --- a/README.md +++ b/README.md @@ -29,7 +29,7 @@ Repository to describe, develop, document and test the DeviceStatus APIs ## Contributing * Meetings - * Bi-weekly on Wednesday, 11:00 CET/CEST (08:00 UTC, 09:00 UTC during European DST) + * Bi-weekly on Wednesday, 09:00 UTC * [Registration / Join](https://zoom-lfx.platform.linuxfoundation.org/meeting/93413850406?password=3aeb0f1b-d9f9-42c5-91d8-3d2b20421ef1) * Access [meeting minutes](https://lf-camaraproject.atlassian.net/wiki/x/fzLe) * Mailing List From 3b0d5b1b6d627c7b6e8847b50e7bba30abd8c81b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 20:55:36 +0100 Subject: [PATCH 19/29] Update CHANGELOG.md --- CHANGELOG.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index f0ac26e..f2a57ff 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -22,7 +22,7 @@ The below sections record the changes for each API version in each release as fo ## Release Notes This patch release contains the definition and documentation of -* device-roaming-status v0.6.0 +* device-roaming-status v0.6.1 * device-roaming-status-subscriptions v0.6.1 * device-reachability-status v0.6.1 * device-reachability-status-subscriptions v0.6.1 @@ -33,7 +33,7 @@ The API definition(s) are based on Note: these patch release notes are listing only the change compared to the [r1.2](https://github.com/camaraproject/DeviceStatus/releases/tag/r1.2) release. For the full list of changes of the 0.6.0 API versions compared to 0.5.x see [r1.2](#r12). -## device-roaming-status v0.6.0 +## device-roaming-status v0.6.1 - API definition **with inline documentation**: - [View it on ReDoc](https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/camaraproject/DeviceStatus/r1.3/code/API_definitions/device-roaming-status.yaml&nocors) @@ -45,6 +45,7 @@ Note: these patch release notes are listing only the change compared to the [r1. ### Changed ### Fixed +* Minor corrections in info.description ### Removed @@ -62,6 +63,7 @@ Note: these patch release notes are listing only the change compared to the [r1. ### Fixed * Add missing `protocol`-components for device-roaming-status-subscriptions by @maxl2287 in https://github.com/camaraproject/DeviceStatus/pull/208 * Correct the examples for sub - initialEvent and error MULTIEVENT_SUBSCRIPTION_NOT_SUPPORTED by @dfischer-tech in https://github.com/camaraproject/DeviceStatus/pull/210 +* Minor corrections in info.description ### Removed @@ -79,6 +81,7 @@ Note: these patch release notes are listing only the change compared to the [r1. * Update description of the reachability types by @akoshunyadi in https://github.com/camaraproject/DeviceStatus/pull/215 ### Fixed +* Minor corrections in info.description ### Removed @@ -96,6 +99,7 @@ Note: these patch release notes are listing only the change compared to the [r1. ### Fixed * Correct the examples for sub - initialEvent and error MULTIEVENT_SUBSCRIPTION_NOT_SUPPORTED by @dfischer-tech in https://github.com/camaraproject/DeviceStatus/pull/210 +* Minor corrections in info.description ### Removed From 382bec86286ec90f9bd84fd0e0bf9d9ba0df2a43 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 20:58:14 +0100 Subject: [PATCH 20/29] 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 682fad7..1102e8d 100644 --- a/code/API_definitions/device-reachability-status-subscriptions.yaml +++ b/code/API_definitions/device-reachability-status-subscriptions.yaml @@ -72,7 +72,7 @@ info: x-camara-commonalities: 0.4.0 externalDocs: description: Product documentation at CAMARA - url: https://github.com/camaraproject/ + url: https://github.com/camaraproject/DeviceStatus servers: - url: "{apiRoot}/device-reachability-status-subscriptions/v0.6" From 25e4dd7cba9ef6411dde7215466f91e8cdcc36b1 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 21:00:06 +0100 Subject: [PATCH 21/29] 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 07243a2..d5b58ca 100644 --- a/code/API_definitions/device-reachability-status.yaml +++ b/code/API_definitions/device-reachability-status.yaml @@ -73,7 +73,7 @@ info: x-camara-commonalities: 0.4.0 externalDocs: description: Product documentation at CAMARA - url: https://github.com/camaraproject/ + url: https://github.com/camaraproject/DeviceStatus servers: - url: "{apiRoot}/device-reachability-status/v0.6" From eb7fde9452bdac7f59654023cfab831e241b2bfc Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 21:01:03 +0100 Subject: [PATCH 22/29] 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 1ded505..41c34e0 100644 --- a/code/API_definitions/device-roaming-status-subscriptions.yaml +++ b/code/API_definitions/device-roaming-status-subscriptions.yaml @@ -74,7 +74,7 @@ info: x-camara-commonalities: 0.4.0 externalDocs: description: Product documentation at CAMARA - url: https://github.com/camaraproject/ + url: https://github.com/camaraproject/DeviceStatus servers: - url: "{apiRoot}/device-roaming-status-subscriptions/v0.6" From d58b2171dbcf05c1b4d3b04fabdf5b6246bd2f30 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 21:02:08 +0100 Subject: [PATCH 23/29] 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 ca219fc..e56135c 100644 --- a/code/API_definitions/device-roaming-status.yaml +++ b/code/API_definitions/device-roaming-status.yaml @@ -80,7 +80,7 @@ info: x-camara-commonalities: 0.4.0 externalDocs: description: Product documentation at CAMARA - url: https://github.com/camaraproject/ + url: https://github.com/camaraproject/DeviceStatus servers: - url: "{apiRoot}/device-roaming-status/v0.6" From f2f20219b7e25fc6218bc250672a2cff93f3af65 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 22:34:36 +0100 Subject: [PATCH 24/29] 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 1102e8d..3d1349f 100644 --- a/code/API_definitions/device-reachability-status-subscriptions.yaml +++ b/code/API_definitions/device-reachability-status-subscriptions.yaml @@ -56,7 +56,7 @@ info: ## Further info and support (FAQs will be added in a later version of the documentation) - + ### 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. From 633d073fab66f71bf5ca92e31cb1b87a6506e2b7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 22:35:38 +0100 Subject: [PATCH 25/29] 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 d5b58ca..d7df64e 100644 --- a/code/API_definitions/device-reachability-status.yaml +++ b/code/API_definitions/device-reachability-status.yaml @@ -37,7 +37,7 @@ info: 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. 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. - + # Identifying a device from the access token This specification defines the `device` object field as optional in API requests, specifically in cases where the API is accessed using a 3-legged access token, and the device can be uniquely identified by the token. This approach simplifies API usage for API consumers by relying on the device information associated with the access token used to invoke the API. From be2f5c5d086104d883fdbe6cf51e80cf5f5aaafe Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 22:38:25 +0100 Subject: [PATCH 26/29] 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 e56135c..279841a 100644 --- a/code/API_definitions/device-roaming-status.yaml +++ b/code/API_definitions/device-roaming-status.yaml @@ -44,7 +44,7 @@ info: 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. 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. - + # Identifying a device from the access token This specification defines the `device` object field as optional in API requests, specifically in cases where the API is accessed using a 3-legged access token, and the device can be uniquely identified by the token. This approach simplifies API usage for API consumers by relying on the device information associated with the access token used to invoke the API. From 32d08d1fb0ad21712eafa7c6ab401466b459583d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 22:41:27 +0100 Subject: [PATCH 27/29] Update device-roaming-status-subscriptions.yaml --- .../device-roaming-status-subscriptions.yaml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/code/API_definitions/device-roaming-status-subscriptions.yaml b/code/API_definitions/device-roaming-status-subscriptions.yaml index 41c34e0..e9417cd 100644 --- a/code/API_definitions/device-roaming-status-subscriptions.yaml +++ b/code/API_definitions/device-roaming-status-subscriptions.yaml @@ -59,13 +59,13 @@ info: (FAQs will be added in a later version of the documentation) - ### Authorization and authentication + ### 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 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 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. + 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. - 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. + 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. license: name: Apache 2.0 From 960cceca394cca2e9574928c2e24fdc16725a040 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Wed, 30 Oct 2024 22:47:06 +0100 Subject: [PATCH 28/29] 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 e9417cd..3900f9a 100644 --- a/code/API_definitions/device-roaming-status-subscriptions.yaml +++ b/code/API_definitions/device-roaming-status-subscriptions.yaml @@ -59,7 +59,7 @@ info: (FAQs will be added in a later version of the documentation) - ### Authorization and authentication + ### 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. From 798a0ebc06b6679f1076953609b20b6ec8d17b8d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=81kos=20Hunyadi?= <67875049+akoshunyadi@users.noreply.github.com> Date: Thu, 31 Oct 2024 09:11:02 +0100 Subject: [PATCH 29/29] Update CHANGELOG.md --- CHANGELOG.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index f2a57ff..b1a344a 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -45,7 +45,7 @@ Note: these patch release notes are listing only the change compared to the [r1. ### Changed ### Fixed -* Minor corrections in info.description +* Minor corrections in info.description by @akoshunyadi in https://github.com/camaraproject/DeviceStatus/pull/216 ### Removed @@ -63,7 +63,7 @@ Note: these patch release notes are listing only the change compared to the [r1. ### Fixed * Add missing `protocol`-components for device-roaming-status-subscriptions by @maxl2287 in https://github.com/camaraproject/DeviceStatus/pull/208 * Correct the examples for sub - initialEvent and error MULTIEVENT_SUBSCRIPTION_NOT_SUPPORTED by @dfischer-tech in https://github.com/camaraproject/DeviceStatus/pull/210 -* Minor corrections in info.description +* Minor corrections in info.description by @akoshunyadi in https://github.com/camaraproject/DeviceStatus/pull/216 ### Removed @@ -81,7 +81,7 @@ Note: these patch release notes are listing only the change compared to the [r1. * Update description of the reachability types by @akoshunyadi in https://github.com/camaraproject/DeviceStatus/pull/215 ### Fixed -* Minor corrections in info.description +* Minor corrections in info.description by @akoshunyadi in https://github.com/camaraproject/DeviceStatus/pull/216 ### Removed @@ -99,7 +99,7 @@ Note: these patch release notes are listing only the change compared to the [r1. ### Fixed * Correct the examples for sub - initialEvent and error MULTIEVENT_SUBSCRIPTION_NOT_SUPPORTED by @dfischer-tech in https://github.com/camaraproject/DeviceStatus/pull/210 -* Minor corrections in info.description +* Minor corrections in info.description by @akoshunyadi in https://github.com/camaraproject/DeviceStatus/pull/216 ### Removed