Earlier quoted context omitted.
Note the qualifier: “not an Internet standard” (my emphasis).
And again: None of that matters. I am not talking about formalities here, I am talking about technical realities. Whether it is formally called a standard or no doesn't change the fact that this is the document everyone points at when determining what CSV is and is supposed to look like. So it is de-facto a standard. Call it a "quasi standard" if that makes you happy.
CSVs Are Kinda Bad. DSVs Are Kinda Good
131–133 of 133 posts
Re: CSVs Are Kinda Bad. DSVs Are Kinda Good
#132Earlier quoted context omitted.
> https://www.ietf.org/rfc/rfc4180.txt is very clear about what CSV files are supposed to look like Mm, not really. By its own admission, it is descriptive, not prescriptive : > This section documents the format that seems to be followed by most implementations And it came out in 2005, by which date CSVs had already been in use for some twenty or thirty years.
It doesn't matter when it came out, it doesn't matter that it it descriptive. It is the standard, period. Yes, CSV is much, much older. In fact it predates personal computers. And it went through changes. Again: None of that matters. We have a standard, we should use the standard, and systems should demand the standard. Standards are meant to ensure minimal-friction interoperability. If systems don't enforce standard…
Re: CSVs Are Kinda Bad. DSVs Are Kinda Good
#133Earlier quoted context omitted.
And again: None of that matters. I am not talking about formalities here, I am talking about technical realities. Whether it is formally called a standard or no doesn't change the fact that this is the document everyone points at when determining what CSV is and is supposed to look like. So it is de-facto a standard. Call it a "quasi standard" if that makes you happy.
Oh no; I agree with you completely. I just wanted to point out that the document does not disclaim being a “standard”, is just says that it is not an “Internet standard”.