#microformats 2015-01-21

2015-01-21 UTC
prtksxna, tantek_, tantek, KartikPrabhu and KevinMarks_ joined the channel
#
kylewm
I'm at the place. got 3/4 of a long table by the cash register
#
aaronpk
good evening!
#
kylewm
hi aaronpk. tommorris kevinmarks and I are here, waiting for tantek and a few more
#
aaronpk
according to this, tantek is gonna be a little late http://indiewebcamp.com/irc/2015-01-20/line/1421806726555
kylewm-boulange joined the channel
#
kylewm-du-dome
we have a tantek
KevinMarks_ joined the channel
#
aaronpk
is joining from a bar in portland after just having watched the SOTU
#
tommorris
aaronpk: talky.io time?
#
aaronpk
i'm in a bar so i will mute myself but sure
#
kylewm_
talky.io/microformats
#
aaronpk
OMG is that tommorris IRL?!
#
aaronpk
hello?
#
aaronpk
that lady who just walked by seemed very confused by the table of laptops
#
tommorris
...in San Francisco. What a sight!
#
aaronpk
*gasp*
#
KartikPrabhu
tommorris: kylewm_ : oh the new e-parsing does not get rid of the blank spaces it seems?...
#
KevinMarks_
it's the bonus laptop not attached to humans
#
tommorris
KartikPrabhu: I haven't merged that in yet. :)
#
KartikPrabhu
tommorris: oh so that bug is separate?
#
tommorris
the bug is against the current master.
#
aaronpk
so how bout them h-entry's?
tantek joined the channel
#
aaronpk
oh dammit talky is eating my cpu
#
kylewm_
KartikPrabhu: tommorris: I'm confused about the HTML whitespace thing. if i knew how to use git blame, i could maybe figure out where it was introduced...
#
aaronpk
what do you say we get to the meat of this meetup within 30 minutes
#
tommorris
Yup. :)
#
KartikPrabhu
ok so what is the agenda?
#
aaronpk
kylewm_: github has a git blame view
#
aaronpk
what's the repo in question?
#
kylewm_
tantek: when I came up with the idea of implied property, when i came up wtih the idea of backcompat, i did not think about using them together
#
aaronpk
agreed
#
kylewm_
the proposal is when prsing backcompat, implied properties should not be implied
#
kylewm_
it is causing bad false positives
#
kylewm_
KevinMarks_: the counter example might be wordpress templates that have microformats framing everything, but microformats2 nested inside
#
kylewm_
might be a good idea to check wtih GWG and who all is doing wordpress templates
#
kylewm_
aaronpk: is that anomalilly?
#
aaronpk
kylewm_: yes she dragged me to an SOTU viewing party ;)
#
kylewm_
tommorris: suggesting setting some boundaries, when you are parsing a mf1 legacy entry, do not allow any mf2 entries inside
#
kylewm_
tantek+Kevin: we should specify behavior for mf1 nested inside mf2
#
kylewm_
hi anomalily :)
#
kylewm_
KevinMarks_: showing a wordpress example where you install micformats2 plugin without a compatible theme
#
kylewm_
p-name inside entry-content
#
KevinMarks_
example: http://www.jeanmrussell.com/testing-brid-gy/ using wordpress with a classic template and mf-2 inside it
#
kylewm_
that example has <body class="...h-entry hentry..."> which means it would be parsed *without* backward compatibility
#
kylewm_
because h-entry implies that it has mf2, so mf1 would be overmatching
#
KevinMarks_
note the 2 content's
#
KevinMarks_
and 3(!) names
#
tommorris
That looks like a particularly fun way of making parser developers buy painkillers. :)
#
tommorris
and the four names are not all the same
#
kylewm_
tantek edits the wiki
#
KartikPrabhu
a minimal example would be nice
#
tantek
edited /microformats2-parsing-issues (+707) "adding two issues to stop "crossing the streams" interactions between classic/uf2 roots/properties. AKA don't cross the streams."
(view diff)
#
kylewm_
KartikPrabhu: of which part? the wordpress blog Kevin posted is pretty good
#
KartikPrabhu
kylewm_ that seems to have a whole bunch of comments and all that. the error is in the main h-entry yes?
#
kylewm_
KartikPrabhu: every post on snarfed.org has the same <entry-content><e-content> problem, e.g. https://snarfed.org/2014-11-24_11741
#
tantek
edited /microformats2-parsing-issues (+574) "/* issues */ add reasoning/thoughts sections to don't cross the streams issues"
(view diff)
#
kylewm_
hard to find one without comments
#
tantek
edited /microformats2-parsing-issues (+90) "/* implied properties on backcompat parsing unlikely to be intended */ resolved at meetup"
(view diff)
#
KevinMarks_
"name": [ "Testing Brid.gy", "Testing Brid.gy", "Disruption and IIW Fall 2014", "Testing Brid.gy" ], "category": [ "Uncategorized" ], "content": [ { "html": "&#xD;\n \t\t\t<div class=\"e-content\"><p>How do I get things to show up from here to twitter and facebook and also for twitter and facebook to show up here?<\/p>\n<\/div> \t\t\t",
#
aaronpk
has to run!
#
aaronpk
good evening!
#
kylewm_
KartikPrabhu: the whitespace issue seems to go back forever, I bet it is dependent on html5lib vs. lxml or whatever
#
KartikPrabhu
kylewm_ o poo!
GWG joined the channel
#
KartikPrabhu
kylewm_ odd that this test failuer did not show before!?
#
GWG
So, where are we in this backward compatibility discussion?
#
GWG
I'm still trying to get mf2 into WordPress core.
#
GWG
I got someone to agree to bring it up at the next dev meeting
#
kylewm_
GWG: the idea is basically, 1) if a root element has a mf2 class on it, it will be parsed without backward compatibility; and 2) if a root element has a mf1 class without an mf2 class, mf2 properties will be ignored
#
GWG
So, all anyone has to do is add the new class, not necessarily remove the old?
#
GWG
Works
#
tommorris
kylewm_: good work!
#
KevinMarks_
next discussion: child microformats issues -
#
KevinMarks_
t: classic mf1 had specified child properties only
#
KevinMarks_
mf2 allows more arbitrary embedding
#
kylewm_
an mf2 class with an mf1 class nested inside "obviously" makes sense, since mf2 expects nested objects
#
kylewm_
an mf1 class with a nested mf2 class is tricky
#
kylewm_
should the mf1 class be the end of the line (since mf1 did not have expected children), or should the mf2 class be parsed as a child
#
KevinMarks_
GWG: note that google only currently parses mf1, and is using it for page-type categorisation; it will only show a single type (though may show eg multiple reviews or events
#
GWG
Who else uses mf1?
#
GWG
I know few people use 2
#
kylewm_
tantek: my default is to ignore the nested mf2 class
#
KevinMarks_
https://developers.google.com/webmasters/structured-data/testing-tool/ shows this; this was a motivation for a lot of SEO, and many wp users do this
#
kylewm_
GWG: every wordpress blog uses mf1 right?
#
kylewm_
tantek: hAtom has hFeed with unattached hEntry children
#
KevinMarks_
hReviewAggregate doesn't get hReview children
#
kylewm_
tantek: another option is to hoist micformats2 classes up to the peer level with its parent mf1 element
#
KevinMarks_
tom: can we find a significant corpus of mixing 1 and 2
#
KevinMarks_
tom: suggest to barnaby that our online parsers have an opt-out "stash a copy as an example" checkbox
#
GWG
kylewm_: Not every, no.
#
KevinMarks_
by default, with default themes
tantek_ and KartikPrabhu joined the channel
#
tantek
edited /microformats2-parsing-issues (+2064) "uf2 children inside a classic microformats root class name, any h- root class name overrides and stops backcompat root"
(view diff)
tantek joined the channel
#
tantek
edited /microformats2-parsing-brainstorming (+165) "resolve nested object on a property brainstorm from kylewm, decided to adopt"
(view diff)
#
tantek
edited /microformats2-parsing-issues (+96) "/* issues */ resolve uf2 children inside a classic microformats root class name"
(view diff)
KartikPrabhu and tantek_ joined the channel
#
tantek
edited /microformats2-parsing-issues (+652) "resolve a bunch more"
(view diff)
#
tantek
edited /microformats2-parsing-issues (+110) "no consensus on the form root issue"
(view diff)
#
tantek
edited /microformats2-parsing-brainstorming (+191) "/* Canonicalization of datetime output */ consensus on choices, not clear how strong a priority"
(view diff)
#
tantek
edited /microformats2-parsing-brainstorming (+497) "/* Add meta http-equiv to microformats2 parsing model */ http - reasonable as optional pass, no need for metas until someone provides use-cases"
(view diff)
#
tantek
and with that I believe we are done with key issues and brainstorms for microformats2
tantek joined the channel
#
tantek
edited /microformats2-parsing-issues (-10) "not a stub for a while"
(view diff)
kez_, tantek_, tantek, krendil, chiui, KartikPrabhu, eschnou, adactio, kez__, Musk, Acidnerd, prtksxna, TallTed, gRegor`, hectorMcSpector, hectorMc_, hectorM__, caseorganic, elux and Loqi joined the channel
#
tantek
what was the comment last night about <template> and microformats parsing?
#
tantek
could someone (tommorris kylewm KevinMarks_ ) remember and add it to the parsing issues doc?
#
tantek
(along with proposed resolution I hope :) )
#
tantek
microformats.org/wiki/microformats2-parsing-issues
#
tantek
thanks!
tlor joined the channel
KartikPrabhu, prtksxna and tantek joined the channel
#
robertoa
edited /rel-home (+146) "Added an example in the wild"
(view diff)
#
robertoa
edited /rel-home (+11) "/* Examples in the Wild */"
(view diff)
#
tommorris
tantek: yes, the template tag needs to be ignored. mf2py already does this and I believe php-mf2 does too. someone reported it on IRC a while back (Hixie perhaps?)
#
tommorris
mf2py handles it by removing any template elements from the document before parsing.