tantekcopying from #indiewebcamp for the logs: in practice hMedia never found any interesting consuming applications, so it didn't get moved forward to microformats2
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
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
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
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
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
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
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
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
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?
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?