json-toolkit VS usv

CSV is great because excel can import it, but it can't import USV, so at that point, why use USV when you can use JSON?

https://github.com/tyleradams/json-toolkit/

> Also note that this approach generalizes to other text-based formats. If you have 10 gigabyte of CSV, you can use Miller for processing. For binary formats, you could use fq if you can find a workable record separator.

You can also generalize it without learning a new minilanguage by using https://github.com/tyleradams/json-toolkit which converts csv/binary/whatever to/from json

I really like this tool, but I'm not sure what it gets me more than jq (and https://github.com/tyleradams/json-toolkit to convert non-json to json).

What can angle grinder do better than jq?

The reason why USV did not use the proper ASCII codes for field separator and record separator is a bit too pragmatic for me…

https://github.com/SixArm/usv/tree/main/doc/faq#why-use-cont...

https://github.com/SixArm/usv/blob/main/doc/criticisms/index...

I'm working on standardizing a data exchange format and media time, and seeking advice here from anyone experienced with how to do this.

For example, how to properly submit a request to Internet Assigned Numbers Authority (IANA.org), or Internet Engineering Task Force (IETF.org), and proofread the Augmented Backus-Naur Form (ABNF).

The project is Unicode Separated Values (USV) and media type is "text/usv".

Work in progress here: https://github.com/sixarm/usv

My email is [email protected]

Thanks!

Ben this is great, thank you. Would you be open to adding Unicode Separated Values (USV) as well? It's much like CSV and also simpler because of no escaping and no quoting. I can donate $50 to you or your charity of choice as a token of thanks and encouragement.

https://github.com/sixarm/usv