2015-05-26 UTC
KevinMarks__, dariusdunlap, KevinMarks_, KevinMarks___, KartikPrabhu, fuzzyhorns, tantek, andicascadesf, pfefferle, pfefferle_, eschnou, csarven, Left_Turn, elf-pavlik, adactio, kez, Erkan_Yilmaz, kez_, glennjones and dariusdunlap_ joined the channel
tantek, benborges, Left_Turn, eschnou, elf-pavlik_, gRegorLove, KevinMarks_, KevinMarks__, csarven, dariusdunlap, KevinMarks___, KartikPrabhu, fuzzyhorns and uf-wiki-visitor joined the channel
# 22:13 uf-wiki-visitor hi all, quick question. Is it appropriate to combine microformat markup with microformat2 for compatibility? e.g. class="h-event vevent"
# 22:28 gRegorLove Hi uf-wiki-visitor. I've seen that and the parsers are intended to be backwards compatible, so it shouldn't be a problem. Personally I just use mf2.
# 22:28 tantek in fact it is recomended practice for the main object of the page!
# 22:30 tantek gRegorLove: for legacy consuming search engines that don't yet (AFAIK) consume native uf2
# 22:31 tantek uf-wiki-visitor: you can also provide yours here if you'd like folks to take a look at it
fuzzyhorns, tantek, KartikPrabhu and KevinMarks_ joined the channel
# 23:40 Vendan hey tantek, <a href="test">test</a> inside a e-content, should that href be resolved?
# 23:40 tantek Vendan probably better to use different strings
# 23:41 tantek but yes implied <base> - that's a great question!
# 23:42 Vendan should it be <a href="http://example.org/test">test</a>
# 23:42 Vendan according to the current spec, seems it shouldn't
KevinMarks__ joined the channel
# 23:42 tantek right - which seems like it could pose problems for use-cases
# 23:45 Vendan logically, I can see where it'd be useful/better that way, and the current microformats tests do expect it
# 23:45 Vendan just doesn't line up with the parsing spec itself
# 23:51 kylewm I have done it as a post-processing step after mf2py is done
benborges joined the channel