Open nex3 opened 2 weeks ago
For the time being, I'm preferring u-photo
over u-logo
even for non-photographic avatars because that seems to loosely be what consumers expect. For example, the WordPress Webmention parser looks for u-photo
and seems to ignore u-logo
.
Agreed the language should be cleared up.
My understanding and usage is that neither property is about the style of the image (whether a photo of the person, a drawing, something abstract, etc.). If it's an avatar representing the person, I use u-photo
. If it's a logo for a brand or company, I use u-logo
.
I've only used u-logo
for an h-card representing a business. In theory, on my personal site I could add my favicon with a u-logo
to my h-card
in addition to the u-photo
I have, but I haven't had a need to. Most consumers of h-card are going to prefer u-photo
and use that, in my experience.
u-photo
andu-logo
are, at a glance, very similar in purpose especially for a context like a blog or a social media site where users may well use a literal photo or a more cartoonish or even abstract representation (which could be considered a "face icon"). When implementing a producer, I'm not sure which one to use for cases where I don't have extra information about whether the content of an image is a literal photograph or just an icon; and I'm not sure which to prefer if both exist when I'm displaying a visual representation of a person.Having some text in the spec along the lines of "use
u-photo
when you know the image is a photograph of the person or organization andu-logo
when you know it's not, but otherwise preferu-<whichever>
if this information isn't available" and "if bothu-photo
andu-logo
are present and only one image is shown, preferu-<whichever>
" would be helpful to disambiguate.