Microformats Wiki
microformats.org
Microformats Wiki
1–10 of 69 posts
Re: Microformats Wiki
#2I 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.
Re: Microformats Wiki
#3I 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 tag if you want the title of a page. You need to select the title tag in the -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.
Re: Microformats Wiki
#4It'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.
Re: Microformats Wiki
#5Google 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...
Re: Microformats Wiki
#6PSA: 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.)
Re: Microformats Wiki
#7The data that you mark up might be micro but the markup isn’t.
Re: Microformats Wiki
#8I 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 tag if you want the title of a page. You need to select the t…
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.
Re: Microformats Wiki
#9I 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 tag if you want the title of a page. You need to select the t…
Plus 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,
not here -->
SVG Tooltip
Some SVG
Title For Adoption.
Second late title.
And the title is: »«.
("Yet unseen attributes" of the consecutive BODY tags are physically "hoisted" to real body node, but it's a different chapter.)
Plus both / 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.
Re: Microformats Wiki
#10I 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 tag if you want the title of a page. You need to select the t…
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.