https://microformats.org/wiki/api.php?action=feedcontributions&user=SudarshanP&feedformat=atomMicroformats Wiki - User contributions [en]2024-03-29T02:33:34ZUser contributionsMediaWiki 1.38.4https://microformats.org/wiki/index.php?title=recipe-formats&diff=20103recipe-formats2007-07-15T21:25:36Z<p>SudarshanP: </p>
<hr />
<div>== MealMaster ==<br />
<br />
[http://home.comcast.net/~episoft/ MealMaster]<br />
<br />
==Recipe Markup Language==<br />
It was (formerly known as DESSERT -- Document Encoding and Structuring Specification for Electronic Recipe Transfer) is an [[XML]]-based format for marking up [[recipe]]s. The format was created in [[2000]] by the company FormatData.<br />
<br />
[http://www.formatdata.com/recipeml/spec/recipeml-spec.html Specification]<br />
<br />
The format provides detailed markup for defining ingredients, which facilitates automated conversions from one type of [[unit of measurement|measurement]] to another. The markup language also provides for step-based instructions. [[Metadata]] can be added to a RecipeML document through the [[Dublin Core]].<br />
<br />
There are some software programs that read and write the RecipeML format. The most notable of these is [http://www.recipewebservice.com/largorecipes/ Largo Recipes]. The RecipeML [http://www.formatdata.com/recipeml/license.html license] is fairly open.<br />
<br />
[http://dsquirrel.tripod.com/recipeml/indexrecipes2.html This archive] contains 10,000 recipes in Recipe Markup Language<br />
<br />
== RxOL ==<br />
[http://www.anthus.com/Recipes/CompCook.html RxOL] uses a postfix notation to represent recipes.<br />
<br />
On the website [http://www.cookingforengineers.com/recipe/26/Simple-Tiramisu Cooking For Engineers] you can see a beautiful graphical representation of a recipe tree which could be constructed from the RxOL tree or one could easily code the Microformat in the form of the tree mentioned in that site. You need to scroll down to the bottom of the main article just above the comments section.<br />
<br />
== REML: The Recipe Exchange Markup Language ==<br />
[http://reml.sourceforge.net/ REML on Sourceforge]<br />
<br />
REML is an XML schema that describes a file format for recipe exchange. <br />
On the sourceforge page Gary says:<br />
I might have developed against an existing markup languages, but RecipeML is mired in licensing problems, and CookML is written in German. And I had my own ideas about recipe exchange that could better support commercial uses, such as the development of restaurant menus and cookbooks. In any case, this is a viable XML-based format for exchanging food recipes, developed from scratch by Gary Gocek. If you have suggestions, please contact Gary.<br />
<br />
==RecipeBook XML==<br />
From [http://www.happy-monkey.net/recipebook/ RecipeBook XML]<br />
RecipeBook XML is a markup language used to write recipes and cookbooks. It is simple and easy to learn, but offers some powerful features. Once a recipe is written in RecipeBook XML it can be reproduced in HTML, PDF, Rich Text formats all from the same source document.<br />
<br />
The primary goal of RecipeBook XML is to allow people to create, store and share recipes in a variety of electronic formats. Consideration is also given to computer manipulation of the data contained within the recipes. More details are given below. Uses creative common's licence<br />
<br />
== Eat Drink Feel Good Markup Language ==<br />
<br />
Here is an [http://www.xml.com/pub/a/2005/02/16/edfg.html XML.com] article. See also [http://ptsefton.com/blog/2004/06/02/recipe_schema]<br />
<br />
== MasterCook format ==<br />
Text format: [http://fp.enter.net/~rburk/pastries/doughnuts/appleorc.txt Example]<br />
See Also: <br />
*[http://fp.enter.net/~rburk/ MasterCook Recipies]<br />
*[http://www.valusoft.com/products/mastercook.html Software]<br />
*[http://www.geocities.com/napavalley/2267/mastercook.html Recipies]<br />
*[http://www.grassrootsrecipes.com/ Recipies]</div>SudarshanPhttps://microformats.org/wiki/index.php?title=recipe-formats&diff=18413recipe-formats2007-07-15T21:11:59Z<p>SudarshanP: /* RxOL */</p>
<hr />
<div>==Recipe Markup Language==<br />
It was (formerly known as DESSERT -- Document Encoding and Structuring Specification for Electronic Recipe Transfer) is an [[XML]]-based format for marking up [[recipe]]s. The format was created in [[2000]] by the company FormatData.<br />
<br />
[http://www.formatdata.com/recipeml/spec/recipeml-spec.html Specification]<br />
<br />
The format provides detailed markup for defining ingredients, which facilitates automated conversions from one type of [[unit of measurement|measurement]] to another. The markup language also provides for step-based instructions. [[Metadata]] can be added to a RecipeML document through the [[Dublin Core]].<br />
<br />
There are some software programs that read and write the RecipeML format. The most notable of these is [http://www.recipewebservice.com/largorecipes/ Largo Recipes]. The RecipeML [http://www.formatdata.com/recipeml/license.html license] is fairly open.<br />
<br />
[http://dsquirrel.tripod.com/recipeml/indexrecipes2.html This archive] contains 10,000 recipes in Recipe Markup Language<br />
<br />
== RxOL ==<br />
[http://www.anthus.com/Recipes/CompCook.html RxOL] uses a postfix notation to represent recipes.<br />
<br />
On the website [http://www.cookingforengineers.com/recipe/26/Simple-Tiramisu Cooking For Engineers] you can see a beautiful graphical representation of a recipe tree which could be constructed from the RxOL tree or one could easily code the Microformat in the form of the tree mentioned in that site. You need to scroll down to the bottom of the main article just above the comments section.<br />
<br />
== REML: The Recipe Exchange Markup Language ==<br />
[http://reml.sourceforge.net/ REML on Sourceforge]<br />
<br />
REML is an XML schema that describes a file format for recipe exchange. <br />
On the sourceforge page Gary says:<br />
I might have developed against an existing markup languages, but RecipeML is mired in licensing problems, and CookML is written in German. And I had my own ideas about recipe exchange that could better support commercial uses, such as the development of restaurant menus and cookbooks. In any case, this is a viable XML-based format for exchanging food recipes, developed from scratch by Gary Gocek. If you have suggestions, please contact Gary.<br />
<br />
==RecipeBook XML==<br />
From [http://www.happy-monkey.net/recipebook/ RecipeBook XML]<br />
RecipeBook XML is a markup language used to write recipes and cookbooks. It is simple and easy to learn, but offers some powerful features. Once a recipe is written in RecipeBook XML it can be reproduced in HTML, PDF, Rich Text formats all from the same source document.<br />
<br />
The primary goal of RecipeBook XML is to allow people to create, store and share recipes in a variety of electronic formats. Consideration is also given to computer manipulation of the data contained within the recipes. More details are given below. Uses creative common's licence<br />
<br />
== Eat Drink Feel Good Markup Language ==<br />
<br />
Here is an [http://www.xml.com/pub/a/2005/02/16/edfg.html XML.com] article. See also [http://ptsefton.com/blog/2004/06/02/recipe_schema]<br />
<br />
== MasterCook format ==<br />
Text format: [http://fp.enter.net/~rburk/pastries/doughnuts/appleorc.txt Example]<br />
See Also: <br />
*[http://fp.enter.net/~rburk/ MasterCook Recipies]<br />
*[http://www.valusoft.com/products/mastercook.html Software]<br />
*[http://www.geocities.com/napavalley/2267/mastercook.html Recipies]<br />
*[http://www.grassrootsrecipes.com/ Recipies]</div>SudarshanPhttps://microformats.org/wiki/index.php?title=recipe-formats&diff=18412recipe-formats2007-07-15T21:10:45Z<p>SudarshanP: /* Eat Drink Feel Good Markup Language */</p>
<hr />
<div>==Recipe Markup Language==<br />
It was (formerly known as DESSERT -- Document Encoding and Structuring Specification for Electronic Recipe Transfer) is an [[XML]]-based format for marking up [[recipe]]s. The format was created in [[2000]] by the company FormatData.<br />
<br />
[http://www.formatdata.com/recipeml/spec/recipeml-spec.html Specification]<br />
<br />
The format provides detailed markup for defining ingredients, which facilitates automated conversions from one type of [[unit of measurement|measurement]] to another. The markup language also provides for step-based instructions. [[Metadata]] can be added to a RecipeML document through the [[Dublin Core]].<br />
<br />
There are some software programs that read and write the RecipeML format. The most notable of these is [http://www.recipewebservice.com/largorecipes/ Largo Recipes]. The RecipeML [http://www.formatdata.com/recipeml/license.html license] is fairly open.<br />
<br />
[http://dsquirrel.tripod.com/recipeml/indexrecipes2.html This archive] contains 10,000 recipes in Recipe Markup Language<br />
<br />
== RxOL ==<br />
[http://www.anthus.com/Recipes/CompCook.html RxOL] uses a postfix notation to represent recipes.<br />
<br />
On the website [http://www.cookingforengineers.com/recipe/26/Simple-Tiramisu Cooking For Engineers] you can see a beautiful graphical representation of a recipe tree which could be constructed from the RxOL tree or one could easily code the Microformat in the form of the tree mentioned in that site.<br />
<br />
== REML: The Recipe Exchange Markup Language ==<br />
[http://reml.sourceforge.net/ REML on Sourceforge]<br />
<br />
REML is an XML schema that describes a file format for recipe exchange. <br />
On the sourceforge page Gary says:<br />
I might have developed against an existing markup languages, but RecipeML is mired in licensing problems, and CookML is written in German. And I had my own ideas about recipe exchange that could better support commercial uses, such as the development of restaurant menus and cookbooks. In any case, this is a viable XML-based format for exchanging food recipes, developed from scratch by Gary Gocek. If you have suggestions, please contact Gary.<br />
<br />
==RecipeBook XML==<br />
From [http://www.happy-monkey.net/recipebook/ RecipeBook XML]<br />
RecipeBook XML is a markup language used to write recipes and cookbooks. It is simple and easy to learn, but offers some powerful features. Once a recipe is written in RecipeBook XML it can be reproduced in HTML, PDF, Rich Text formats all from the same source document.<br />
<br />
The primary goal of RecipeBook XML is to allow people to create, store and share recipes in a variety of electronic formats. Consideration is also given to computer manipulation of the data contained within the recipes. More details are given below. Uses creative common's licence<br />
<br />
== Eat Drink Feel Good Markup Language ==<br />
<br />
Here is an [http://www.xml.com/pub/a/2005/02/16/edfg.html XML.com] article. See also [http://ptsefton.com/blog/2004/06/02/recipe_schema]<br />
<br />
== MasterCook format ==<br />
Text format: [http://fp.enter.net/~rburk/pastries/doughnuts/appleorc.txt Example]<br />
See Also: <br />
*[http://fp.enter.net/~rburk/ MasterCook Recipies]<br />
*[http://www.valusoft.com/products/mastercook.html Software]<br />
*[http://www.geocities.com/napavalley/2267/mastercook.html Recipies]<br />
*[http://www.grassrootsrecipes.com/ Recipies]</div>SudarshanPhttps://microformats.org/wiki/index.php?title=recipe-formats&diff=18411recipe-formats2007-07-15T20:58:28Z<p>SudarshanP: /* RxOL */</p>
<hr />
<div>==Recipe Markup Language==<br />
It was (formerly known as DESSERT -- Document Encoding and Structuring Specification for Electronic Recipe Transfer) is an [[XML]]-based format for marking up [[recipe]]s. The format was created in [[2000]] by the company FormatData.<br />
<br />
[http://www.formatdata.com/recipeml/spec/recipeml-spec.html Specification]<br />
<br />
The format provides detailed markup for defining ingredients, which facilitates automated conversions from one type of [[unit of measurement|measurement]] to another. The markup language also provides for step-based instructions. [[Metadata]] can be added to a RecipeML document through the [[Dublin Core]].<br />
<br />
There are some software programs that read and write the RecipeML format. The most notable of these is [http://www.recipewebservice.com/largorecipes/ Largo Recipes]. The RecipeML [http://www.formatdata.com/recipeml/license.html license] is fairly open.<br />
<br />
[http://dsquirrel.tripod.com/recipeml/indexrecipes2.html This archive] contains 10,000 recipes in Recipe Markup Language<br />
<br />
== RxOL ==<br />
[http://www.anthus.com/Recipes/CompCook.html RxOL] uses a postfix notation to represent recipes.<br />
<br />
On the website [http://www.cookingforengineers.com/recipe/26/Simple-Tiramisu Cooking For Engineers] you can see a beautiful graphical representation of a recipe tree which could be constructed from the RxOL tree or one could easily code the Microformat in the form of the tree mentioned in that site.<br />
<br />
== REML: The Recipe Exchange Markup Language ==<br />
[http://reml.sourceforge.net/ REML on Sourceforge]<br />
<br />
REML is an XML schema that describes a file format for recipe exchange. <br />
On the sourceforge page Gary says:<br />
I might have developed against an existing markup languages, but RecipeML is mired in licensing problems, and CookML is written in German. And I had my own ideas about recipe exchange that could better support commercial uses, such as the development of restaurant menus and cookbooks. In any case, this is a viable XML-based format for exchanging food recipes, developed from scratch by Gary Gocek. If you have suggestions, please contact Gary.<br />
<br />
==RecipeBook XML==<br />
From [http://www.happy-monkey.net/recipebook/ RecipeBook XML]<br />
RecipeBook XML is a markup language used to write recipes and cookbooks. It is simple and easy to learn, but offers some powerful features. Once a recipe is written in RecipeBook XML it can be reproduced in HTML, PDF, Rich Text formats all from the same source document.<br />
<br />
The primary goal of RecipeBook XML is to allow people to create, store and share recipes in a variety of electronic formats. Consideration is also given to computer manipulation of the data contained within the recipes. More details are given below. Uses creative common's licence<br />
<br />
== Eat Drink Feel Good Markup Language ==<br />
<br />
Here is an [http://www.xml.com/pub/a/2005/02/16/edfg.html XML.com] article. See also [http://ptsefton.com/blog/2004/06/02/recipe_schema]</div>SudarshanPhttps://microformats.org/wiki/index.php?title=recipe-formats&diff=18410recipe-formats2007-07-15T20:42:26Z<p>SudarshanP: </p>
<hr />
<div>==Recipe Markup Language==<br />
It was (formerly known as DESSERT -- Document Encoding and Structuring Specification for Electronic Recipe Transfer) is an [[XML]]-based format for marking up [[recipe]]s. The format was created in [[2000]] by the company FormatData.<br />
<br />
[http://www.formatdata.com/recipeml/spec/recipeml-spec.html Specification]<br />
<br />
The format provides detailed markup for defining ingredients, which facilitates automated conversions from one type of [[unit of measurement|measurement]] to another. The markup language also provides for step-based instructions. [[Metadata]] can be added to a RecipeML document through the [[Dublin Core]].<br />
<br />
There are some software programs that read and write the RecipeML format. The most notable of these is [http://www.recipewebservice.com/largorecipes/ Largo Recipes]. The RecipeML [http://www.formatdata.com/recipeml/license.html license] is fairly open.<br />
<br />
[http://dsquirrel.tripod.com/recipeml/indexrecipes2.html This archive] contains 10,000 recipes in Recipe Markup Language<br />
<br />
== RxOL ==<br />
[http://www.anthus.com/Recipes/CompCook.html RxOL] uses a postfix notation to represent recipes.<br />
<br />
== REML: The Recipe Exchange Markup Language ==<br />
[http://reml.sourceforge.net/ REML on Sourceforge]<br />
<br />
REML is an XML schema that describes a file format for recipe exchange. <br />
On the sourceforge page Gary says:<br />
I might have developed against an existing markup languages, but RecipeML is mired in licensing problems, and CookML is written in German. And I had my own ideas about recipe exchange that could better support commercial uses, such as the development of restaurant menus and cookbooks. In any case, this is a viable XML-based format for exchanging food recipes, developed from scratch by Gary Gocek. If you have suggestions, please contact Gary.<br />
<br />
==RecipeBook XML==<br />
From [http://www.happy-monkey.net/recipebook/ RecipeBook XML]<br />
RecipeBook XML is a markup language used to write recipes and cookbooks. It is simple and easy to learn, but offers some powerful features. Once a recipe is written in RecipeBook XML it can be reproduced in HTML, PDF, Rich Text formats all from the same source document.<br />
<br />
The primary goal of RecipeBook XML is to allow people to create, store and share recipes in a variety of electronic formats. Consideration is also given to computer manipulation of the data contained within the recipes. More details are given below. Uses creative common's licence<br />
<br />
== Eat Drink Feel Good Markup Language ==<br />
<br />
Here is an [http://www.xml.com/pub/a/2005/02/16/edfg.html XML.com] article. See also [http://ptsefton.com/blog/2004/06/02/recipe_schema]</div>SudarshanPhttps://microformats.org/wiki/index.php?title=recipe-formats&diff=18409recipe-formats2007-07-15T20:41:20Z<p>SudarshanP: /* RecipeBook XML */</p>
<hr />
<div>==Recipe Markup Language==<br />
It was (formerly known as DESSERT -- Document Encoding and Structuring Specification for Electronic Recipe Transfer) is an [[XML]]-based format for marking up [[recipe]]s. The format was created in [[2000]] by the company FormatData.<br />
<br />
[http://www.formatdata.com/recipeml/spec/recipeml-spec.html Specification]<br />
<br />
The format provides detailed markup for defining ingredients, which facilitates automated conversions from one type of [[unit of measurement|measurement]] to another. The markup language also provides for step-based instructions. [[Metadata]] can be added to a RecipeML document through the [[Dublin Core]].<br />
<br />
There are some software programs that read and write the RecipeML format. The most notable of these is [http://www.recipewebservice.com/largorecipes/ Largo Recipes]. The RecipeML [http://www.formatdata.com/recipeml/license.html license] is fairly open.<br />
<br />
[http://dsquirrel.tripod.com/recipeml/indexrecipes2.html This archive] contains 10,000 recipes in Recipe Markup Language<br />
<br />
== RxOL ==<br />
[http://www.anthus.com/Recipes/CompCook.html RxOL] uses a postfix notation to represent recipes.<br />
<br />
== REML: The Recipe Exchange Markup Language ==<br />
[http://reml.sourceforge.net/ REML on Sourceforge]<br />
<br />
REML is an XML schema that describes a file format for recipe exchange. <br />
On the sourceforge page Gary says:<br />
I might have developed against an existing markup languages, but RecipeML is mired in licensing problems, and CookML is written in German. And I had my own ideas about recipe exchange that could better support commercial uses, such as the development of restaurant menus and cookbooks. In any case, this is a viable XML-based format for exchanging food recipes, developed from scratch by Gary Gocek. If you have suggestions, please contact Gary.<br />
<br />
==RecipeBook XML==<br />
From [http://www.happy-monkey.net/recipebook/ RecipeBook XML]<br />
RecipeBook XML is a markup language used to write recipes and cookbooks. It is simple and easy to learn, but offers some powerful features. Once a recipe is written in RecipeBook XML it can be reproduced in HTML, PDF, Rich Text formats all from the same source document.<br />
<br />
The primary goal of RecipeBook XML is to allow people to create, store and share recipes in a variety of electronic formats. Consideration is also given to computer manipulation of the data contained within the recipes. More details are given below. Uses creative common's licence<br />
<br />
== Eat Drink Feel Good Markup Language ==<br />
<br />
Here is an [http://www.xml.com/pub/a/2005/02/16/edfg.html XML.com] article.<br />
<br />
==Misc==<br />
[http://ptsefton.com/blog/2004/06/02/recipe_schema]</div>SudarshanPhttps://microformats.org/wiki/index.php?title=recipe-formats&diff=18408recipe-formats2007-07-15T20:27:25Z<p>SudarshanP: </p>
<hr />
<div>==Recipe Markup Language==<br />
It was (formerly known as DESSERT -- Document Encoding and Structuring Specification for Electronic Recipe Transfer) is an [[XML]]-based format for marking up [[recipe]]s. The format was created in [[2000]] by the company FormatData.<br />
<br />
[http://www.formatdata.com/recipeml/spec/recipeml-spec.html Specification]<br />
<br />
The format provides detailed markup for defining ingredients, which facilitates automated conversions from one type of [[unit of measurement|measurement]] to another. The markup language also provides for step-based instructions. [[Metadata]] can be added to a RecipeML document through the [[Dublin Core]].<br />
<br />
There are some software programs that read and write the RecipeML format. The most notable of these is [http://www.recipewebservice.com/largorecipes/ Largo Recipes]. The RecipeML [http://www.formatdata.com/recipeml/license.html license] is fairly open.<br />
<br />
[http://dsquirrel.tripod.com/recipeml/indexrecipes2.html This archive] contains 10,000 recipes in Recipe Markup Language<br />
<br />
== RxOL ==<br />
[http://www.anthus.com/Recipes/CompCook.html RxOL] uses a postfix notation to represent recipes.<br />
<br />
== REML: The Recipe Exchange Markup Language ==<br />
[http://reml.sourceforge.net/ REML on Sourceforge]<br />
<br />
REML is an XML schema that describes a file format for recipe exchange. <br />
On the sourceforge page Gary says:<br />
I might have developed against an existing markup languages, but RecipeML is mired in licensing problems, and CookML is written in German. And I had my own ideas about recipe exchange that could better support commercial uses, such as the development of restaurant menus and cookbooks. In any case, this is a viable XML-based format for exchanging food recipes, developed from scratch by Gary Gocek. If you have suggestions, please contact Gary.<br />
<br />
==RecipeBook XML==<br />
From [http://www.happy-monkey.net/recipebook/ RecipeBook XML]<br />
RecipeBook XML is a markup language used to write recipes and cookbooks. It is simple and easy to learn, but offers some powerful features. Once a recipe is written in RecipeBook XML it can be reproduced in HTML, PDF, Rich Text formats all from the same source document.<br />
<br />
The primary goal of RecipeBook XML is to allow people to create, store and share recipes in a variety of electronic formats. Consideration is also given to computer manipulation of the data contained within the recipes. More details are given below. Uses creative common's licence<br />
<br />
==Misc==<br />
[http://ptsefton.com/blog/2004/06/02/recipe_schema]</div>SudarshanPhttps://microformats.org/wiki/index.php?title=recipe-formats&diff=18407recipe-formats2007-07-15T20:27:03Z<p>SudarshanP: /* REML: The Recipe Exchange Markup Language */</p>
<hr />
<div>One of the available recipe formats is the recipe markup language<br />
<br />
==Recipe Markup Language==<br />
It was (formerly known as DESSERT -- Document Encoding and Structuring Specification for Electronic Recipe Transfer) is an [[XML]]-based format for marking up [[recipe]]s. The format was created in [[2000]] by the company FormatData.<br />
<br />
[http://www.formatdata.com/recipeml/spec/recipeml-spec.html Specification]<br />
<br />
The format provides detailed markup for defining ingredients, which facilitates automated conversions from one type of [[unit of measurement|measurement]] to another. The markup language also provides for step-based instructions. [[Metadata]] can be added to a RecipeML document through the [[Dublin Core]].<br />
<br />
There are some software programs that read and write the RecipeML format. The most notable of these is [http://www.recipewebservice.com/largorecipes/ Largo Recipes]. The RecipeML [http://www.formatdata.com/recipeml/license.html license] is fairly open.<br />
<br />
[http://dsquirrel.tripod.com/recipeml/indexrecipes2.html This archive] contains 10,000 recipes in Recipe Markup Language<br />
<br />
== RxOL ==<br />
[http://www.anthus.com/Recipes/CompCook.html RxOL] uses a postfix notation to represent recipes.<br />
<br />
== REML: The Recipe Exchange Markup Language ==<br />
[http://reml.sourceforge.net/ REML on Sourceforge]<br />
<br />
REML is an XML schema that describes a file format for recipe exchange. <br />
On the sourceforge page Gary says:<br />
I might have developed against an existing markup languages, but RecipeML is mired in licensing problems, and CookML is written in German. And I had my own ideas about recipe exchange that could better support commercial uses, such as the development of restaurant menus and cookbooks. In any case, this is a viable XML-based format for exchanging food recipes, developed from scratch by Gary Gocek. If you have suggestions, please contact Gary.<br />
<br />
==RecipeBook XML==<br />
From [http://www.happy-monkey.net/recipebook/ RecipeBook XML]<br />
RecipeBook XML is a markup language used to write recipes and cookbooks. It is simple and easy to learn, but offers some powerful features. Once a recipe is written in RecipeBook XML it can be reproduced in HTML, PDF, Rich Text formats all from the same source document.<br />
<br />
The primary goal of RecipeBook XML is to allow people to create, store and share recipes in a variety of electronic formats. Consideration is also given to computer manipulation of the data contained within the recipes. More details are given below. Uses creative common's licence<br />
<br />
==Misc==<br />
[http://ptsefton.com/blog/2004/06/02/recipe_schema]</div>SudarshanPhttps://microformats.org/wiki/index.php?title=recipe-formats&diff=18406recipe-formats2007-07-15T20:19:00Z<p>SudarshanP: </p>
<hr />
<div>One of the available recipe formats is the recipe markup language<br />
<br />
==Recipe Markup Language==<br />
It was (formerly known as DESSERT -- Document Encoding and Structuring Specification for Electronic Recipe Transfer) is an [[XML]]-based format for marking up [[recipe]]s. The format was created in [[2000]] by the company FormatData.<br />
<br />
[http://www.formatdata.com/recipeml/spec/recipeml-spec.html Specification]<br />
<br />
The format provides detailed markup for defining ingredients, which facilitates automated conversions from one type of [[unit of measurement|measurement]] to another. The markup language also provides for step-based instructions. [[Metadata]] can be added to a RecipeML document through the [[Dublin Core]].<br />
<br />
There are some software programs that read and write the RecipeML format. The most notable of these is [http://www.recipewebservice.com/largorecipes/ Largo Recipes]. The RecipeML [http://www.formatdata.com/recipeml/license.html license] is fairly open.<br />
<br />
[http://dsquirrel.tripod.com/recipeml/indexrecipes2.html This archive] contains 10,000 recipes in Recipe Markup Language<br />
<br />
== RxOL ==<br />
[http://www.anthus.com/Recipes/CompCook.html RxOL] uses a postfix notation to represent recipes.<br />
<br />
== REML: The Recipe Exchange Markup Language ==<br />
[http://reml.sourceforge.net/ REML on Sourceforge]<br />
<br />
REML is an XML schema that describes a file format for recipe exchange. <br />
On the sourceforge page Gary says:<br />
I might have developed against an existing markup languages, but RecipeML is mired in licensing problems, and CookML is written in German. And I had my own ideas about recipe exchange that could better support commercial uses, such as the development of restaurant menus and cookbooks. In any case, this is a viable XML-based format for exchanging food recipes, developed from scratch by Gary Gocek. If you have suggestions, please contact Gary.</div>SudarshanPhttps://microformats.org/wiki/index.php?title=recipe-formats&diff=18405recipe-formats2007-07-15T20:09:52Z<p>SudarshanP: </p>
<hr />
<div>One of the available recipe formats is the recipe markup language<br />
<br />
==Recipe Markup Language==<br />
It was (formerly known as DESSERT -- Document Encoding and Structuring Specification for Electronic Recipe Transfer) is an [[XML]]-based format for marking up [[recipe]]s. The format was created in [[2000]] by the company FormatData.<br />
<br />
[http://www.formatdata.com/recipeml/spec/recipeml-spec.html Specification]<br />
<br />
The format provides detailed markup for defining ingredients, which facilitates automated conversions from one type of [[unit of measurement|measurement]] to another. The markup language also provides for step-based instructions. [[Metadata]] can be added to a RecipeML document through the [[Dublin Core]].<br />
<br />
There are some software programs that read and write the RecipeML format. The most notable of these is [http://www.recipewebservice.com/largorecipes/ Largo Recipes]. The RecipeML [http://www.formatdata.com/recipeml/license.html license] is fairly open.<br />
<br />
[http://dsquirrel.tripod.com/recipeml/indexrecipes2.html This archive] contains 10,000 recipes in Recipe Markup Language<br />
<br />
== RxOL ==<br />
[http://www.anthus.com/Recipes/CompCook.html RxOL] uses a postfix notation to represent recipes.</div>SudarshanPhttps://microformats.org/wiki/index.php?title=recipe-formats&diff=18404recipe-formats2007-07-15T20:06:18Z<p>SudarshanP: </p>
<hr />
<div>One of the available recipie formats is the recipie markup language<br />
<br />
==Recipe Markup Language==<br />
It was (formerly known as DESSERT -- Document Encoding and Structuring Specification for Electronic Recipe Transfer) is an [[XML]]-based format for marking up [[recipe]]s. The format was created in [[2000]] by the company FormatData.<br />
<br />
[http://www.formatdata.com/recipeml/spec/recipeml-spec.html Specification]<br />
<br />
The format provides detailed markup for defining ingredients, which facilitates automated conversions from one type of [[unit of measurement|measurement]] to another. The markup language also provides for step-based instructions. [[Metadata]] can be added to a RecipeML document through the [[Dublin Core]].<br />
<br />
There are some software programs that read and write the RecipeML format. The most notable of these is [http://www.recipewebservice.com/largorecipes/ Largo Recipes]. The RecipeML [http://www.formatdata.com/recipeml/license.html license] is fairly open.<br />
<br />
== RxOL ==<br />
[http://www.anthus.com/Recipes/CompCook.html RxOL] uses a postfix notation to represent Recipies.</div>SudarshanPhttps://microformats.org/wiki/index.php?title=recipe-formats&diff=18403recipe-formats2007-07-15T20:00:32Z<p>SudarshanP: </p>
<hr />
<div>One of the available recipie formats is the recipie markup language<br />
<br />
'''Recipe Markup Language''' (formerly known as DESSERT -- Document Encoding and Structuring Specification for Electronic Recipe Transfer) is an [[XML]]-based format for marking up [[recipe]]s. The format was created in [[2000]] by the company FormatData.<br />
<br />
[http://www.formatdata.com/recipeml/spec/recipeml-spec.html Specification]<br />
<br />
The format provides detailed markup for defining ingredients, which facilitates automated conversions from one type of [[unit of measurement|measurement]] to another. The markup language also provides for step-based instructions. [[Metadata]] can be added to a RecipeML document through the [[Dublin Core]].<br />
<br />
There are some software programs that read and write the RecipeML format. The most notable of these is [http://www.recipewebservice.com/largorecipes/ Largo Recipes]. The RecipeML [http://www.formatdata.com/recipeml/license.html license] is fairly open.</div>SudarshanPhttps://microformats.org/wiki/index.php?title=recipe-formats&diff=18402recipe-formats2007-07-15T19:56:01Z<p>SudarshanP: </p>
<hr />
<div>'''Recipe Markup Language''' (formerly known as DESSERT -- Document Encoding and Structuring Specification for Electronic Recipe Transfer) is an [[XML]]-based format for marking up [[recipe]]s. The format was created in [[2000]] by the company FormatData.<br />
<br />
The format provides detailed markup for defining ingredients, which facilitates automated conversions from one type of [[unit of measurement|measurement]] to another. The markup language also provides for step-based instructions. [[Metadata]] can be added to a RecipeML document through the [[Dublin Core]].<br />
<br />
There are some software programs that read and write the RecipeML format. The most notable of these is [http://www.recipewebservice.com/largorecipes/ Largo Recipes]. The RecipeML [http://www.formatdata.com/recipeml/license.html license] is fairly open.</div>SudarshanPhttps://microformats.org/wiki/index.php?title=recipe-brainstorming&diff=18214recipe-brainstorming2007-06-26T13:46:19Z<p>SudarshanP: /* Issues */</p>
<hr />
<div>= recipe brainstorming =<br />
<br />
Towards a [[recipe]] microformat. Please read [[process]] before editing this page.<br />
<br />
This page is currently a rough draft formed after surveying the [[recipe-examples]] and other related formats such as RecipeML and existing microformats. '''RecipeML MUST be documented in [[recipe-formats]], otherwise the reference is meaningless.'''<br />
<br />
'''This page is currently premature, as there first needs to be a [[recipe-formats]] page where pre-existing recipe formats are documented (e.g. RecipeML), BEFORE brainstorming, per the [[process]]'''<br />
<br />
==Suggested fields for inclusion==<br />
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:<br />
*Recipe_Title<br />
*Summary Description (one liner)<br />
*Measurement System (U.S., Imperial etc)<br />
*Ingredients (each one a separate "item" rather than block text with count/amount/range/unit broken out too)<br />
**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)<br />
** Ingredient importance (e.g. Main, Required, Optional) should be listed as an attribute of each entry. [[User:AlexanderShusta|α]]<br />
**Units need separate microformat: see [[measure]] <br />
**Ingredient Preparation: such as diced, chopped, sliced, grated, minced, etc. [[User:SteveL|Steve Lewis]] 18:55, 11 Feb 2007 (PST)<br />
*Preparation Time (overall time)<br />
*Yield Quantity and Unit (4 pancakes or 5 servings)<br />
**Calories per serving [[User:JohnLeMasney| John LeMasney]]<br />
**Calories per ounce [[User:JohnLeMasney| John LeMasney]] <br />
*Background Information - Optional section to encapsulate information that is useful but not necessarily required for a successful recipe. [[User:AlexanderShusta|α]]<br />
**Author (Person) ([[hcard]]?)<br />
**Submitter (Person) ([[hcard]]?)<br />
**Source (Book Title etc)<br />
*** could use the proposed [[citation]] microformat. [[User:AndyMabbett|Andy Mabbett]] 06:43, 16 Nov 2006 (PST)<br />
**Date (Of Creation or Publication)<br />
**Rights (Copyright or other)<br />
**Meal Category (Starter, entree, dessert )<br />
**Cuisine Category (Italian etc)<br />
*Instructions (text, but can contain:)<br />
**Steps (optional)<br />
***Should be an ordered list [[User:AndyMabbett|Andy Mabbett]] 14:46, 16 Nov 2006 (PST)<br />
***Another vote for an ordered list, perhaps in the [[XOXO]] format. [[User:AlexanderShusta|α]]<br />
*Photo (optional) [[User:IamCam|Cameron Perry]]<br />
**Could be one per dish, or one for each (or for some of the) step(s). [[User:AndyMabbett|Andy Mabbett]]<br />
<br />
== Additional Suggestions ==<br />
<br />
*Difficulty/Notes - Perhaps incorporation of [[hreview|hReview]] to describe difficulty (using rating) and general comments (review), as an optional field. [[User:Phae|Frances Berriman]]<br />
*Suitability (e.g. vegetarian, vegan, wheat-free, etc.). Possibly [[rel-tag]]. [[User:AndyMabbett|Andy Mabbett]] 14:57, 16 Nov 2006 (PST)<br />
*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<br />
<br />
== Cookcamp brainstorming ==<br />
<br />
At [http://barcamp.org/CookCamp CookCamp] in February 2007, Tantek moderated a fairly free form discussion of how to publish/share recipes. Here is a [http://flickr.com/photos/tantek/422072573/ photo of the whiteboard]:<br />
<br />
[http://flickr.com/photos/tantek/422072573/ http://farm1.static.flickr.com/162/422072573_9956d93f61.jpg]<br />
<br />
'''To Do''': OCR this and enter rough notes here...<br />
<br />
<br />
==Issues==<br />
===Scope===<br />
*Is this intended for only food recipes, or also recipes for, say, glue, paint, dyes and other chemicals? [[User:AndyMabbett|Andy Mabbett]] 14:53, 16 Nov 2006 (PST)<br />
** +1 Wondered the same. I'd like to see this extended as a general recipe for anything that can be created in a defined way/order, rather than just edible food.[[User:Phae|Frances Berriman]]<br />
** Agreed. This format could apply to a set of methods and materials, including cooking, science experiments, craft making, building, etc. - essentially any how-to or tutorial. [[User:IamCam|Cameron Perry]]<br />
** However, now I view my addition of 'calories per serving' as suspect, ;) though I guess it could still apply, since it's just a unit of energy. [[User:JohnLeMasney|John LeMasney]]<br />
***Recipe for Nitroglycerine (not recommended by Weight Watchers) ? [[User:AndyMabbett|Andy Mabbett]] 10:43, 1 Feb 2007 (PST)<br />
** The scope is determined by the [[recipe-examples]] research that is done, other musings are purely theoretical and thus discouraged. So far this means recipes means only food recipes. In addition, "recipe" in common vernacular applies primarily to food. Other uses are certainly outside the common 80/20 (note that 80/20 does note mean there are no non-food cases, merely that they are outside the 80). If you want to pursue other types of recipes, e.g. "chemical-recipes" - start that as a separate research effort per the [[process]]. [[User:Tantek|Tantek]] 07:39, 15 Mar 2007 (PDT)<br />
*Is it possible to have special structure for the details of the operations in the cooking. For Eg. I invite you to have a look at the following Page [http://www.anthus.com/Recipes/CompCook.html]. Should it be possible to have special markup for the operations? Or is that going too far? Maybe we could keep this open ended so that it could be included when sites would actually be interested in including the same... Anyway the article makes for some interesting reading though it is from 1985 ;-) [[User:SudarshanP|SudarshanP]] 06:46, 26 Jun 2007 (PDT)<br />
<br />
== See Also ==<br />
* [[recipe]]<br />
* [[recipe-examples]]<br />
* [[recipe-formats]]</div>SudarshanP