Replies: 1 comment
-
|
The how-to schemas (i.e., So, in addition to (1) encoding alternatives, choices, and optionality in procedures, there are to consider: (2) encoding parallel or concurrent sequences of steps, and (3) encoding procedures which might branch, or vary, based upon conditions or upon observations or decisions to be made by those following the procedures. With respect to With respect to Implementation might involve providing instances of Some collections of alternatives, choices, or options could be, could use, or could map with the In my opinion, it's worth considering both simple That is, some simple representations of a Meanwhile, other more complex representations of a |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Context: I previously asked a question about how to represent multi-part recipes using the Recipe schema. The suggestion provided by Jarno van Driel was to represent each part as a separate HowToStep, each of which contains a Recipe, example:
{ "@context": "https://schema.org", "@type": "Recipe", "author": "Alice", "name": "Example Recipe", "recipeInstructions": [{ "@type": "HowToStep", "position": 1, "name": "Make Shortcrust pastry", "text": "Follow the recipe for Shortcrust pastry.", "item": { "@type": "Recipe", "name": "Shortcrust pastry", "recipeIngredient": [ "1 cup flour", "1 cup butter", "1 tbs water" ], "recipeInstructions": [{ "@type": "HowToStep", "position": 1, "name": "cut", "text": "cut butter into flour" }, { "@type": "HowToStep", "position": 2, "name": "add", "text": "add water and work into crust" }, { "@type": "HowToStep", "position": 3, "name": "form", "text": "form into oval on pan" }] } }, { "@type": "HowToStep", "position": 2, "name": "Make Choux pastry", "text": "Follow the recipe for Choux pastry.", "item": { "@type": "Recipe", "name": "Choux pastry", "recipeIngredient": [ "1 cup flour", "1/4 cup butter", "1 cup water", "3 eggs" ], "recipeInstructions": [{ "@type": "HowToStep", "position": 1, "name": "follow", "text": "follow the standard stove top process" }, { "@type": "HowToStep", "position": 2, "name": "place", "text": "place pastry on top of shortcrust" }, { "@type": "HowToStep", "position": 3, "name": "bake", "text": "bake together at 400 degrees for 40 minutes" }] } }] }Goal: I would like to represent variations ("choose to do this instead") and optional steps in this schema. For example, offering the choice of making a Greek-style dressing or an Italian-style dressing when making a salad.
Research: I have reviewed HowToStep, but none of the properties seem to be useful for this to specify optionality or a choice. I have also reviewed ChooseAction, which seems like it could be used to offer choices under the item property of a HowToStep. However, it's not clear to me how to encode choose 1 vs choose n vs optional using these types.
Question: What would be the best way to encode choices and optionality in recipes?
Thank you in advance for your help!
Beta Was this translation helpful? Give feedback.
All reactions