btremI lived in France for a year, and most restaurants offered a prix-fixe menu. At least, most restaurants that I could afford. There was no upselling there that I recall.
btremI think the upsell in French restaurants was a different prix fixe menu. In other words, restaurants offered two or three different prix fixe menus, which offered different choices.
btremIn the spirit of microformats2 implied properties and designing for ease-of-authoring, I wonder if h-recipe ingredient property can be improved in this way: if p-ingredient is on a <ul> or <ol> element, then each <li> will represent an ingredient, as if that <li> had the class name p-ingredient.
btremThis does't, I don't think, call for e-ingredient, since that is to include the markup itself. This is only to include the text, but separated into a list of ingredients.
[tantek]the microformats2 implied properties were based on real world experience with publishing classic microformats, not anticipating a future optimization
btremFair enough, but every recipe I've ever seen on a website uses list markup (or pseudo list markup, i.e., bullets) for ingredient lists. It would make it easier and more intuitive for authors.
[tantek]that's one of the biggest challenges with any sort of implied properties, and one which we've had to fix with increasing strictness on what and what is not implied
[tantek]since both hRecipe and h-recipe have been around for a while, if a recipe site like that using list markup isn't at least trying to use the existing solutions, there's is little hope that they would bother with any improvements (unless they actually show up here in-person and indicate as such)
btremIt's for more than recipe sites. The point of my proposal is to make it easier to adapt for an author with a blog, for example. Just one class name on a ul element, and ingredients are done.