RSV-Specification

A similar concept that is (IMHO) much nicer: RSV It doesn't need any escaping or quoting: a field just has to be valid UTF-8. The trick is that the delimiters are bytes that are invalid UTF-8. The spec fits on a napkin, parsing is trivial, you can jump to the middle of a doc and find the nearest row, etc. Main downside is you need an editor/viewer that can handle it. https://github.com/Stenway/RSV-Specification

I don't think I would ever consider RSV and Parquet alongside each other. I also don't think I've ever personally had a use case where the proposed RSV format would have been a good fit. Nevertheless I found it interesting. Even if you were to use FS, GS, RS, US, they are all parts of valid UTF-8 strings. I agree that they would be vanishingly rare in most corpi of "ordinary text". The author here is also aware of them.[0] I found it quite an interesting idea to use bytes that are invalid in UTF-8 strings as delimiters for data that is guaranteed to be encoded as UTF-8 strings. This moves those control characters properly out of band. Out of band is a much stronger guarantee than vanishingly rare. I don't think I'll use RSV anytime soon, but I appreciate the creativity that went into it, as well as the many implementations the author has