angelo_, angelo, ur5us_, barnaby, robo, [Zeina]1, [aciccarello]1, cygnoir[d], ben_thatmustbeme, [tonz]1, [schmarty]1, [Zeina] and [James_Van_Dyne] joined the channel
#@SquiggleReminded myself that XHTML and microformats used to be a thing, and now I'm sad.
The standardised semantic web had so much promise, and now we have... <waves hands> whatever this thing is (twitter.com/_/status/1493902707068973058)
jacky, Guest6, hans63us[d], angelo, KartikPrabhu, Seb[d] and barnaby joined the channel
#barnabyis there any archived discussion about h-card/vCard photo vs logo properties, and real-world use cases where distinguishing between them is required? the indieweb h-card wiki page mentions that homepage h-cards should include u-photo or u-logo, but I suspect that the majority of mf2 consumers ignore the logo property
#barnabythe only indieweb u-logo consumer I can think of OTTOMH is indieauth authorization endpoints looking for logo properties in a h-app vocab, to show to users on a “this app is requesting permissions” page
#barnaby“should” is fine and good, but plenty of people use non-photo profile pictures on their personal sites. should those theoretically be marked up with u-logo instead? and should all feed readers look for both properties?
#barnabyand for CMSes to get that “right”, they’d have to ask users whether their profile photo is a real photo of them on a settings page somewhere, and then switch out u-photo for u-logo where appropriate
jacky joined the channel
#barnabyI suppose my specific questions would be: should the indieweb wiki h-entry page continue to encourage use of u-logo without any known consumers/use cases?
#barnabyand: should guides to consuming h-card data for feed readers etc encourage implementations to look for logo as well as photo properties? if both, what should be prioritised, and in which situation?
#[KevinMarks]I think it's reasonable from the vcard heritage, and the common usecase of a card with a photo and/or company logo on
#barnabyfor the former I’d err towards not encouraging it without clear use-cases, for the latter I’d tend towards encouraging consumers to look for any relevant properties they can find
#[KevinMarks]especially as orgs in h-card can be nested h-cards and so could have the logo associated with them
#barnabyI think both absolutely belong in the vocab itself, especially as afaik we try to keep h-card in sync with vcard
#barnabyI’m more interested in what to recommend for individual publishers and consumers in an indieweb context
#barnaby(so maybe this discussion belongs in #indieweb-dev :P)
#barnabyI’ve been throwing around the idea of writing a guide to consuming microformats (i.e. once you’ve got parsed data from a page, how best to go about dealing with it), and have been thinking about questions like this
#barnabybecause there are lots of things you can get tripped up on, which are usually fairly easy to deal with if you know what to expect
#[KevinMarks]Did tantek's h-card have logos for the organisations in it at some point?
#[tantek]It's worth documenting what current mf2 consuming code does, and identifying places where the specs or wiki gives guidance that's not supported by any implementations
#[tantek]KevinMarks, in practice (nearly?) no one publishing bothers with differentiating logo vs photo so that bit of vCard legacy distinction is not worth carrying forward. I mean are there even vCard consuming apps that treat them distinctly like that?