[miklb], deep-book-gk, rodolfojcj, AngeloGladding, tantek, gRegorLove, GK1wmSU, _GK1wmSU, barpthewire, [kevinmarks], nitot, davidmead, [jeremycherfas], Garbee, pniedzielski[m], AlanPearce[m], TheGillies and schmarty joined the channel
#gRegorLoveOne thing about https://github.com/tommorris/mf2py/issues/75 raised by the microformats-parsing #11 is when a classic property and root appear inside an mf2 root, should both be ignored, or only the property? I think I treated it like both should be ignored in php-mf2 and had a good reason for that, but I don't remember it offhand.
#gRegorLoveThe alternative is that the vcard still be parsed with backcompat and added as a child.
[davidmead] joined the channel
#sknebelgRegorLove: from the parsing specification, a parser currently parsing an mf2 microformat root isn't even supposed to look for backcompat property names
#sknebel" if parsing a backcompat root, parse child element class name(s) for backcompat properties" " else parse a child element class for property class name(s) "p-*,u-*,dt-*,e-*" "
#gRegorLoveCorrect. The question is whether it should still parse the 'vcard'
#gRegorLoveSince it's on the same element as the mf1 property.
#sknebelif it isn't aware of the mf1 property, it can't make a difference between it being there and not (again, from my current interpretation of the wording of the spec)?
#gRegorLoveAs worded now, I think it should, even though it appearing as a child object is not what the publisher intended. Seems to serve as a warning almost, "you didn't fully upgrade your mf1 to mf2, that's why h-card is a child object, not on the author property"
#gRegorLoveSo I'll have to re-visit backcompat in php-mf2 a bit, try to figure out why I ignored the vcard there
#sknebelI think aaronpk intentionally left the mf2 properties out since the author is already covered by authorship rules?
#gRegorLoveYeah, he has a u-author property in there
#gRegorLoveIt's not technically causing any problems currently, that I'm aware of, but backcompat isn't following the spec as worded precisely, apparently. It should have a child h-card there, like the mf2py parser has
#sknebelnice to see that we all agree on the interpretation of the spec at least
#gRegorLoveI think my main point of confusion is "parse a child element for microformats (recurse)" -- is that supposed to start at the last property element parsed, or at the mf2 root? Probably the latter.
#gRegorLoveScratch that. Poorly worded on my part. I get it.
#tantekedited /Special:Log/block () "blocked [[User:Vedder8673]] with an expiry time of infinite (account creation disabled): Spamming links to external sites: obvious attempt to spam keyword links" (view diff)
#tantekgRegorLove++ thanks for the heads-up and cleanup of the realestate page
#Loqigregorlove has 13 karma in this channel (177 overall)
#tanteknow lets see how long it takes Google to take down that blogspot :P
[kevinmarks] joined the channel
#gRegorLovetantek: Did you catch the first username in that tell? CaitliMie spammed as well, though in 2014
#tantekapparently \ "CaitliMie" is already blocked \