#microformats 2018-09-30
2018-09-30 UTC
[jgmac1106] joined the channel
# ↩️ Just love idea of being able to handle badging strictly in HTML and microformats enables this. To me not a better signed signature endorsment than someone’s DNS. Just two permalinks to criteria/evidence and two website talking together. (http://jgregorymcverry.com/7517-2/) ( twitter.com/_/status/1046196169985204224)
[jgmac1106], [dougbeal] and gRegorLove joined the channel
# ↩️ On display makes sense, more flexibility in design, caching, display. Though often just adding u-photo and a bit of css is enough. Doing this for me and friends, not Google. Parsers pretty neutral. I know html so microformats works for me (http://jgregorymcverry.com/7524-2/) ( twitter.com/_/status/1046248095527374849)
[tantek] joined the channel
# ↩️ Get that, valuable to me, that’s my goal.
In terms of webmention badges doubt anyone but other badging platforms parsing #OpenBadges, webmentions own standard, don’t require microformats.
Plenty of tools can handle both.
(http://jgregorymcverry.com/7544-2/) ( twitter.com/_/status/1046271063846514688)
# ↩️ As you said nobody really parsing #Openbadges stuff that much still trying to convince folks of value.
Do know community I care about parses microformats everyday. Real life implementation a not just standards for tomorrow that never comes (http://jgregorymcverry.com/7549-2/) ( twitter.com/_/status/1046272203300524032)
[grantcodes], [kevinmarks] and [schmarty] joined the channel
[schmarty] and [eddie] joined the channel
[eddie] joined the channel
[schmarty], [kevinmarks], tantek__, [tantek] and [eddie] joined the channel
[schmarty] and [jgmac1106] joined the channel
[schmarty] and [jgmac1106] joined the channel