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

Re: Architecture of mapping CSV to other formats

From: Jeni Tennison <jeni@jenitennison.com>
Date: Thu, 24 Apr 2014 10:45:51 +0100
To: Alf Eaton <eaton.alf@gmail.com>
Cc: "public-csv-wg@w3.org" <public-csv-wg@w3.org>
Message-ID: <etPan.5358dd4f.66334873.640f@jenit.local>
Alf,

What a good default XML representation would be is outside the scope of this particular discussion :) But if you have strong opinions about it, perhaps you’d like to take on speccing it?!? :)

Jeni

------------------------------------------------------
From: Alf Eaton eaton.alf@gmail.com
Reply: Alf Eaton eaton.alf@gmail.com
Date: 24 April 2014 at 09:49:13
To: Jeni Tennison jeni@jenitennison.com
Cc: public-csv-wg@w3.org public-csv-wg@w3.org
Subject:  Re: Architecture of mapping CSV to other formats

> On 23 April 2014 20:13, Jeni Tennison wrote:
>  
> > On the call today we discussed briefly the general architecture of mapping from CSV  
> to other formats (eg RDF, JSON, XML, SQL), specifically where to draw the lines between  
> what we specify and what is specified elsewhere.
> >
> > To make this clear with an XML-based example, suppose that we have a CSV file like:
> >
> > GID,On Street,Species,Trim Cycle,Inventory Date
> > 1,ADDISON AV,Celtis australis,Large Tree Routine Prune,10/18/2010
> > 2,EMERSON ST,Liquidambar styraciflua,Large Tree Routine Prune,6/2/2010
> > 3,EMERSON ST,Liquidambar styraciflua,Large Tree Routine Prune,6/2/2010
> >
> > This will have a basic mapping into XML which might look like:
> >
> >  
> >  
> > 1
> > ADDISON AV
> > Celtis australis
> > Large Tree Routine Prune
> > 10/18/2010
> >  
> > ...
> >  
>  
> As there's only ever a single, string value for each property of an
> item (when the data comes from CSV), it would be most straightforward
> to map everything to attributes as the default:
>  
>  
> > trim-cycle="Large Tree Routine Prune" inventory-date="2010-10-18"/>
> …
>  
>  
> Alf
>  
>  

--  
Jeni Tennison
http://www.jenitennison.com/
Received on Thursday, 24 April 2014 09:45:48 UTC

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