On this page
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.
Each calendar configuration is highly flexible but the underlying specification must follow a dedicated syntax.
Time specifiers
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;}
Frame definition
Defines the time frame to be included in the specification (e.g. JAN-MAR).
Scope definition
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 ";".
Hierarchy levels
Time specifiers are ordered in five hierarchical levels:
- Global
- Year
- Month
- Week
- Day
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).
Absolute vs. relative time fames
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. }
Comments
JWT calendars supports single-line comments. Comments begin with a #. e.g.:
#Summer Calendar
Examples and syntax details
If you still have questions, feel free to refer to our support team.