recipe-brainstorming - Revision history

DaveCorboy: /* Promoting hRecipe for use in Recipe Search Indexing */

2010-04-04T04:57:13Z

Promoting hRecipe for use in Recipe Search Indexing

← Older revision		Revision as of 04:57, 4 April 2010
Line 170:		Line 170:

	--[[User:DaveCorboy\|DaveCorboy]] 03:43, 22 March 2010 (UTC)		--[[User:DaveCorboy\|DaveCorboy]] 03:43, 22 March 2010 (UTC)

			* We have now published the page I reference above [http://www.ziplist.com/recipe_microformat here]. --[[User:DaveCorboy\|DaveCorboy]] 04:57, 4 April 2010 (UTC)

	==== Proposed Extensions ====		==== Proposed Extensions ====

DaveCorboy: promoting some extensions to hRecipe for use in recipe search indexing

2010-03-22T03:43:39Z

promoting some extensions to hRecipe for use in recipe search indexing

← Older revision		Revision as of 03:43, 22 March 2010
Line 160:		Line 160:
	* Do we have <code>ingredients</code> (plural) as an element? Doesn't that open a whole can of list-issues? --[[User:ThomasLoertsch\|ThomasLoertsch]] 15:37, 01 Oct 2008 (CET)		* Do we have <code>ingredients</code> (plural) as an element? Doesn't that open a whole can of list-issues? --[[User:ThomasLoertsch\|ThomasLoertsch]] 15:37, 01 Oct 2008 (CET)

			=== Promoting hRecipe for use in Recipe Search Indexing ===
			My company has an interest in the establishment and adoption of a recipe-based microformat in support of our goal to index recipe content for search.

			We would like to promote a few [http://microformats.org/wiki/posh POSH] extensions to hRecipe that we think will be useful to the recipe-publishing community in support of our shared intention to promote hRecipe's adoption as a standard.

			I have outlined these extensions (and our rationale) below and would like to ask the community for comment in advance of any publication. After comment, we will host a public page outlining the extensions which will refer to microformats.org as the authoritative source for hRecipe.

			(My intent is also to share whatever data we collect on the adoption of hRecipe in the sites we index, which will include smaller blogger sites where we expect hRecipe will initially be most prevalent.)

			--[[User:DaveCorboy\|DaveCorboy]] 03:43, 22 March 2010 (UTC)

			==== Proposed Extensions ====
			===== comment =====
			* An inline comment for an ingredient within the recipe.
			* Optional. Text. Limited to one '''comment''' per ingredient.
			* ''Rationale: We have seen a number of examples in the wild of comments mixed in with ingredients. '''comment''' allows the expression of a standard ingredient list while also allowing for prose-style lists and additional commentary (e.g., substitutions) related to specific ingredients.''
			Example
			<pre><nowiki>
			<ul>
			<li class="ingredient">1 cup of walnuts or pecans
			<span class="comment">
			(Though I usually prefer pecans in most recipes, I like walnuts best in this.)
			</span>
			</li>
			</ul>
			</nowiki></pre>

			===== step =====
			* The steps necessary to prepare the recipe.
			* Optional. Text. No limit to the total number of '''step'''s per recipe. Use of step properties within an instructions block are optional, but recommended.
			* ''Rationale: The [http://www.cookingforengineers.com/recipe/33/Lemon-Bars Cooking for Engineers] website is an excellent real-world example of the many alternative recipe writing styles described in [http://www.anthus.com/Recipes/CompCook.html this paper]. hRecipe has reasonably [http://microformats.org/wiki/recipe-issues#closed_issues closed this as an immediate need], however we wish to try to accommodate this sort of prose-style recipes that do not have an explicit collection of steps.''
			Example
			<pre><nowiki>
			<div class="instructions">
			<p>So before we get to the recipe, let me tell you a story about cranberries...</p>
			<p>
			Now, let's get to cooking! First, you will need to <span class="step">coarsely grind the cranberries. Fill your blender 2/3 full...</span>
			After you have done this, you will need to <span class="step">pour the blender contents into your strainer and let the liquid...</span>
			</p>
			<p>
			All this cooking reminds me of the apple farm where I grew up...
			Now that you know where apples come from, you will need to <span class="step">peel and dice the apples and add them to the drained cranberries.</span>
			</p>
			</div>
			</nowiki></pre>

			===== preptime =====
			* Time it takes for the preparation step of the recipe.
			* Optional. Text or the property may be encoded using the [http://microformats.org/wiki/value-class-pattern value-class-pattern]. Limited to one '''preptime''' per recipe.
			* ''Rationale: We add '''preptime''' and '''cooktime''' to help publishers express these values explicitly and request only one '''duration''' property to express total time for the recipe.''
			Example
			<pre><nowiki>
			<h6>Preparation time: <span class="preptime">5 minutes</span></h6>
			</nowiki></pre>

			===== cooktime =====
			* Time it takes for the cooking step of the recipe.
			* Optional. Text or the property may be encoded using the [http://microformats.org/wiki/value-class-pattern value-class-pattern]. Limited to one '''cooktime''' per recipe.
			* ''Rationale: We add '''preptime''' and '''cooktime''' to help publishers express these values explicitly and request only one '''duration''' property to express total time for the recipe.''
			Example
			<pre><nowiki>
			<h6>Cooking time: <span class="cooktime">25 minutes</span></h6>
			</nowiki></pre>

			===== tag =====
			* One or more tags (cuisine, keyword, etc.) for the recipe.
			* Optional. No limit to number of '''tag''' properties per recipe.
			* ''Rationale: Our use of tagging is very different from the use-case of [http://microformats.org/wiki/rel-tag rel-tag] which requires a tagspace. In our use case, we need to allow users of the microformat the ability to associate descriptive words to a recipe, but cannot require they also construct a web infrastructure. This view is correctly rejected by the rel-tag issues reviewers citing large-scale sites such as Flickr and del.icio.us. Perhaps "tags" is simply the wrong term for us?''
			Example
			<pre><nowiki>
			<span class="tag">Salad</span>
			<span class="tag">Fruit</span>
			</nowiki></pre>

			===== category =====
			* Category of the recipe.
			* Optional. Limited to one '''category''' per recipe.
			* ''Rationale: While hRecipe recommends tags for this, we find that the category of the recipe is often treated differently in published recipes and we'd like to try to promote it out of the tags.''
			Example
			<pre><nowiki>
			<span class="category">Side dish</span>
			</nowiki></pre>

			===== difficulty =====
			* Difficulty level of preparing the recipe.
			* Optional. The value should be encoded as a fraction using the '''value-title''' class defined in the [http://microformats.org/wiki/value-class-pattern value-class-pattern]. Limited to one '''difficulty''' per recipe.
			* ''Rationale: While hRecipe recommends tags for this, we find that the difficulty of the recipe is often expressed in published recipes as a specific ratio.''
			Example
			<pre><nowiki>
			<span class="difficulty"><span class="value-title" title="1/3" />Easy</span>
			</nowiki></pre>

			===== rating =====
			* Rating of the recipe.
			* Optional. The value should be encoded as a fraction using the '''value-title''' class defined in the [http://microformats.org/wiki/value-class-pattern value-class-pattern]. Limited to one '''rating''' per recipe.
			* ''While hRecipe recommends tags for this, we find that the rating of the recipe is often expressed in published recipes as a specific ratio.''
			Example
			<pre><nowiki>
			<span class="rating"><span class="value-title" title="4/5" /><img src="/images/4-out-of-5-stars.jpg" /></span>
			</nowiki></pre>

	==issues==		==issues==

ThomasLoertsch: moved format-in-progress-#2 to the brainstorming-archive

2009-07-09T12:49:23Z

moved format-in-progress-#2 to the brainstorming-archive

Show changes

Brian: Reverted edits by SitboMonvi (Talk) to last version by TobyInk

2009-01-03T19:16:01Z

Reverted edits by SitboMonvi (Talk) to last version by TobyInk

← Older revision		Revision as of 19:16, 3 January 2009
Line 1:		Line 1:
	~~chic4terco~~
	Towards a [[recipe\|Recipe]] microformat. Please read the [[process]] before editing this page.		Towards a [[recipe\|Recipe]] microformat. Please read the [[process]] before editing this page.

Line 40:		Line 39:
	===Root Class Name===		===Root Class Name===

	To be decided. Likely ~~âhRecipeâ~~.		To be decided. Likely ‘hRecipe’.

	===Property List===		===Property List===
Line 182:		Line 181:
	*** None of the [[recipe-examples]] show references to species names, therefore there is no empirical justification for inclusion of such detail in the microformat. [[User:Tantek\|Tantek]] 23:19, 27 December 2008 (UTC)		*** None of the [[recipe-examples]] show references to species names, therefore there is no empirical justification for inclusion of such detail in the microformat. [[User:Tantek\|Tantek]] 23:19, 27 December 2008 (UTC)
	**** The vast majority of recipes reference a species of plant or animal (e.g. "chicken", "carrot"). Binomial/trinomial names are pretty much never seen of course, but the current species proposal allows for vernacular (common) names to be marked up, so it is not an especially odd suggestion to define a pattern for marking up species within ingredients. [[User:TobyInk\|TobyInk]] 20:11, 29 December 2008 (UTC)		**** The vast majority of recipes reference a species of plant or animal (e.g. "chicken", "carrot"). Binomial/trinomial names are pretty much never seen of course, but the current species proposal allows for vernacular (common) names to be marked up, so it is not an especially odd suggestion to define a pattern for marking up species within ingredients. [[User:TobyInk\|TobyInk]] 20:11, 29 December 2008 (UTC)
	** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta\|Î±]]		** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta\|α]]
	**Units need separate microformat: see [[measure]]		**Units need separate microformat: see [[measure]]
	**Ingredient Preparation: such as diced, chopped, sliced, grated, minced, etc. [[User:SteveL\|Steve Lewis]] 18:55, 11 Feb 2007 (PST)		**Ingredient Preparation: such as diced, chopped, sliced, grated, minced, etc. [[User:SteveL\|Steve Lewis]] 18:55, 11 Feb 2007 (PST)
Line 189:		Line 188:
	**Calories per serving [[User:JohnLeMasney\| John LeMasney]]		**Calories per serving [[User:JohnLeMasney\| John LeMasney]]
	**Calories per ounce [[User:JohnLeMasney\| John LeMasney]]		**Calories per ounce [[User:JohnLeMasney\| John LeMasney]]
	*Background Information - Optional section to encapsulate information that is useful but not necessarily required for a successful recipe. [[User:AlexanderShusta\|Î±]]		*Background Information - Optional section to encapsulate information that is useful but not necessarily required for a successful recipe. [[User:AlexanderShusta\|α]]
	**Author (Person) ([[hcard]]?)		**Author (Person) ([[hcard]]?)
	**Submitter (Person) ([[hcard]]?)		**Submitter (Person) ([[hcard]]?)
Line 201:		Line 200:
	**Steps (optional)		**Steps (optional)
	***Should be an ordered list [[User:AndyMabbett\|Andy Mabbett]] 14:46, 16 Nov 2006 (PST)		***Should be an ordered list [[User:AndyMabbett\|Andy Mabbett]] 14:46, 16 Nov 2006 (PST)
	***Another vote for an ordered list, perhaps in the [[XOXO]] format. [[User:AlexanderShusta\|Î±]]		***Another vote for an ordered list, perhaps in the [[XOXO]] format. [[User:AlexanderShusta\|α]]
	***Many recipes associate ingredients with specific steps of a multi-step method; if methods are broken out into steps, then the format should support this association whether the complete ingredient list is up front or the ingredient list is itself broken out per step. [[User:Quixote\|Ben Curtis]]		***Many recipes associate ingredients with specific steps of a multi-step method; if methods are broken out into steps, then the format should support this association whether the complete ingredient list is up front or the ingredient list is itself broken out per step. [[User:Quixote\|Ben Curtis]]
	*Photo (optional) [[User:IamCam\|Cameron Perry]]		*Photo (optional) [[User:IamCam\|Cameron Perry]]
Line 219:		Line 218:
	*Suitability (e.g. vegetarian, vegan, wheat-free, etc.). Possibly [[rel-tag]]. [[User:AndyMabbett\|Andy Mabbett]] 14:57, 16 Nov 2006 (PST)		*Suitability (e.g. vegetarian, vegan, wheat-free, etc.). Possibly [[rel-tag]]. [[User:AndyMabbett\|Andy Mabbett]] 14:57, 16 Nov 2006 (PST)
	*Ingredient Grouping - In baking you need to differentiate wet from dry ingredients. See also an [[recipe-examples\|example recipe]] from [http://www.extratasty.com/recipe/46/cuba_libre extratasty.com] for useful grouping in cocktail mixing. [[SteveL\|Steve Lewis]] 19:10, 11 Feb 2007		*Ingredient Grouping - In baking you need to differentiate wet from dry ingredients. See also an [[recipe-examples\|example recipe]] from [http://www.extratasty.com/recipe/46/cuba_libre extratasty.com] for useful grouping in cocktail mixing. [[SteveL\|Steve Lewis]] 19:10, 11 Feb 2007
	** Maybe this ingredient grouping can be used to express some alternative ingredients, like "mayonnaise or cream cheese". [[EstevaoSamuel\|~~EstÃªvÃ£o~~ Samuel ~~ProcÃ³pio~~]] 15:33, 16 Dez 2007 (PDT)		** Maybe this ingredient grouping can be used to express some alternative ingredients, like "mayonnaise or cream cheese". [[EstevaoSamuel\|Estêvão Samuel Procópio]] 15:33, 16 Dez 2007 (PDT)
	** This could be solved by using a xoxo list and ignoring list items that don't include a class="name". Example:<pre><nowiki>		** This could be solved by using a xoxo list and ignoring list items that don't include a class="name". Example:<pre><nowiki>
	<ul class="ingredients">		<ul class="ingredients">

SitboMonvi: c4tdelrola

2009-01-03T11:26:36Z

c4tdelrola

← Older revision		Revision as of 11:26, 3 January 2009
Line 1:		Line 1:
			chic4terco
	Towards a [[recipe\|Recipe]] microformat. Please read the [[process]] before editing this page.		Towards a [[recipe\|Recipe]] microformat. Please read the [[process]] before editing this page.

Line 39:		Line 40:
	===Root Class Name===		===Root Class Name===

	To be decided. Likely ~~‘hRecipe’~~.		To be decided. Likely âhRecipeâ.

	===Property List===		===Property List===
Line 181:		Line 182:
	*** None of the [[recipe-examples]] show references to species names, therefore there is no empirical justification for inclusion of such detail in the microformat. [[User:Tantek\|Tantek]] 23:19, 27 December 2008 (UTC)		*** None of the [[recipe-examples]] show references to species names, therefore there is no empirical justification for inclusion of such detail in the microformat. [[User:Tantek\|Tantek]] 23:19, 27 December 2008 (UTC)
	**** The vast majority of recipes reference a species of plant or animal (e.g. "chicken", "carrot"). Binomial/trinomial names are pretty much never seen of course, but the current species proposal allows for vernacular (common) names to be marked up, so it is not an especially odd suggestion to define a pattern for marking up species within ingredients. [[User:TobyInk\|TobyInk]] 20:11, 29 December 2008 (UTC)		**** The vast majority of recipes reference a species of plant or animal (e.g. "chicken", "carrot"). Binomial/trinomial names are pretty much never seen of course, but the current species proposal allows for vernacular (common) names to be marked up, so it is not an especially odd suggestion to define a pattern for marking up species within ingredients. [[User:TobyInk\|TobyInk]] 20:11, 29 December 2008 (UTC)
	** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta\|α]]		** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta\|Î±]]
	**Units need separate microformat: see [[measure]]		**Units need separate microformat: see [[measure]]
	**Ingredient Preparation: such as diced, chopped, sliced, grated, minced, etc. [[User:SteveL\|Steve Lewis]] 18:55, 11 Feb 2007 (PST)		**Ingredient Preparation: such as diced, chopped, sliced, grated, minced, etc. [[User:SteveL\|Steve Lewis]] 18:55, 11 Feb 2007 (PST)
Line 188:		Line 189:
	**Calories per serving [[User:JohnLeMasney\| John LeMasney]]		**Calories per serving [[User:JohnLeMasney\| John LeMasney]]
	**Calories per ounce [[User:JohnLeMasney\| John LeMasney]]		**Calories per ounce [[User:JohnLeMasney\| John LeMasney]]
	*Background Information - Optional section to encapsulate information that is useful but not necessarily required for a successful recipe. [[User:AlexanderShusta\|α]]		*Background Information - Optional section to encapsulate information that is useful but not necessarily required for a successful recipe. [[User:AlexanderShusta\|Î±]]
	**Author (Person) ([[hcard]]?)		**Author (Person) ([[hcard]]?)
	**Submitter (Person) ([[hcard]]?)		**Submitter (Person) ([[hcard]]?)
Line 200:		Line 201:
	**Steps (optional)		**Steps (optional)
	***Should be an ordered list [[User:AndyMabbett\|Andy Mabbett]] 14:46, 16 Nov 2006 (PST)		***Should be an ordered list [[User:AndyMabbett\|Andy Mabbett]] 14:46, 16 Nov 2006 (PST)
	***Another vote for an ordered list, perhaps in the [[XOXO]] format. [[User:AlexanderShusta\|α]]		***Another vote for an ordered list, perhaps in the [[XOXO]] format. [[User:AlexanderShusta\|Î±]]
	***Many recipes associate ingredients with specific steps of a multi-step method; if methods are broken out into steps, then the format should support this association whether the complete ingredient list is up front or the ingredient list is itself broken out per step. [[User:Quixote\|Ben Curtis]]		***Many recipes associate ingredients with specific steps of a multi-step method; if methods are broken out into steps, then the format should support this association whether the complete ingredient list is up front or the ingredient list is itself broken out per step. [[User:Quixote\|Ben Curtis]]
	*Photo (optional) [[User:IamCam\|Cameron Perry]]		*Photo (optional) [[User:IamCam\|Cameron Perry]]
Line 218:		Line 219:
	*Suitability (e.g. vegetarian, vegan, wheat-free, etc.). Possibly [[rel-tag]]. [[User:AndyMabbett\|Andy Mabbett]] 14:57, 16 Nov 2006 (PST)		*Suitability (e.g. vegetarian, vegan, wheat-free, etc.). Possibly [[rel-tag]]. [[User:AndyMabbett\|Andy Mabbett]] 14:57, 16 Nov 2006 (PST)
	*Ingredient Grouping - In baking you need to differentiate wet from dry ingredients. See also an [[recipe-examples\|example recipe]] from [http://www.extratasty.com/recipe/46/cuba_libre extratasty.com] for useful grouping in cocktail mixing. [[SteveL\|Steve Lewis]] 19:10, 11 Feb 2007		*Ingredient Grouping - In baking you need to differentiate wet from dry ingredients. See also an [[recipe-examples\|example recipe]] from [http://www.extratasty.com/recipe/46/cuba_libre extratasty.com] for useful grouping in cocktail mixing. [[SteveL\|Steve Lewis]] 19:10, 11 Feb 2007
	** Maybe this ingredient grouping can be used to express some alternative ingredients, like "mayonnaise or cream cheese". [[EstevaoSamuel\|~~Estêvão~~ Samuel ~~Procópio~~]] 15:33, 16 Dez 2007 (PDT)		** Maybe this ingredient grouping can be used to express some alternative ingredients, like "mayonnaise or cream cheese". [[EstevaoSamuel\|EstÃªvÃ£o Samuel ProcÃ³pio]] 15:33, 16 Dez 2007 (PDT)
	** This could be solved by using a xoxo list and ignoring list items that don't include a class="name". Example:<pre><nowiki>		** This could be solved by using a xoxo list and ignoring list items that don't include a class="name". Example:<pre><nowiki>
	<ul class="ingredients">		<ul class="ingredients">

TobyInk: /* RecipeML-based Brainstorm */ species

2008-12-29T20:11:40Z

RecipeML-based Brainstorm: species

← Older revision		Revision as of 20:11, 29 December 2008
Line 180:		Line 180:
	**Some (e.g. meats, vegetables) could optionally be marked up with (elements of) the proposed [[species]] microformat. [[User:AndyMabbett\|Andy Mabbett]] 06:41, 16 Nov 2006 (PST)		**Some (e.g. meats, vegetables) could optionally be marked up with (elements of) the proposed [[species]] microformat. [[User:AndyMabbett\|Andy Mabbett]] 06:41, 16 Nov 2006 (PST)
	*** None of the [[recipe-examples]] show references to species names, therefore there is no empirical justification for inclusion of such detail in the microformat. [[User:Tantek\|Tantek]] 23:19, 27 December 2008 (UTC)		*** None of the [[recipe-examples]] show references to species names, therefore there is no empirical justification for inclusion of such detail in the microformat. [[User:Tantek\|Tantek]] 23:19, 27 December 2008 (UTC)
			**** The vast majority of recipes reference a species of plant or animal (e.g. "chicken", "carrot"). Binomial/trinomial names are pretty much never seen of course, but the current species proposal allows for vernacular (common) names to be marked up, so it is not an especially odd suggestion to define a pattern for marking up species within ingredients. [[User:TobyInk\|TobyInk]] 20:11, 29 December 2008 (UTC)
	** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta\|α]]		** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta\|α]]
	**Units need separate microformat: see [[measure]]		**Units need separate microformat: see [[measure]]

