#microformats 2022-11-30
2022-11-30 UTC
# 
tantek edited /Special:Log/patrol () "marked revision 70586 of [[h-recipe]] patrolled" (view diff)
# 
[schmarty] bahahahaha
gRegor, [jeremycherfas], angelo, gRegorLove_, ur5us, alex2, tiim, barnaby, [manton], ash[m] and btrem joined the channel
# btrem @aaronpk @tantek re e-logo, I'm already using that. Don't know if anyone is making use of it, but you can see it here: https://greenbankplants.com/
# btrem Besides e-logo, I'm using an h-card class name on the `text` elements in the svg: `<text class="p-name fn">Greenbank Plant Nursery</text>` (simplified for clarity).
# btrem As I matter of fact, I have. :)
# btrem Note that my proof that the text element is getting parsed by search engines doesn't necessarily mean they're parsing the *microformats* therein. It might be paying attention to the text element because its ancestor is `<h1>`.
# btrem I don't know of any way to prove that a microformat is being used in some special way by a search engine.
# btrem Right.
# btrem Both ddg and google include the business' address, marked up as h-adr. That would tend to make me think they *are* parsing the h-card. But no way to know for sure.
# btrem What is ML?
# btrem (Yes, I know you can't do that here. So I'm actually asking you!)
# btrem Ah.
# btrem I'm not sure why aaronpk is leery of e-logo: https://chat.indieweb.org/microformats/2022-11-29/1669743151076000
# btrem Doesn't seem all that different than e-content.
# btrem Speaking of microformats and svg: I just learned that microdata attributes are not permitted on svg elements, whereas class is. So if one wants to add machine readable bits of data, microformats is the only way to do that. With the caveat that, again, there's no way to know what e.g. search engines do with any of this stuff. Maybe they process microdata in spite of the spec.
ur5us joined the channel
# btrem Is the microformats/microformats.io repo dormant?
# 
[tantek] aaronpk, e.g. https://www.w3.org/TR/SVGTiny/
jamietanna joined the channel
jamietanna joined the channel
# btrem Yes, that's why I was asking.
jamietanna joined the channel
# btrem I've been working on a complete rewrite of the micformats.io page, removing the bootstrap css stuff, which seems unnecessary for such a simple one page site. And then simplifying the markup. That would make the source code a bit more of a good example of coding with mf.
# btrem But I haven't pushed that yet. I was waiting for the minor changes to be merged.
# 
@brianwisti ↩️ Not that I found specifically for pytest, but there are numerous microformats2 validators and at least one cross-format handler on PyPI:
https://pypi.org/project/granary/ (twitter.com/_/status/1598070100263067650)
# 
gRegor btrem, merged all but https://github.com/microformats/microformats.io/pull/54, small note and need to resolve branch conflicts, otherwise good
[mattl] and tiim joined the channel; tiim left the channel
# btrem Well, I copied/modified the code from another page, and apparently used a deprecated tag `<source>`. Annoyingly, the wiki software doesn't tell me what the /replacement/ is. (grumble grumble)
# btrem gRegor Ah, well I just fixed the PR, but didn't mention you. So you probably don't know. (Well, you do now.) :)
# btrem Thanks gRegor++.
btrem joined the channel; btrem left the channel
# btrem edited /microformats2-parsing (+54) "Fix: replaces deprecated <source> tag with <syntaxhighlight>" (view diff)
# btrem edited /microformats2-parsing (-11) "Fix: corrects syntaxhightlight lang attributes" (view diff)
# btrem edited /existing-rel-values (+72) "Fix: replaces deprecated <source> tag with <syntaxhighlight>" (view diff)