From b1bd85653430fcd0b5db3b9973ef77d1a3382df6 Mon Sep 17 00:00:00 2001 From: DlondonoD Date: Thu, 4 Jun 2026 18:36:53 +0200 Subject: [PATCH 1/2] fix: mandatory templates for info.description --- .../edge-application-management.yaml | 26 +++++++++++++++++-- 1 file changed, 24 insertions(+), 2 deletions(-) diff --git a/code/API_definitions/edge-application-management.yaml b/code/API_definitions/edge-application-management.yaml index 694ef0d..43d028f 100644 --- a/code/API_definitions/edge-application-management.yaml +++ b/code/API_definitions/edge-application-management.yaml @@ -87,6 +87,8 @@ info: status, ordering the results by location and filtering by status (active/inactive/unknown) + + # Authorization and authentication 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. @@ -94,7 +96,7 @@ info: 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. - + 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 @@ -102,6 +104,7 @@ info: 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. + # API documentation Two operations have been defined in Edge Application Management API. @@ -152,8 +155,27 @@ info: abstraction exposed to an Application Provider who wants to deploy an Application on Edge Cloud. Edge Cloud Zones exists within a Edge Cloud Region. + + + + # Additional CAMARA error responses + + The list of error codes in this API specification is not exhaustive. Therefore the API specification MAY not document some non-mandatory error statuses as indicated in `CAMARA API Design Guide`. + + Please refer to the `CAMARA_common.yaml` of the Commonalities Release associated to this API version for a complete list of error responses. The applicable Commonalities Release can be identified in the `API Readiness Checklist` document associated to this API version. + + As a specific rule, error `501 - NOT_IMPLEMENTED` can be only a possible error response if it is explicitly documented in the API. + + + + + # Request body strictness + + This API rejects requests with JSON request bodies that contain properties not declared in this specification, at any nesting level. Unknown properties result in a `400 INVALID_ARGUMENT` response. + + --- - x-camara-commonalities: 0.8.0-rc.2 + x-camara-commonalities: 0.8.0 license: name: Apache 2.0 url: https://www.apache.org/licenses/LICENSE-2.0.html From 3223cc86ebc6ea70c879c3f988690cba4e680766 Mon Sep 17 00:00:00 2001 From: DlondonoD Date: Thu, 4 Jun 2026 19:00:46 +0200 Subject: [PATCH 2/2] fix: mandatory templates for info.description - spaces correction --- code/API_definitions/edge-application-management.yaml | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/code/API_definitions/edge-application-management.yaml b/code/API_definitions/edge-application-management.yaml index 43d028f..76f78ca 100644 --- a/code/API_definitions/edge-application-management.yaml +++ b/code/API_definitions/edge-application-management.yaml @@ -88,7 +88,7 @@ info: (active/inactive/unknown) - + # Authorization and authentication 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. @@ -157,7 +157,7 @@ info: Edge Cloud Zones exists within a Edge Cloud Region. - + # Additional CAMARA error responses The list of error codes in this API specification is not exhaustive. Therefore the API specification MAY not document some non-mandatory error statuses as indicated in `CAMARA API Design Guide`. @@ -168,7 +168,7 @@ info: - + # Request body strictness This API rejects requests with JSON request bodies that contain properties not declared in this specification, at any nesting level. Unknown properties result in a `400 INVALID_ARGUMENT` response.