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

On 12 Mar 2014, at 17:27 , Ross Jones <ross@servercode.co.uk> wrote:

> Sorry for missing the call today, Wednesday's has turned out to be a bad day for me.
> 
> I’m fairly sure Rufus will get back with his use-cases but from my perspective on data.gov.uk converting CSV to JSON has been useful when using JSON as the lingua franca to talk to apps in the browser. It's more widely implemented in browsers and involves less (no) external libraries to process, 'guarantees' a correct encoding and is easily query-able. Would a use-case for csv->json for presentation be useful? I could write one up to describe how CKAN uses it for previewing data.  

Although I am not Jeremy:-) I think this use case would be very useful indeed!

Thanks

Ivan

> 
> Ross
> 
> 
> On 12 Mar 2014, at 14:54, Tandy, Jeremy <jeremy.tandy@metoffice.gov.uk> wrote:
> 
>> (FAO: Rufus Pollock)
>>  
>> At today’s teleconf we raised the issue that the current set of use cases lack an explicit motivation to convert from CSV to JSON or XML.
>>  
>> There is a clear requirement to transform from CSV to RDF – 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
> 


----
Ivan Herman, W3C 
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
GPG: 0x343F1A3D
FOAF: http://www.ivan-herman.net/foaf