I prefer having something resilient to arbitrary data. Currently this uses 64-character fields for event descriptions and UIDs -- but we can change that later. CSV is a pain the ass to deal with.

Hence why there's a `dev` in the filename, we can version them as needed and add conversion modules once it's rolled out. Overkill, but it works.

If you *really* want flexibility, take a look at Google Protocol Buffers. IIRC they have Python bindings. That shit's cray.