rsmp_schema 0.8.4 → 0.8.6

data/schemas/tlc/1.0.14/sxl.yaml

@@ -469,7 +469,7 @@ objects:
               Function legend:
               0=no plan is selected by time table
               1=set plan 1
-              …
+              ...
               16= set plan 16
               
               hour and minute is using local time (not UTC)
@@ -589,7 +589,7 @@ objects:
               Number of vehicles.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
       S0206:
         description: |-
@@ -608,7 +608,7 @@ objects:
               Average speed in km/h (integer).
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
       S0207:
         description: |-
@@ -627,7 +627,7 @@ objects:
               Occupancy in percent (%) (0-100)
               - Value expressed as an integer with a range of 0-100.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-100,...]"
       S0208:
         description: |-
@@ -646,7 +646,7 @@ objects:
               Number of cars.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           PS:
             type: string
@@ -654,7 +654,7 @@ objects:
               Number of cars with trailers.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           L:
             type: string
@@ -662,7 +662,7 @@ objects:
               Number of trucks.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           LS:
             type: string
@@ -670,7 +670,7 @@ objects:
               Number of trucks with trailers.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           B:
             type: string
@@ -678,7 +678,7 @@ objects:
               Number of busses.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           SP:
             type: string
@@ -686,7 +686,7 @@ objects:
               Number of trams.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           MC:
             type: string
@@ -694,7 +694,7 @@ objects:
               Number of motor cycles.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           C:
             type: string
@@ -702,7 +702,7 @@ objects:
               Number of bicycles.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           F:
             type: string
@@ -710,7 +710,7 @@ objects:
               Number of pedestrians.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
     commands:
       M0001:
@@ -873,7 +873,7 @@ objects:
               1=Order signal group to green
               0=Order signal group to red
               
-              Format: [Offset],[Bits to set],[Bits to unset]:…
+              Format: [Offset],[Bits to set],[Bits to unset]:...
               
               Offset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.
               
@@ -906,7 +906,7 @@ objects:
             description: |-
               Sets/Unsets a block of 16 inputs at a time. Can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon, ":" is used in example below.
               
-              Format: [Offset],[Bits to set],[Bits to unset]:…
+              Format: [Offset],[Bits to set],[Bits to unset]:...
               
               Offset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.
               
@@ -1024,7 +1024,7 @@ objects:
               Function legend:
               0=no plan is selected by time table
               1=set plan 1
-              …
+              ...
               16= set plan 16
               
               hour and minute is using local time (not UTC)

data/schemas/tlc/1.0.15/commands/M0012.json

