ADX Schema ADIF Version: 3.1.7 Schema Version: 3.1.7.0 Date: 2026-03-09 DESCRIPTION: This schema represents ADIF/ADX 3.1.7 as closely as is practical within the features provided by XML Schema 1.0 (see LIMITATIONS below). It is specific to ADX 3.1.7 and disallows deprecated features. Expected use is when exporting ADIF as ADX 3.1.7 (For when importing ADX and the ADIF version is not known in advance, the alternative generic schema adx317generic.xsd schema can be used because it allows features deprecated in ADX versions 3.1.7 and earlier.) There is a useful guide here BUT not all features are supported in XML Schema 1.0 regular expressions: "Regular Expression Language - Quick Reference" https://learn.microsoft.com/en-us/dotnet/standard/base-types/regular-expression-language-quick-reference Here's the XML Schema details: "Working with XML Schemas" https://learn.microsoft.com/en-us/dotnet/standard/data/xml/working-with-xml-schemas Note: In regular expressions, it is not possible to use \d because in addition to ASCII 0-9, it matches other Unicode digit characters. LIMITATIONS: MY_STATE and STATE element contents are not validated against the "Primary Administrative Subdivision" enumeration due to the excessively long regular expression required. CNTY_ALT and MY_CNTY_ALT validation is limited to the format rather than specific values 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). LICENSE: This schema by Graham Smith is marked CC0 1.0 Universal. To view a copy of this mark, visit https://creativecommons.org/publicdomain/zero/1.0/ CHANGE HISTORY 2026-03-09 3.1.7.0: New version for ADIF 3.1.7. 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