Skip to content

Commit a9c52fb

Browse files
committed
fixed linting errors related to trailing spaces.
1 parent 271930a commit a9c52fb

File tree

1 file changed

+19
-18
lines changed

1 file changed

+19
-18
lines changed

code/API_definitions/Application-endpoint-registration.yaml

+19-18
Original file line numberDiff line numberDiff line change
@@ -1,40 +1,40 @@
1-
openapi: 3.0.3
1+
---openapi: 3.0.3
22
info:
33
title: Application Endpoint Registration API
44
version: 0.1.0
55
license:
66
name: Apache 2.0
77
url: https://www.apache.org/licenses/LICENSE-2.0.html
88
description: |
9-
Application endpoint registration allows application developers to
10-
register one or more Application Endpoints, and retrieve, update,and
9+
Application endpoint registration allows application developers to
10+
register one or more Application Endpoints, and retrieve, update,and
1111
delete those egistrations.
1212
13-
This information can we used for various usecases like optimal end
14-
point discovery to help end users connect to the most most optimal
13+
This information can we used for various usecases like optimal end
14+
point discovery to help end users connect to the most most optimal
1515
instance of the application. Addtionally the information can be used
16-
to also monitor the different instance to take decisions from a lifecycle
16+
to also monitor the different instance to take decisions from a lifecycle
1717
mangement perspective.
1818
1919
### Authorization and authentication
2020
21-
The "Camara Security and Interoperability Profile" provides details on
22-
how a client requests an access token. Please refer to Identify and
23-
Consent Management
24-
(https://github.com/camaraproject/IdentityAndConsentManagement/)
21+
The "Camara Security and Interoperability Profile" provides details on
22+
how a client requests an access token. Please refer to Identify and
23+
Consent Management
24+
(https://github.com/camaraproject/IdentityAndConsentManagement/)
2525
for the released version of the Profile.
2626
2727
Which specific authorization flows are to be used will be determined
28-
during onboarding process, happening between the API Client and the
29-
Telco Operator exposing the API, taking into account the declared
28+
during onboarding process, happening between the API Client and the
29+
Telco Operator exposing the API, taking into account the declared
3030
purpose for accessing the API, while also being subject to the prevailing
3131
legal framework dictated by local legislation.
3232
33-
It is important to remark that in cases where personal user data
34-
is processed by the API, and users can exercise their rights through
35-
mechanisms such as opt-in and/or opt-out, the use of 3-legged access
36-
tokens becomes mandatory. This measure ensures that the API remains in
37-
strict compliance with user privacy preferences and regulatory obligations,
33+
It is important to remark that in cases where personal user data
34+
is processed by the API, and users can exercise their rights through
35+
mechanisms such as opt-in and/or opt-out, the use of 3-legged access
36+
tokens becomes mandatory. This measure ensures that the API remains in
37+
strict compliance with user privacy preferences and regulatory obligations,
3838
upholding the principles of transparency and user-centric data control.
3939
4040
x-camara-commonalities: 0.4.0
@@ -51,7 +51,8 @@ servers:
5151
tags:
5252
- name: Application Endpoint Registration
5353
description: |
54-
Operations to register, read and manage an deployed instances of the application.
54+
Operations to register, read and manage an deployed instances of the
55+
application.
5556
5657
paths:
5758
/application-endpoints:

0 commit comments

Comments
 (0)