#microformats 2016-02-19

2016-02-19 UTC
KartikPrabhu, fuzzyhorns, gRegorLove, davidmead, tantek and dogada joined the channel
#
dogada
uf-wiki-visitor: schema.org microformats used by Google supports several breadcrumbs on single page
#
Loqi
dogada: aaronpk left you a message on 2/12 at 2:59pm: shoot, I suspect the server can't speak your SSL. I'll be moving pin13.net to a new server soon which should fix that problem.
#
KartikPrabhu
dogada: schema.org is not microformats
#
KartikPrabhu
it uses RDFa syntax IIRC
#
dogada
On https://dogada.org I use both schema.org and h-breadcrumb. It both allow to extend html with meta-information about paths. It looks like http://pastebin.com/REkNXPYa
#
KartikPrabhu
you can use both sure. but schema.org has no specifications for microformats
#
dogada
aaronpk: thanks for looking into pin13.net SSL issue, on dogada.org I use free TLS-cert from startssl.com if it helps
#
dogada
KartikPrabhu: even if schema.org isn't formally a microformat, it's listed on http://microformats.org/wiki/breadcrumbs-formats, so if it walks like duck...
KartikPrabhu joined the channel
#
KartikPrabhu
it doesn't walk like a duck, because microformats parsers don't parse RDFa syntax
#
KartikPrabhu
even if it is mentioned on the microformats wiki as an alternative/prior attempts at breadcrumbs
termie, gRegorLove and fuzzyhorns joined the channel
#
dogada
Got strange issue with brid.gy after I added h-breadcrumb microformat to my blog. Page now has both h-breadcrumb and h-entry (for example please see https://dogada.org/dvd/blog/implemented-breadcrumbs) but when I try to publish it via brid.gy, it offers me to use text from h-breadcrumb and not from h-entry. Is it correct?
#
KartikPrabhu
I don't think it should
#
KartikPrabhu
feel free to ask on #indiewebcamp or file a bug with brid.gy
ivc_ and netweb joined the channel
tantek, adactio and fuzzyhorns joined the channel
#
cjk101010
edited /microformats2 (+153) "new MF2 parser"
(view diff)
#
cjk101010
edited /microformats2 (-41) "Fixed value attribute according to spec and validator"
(view diff)
#
cjk101010
edited /microformats2 (+1) "match URL from href (ends with a slash)"
(view diff)
TallTed, fuzzyhorns, ben_thatmustbeme, dogada, Left_Turn, gRegorLove, tantek, kylewm, hober and Erkan_Yilmaz joined the channel
#
@kevinmarks
I wish people would stop using u- as a prefix for utility classes in CSS. Use util- instead. You're messing with my microformats.
(twitter.com/_/status/700752598123433985)
#
tantek
what exactly *is* a utility class (vs. what other kinds of class) name anyway KevinMarks ?
#
@davidmead
RT @kevinmarks I wish people would stop using u- as a prefix for utility classes in CSS. Use util- instead. You're messing with my microformats.
(twitter.com/_/status/700753042866630656)
#
tantek
KevinMarks: wow what?!? "Apply .float-left whenever you need something floated left, and you won’t end up filling stylesheets with repeated float: left;"
#
tantek
seriously? this sounds like a hack to workaround putting in inline style attributes on elements
#
KevinMarks
and there is a convention for using u- for them, at elast in suits
#
tantek
hmm, this seems like a bad idea as a formalized practice for the same reasons that style attributes are
#
tantek
but at least with style attributes, their mere existence is like a giant (easily findable) FIXME in your code
#
tantek
so using something like .float-left is actually WORSE for maintenance / improvement than style="float:left"
#
KevinMarks
it's a way for people to violate the 'don't put inline styles in, use CSS' rule
#
tantek
maybe that's the better argument to make
#
tantek
that so-called "utility classes" are actually a bad (not good longterm) technique
#
tantek
I wonder if we have to black list certain u-*- prefixes
#
tantek
wow they're even mixing '-' and camelCase ?!?
#
tantek
a-ha, perhaps we can use that to our advantage to filter them out
#
tantek
pretty sure I documented an "all lowercase hyphenated words" convention somewhere for microformats
#
tantek
we could have parsers MUST IGNORE u-* properties where the * is camelCased
#
KevinMarks
well, to an extent it doesn't matter too much, as we aren't looking for those properties
#
tantek
KevinMarks, tommorris, gRegorLove, kylewm, aaronpk and anyone else actively working on / using mf2 parsers - what do you think of: "parsers MUST IGNORE u-* properties where the * is camelCased"
#
@FakeUnicode
RT @kevinmarks I wish people would stop using u- as a prefix for utility classes in CSS. Use util- instead. You're messing with my microformats.
(twitter.com/_/status/700756348628180992)
#
KevinMarks
a general post doing some utility class shaming may be a good thing
#
KevinMarks
that only gets the two word ones though
#
tommorris
Not sure, tantek. The other alternative is to only sniff for u-x-* and known u-'s
#
tommorris
But that makes the parser less flexible.
#
tantek
ugh - no way we want to go back down the "known u-'s" road
#
KevinMarks
is this a vendor prefix workaround?
#
aaronpk
ignoring camel case seems not terrible
#
KevinMarks
I'm still wary of that
#
KevinMarks
they don't actually put the vendor prefixes on
#
tantek
that's just apart of their -sm- -md- -lg- horribly misthought media query breakpoints
#
tantek
I can't even begin to say why that's such a bad idea
#
KevinMarks
did I mention I hated bootstrap recently?
#
tantek
bootstrap--
#
Loqi
bootstrap has -4 karma
#
KevinMarks
gah, now I see why that chap wanted CDATA the other day
#
KevinMarks
when I embed the mf2 with html inside I get actual tags
#
KevinMarks
so I need to < it
#
KevinMarks
there's no way of doing the CDATA-like 'ignore < inside this" in html5
#
tantek
edited /microformats2-parsing-issues (+893) "ignore u-camelCase properties"
(view diff)
nitot_, KevinMarks and fuzzyhorns joined the channel
#
cjk101010
edited /parsers (+123) "Adding elixir"
(view diff)
fuzzyhorns joined the channel