Add a "Notes" property to schema

[Ziris85]

Hello! I'm more or less opening this issue to link it to some old-but-ongoing discussion happening here, which is discussing how they might go about adding an ability to add notes to recipes (such as for ingredient swaps, recipe variations, tips & tricks, etc). Their main issue is that the schema they're using (this one) doesn't support it natively, so they're faced with having to do a bolt-on that they'd have to maintain. Ideally this could just be folded in to the schema spec itself, which I think makes enough sense to at least fire up the discussion here on! I have plenty of recipes with little notes and such that can't be included currently (at least not to my, and many others', understanding).

So here's a feature request for just such a thing, if one doesn't already exist 🙂 Thank you!

[github-actions[bot]]

This issue is being nudged due to inactivity.

[MatthiasWiesmann]

Is this needed? can't you just have a CreativeWork like Comment whose about field points to the Recipe object?

[jspidey03]

Hello ! I agree with @Ziris85 : more and more websites and cookbooks include this concept of note, which often presents possible variations or additional information that cannot be quantified. For example I was using the Paprika app which includes that notion but I am not able to get the "Notes" field imported in applications based on the Recipe schema. I'm not familiar with the various field so I cannot say if the Comment would be appropriate. It seems that it is used for richer data.

[Ziris85]

@MatthiasWiesmann , hmm, in my mind that doesn't necessarily fit. A "comment" in this sense seems more like an area for discussion about the recipe from a community or other people. Sure, this commentary may include those folks' tweaks, ingredient swaps, suggestions, etc, but as the author, I may wish to include these kinds of things in the core recipe itself. I guess for me these notes aren't commentary or discussion about the recipe - they ARE the recipe.

On a purely technical level, perhaps a comment field could be used in this way. For the Nextcloud discussion linked, where there is no public forum for recipes, sure the comment field could be repurposed for that. However, just thinking about a public website for hosting recipes where there may be a desire for people to comment on and discuss a recipe, there'd be no means of separating the authors own swaps/optional ingredients/etc and the broader communities. They're similar in nature for sure, but they serve different purposes.