ADX Schema ADIF Version: 3.0.2 Schema Version: 3.0.2.3 Date: 16 February 2013 Description: This schema represents ADIF/ADX as closely as is practical within the features provided by XML Schema 1.0 (see Limitations below). 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. 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 only 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. Change History 2012/05/08 3.0.2.2: New version for ADIF 3.0.2. 2013/06/02 3.0.2.3: Added missing left bracket to CONT field's regular expression. 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