XDIF

logging and more in XML, by and for hams

What is XDIF?

• XDIF is the name for a new ham radio logging format based on XML.
• XDIF.org is a community consortium and is vendor-neutral.
• The goal of XDIF.org is to develop a common XML framework for amateur radio operations, starting with logging, and later serving as a clearinghouse for developing interoperable XML definitions for other areas of ham radio, such as DX spotting, callsign lookup, and propagation reports.
• Design of XDIF is be done through mailing lists and a bulletin board, open for any radio amateur to join.
• To join the mailing list, or just read the archives, visit the xdif-discuss mailing list page
• To join the bulletin board, or just read the postings, visit the bboard page

Goals and Requirements for XDIF Logging format

• Develop a standards-based XML format for amateur radio logging
• Leverage the power of XML and associated tools to provide precise definitions of logging formats and improve interoperability
• Use XML extensibility to make XDIF resilient in the face of future changes in bands, modes, contests, and propagation records.
• Enable new classes of operations such as combination ham logs / web logs.
• ... More TBD

Samples

Get an idea for some current explorations in XDIF format below, but please note that these are a samples for experimental purposes only, and do not necessarily reflect the goals and requirements of XDIF:

• Submission xdif-200603120001 from WA5ZNU (download zip, browse, CHANGELOG), including WA5ZNU FD 2005 log, WA5ZNU EQP 2006 log, and enumerations
• See the map sample at Map_of_USA_with_state_names.svg. Try clicking on Arizona or Colorado. The logfile used is wa5znu-fybo.xml.

Process

• Any licensed ham is eligible for membership, though there will be criteria for remaining in good standing
• Discussion will take place in publicly-readable mailing lists
• Comments from the ham radio community will be sought during each phase of development.
• XDIF members must grant a royalty-free license to any intellectual property required to implement XDIF to anyone who implements software conformant with XDIF.
• Work products for XDIF logging format will include the following:
  • Formal definitions of XDIF in at least XML Schema and Relax NG
  • Sample XDIF log files
  • Formal definitions of ancillary XML files describing such things as
    • human-readable labels for items such as propagation modes, etc.
    • programmatic data such as band limits.
  • Sample, but not necessarily normative, versions of the ancillary files.
• ... More TBD

QA and Conformance

• There should be a test suite.
• There should be multiple levels of conformance, including at least the following:
  • Import -- an application can import an XDIF log file, but discards any information that it does not already process (for example, a generic logging application might discard VHF Contesting qualifiers)
  • Exchange -- an application can import an XDIF log file, and can keep all information in the original log, even if it does not handle the functionality or extension, can support modifications to the parts that it does handle, and can save the resulting file back in XDIF format without loss.
• ... More TBD

Mailing list Members

Membership in the mailing list does not necessarily imply support for XDIF or agreement with the above principles.

Current members include

• AA7BQ, Fred Lloyd
• AA6YQ, Dave Bernstein
• AE6IP, Martin Fouts
• DF3CB, Bernd Koch
• HB9DRV, Simon Brown
• KC8RRO, Mark Harms
• KD5FID, Steve Ahrendt
• KD6WYK, Rich Hyde
• KE4MA, Mark Andrews
• LX1NO, Norbert Oberweis
• N5UP, Dave Morris
• NW7US Tomas Hood
• OH2KKU, Tapio Sokura
• PE1DSR, John Sjouken
• WA5ZNU, Leigh Klotz, Jr.
• W6FB, Jack Brindle

Calls needed for:

• MVHenly
• PSIONIC
• Mike Goodey
• Dave Gibson
• Robert Barron