Wikidata:Property proposal/preparation instructions
Jump to navigation
Jump to search
preparation instructions[edit]
Originally proposed at Wikidata:Property proposal/Generic
Not done
Description | instructions for the recipe |
---|---|
Represents | cooking (Q38695) |
Data type | Multilingual text (not available yet) |
Domain | Wikibook recipes |
Example 1 | warm black bean salad with kale and tomatoes (Q59862818) → "In a medium saucepan, heat oil over medium heat for 2-3 minutes. Add onion, garlic, and a pinch of salt into the pan. Cook and stir 2-3 minutes or until onion is tender." (en) |
Example 2 | MISSING |
Example 3 | MISSING |
Motivation[edit]
This way we can make Cookbook recipes more machine readable. NMaia (talk) 18:45, 18 December 2018 (UTC)
Discussion[edit]
- Is the intention to put together some kind of machine-readable language for such instructions? The example seems to be written in a (non-structured) human language, and would not be structured data... --Yair rand (talk) 16:05, 19 December 2018 (UTC)
- IMO what's important is not so much the text in the instructions, but the fact that they are intructions, and given in a certain order for the reader. I don't see how it would be useful to make the instructions themselves machine-readable, since we're not going to have robots preparing full meals anytime soon, but it could be useful as an instant answer for a search engine, for instance. NMaia (talk) 19:30, 19 December 2018 (UTC)
- I see. Oppose, as this would not be structured data, and thus would not be suitable for Wikidata. --Yair rand (talk) 05:04, 14 March 2019 (UTC)
- IMO what's important is not so much the text in the instructions, but the fact that they are intructions, and given in a certain order for the reader. I don't see how it would be useful to make the instructions themselves machine-readable, since we're not going to have robots preparing full meals anytime soon, but it could be useful as an instant answer for a search engine, for instance. NMaia (talk) 19:30, 19 December 2018 (UTC)
- Comment Hmm, this really doesn't seem like the right place for this. However, to pursue a bit further (and it might help if you added additional examples) - for a recipe you have a list of ingredients, for which we have has part(s) (P527) with qualifiers for amount etc., and then a sequence of preparation instructions. For the example recipe you've linked there are actually a sequence of 3, so with this property you would presumably add 3 statements with this property, with a series ordinal (P1545) qualifier to order them? ArthurPSmith (talk) 19:05, 20 December 2018 (UTC)
- That's how I envisioned it, yes. NMaia (talk) 12:26, 22 December 2018 (UTC)
- Something a bit more specific than "significant event" qualified with "series ordinal" could work. --- Jura 09:09, 16 March 2019 (UTC)
- Oppose I don't see a reason to introduce plain text into Wikidata for such a minor purpose.
- People do prepare meals with now with Alexa (who's basically a robot for this purpose) but machine-readability is also important to allow automatic translation and analysis of the data. ChristianKl ❪✉❫ 11:22, 21 December 2018 (UTC)
- Oppose I've attempted to model two simple recipe using structured data at sautéed mushrooms (Q29887670) and duxelles (Q1268122). Improvements are needed for example, consideration of temperature and duration of cooking steps. This would be my preference over the use of non-structured textual data for recipes. I admit that it is a significant amount more work. For example, with more complex recipes, it'd be necessary to create items for intermediate food states such as "browned onion" and have dozens of cooking methods/processes listed using fabrication method (P2079) for each recipe. Dhx1 (talk) 13:13, 20 March 2019 (UTC)
- Those are some very interesting proofs-of-concept! NMaia (talk) 01:06, 21 March 2019 (UTC)
Not done No appetite for this at the moment. Good to see ingestigation of other methods of representation. --99of9 (talk) 07:50, 17 April 2019 (UTC)