It's already there via JSON. CSV is OK, but you must know the schema of each column/token. Is it a bit? Integer? Real? Text? To come up with some kind of generic CSV parser would be very difficult.
I recommend you read up on JSON. JSON handles it much better than CSV, and Do-more already supports it!
JSON supports arrays and/or fields and you can nest them. For flat CSV, you can easily implement it as an array of 0/1 bits:
[0, 1, 1, 0]
or even as Boolean (Do-more supports BOTH)
[false, true, true, false]
And even better, if it's a profile/recipe, you can store it as "field"/colon/value list:
{
"CookTemp" : 42,
"CookTime": 60,
"UseIngredientA": true,
"UseIncredientB": false
}