@@ -46,7 +46,7 @@
             "then" : {
               "properties" : {
                 "v" : {
-                  "description" : "Orders signal groups to green or red. Sets a block of 16 signal groups at a time. Can be repeated to set several blocks of 16 signal groups. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon is used in example below.\n\n1=Order signal group to green\n0=Order signal group to red\n\nFormat: [Offset],[Bits to set],[Bits to unset]:…\n\nOffset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.\n\nExample 1:\n\"5, 4134, 65\" sets input 6,7,10,17 = on and 5,11 = off\n(Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)\n\nExample 2:\n\"22, 1, 4\" sets input 22 = on and 24 = off\n(Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)\n\nAnd both these examples could be sent in the same message as:\n\"5,4143,65:22,1,4\"\n\nSuch a message would order signal group 6,7,10,17,22 to green and signal group 5,11,24 to red",
+                  "description" : "Orders signal groups to green or red. Sets a block of 16 signal groups at a time. Can be repeated to set several blocks of 16 signal groups. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon is used in example below.\n\n1=Order signal group to green\n0=Order signal group to red\n\nFormat: [Offset],[Bits to set],[Bits to unset]:...\n\nOffset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.\n\nExample 1:\n\"5, 4134, 65\" sets input 6,7,10,17 = on and 5,11 = off\n(Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)\n\nExample 2:\n\"22, 1, 4\" sets input 22 = on and 24 = off\n(Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)\n\nAnd both these examples could be sent in the same message as:\n\"5,4143,65:22,1,4\"\n\nSuch a message would order signal group 6,7,10,17,22 to green and signal group 5,11,24 to red",
                   "type" : "string"
                 }
               }

data/schemas/tlc/1.0.15/commands/M0013.json

@@ -46,7 +46,7 @@
             "then" : {
               "properties" : {
                 "v" : {
-                  "description" : "Sets/Unsets a block of 16 inputs at a time. Can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon, \":\" is used in example below.\n\nFormat: [Offset],[Bits to set],[Bits to unset]:…\n\nOffset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.\n\nExample 1:\n\"5, 4134, 65\" sets input 6,7,10,17 = on and 5,11 = off\n(Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)\n\nExample 2:\n\"22, 1, 4\" sets input 22 = on and 24 = off\n(Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)\n\nAnd both thease examples could be sent in the same message as:\n\"5,4143:65:22,1,4\"\n\nSuch a message would activate input 6,7,10,17,22 and deactivate input 5,11,24",
+                  "description" : "Sets/Unsets a block of 16 inputs at a time. Can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon, \":\" is used in example below.\n\nFormat: [Offset],[Bits to set],[Bits to unset]:...\n\nOffset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.\n\nExample 1:\n\"5, 4134, 65\" sets input 6,7,10,17 = on and 5,11 = off\n(Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)\n\nExample 2:\n\"22, 1, 4\" sets input 22 = on and 24 = off\n(Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)\n\nAnd both thease examples could be sent in the same message as:\n\"5,4143:65:22,1,4\"\n\nSuch a message would activate input 6,7,10,17,22 and deactivate input 5,11,24",
                   "type" : "string"
                 }
               }

data/schemas/tlc/1.0.15/commands/M0017.json

@@ -46,7 +46,7 @@
             "then" : {
               "properties" : {
                 "v" : {
-                  "description" : "Time Table. Defines time tables.\nEach time definition is written as t-o-h-m where:\nt=time table nr (1-12)\no=function\nh=hour - switching time\nm=minute - switching minute\n\nFunction legend:\n0=no plan is selected by time table\n1=set plan 1\n…\n16= set plan 16\n\nhour and minute is using local time (not UTC)\n\nEach time definition is separated with a comma.\n\nE.g.\nt-o-h-m,t-o-h-m",
+                  "description" : "Time Table. Defines time tables.\nEach time definition is written as t-o-h-m where:\nt=time table nr (1-12)\no=function\nh=hour - switching time\nm=minute - switching minute\n\nFunction legend:\n0=no plan is selected by time table\n1=set plan 1\n...\n16= set plan 16\n\nhour and minute is using local time (not UTC)\n\nEach time definition is separated with a comma.\n\nE.g.\nt-o-h-m,t-o-h-m",
                   "type" : "string"
                 }
               }

data/schemas/tlc/1.0.15/statuses/S0027.json

@@ -42,7 +42,7 @@
             "then" : {
               "properties" : {
                 "s" : {
-                  "description" : "Time Table. Defines time tables.\nEach time definition is written as t-o-h-m where:\nt=time table nr (1-12)\no=function\nh=hour - switching time\nm=minute - switching minute\n\nFunction legend:\n0=no plan is selected by time table\n1=set plan 1\n…\n16= set plan 16\n\nhour and minute is using local time (not UTC)\n\nEach time definition is separated with a comma\n\nE.g.\nt-o-h-m,t-o-h-m",
+                  "description" : "Time Table. Defines time tables.\nEach time definition is written as t-o-h-m where:\nt=time table nr (1-12)\no=function\nh=hour - switching time\nm=minute - switching minute\n\nFunction legend:\n0=no plan is selected by time table\n1=set plan 1\n...\n16= set plan 16\n\nhour and minute is using local time (not UTC)\n\nEach time definition is separated with a comma\n\nE.g.\nt-o-h-m,t-o-h-m",
                   "type" : "string"
                 }
               }

data/schemas/tlc/1.0.15/statuses/S0205.json

@@ -69,7 +69,7 @@
             "then" : {
               "properties" : {
                 "s" : {
-                  "description" : "Number of vehicles.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
+                  "description" : "Number of vehicles.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to \"-1\" if no data could be measured (e.g. detector fault)",
                   "type" : "string"
                 }
               }

data/schemas/tlc/1.0.15/statuses/S0206.json

@@ -69,7 +69,7 @@
             "then" : {
               "properties" : {
                 "s" : {
-                  "description" : "Average speed in km/h (integer).\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
+                  "description" : "Average speed in km/h (integer).\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to \"-1\" if no data could be measured (e.g. detector fault)",
                   "type" : "string"
                 }
               }

data/schemas/tlc/1.0.15/statuses/S0207.json

@@ -69,7 +69,7 @@
             "then" : {
               "properties" : {
                 "s" : {
-                  "description" : "Occupancy in percent (%) (0-100)\n- Value expressed as an integer with a range of 0-100.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
+                  "description" : "Occupancy in percent (%) (0-100)\n- Value expressed as an integer with a range of 0-100.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to \"-1\" if no data could be measured (e.g. detector fault)",
                   "type" : "string"
                 }
               }

data/schemas/tlc/1.0.15/statuses/S0208.json

@@ -77,7 +77,7 @@
             "then" : {
               "properties" : {
                 "s" : {
-                  "description" : "Number of cars.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
+                  "description" : "Number of cars.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to \"-1\" if no data could be measured (e.g. detector fault)",
                   "type" : "string"
                 }
               }
@@ -97,7 +97,7 @@
             "then" : {
               "properties" : {
                 "s" : {
-                  "description" : "Number of cars with trailers.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
+                  "description" : "Number of cars with trailers.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to \"-1\" if no data could be measured (e.g. detector fault)",
                   "type" : "string"
                 }
               }
@@ -117,7 +117,7 @@
             "then" : {
               "properties" : {
                 "s" : {
-                  "description" : "Number of trucks.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
+                  "description" : "Number of trucks.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to \"-1\" if no data could be measured (e.g. detector fault)",
                   "type" : "string"
                 }
               }
@@ -137,7 +137,7 @@
             "then" : {
               "properties" : {
                 "s" : {
-                  "description" : "Number of trucks with trailers.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
+                  "description" : "Number of trucks with trailers.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to \"-1\" if no data could be measured (e.g. detector fault)",
                   "type" : "string"
                 }
               }
@@ -157,7 +157,7 @@
             "then" : {
               "properties" : {
                 "s" : {
-                  "description" : "Number of busses.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
+                  "description" : "Number of busses.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to \"-1\" if no data could be measured (e.g. detector fault)",
                   "type" : "string"
                 }
               }
@@ -177,7 +177,7 @@
             "then" : {
               "properties" : {
                 "s" : {
-                  "description" : "Number of trams.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
+                  "description" : "Number of trams.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to \"-1\" if no data could be measured (e.g. detector fault)",
                   "type" : "string"
                 }
               }
@@ -197,7 +197,7 @@
             "then" : {
               "properties" : {
                 "s" : {
-                  "description" : "Number of motor cycles.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
+                  "description" : "Number of motor cycles.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to \"-1\" if no data could be measured (e.g. detector fault)",
                   "type" : "string"
                 }
               }
@@ -217,7 +217,7 @@
             "then" : {
               "properties" : {
                 "s" : {
-                  "description" : "Number of bicycles.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
+                  "description" : "Number of bicycles.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to \"-1\" if no data could be measured (e.g. detector fault)",
                   "type" : "string"
                 }
               }
@@ -237,7 +237,7 @@
             "then" : {
               "properties" : {
                 "s" : {
-                  "description" : "Number of pedestrians.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to “-1” if no data could be measured (e.g. detector fault)",
+                  "description" : "Number of pedestrians.\n- Value expressed as an integer with a range of 0-65535.\n- Contains data from all detector logics. Each detector logic is separated with a comma.\n- The value is set to \"-1\" if no data could be measured (e.g. detector fault)",
                   "type" : "string"
                 }
               }

data/schemas/tlc/1.0.15/sxl.yaml

@@ -475,7 +475,7 @@ objects:
               Function legend:
               0=no plan is selected by time table
               1=set plan 1
-              …
+              ...
               16= set plan 16
               
               hour and minute is using local time (not UTC)
@@ -686,7 +686,7 @@ objects:
               Number of vehicles.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
       S0206:
         description: |-
@@ -705,7 +705,7 @@ objects:
               Average speed in km/h (integer).
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
       S0207:
         description: |-
@@ -724,7 +724,7 @@ objects:
               Occupancy in percent (%) (0-100)
               - Value expressed as an integer with a range of 0-100.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-100,...]"
       S0208:
         description: |-
@@ -743,7 +743,7 @@ objects:
               Number of cars.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           PS:
             type: string
@@ -751,7 +751,7 @@ objects:
               Number of cars with trailers.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           L:
             type: string
@@ -759,7 +759,7 @@ objects:
               Number of trucks.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           LS:
             type: string
@@ -767,7 +767,7 @@ objects:
               Number of trucks with trailers.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           B:
             type: string
@@ -775,7 +775,7 @@ objects:
               Number of busses.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           SP:
             type: string
@@ -783,7 +783,7 @@ objects:
               Number of trams.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           MC:
             type: string
@@ -791,7 +791,7 @@ objects:
               Number of motor cycles.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           C:
             type: string
@@ -799,7 +799,7 @@ objects:
               Number of bicycles.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
           F:
             type: string
@@ -807,7 +807,7 @@ objects:
               Number of pedestrians.
               - Value expressed as an integer with a range of 0-65535.
               - Contains data from all detector logics. Each detector logic is separated with a comma.
-              - The value is set to “-1” if no data could be measured (e.g. detector fault)
+              - The value is set to "-1" if no data could be measured (e.g. detector fault)
             range: "[0-65535,...]"
     commands:
       M0001:
@@ -970,7 +970,7 @@ objects:
               1=Order signal group to green
               0=Order signal group to red
               
-              Format: [Offset],[Bits to set],[Bits to unset]:…
+              Format: [Offset],[Bits to set],[Bits to unset]:...
               
               Offset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.
               
@@ -1003,7 +1003,7 @@ objects:
             description: |-
               Sets/Unsets a block of 16 inputs at a time. Can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon, ":" is used in example below.
               
-              Format: [Offset],[Bits to set],[Bits to unset]:…
+              Format: [Offset],[Bits to set],[Bits to unset]:...
               
               Offset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.
               
@@ -1121,7 +1121,7 @@ objects:
               Function legend:
               0=no plan is selected by time table
               1=set plan 1
-              …
+              ...
               16= set plan 16
               
               hour and minute is using local time (not UTC)

data/schemas/tlc/1.0.8/commands/M0012.json

@@ -46,7 +46,7 @@
             "then" : {
               "properties" : {
                 "v" : {
-                  "description" : "Orders signal groups to green or red. Sets a block of 16 signal groups at a time. Can be repeated to set several blocks of 16 signal groups. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon is used in example below.\n\n1=Order signal group to green\n0=Order signal group to red\n\nFormat: [Offset],[Bits to set],[Bits to unset]:…\n\nOffset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.\n\nExample 1:\n\"5, 4134, 65\" sets input 6,7,10,17 = on and 5,11 = off\n(Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)\n\nExample 2:\n\"22, 1, 4\" sets input 22 = on and 24 = off\n(Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)\n\nAnd both these examples could be sent in the same message as:\n\"5,4143,65:22,1,4\"\n\nSuch a message would order signal group 6,7,10,17,22 to green and signal group 5,11,24 to red",
+                  "description" : "Orders signal groups to green or red. Sets a block of 16 signal groups at a time. Can be repeated to set several blocks of 16 signal groups. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon is used in example below.\n\n1=Order signal group to green\n0=Order signal group to red\n\nFormat: [Offset],[Bits to set],[Bits to unset]:...\n\nOffset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.\n\nExample 1:\n\"5, 4134, 65\" sets input 6,7,10,17 = on and 5,11 = off\n(Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)\n\nExample 2:\n\"22, 1, 4\" sets input 22 = on and 24 = off\n(Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)\n\nAnd both these examples could be sent in the same message as:\n\"5,4143,65:22,1,4\"\n\nSuch a message would order signal group 6,7,10,17,22 to green and signal group 5,11,24 to red",
                   "type" : "string"
                 }
               }

data/schemas/tlc/1.0.8/commands/M0013.json

@@ -46,7 +46,7 @@
             "then" : {
               "properties" : {
                 "v" : {
-                  "description" : "Sets/Unsets a block of 16 inputs at a time. Can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon, \":\" is used in example below.\n\nFormat: [Offset],[Bits to set],[Bits to unset]:…\n\nOffset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.\n\nExample 1:\n\"5, 4134, 65\" sets input 6,7,10,17 = on and 5,11 = off\n(Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)\n\nExample 2:\n\"22, 1, 4\" sets input 22 = on and 24 = off\n(Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)\n\nAnd both thease examples could be sent in the same message as:\n\"5,4143:65:22,1,4\"\n\nSuch a message would activate input 6,7,10,17,22 and deactivate input 5,11,24",
+                  "description" : "Sets/Unsets a block of 16 inputs at a time. Can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon, \":\" is used in example below.\n\nFormat: [Offset],[Bits to set],[Bits to unset]:...\n\nOffset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.\n\nExample 1:\n\"5, 4134, 65\" sets input 6,7,10,17 = on and 5,11 = off\n(Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)\n\nExample 2:\n\"22, 1, 4\" sets input 22 = on and 24 = off\n(Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)\n\nAnd both thease examples could be sent in the same message as:\n\"5,4143:65:22,1,4\"\n\nSuch a message would activate input 6,7,10,17,22 and deactivate input 5,11,24",
                   "type" : "string"
                 }
               }

data/schemas/tlc/1.0.8/sxl.yaml

@@ -606,7 +606,7 @@ objects:
               1=Order signal group to green
               0=Order signal group to red
               
-              Format: [Offset],[Bits to set],[Bits to unset]:…
+              Format: [Offset],[Bits to set],[Bits to unset]:...
               
               Offset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.
               
@@ -639,7 +639,7 @@ objects:
             description: |-
               Sets/Unsets a block of 16 inputs at a time. Can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon, ":" is used in example below.
               
-              Format: [Offset],[Bits to set],[Bits to unset]:…
+              Format: [Offset],[Bits to set],[Bits to unset]:...
               
               Offset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.
               

data/schemas/tlc/1.0.9/commands/M0012.json

@@ -46,7 +46,7 @@
             "then" : {
               "properties" : {
                 "v" : {
-                  "description" : "Orders signal groups to green or red. Sets a block of 16 signal groups at a time. Can be repeated to set several blocks of 16 signal groups. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon is used in example below.\n\n1=Order signal group to green\n0=Order signal group to red\n\nFormat: [Offset],[Bits to set],[Bits to unset]:…\n\nOffset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.\n\nExample 1:\n\"5, 4134, 65\" sets input 6,7,10,17 = on and 5,11 = off\n(Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)\n\nExample 2:\n\"22, 1, 4\" sets input 22 = on and 24 = off\n(Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)\n\nAnd both these examples could be sent in the same message as:\n\"5,4143,65:22,1,4\"\n\nSuch a message would order signal group 6,7,10,17,22 to green and signal group 5,11,24 to red",
+                  "description" : "Orders signal groups to green or red. Sets a block of 16 signal groups at a time. Can be repeated to set several blocks of 16 signal groups. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon is used in example below.\n\n1=Order signal group to green\n0=Order signal group to red\n\nFormat: [Offset],[Bits to set],[Bits to unset]:...\n\nOffset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.\n\nExample 1:\n\"5, 4134, 65\" sets input 6,7,10,17 = on and 5,11 = off\n(Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)\n\nExample 2:\n\"22, 1, 4\" sets input 22 = on and 24 = off\n(Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)\n\nAnd both these examples could be sent in the same message as:\n\"5,4143,65:22,1,4\"\n\nSuch a message would order signal group 6,7,10,17,22 to green and signal group 5,11,24 to red",
                   "type" : "string"
                 }
               }

data/schemas/tlc/1.0.9/commands/M0013.json

@@ -46,7 +46,7 @@
             "then" : {
               "properties" : {
                 "v" : {
-                  "description" : "Sets/Unsets a block of 16 inputs at a time. Can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon, \":\" is used in example below.\n\nFormat: [Offset],[Bits to set],[Bits to unset]:…\n\nOffset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.\n\nExample 1:\n\"5, 4134, 65\" sets input 6,7,10,17 = on and 5,11 = off\n(Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)\n\nExample 2:\n\"22, 1, 4\" sets input 22 = on and 24 = off\n(Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)\n\nAnd both thease examples could be sent in the same message as:\n\"5,4143:65:22,1,4\"\n\nSuch a message would activate input 6,7,10,17,22 and deactivate input 5,11,24",
+                  "description" : "Sets/Unsets a block of 16 inputs at a time. Can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon, \":\" is used in example below.\n\nFormat: [Offset],[Bits to set],[Bits to unset]:...\n\nOffset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.\n\nExample 1:\n\"5, 4134, 65\" sets input 6,7,10,17 = on and 5,11 = off\n(Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)\n\nExample 2:\n\"22, 1, 4\" sets input 22 = on and 24 = off\n(Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)\n\nAnd both thease examples could be sent in the same message as:\n\"5,4143:65:22,1,4\"\n\nSuch a message would activate input 6,7,10,17,22 and deactivate input 5,11,24",
                   "type" : "string"
                 }
               }

data/schemas/tlc/1.0.9/sxl.yaml

@@ -606,7 +606,7 @@ objects:
               1=Order signal group to green
               0=Order signal group to red
               
-              Format: [Offset],[Bits to set],[Bits to unset]:…
+              Format: [Offset],[Bits to set],[Bits to unset]:...
               
               Offset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.
               
@@ -639,7 +639,7 @@ objects:
             description: |-
               Sets/Unsets a block of 16 inputs at a time. Can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon, ":" is used in example below.
               
-              Format: [Offset],[Bits to set],[Bits to unset]:…
+              Format: [Offset],[Bits to set],[Bits to unset]:...
               
               Offset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.
               

data/schemas/tlc/1.1.0/alarms/A0303.json

@@ -1,5 +1,5 @@
 {
-  "description" : "Serious detector error (hardware).\nIs a “major fault” defined according to 3.8 i EN12675 which causes the controller to switch to a “failure mode” according to 3.6 in EN12675.",
+  "description" : "Serious detector error (hardware).\nIs a \"major fault\" defined according to 3.8 i EN12675 which causes the controller to switch to a \"failure mode\" according to 3.6 in EN12675.",
   "allOf" : [
     {
       "properties" : {

data/schemas/tlc/1.1.0/alarms/A0304.json

@@ -1,5 +1,5 @@
 {
-  "description" : "Serious detector error (logic error).\nFor instance; detector continuously on or off during an extended time.\nIs a “major fault” defined according to 3.8 i EN12675 which causes the controller to switch to a “failure mode” according to 3.6 in EN12675",
+  "description" : "Serious detector error (logic error).\nFor instance; detector continuously on or off during an extended time.\nIs a \"major fault\" defined according to 3.8 i EN12675 which causes the controller to switch to a \"failure mode\" according to 3.6 in EN12675",
   "allOf" : [
     {
       "properties" : {

data/schemas/tlc/1.1.0/commands/M0012.json

@@ -46,7 +46,7 @@
             "then" : {
               "properties" : {
                 "v" : {
-                  "description" : "Orders signal groups to green or red. Sets a block of 16 signal groups at a time. Can be repeated to set several blocks of 16 signal groups. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon is used in example below.\n\n1=Order signal group to green\n0=Order signal group to red\n\nFormat: [Offset],[Bits to set],[Bits to unset]:…\n\nOffset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.\n\nExample 1:\n\"5, 4134, 65\" sets input 6,7,10,17 = on and 5,11 = off\n(Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)\n\nExample 2:\n\"22, 1, 4\" sets input 22 = on and 24 = off\n(Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)\n\nAnd both these examples could be sent in the same message as:\n\"5,4143,65:22,1,4\"\n\nSuch a message would order signal group 6,7,10,17,22 to green and signal group 5,11,24 to red",
+                  "description" : "Orders signal groups to green or red. Sets a block of 16 signal groups at a time. Can be repeated to set several blocks of 16 signal groups. Values are separated with comma. Blocks are separated with semicolon. Since semicolon breaks the SXL csv-format, colon is used in example below.\n\n1=Order signal group to green\n0=Order signal group to red\n\nFormat: [Offset],[Bits to set],[Bits to unset]:...\n\nOffset sets where the 16 inputs starts from followed by two 16 bit values telling which bit to set and unset in binary format, i.e. first bit have value 1 and last bit have value 32768.\n\nExample 1:\n\"5, 4134, 65\" sets input 6,7,10,17 = on and 5,11 = off\n(Input starts from no. 5 and bit 1,2,5,12 = 1 and bit 0,6 = 0)\n\nExample 2:\n\"22, 1, 4\" sets input 22 = on and 24 = off\n(Input starts from no. 22 and bit 0 = 1 and bit 2 = 0)\n\nAnd both these examples could be sent in the same message as:\n\"5,4143,65:22,1,4\"\n\nSuch a message would order signal group 6,7,10,17,22 to green and signal group 5,11,24 to red",
                   "type" : "string"
                 }
               }

data/schemas/tlc/1.1.0/commands/M0013.json

@@ -1,5 +1,5 @@
 {
-  "description" : "Activate a series of inputs\n\nSet given inputs (1-255) of the controllers general purpose I/O to either true or false. This command was introduced due to coordination requirements needing to set many inputs to true/false at the same time and M0006 being to slow to send a message for each input individually. With this command many inputs can be set to true/false at the same time using a single command message. It can be used for all types of input where the traffic light controller must react to external control. Typical usages are bus priority, coordination between traffic controllers, external control systems, and much more.\n\nRequires security code 2.\n\nThe parameter ‘status’ sets/unsets a block of 16 inputs at a time. It can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon. Format: [Offset];[Bits to set];[Bits to unset];…\n\n- ‘Offset’ defines where the 16 inputs starts from\n- ‘Bits to set’ defines which bit(s) to set. ‘0’ if unused\n- ‘Bits to unset’ defines which bit(s) to unset. ‘0’ if unused\n\nExample 1:\n“3,4134,65” sets input 4,5,8,15 and unsets 3,9\n- Input starts from no. 5\n- “4134” is 1 0000 0010 0110 in binary, but since input starts from 3, it is shifted 3 bits, e.g. 1000 0001 0011 0000 which are bits 4,5,8,15\n- “65” is 100 0001 in binary, but since input starts from 3, it is shifted 3 bits, e.g. 10 0000 1000 which are bits 3,9\n\nExample 2:\n“12,1,4” sets input 12 and unsets 14\n- Input starts from no. 12\n- “1” is 1 in binary, but since input starts at 12 it is shifted 12 bits, e.g. 1 0000 0000 0000, which is bit 12\n- “4” is 100 in binary, but since input starts at 12 it is shifted 12 bits, e.g. 100 0000 0000 0000, which is bit 14\n\nAnd both these examples could be sent in the same message as: “3,4143,65;12,1,4”\n\nSuch a message would set input 4,5,8,12,15 and unset input 3,9,14\n\nExample 3:\n“0,1,2” sets input 0 and unsets 1\n- Input starts from 0\n- “1” is 1 in binary, which is bit 0\n- “2” is 10 in binary, which is bit 1",
+  "description" : "Activate a series of inputs\n\nSet given inputs (1-255) of the controllers general purpose I/O to either true or false. This command was introduced due to coordination requirements needing to set many inputs to true/false at the same time and M0006 being to slow to send a message for each input individually. With this command many inputs can be set to true/false at the same time using a single command message. It can be used for all types of input where the traffic light controller must react to external control. Typical usages are bus priority, coordination between traffic controllers, external control systems, and much more.\n\nRequires security code 2.\n\nThe parameter 'status' sets/unsets a block of 16 inputs at a time. It can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon. Format: [Offset];[Bits to set];[Bits to unset];...\n\n- 'Offset' defines where the 16 inputs starts from\n- 'Bits to set' defines which bit(s) to set. '0' if unused\n- 'Bits to unset' defines which bit(s) to unset. '0' if unused\n\nExample 1:\n\"3,4134,65\" sets input 4,5,8,15 and unsets 3,9\n- Input starts from no. 5\n- \"4134\" is 1 0000 0010 0110 in binary, but since input starts from 3, it is shifted 3 bits, e.g. 1000 0001 0011 0000 which are bits 4,5,8,15\n- \"65\" is 100 0001 in binary, but since input starts from 3, it is shifted 3 bits, e.g. 10 0000 1000 which are bits 3,9\n\nExample 2:\n\"12,1,4\" sets input 12 and unsets 14\n- Input starts from no. 12\n- \"1\" is 1 in binary, but since input starts at 12 it is shifted 12 bits, e.g. 1 0000 0000 0000, which is bit 12\n- \"4\" is 100 in binary, but since input starts at 12 it is shifted 12 bits, e.g. 100 0000 0000 0000, which is bit 14\n\nAnd both these examples could be sent in the same message as: \"3,4143,65;12,1,4\"\n\nSuch a message would set input 4,5,8,12,15 and unset input 3,9,14\n\nExample 3:\n\"0,1,2\" sets input 0 and unsets 1\n- Input starts from 0\n- \"1\" is 1 in binary, which is bit 0\n- \"2\" is 10 in binary, which is bit 1",
   "allOf" : [
     {
       "properties" : {
@@ -46,7 +46,7 @@
             "then" : {
               "properties" : {
                 "v" : {
-                  "description" : "Sets/Unsets a block of 16 inputs at a time. Can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon.\nFormat: [Offset];[Bits to set];[Bits to unset];…",
+                  "description" : "Sets/Unsets a block of 16 inputs at a time. Can be repeated to set several blocks of 16 inputs. Values are separated with comma. Blocks are separated with semicolon.\nFormat: [Offset];[Bits to set];[Bits to unset];...",
                   "type" : "string"
                 }
               }

data/schemas/tlc/1.1.0/commands/M0017.json

@@ -46,7 +46,7 @@
             "then" : {
               "properties" : {
                 "v" : {
-                  "description" : "Time Table. Defines time tables.\nEach time definition is written as t-o-h-m where:\nt=time table nr (1-12)\no=function\nh=hour - switching time\nm=minute - switching minute\n\nFunction legend:\n0=no plan is selected by time table\n1=set plan 1\n…\n16= set plan 16\n\nhour and minute is using local time (not UTC)\n\nEach time definition is separated with a comma.\n\nE.g.\nt-o-h-m,t-o-h-m",
+                  "description" : "Time Table. Defines time tables.\nEach time definition is written as t-o-h-m where:\nt=time table nr (1-12)\no=function\nh=hour - switching time\nm=minute - switching minute\n\nFunction legend:\n0=no plan is selected by time table\n1=set plan 1\n...\n16= set plan 16\n\nhour and minute is using local time (not UTC)\n\nEach time definition is separated with a comma.\n\nE.g.\nt-o-h-m,t-o-h-m",
                   "type" : "string"
                 }
               }