- From: Andy Seaborne <andy@apache.org>
- Date: Wed, 10 Sep 2014 11:21:48 +0100
- To: public-csv-wg@w3.org
One aspect of this choice is whether a transformation of a CSV file to be published on the web so other people (other than the data publisher) run it? Or is it the input for a toolkit to generate format X and then a file with format X is put on the web? If transforms are published, then there is a requirement for a programming-language, template-language independent solution. I agree this is more work. Assuming javascript is a possibility; while it is arguably the safest single choice, it does not work for many environments. If you're in a lang-X programmer (e.g. R), you want to use lang-X skills. Otherwise, if it's a tool-input and not published to be run elsewhere, it does not need this portability requirement. A language or a basic-transform+improve style is more reasonable. The tool space is weaker (transforms are tool specific). Andy
Received on Wednesday, 10 September 2014 10:22:17 UTC