tablib

W3C CSVW supports per-column schema. Serialize a dict containing a value with uncertainties and/or Pint (or astropy.units) and complex values to JSON, then read it from JSON back to the same types. Handle datetimes, complex values, and categoricals "CSVW: CSV on the Web" https://github.com/jazzband/tablib/issues/305 7 Columnar metadata header rows for a CSV: column label, property URI, datatype, quantity/unit, accuracy, precision, significant figures https://wrdrd.github.io/docs/consulting/linkedreproducibilit... CSV on the Web: A Primer > 6. Advanced Use > 6.1 How do you support units of measure? https://www.w3.org/TR/tabular-data-primer/#units-of-measure You can specify units in a CSVW file with QUDT, an RDFS schema and vocabulary for Quantities, Units, Dimensions, and Types Schema.org has StructuredValue and rdfs:subPropertyOf like

There are two problems that reasonably explain the decision of only accepting public domain info: licensing and provenance. "Licensing" is hard. The "Open Specifications Promise" [1], which covers a bunch of Microsoft-designed file formats, is merely a covenant not to sue. "Provenance" is tricky. For example, much of the knowledge of the Apple iWork formats were derived by reverse-engineering the source programs and extracting protobuf definitions. Many open source projects have freely copied from each other, making detailed analysis tricky [2]. [1] https://en.wikipedia.org/wiki/Microsoft_Open_Specification_P... [2] https://github.com/jazzband/tablib/issues/114