Tantek: brainstorming based on implied schema of examples is better than explicit schema of other formats, rm nonexistent pagelink, note new pages for hRecipe etc.

2008-12-27T23:19:05Z

brainstorming based on implied schema of examples is better than explicit schema of other formats, rm nonexistent pagelink, note new pages for hRecipe etc.

← Older revision		Revision as of 23:19, 27 December 2008
Line 171:		Line 171:
	==brainstorming==		==brainstorming==
	===RecipeML-based Brainstorm===		===RecipeML-based Brainstorm===
			'''NOTE: Brainstorms should be based on implied schema of examples, not on explicit schema of other formats. The only exceptions where this appears to have been ok (perhaps I got lucky) was with hCard (based on vCard) and hCalendar (based on iCalendar), but even in those cases, experience has shown that there are several properties in each that in practice have not shown much if any use, therefore indicating that the microformats were/are bigger than they need(ed) to be.''' [[User:Tantek\|Tantek]] 23:19, 27 December 2008 (UTC)

	Excerpted from [http://conoroneill.com/2006/03/21/what-if-i-suggest-a-structured-recipe-format-and-you-critique-it/ Conor Bandon's Blog entry] and derived from The RecipeML Spec:		Excerpted from [http://conoroneill.com/2006/03/21/what-if-i-suggest-a-structured-recipe-format-and-you-critique-it/ Conor Bandon's Blog entry] and derived from The RecipeML Spec:
	*Recipe_Title		*Recipe_Title
Line 177:		Line 179:
	*Ingredients (each one a separate "item" rather than block text with count/amount/range/unit broken out too)		*Ingredients (each one a separate "item" rather than block text with count/amount/range/unit broken out too)
	**Some (e.g. meats, vegetables) could optionally be marked up with (elements of) the proposed [[species]] microformat. [[User:AndyMabbett\|Andy Mabbett]] 06:41, 16 Nov 2006 (PST)		**Some (e.g. meats, vegetables) could optionally be marked up with (elements of) the proposed [[species]] microformat. [[User:AndyMabbett\|Andy Mabbett]] 06:41, 16 Nov 2006 (PST)
			*** None of the [[recipe-examples]] show references to species names, therefore there is no empirical justification for inclusion of such detail in the microformat. [[User:Tantek\|Tantek]] 23:19, 27 December 2008 (UTC)
	** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta\|α]]		** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta\|α]]
	**Units need separate microformat: see [[measure]]		**Units need separate microformat: see [[measure]]
