Comma Separated JSON

Re:Comma Separated JSON by gregmac on Tuesday June 21, 2016 @08:45PM (#11950756)

This is actually a very elegant way of formalizing CSV. For most apps, if you were to simply output "CSV files" using this encoding, really no one consuming them would know any different -- except you could actually point them at a spec being used.

I've been in arguments with customers before where they complained we were quoting strings, and CSV files shouldn't have quotes, and it would have been nice to say "We're using CSJ, please just parse that way".

I think the name is perhaps misleading though, as it sounds more like it's a variant of JSON than a formalization of CSV. Perhaps "JSON flavored CSV" would be more appropriate?

[ Parent | on HN ]

Re:Comma Separated JSON by LukeShu on Wednesday June 22, 2016 @12:31AM (#11951564)

I mean, you could always point them to RFC 4180.

[ Parent | on HN ]

Re:Comma Separated JSON by gregmac on Friday July 01, 2016 @02:00PM (#12018293)

Okay talk about ironic. Yesterday in our ops meeting, it came up that some tool another department had built was exporting csv "with extra quotes that were causing problems" (I've had no involvement in any of this). My ears perked up remembering this comment and I was able to point out this RFC, so hopefully it will save them some time in arguing about csv formatting. Thanks!

[ Parent | on HN ]

Re:Comma Separated JSON by gregmac on Wednesday June 22, 2016 @08:40PM (#11958141)

Ah, well, look at that. Thankfully I haven't had to deal with CSV files for several years, though I wish I knew about that RFC at the time. Thanks.

[ Parent | on HN ]

Re:Comma Separated JSON by astrodust on Wednesday June 22, 2016 @01:35PM (#11955608)

"Comma-Separated JSON" implies objects, "object-notation" is integral to the definition.

What about "Comma-Separated JSON Values"? CSJV!

[ Parent | on HN ]