...
The data verification 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.
| 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 shall have timeReference='UTC' | In NOTAM 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 shall have daylightSavingAdjust='NO' | In NOTAM it is not allowed to use 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 |
| ||
| new | The startTimeRelativeEvent@uom cannot be other-than 'MIN' | proposed by Indra/Avitech, based on OPADD 4.1, section 2.3.20.2 |
| new | The endTimeRelativeEvent@uom cannot be other-than 'MIN' | proposed by Indra/Avitech, based on OPADD 4.1, section 2.3.20.2 |
| new | The startTimeRelativeEvent value cannot be higher-than 99 | proposed by Indra/Avitech, based on OPADD 4.1, section 2.3.20.2 |
| new | The endTimeRelativeEvent value cannot be higher-than 99 | proposed by Indra/Avitech, based on OPADD 4.1, section 2.3.20.2 |