<?xml version="1.0" encoding="UTF-8"?>

<!--

	Feeds whisper secrets,
	In the RSS Club's embrace,
	Knowledge blooms in grace.

-->

<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
xmlns:source="https://source.scripting.com/"
>

<channel>
	<title>metaformats &#8211; notizBlog</title>
	<atom:link href="https://notiz.blog/tag/metaformats/feed/" rel="self" type="application/rss+xml" />
	<link>https://notiz.blog</link>
	<description>a weblog mainly about the open, portable, interoperable, small, social, synaptic, semantic, structured, distributed, (re-)decentralized, independent, microformatted and federated social web</description>
	<lastBuildDate>Mon, 11 Apr 2022 09:43:00 +0000</lastBuildDate>
	<language>de</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://notiz.blog/wp-content/uploads/2019/10/cropped-notizblog-icon-1-32x32.png</url>
	<title>metaformats &#8211; notizBlog</title>
	<link>https://notiz.blog</link>
	<width>32</width>
	<height>32</height>
</image> 
<creativeCommons:license>https://creativecommons.org/licenses/by-sa/4.0/</creativeCommons:license>
	<script xmlns="http://www.w3.org/1999/xhtml" type="application/json" id="pretty-feed-translations">{"translation-revision-date":"2026-07-06T10:30:00+00:00","generator":"WP-CLI\/2.12.0","source":"assets\/js\/pretty-feed.js","domain":"messages","locale_data":{"messages":{"":{"domain":"messages","lang":"de_DE","plural-forms":"nplurals=2; plural=(n != 1);"},"RSS feed icon":["RSS-Feed-Symbol"],"Web Feed":["Web-Feed"],"&lt;strong&gt;Look at you, following along the old-school way.&lt;\/strong&gt; Subscribe by copy-pasting the URL into your feed reader, or by clicking %1$shere%2$s...":["&lt;strong&gt;Sieh dich an, ganz old-school unterwegs.&lt;\/strong&gt; Abonniere den Feed, indem du die URL in deinen Feed-Reader kopierst oder %1$shier%2$s klickst ..."],"Visit %1$sAbout Feeds%2$s to get started with newsreaders and subscribing. It\u2019s free.":["Besuche %1$sAbout Feeds%2$s, um mit Newsreadern und dem Abonnieren zu starten. Es ist kostenlos."],"Visit Website":["Website besuchen"],"Recent Items":["Neueste Eintr\u00e4ge"],"Published:":["Ver\u00f6ffentlicht:"]}}}</script>
	<script xmlns="http://www.w3.org/1999/xhtml" src="https://notiz.blog/wp-includes/js/dist/hooks.min.js?ver=f0f188028580e8dc1255" defer=""/>
	<script xmlns="http://www.w3.org/1999/xhtml" src="https://notiz.blog/wp-includes/js/dist/i18n.min.js?ver=1dfe7db3940c23ea9216" defer=""/>
	<script xmlns="http://www.w3.org/1999/xhtml" src="https://notiz.blog/wp-content/plugins/pretty-feeds/assets/js/pretty-feed.js?ver=1.0.0" defer=""/>
<atom:link rel="hub" href="https://pubsubhubbub.appspot.com"/>
<atom:link rel="hub" href="https://pubsubhubbub.superfeedr.com"/>
<atom:link rel="hub" href="https://switchboard.p3k.io/"/>
<atom:link rel="self" href="https://notiz.blog/tag/metaformats/feed/"/>
<atom:link rel="search" type="application/opensearchdescription+xml" title="Search notizBlog" href="https://notiz.blog/wp-api/opensearch/1.1/document" />
	<source:account service="rss.chat">notizBlog</source:account>
	<source:self>https://notiz.blog/tag/metaformats/feed/</source:self>
