#microformats 2021-08-04

2021-08-04 UTC
#
rascul
or at least that's what i'm telling myself
#
[jacky]
def lean on this channel as a resource 🙂
jacky and Seirdy joined the channel
jacky, KartikPrabhu and ur5us__ joined the channel
#
rascul
is h_entry valid? or just h-entry?
#
rascul
ok thanks
#
rascul
hentry is mf1, h-entry is mf2
#
rascul
oh that's easy enough
#
rascul
mf1 properties look like they can get a bit interesting
#
KartikPrabhu
all mf2 objects/properties are *-*
#
rascul
yes i have seen that, makes the mf2 stuff easier
#
jacky
thaknfully :)
#
jacky
*thankfully
ur5us__, Stasimon and neceve joined the channel
#
[KevinMarks]
The python parser has a mapping for mf1 to mf2 properties, and works by finding the mf1 ones and adding the equivalent mf2 ones
hendursa1, KartikPrabhu, chee, ur5us__ and rockorager joined the channel
#
rascul
are microformats case sensitive? ie is H-eNTrY valid ?
#
aaronpk
i was pretty sure it's all case sensitive and everything is lowercase, but now I am not finding that on http://microformats.org/wiki/microformats2-parsing
#
aaronpk
in any case the prefixes are certainly case sensitive
#
Loqi
Tantek Çelik
#
rascul
i'll just assume only lowercase is valid for now
#
rascul
until i know better
#
aaronpk
the php parser ignores the one with caps so i think that's a safe assumption http://pin13.net/mf2/?id=20210804125440668
#
rascul
i see, thanks
hendursaga, rockorager, hendursa1 and [grantcodes] joined the channel
#
[KevinMarks]
The prefixes were defined to be lower case. The field names I think we constrained to avoid false positives from all the u- utility classes in bootstrap
#
Loqi
Tantek Çelik
#
rascul
excellent, lowercase only then
rockorager joined the channel
#
rascul
no need to play with things like to_lowercase()
[jeremycherfas], hendursaga, jacky, KartikPrabhu, neceve, ur5us__, chee and rockorager joined the channel