From ac09c0f926b687d3072aa11028d8da98e75e8d62 Mon Sep 17 00:00:00 2001
From: FabrizioMoggio <87469955+FabrizioMoggio@users.noreply.github.com>
Date: Fri, 5 Jul 2024 15:23:38 +0200
Subject: [PATCH] MegaLinter Fix

---
 code/API_definitions/Traffic_Influence.yaml | 56 ++++++++++-----------
 1 file changed, 28 insertions(+), 28 deletions(-)

diff --git a/code/API_definitions/Traffic_Influence.yaml b/code/API_definitions/Traffic_Influence.yaml
index d0a8b35..a8dddcd 100644
--- a/code/API_definitions/Traffic_Influence.yaml
+++ b/code/API_definitions/Traffic_Influence.yaml
@@ -738,36 +738,36 @@ components:
       type: string
       additionalProperties: false
     Device:
-     description: |
-       End-user equipment able to connect to a mobile network. Examples of
-       devices include smartphones or IoT sensors/actuators.
-       The developer can choose to provide the below specified device
-       identifiers:
-       * `ipv4Address`
-       * `ipv6Address`
-       * `phoneNumber`
-       * `networkAccessIdentifier`
-       NOTE1: the MNO might support only a subset of these options.
-       The API invoker can provide multiple identifiers to be compatible
-       across different MNOs. In this case the identifiers MUST belong to
-       the same device.
-       NOTE2: for the Commonalities release v0.4, we are enforcing that the
-       networkAccessIdentifier is only part of the schema for
-       future-proofing, and CAMARA does not currently allow its use.
-       After the CAMARA meta-release work is concluded and the relevant
-       issues are resolved, its use will need to be explicitly documented
-       in the guidelines.
-     type: object
-     properties:
-      phoneNumber:
-        $ref: "#/components/schemas/PhoneNumber"
-      networkAccessIdentifier:
+      description: |
+        End-user equipment able to connect to a mobile network. Examples of
+        devices include smartphones or IoT sensors/actuators.
+        The developer can choose to provide the below specified device
+        identifiers:
+        * `ipv4Address`
+        * `ipv6Address`
+        * `phoneNumber`
+        * `networkAccessIdentifier`
+        NOTE1: the MNO might support only a subset of these options.
+        The API invoker can provide multiple identifiers to be compatible
+        across different MNOs. In this case the identifiers MUST belong to
+        the same device.
+        NOTE2: for the Commonalities release v0.4, we are enforcing that the
+        networkAccessIdentifier is only part of the schema for
+        future-proofing, and CAMARA does not currently allow its use.
+        After the CAMARA meta-release work is concluded and the relevant
+        issues are resolved, its use will need to be explicitly documented
+        in the guidelines.
+      type: object
+      properties:
+       phoneNumber:
+         $ref: "#/components/schemas/PhoneNumber"
+       networkAccessIdentifier:
         $ref: "#/components/schemas/NetworkAccessIdentifier"
-      ipv4Address:
+       ipv4Address:
         $ref: "#/components/schemas/DeviceIpv4Addr"
-      ipv6Address:
-        $ref: "#/components/schemas/DeviceIpv6Address"
-     minProperties: 1
+       ipv6Address:
+         $ref: "#/components/schemas/DeviceIpv6Address"
+      minProperties: 1
     PhoneNumber:
       description: A public identifier addressing a telephone subscription. In
         mobile networks it corresponds to the MSISDN (Mobile Station