#microformats 2021-08-05

2021-08-05 UTC
# 01:00 
@BrendanEich ↩️ If only there were semantic markup conventions for UGC platforms, a la http://microformats.org/wiki/code-tools. Ccing @t in case he knows of any for things like Disqus comments, tweets, HN/Reddit posts, etc. Wouldn’t help with big platforms who won’t change, might help new wave and grass roots. (twitter.com/_/status/1423085699222294531)
nsmsn, ur5us__ and jacky joined the channel
# 01:55 
@jfairbairn ↩️ The great thing about standards... http://microformats.org/wiki/resume-formats

(Also, format, aka what boxes exist, is probably not gonna solve your problem :D) (twitter.com/_/status/1423100117591072769)
chee and jacky joined the channel
# 04:55 
@William99316397 Likely candidates are Microformats, and RDFa. (twitter.com/_/status/1423144425102925824)
jacky, neceve, hendursa1, rockorager, [Rose] and hendursaga joined the channel
# 18:23 
[tantek] class names are all case-sensitive yes. by convention all the standard microformats roots & properties are all lower-case
# 18:24 
[tantek] Brendan's question is a good one, and I think one where existing uses of h-entry may be sufficient (e.g. for comments, reactions etc.). I wonder if we have consistent guidance on that (might be better for the IndieWeb #indieweb-dev channel)
# 18:25 
[tantek] KevinMarks, please note that the "adding the equivalent mf2 ones" approach for mf1 backcompat is insufficient and will result in some nasty bugs. There are some very specific rules about when to look for and when to *ignore* (i.e. not look for) class mf1 class names
[schmarty], [chrisaldrich], willnorris, voxpelli, ur5us__ and KartikPrabhu joined the channel