[HN Gopher] Microformats Wiki
___________________________________________________________________
Microformats Wiki
Author : Tomte
Score : 49 points
Date : 2022-08-29 20:30 UTC (2 hours ago)
(HTM) web link (microformats.org)
(TXT) w3m dump (microformats.org)
| dang wrote:
| Related:
|
| _Microformats: Still Relevant?_ -
| https://news.ycombinator.com/item?id=32285207 - July 2022 (1
| comment)
|
| _Google confirms microformats are still a supported metadata
| format for content_ -
| https://news.ycombinator.com/item?id=22521666 - March 2020 (40
| comments)
|
| _Ask HN: Is it worth it to implement HTML5 microformats?_ -
| https://news.ycombinator.com/item?id=14515178 - June 2017 (1
| comment)
|
| _Microformats are easy to learn, and pay off well in SEO and
| mobile_ - https://news.ycombinator.com/item?id=4328853 - Aug 2012
| (4 comments)
|
| _Ask HN: Micro-formats, are they still relevant /useful?_ -
| https://news.ycombinator.com/item?id=2702516 - June 2011 (2
| comments)
|
| _Ask HN: Microformats - Still useful?_ -
| https://news.ycombinator.com/item?id=1747657 - Oct 2010 (5
| comments)
|
| _Microformats.org at 5: Two Billion Pages With hCards_ -
| https://news.ycombinator.com/item?id=1583784 - Aug 2010 (1
| comment)
|
| _Ask HN: Micro formats? Or, how to make my site 's google link
| look good?_ - https://news.ycombinator.com/item?id=1224242 -
| March 2010 (3 comments)
|
| _Microformats: Boon or Bane?_ -
| https://news.ycombinator.com/item?id=987688 - Dec 2009 (5
| comments)
|
| _Rest /ahah * Microformats Wiki_ -
| https://news.ycombinator.com/item?id=808251 - Sept 2009 (1
| comment)
|
| _Google Announces Support for Microformats and RDFa_ -
| https://news.ycombinator.com/item?id=606126 - May 2009 (8
| comments)
|
| _If the next "version" of the web is all about semantics, why
| aren't more people using microformats?_ -
| https://news.ycombinator.com/item?id=171818 - April 2008 (34
| comments)
|
| _Consolidate and take back your social network with XFN, openID
| and microformats_ - https://news.ycombinator.com/item?id=29512 -
| June 2007 (5 comments)
| cxr wrote:
| PSA: the best way to enable Microformat-like stuff with almost no
| effort is to keep describing content with reasonable class names
| even if you never pay any special attention to the
| microformats.org standards.
|
| One unfortunate side effect of things like Tailwind CSS is that
| some folks with a single-minded focus on looks are now using only
| the Tailwind class names, but you can do both. If before you'd
| have written something like class="video-thumbnail" and styled
| the content with a class selector in your CSS, but now you've
| adopted Tailwind and have excised all the descriptive class name
| from the content (rather than just rming your stylesheet and
| _adding_ Tailwind classes to whatever class names are already
| there), then please put the descriptive class names back in! And
| if you have colleagues submitting patches that remove class names
| because you 're migrating to Tailwind, tell them to use Tailwind
| classes in a way that _adds_ to the classification instead of as
| a replacement for traditional, descriptive class names.
|
| (A similar thing happens with CSS compilers. The autogenerated
| stuff served up on podcasts.google.com is nasty, for example.)
| avgcorrection wrote:
| The data that you mark up might be micro but the markup isn't.
| marginalia_nu wrote:
| I don't get it. The big problem with the old meta tags is that
| nobody follows standards[1], and they were frequently abused to
| misrepresent the document in a favorable way (especially keywords
| and description).
|
| How would this help alleviate those problems?
|
| [1] To this day. I've learned, from building a parser for my
| search engine, you can't just select the <title> tag if you want
| the title of a page. You need to select the title tag in the
| <head>-tag. Otherwise you'll get the title-tags people semi-
| regularly use in the body as well... Like not just hobbyists.
| Found a major American university that used title-tags to wrap
| navigational links.
| gnlrtntv wrote:
| I think these things are very related, but Microformats isn't
| going to solve this problem on its own. After all, it's been
| around for quite a while, just like most of these conventions.
|
| 10-15 years ago, we had a bunch of different ways everyone was
| trying to schematize their data on the web, and since we never
| all agreed to just use one of them, everyone now uses fragments
| of all of them -- and of other pseudo-proprietary systems -- in
| their own unique ways.
| soneil wrote:
| I keep finding these when I least expect it and they've been
| fantastic every time - it usually means whatever I'm trying to
| automate is 90% solved for me.
|
| Scraping recipes from the bbc, flight reservations from my
| email, etc. If something includes schema.org/RsvpAction it
| probably needs to be actioned, if something contains
| schema.org/DiscountOffer it can probably go in the Noise
| folder.
|
| If someone starts sending spam containing flight reservation
| meta I'm going to be so sorely disappointed in the human race.
| marginalia_nu wrote:
| I've gotten spam calendar appointments that my email client
| has helpfully added to my calendar so that I'm helpfully
| reminded of their spam sometime in the future with a push
| notification.
| myfonj wrote:
| Plus <title> tag is valid in SVG context, where it does what
| `title` attribute does on HTML elements (provides content for
| HTML tooltips and screen readers). And since inline SVG is
| valid in HTML, you can get valid title tags (from SVG
| namespace) outside HEAD element
|
| Plus if there wasn't TITLE in the head and is encountered
| inside BODY (not valid), it is adopted into the HEAD from
| document object model's perspective as if it was hoisted there
| (but it is not, just its value):
| data:text/html;charset=utf-8,<head> <!-- <title>not
| here</title> --> </head> <body bgcolor=dimgray>
| <svg viewbox="0 -15 80 20" fill=cyan> <title>SVG
| Tooltip</title> <text>Some SVG<text> </svg>
| <title>Title For Adoption.</title> <title>Second late
| title.</title> <p>And the title is: >><output
| id=o></output><<. <body onload="o.value =
| document.title"> <body text=snow>
|
| Resulting paragraph reads: "And the title is: >>Title For
| Adoption.<<."
|
| ("Yet unseen attributes" of the consecutive BODY tags are
| physically "hoisted" to real body node, but it's a different
| chapter.)
|
| Plus both <head> / </head> tags are optional -- and implied --
| so "selecting title in head tag" can become very hard task, if
| taken seriously.
|
| Making HTML parser ain't easy.
| alpb wrote:
| It's worth noting Microformats is introduced 17 years ago, and
| was last updated about 12 years ago. It never really picked up
| traction, largely because players like Google have their own
| knowledge graph, and similar structured formats like RSS have
| lost their popularity since then.
| dane-pgp wrote:
| I used to wonder "What would Social Networking look like if it
| were based on self-hosted pages written with microformats like
| h-card[0]?", but presumably the answer is "a privacy nightmare"
| (even more so than existing social networks).
|
| Perhaps a better answer to that question is "the Fediverse",
| which is based on ActivityPub. Unfortunately, though, there still
| seem to be open questions about how well/widely the Fediverse
| supports something like "circles" (the concept that Google Plus
| had) for selectively sharing content with different groups of
| people.
|
| [0] http://microformats.org/wiki/h-card
|
| [1] https://rusingh.com/fediverse-google-plus-circles/
| fsiefken wrote:
| Yes, this is something were facebook excels at, but it can also
| create in-group and out-group dynamics. A possible federated
| solution: https://beesbuzz.biz/blog/6128-Federated-access-
| control-with...
| sleepyhead wrote:
| Google prefers JSON-LD though[0]. Also I'm not keen on defining
| content with styling classes.
|
| [0] https://www.searchenginejournal.com/google-structured-
| data-p...
| lawtalkinghuman wrote:
| The class attribute isn't just for styling though.
|
| See https://html.spec.whatwg.org/multipage/dom.html#global-
| attri...
|
| > authors are encouraged to use values that describe the nature
| of the content, rather than values that describe the desired
| presentation of the content.
___________________________________________________________________
(page generated 2022-08-29 23:00 UTC)