Line 326:		Line 329:

	== related pages ==		== related pages ==
	* [[recipe]]		[[recipe]] effort per the process:
	* [[recipe-feedback]]
	* [[recipe-examples]]		* [[recipe-examples]]
	* [[recipe-brainstorming-archive]]
	* [[recipe-formats]]		* [[recipe-formats]]
			* [[recipe-brainstorming]] (see also [[recipe-brainstorming-archive]])
	* [[recipe-issues]]		* [[recipe-issues]]
	* [[~~recipe~~-~~hrecipe2rdf~~]]
			See now:
			* [[hRecipe]]
			* [[hrecipe-issues\|hRecipe issues]]

Brian: Reverted edits by DrondArvar (Talk) to last version by ThomasLoertsch

2008-12-20T22:14:27Z

Reverted edits by DrondArvar (Talk) to last version by ThomasLoertsch

← Older revision		Revision as of 22:14, 20 December 2008
Line 1:		Line 1:
	~~relsitace~~
	Towards a [[recipe\|Recipe]] microformat. Please read the [[process]] before editing this page.		Towards a [[recipe\|Recipe]] microformat. Please read the [[process]] before editing this page.

Line 40:		Line 39:
	===Root Class Name===		===Root Class Name===

	To be decided. Likely ~~âhRecipeâ~~.		To be decided. Likely ‘hRecipe’.

	===Property List===		===Property List===
