F3 seems to be a reasonable archival data format. I see many replies criticizing F3 as an operational data format, like Parquet. Of course it can't be made as

F3 seems to be a reasonable archival data format. I see many replies criticizing F3 as an operational data format, like Parquet. Of course it can't be made as fast in the general case, or as compatible to the existing infrastructure. OTOH F3 would be easy to decode into almost any of today's accepted formats, and likely to any of tomorrow's data formats. That's where being self-describing and self-unpacking would be important.