Why not just put your recipies in a text editor and then use git?
>Hey grandpa, can you show me the family brisket recipe?
>Sure grandson. But first, let me tell you what git is.
I think my current recipes app stores entries in the Recipe JSON Schema format[1]. This format is also useful since many websites will offer recipes in that schema. If I could make a conversion layer that transformed between a markdown version and the JSON recipe schema, that would probably be all I need.
For example, the schema.org schema puts quantities, units, and ingredients in a single field. Fail, IMO.
Other issues include things like not being able to group ingredients or procedures.
I don't have my notes on what I thought of each of the ones I've reviewed handy, but here are some I've looked at:
- http://www.formatdata.com/recipeml/
- https://recipemd.org/index.html
EDIT - for clarity, added examples of standards
Why? Recipes are for humans to read, and we're good at accomodating a wide variety of formats as long as they are reasonably sane.