So every (good) recipe enumerates several lists of things:

  • Ingredients: a list of all the foods/seasonings/etc. that you'll use when following the recipe
  • Utensils: a list of all the tools, utensils and appliances that you'll use when following the recipe

My question: Is there an umbrella term for both ingredients and utensils? Meaning, some term that implies both of them?

In other words, instead of maintaining two lists, 1 for ingredients, and 1 for utensils, I'd like to make 1 master list of everything you'd need for a recipe. What would I call that master list?!?

(Not-so-pro-tip: it can't be "recipe" because the recipe is the algorithm you follow to produce some final dish.)

  • 4
    For what it's worth, plenty of good recipes don't really list tools, utensils, or appliances - it's generally only potentially helpful to call out equipment if it's something irreplaceable people would be likely not to have.
    – Cascabel
    Commented Jan 11, 2016 at 15:52
  • I'm building food/culinary related software and am trying to understand the domain language. A Recipe has a list of dependencies, Ingredients and Utensils, but need a meaningful, domain-specific term to refer to them both.
    – smeeb
    Commented Jan 11, 2016 at 17:12
  • @smeeb : a concept only needs a label if you're going to be presenting it to the user. If you're just using it internally, any identifier will suffice. (although most people really object to it, but it's often needed in multi-language ontologies where concepts don't neatly match up between languages/cultures ... like that whole cobbler/betty/crisp thing.
    – Joe
    Commented Jan 11, 2016 at 17:24
  • Technically a "recipe" includes variables (lists -- the ingredients/utensils), function/algorithm (the instructions on what to do with the variables), and metadata (e.g. name of recipe, servings, nutrition information). It's not just the algorithm :)
    – Erica
    Commented Jan 11, 2016 at 17:28
  • Okay, so this is a "what do I name my variables" question. I believe what I said is still relevant: if you want to ever show the recipe to a user, you need to be able to show just the ingredients, so having the ingredient and equipment lists merged is maybe not so good! Yes, you can tag your items with types, and select only items of the appropriate type to show - but the point is that it's worth trying to have your data structure design mirror the way people actually think about recipes.
    – Cascabel
    Commented Jan 11, 2016 at 17:30

1 Answer 1



(which is way too short of an answer for the site to accept on its own)

  • Oh good answer, I was thinking gee, I don't knownwhatbthatnwould be, but you nailed it
    – Escoce
    Commented Jan 11, 2016 at 15:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.