Propose these changes:
New structure would look like:
// csvddfVersion is now optional
Client specs (e.g. Tabular Data Package) would probably nest this info under a key named dialect or similar but that would be up to them.
Version change: csvddfVersion would be bumped to 2.0
Make keys optional and specify defaults for their absence (defaults would be as in the example above).
I agree. For the datapackage validator I did, I assumed that the dialect key in the package referred to the sub key, rather than nesting (I couldn't find examples).
So a flatter structure with suggestion of a default key name (dialect) for embedding sounds good to me.
[csv-dialect][s]: fixes #99 (move attributes up a level and set defau…