Re: Request for comments - Requirements analysis

Hi all,

This is my first post to the list, so please help guide me if I am off topic.

I’ve added a column “Tim’s comments” to the spreadsheet (attached) posing some questions for consideration.  

Additionally with respect to the annotations requirements, I wonder if these are considered adequately covered / out of scope / too specific:
- Is there a need to declare the NULL value (e.g. \N for mysql dumps) 
- Is there a need to consider declaring the encoding explicitly to enable clients to stream CSVs without reading file headers? 
- Related: Is there a need to declare the compression format as a specific annotation?
- Is there a need to consider split files (particularly those that are compressed as individual parts using e.g. snappy compression)?  This is of particular importance for processing performance (e.g. utilising multiple cores)

Many thanks,
Tim

[1] http://rs.tdwg.org/dwc/terms/guides/text/index.htm
[2] http://www.gbif.org/occurrence







On 28 Apr 2014, at 17:38, Ceolin, D. <d.ceolin@vu.nl> wrote:

> Hi all,
> 
> Eric, Jeremy and I had a first round of comments about the requirements and came up with a series of proposal, nicely organized by Eric. Please find them on github (in CSV or CLS format):
> 
> https://github.com/w3c/csvw/blob/gh-pages/use-cases-and-requirements/csvw-requirements-notes.csv
> 
> https://github.com/w3c/csvw/blob/gh-pages/use-cases-and-requirements/csvw-requirements-notes.xls
> 
> Since we would like to have your opinions, to facilitate commenting, I've also ported the CSV on the wiki (I hope not to create troubles due to duplication of resources):
> 
> https://www.w3.org/2013/csvw/wiki/Requirements_analysis
> 
> We look forward to hearing what you all think,
> 
> Davide