rsmp_schema 0.8.3 → 0.8.5

data/schemas/tlc/1.2.1/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.2.1/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.2.1/commands/M0022.json

@@ -1,5 +1,5 @@
 {
-  "description" : "Request Signal Priority\n\nUseful for bus priority or other type of priorities like emergency vehicles or groups of cyclists.\n\nThe benefit of using this message over activating inputs or detector logics is that you can specify a priority level, vehicle type and estimated time of arrival. You can also update or cancel the request, and use the corresponding status message to track the status of the request, including how much priority was actually given.\n\nTo understand how this command relates to ETSI/J2735, please see the [wiki](https://github.com/rsmp-nordic/rsmp_sxl_traffic_lights/wiki/Signal-priority-and-ETSI-J2735).\n\nActivating signal priority is expected to provide more green time for a particular movement through the intersection, but the exact mechanism must typically be configured in the controller.\n\nThe movement to prioritize can be referenced in a number of ways, depending on what is configured in the controller, and in the system that sends priority requests. Either:\n\n- Reference a signal group by setting ‘signalGroupId’. This method is simple, but will not allow you to have different priority mechanism for the same signal group, unless they can be distinguished by the vehicle type. For example, if you need to trigger different priorities depending on whether a bus goes straight or makes a turn for the same signal group, you need to use of the other referencing methods.\n- Reference an input by setting ‘inputId’. This can be useful if you previously used inputs to activate priority. The input will not be activated, only the priority.\n- Reference a connection by setting ‘connectionId’. A connection is a movement from a specific ingoing lane to a specific outgoing lane.\n- Reference an intersection approach by setting ‘approachId’.\n- Reference an ingoing lane by setting ‘laneInId’, and optionally also reference an outgoing lane by setting ‘laneOutId’.\n\nReferencing attributes that are not used must be left out, rather than set to null or empty strings. This includes:\n\n- signalGroupId\n- inputId\n- connectionId\n- approachId\n- laneInId\n- laneOutId\n\nReferencing attributes are only used when initiating a request. When updating or cancelling the request, the request is identified by its requestId, and no referencing attributes are allowed.\n\nYou initiate a priority request with type set to ‘new’. You must provide a request id that uniquely identifies the request on the controller. It can be a randomly generated UUID (universally unique identifier), or it can be constructed by combining e.g. a vehicle id and some other identifier. When updating or cancelling a request, you must pass the same request id again.\n\nProviding ETA (estimated time of arrival) when initiating a request is optional, but can help the controller plan ahead in cases where you’re able to send the request before the vehicle arrives at the intersection. You’re allowed to initiate the request without an ETA and provide it in a later request update. But providing the ETA when initiating the request is recommended, since it will give the controller more time to plan ahead.\n\nLike ETA, providing a vehicle type is optional, but can help the controller decide how to best handle the request.\n\nThe priority level provides a way to indicate the relative importance of the request compared to other requests. For example, emergency vehicles or delayed buses could be given a higher priority level.\n\nIf the ETA changes before the priority is cancelled, or you want to change the priority level, you can send another request message with type set to ‘update’. The vehicle type cannot be changed.\n\nWhen you send a priority request, it will be processed to decide if it’s possible to activate the requested priority.\n\nIf the request is accepted, the priority can either be activated immediately, or if another priority is currently active, it can be queued for later activation.\n\nIf the priority cannot be accepted the request is rejected. Cooldown is a specific type of rejection, which means that s similar request has just completed, and some time needs to pass before a similar request can be activated.\n\nWhen a request is queued, it is expected to become activated later, but in case too long passes without activation, the controller is expected to time out the request.\n\nOnce a priority is activated, you’re excepted to cancel it as soon as there’s no need for it anymore, typically when the vehicle has passed the intersection. You cancel a request by sending a request passing the existing request id setting the type to ‘cancel’.\n\nIf a request is never cancelled, the controller is expected to remove the priority at some point, but until then the priority might block requests in other direction which is why you should always cancel a priority when it’s not needed anymore.",
+  "description" : "Request Signal Priority\n\nUseful for bus priority or other type of priorities like emergency vehicles or groups of cyclists.\n\nThe benefit of using this message over activating inputs or detector logics is that you can specify a priority level, vehicle type and estimated time of arrival. You can also update or cancel the request, and use the corresponding status message to track the status of the request, including how much priority was actually given.\n\nTo understand how this command relates to ETSI/J2735, please see the [wiki](https://github.com/rsmp-nordic/rsmp_sxl_traffic_lights/wiki/Signal-priority-and-ETSI-J2735).\n\nActivating signal priority is expected to provide more green time for a particular movement through the intersection, but the exact mechanism must typically be configured in the controller.\n\nThe movement to prioritize can be referenced in a number of ways, depending on what is configured in the controller, and in the system that sends priority requests. Either:\n\n- Reference a signal group by setting 'signalGroupId'. This method is simple, but will not allow you to have different priority mechanism for the same signal group, unless they can be distinguished by the vehicle type. For example, if you need to trigger different priorities depending on whether a bus goes straight or makes a turn for the same signal group, you need to use of the other referencing methods.\n- Reference an input by setting 'inputId'. This can be useful if you previously used inputs to activate priority. The input will not be activated, only the priority.\n- Reference a connection by setting 'connectionId'. A connection is a movement from a specific ingoing lane to a specific outgoing lane.\n- Reference an intersection approach by setting 'approachId'.\n- Reference an ingoing lane by setting 'laneInId', and optionally also reference an outgoing lane by setting 'laneOutId'.\n\nReferencing attributes that are not used must be left out, rather than set to null or empty strings. This includes:\n\n- signalGroupId\n- inputId\n- connectionId\n- approachId\n- laneInId\n- laneOutId\n\nReferencing attributes are only used when initiating a request. When updating or cancelling the request, the request is identified by its requestId, and no referencing attributes are allowed.\n\nYou initiate a priority request with type set to 'new'. You must provide a request id that uniquely identifies the request on the controller. It can be a randomly generated UUID (universally unique identifier), or it can be constructed by combining e.g. a vehicle id and some other identifier. When updating or cancelling a request, you must pass the same request id again.\n\nProviding ETA (estimated time of arrival) when initiating a request is optional, but can help the controller plan ahead in cases where you're able to send the request before the vehicle arrives at the intersection. You're allowed to initiate the request without an ETA and provide it in a later request update. But providing the ETA when initiating the request is recommended, since it will give the controller more time to plan ahead.\n\nLike ETA, providing a vehicle type is optional, but can help the controller decide how to best handle the request.\n\nThe priority level provides a way to indicate the relative importance of the request compared to other requests. For example, emergency vehicles or delayed buses could be given a higher priority level.\n\nIf the ETA changes before the priority is cancelled, or you want to change the priority level, you can send another request message with type set to 'update'. The vehicle type cannot be changed.\n\nWhen you send a priority request, it will be processed to decide if it's possible to activate the requested priority.\n\nIf the request is accepted, the priority can either be activated immediately, or if another priority is currently active, it can be queued for later activation.\n\nIf the priority cannot be accepted the request is rejected. Cooldown is a specific type of rejection, which means that s similar request has just completed, and some time needs to pass before a similar request can be activated.\n\nWhen a request is queued, it is expected to become activated later, but in case too long passes without activation, the controller is expected to time out the request.\n\nOnce a priority is activated, you're excepted to cancel it as soon as there's no need for it anymore, typically when the vehicle has passed the intersection. You cancel a request by sending a request passing the existing request id setting the type to 'cancel'.\n\nIf a request is never cancelled, the controller is expected to remove the priority at some point, but until then the priority might block requests in other direction which is why you should always cancel a priority when it's not needed anymore.",
   "allOf" : [
     {
       "properties" : {

data/schemas/tlc/1.2.1/statuses/S0001.json

@@ -68,7 +68,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "description" : "Cycle counter.\nUsed for handling of coordination between TLC’s.\nIs counted from 0 until it reaches the cycle time (See S0028).\n\nc = (b + o) mod t\n\nwhere c = cycle counter,\nb = base cycle counter,\no = offset,\nt = cycle time,\nmod = modulo\n\nSee the coordination section for more information."
+                      "description" : "Cycle counter.\nUsed for handling of coordination between TLC's.\nIs counted from 0 until it reaches the cycle time (See S0028).\n\nc = (b + o) mod t\n\nwhere c = cycle counter,\nb = base cycle counter,\no = offset,\nt = cycle time,\nmod = modulo\n\nSee the coordination section for more information."
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer"
@@ -94,7 +94,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "description" : "Base cycle counter.\nUsed for handling of coordination between TLC’s.\nSynchronized between all TLC’s in an active coordination.\nSee the coordination section for more information."
+                      "description" : "Base cycle counter.\nUsed for handling of coordination between TLC's.\nSynchronized between all TLC's in an active coordination.\nSee the coordination section for more information."
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer"

data/schemas/tlc/1.2.1/statuses/S0007.json

@@ -46,7 +46,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "description" : "Comma separated list of intersections which the status relates to, e.g. “1,2”.\nUse “0” for all intersections of the TLC."
+                      "description" : "Comma separated list of intersections which the status relates to, e.g. \"1,2\".\nUse \"0\" for all intersections of the TLC."
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"

data/schemas/tlc/1.2.1/statuses/S0008.json

@@ -46,7 +46,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "description" : "Comma separated list of intersections which the status relates to, e.g. “1,2”.\nUse “0” for all intersections of the TLC."
+                      "description" : "Comma separated list of intersections which the status relates to, e.g. \"1,2\".\nUse \"0\" for all intersections of the TLC."
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"

data/schemas/tlc/1.2.1/statuses/S0009.json

@@ -46,7 +46,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "description" : "Comma separated list of intersections which the status relates to, e.g. “1,2”.\nUse “0” for all intersections of the TLC."
+                      "description" : "Comma separated list of intersections which the status relates to, e.g. \"1,2\".\nUse \"0\" for all intersections of the TLC."
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"

data/schemas/tlc/1.2.1/statuses/S0010.json

@@ -46,7 +46,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "description" : "Comma separated list of intersections which the status relates to, e.g. “1,2”.\nUse “0” for all intersections of the TLC."
+                      "description" : "Comma separated list of intersections which the status relates to, e.g. \"1,2\".\nUse \"0\" for all intersections of the TLC."
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"

data/schemas/tlc/1.2.1/statuses/S0011.json

@@ -46,7 +46,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "description" : "Comma separated list of intersections which the status relates to, e.g. “1,2”.\nUse “0” for all intersections of the TLC."
+                      "description" : "Comma separated list of intersections which the status relates to, e.g. \"1,2\".\nUse \"0\" for all intersections of the TLC."
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"

data/schemas/tlc/1.2.1/statuses/S0012.json

@@ -46,7 +46,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "description" : "Comma separated list of intersections which the status relates to, e.g. “1,2”.\nUse “0” for all intersections of the TLC."
+                      "description" : "Comma separated list of intersections which the status relates to, e.g. \"1,2\".\nUse \"0\" for all intersections of the TLC."
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"

data/schemas/tlc/1.2.1/statuses/S0013.json

@@ -45,7 +45,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "description" : "Comma separated list of intersections which the status relates to, e.g. “1,2”.\nUse “0” for all intersections of the TLC."
+                      "description" : "Comma separated list of intersections which the status relates to, e.g. \"1,2\".\nUse \"0\" for all intersections of the TLC."
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"

data/schemas/tlc/1.2.1/statuses/S0020.json

@@ -45,7 +45,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "description" : "Comma separated list of intersections which the status relates to, e.g. “1,2”.\nUse “0” for all intersections of the TLC."
+                      "description" : "Comma separated list of intersections which the status relates to, e.g. \"1,2\".\nUse \"0\" for all intersections of the TLC."
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"

data/schemas/tlc/1.2.1/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.2.1/statuses/S0032.json

@@ -1,5 +1,5 @@
 {
-  "description" : "Coordinated control\nThis status is used when coordination between traffic light controllers is active. Coordination is described in detail in the corresponding section\nPlease note that all values in this status uses comma-separated lists - one value for each intersection, e.g. “1,2” and “centralized,off”",
+  "description" : "Coordinated control\nThis status is used when coordination between traffic light controllers is active. Coordination is described in detail in the corresponding section\nPlease note that all values in this status uses comma-separated lists - one value for each intersection, e.g. \"1,2\" and \"centralized,off\"",
   "allOf" : [
     {
       "properties" : {
@@ -46,7 +46,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "description" : "Comma separated list of intersections which the status relates to, e.g. “1,2”.\nUse “0” for all intersections of the TLC."
+                      "description" : "Comma separated list of intersections which the status relates to, e.g. \"1,2\".\nUse \"0\" for all intersections of the TLC."
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"

data/schemas/tlc/1.2.1/statuses/S0033.json

@@ -1,5 +1,5 @@
 {
-  "description" : "Signal Priority Status\nThis status can be used to get updates about priority requests. For example, you can use it to know when priority requests are activated or cancelled.\nA list of priorities is returned, referred to by their request ids. The same request id can appear only once.\nAll priorities are included in the list (not only the ones that have changed state since the last update). This is done regardless of whether the status is send in respond to a status request, or due to a status subscription, and also regardless of whether a status subscription uses an update interval, or send-on-change, or both.\nIf you subscribe using an update interval, you’re not guaranteed to get all intermediate states. To guarantee that, send-on-change must be used when subscribing.\nTo understand how this status relates to ETSI/J2735, please see the [wiki](https://github.com/rsmp-nordic/rsmp_sxl_traffic_lights/wiki/Signal-priority-and-ETSI-J2735).\nAll priorities are send on every status update, regardless of whether an interval, or sendOnChange (or both) is used.\nWhen a priority reaches an end states (completed, timeout, rejected, cooldown or stale), it must be sent once on the next status update, then removed from the list.\nA request always starts in the ‘received’ state. The following table shows the possible state transitions:\n\nState      | Possible next states\n---------- | -------------------------------------\nreceived   | queued, activated, rejected, cooldown\nqueued     | activated, timeout\nactivated  | completed, stale\ncompleted  |\ntimeout    |\nrejected   |\ncooldown   |\nstale      |",
+  "description" : "Signal Priority Status\nThis status can be used to get updates about priority requests. For example, you can use it to know when priority requests are activated or cancelled.\nA list of priorities is returned, referred to by their request ids. The same request id can appear only once.\nAll priorities are included in the list (not only the ones that have changed state since the last update). This is done regardless of whether the status is send in respond to a status request, or due to a status subscription, and also regardless of whether a status subscription uses an update interval, or send-on-change, or both.\nIf you subscribe using an update interval, you're not guaranteed to get all intermediate states. To guarantee that, send-on-change must be used when subscribing.\nTo understand how this status relates to ETSI/J2735, please see the [wiki](https://github.com/rsmp-nordic/rsmp_sxl_traffic_lights/wiki/Signal-priority-and-ETSI-J2735).\nAll priorities are send on every status update, regardless of whether an interval, or sendOnChange (or both) is used.\nWhen a priority reaches an end states (completed, timeout, rejected, cooldown or stale), it must be sent once on the next status update, then removed from the list.\nA request always starts in the 'received' state. The following table shows the possible state transitions:\n\nState      | Possible next states\n---------- | -------------------------------------\nreceived   | queued, activated, rejected, cooldown\nqueued     | activated, timeout\nactivated  | completed, stale\ncompleted  |\ntimeout    |\nrejected   |\ncooldown   |\nstale      |",
   "allOf" : [
     {
       "properties" : {
@@ -84,7 +84,7 @@
                       "e" : {
                         "allOf" : [
                           {
-                            "description" : "Estimated green extension provided by the priority, in seconds\nOnly used when state is ‘completed’."
+                            "description" : "Estimated green extension provided by the priority, in seconds\nOnly used when state is 'completed'."
                           },
                           {
                             "$ref" : "../../../core/3.1.2/definitions.json#/integer"
@@ -94,7 +94,7 @@
                       "d" : {
                         "allOf" : [
                           {
-                            "description" : "Estimated red reduction provided by the priority, in seconds\nOnly used when state is ‘completed’."
+                            "description" : "Estimated red reduction provided by the priority, in seconds\nOnly used when state is 'completed'."
                           },
                           {
                             "$ref" : "../../../core/3.1.2/definitions.json#/integer"

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

@@ -71,7 +71,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "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)"
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"

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

@@ -71,7 +71,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "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)"
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"

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

@@ -71,7 +71,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "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)"
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"

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

@@ -79,7 +79,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "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)"
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"
@@ -105,7 +105,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "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)"
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"
@@ -131,7 +131,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "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)"
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"
@@ -157,7 +157,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "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)"
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"
@@ -183,7 +183,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "description" : "Number of buses.\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 buses.\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)"
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"
@@ -209,7 +209,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "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)"
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"
@@ -235,7 +235,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "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)"
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"
@@ -261,7 +261,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "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)"
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"
@@ -287,7 +287,7 @@
                 "s" : {
                   "allOf" : [
                     {
-                      "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)"
                     },
                     {
                       "$ref" : "../../../core/3.1.2/definitions.json#/integer_list"