time-range

asternos yang model for aster nos time range define a period of time, which is in absolute or cyclic type yang tree diagram yang tree diagram module asternos time range + rw time ranges + rw time range \[name] + rw name string + rw (absolute cyclic)? + (absolute range) \| + rw start date time? yang\ date and time \| + rw end date time? yang\ date and time + (cyclic range) + rw days in week? bits + rw start? time hhmm + rw end? time hhmm resources resources resource list resource list path access /time ranges read write /time ranges/time range read write /time ranges/time range/name read write /time ranges/time range/absolute cyclic read write /time ranges/time range/absolute cyclic/absolute range read write /time ranges/time range/absolute cyclic/absolute range/start date time read write /time ranges/time range/absolute cyclic/absolute range/end date time read write /time ranges/time range/absolute cyclic/cyclic range read write /time ranges/time range/absolute cyclic/cyclic range/days in week read write /time ranges/time range/absolute cyclic/cyclic range/start read write /time ranges/time range/absolute cyclic/cyclic range/end read write detailed nodes detailed nodes /time ranges /time ranges path /time ranges node type container access read write /time ranges/time range /time ranges/time range path /time ranges/time range node type list description the time range instances access read write /time ranges/time range/name /time ranges/time range/name path /time ranges/time range/name node type leaf description the name of time range instance access read write data type \<yang type string> /time ranges/time range/absolute cyclic /time ranges/time range/absolute cyclic path /time ranges/time range/absolute cyclic node type choice description there are two kinds of tima range the absolute time range and cyclic time range once days in week is used, it treated as the cyclic range access read write /time ranges/time range/absolute cyclic/absolute range /time ranges/time range/absolute cyclic/absolute range path /time ranges/time range/absolute cyclic/absolute range node type choice case description the absolute time the end time must be later than the start time access read write /time ranges/time range/absolute cyclic/absolute range/start date time /time ranges/time range/absolute cyclic/absolute range/start date time path /time ranges/time range/absolute cyclic/absolute range/start date time node type leaf description the start date and time the format can be two types 1 2023 10 05t14 48 30 123+08 00, it means 14 48 30 123 on october 5, 2023, east 8th district time 2 2023 10 05t14 48 00z, it means 14 48 00 on october 5, 2023, utc time limitation second, microsecond and timezone is not supported access read write data type \<yang type date and time> constraints the date and time type is a profile of the iso 8601 standard for representation of dates and times using the gregorian calendar the profile is defined by the date time production in section 5 6 of rfc 3339 the date and time type is compatible with the datetime xml schema type with the following notable exceptions (a) the date and time type does not allow negative years (b) the date and time time offset 00 00 indicates an unknown time zone (see rfc 3339) while 00 00 and +00 00 and z all represent the same time zone in datetime (c) the canonical format (see below) of data and time values differs from the canonical format used by the datetime xml schema type, which requires all times to be in utc using the time offset 'z' this type is not equivalent to the dateandtime textual convention of the smiv2 since rfc 3339 uses a different separator between full date and full time and provides higher resolution of time secfrac the canonical format for date and time values with a known time zone uses a numeric time zone offset that is calculated using the device's configured known offset to utc time a change of the device's offset to utc time will cause date and time values to change accordingly such changes might happen periodically in case a server follows automatically daylight saving time (dst) time zone offset changes the canonical format for date and time values with an unknown time zone (usually referring to the notion of local time) uses the time offset 00 00 /time ranges/time range/absolute cyclic/absolute range/end date time /time ranges/time range/absolute cyclic/absolute range/end date time path /time ranges/time range/absolute cyclic/absolute range/end date time node type leaf description the end date and time, same as the description in start date time access read write data type \<yang type date and time> constraints the date and time type is a profile of the iso 8601 standard for representation of dates and times using the gregorian calendar the profile is defined by the date time production in section 5 6 of rfc 3339 the date and time type is compatible with the datetime xml schema type with the following notable exceptions (a) the date and time type does not allow negative years (b) the date and time time offset 00 00 indicates an unknown time zone (see rfc 3339) while 00 00 and +00 00 and z all represent the same time zone in datetime (c) the canonical format (see below) of data and time values differs from the canonical format used by the datetime xml schema type, which requires all times to be in utc using the time offset 'z' this type is not equivalent to the dateandtime textual convention of the smiv2 since rfc 3339 uses a different separator between full date and full time and provides higher resolution of time secfrac the canonical format for date and time values with a known time zone uses a numeric time zone offset that is calculated using the device's configured known offset to utc time a change of the device's offset to utc time will cause date and time values to change accordingly such changes might happen periodically in case a server follows automatically daylight saving time (dst) time zone offset changes the canonical format for date and time values with an unknown time zone (usually referring to the notion of local time) uses the time offset 00 00 /time ranges/time range/absolute cyclic/cyclic range /time ranges/time range/absolute cyclic/cyclic range path /time ranges/time range/absolute cyclic/cyclic range node type choice case description the cyclic time range for days in every week access read write /time ranges/time range/absolute cyclic/cyclic range/days in week /time ranges/time range/absolute cyclic/cyclic range/days in week path /time ranges/time range/absolute cyclic/cyclic range/days in week node type leaf description a set of days in week flags, multiple inputs should be separated by spaces access read write data type \<yang bits bits> constraints bit type with defined bits \[sunday,monday,tuesday,wednesday,thursday,friday,saturday] /time ranges/time range/absolute cyclic/cyclic range/start /time ranges/time range/absolute cyclic/cyclic range/start path /time ranges/time range/absolute cyclic/cyclic range/start node type leaf description the start time of a day access read write data type \<yang type time hhmm> constraints multiple constraints string with length 3 to 5 time string with format 'hh\ mm' 'hh' is hour, 'mm' is minute its range is from 00 00 to 23 59 /time ranges/time range/absolute cyclic/cyclic range/end /time ranges/time range/absolute cyclic/cyclic range/end path /time ranges/time range/absolute cyclic/cyclic range/end node type leaf description the end time of a day access read write data type \<yang type time hhmm> constraints multiple constraints string with length 3 to 5 time string with format 'hh\ mm' 'hh' is hour, 'mm' is minute its range is from 00 00 to 23 59