3 ms·
Strange that they can call it a standard yet continue to include non-agreed-upon extensions. At some point it becomes false advertising, unless they fork it und
by paulryanrogers 7y ago
Strange that they can call it a standard yet continue to include non-agreed-upon extensions. At some point it becomes false advertising, unless they fork it under a new MIME type
- sokoloff 7y agoI believe a company has a right to support backwards compatibility for file formats. If they propose a standard and the outcome of the standards work prevents their supporting backwards compatibility (in both directions), I’d rather they support their customers (and their data/files), document their extension use, even at the expense of pure standards implementations not being able to read those files.