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

Re: ACTION-29: Document patterns of use for conversion to different formats (CSV on the Web Working Group)

From: Jeni Tennison <jeni@jenitennison.com>
Date: Sat, 13 Sep 2014 17:17:46 +0100
To: CSV on the Web Working Group <public-csv-wg@w3.org>
Message-ID: <etPan.54146e2a.1f48eaa1.14e@jenit.local>
Hi,

I have attempted to document a few different scenarios in which people might want to convert CSV into another format. These are here:

  https://github.com/w3c/csvw/blob/gh-pages/examples/conversion-scenarios.md

but also below.

---

## User-created configuration

### For Importing

Andrea downloads a set of CSV files that she's found on the web and she wants to import it into the MySQL database that she's using. She is using a third-party tool to do the import. She can perform a default import of each CSV file individually (so each CSV file becomes a table, and she then uses SQL commands to convert the data as necessary into columns with the correct types and cross-references between tables) but the tool can also be configured by supplying a descriptive (metadata) file for the CSV files.

She creates the metadata file to configure things like:

  * the names of the tables in the import
  * the names of the columns in those tables
  * the types of the columns
  * which are the primary keys and references between tables

To run the import, she points the tool at the metadata file and it creates the new tables and columns within her database, providing errors when the data doesn't match the schema that she's assumed.

### For Display

Bill is creating a web application in which he is displaying crimes within a city as a heatmap. The data is published by his local municipality on a routine basis and embeds it in his page using a web component. The web component enables Bill to simply point to the CSV file and indicate which columns should be used to provide longitude, latitude and label.

The municipality has included a metadata file that defines a conversion of the CSV file into a structured GeoJSON format, but the web component that Bill uses assumes a simple tabular structure and thus ignores the conversion supplied by the publisher in the metadata file.

## Publisher-created configuration

Clara is using some server-side software (like Jekyll) which automatically creates statically converted versions of contact information that she provides as CSV. This means that she can just author and update CSV files but her website can provide those files in a variety of formats for others to reuse (eg schema.org JSON for those that prefer it, vCard RDF for those that prefer that, HTML with embedded microdata for a readable page).

The server-side software uses the metadata file that Clara authors to work out how to do the conversions into other formats. She decides on what those conversions should look like to meet the existing standard formats for sharing contact information. The styling of the HTML page in particular needs to be customised to give the site the look and feel that she wants.

---

Have I missed any scenarios that demonstrate different kinds of requirements (not just changing the type of format that is being targeted)?

Cheers,

Jeni

-----Original Message-----
From: CSV on the Web Working Group Issue Tracker <sysbot+tracker@w3.org>
Reply: CSV on the Web Working Group <public-csv-wg@w3.org>>
Date: 10 September 2014 at 13:58:46
To: jeni@jenitennison.com <jeni@jenitennison.com>>
Subject:  ACTION-29: Document patterns of use for conversion to different formats (CSV on the Web Working Group)

> ACTION-29: Document patterns of use for conversion to different formats (CSV on the  
> Web Working Group)
>  
> http://www.w3.org/2013/csvw/track/actions/29
>  
> On: Jeni Tennison
> Due: 2014-09-17
>  
> If you do not want to be notified on new action items for this group, please update your  
> settings at:
> http://www.w3.org/2013/csvw/track/users/33715#settings
>  
>  
>  

--  
Jeni Tennison
http://www.jenitennison.com/
Received on Saturday, 13 September 2014 16:18:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:27:42 UTC