hrecipe-feedback

This document is for keeping track of feedback about hRecipe, one of several microformats.

Template

Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.

Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.

<div class="hentry">
{{OpenIssue}} 
<span class="entry-summary author vcard">
 <span class="published">2011-MM-DD</span> 
 raised by <span class="fn">~~~</span>
</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2
</div>
</div>

Feedback

General Comments

open issue!

2010-06-29 
raised by Sluggy

• Draft Status?. Timeline for publishing this specification
  • I am interested in using this format. It appears that there is some usage out there (foodnetwork, epicurious, etc). Any thoughts on a timeline for moving this from a draft to a specification.

2010-06-29 
raised by awjans

• Please use hMeasure.
  • Being a enthusiastic home cook that has developed several recipes for sharing with friends and family, I like the more specific hMeasure microformat for ingredients. It seems to also be more semantically correct, IMHO.

related pages

• hRecipe
• hRecipe issues - issues regarding the hRecipe draft

Per the microformats process, the recipe effort developed

• recipe-examples
• recipe-formats
• recipe-brainstorming (see also recipe-brainstorming-archive)
• recipe-issues

towards the development of this draft.