#microformats 2015-12-11
2015-12-11 UTC
tantek, nitot, fuzzyhor_, KartikPrabhu and davidmead joined the channel
# 
@wonsterscript [GET] Rich Snippets WordPress Plugin v1.6.1 http://wonsterscript.net/rich-snippets-wordpress-plugin/?utm_source=dlvr.it&utm_medium=twitter #WordpressPlugins #shortcodes #microformats https://twitter.com/wonsterscript/status/675161474189434883/photo/1 (twitter.com/_/status/675161474189434883)
tantek, nitot, Calli, fuzzyhor_, eschnou, Left_Turn, mouserat and adactio joined the channel
fuzzyhor_, mouserat, tantek and TallTed joined the channel
# 
@pypi_updates mf2py 1.0.1: Python Microformats2 parser https://pypi.python.org/pypi/mf2py/1.0.1 (twitter.com/_/status/675404186322927616)
nitot joined the channel
# 
@artwisanggeni #python mf2py 1.0.1: Python Microformats2 parser https://pypi.python.org/pypi/mf2py/1.0.1 (twitter.com/_/status/675412304524009473)
eschnou, nitot_, tantek and nitot joined the channel
# 
@t Favorite #Mozlando moment: Working with @mixedpuppy @dietrich reviewing @GlennJones #microformats parser for #Firefox! (ttk.me t4ef4) (twitter.com/_/status/675422689637490688)
# 
tantek kylewm: re: https://twitter.com/kylewmahan/status/649287894520066049 I keep leaning more towards *not* implying a p-name if there are any specified p-* properties. I think that would handle the 99% use-case of implied p-names, as well as likely avoid most "noisy" p-names.
# tantek kylewm: if you think that approach has merit, could you open a new issue about that (since you raised it on Twitter) on http://microformats.org/wiki/microformats2-parsing-issues? This is different (even more restrictive) than "implied properties when an explicit class is provided (on the same element)"
fnordle, nitot and glennjones joined the channel
# 
@RapStarGenius RT @t: Favorite #Mozlando moment: Working with @mixedpuppy @dietrich reviewing @GlennJones #microformats parser for #Firefox! (ttk.me t4ef4) (twitter.com/_/status/675443982684549121)
nitot joined the channel