Line 178:		Line 177:
	*Ingredients (each one a separate "item" rather than block text with count/amount/range/unit broken out too)		*Ingredients (each one a separate "item" rather than block text with count/amount/range/unit broken out too)
	**Some (e.g. meats, vegetables) could optionally be marked up with (elements of) the proposed [[species]] microformat. [[User:AndyMabbett\|Andy Mabbett]] 06:41, 16 Nov 2006 (PST)		**Some (e.g. meats, vegetables) could optionally be marked up with (elements of) the proposed [[species]] microformat. [[User:AndyMabbett\|Andy Mabbett]] 06:41, 16 Nov 2006 (PST)
	** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta\|Î±]]		** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta\|α]]
	**Units need separate microformat: see [[measure]]		**Units need separate microformat: see [[measure]]
	**Ingredient Preparation: such as diced, chopped, sliced, grated, minced, etc. [[User:SteveL\|Steve Lewis]] 18:55, 11 Feb 2007 (PST)		**Ingredient Preparation: such as diced, chopped, sliced, grated, minced, etc. [[User:SteveL\|Steve Lewis]] 18:55, 11 Feb 2007 (PST)
Line 185:		Line 184:
	**Calories per serving [[User:JohnLeMasney\| John LeMasney]]		**Calories per serving [[User:JohnLeMasney\| John LeMasney]]
	**Calories per ounce [[User:JohnLeMasney\| John LeMasney]]		**Calories per ounce [[User:JohnLeMasney\| John LeMasney]]
	*Background Information - Optional section to encapsulate information that is useful but not necessarily required for a successful recipe. [[User:AlexanderShusta\|Î±]]		*Background Information - Optional section to encapsulate information that is useful but not necessarily required for a successful recipe. [[User:AlexanderShusta\|α]]
	**Author (Person) ([[hcard]]?)		**Author (Person) ([[hcard]]?)
	**Submitter (Person) ([[hcard]]?)		**Submitter (Person) ([[hcard]]?)
