#microformats 2018-11-20
2018-11-20 UTC
nitot, [chrisaldrich], [kimberlyhirsh], [jgmac1106], KartikPrabhu, [kevinmarks], tantek, haha, [Rose], kisik21, barpthewire, [grantcodes], TallTed, vivus, [dave], [eddie], [voss] and [tantek] joined the channel
# ↩️ it's totally understandable, not everyone has the time to track all the terminological nuances --- I've seen this stuff called "microformats" too, understandable given that the MF community were trailblazers in this area ( twitter.com/_/status/1064961200088203264)
[tantek] and nitot joined the channel
# ↩️ We've struggled w terminology re various forms of markup, too. Would 'Microformats' be the best frame to use in the Facebook docs example?
I have not yet found an extant canonical taxonomy of markup, save highest-level:
- Presentational
- Procedural
- Descriptive ( twitter.com/_/status/1064967846046965760)
# ↩️ 'Microformats' would be misleading here, as it is a very specific name for a project with its own processes, syntax designs and agreed vocabularies.
'Structured data', while bland, oxymoronic and vague, does kinda work... ( twitter.com/_/status/1064970208220082176)
# ↩️ Yeah, I see "microformats" used all the time as a proxy for any number of structured data vocabularies and/or syntaxes. The pedant in me *tries* to just ignore the inexactitude of this when it's actually inconsequential. ( twitter.com/_/status/1064970392136146944)
[eddie], KartikPrabhu and [grantcodes] joined the channel
# ↩️ Nope. :) Main challenge here, IMO, is vocabulary *and* syntax are sometimes tightly bound for some types of "structured data" (Microformats, OGP, etc.) but more separated for others (#schema.org, DCMI, etc.). ( twitter.com/_/status/1064978512405135360)
ben_thatmustbeme, [tantek], nitot, tantek, [schmarty], [eddie], [jgmac1106] and eduardm joined the channel