ADX Schema ADIF Versions: 3.1.4 - 3.0.2 Schema Version: 3.1.4.0 Date: 2022/11/01 DESCRIPTION: This schema represents ADIF/ADX 3.1.4 - 3.0.2 as closely as is practical within the features provided by XML Schema 1.0 (see LIMITATIONS below). It is not version-specific and includes deprecated features. It is provided for situations where the ADX version is not known in advance and could be ADX 3.1.4 or earlier. Expected use is when importing ADIF as ADX. (For when exporting ADX 3.1.4, the alternative version-specific schema, adx312.xsd, provides more accurate validation because it does not allow deprecated features. Similar schemas exist for previous versions: adx313.xsd, adx312.xsd, adx311.xsd, adx310.xsd, adx309.xsd, adx308.xsd, adx307.xsd, adx306.xsd, adx305.xsd, adx304.xsd, adx303.xsd, and adx302.xsd) LIMITATIONS: MY_STATE and STATE element contents are not validated against the "Primary Administrative Subdivision" enumeration due to the excessively long regular expression required. User-defined field names (contents of the USERDEF element nested in the HEADER element) are not validated against the pre-defined ADIF field names due to the excessively long regular expression required. USERDEF elements nested in the HEADER element can optionally have either a RANGE or ENUM attribute but not both; this is not validated. Values in FIELDNAME attributes belonging to USERDEF elements nested in a RECORD element are not validated against the USERDEF elements in the HEADER element. USERDEF elements nested in RECORD elements do not have their contents validated against the TYPE, RANGE or ENUM (if any) attributes of the corresponding USERDEF element nested in the HEADER element. APP element contents are not validated against the TYPE attribute (if any) given. In a record or in the header, no field may appear in more than one Data Specifier; this is not validated. CHECKS NOT REQUIRED: CONTEST_ID element contents are not validated against the "Contest ID" enumeration because the ADIF field type is "String" (i.e. the enumeration is advisory). CNTY and MY_CNTY element contents are not validated against the "Secondary Administrative Subdivision" enumeration because the enumeration values are controlled by external organizations and so are subject to change without notice. SUBMODE element contents are not validated against the "Submode" enumeration because the ADIF field type is "String" (i.e. the enumeration is advisory). CHANGE HISTORY 2022/11/01 3.1.4.0: New version for ADIF 3.1.4. Award_Enumeration is not defined as it is included as part of the AwardList data type. Contest_ID_Enumeration is not referenced because CONTEST_ID is of type String