shaners, gRegor`, KevinMarks, Soopaman, tantek, KartikPrabhu and Atamido_ joined the channel
#shanersHas anyone moved hMedia into mf2-land as h-media?
pfefferle joined the channel
#tantekah - sorry - I shoud have answered that here
#tantekcopying from #indiewebcamp for the logs: in practice hMedia never found any interesting consuming applications, so it didn't get moved forward to microformats2
#tantekbasically, any classic microformat that has no consuming applications got dropped.
#tantekand only those with publicly visible / useful consuming applications got upgraded to microformats2, and even those had every property scrutinized.
#xtofneuro`michel_v bonjour. Pour info, meetup indiewebcamp improvisé et ouvert par Auli nouvelle venue et motivée iwc. On s’y retrouve ? á la mutinerie 29 rue de Meaux, Paris Bise. http://indiewebcamp.com/IndieWebCampParis
pfefferle, alanpearce, barnabywalters, TallTed, alanpearce_, kez, kez_, gRegor` and Soopaman joined the channel
#barnabywalterswhat about <audio><source>? and preserving codec information for each of the links?
#barnabywaltersjust grabbing <audio src=“”> is easy enough but it doesn’t cover real-world <audio> element usage
#barnabywaltersunless you put the u-audio class on <source> children, and apply the parsing rule to those as well
pfefferle joined the channel
#KevinMarksHow do we cue your feed generator to make podcast catching friendly output?
#KevinMarksYou can have multiple audio formats in a podcast too?
#barnabywaltersI don’t know anything about podcast markup, but if someone can spec out what the RSS <entry> should look like for a post with audio elements in, I’ll update it
KevinMarks, KartikPrabhu, barnabywalters and tantek joined the channel
#barnabywaltersI can’t see a “comparison”, or even “normalization” heading in there
KartikPrabhu joined the channel
#barnabywaltersRE group blog with profiles on homepage example — you don’t have a monopoly on demanding real-world evidence ;) other people are allowed to require it too
#barnabywaltersthe closest thing is multiple conference speakers, which is not equivalent as speakers wouldn’t add the conference site as a url to their h-card
#tantekin this case I'm trying to avoid false positives, rather than make up a property for something without evidence
#tantekit's an aspect of being more conservative with protocol/format design
#tantekthe only indirect circumstantial evidence I have is people using URLs on the Twitter profiles that point to group blogs, or their companies, rather than *themsevles*
#tantekand look at this another way - if we do allow mere page = u-url matching, then we explicitly *disallow* the behavior of group-blogs with mini-profiles for the people on the home page which link to the home page.
#tantekmaybe that's ok? and I do feel that's one of those generation 2-3 use-cases that we're not going to see a lot of until indieweb stuff is more popular
#tantekwhere only one person is maintaining the site, but everyone in the family has an account on it
#tantekFWIW - Known has such assumptions built in - that one install might be used by a small group like that.
xtof joined the channel
#barnabywalters!tell tantek ah yes I understand better now, it’s the liberal-in-what-you-accept conservative-in-what-you-publish principle applied to formats. makes total sense
#KartikPrabhuKevinMarks__ that seems to be what rep-h-card algo says
tantek, caseorganic, Exploter and barnabywalters joined the channel
#tantekbarnabywalters: I'm willing to go with your proposal, while documenting my reservations / fears as an outstanding issue, and see if anything breaks.
#Loqitantek: barnabywalters left you a message 2 hours, 48 minutes ago: ah yes I understand better now, it’s the liberal-in-what-you-accept conservative-in-what-you-publish principle applied to formats. makes total sense
#tanteksince no one else seems to confirm my concerns
#tantekdropping the u-uid requirement makes it easier for authors/publishers to "get it right"
#tantekas well as gets more real world examples to "just work" immediately, e.g. adactio.com
#tantekso that's a concrete real world benefit now, that we have to measure against the hypothetical even if highly expected problem scenario
#barnabywalterstantek: actually your concerns make a lot of sense
#barnabywaltersI wonder if there’d be any downsides to speccing the stricter version but noting that implementations may choose looser requirements if they want
#tantekand the counter-point to " very few real-world h-cards with u-uid " is what I said about adactio.com - dropping the u-uid requirement gets more real world examples to "just work" immediately
#barnabywaltershow about simply requiring there to only be one h-card on the page with the same u-url as the page for it to be representative
#barnabywaltersif there’s one with u-url and u-uid == url, that’s the rep. h-card
krendil joined the channel
#barnabywaltersif there are multiple with u-url == url, one with u-uid == u-url == url, that’s the rep. h-card
#barnabywaltersif there are multiple with u-url == url, none are the rep. h-card
#barnabywaltersunless the u-url == rel-me case overrides that
#tantekthat might actually be sufficient - uniqueness of u-url = page
#tantekif there is only one h-card with u-url == page, use that h-card
#barnabywalterstantek: yep, if no u-uid == u-url == page found, look for SINGLE u-url == page
#tantekotherwise there is no definitive representative h-card
#barnabywalterstbh I’d rather people used the u-url == rel-me markup instead. That way implementations don’t have to worry about URL normalisation and matching
#tantekok that sounds like a good very deliberate incremental step forward that both addresses real world examples like adactio.com, *and* provides some guarding against the multi-author blog case
#barnabywaltersthat’s what I’m recommending people do in the indiewebify.me sample code if there’s no h-card found
#tantekeven u-url = rel-me markup needs URL normalisation and matching
#barnabywalterstantek: don’t have the right focus for adding shrewdness features right now so going to write up improved, mf2-compliant representative h-card parsing algo
#barnabywaltersI assume the back compat is handled by the h-card backcompat parsing and there doesn’t need to be a separate backcompat codepath in the algo itself?
#KevinMarks__empirical URL normalisation can be useful too
#barnabywalterse.g. should URL comparison involve redirect resolution?
#barnabywaltersif http://waterpigs.co.uk redirects to https://, my site has an h-card with url uid of https://, but someone types in the http:// to a service which does representative h-card parsing, should it correctly follow the redirect to the https:// site?
#tantekbarnabywalters: anything that *loads* the URL should use the destination of the redirect