trwnhi think the footgun here is that a well-meaning publisher (like me!) can naturally author an a element wrapping a u-* property and then not realize it's actually An Issue
trwnhthat's a tricky one because it works only because the img is implicit? so double implicit works, the instant you get explicit about the img.u-logo it stops working?
trwnhso then the "parsing for implied properties" section should have more warnings that you can't really depend on it in various situations outside the simplest one
trwnh"as soon as you use a p-* or e-* property, you need to explicitly markup a p-name because it will no longer be implied. similarly, as soon as you use a u-* property, you need to explicitly markup a u-url because it will no longer be implied."
gRegorOut of curiosity, did you follow a tutorial that said to add the u-logo u-photo on that nested image, or were you referring to the properties on the mf2 wiki?
trwnhand i was writing my html in a sort of "purist" sense of no classes no consideration for css or rendering kind of way, with the aim of progressively adding on support for things like mf2
trwnhthat's one of the places that makes sense yeah but admittedly i wasn't aware that page existed until just now so it's maybe not the best/only page to edit ^_^
gRegorWhich also has "When more than those three minimal properties are needed, the root class name must be placed on an element which encloses all the desired properties, and then the properties themselves marked up using the classnames given below."
gRegor Slightly misspoke earlier, there are minimal photo + name versions: https://indieweb.org/h-card#How_to_markup
trwnh i can similarly suppress the implied "name" property by using p-given-name and p-family-name http://php.microformats.io/?id=20261108000837805