Line 197:		Line 196:
	**Steps (optional)		**Steps (optional)
	***Should be an ordered list [[User:AndyMabbett\|Andy Mabbett]] 14:46, 16 Nov 2006 (PST)		***Should be an ordered list [[User:AndyMabbett\|Andy Mabbett]] 14:46, 16 Nov 2006 (PST)
	***Another vote for an ordered list, perhaps in the [[XOXO]] format. [[User:AlexanderShusta\|Î±]]		***Another vote for an ordered list, perhaps in the [[XOXO]] format. [[User:AlexanderShusta\|α]]
	***Many recipes associate ingredients with specific steps of a multi-step method; if methods are broken out into steps, then the format should support this association whether the complete ingredient list is up front or the ingredient list is itself broken out per step. [[User:Quixote\|Ben Curtis]]		***Many recipes associate ingredients with specific steps of a multi-step method; if methods are broken out into steps, then the format should support this association whether the complete ingredient list is up front or the ingredient list is itself broken out per step. [[User:Quixote\|Ben Curtis]]
	*Photo (optional) [[User:IamCam\|Cameron Perry]]		*Photo (optional) [[User:IamCam\|Cameron Perry]]
Line 215:		Line 214:
	*Suitability (e.g. vegetarian, vegan, wheat-free, etc.). Possibly [[rel-tag]]. [[User:AndyMabbett\|Andy Mabbett]] 14:57, 16 Nov 2006 (PST)		*Suitability (e.g. vegetarian, vegan, wheat-free, etc.). Possibly [[rel-tag]]. [[User:AndyMabbett\|Andy Mabbett]] 14:57, 16 Nov 2006 (PST)
	*Ingredient Grouping - In baking you need to differentiate wet from dry ingredients. See also an [[recipe-examples\|example recipe]] from [http://www.extratasty.com/recipe/46/cuba_libre extratasty.com] for useful grouping in cocktail mixing. [[SteveL\|Steve Lewis]] 19:10, 11 Feb 2007		*Ingredient Grouping - In baking you need to differentiate wet from dry ingredients. See also an [[recipe-examples\|example recipe]] from [http://www.extratasty.com/recipe/46/cuba_libre extratasty.com] for useful grouping in cocktail mixing. [[SteveL\|Steve Lewis]] 19:10, 11 Feb 2007
	** Maybe this ingredient grouping can be used to express some alternative ingredients, like "mayonnaise or cream cheese". [[EstevaoSamuel\|~~EstÃªvÃ£o~~ Samuel ~~ProcÃ³pio~~]] 15:33, 16 Dez 2007 (PDT)		** Maybe this ingredient grouping can be used to express some alternative ingredients, like "mayonnaise or cream cheese". [[EstevaoSamuel\|Estêvão Samuel Procópio]] 15:33, 16 Dez 2007 (PDT)
	** This could be solved by using a xoxo list and ignoring list items that don't include a class="name". Example:<pre><nowiki>		** This could be solved by using a xoxo list and ignoring list items that don't include a class="name". Example:<pre><nowiki>
	<ul class="ingredients">		<ul class="ingredients">

DrondArvar: lioupascnac4

2008-12-20T03:55:20Z

lioupascnac4

← Older revision		Revision as of 03:55, 20 December 2008
Line 1:		Line 1:
			relsitace
	Towards a [[recipe\|Recipe]] microformat. Please read the [[process]] before editing this page.		Towards a [[recipe\|Recipe]] microformat. Please read the [[process]] before editing this page.

Line 39:		Line 40:
	===Root Class Name===		===Root Class Name===

	To be decided. Likely ~~‘hRecipe’~~.		To be decided. Likely âhRecipeâ.

	===Property List===		===Property List===
Line 177:		Line 178:
	*Ingredients (each one a separate "item" rather than block text with count/amount/range/unit broken out too)		*Ingredients (each one a separate "item" rather than block text with count/amount/range/unit broken out too)
	**Some (e.g. meats, vegetables) could optionally be marked up with (elements of) the proposed [[species]] microformat. [[User:AndyMabbett\|Andy Mabbett]] 06:41, 16 Nov 2006 (PST)		**Some (e.g. meats, vegetables) could optionally be marked up with (elements of) the proposed [[species]] microformat. [[User:AndyMabbett\|Andy Mabbett]] 06:41, 16 Nov 2006 (PST)
	** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta\|α]]		** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta\|Î±]]
	**Units need separate microformat: see [[measure]]		**Units need separate microformat: see [[measure]]
	**Ingredient Preparation: such as diced, chopped, sliced, grated, minced, etc. [[User:SteveL\|Steve Lewis]] 18:55, 11 Feb 2007 (PST)		**Ingredient Preparation: such as diced, chopped, sliced, grated, minced, etc. [[User:SteveL\|Steve Lewis]] 18:55, 11 Feb 2007 (PST)