<source:blogroll>https://notiz.blog/blogroll/?opml</source:blogroll>
	<item>
		<title>metaformats</title>
		<link>https://notiz.blog/2022/04/10/metaformats/</link>
					<comments>https://notiz.blog/2022/04/10/metaformats/#comments</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Sun, 10 Apr 2022 21:58:49 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[FediBlog]]></category>
		<category><![CDATA[IndieWeb]]></category>
		<category><![CDATA[metaformats]]></category>
		<category><![CDATA[Microformats]]></category>
		<category><![CDATA[Microformats2]]></category>
		<category><![CDATA[Open Graph Protocol]]></category>
		<category><![CDATA[Twitter Cards]]></category>
		<guid isPermaLink="false">https://notiz.blog/?p=21908</guid>

					<description><![CDATA[Vor ein paar Tagen bin ich über einen Post von Tantek Çelik gestolpert, in dem er metaformats vorstellt. Introducing #metaformats (https://microformats.org/wiki/metaformats), an extension to #microformats2 for parsing invisible data published in HTML meta tags, for backward compatibility with existing vocabularies consumed by multiple testable interoperable implementations. https://tantek.com/2022/091/t1/metaformats Der Vorschlag ist vom 01. April und war [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph">Vor ein paar Tagen bin ich über <a href="https://tantek.com/2022/091/t1/metaformats" data-type="URL" data-id="https://tantek.com/2022/091/t1/metaformats">einen Post von Tantek Çelik</a> gestolpert, in dem er <strong>metaformats</strong> vorstellt.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p>Introducing <a rel="tag" class="hashtag u-tag u-category" href="https://notiz.blog/tag/metaformats/">#metaformats</a> (<a href="https://microformats.org/wiki/metaformats">https://microformats.org/wiki/metaformats</a>), an extension to <a rel="tag" class="hashtag u-tag u-category" href="https://notiz.blog/tag/microformats2/">#microformats2</a> for parsing invisible data published in HTML meta tags, for backward compatibility with existing vocabularies consumed by multiple testable interoperable implementations.</p><cite><a href="https://tantek.com/2022/091/t1/metaformats">https://tantek.com/2022/091/t1/metaformats</a></cite></blockquote>



<p class="wp-block-paragraph">Der Vorschlag ist vom 01. April und war wohl ursprünglich als April-Scherz gedacht.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p><strong><dfn><a href="https://microformats.org/wiki/metaformats">metaformats</a></dfn></strong> started as an April Fools joke concept to describe how to both publish using microformats class names and openly parse meta tags as a fallback for what should be in-the-body visible data, including backcompat with <a href="https://indieweb.org/OGP">OGP</a>, <a href="https://indieweb.org/Twitter_Cards">Twitter Cards</a>, and meta author, description, and anything else real sites (like search engines) appear to consume.</p><cite><a href="https://indieweb.org/metaformats">https://indieweb.org/metaformats</a></cite></blockquote>



<p class="wp-block-paragraph">Eine Art Fallback-Spezifikation für <a href="https://microformats.io/#parsers" data-type="URL" data-id="https://microformats.io/#parsers">Microformats-Parser</a> finde ich in der Tat etwas sperrig, aber ich mag die Idee eines Fallbacks an sich.</p>



<p class="wp-block-paragraph"><a href="https://notiz.blog/2006/11/20/microformats/" data-type="URL" data-id="https://notiz.blog/2006/11/20/microformats/">Microformats</a> sind ein <a href="https://indieweb.org/Category:building-blocks" data-type="URL" data-id="https://indieweb.org/Category:building-blocks">Building-Block</a> des IndieWebs und werden unter anderem auch von Webmentions genutzt. Es sind Markup-Formate zur semantischen Auszeichnung von HTML. In der <a href="https://notiz.blog/2012/07/03/microformats-the-next-generation/">Version 2</a>, werden Microformats aber fast ausschließlich von der IndieWeb Community benutzt und sind darüber hinaus wenig bekannt.</p>



<p class="wp-block-paragraph">Aber gerade für WordPress ist es extrem schwer, bestehende Themes nachträglich mit Microformats zu &#8222;veredeln&#8220;. Wir haben es mit <a href="https://wordpress.org/plugins/wp-uf2/" data-type="URL" data-id="https://wordpress.org/plugins/wp-uf2/">diversen</a> <a href="https://wordpress.org/plugins/mf2-feed/" data-type="URL" data-id="https://wordpress.org/plugins/mf2-feed/">Plugins</a> versucht, mit nur mäßigem Erfolg. Andere Formate wie das <a href="https://ogp.me/" data-type="URL" data-id="https://ogp.me/">Open Graph Protocol</a> oder <a href="https://developers.google.com/search/docs/advanced/structured-data/intro-structured-data?hl=de">Schema.org (JSON-LD)</a> sind da wesentlich einfacher zu integrieren, da sie nicht bestehendes HTML erweitern und durch den Support der großen Suchmaschinen und sozialen Netzwerke, auch viel attraktiver sind.</p>



<p class="wp-block-paragraph">Ich bin <a href="https://notiz.blog/2013/08/07/embedded-json-ld/" data-type="URL" data-id="https://notiz.blog/2013/08/07/embedded-json-ld/">kein großer Fan von embedded JSON-LD</a>, aber wenn es nicht anders funktioniert und seine Reichweite hat, warum sollte man es dann ignorieren?</p>



<div class="wp-block-image"><figure class="aligncenter size-full"><img fetchpriority="high" decoding="async" width="593" height="421" sizes="(max-width: 593px) 100vw, 593px" src="https://notiz.blog/wp-content/uploads/2022/04/bridge-all-the-things.jpg" alt="" class="wp-image-21911"/></figure></div>



<p class="wp-block-paragraph">Das IndieWeb hat eigentlich eine großartige Philosophie um mit solchen &#8222;Problemen&#8220; umzugehen.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p><strong><dfn>bridge all the things</dfn></strong> is a nascent IndieWeb philosophy that prioritizes interoperability over ideology, NIH, historical disagreements, etc. ecosystems are valuable and powerful, and one easy way to extend an ecosystem is to bridge it with other existing ecosystems.</p><cite><a href="https://indieweb.org/bridge_all_the_things">https://indieweb.org/bridge_all_the_things</a></cite></blockquote>



<p class="wp-block-paragraph">Für das <a href="https://wordpress.org/plugins/webmention/">Webmention Plugin</a> haben <a href="https://david.shanske.com/" data-type="URL" data-id="https://david.shanske.com/">David</a> und ich schon vor Monaten einen ganz ähnlichen Ansatz gewählt. Neben Microformats unterstützen wir auch <a href="https://notiz.blog/tag/open-graph-protocol/" data-type="URL" data-id="https://notiz.blog/tag/open-graph-protocol/">OGP</a>, <a href="https://notiz.blog/2012/06/22/twitter-cards/" data-type="URL" data-id="https://notiz.blog/2012/06/22/twitter-cards/">Twitter-Cards</a>, <a href="https://notiz.blog/2012/09/21/schema-org-what-ive-learned-so-far/" data-type="URL" data-id="https://notiz.blog/2012/09/21/schema-org-what-ive-learned-so-far/">Schema.org</a>, <a href="https://de.wikipedia.org/wiki/Meta-Element">Meta-Header</a> und die WordPress API, um eventuell fehlende Microformats v2 zu kompensieren.</p>



<p class="wp-block-paragraph">Selbst wenn &#8222;metaformats&#8220; nur als April Scherz gedacht waren, hat die Idee Potential um speziell Webmentions voran zu treiben, da sie eine direkte Abhängikeit zu einer speziellen Websemantik verhindert.</p>



<p class="wp-block-paragraph"><strong>Bridge all the things!</strong></p>
<hr /><p>Glückwunsch, du liest per RSS! Du gehörst zu einer kleinen, feinen Gruppe, die stilvoll auf dem Laufenden bleibt.</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2022/04/10/metaformats/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
	</channel>
</rss>
