|
On this page |
Each calendar configuration is highly flexible but the underlying specification must follow a dedicated syntax. |
JWT calendars elements and syntax
A calendar is a system on which JWT will be able to do time calculations. Each calendars should be composed of at least one time specifier.
A simple time specifier is composed of a time definition or frame and a scope definition in the following format:
<frame> { <scope>; } #e.g. JAN-MAR {08:00 - 12:00;} |
Defines the time frame to be included in the specification (e.g. JAN-MAR).
The scope definition further refines a time frame. Multiple time definitions and scopes can be specified and nested based on their hierarchy level.
Each scope needs to be ended with a ";".
Time specifiers are ordered in five hierarchical levels:
A time specifier of a particular level is always explicitly or implicitly contained in a time specifier of the immediately higher level (e.g. a day is contained in a month). When the higher level time specifier is not configured (e.g. no month defined) , then it is implicitly contained in an unrestricted higher level time specifier (e.g. year). |
|
Time specifiers each have a dedicated priority. In case that two or more time specifiers overlap in the same level, the one with the highest priority is applied.
Time specifiers with the same priority in the same level are not allowed to overlap, i.e., the intersection of their time definitions must be empty.
Time specifiers can be classified into two categories:
Absolute: Defines the unique and specific parts of the time continuum. This category of time specifiers represents the ones in the global level.
2020/03/25 #this is a unique and specific date |
Relative: Define parts of the time in the context of other time specifiers. The definition depends on the time specifier where it is contained. This category of time specifiers is contained in the all levels besides the global.
FRI { 08:00 - 15:00; #the time specifier depends on the "container". In this a day of the week, which is Friday. } |
JWT calendars supports single-line comments. Comments begin with a #. e.g.:
#Summer Calendar |
The following table represents all the available time specifiers ordered by level and priority:
High priority | Medium priority | Low priority | |||||
---|---|---|---|---|---|---|---|
Level | |||||||
Global | Date list
| Date
| Year list
| ||||
Year | Month-Day list
| Month-day
| Month list
| ||||
Month | Day of month list
| ||||||
Week | Day of week list
| ||||||
Day | Whole day
| Time
| Empty
|
Get some inspiration by looking at the example specifications below.
Calendar | Description | |||
---|---|---|---|---|
| Any date-time with time part between 08:00 and 15:00, or 16:00 and 20:00.
| |||
| Mondays to Fridays from 08:00 to 15:00 and from 16:00 to 20:00. | |||
|
| |||
|
| |||
| This calendar additionally contains a specification for:
| |||
| This example combines two calendars. A future calendar coming into effect on December 1st of 2021 and the currently valid calendar.
|