Line 184:		Line 185:
	**Calories per serving [[User:JohnLeMasney\| John LeMasney]]		**Calories per serving [[User:JohnLeMasney\| John LeMasney]]
	**Calories per ounce [[User:JohnLeMasney\| John LeMasney]]		**Calories per ounce [[User:JohnLeMasney\| John LeMasney]]
	*Background Information - Optional section to encapsulate information that is useful but not necessarily required for a successful recipe. [[User:AlexanderShusta\|α]]		*Background Information - Optional section to encapsulate information that is useful but not necessarily required for a successful recipe. [[User:AlexanderShusta\|Î±]]
	**Author (Person) ([[hcard]]?)		**Author (Person) ([[hcard]]?)
	**Submitter (Person) ([[hcard]]?)		**Submitter (Person) ([[hcard]]?)
Line 196:		Line 197:
	**Steps (optional)		**Steps (optional)
	***Should be an ordered list [[User:AndyMabbett\|Andy Mabbett]] 14:46, 16 Nov 2006 (PST)		***Should be an ordered list [[User:AndyMabbett\|Andy Mabbett]] 14:46, 16 Nov 2006 (PST)
	***Another vote for an ordered list, perhaps in the [[XOXO]] format. [[User:AlexanderShusta\|α]]		***Another vote for an ordered list, perhaps in the [[XOXO]] format. [[User:AlexanderShusta\|Î±]]
	***Many recipes associate ingredients with specific steps of a multi-step method; if methods are broken out into steps, then the format should support this association whether the complete ingredient list is up front or the ingredient list is itself broken out per step. [[User:Quixote\|Ben Curtis]]		***Many recipes associate ingredients with specific steps of a multi-step method; if methods are broken out into steps, then the format should support this association whether the complete ingredient list is up front or the ingredient list is itself broken out per step. [[User:Quixote\|Ben Curtis]]
	*Photo (optional) [[User:IamCam\|Cameron Perry]]		*Photo (optional) [[User:IamCam\|Cameron Perry]]
