W3C home > Mailing lists > Public > public-csv-wg@w3.org > February 2014

RE: use case: peel sessions

From: Tandy, Jeremy <jeremy.tandy@metoffice.gov.uk>
Date: Wed, 26 Feb 2014 11:03:09 +0000
To: Alf Eaton <eaton.alf@gmail.com>
CC: W3C CSV on the Web Working Group <public-csv-wg@w3.org>
Message-ID: <2624871D9A05174691BD59F8EFD68AE2B36876@EXXCMPD1DAG3.cmpd1.metoffice.gov.uk>
OK - thanks for clarification Alf. I'll leave you to adapt as more use cases get edited into the document.


-----Original Message-----
From: Alf Eaton [mailto:eaton.alf@gmail.com] 
Sent: 25 February 2014 23:46
To: Tandy, Jeremy
Cc: W3C CSV on the Web Working Group
Subject: Re: use case: peel sessions

Hi Jeremy,

The Peel Sessions data has been published in various formats at different times in the past, though some of them have disappeared from the web by now. There was a data dump at <https://web.archive.org/web/20081023060734/http://bbc-hackday.dyndns.org/>
which I think might have been CSV, then an RDF dump, then the current HTML versions at <http://www.bbc.co.uk/radio1/johnpeel/sessions/>.

It would be nice to have a published CSV version to work with again - which is what I was trying to produce, via OpenRefine, hence the use case - but I couldn't figure out the best way to represent multiple, nested values without repeating all the objects multiple times. It seemed like a nice, straightforward example of the kind of thing that CSV (or some other line-oriented format) needs to be able to handle, in one way or another.

Once there are some more use cases written up I'll have a go at adapting this one to the same style; if it turns out that one of the other use cases covers the same ground, feel free to delete it.


On 25 February 2014 22:10, Tandy, Jeremy <jeremy.tandy@metoffice.gov.uk> wrote:
> Hi Alf – thanks for all the great work so far in coming up with use 
> cases for our work.
> I’ve been looking at the Peel Sessions use case and scratching my head 
> a little … I’m probably getting the wrong end of the stick, but it 
> sounds as though this data is not currently published in CSV form. As 
> such it reads a bit like a wish list of “nice to haves”. What I am 
> hoping to get from the use cases are clear, concrete examples of where 
> CSV is already the choice of format for their particular application 
> and/or the limitations of working with Plain-Old-Tabular-Text (let’s 
> call them “POTT”) files are inhibitors to productivity.
> Is there anything unique about this use case that is not covered elsewhere?
> If it does contain unique issues, can you develop this use case 
> further along the lines discussed previously (narrative style etc.)
> Many thanks, Jeremy
Received on Wednesday, 26 February 2014 11:03:38 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:21:39 UTC