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

Re: Architecture of mapping CSV to other formats

From: Alf Eaton <eaton.alf@gmail.com>
Date: Thu, 24 Apr 2014 09:48:46 +0100
Message-ID: <CAJVrAaSO34Rx4+QNc4Zj7EA=TCZYiowf3P9mq1kXO_Zc_nwBbw@mail.gmail.com>
To: Jeni Tennison <jeni@jenitennison.com>
Cc: "public-csv-wg@w3.org" <public-csv-wg@w3.org>
On 23 April 2014 20:13, Jeni Tennison <jeni@jenitennison.com> 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:
> <data>
>   <row>
>     <GID>1</GID>
>     <On_Street>ADDISON AV</On_Street>
>     <Species>Celtis australis</Species>
>     <Trim_Cycle>Large Tree Routine Prune</Trim_Cycle>
>     <Inventory_Date>10/18/2010</Inventory_Date>
>   </row>
>   ...
> </data>

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:

  <tree gid="1" on-street="ADDISON AV" species="Celtis australis"
trim-cycle="Large Tree Routine Prune" inventory-date="2010-10-18"/>

Received on Thursday, 24 April 2014 08:49:33 UTC

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