#microformats 2015-12-05

2015-12-05 UTC
hober2 joined the channel
#
@ProjectPeachUK Our #html5 framework now contains #seo, #microformats, proxy proof #websockets. We keep on improving your #webapp! #NewBusiness #cpp (twitter.com/_/status/672937128788103169)
#
@recuweb RT @ProjectPeachUK: Our #html5 framework now contains #seo, #microformats, proxy proof #websockets. We keep on improving your #webapp! #New… (twitter.com/_/status/672937372187762692)
KevinMarks__ and KevinMarks joined the channel
#
KevinMarks_ has anyone seen microformats markup with multiple h-* classes on single element?
fuzzyhorns joined the channel
#
kylewm KevinMarks_: sure, Bridgy produces lots of markup like "h-entry h-as-article"
KartikPrabhu, eschenal, KevinMarks__ and KevinMarks joined the channel
#
KevinMarks_ kylewm: so how should we map that in jf2?
#
KevinMarks_ got an example?
eschenal, andicascadesf, Hixie, bret, KartikPrabhu, fuzzyhorns, KevinMarks, KevinMarks__ and fnordle joined the channel
#
aaronpk I thought the "h-as-*" classes were being dropped since nobody is doing anything with them
KevinMarks__, KevinMarks___, KevinMarks and tantek joined the channel
#
kylewm aaronpk: Bridgy still uses them, I'm working gradually to remove them. tantek had some other examples in the main channel though "h-card h-person"
#
aaronpk bridgy parses them or just publishes them?
#
kylewm and iirc ben_thatmustbeme and aaronpk had pretty detailed conversation about what to do with multiple h-*'s
#
kylewm it parses them and allows them to override its post-type-discover
#
kylewm y
tantek and tantek_ joined the channel
#
ben_thatmustbeme I would say h-entry h-as-article would map to either type=entry or type=as-article h-as-article was an activity streams thing that was removed though so you should probably dump it
#
ben_thatmustbeme any multiple h-* things have are there as fallbacks
#
ben_thatmustbeme so best to take the most common ones (h-entry over h-as-*)
#
ben_thatmustbeme thus most supported
#
kylewm just a question if you want to add that knowledge to the parser, up to now they have remained agnostic
#
ben_thatmustbeme well, you don't have to, you could take whichever is first, which is basically random
#
ben_thatmustbeme i don't like the idea of doing it randomly
#
ben_thatmustbeme but i like the idea of a single class other than multiple
#
ben_thatmustbeme s/other/rather/
#
Loqi ben_thatmustbeme meant to say: but i like the idea of a single class rather than multiple
JonathanNeal joined the channel
#
ben_thatmustbeme kylewm: KevinMarks KevinMarks_ aaronpk what do you think of this? https://github.com/dissolve/jf2/commit/45aab2a88d357e63799f5d0726484aa50aa33d36
#
kylewm ben_thatmustbeme: this line is ambiguous (to me) and i think has a typo If
#
kylewm + present is MUST appear only in the top level element
#
kylewm why wouldn't children be in a child element?
KevinMarks joined the channel
#
ben_thatmustbeme Ack lack of sleep. Will fix
#
ben_thatmustbeme It's only context can be at top level was what that was supposed to be
eschenal, fuzzyhorns, KevinMarks__, KartikPrabhu and tantek joined the channel