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.
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-*" "
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"
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
sknebelrelated issue: php-mf2 doesn't allow backcompat roots in mf2 properties: http://php.microformats.io/?id=20170731154747999 (p-author is not a nested h-card) . all other parsers (and my reading of the spec) allow that
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.
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)