#microformats 2020-12-11

2020-12-11 UTC
#
btrem
It must be because I'm American. (a) I don't know exactly what "cheeky" means; and (b) I still find it very funny!
#
btrem
I 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.
#
[KevinMarks]
I don't mean france, I mean uk + us (especially east coast)
#
btrem
I 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.
#
btrem
Never been to the UK. unfortunately. I actually grew up on the east coast of the US, and didn't come across prix fixe very much.
#
[KevinMarks]
that's true, I have seen that in France
#
[KevinMarks]
chekcing Bouchon they were pretty good, only a supplement for cheese instead of dessert
#
btrem
The places I could afford generally didn't offer a cheese course instead of dessert. I did encounter that twice, and it was pretty cool.
#
btrem
I do miss the restaurant experience in France. And the bakeries.
#
btrem
And the metro.
#
btrem
Oh #@! it, I just miss France.
#
btrem
edited /menu-brainstorming (+475) "Adds proposal for prix fixe menus."
(view diff)
[chrisaldrich], [tantek], TeeKay, [jeremycherfas], KartikPrabhu, [Murray], [KevinMarks], hober2, Loqi, ethanyoo, btrem, [Rose], TallTed, [jgmac1106], [Raphael_Luckom], gRegorLove, [schmarty], [snarfed], [fluffy] and milkii joined the channel
#
btrem
In 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.
#
btrem
This 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.
[Raphael_Luckom] joined the channel
#
[tantek]
better not to prematurely overoptimize like that before trying something simpler (fewer rules)
#
[tantek]
the microformats2 implied properties were based on real world experience with publishing classic microformats, not anticipating a future optimization
#
btrem
Fair 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.
#
btrem
IOW, it is no anticipating a need, but paving a cowpath.
#
btrem
...not anticipating...
#
[tantek]
it's not just looking for patterns like that but looking for counter-examples that may result in false positives
#
[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]
also it's not a cowpath in this case unless they're already using microformats and thus indicate motivation to potentially adopt any changes
#
[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)
#
btrem
It'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.