@kentquirk that's a great point. I was thinking about this from the perspective of supporting Nutshell rather than creating a more generic data model that can be augmented by individual use cases.

In that case, I'd suggest we change "name_of_meal" to "name_of_food", because a meal is often a collection of foods. Then make sure it's possible to tie multiple food "events" together into a single master "meal" event. Some more examples below.

In the Nutshell example, "FBLT" would be one food event and "Guacamole" would be another. We'd tie these together to make the meal. The same goes for "Burger" and "Fries". 

This has to scale, in case you're eating "Burger", "Fries", "Milkshake", and a "Slice of Key Lime Pie". It also applies to just "Chocolate cake". Or to "Celery" and "Carrots".

Keeping the food items independent allows us to flexibility to interact with nutrition or recipe APIs. And maintaining the ability to bring them together allows us to accurately reflect how the user thinks about their meal.