lack of clear motivation for transforming from CSV to JSON or XML

(FAO: Rufus Pollock)

At today's teleconf<http://www.w3.org/2014/03/12-csvw-minutes.html> we raised the issue that the current set of use cases<http://w3c.github.io/csvw/use-cases-and-requirements/> lack an explicit motivation to convert from CSV to JSON or XML.

There is a clear requirement to transform from CSV to RDF<http://w3c.github.io/csvw/use-cases-and-requirements/#R-CsvToRdfTransformation> - which implies that is should be possible to convert CSV to one or more of the RDF encodings (incl. TTL, RDF/XML and JSON-LD) ...

But there's a risk that this RDF-centric approach misses a concern simply about, say, converting CSV to simple JSON.

In particular, we noted how "CSV-2-JSON" appears to be central to the work of Rufus Pollock et al.

Rufus - are you able to comment and, preferably, provide a use case which illustrates the utility of CSV-2-JSON conversion?

Many thanks, Jeremy