Yes, that is one of many, many places trying to be the standard. But that is not a universal, used by everyone, used everywhere standard. CSV is simply not standardized, as any data scientist working with CSV files from all over can quickly tell you. Or a simple google search will tell you. For example, Excel, likely the biggest consumer and producer of CSV files, does not implement RFC 4180. So that is the end of that.
From Wikipedia:
"The CSV file format is not fully standardized. Separating fields with commas is the foundation, but commas in the data or embedded line breaks have to be handled specially. Some implementations disallow such content while others surround the field with quotation marks, which yet again creates the need for escaping if quotation marks are present in the data.
The term "CSV" also denotes several closely-related delimiter-separated formats that use other field delimiters such as semicolons.[2] These include tab-separated values and space-separated values. A delimiter guaranteed not to be part of the data greatly simplifies parsing."
From the Library of Congress database on formats: A CSV file is "A simple de facto format, for which no single, official specification exists."
Just because one guy calls his flavor a standard does not make it a widespread standard, any more than one company adding MIDI to GIFs makes that the newest, universal standard.
I get that you must really, really want GIF89a to be the end all of unchanged golden formats. But the lengths you go to to ignore all this other stuff, without putting in equivalent effort to understand them, is not making the case. Simple spend a minute on Google before posting stuff that is simply untrue. It's easy to find all this stuff.
Since you don't seem to care to read about each format, and understand the nuances and that this question is not the black and white case you want, I'm done providing evidence or cases. Good luck.
From Wikipedia:
"The CSV file format is not fully standardized. Separating fields with commas is the foundation, but commas in the data or embedded line breaks have to be handled specially. Some implementations disallow such content while others surround the field with quotation marks, which yet again creates the need for escaping if quotation marks are present in the data.
The term "CSV" also denotes several closely-related delimiter-separated formats that use other field delimiters such as semicolons.[2] These include tab-separated values and space-separated values. A delimiter guaranteed not to be part of the data greatly simplifies parsing."
From the Library of Congress database on formats: A CSV file is "A simple de facto format, for which no single, official specification exists."
Just because one guy calls his flavor a standard does not make it a widespread standard, any more than one company adding MIDI to GIFs makes that the newest, universal standard.
I get that you must really, really want GIF89a to be the end all of unchanged golden formats. But the lengths you go to to ignore all this other stuff, without putting in equivalent effort to understand them, is not making the case. Simple spend a minute on Google before posting stuff that is simply untrue. It's easy to find all this stuff.
Since you don't seem to care to read about each format, and understand the nuances and that this question is not the black and white case you want, I'm done providing evidence or cases. Good luck.