This repository contains descriptions of various app-specific fields for the Abstract ADIF Application or "AAA" for short. The intention of these is to define well-known field names to allow interoperability beyond what the ADIF spec guarantees. The goal is to not burden the ADIF spec with every field imaginable but rather to use the application specific field mechanism it provides to establish a set of well-known field names with well-defined meaning.
ADIF-processing software authors are encouraged to implement whichever documents are applicable to what their software does as well as to contribute field descriptions.
Throughout this and any field definition documents, the key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.