| Code Block | ||||||
|---|---|---|---|---|---|---|
| ||||||
dates = "(1)" ("(2)" "TS.startDate(3)" | "TS.startDate(3)" "-" "TS.endDate(4)") ("(5)" "TS.startTime(6)" | "TS.startEvent(7)" "TS.startTimeRelativeEvent(8)") "-" ("(9)" "TS.endTime(10)" | "TS.endEvent(7)" "TS.endTimeRelativeEvent(8)") {"11" " " ("(5)" "TS.startTime(6)" | "TS.startEvent(7)" "TS.startTimeRelativeEvent(8)") "-" ("(9)" "TS.endTime(10)" | "TS.endEvent(7)" "TS.endTimeRelativeEvent(8)")} {"(12)" " " ("(2)" "TS.startDate(3)" | "TS.startDate(3)" "-" "TS.endDate(4)") ("(5)" "TS.startTime(6)" | "TS.startEvent(7)" "TS.startTimeRelativeEvent(8)") "-" ("(9)" "TS.endTime(10)" | "TS.endEvent(7)" "TS.endTimeRelativeEvent(8)") {"11" " " ("(5)" "TS.startTime(6)" | "TS.startEvent(7)" "TS.startTimeRelativeEvent(8)") "-" ("(9)" "TS.endTime(10)" | "TS.endEvent(7)" "TS.endTimeRelativeEvent(8)")}} "(13)".
remarks = ["ParentElement.annotation.Note (14)" "."]. |
| Reference | Data item (from coding template) | Rule |
|---|---|---|
| (1) | If there are multiple Timesheet (i.e. multiple time periods included in the schedule), then the following algorithm is proposed:
| |
| (2) | Use this branch when:
Otherwise use the alternate branch. | |
| (3) | start date | Convert TS.startDate into the NOTAM format (MMM DD) |
| (4) | end date | If TS.endTime has the value '00:00' (the convention for end of day was applied in the coding), then use the previous calendar (before the coded TS.endDate). Otherwise, use the TS.endDate. Convert the appropriate value in the NOTAM format (MMM DD) |
| (5) | If TS.startTime has a value then use this |
Production rule Dates
If TS.startDate differs from TS.endDate, go through the alternate path, otherwise go through the direct path.
Format the data to show the month abbreviation followed by two digits (MMM DD), eg. AUG 23, according to item D NOTAM syntax. If the month value stored in TS.startDate is identical to the one stored in TS.startDate pertaining to a previous iteration, insert only the day of the month value stored in TS.startDate.
If the month value stored in TS.endDate is identical to the one stored in TS.startDate, insert only the day of the month value stored in TS.endDate.
If consecutive dates are stores in TS.startDate elements or if consecutive date periods are stored in TS.startDate and TS.endDate elements, add a dash between the start date and the end date.
path. Otherwise, if TS.startEvent |
has a value, then use the alternate path. | ||
| (6) | start time | Format the data contained in TS.startTime |
according to NOTAM syntax for this item: hhmm. |
| (7) | start event | Decode this value as follows: 'SR' → "SR", 'SS' → "SS" |
| (8) | rel. start | If TS.startTimeRelativeEvent has a value, then decode |
| by replacing '-' by ' |
| minus' and '+' by ' |
| plus', followed by the number of minutes in mm format. |
| (9 |
| ) | If TS.endTime |
has a value then use this path. Otherwise, if TS.endEvent |
has a value, then use the alternate path. |
| ( |
| 10) |
| end time | Format the data contained in TS. |
endTime according to NOTAM syntax for this item: hhmm. If TS.endTime is '00:00', then the value “2359” shall be used as hhmm group in the NOTAM. | ||
| (11) (12) | If there are multiple Timesheet to process, if the following conditions are met for the next Timesheet (following the ordering specified in rule (1) above):
then, use the return branch (11) and process only the time/event values of the next Timesheet, Otherwise, return through branch (12) and process the next Timesheet in full. | |
| (13) | The algorithm proposed above could still result into date/time groups in item D that have the same date range. That's because the ordering/grouping of the Timesheet is done only by similar starDate/endDate. For example, this could result into the following: "D) SEP 01-05 0700-0900 1300-1400 SEP 08-13 0700-0900 1300-1400 SEP 15 0700 1100". Based on the current NOTAM practice, the first two date/time groups ("SEP 01-05" and "SEP 08-13" should be collapsed into a single dates group, because they have the same times: "D) SEP 01-05 08-13 0700-0900 1300-1400 SEP 15 0700 1100". This streamlining of the resulting schedule text could be done at the end of the text generation process or directly in the production rule, with a more sophisticated algorithm. The resolution of this issue is left for the implementers. | |
| (14) | schedule note | Annotations of parent object that have propertyName='timeInterval' and purpose='REMARK'. shall be translated into free text according to the decoding rules for annotations. The resulting text shall be appended at the end of item E |
A comma shall be used to separate groups of dates or date periods to which the same time periods apply.
If there are any timesheets containing TS.excluded elements with the value 'YES', denoting a schedule with exceptions, select all of them and go through the direct path, otherwise go through the bypass path.
| . |