#microformats 2024-06-17

2024-06-17 UTC
[Scout], ancarda, greenfork, capjamesg, [Murray], [schmarty] and [jeremycherfas] joined the channel
#
Loqi remind tantek to update the copy of cassis.js in https://github.com/microformats/h2vx.com/ (to be the same as what's live on the server)
#
Loqi Countdown set by [tantek] on 2024-06-16 at 12:25am UTC
[Joe_Crawford] and gRegor joined the channel
#
[tantek] done
barnaby, jeremycherfas and ApisNecros joined the channel
#
ApisNecros If I have a question about why a part of microformat specification is the way it is, would this channel, or the discussion page of the wiki be preferred?
#
ApisNecros inb4 asking to ask
#
gRegor Definitely this channel, ask away :)
#
gRegor We tend not to use the wiki talk pages much these days, easy to miss.
#
ApisNecros Okay, thank you.
#
ApisNecros I was looking over the specification for the h-recipe format, and I was curious why the e-instructions property is a body of text, instead of list like p-ingredient is. This caught my eye because, while looking at the php-mf2 output of my recipe, my nice list of steps becomes one log, unbroken paragraph. I thought it was a mistake on my part, but
#
ApisNecros after looking at the parsed output of the Examples In The Wild example, this seems consistent.
#
ApisNecros After looking at the original hRecipe, my guess is backwards compatibility.
#
gRegor Yeah, most likely backwards compatibility. It also gives some more flexibility, so publishers could either use lists or paragraphs in the instructions.
#
gRegor I'm not sure there's many consumers of the format. We try to look for those consuming use-cases before making changes to the specs, though nice thing with mf2 is you can always experiment
#
gRegor Have not used this myself, but Parika can apparently import hRecipe: https://indieweb.org/Paprika
#
ApisNecros re: "I'm not sure there's many consumers of the format." That's fair. I was just thinking, "Hm, maybe I'll have to change how my instructions section is formatted," but then I realized that I don't even have a particular reason to care, as I can't even imagine anyone parsing my recipes this way.
#
ApisNecros Like, I implement it 'cause I think it's fun, not because I know it's actually getting parsed
#
gRegor Yeah, definitely. If you prefer a list you can use <ul> or <ol> inside the e-instructions.
#
gRegor I understand that. There's definitely things I do for kicks. It's cool seeing it parsed!
#
gRegor Since the e- prefix tells it to parse it as HTML, hypothetically, a consumer should render it just like that, after any sanitizing. The parser also returns a plain text value for it the consumer can use.
#
gRegor So even the plaintext could be pretty workable, if it has newlines in it and the consumer preserves those in the display
#
gRegor Some more examples and brainstorming (not strictly about mf2) on https://indieweb.org/recipe
#
[tantek] gRegor++ agreed on all points
#
Loqi gRegor has 7 karma in this channel over the last year (132 in all channels)
#
ApisNecros Ah, okay, I wasn't aware that e- entries are intended to have their sanitized html rendered as is. In that case, I can agree that no change is particularly needed.
to2ds joined the channel