I think we really need to add some guides to demonstrate and motivate stuff on the consumption side to form a complete story. Perhaps COW and CSVLint can currently fulfill this side?
It would be nice for example to add a guide on consuming the grit bins example, and showing the benefits there in R, python, Ruby etc…
Generally I think the biggest bang per buck for CSVW is supporting a consumer side CSVW profile which just adds basic datatype coercion support to the CSV files themselves. I guess you’d need to support URI templates too, so you could have URI as a datatype.
I'm not sure what tooling currently fulfills this usecase; but I think if CSVW is to succeed this is a missing piece.
Longer term it might be worth categorising tools for publication/consumption/validation/transformation etc.
I think we really need to add some guides to demonstrate and motivate stuff on the consumption side to form a complete story. Perhaps COW and CSVLint can currently fulfill this side?
It would be nice for example to add a guide on consuming the grit bins example, and showing the benefits there in R, python, Ruby etc…
Generally I think the biggest bang per buck for CSVW is supporting a consumer side CSVW profile which just adds basic datatype coercion support to the CSV files themselves. I guess you’d need to support URI templates too, so you could have URI as a datatype.
I'm not sure what tooling currently fulfills this usecase; but I think if CSVW is to succeed this is a missing piece.
Longer term it might be worth categorising tools for publication/consumption/validation/transformation etc.