...
Note that the concept of "weekday ranges" (such as "MON-WED") is also not supported in this specification. However, the automatic NOTAM generation rules for item D ensure that a set of consecutive weekdays with a similar start/end time will generate a "weekday range", according to the OPADD recommendations. This does not exclude implementing an HMI that allows the input of weekday ranges, for efficiency reasons. They will have to be converted into individual weekday records in AIXM.
In addition, according to the OPADD, item D is not allowed to exceed 200 characters. The application interface should check the length of the item D that results from the schedule encoding and invite the operator to split the NOTAM into two separate events in case this limit is exceeded. The HMI should allow copying a draft event into a second draft event.
UML class diagrams representation
...
The TEMPDELTA shall contain the complete definition of the activity times, including any eventual time ranges that are recuperated from the BASELINE schedules. Note that according to the OPADD, notification of a schedule modification by NOTAM shall be done by including the new schedule in item E, not in item D. Therefore, the list of Event Scenarios has to include separate scenarios for such situations.
Data encoding rules
The data encoding rules provided in this section shall be followed in order to ensure the harmonisation of the digital encodings provided by different sources. These rules shall be used as complementing the General coding rules for Schedules defined in AIXM Coding Overview - Common Coding Rules - Common coding patterns. In case of contradiction, the rules described below are superseding the general ones.
The information items that may occur in the definition of schedules are identified in the diagrams described in the Common Coding Rules - Common coding patterns, section Common coding patterns. For use of "daily", "on date" and "date ranges" templates please refer to Common coding patterns - "Daily" schedules diagram. For use of "on weekday" and "from weekday...to weekday" please refer to Common coding patterns - "Weekday" schedules diagram. Each diagram is accompanied by the corresponding graphical elements explanation.
The compliance with some of these encoding rules can be checked with automatic data validation rules (see next section).
...
The rule could be deleted from here. A new rule chould be put under the common coding part:
...
Common coding patterns
The Common coding patterns apply also for Digital NOTAM Event schedules, but with the limitations specified below.
"Daily" and "date" based schedules
Refer to the Common coding patterns "Daily" schedules diagram.The following additional coding rules apply:
each use of "daily", "on date", "date range", "on weekday", or "from weekday...to weekday" shall be encoded as a single Timesheet, according to the [
...
TSH] and [/
...
TSH] indications in the
...
Note: There exists already an indication in the common coding patterns, that separate Timesheets are needed but they are mentioned with respect to the diagrams. Probably needs to be deleted.
...
diagrams;
"on date" needs to be coded with both startDate and endDate having the same value
If "excluded date" is used, then
...
it shall be encoded as one Timesheet that has excluded='YES', startTime='00:00' and endTime='24:00'; startDate and endDate shall both get the value specified for "
...
excluded date".
...
The rule could be deleted from here. A new rule chould be put under the common coding part:
If the Timesheet is related to one single date, both the Timesheet.startDate and the Timesheet.endDate shall get the value specified for that date.
...
The rule could be deleted from here. A new rule chould be put under the common coding part:
If the Timesheet is related to one single date or date range, then Timesheet.day shall get the value "ANY" and Timesheet.dayTill shall be left empty.
...
The rule could be deleted from here. A new rule chould be put under the common coding part:
If the Timesheet is related to one single date, a weekday or time interval spreading over multiple weekdays then in the corresponding Timesheet(s) both startDate and endDate shall be left empty.
...
The rule could be deleted from here. A new rule chould be put under the common coding part:
If the Timesheet is related to a weekday then Timesheet.day shall get that value and Timesheet.dayTill shall be left empty.
...
I suggest to keep the rule here due to the time reference limitation. The common rules contain already an indication regarding excluded date, but require to be coded having timeReference='UTC+/-X' (local time as UTC zone).
...
"Days of the week" based schedules
Refer to the Common coding patterns "Days of the week" schedules diagram.
Data encoding rules
...
The data encoding rules provided in this section shall be followed in order to ensure the harmonisation of the digital encodings provided by different sources. These rules shall be used as complementing the General coding rules for Schedules defined in AIXM Coding Overview - Common Coding Rules - Common coding patterns. In case of contradiction, the rules described below are superseding the general ones.
The compliance with some of these encoding rules can be checked with automatic data validation rules (see next section).
| Identifier | Data encoding rule | Remarks (column to be deleted at the end) | |||
|---|---|---|---|---|---|
| TSH.EVT-01 | Any Timesheet that is part of a TimeSlice associated with an Event that isNotifiedBy NOTAM and shall have timeReference='UTC' | In NOTAM is is mandatory to use UTC times only. | |||
| TSH.EVT-02 | Any Timesheet that is part of a TimeSlice associated with an Event that isNotifiedBy NOTAM and shall have daylightSavingAdjust='NO' | In NOTAM it is not allowed to use a auto-adjusted summer time values. | |||
| TSH.EVT-03 | Any Timesheet that is part of a TimeSlice associated with an Event that isNotifiedBy NOTAM and that has assigned values for startDate and endDate, must have day equal-to 'ANY'. | In NOTAM it is not possible to mix date ranges with week days. | |||
| TSH.EVT-04 | Any Timesheet that is part of a TimeSlice associated with an Event that isNotifiedBy NOTAM cannot use 'WORK_DAY', 'BEF_WORK_DAY', 'AFT_WORK_DAY', 'HOL', 'BEF_HOL', 'AFT_HOL' and 'BUSY_FRI' as day or dayTill values. | HOL and similar are not allowed in NOTAM schedules | |||
| TSH.EVT-05 | It is not allowed to use "overnight" time periods in Event Schedules, e.g. 2200-0600. These shall be split into two separate time periods, e.g. 2200-2400 and 0000-0600.(to be deleted) | The rule could be deleted from here. A new rule chould be put under the common coding part: The rule could be deleted from here. A new rule chould be put under the common coding part: It is not allowed to use "overnight" time periods in Schedules, e.g. 2200-0600. These shall be split into two separate time periods, e.g. 2200-2400 and 0000-0600. | If a schedule is more complex than the types provided, then it shall be described in as a free text "note". |
...