Line 214:		Line 215:
	*Suitability (e.g. vegetarian, vegan, wheat-free, etc.). Possibly [[rel-tag]]. [[User:AndyMabbett\|Andy Mabbett]] 14:57, 16 Nov 2006 (PST)		*Suitability (e.g. vegetarian, vegan, wheat-free, etc.). Possibly [[rel-tag]]. [[User:AndyMabbett\|Andy Mabbett]] 14:57, 16 Nov 2006 (PST)
	*Ingredient Grouping - In baking you need to differentiate wet from dry ingredients. See also an [[recipe-examples\|example recipe]] from [http://www.extratasty.com/recipe/46/cuba_libre extratasty.com] for useful grouping in cocktail mixing. [[SteveL\|Steve Lewis]] 19:10, 11 Feb 2007		*Ingredient Grouping - In baking you need to differentiate wet from dry ingredients. See also an [[recipe-examples\|example recipe]] from [http://www.extratasty.com/recipe/46/cuba_libre extratasty.com] for useful grouping in cocktail mixing. [[SteveL\|Steve Lewis]] 19:10, 11 Feb 2007
	** Maybe this ingredient grouping can be used to express some alternative ingredients, like "mayonnaise or cream cheese". [[EstevaoSamuel\|~~Estêvão~~ Samuel ~~Procópio~~]] 15:33, 16 Dez 2007 (PDT)		** Maybe this ingredient grouping can be used to express some alternative ingredients, like "mayonnaise or cream cheese". [[EstevaoSamuel\|EstÃªvÃ£o Samuel ProcÃ³pio]] 15:33, 16 Dez 2007 (PDT)
	** This could be solved by using a xoxo list and ignoring list items that don't include a class="name". Example:<pre><nowiki>		** This could be solved by using a xoxo list and ignoring list items that don't include a class="name". Example:<pre><nowiki>
	<ul class="ingredients">		<ul class="ingredients">

ThomasLoertsch: /* related pages */ added recipe-feedback, modified hrecipe2rdf

2008-12-09T14:40:03Z

related pages: added recipe-feedback, modified hrecipe2rdf

← Older revision		Revision as of 14:40, 9 December 2008
Line 327:		Line 327:
	== related pages ==		== related pages ==
	* [[recipe]]		* [[recipe]]
			* [[recipe-feedback]]
	* [[recipe-examples]]		* [[recipe-examples]]
	* [[recipe-brainstorming-archive]]		* [[recipe-brainstorming-archive]]
	* [[recipe-formats]]		* [[recipe-formats]]
	* [[recipe-issues]]		* [[recipe-issues]]
	* [[~~recipe2rdf~~]]		* [[recipe-hrecipe2rdf]]

← Older revision		Revision as of 20:11, 29 December 2008
Line 180:		Line 180:
	**Some (e.g. meats, vegetables) could optionally be marked up with (elements of) the proposed [[species]] microformat. [[User:AndyMabbett\|Andy Mabbett]] 06:41, 16 Nov 2006 (PST)		**Some (e.g. meats, vegetables) could optionally be marked up with (elements of) the proposed [[species]] microformat. [[User:AndyMabbett\|Andy Mabbett]] 06:41, 16 Nov 2006 (PST)
	*** None of the [[recipe-examples]] show references to species names, therefore there is no empirical justification for inclusion of such detail in the microformat. [[User:Tantek\|Tantek]] 23:19, 27 December 2008 (UTC)		*** None of the [[recipe-examples]] show references to species names, therefore there is no empirical justification for inclusion of such detail in the microformat. [[User:Tantek\|Tantek]] 23:19, 27 December 2008 (UTC)
			**** The vast majority of recipes reference a species of plant or animal (e.g. "chicken", "carrot"). Binomial/trinomial names are pretty much never seen of course, but the current species proposal allows for vernacular (common) names to be marked up, so it is not an especially odd suggestion to define a pattern for marking up species within ingredients. [[User:TobyInk\|TobyInk]] 20:11, 29 December 2008 (UTC)
	** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta\|α]]		** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta\|α]]
	**Units need separate microformat: see [[measure]]		**Units need separate microformat: see [[measure]]