gRegorLoveThe current approach is "replace all mf1 class names with their mf2 versions" which causes the messes we've run into. Actually following the algorithm, taking into account whether the parent element has an mf2, works much better.
gRegorLoveIf that was just a <div class="adr"> then the improved backcompat would make it <div class="adr p-adr h-adr"> and it would parse as a property, not child
gRegorLove"if that child element itself has a microformat ("h-*" or backcompat roots) and is a property element, add it into the array of values for that property..."
gRegorLoveIf there's any hReview examples that php-mf2 is handling badly now, let me know and I'll try them with this. So far using old examples on the wiki
sknebelit's a degratory term for a state dominated by corruption supporting powerful interests (originally, banana export companies basically ruling latin american states)
tantek1. sites that haven't been updated with mf2 yet (e.g. lots of WordPress hentry out there, let's make that work "out of the box" with mf2 parsers)
tantek2. sites that MUST keep some classic mf for search engines etc. at least for the root object, but want to add more details with mf2 inside, WITHOUT losing the root object, and maybe they can't update the root object (WordPress, again, because class="hentry" is in core, not themes)
aaronpkre: 2, I think we're on the same page, but just want to clarify that "want to add more details with mf2 inside" does not preclude adding "details" with mf1
tantekright now that is the case yes, because there are WordPress pages with multiple hentry objects on them with properties and such, and we want to keep supporting that
gRegorLoveIt seems to conflict with the microformats2-parsing-issues example I linked, where <div class="adr h-adr"> is upgraded to <div class="adr p-adr h-adr">. The node parser does that, making the adr the property of the h-card, not a child
gRegorLoveIs it correct to say then: If you're inside a mf1 root class, 'adr' should be considered a property for backcompat and upgraded to 'adr p-adr'?
gRegorLoveOh, I think I get it. I misspoke. Yes, 'adr' is only treated as a property inside hCard by the backcompat code -- not inside just *any* mf1 root.