<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="https://notiz.blog/wp-content/plugins/pretty-feeds/pretty-feed-v4.xsl" type="text/xsl" media="screen" ?>


<!--

	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:source="http://source.scripting.com/"
xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule"
>

<channel>
	<title>Firefox &#8211; notizBlog</title>
	<atom:link href="https://notiz.blog/tag/firefox/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>Thu, 21 Mar 2024 15:49:16 +0000</lastBuildDate>
	<language>de</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://notiz.blog/wp-content/uploads/2019/10/cropped-notizblog-icon-1-32x32.png</url>
	<title>Firefox &#8211; notizBlog</title>
	<link>https://notiz.blog</link>
	<width>32</width>
	<height>32</height>
</image> 
<source:blogroll>https://reader.pfefferle.org/i/?a=opml&amp;get=c_2</source:blogroll>
<creativeCommons:license>https://creativecommons.org/licenses/by-sa/4.0/</creativeCommons:license>
<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/firefox/feed/"/>
<atom:link rel="search" type="application/opensearchdescription+xml" title="Search notizBlog" href="https://notiz.blog/wp-api/opensearch/1.1/document" />	<item>
		<title>OpenWeb-Notizen: Contacts in the Browser, Open Web Apps, PubSubJubhub, FederatedSocialWebCharter</title>
		<link>https://notiz.blog/2010/10/27/openweb-notizen-contacts-in-the-browser-open-web-apps-pubsubjubhub-federatedsocialwebcharter/</link>
					<comments>https://notiz.blog/2010/10/27/openweb-notizen-contacts-in-the-browser-open-web-apps-pubsubjubhub-federatedsocialwebcharter/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Wed, 27 Oct 2010 21:18:39 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[OpenWeb Notizen]]></category>
		<category><![CDATA[federated social web]]></category>
		<category><![CDATA[FederatedSocialWebCharter]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Mozilla]]></category>
		<category><![CDATA[OAuth]]></category>
		<category><![CDATA[PubSubHubbub]]></category>
		<category><![CDATA[PubSubJubBub]]></category>
		<category><![CDATA[W3C]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=3344</guid>

					<description><![CDATA[Neue Version von &#8222;Contacts in the Browser&#8220; Contacts in the Browser kann jetzt auch OAuth: Where possible, Contacts now uses the industry-standard OAuth login mechanism to access websites. You will need to re-connect your browser to your services once to set it up. » Contacts in the Browser 0.4 released Mozillas &#8222;Prototype of an Open [&#8230;]]]></description>
										<content:encoded><![CDATA[
<h2 class="wp-block-heading">Neue Version von &#8222;Contacts in the Browser&#8220;</h2>



<p><em>Contacts in the Browser</em> kann jetzt auch OAuth:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>Where possible, Contacts now uses the industry-standard OAuth login mechanism to access websites. You will need to re-connect your browser to your services once to set it up.</p>
</blockquote>



<p>» <a href="https://web.archive.org/web/20120321140225/http://mozillalabs.com:80/contacts/2010/10/22/contacts-in-the-browser-0-4-released/">Contacts in the Browser 0.4 released</a></p>



<h2 class="wp-block-heading">Mozillas &#8222;Prototype of an Open Web App Ecosystem&#8220;</h2>



<p>Und nochmal Firefox: Mozilla arbeitet an der Verschmelzung von Webservices und dem Browser:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>Apps built using HTML/CSS/JavaScript that work both on computers and mobile phones, have many of the characteristics that users find compelling about native apps and provide developers with open and flexible distribution options.</p>
</blockquote>



<p>» <a href="http://blog.mozilla.com/blog/2010/10/19/prototype-of-an-open-web-app-ecosystem/">Prototype of an Open Web App Ecosystem</a></p>



<h2 class="wp-block-heading">PubSubJubhub</h2>



<p>PubSubHubBub mit JavaScript abonnieren:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>A little web service that allows you to subscribe to PubSubHubbub feeds from Javascript! </p>
</blockquote>



<p>» <a href="https://web.archive.org/web/20141218194609/http://pubsubjubhub.appspot.com/">PubSubJubhub</a></p>



<h2 class="wp-block-heading">W3Cs FederatedSocialWebCharter</h2>



<p>Das W3C will jetzt auch im <em>OpenWeb</em> mit mischen und ruft das (oder den) <em>FederatedSocialWebCharter</em> ins leben:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>The mission of the Federated Social Web Incubator Group is to provide a set of community-driven specifications and a test-case suite for a federated social web.</p>
</blockquote>



<p>» <a href="http://www.w3.org/2005/Incubator/socialweb/wiki/FederatedSocialWebCharter">FederatedSocialWebCharter</a></p>
<p>Thanks for reading this post via RSS. RSS is great, and you’re great for using it. ♥️</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2010/10/27/openweb-notizen-contacts-in-the-browser-open-web-apps-pubsubjubhub-federatedsocialwebcharter/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>OpenWeb-Notizen: Mozilla, Thunderbird, AOL, Webfinger</title>
		<link>https://notiz.blog/2010/08/11/openweb-notizen-mozilla-thunderbird-aol-webfinger/</link>
					<comments>https://notiz.blog/2010/08/11/openweb-notizen-mozilla-thunderbird-aol-webfinger/#comments</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Wed, 11 Aug 2010 18:26:51 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[OpenWeb Notizen]]></category>
		<category><![CDATA[AOL]]></category>
		<category><![CDATA[federated social web]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[HTML5]]></category>
		<category><![CDATA[Mozilla]]></category>
		<category><![CDATA[Thunderbird]]></category>
		<category><![CDATA[WebFinger]]></category>
		<category><![CDATA[XAuth]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=3129</guid>

					<description><![CDATA[Letztes Mal sind die Notizen dank zu viel Arbeit und StarCraft II leider ausgefallen, aber das wird nicht einreißen&#8230; hoffe ich zumindest 🙂 Der Browser und das Federated Web Ein großes Problem im dezentralen Web: Der gemeine User kann nichts mit Identifiern anfangen, weder mit URLs (wie es NoseRub versucht hat) noch mit E-Mail Adressen [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>Letztes Mal sind die <em>Notizen</em> dank <em>zu viel Arbeit</em> und <em>StarCraft II</em> leider ausgefallen, aber das wird nicht einreißen&#8230; hoffe ich zumindest 🙂</p>



<h2 class="wp-block-heading">Der Browser und das <em>Federated Web</em></h2>



<p>Ein großes Problem im dezentralen Web: Der gemeine User kann nichts mit <em>Identifiern</em> anfangen, weder mit URLs (wie es NoseRub versucht hat) noch mit E-Mail Adressen (wie es Status.Net mit Webfinger versucht). Austin King zeigt auf <em>Mozilla Webdev</em> wie man dem, mit Hilfe des Browsers und der JavaScript Methoden <em>registerProtocolHandler</em> und <em>postMessage</em>, entgegen wirken kann. <a href="https://web.archive.org/web/20120808043826/http://xauth.org:80/">XAuth</a> funktioniert übrigens nach einem ähnlichen Prinzip.</p>



<p>» <a href="http://blog.mozilla.com/webdev/2010/07/26/registerprotocolhandler-enhancing-the-federated-web/">RegisterProtocolHandler Enhancing the Federated Web</a></p>



<h2 class="wp-block-heading">Thunderbird Contacts</h2>



<p>Endlich gibt es das <em>Contacts</em>-Addon auch für den Thunerbird, denn da gehören sie ja auch hin.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p>The goal of add-on is to experiment in evolving the address book of Thunderbird beyond what it currently is today. Thunderbird Contacts isn’t a standalone address book, instead it understands that your contacts live on the web as much as they do inside Thunderbird. The add-on can pull in contact data from various services where your contacts already exist.</p></blockquote>



<p>» <a href="https://web.archive.org/web/20120403104228/http://mozillalabs.com:80/messaging/2010/08/04/thunderbird-contacts">Thunderbird Contacts</a></p>



<h2 class="wp-block-heading">AOL und der Webfinger</h2>



<p>AOL implementiert Webfinger für <em>@aol.com</em> und <em>@aim.com</em>.</p>


<pre class="wp-block-code"><span><code class="hljs language-xml"><span class="hljs-meta">&lt;?xml version='1.0' encoding='UTF-8'?&gt;</span>
<span class="hljs-tag">&lt;<span class="hljs-name">XRD</span> <span class="hljs-attr">xmlns</span>=<span class="hljs-string">'http://docs.oasis-open.org/ns/xri/xrd-1.0'</span>&gt;</span>
  <span class="hljs-comment">&lt;!-- Host-wide Information --&gt;</span>
  <span class="hljs-tag">&lt;<span class="hljs-name">Link</span> <span class="hljs-attr">rel</span>=<span class="hljs-string">'http://specs.openid.net/auth/2.0/provider'</span> <span class="hljs-attr">href</span>=<span class="hljs-string">'https://api.screenname.aol.com/auth/openidServer'</span>&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">Title</span>&gt;</span>OpenID 2.0 Provider<span class="hljs-tag">&lt;/<span class="hljs-name">Title</span>&gt;</span>
  <span class="hljs-tag">&lt;/<span class="hljs-name">Link</span>&gt;</span>
  <span class="hljs-comment">&lt;!-- Resource-specific Information --&gt;</span>
  <span class="hljs-tag">&lt;<span class="hljs-name">Link</span> <span class="hljs-attr">rel</span>=<span class="hljs-string">'lrdd'</span> <span class="hljs-attr">template</span>=<span class="hljs-string">'https://api.screenname.aol.com/auth/describe?uri={uri}'</span>&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">Title</span>&gt;</span>Resource Descriptor<span class="hljs-tag">&lt;/<span class="hljs-name">Title</span>&gt;</span>
  <span class="hljs-tag">&lt;/<span class="hljs-name">Link</span>&gt;</span>
<span class="hljs-tag">&lt;/<span class="hljs-name">XRD</span>&gt;</span></code></span></pre>


<p>» <a href="http://practicalid.blogspot.com/2010/08/webfinger-enabled-for-aolcom.html">Webfinger enabled for @aol.com</a></p>
<p>Hey there, RSS reader! You’re cool. Keep being awesome! 😎</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2010/08/11/openweb-notizen-mozilla-thunderbird-aol-webfinger/feed/</wfw:commentRss>
			<slash:comments>4</slash:comments>
		
		
			</item>
		<item>
		<title>OpenWeb-Notizen: XAuth, OExchange, Firefox Sync, RDFa</title>
		<link>https://notiz.blog/2010/06/02/openweb-notizen-xauth-oexchange-firefox-sync-rdfa/</link>
					<comments>https://notiz.blog/2010/06/02/openweb-notizen-xauth-oexchange-firefox-sync-rdfa/#comments</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Wed, 02 Jun 2010 19:09:15 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[OpenWeb Notizen]]></category>
		<category><![CDATA[FediBlog]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[NASCAR problem]]></category>
		<category><![CDATA[OAuth]]></category>
		<category><![CDATA[OExchange]]></category>
		<category><![CDATA[OpenID]]></category>
		<category><![CDATA[RDFa]]></category>
		<category><![CDATA[sync]]></category>
		<category><![CDATA[Video]]></category>
		<category><![CDATA[XAuth]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=2745</guid>

					<description><![CDATA[Chris Messina erklärt XAuth XAuth ist eine Art Cross-Domain Cookie mit dem man Versucht die Flut an Share, Like und Login Icons auf ein Minimum zu reduzieren. » XAuth &#8211; an introduction » Offizielle XAuth Seite OExchange einfach erklärt OExchange ist ein offenes Protokoll um eine beliebige URL mit einem beliebigen Service im Web zu [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p><strong>Chris Messina erklärt XAuth</strong><br> XAuth ist eine Art <em>Cross-Domain</em> Cookie mit dem man Versucht die Flut an Share, Like und Login Icons auf ein Minimum zu reduzieren.</p>



<figure class="wp-block-embed-vimeo alignwide wp-block-embed is-type-video is-provider-vimeo"><div class="wp-block-embed__wrapper">
<span class="embed-privacy-url"><a href="http://vimeo.com/12121710">Eingebetteten Inhalt von Vimeo öffnen</a></span>
</div></figure>



<p>» <a href="http://vimeo.com/12121710">XAuth &#8211; an introduction</a><br> » <a href="https://web.archive.org/web/20120808043826/http://xauth.org:80/">Offizielle XAuth Seite</a></p>



<p><strong>OExchange einfach erklärt</strong><br> OExchange ist ein offenes Protokoll um eine beliebige URL mit einem beliebigen Service im Web zu teilen. Die Demo zeigt die Funktionsweise von OExchange und welche Vorteile sich in Kombination mit z.B. XAuth ergeben.</p>



<figure class="wp-block-embed-youtube wp-block-embed is-type-video is-provider-youtube"><div class="wp-block-embed__wrapper">
<span class="embed-privacy-url"><a href="https://www.youtube.com/watch?v=Be9ArGBUTco">Eingebetteten Inhalt von YouTube öffnen</a></span>
</div></figure>



<p>» <a href="https://web.archive.org/web/20210129102822/http://www.oexchange.org/demo/">OExchange in action</a><br> » <a href="https://github.com/oexchange">Offizielle OExchange Seite</a></p>



<p><strong>Firefox Sync</strong><br> Mozilla benennt das Labs-Projekt <em>Weave Sync</em> in <em>Firefox Sync</em> um und kündigt an, den Sync-Mechanismus in eine der nächsten Firefox Versionen fest zu integrieren. Im Zuge meiner Recherche bin ich außerdem noch auf einen Wiki-Artikel gestoßen, der erklärt wie man den <em>Firefox Sync</em> zukünftig auch mit OpenID oder OAuth koppeln könnte:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p>The user must have a way of proving to a third-party service that they really are who they claim, and for the Mozilla service to provide information back to the third-party service that access has been granted. The OpenID and OAuth protocols provide what we need here, and the OpenID/OAuth hybrid flow has been described.</p><p>Once this is done, the third party service will be able to establish a relationship with the Weave Sync service for a user, without the user disclosing his or her password.</p></blockquote>



<p>» <a href="http://www.mozilla.com/en/firefox/sync/">Stay in Sync With Your Firefox</a><br> » <a href="https://web.archive.org/web/20111026001208/https://mozillalabs.com/blog/2010/06/firefox-sync-graduates-from-mozilla-labs/">Firefox Sync Graduates from Mozilla Labs</a><br> » <a href="https://wiki.mozilla.org/Labs/Weave/Developer/SecureDataSharing">Secure Data Sharing</a></p>



<p><strong>RDFa 1.1 &#8211; Alles neu, alles anders</strong><br> Dank HTML5 (ohne X) wurde RDFa noch einmal grundlegend überdacht. In der Version 1.1 werden die RDF-Vocabularies beispielsweise nicht mehr über Namespaces definiert. Früher:</p>


<pre class="wp-block-code"><span><code class="hljs language-xml"><span class="hljs-tag">&lt;<span class="hljs-name">a</span> <span class="hljs-attr">xmlns:cc</span>=<span class="hljs-string">"http://creativecommons.org/ns#"</span>
   <span class="hljs-attr">rel</span>=<span class="hljs-string">"cc:license"</span>
   <span class="hljs-attr">href</span>=<span class="hljs-string">"http://creativecommons.org/licenses/by-nc-nd/3.0/"</span>&gt;</span>
<span class="hljs-tag">&lt;/<span class="hljs-name">a</span>&gt;</span>.</code></span></pre>


<p>Jetzt:</p>


<pre class="wp-block-code"><span><code class="hljs language-xml"><span class="hljs-tag">&lt;<span class="hljs-name">a</span> <span class="hljs-attr">prefix</span>=<span class="hljs-string">"cc: http://creativecommons.org/ns#"</span>
   <span class="hljs-attr">rel</span>=<span class="hljs-string">"cc:license"</span>
   <span class="hljs-attr">href</span>=<span class="hljs-string">"http://creativecommons.org/licenses/by-nc-nd/3.0/"</span>&gt;</span>
<span class="hljs-tag">&lt;/<span class="hljs-name">a</span>&gt;</span>.</code></span></pre>


<p>Grund der Änderung: HTML kennt im Gegensatz zu XHTML keine Namespaces und RDFa soll sowohl in HTML5 als auch in XHTML5 integriert werden.</p>



<p>» <a href="https://www.w3.org/TR/rdfa-core/">RDFa Core 1.1</a></p>



<p><strong>RDFa checker</strong><br> Toby Inkster hat einen sehr umfangreichen RDFa checker veröffentlicht:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p>It checks your web page for RDFa and displays any data found there. It also compares your data against the published recommendations from major consumers/users of RDFa data, to see how well your data matches their requirements.</p></blockquote>



<p>» <a href="http://linter.structured-data.org/">check rdfa</a></p>
<p>Hey there, RSS reader! You’re one of a special few, choosing this old-school yet awesome way of staying informed. Kudos!</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2010/06/02/openweb-notizen-xauth-oexchange-firefox-sync-rdfa/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
		<item>
		<title>OpenWeb-Notizen: DiSo 2, Mozilla, Microdata, Portability Policy</title>
		<link>https://notiz.blog/2010/05/26/openweb-notizen-diso-2-mozilla-facebook-semantic-web/</link>
					<comments>https://notiz.blog/2010/05/26/openweb-notizen-diso-2-mozilla-facebook-semantic-web/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Wed, 26 May 2010 18:40:59 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[OpenWeb Notizen]]></category>
		<category><![CDATA[DataPortability]]></category>
		<category><![CDATA[DiSo]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Mozilla]]></category>
		<category><![CDATA[OpenWeb Podcast]]></category>
		<category><![CDATA[Portability Policy]]></category>
		<category><![CDATA[Privacy Policy]]></category>
		<category><![CDATA[Webstandards]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=2691</guid>

					<description><![CDATA[Da ich in den letzten Monaten nicht wirklich viel Zeit zum bloggen hatte, im (Open)Web aber trotzdem viel zu viel interessantes passiert und ich hackrs kurzen und prägnanten Schreibstil sehr schätze, versuche ich mich jetzt mal an einer OpenWeb-Version von Linkwertig und nenne es &#8222;OpenWeb-Notizen&#8222;&#8230; Das versuche ich jetzt mal jeden Mittwoch zu machen&#8230; eine [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>Da ich in den letzten Monaten nicht wirklich viel Zeit zum bloggen hatte, im (Open)Web aber trotzdem viel zu viel interessantes passiert und ich <a href="https://hackr.de/">hackrs</a> kurzen und prägnanten Schreibstil sehr schätze, versuche ich mich jetzt mal an einer OpenWeb-Version von <a href="http://netzwertig.com/2010/05/26/linkwertig-pac-man-semantisches-web-google-analytics-mobile-commerce/">Linkwertig</a> und nenne es &#8222;<a href="https://notiz.blog/category/openweb-notizen/">OpenWeb-Notizen</a>&#8222;&#8230; Das versuche ich jetzt mal jeden Mittwoch zu machen&#8230; eine Art <em>OpenWeb-Wednesday</em> so zu sagen&#8230;</p>



<p><strong>DiSO 2</strong><br/> Steve Ivy (Mitbegründer des DiSo-Projekts) interviewt Tantek Çelik (geistiger Vater der Microformats) zu <em>Distributed Social Networks</em>. Im aktuellen Interview spricht Tantek über URL-Shortener: warum sie das Internet &#8222;verletzen&#8220;, warum man sie dennoch braucht, warum <em>jeder</em> seinen eigen Shortening-Service betreiben sollte und wie er das Problem für sich gelöst hat.</p>



<p>» <a href="https://web.archive.org/web/20100418004554/http://www.monkinetic.com/2010/03/interview-tantek-celik-conceptualizing-diso-20.html">Interview: Tantek Celik, Conceptualizing DiSo 2.0</a><br/> » <a href="https://web.archive.org/web/20100529033049/http://www.monkinetic.com/2010/05/tantek-celik-diso-20-brass-tacks.html">Tantek Celik on DiSo 2.0: Down to Brass Tacks</a></p>



<p><strong>Tantek Çelik unterstützt Mozilla</strong><br/> &#8230;und nochmal etwas vom Mr. Microformat. Tantek soll dem Firefox-Team während der nächsten Monate mit seiner <em>Open-/Web-Standards Erfahrung</em> zur Seite stehen:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>My belief is that by basing our work on simple, open, accessible Web standards, that we can help usher in a whole new era of distributed social Web sites.</p>
</blockquote>



<p>» <a href="https://web.archive.org/web/20140209140004/http://news.cnet.com/8301-13577_3-20005987-36.html">Mozilla hires open-standards guru Celik</a></p>



<p><strong>Umfassende Microdata-Einführung</strong><br/> Mark Pilgrim befasst sich in seinem frei erhältlichen Online-Buch &#8222;Dive Into HTML5&#8220; auch sehr detailliert mit dem Thema <em>Microdata</em>. Sehr empfehlenswert für Einsteiger <em>und</em> Fortgeschrittene!</p>



<p>» <a href="http://diveintohtml5.info/extensibility.html">&#8222;Distributed&#8220;, &#8222;Extensibility&#8220;, &amp; Other Fancy Words</a></p>



<p><strong>Portability Policy</strong><br/> Die <em>DataPortability Organisation</em> veröffentlicht die <em>Portability Policy</em>. Die Policy soll eine Art standardisierte Zusammenfassung der <em>Privacy Policy</em> und der <em>Terms of Services</em> sein, mit der Plattformbetreiber auf die <em>Portabilität</em> ihrer Daten hinweisen können.</p>



<p>» <a href="https://web.archive.org/web/20110830165828/http://portabilitypolicy.org/index.html">Portability Policy</a></p>



<p><strong>(Video) Podcasts</strong><br/> Es gibt wieder neue Folgen von &#8222;The SocialWeb TV&#8220; und dem &#8222;OpenWebPodcast&#8220;:</p>



<p>» <a href="https://web.archive.org/web/20131207055646/http://www.thesocialweb.tv/blog/2010/05/f.html">SocialWeb TV: Making Sense of Recent News</a><br/> » <a href="http://blog.openwebpodcast.de/347/owp29/">OpenWebPodcast: Episode 29 – OpenWebNews</a></p>
<p>Hey there, RSS reader! You’re one of a special few, choosing this old-school yet awesome way of staying informed. Kudos!</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2010/05/26/openweb-notizen-diso-2-mozilla-facebook-semantic-web/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Operator wird doch weiter entwickelt</title>
		<link>https://notiz.blog/2009/09/08/operator-wird-doch-weiter-entwickelt/</link>
					<comments>https://notiz.blog/2009/09/08/operator-wird-doch-weiter-entwickelt/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Tue, 08 Sep 2009 21:40:36 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[Addon]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Firefox 3]]></category>
		<category><![CDATA[Microformats]]></category>
		<category><![CDATA[Microformats API]]></category>
		<category><![CDATA[Mikroformate]]></category>
		<category><![CDATA[Operator]]></category>
		<category><![CDATA[Plugin]]></category>
		<category><![CDATA[value class pattern]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=1852</guid>

					<description><![CDATA[Gute Neuigkeiten! Michael Kaply, der die Weiterentwicklung von Operator (ein Microformats Addon für Firefox) Ende 2008 eingestellt hat&#8230; Operator – Deciding what to do with Operator is difficult. [&#8230;] That being said, I’m going to do a few fixes for Operator, call it 1.0 and then stop development. &#8230;widmet sich jetzt doch wieder dem de [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>Gute Neuigkeiten! <a href="https://mike.kaply.com/">Michael Kaply</a>, der die Weiterentwicklung von <a href="https://web.archive.org/web/20101120155908/http://kaply.com:80/weblog/operator/">Operator</a> (ein <a href="http://microformats.org/wiki/browser">Microformats Addon</a> für Firefox) Ende 2008 eingestellt hat&#8230;</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>Operator – Deciding what to do with Operator is difficult. [&#8230;] That being said, I’m going to do a few fixes for Operator, call it 1.0 and then stop development.</p>
</blockquote>



<p>&#8230;widmet sich jetzt doch wieder dem de facto <em>(Microformats) Browser Plugin</em>&#8230;</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>The biggest news I have is that I have resumed work on Operator. In particular, I’m fixing bugs, adding a few usability enhancements and adding support for new microformat stuff like the value class/pattern for dates. I’m also considering completely removing the “Actions” toolbar and switching to interacting only with the data. I’m definitely looking for feedback on that one.</p>
</blockquote>



<p>Wer Ideen zu neuen Features oder Funktionen hat, kann diese gerne auf Michaels Weblog loswerden.<br/> Mein Wunsch: <a href="https://notiz.blog/2009/06/18/microdata-semantisches-html5/">Microdata</a> support 🙂</p>



<p>(Ich hoffe dass die Angekündigten <a href="http://microformats.org/wiki/value-class-pattern">value-class-pattern</a> Änderungen eventuell auch irgendwann in die native <a href="https://web.archive.org/web/20080701113514/http://www.kaply.com/weblog/2008/05/20/where-are-the-microformat-in-firefox-3/">Microformats Firefox API</a> aufgenommen werden.)</p>
<p>RSS readers like you are the secret sauce of the internet. Keep rocking and staying informed!</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2009/09/08/operator-wird-doch-weiter-entwickelt/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Mozilla Jetpack (und Microformats)</title>
		<link>https://notiz.blog/2009/06/05/mozilla-jetpack-und-microformats/</link>
					<comments>https://notiz.blog/2009/06/05/mozilla-jetpack-und-microformats/#comments</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Fri, 05 Jun 2009 06:50:38 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[FediBlog]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[JavaScript]]></category>
		<category><![CDATA[Jetpack]]></category>
		<category><![CDATA[Microformats]]></category>
		<category><![CDATA[Mozilla]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=1627</guid>

					<description><![CDATA[Jetpack ist das jüngste Baby der Mozilla Labs und bietet eine Art API, die es Entwicklern ermöglicht, den Firefox mit klassischen Web-Techniken (HTML, JavaScript und CSS) zu erweitern. Statt mit XUL kann man seine Firefox Addons demnächst vielleicht wirklich mit HTML und CSS gestalten. Großartige Idee! Übrigens unterstützt Jetpack, wie auch Ubiquity, die ab der [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p><a href="https://wiki.mozilla.org/Jetpack" data-type="URL" data-id="https://wiki.mozilla.org/Jetpack">Jetpack</a> ist das jüngste Baby der <em>Mozilla Labs</em> und bietet eine Art API, die es Entwicklern ermöglicht, den Firefox mit klassischen Web-Techniken (HTML, JavaScript und CSS) zu erweitern. Statt mit <abbr title="XML User Interface Language"><a href="http://www.mozilla.org/projects/xul/">XUL</a></abbr> kann man seine Firefox Addons demnächst vielleicht wirklich mit HTML und CSS gestalten. Großartige Idee!</p>



<figure class="wp-block-embed alignwide is-type-video is-provider-vimeo wp-block-embed-vimeo"><div class="wp-block-embed__wrapper">
<span class="embed-privacy-url"><a href="https://vimeo.com/4752576">Eingebetteten Inhalt von Vimeo öffnen</a></span>
</div></figure>



<p>Übrigens unterstützt Jetpack, <a href="https://notiz.blog/2008/09/16/ubiquity-und-microformats/">wie auch Ubiquity</a>, die ab der Version 3 in Firefox nativ implementierte <a href="https://developer.mozilla.org/En/Using_microformats">Microformats API</a>. Der folgende Code zeigt, wie man die Microformats API in Jetpack-Skripte integrieren kann. Das Beispiel zählt z.B. alle hCards der Seite, auf der man sich gerade befindet und zeigt das Ergebnis per Info-Message an:</p>


<pre class="wp-block-code"><span><code class="hljs language-javascript">Components.utils.import(<span class="hljs-string">"resource://gre/modules/Microformats.js"</span>);
<span class="hljs-comment">// count hCards</span>
jetpack.tabs.onFocus(<span class="hljs-function"><span class="hljs-keyword">function</span>(<span class="hljs-params"></span>) </span>{
  <span class="hljs-comment">// load HTML</span>
  <span class="hljs-keyword">var</span> doc = jetpack.tabs.focused.contentDocument;
  <span class="hljs-comment">// count microformats </span>
  <span class="hljs-keyword">var</span> uFcount = Microformats.count(<span class="hljs-string">'hCard'</span>, doc);
  <span class="hljs-comment">// load notifier</span>
  jetpack.notifications.show({
    <span class="hljs-attr">title</span>: <span class="hljs-string">'hCards'</span>,
    <span class="hljs-attr">body</span>: <span class="hljs-string">'number of hCards on this website: '</span> + uFcount,
    <span class="hljs-attr">icon</span>: <span class="hljs-string">'http://microformats.org/favicon.ico'</span>
  });
});</code></span></pre>


<p><ins><strong>Nachtrag</strong></ins>:</p>



<p>Unter Windows und Linux scheinen die Messages nicht so ganz zu funktionieren, deshalb gibt&#8217;s hier nochmal nen Beispiel wo der Counter in der Statusbar ausgegeben wird:</p>


<pre class="wp-block-code"><span><code class="hljs language-javascript">Components.utils.import(<span class="hljs-string">"resource://gre/modules/Microformats.js"</span>);
jetpack.statusBar.append({
  <span class="hljs-attr">html</span>: <span class="hljs-string">'&lt;img src="http://microformats.org/favicon.ico"&gt; hCards: &lt;span id="hcard-count"&gt;0&lt;/span&gt;'</span>,
  <span class="hljs-attr">onReady</span>: <span class="hljs-function"><span class="hljs-keyword">function</span>(<span class="hljs-params">jetpackWidget</span>) </span>{
    <span class="hljs-function"><span class="hljs-keyword">function</span> <span class="hljs-title">counthCard</span>(<span class="hljs-params"></span>)</span>{
      <span class="hljs-comment">//load HTML</span>
      <span class="hljs-keyword">var</span> doc = jetpack.tabs.focused.contentDocument;
      <span class="hljs-comment">// count microformats</span>
      <span class="hljs-keyword">var</span> uFcount = Microformats.count(<span class="hljs-string">'hCard'</span>, doc);
      <span class="hljs-keyword">if</span> (uFcount &gt; <span class="hljs-number">0</span>) {
        $(jetpackWidget).find(<span class="hljs-string">'#hcard-count'</span>).html(uFcount);
      }
    }
    jetpack.tabs.onFocus(counthCard);
  }
});</code></span></pre>


<p>Mal schaun ob mir demnächst noch etwas sinnvolleres Einfällt 😉</p>
<p>RSS readers like you are the unsung heroes of the internet. Keep up the good work!</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2009/06/05/mozilla-jetpack-und-microformats/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Identity In The Browser</title>
		<link>https://notiz.blog/2009/05/08/identity-in-the-browser/</link>
					<comments>https://notiz.blog/2009/05/08/identity-in-the-browser/#comments</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Fri, 08 May 2009 14:41:39 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[Browser]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Identity in the Browser]]></category>
		<category><![CDATA[Mozilla]]></category>
		<category><![CDATA[Mozilla Labs]]></category>
		<category><![CDATA[OpenID]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=1528</guid>

					<description><![CDATA[Mozilla wagt sich an OpenID 🙂 . Weave, ein in den Mozilla Labs entwickeltes Addon, bietet in einer ersten Beta jetzt auch einen browser-gestützten OpenID-Login an. Zum Screencast!]]></description>
										<content:encoded><![CDATA[
<p><a href="https://web.archive.org/web/20090510235750/http://labs.mozilla.com:80/2009/05/identity-in-the-browser/">Mozilla wagt sich an OpenID</a> 🙂 .</p>



<p><a href="https://web.archive.org/web/20090423171229/http://labs.mozilla.com:80/projects/weave/">Weave</a>, ein in den Mozilla Labs entwickeltes Addon, bietet in einer <a href="https://web.archive.org/web/20091213212416/http://people.mozilla.com:80/~cbeard/weave/dist/latest-weave.xpi">ersten Beta</a> jetzt auch einen browser-gestützten OpenID-Login an.</p>



<p><a href="https://web.archive.org/web/20120513015630/http://people.mozilla.com/~dmills/weave/weave-id-screencast-2009-05-06.swf">Zum Screencast!</a></p>
<p>Hey there, RSS reader! You’re one of a special few, choosing this old-school yet awesome way of staying informed. Kudos!</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2009/05/08/identity-in-the-browser/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>OpenID für Flock</title>
		<link>https://notiz.blog/2008/12/02/openid-fuer-flock/</link>
					<comments>https://notiz.blog/2008/12/02/openid-fuer-flock/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Tue, 02 Dec 2008 20:54:19 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[Browser]]></category>
		<category><![CDATA[FediBlog]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[flock]]></category>
		<category><![CDATA[Identity]]></category>
		<category><![CDATA[IDIB]]></category>
		<category><![CDATA[OpenID]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=1320</guid>

					<description><![CDATA[Bei Vidoop hab ich gerade von dem neuen OpenID Plugin für Flock gelesen. Das Plugin ist eine Zusammenarbeit zwischen Vidoop, MySpace und Flock und basiert auf dem Know-How des IDIB (Identity in the Browser) Plugins für den Firefox. Ähnlich wie bei IDIB für Firefox kann man auch bei der Flock Version mehrere OpenIDs voreinstellen. Neu [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>Bei Vidoop hab ich gerade von dem neuen <a href="https://web.archive.org/web/20090327191036/http://blog.vidoop.com:80/2008/12/identity-in-the-browser-takes-a-big-step-forward/">OpenID Plugin für Flock</a> gelesen. Das Plugin ist eine Zusammenarbeit zwischen Vidoop, MySpace und Flock und basiert auf dem Know-How des <strong><a href="https://notiz.blog/2008/08/07/identity-in-the-browser-an-openid-firefox-extension/"><abbr title="Identity in the Browser">IDIB</abbr> (Identity in the Browser) Plugins</a></strong> für den Firefox.</p>



<p>Ähnlich wie bei <abbr title="Identity in the Browser">IDIB</abbr> für Firefox kann man auch bei der Flock Version mehrere OpenIDs voreinstellen. Neu beim Flock-Plugin ist die Automatische Erkennung von <em>OpenID Providern</em> und <em>OpenID Relying Parties</em>. Besuchte <em>OpenID Profider</em> wie z.B. Yahoo! oder MySpace merkt sich das Plugin und schlägt sie unter &#8222;Suggested OpenID&#8217;s&#8220; vor.</p>



<figure class="wp-block-image aligncenter"><img decoding="async" src="https://notiz.blog/wp-content/uploads/2008/12/flock-openid-config.png" alt="Flock-openid-config.png" /></figure>



<p><em>OpenID Consumer</em> oder <em>Relying Parties</em> werden wohl nur noch am Login-Feld <code>&lt;input id="openid_identifier" /></code> und nicht mehr (wie bei <abbr title="Identity in the Browser">IDIB</abbr>) über <a href="https://github.com/diso/idib">XRDS-Simple</a> erkannt. Ist ein OpenID Login möglich, werden einem die vorher angelegten OpenIDs angeboten und man kann sich bequem über das Plugin anmelden.</p>



<figure class="wp-block-image aligncenter"><img decoding="async" src="https://notiz.blog/wp-content/uploads/2008/12/flock-openid-login.png" alt="Flock-openid-login.png" /></figure>



<p>Für die Audio-Visuellen unter euch gibt es auch noch eine kurze Einführung per ScreenCast.</p>



<p>Download OpenID Plugin: <a href="https://web.archive.org/web/20100106113605/https://extensions.flock.com/extensions/">https://extensions.flock.com/extensions/</a></p>
<p>Thanks for reading this post via RSS. RSS is great, and you’re great for using it. ♥️</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/12/02/openid-fuer-flock/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Ubiquity und Microformats</title>
		<link>https://notiz.blog/2008/09/16/ubiquity-und-microformats/</link>
					<comments>https://notiz.blog/2008/09/16/ubiquity-und-microformats/#comments</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Tue, 16 Sep 2008 18:38:37 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Microformats]]></category>
		<category><![CDATA[Semantic HTML]]></category>
		<category><![CDATA[Ubiquity]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=1141</guid>

					<description><![CDATA[Ubiquity bietet (neben Operator) endlich einen echten Anwendungsfall für die Microformats Firefox API. Die Microformats API basiert auf JavaScript und lässt sich somit auch direkt (und ohne viel Aufwand) in die Ubiquity-Commands integrieren. Das folgende wirklich sinnvolle Beispiel zählt alle hCards einer Seite und gibt das Ergebnis als System-Message aus: Martin McEvoy hat ein paar [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>Ubiquity bietet (neben <a href="https://web.archive.org/web/20120630183520/http://mike.kaply.com/2008/03/17/operator-09-is-available/">Operator</a>) endlich einen echten Anwendungsfall für die <em>Microformats Firefox API</em>. Die <a href="https://web.archive.org/web/20120503100548/https://developer.mozilla.org/en/Using_microformats">Microformats API</a> basiert auf JavaScript und lässt sich somit auch direkt (und ohne viel Aufwand) in die <a href="https://wiki.mozilla.org/Labs/Ubiquity/Commands_In_The_Wild">Ubiquity-Commands</a> integrieren.</p>



<p>Das folgende wirklich sinnvolle Beispiel zählt alle <a href="http://microformats.org/wiki/hCard">hCards</a> einer Seite und gibt das Ergebnis als <a href="https://wiki.mozilla.org/Labs/Ubiquity/Ubiquity_0.1_Author_Tutorial#Hello_World:_The_First_Command">System-Message</a> aus:</p>


<pre class="wp-block-code"><span><code class="hljs language-javascript">Components.utils.import(<span class="hljs-string">"resource://gre/modules/Microformats.js"</span>);
CmdUtils.CreateCommand({
  <span class="hljs-attr">name</span>: <span class="hljs-string">"count-hcards"</span>,
  <span class="hljs-attr">execute</span>: <span class="hljs-function"><span class="hljs-keyword">function</span>(<span class="hljs-params"></span>) </span>{
    <span class="hljs-keyword">var</span> doc = Application.activeWindow.activeTab.document;	
    <span class="hljs-keyword">var</span> uFcount = Microformats.count(<span class="hljs-string">'hCard'</span>, doc);
    displayMessage( uFcount );
  }
})</code></span></pre>


<p>Martin McEvoy hat ein paar wesentlich schickere Commands gebaut, die mit Hilfe des <a href="https://web.archive.org/web/20100413130036/http://transformr.co.uk/">Transformrs</a> Mikroformate verarbeitet. Da für diese Verarbeitung ein Redirect (oder das öffnen einer zweiten Seite) notwendig ist, überprüft er mit Hilfe der Microformats-API zuerst ob sich die notwendigen Mikroformate überhaupt auf der Seite befinden.</p>



<p>Der folgende Code (von Martin) testet z.B. ob mind. ein hCalendar verfügbar ist, bevor er diesen verarbeitet:</p>


<pre class="wp-block-code"><span><code class="hljs language-php">CmdUtils.CreateCommand({
  icon: <span class="hljs-string">"http://transformr.co.uk/favicon.ico"</span>,
  name: <span class="hljs-string">"get-webcal"</span>,
  author: {name: <span class="hljs-string">"Martin McEvoy"</span>, email: <span class="hljs-string">"weborganics@googlemail.com"</span>},
  help: <span class="hljs-string">"Subscribe to a webcal feed using the 
&lt;a href=\"http://microformats.org/wiki/hcalendar\"&gt;hCalendar&lt;/a&gt; Microformat."</span>,
  preview: <span class="hljs-function"><span class="hljs-keyword">function</span> <span class="hljs-params">( pblock )</span> </span>{
    pblock.innerHTML = <span class="hljs-string">"Subscribe to web calendar"</span>;
  },
  execute: <span class="hljs-function"><span class="hljs-keyword">function</span><span class="hljs-params">()</span> </span>{
    <span class="hljs-keyword">var</span> doc = Application.activeWindow.activeTab.document;
    <span class="hljs-keyword">var</span> mFcount = Microformats.count(<span class="hljs-string">'hCalendar'</span>, doc,{ showHidden : <span class="hljs-keyword">true</span> });
    <span class="hljs-keyword">if</span> (mFcount &gt; <span class="hljs-number">0</span>) {
      <span class="hljs-keyword">var</span> url = <span class="hljs-string">"webcal://transformr.co.uk/hcalendar/"</span>;
      url += CmdUtils.getWindowInsecure().location ; 
      Utils.openUrlInBrowser(url);
    } <span class="hljs-keyword">else</span> {
      displayMessage(<span class="hljs-string">'Sorry No hCalendar Events Found!'</span>);
    }
  }
})</code></span></pre>


<p>Quelle: <a href="https://web.archive.org/web/20081121062147/http://transformr.co.uk/commands">http://transformr.co.uk/commands</a></p>



<p>Weitere großartige Ubiquity-Commands im <a href="http://microformats.org/wiki/ubiquity">Microfromats-Wiki</a>&#8230;</p>
<p>You are a true RSS aficionado! While others are drowning in social media noise, you enjoy the simplicity and control of RSS. Congrats!</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/09/16/ubiquity-und-microformats/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Ubiquity (der Vollständigkeit halber)</title>
		<link>https://notiz.blog/2008/09/09/ubiquity-der-vollstaendigkeit-halber/</link>
					<comments>https://notiz.blog/2008/09/09/ubiquity-der-vollstaendigkeit-halber/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Tue, 09 Sep 2008 18:47:14 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[Addon]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Ubiquity]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=1119</guid>

					<description><![CDATA[Ubiquity gibt es ja jetzt schon ne ganze Weile und es wurde auch schon zu genüge darüber berichtet, deshalb will ich auch gar nicht mehr groß darauf eingehen. Da ich das Firefox-Addon aber recht spannend finde und sicherlich noch einiges darüber schreiben werde, möchte ich diejenigen die noch nichts von Ubiquity gehört haben auf den [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p><a href="https://web.archive.org/web/20090628091724/https://labs.mozilla.com/2008/08/introducing-ubiquity/">Ubiquity</a> gibt es ja jetzt schon ne ganze Weile und es wurde auch schon zu genüge darüber berichtet, deshalb will ich auch gar nicht mehr groß darauf eingehen. Da ich das Firefox-Addon aber recht spannend finde und sicherlich noch einiges darüber schreiben werde, möchte ich diejenigen die noch nichts von Ubiquity gehört haben auf den Artikel von <a href="https://web.archive.org/web/20140209201815/http://netzwertig.com/2008/08/27/firefox-addon-ubiquity-kommandozentrale-im-web/">Markus Spath (auf netzwertig)</a> und das folgende Video hinweisen&#8230;</p>



<figure class="wp-block-embed-vimeo wp-block-embed alignwide is-type-video is-provider-vimeo">
	<span class="embed-privacy-url"><a href="https://vimeo.com/1561578">Eingebetteten Inhalt von Vimeo öffnen</a></span>
</figure>



<p>Ich persönlich mag das <a href="https://web.archive.org/web/20080731083657/http://blacktree.com/?quicksilver">quicksilver-ähnliche</a> Handling und das <em>kontextsensitive reagieren der Ubiquity-Befehle</em> (frei nach <a href="https://web.archive.org/web/20140209201815/http://netzwertig.com/2008/08/27/firefox-addon-ubiquity-kommandozentrale-im-web/">Markus</a>).<br/> D.h. Ubiquity arbeitet, genau nach dem <a href="http://microformats.org/about/">Microformats-Prinzip</a>: &#8222;<strong>Designed for humans first and machines second</strong>&#8230;&#8220;, mit den gleichen Informationen die auch der User zu Gesicht bekommt&#8230; der Webseite.<br/> Das schreit ja nahezu nach einigen coolen <a href="http://microformats.org/wiki/ubiquity">Microformats-Anwendungen</a> 🙂</p>
<p>Thanks for reading this post via RSS. RSS is great, and you’re great for using it. ♥️</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/09/09/ubiquity-der-vollstaendigkeit-halber/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>OAuth in Firefox?</title>
		<link>https://notiz.blog/2008/08/07/oauth-in-firefox/</link>
					<comments>https://notiz.blog/2008/08/07/oauth-in-firefox/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Thu, 07 Aug 2008 11:07:33 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[DataPortability]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[flock]]></category>
		<category><![CDATA[OAuth]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=1042</guid>

					<description><![CDATA[Gestern berichtete ReadWriteWeb über eventuelle Pläne, OAuth nativ in Firefox zu integrieren. The conversation today took place in the context of a question from Matthew &#8222;lilmatt&#8220; Willis, a Flock employee and longtime contributor to Mozilla. Willis wants to know if the Firefox developer community would like OAuth built into Firefox and if so how. He [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>Gestern berichtete <a href="https://web.archive.org/web/20121008195025/http://www.readwriteweb.com:80/archives/mashups_firefox_may_go_oauth.php">ReadWriteWeb</a> über eventuelle Pläne, <a href="http://oauth.net">OAuth</a> nativ in Firefox zu integrieren.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>The conversation today took place in the context of a question from Matthew &#8222;lilmatt&#8220; Willis, a Flock employee and longtime contributor to Mozilla. Willis wants to know if the Firefox developer community would like OAuth built into Firefox and if so how. He points out that much of the work has already been done, if not multiple times.</p>
</blockquote>



<p>Neben <a href="https://notiz.blog/2008/05/21/wo-sind-die-microformats-im-firefox-3/">Microformats</a> und <a href="https://notiz.blog/2008/08/07/identity-in-the-browser-an-openid-firefox-extension/">OpenID</a> wäre OAuth das dritte offene Format welches der Firefox 3 unterstützen würde&#8230;</p>



<p>So macht DataPortability Spass 🙂</p>
<p>Hey there, RSS reader! You’re one of a special few, choosing this old-school yet awesome way of staying informed. Kudos!</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/08/07/oauth-in-firefox/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Identity In The Browser &#8211; an OpenID Firefox Extension</title>
		<link>https://notiz.blog/2008/08/07/identity-in-the-browser-an-openid-firefox-extension/</link>
					<comments>https://notiz.blog/2008/08/07/identity-in-the-browser-an-openid-firefox-extension/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Thu, 07 Aug 2008 07:10:41 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[FediBlog]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Identity]]></category>
		<category><![CDATA[Mozilla]]></category>
		<category><![CDATA[OpenID]]></category>
		<category><![CDATA[Vidoop]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=1038</guid>

					<description><![CDATA[Gestern veröffentlichte Vidoop eine erste Version ihrer Identity In The Browser-Extension für den Firefox 3. IDIB ist OpenSource und soll die OpenID-Verarbeitung, speziell in den Punkten Sicherheit und Browser-Redirects, verbessern. Die derzeitige Version des Addons bietet folgende Möglichkeiten: we help to reduce or eliminate browser-based redirects typically involved in authenticating against identity providers we add [&#8230;]]]></description>
										<content:encoded><![CDATA[
<figure class="wp-block-image aligncenter"><img decoding="async" src="https://notiz.blog/wp-content/uploads/2008/08/add-ons.jpg" alt="Add-ons.jpg" /></figure>



<p>Gestern veröffentlichte Vidoop eine erste Version ihrer <em><a href="https://web.archive.org/web/20080925102635/http://labs.vidoop.com:80/2008/08/06/developer-preview-identity-in-the-browser-idib/">Identity In The Browser</a></em>-Extension für den <a href="http://wiki.mozilla.org/Firefox3">Firefox 3</a>. <abbr title="Identity In The Browser">IDIB</abbr> ist OpenSource und soll die <a href="http://openid.net">OpenID</a>-Verarbeitung, speziell in den Punkten Sicherheit und Browser-Redirects, verbessern.</p>



<p>Die derzeitige Version des Addons bietet folgende Möglichkeiten:</p>



<ul class="wp-block-list">
	<li>we help to reduce or eliminate browser-based redirects typically involved in authenticating against identity providers</li>
	<li>we add security to reduce the potential for phishing/man-in-the-middle attacks</li>
</ul>



<p>Mit <abbr title="Identity In The Browser">IDIB</abbr> möchte Vidoop einen Anfang machen, um die Kommunikation zwischen Mozilla und OpenID wieder anzutreiben:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>It was almost two years ago when the Firefox 3.0 roadmap was announced and OpenID was mentioned as a new component to the platform. The Mozilla Firefox team looked to members of the OpenID community to step up and provide guidance on what exactly we imagined identity in the browser looking like, but we failed to mobilize and answer their call.</p>
</blockquote>



<p>Leider benötigt das Addon einige kleine Erweiterungen (<a href="https://github.com/diso/idib">Relying Parties</a>) zum aktuellen OpenID-Standard, die alle im <a href="https://github.com/diso/idib">Entwickler-Wiki</a> dokumentiert sind&#8230; </p>



<p>(Da <a href="http://willnorris.com/">Will Norris</a> (der Entwickler des <a href="http://wordpress.org/extend/plugins/openid/">OpenID-Plugins für WordPress</a>) aktuell für Vidoop arbeitet, sollte es aber nicht all zu lange dauern bis eine erste, angepasste Version seinen Plugins erhältlich ist.)</p>
<p>RSS readers like you are the unsung heroes of the internet. Keep up the good work!</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/08/07/identity-in-the-browser-an-openid-firefox-extension/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>hForms &#8211; Semantische Formulare</title>
		<link>https://notiz.blog/2008/06/28/hforms-semantische-formulare/</link>
					<comments>https://notiz.blog/2008/06/28/hforms-semantische-formulare/#comments</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Sat, 28 Jun 2008 13:09:39 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[Addon]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Forms]]></category>
		<category><![CDATA[hCard]]></category>
		<category><![CDATA[Microformats]]></category>
		<category><![CDATA[vCard]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=921</guid>

					<description><![CDATA[Warum sollte nur die Ausgabe ((X)HTML) semantisch anreichern und die Eingabe vernachlässigen? Beim spielen mit dem hCard-Mappers und der Firefox-Microformats-API kam mir die Idee, auch Formulare semantisch auszuzeichnen&#8230; In dem Artikel Use the new microformats API in your Firefox 3.0 Extensions beschreibt Rob Crowther wie man mit Hilfe der Firefox-Microformats-API eine hCard speichert um sie [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>Warum sollte nur die Ausgabe ((X)HTML) semantisch anreichern und die Eingabe vernachlässigen?</p>



<p>Beim <em>spielen</em> mit dem <a href="https://notiz.blog/2008/03/28/hcard-mapper/">hCard-Mappers</a> und der <a href="https://notiz.blog/2008/06/04/microformats-api-in-firefox3-erweiterungen-nutzen/">Firefox-Microformats-API</a> kam mir die Idee, auch Formulare semantisch auszuzeichnen&#8230;</p>



<p>In dem Artikel <em><a href="https://web.archive.org/web/20130516000806/http://www.ibm.com:80/developerworks/xml/library/x-tipffoxmicroapi/">Use the new microformats API in your Firefox 3.0 Extensions</a></em> beschreibt Rob Crowther wie man mit Hilfe der Firefox-Microformats-API eine hCard speichert um sie zum Ausfüllen verschiedener Formulare weiterverwenden zu können.</p>



<p>Das Problem: Das Prinzip funktioniert leider nur bei Formularen die dem festgelegten Aufbau entsprechen. Im Fall des Beispiels wäre das:</p>


<pre class="wp-block-code"><span><code class="hljs language-xml"><span class="hljs-tag">&lt;<span class="hljs-name">h1</span>&gt;</span>hCardFormFiller Target Form<span class="hljs-tag">&lt;/<span class="hljs-name">h1</span>&gt;</span>
<span class="hljs-tag">&lt;<span class="hljs-name">form</span> <span class="hljs-attr">action</span>=<span class="hljs-string">"#"</span> <span class="hljs-attr">method</span>=<span class="hljs-string">"post"</span>&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">label</span>&gt;</span>Name: <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"text"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"name"</span> /&gt;</span><span class="hljs-tag">&lt;/<span class="hljs-name">label</span>&gt;</span><span class="hljs-tag">&lt;<span class="hljs-name">br</span> /&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">label</span>&gt;</span>Email: <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"text"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"email"</span> /&gt;</span><span class="hljs-tag">&lt;/<span class="hljs-name">label</span>&gt;</span><span class="hljs-tag">&lt;<span class="hljs-name">br</span> /&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">label</span>&gt;</span>Home page: <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"text"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"homepage"</span> /&gt;</span><span class="hljs-tag">&lt;/<span class="hljs-name">label</span>&gt;</span><span class="hljs-tag">&lt;<span class="hljs-name">br</span> /&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">label</span>&gt;</span>Street Address: <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"text"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"address1"</span> /&gt;</span><span class="hljs-tag">&lt;/<span class="hljs-name">label</span>&gt;</span><span class="hljs-tag">&lt;<span class="hljs-name">br</span> /&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">label</span>&gt;</span>City: <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"text"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"address2"</span> /&gt;</span><span class="hljs-tag">&lt;/<span class="hljs-name">label</span>&gt;</span><span class="hljs-tag">&lt;<span class="hljs-name">br</span> /&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">label</span>&gt;</span>Region: <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"text"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"city"</span> /&gt;</span><span class="hljs-tag">&lt;/<span class="hljs-name">label</span>&gt;</span><span class="hljs-tag">&lt;<span class="hljs-name">br</span> /&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">label</span>&gt;</span>Postcode: <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"text"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"postcode"</span> /&gt;</span><span class="hljs-tag">&lt;/<span class="hljs-name">label</span>&gt;</span><span class="hljs-tag">&lt;<span class="hljs-name">br</span> /&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"submit"</span> /&gt;</span>
<span class="hljs-tag">&lt;/<span class="hljs-name">form</span>&gt;</span></code></span></pre>


<p>Warum nicht gleich das Formular als hCard-From aufbauen?</p>


<pre class="wp-block-code"><span><code class="hljs language-xml"><span class="hljs-tag">&lt;<span class="hljs-name">form</span> <span class="hljs-attr">action</span>=<span class="hljs-string">"#"</span> <span class="hljs-attr">method</span>=<span class="hljs-string">"post"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"vcard"</span> &gt;</span>
  <span class="hljs-tag">&lt;<span class="hljs-name">fieldset</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"fn"</span>&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">legend</span>&gt;</span>Name<span class="hljs-tag">&lt;/<span class="hljs-name">legend</span>&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">label</span> <span class="hljs-attr">for</span>=<span class="hljs-string">"given-name"</span>&gt;</span>Vorname:<span class="hljs-tag">&lt;/<span class="hljs-name">label</span>&gt;</span>
      <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"text"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"given-name"</span> /&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">label</span> <span class="hljs-attr">for</span>=<span class="hljs-string">"family-name"</span>&gt;</span>Nachname:<span class="hljs-tag">&lt;/<span class="hljs-name">label</span>&gt;</span>
      <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"text"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"family-name"</span> /&gt;</span>
  <span class="hljs-tag">&lt;/<span class="hljs-name">fieldset</span>&gt;</span>
  <span class="hljs-tag">&lt;<span class="hljs-name">label</span> <span class="hljs-attr">for</span>=<span class="hljs-string">"email"</span>&gt;</span>Email:<span class="hljs-tag">&lt;/<span class="hljs-name">label</span>&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"text"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"email"</span> /&gt;</span>
  <span class="hljs-tag">&lt;<span class="hljs-name">label</span> <span class="hljs-attr">for</span>=<span class="hljs-string">"url"</span>&gt;</span>Homepage:<span class="hljs-tag">&lt;/<span class="hljs-name">label</span>&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"text"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"url"</span> /&gt;</span>
  <span class="hljs-tag">&lt;<span class="hljs-name">fieldset</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"adr"</span>&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">legend</span>&gt;</span>Adresse<span class="hljs-tag">&lt;/<span class="hljs-name">legend</span>&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">label</span> <span class="hljs-attr">for</span>=<span class="hljs-string">"street-address"</span>&gt;</span>Straße:<span class="hljs-tag">&lt;/<span class="hljs-name">label</span>&gt;</span>
      <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"text"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"street-address"</span> /&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">label</span> <span class="hljs-attr">for</span>=<span class="hljs-string">"locality"</span>&gt;</span>Stadt:<span class="hljs-tag">&lt;/<span class="hljs-name">label</span>&gt;</span>
      <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"text"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"locality"</span> /&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">label</span> <span class="hljs-attr">for</span>=<span class="hljs-string">"region"</span>&gt;</span>Region:<span class="hljs-tag">&lt;/<span class="hljs-name">label</span>&gt;</span>
      <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"text"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"region"</span> /&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">label</span> <span class="hljs-attr">for</span>=<span class="hljs-string">"postal-code"</span>&gt;</span>Postleitzahl:<span class="hljs-tag">&lt;/<span class="hljs-name">label</span>&gt;</span>
      <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"text"</span> <span class="hljs-attr">id</span>=<span class="hljs-string">"postal-code"</span> /&gt;</span>
  <span class="hljs-tag">&lt;/<span class="hljs-name">fieldset</span>&gt;</span>
  <span class="hljs-tag">&lt;<span class="hljs-name">input</span> <span class="hljs-attr">type</span>=<span class="hljs-string">"submit"</span> /&gt;</span>
<span class="hljs-tag">&lt;/<span class="hljs-name">form</span>&gt;</span></code></span></pre>


<p>Das Einheitliche Format für Ein- (Formular) und Ausgabe (Microformats) hätte zur Folge, dass keine aufwendigen Mapper (wie z.B. <a href="https://notiz.blog/2008/03/28/hcard-mapper/">hCard-Mapper</a>) mehr nötig wären um ein Formular per <a href="http://microformats.org/wiki/hCard">hCard</a> auszufüllen&#8230;</p>



<p>Schöne neue Welt 🙂</p>
<p>You are a master of efficiency! By using RSS, you save time and avoid distractions. 👏</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/06/28/hforms-semantische-formulare/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Microformats API in Firefox3-Erweiterungen nutzen</title>
		<link>https://notiz.blog/2008/06/04/microformats-api-in-firefox3-erweiterungen-nutzen/</link>
					<comments>https://notiz.blog/2008/06/04/microformats-api-in-firefox3-erweiterungen-nutzen/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Wed, 04 Jun 2008 18:46:21 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[Addon]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[FediBlog]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[hCard]]></category>
		<category><![CDATA[Microformats]]></category>
		<category><![CDATA[Mikroformate]]></category>
		<category><![CDATA[WordPress]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=896</guid>

					<description><![CDATA[Rob Crowther hat für IBM developerWorks eine großartige Anleitung (mit Beispiel-Code) geschrieben, wie man die Microformats API in Firefox3 Extensions nutzen kann. The upcoming Firefox 3.0 release has built-in support for microformats in the form of an API that you can access from a Firefox extension. In this tip, you follow a simple example of [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p><a href="https://web.archive.org/web/20130516000806/http://www.ibm.com:80/developerworks/xml/library/x-tipffoxmicroapi/">Rob Crowther</a> hat für <a href="http://www.ibm.com/developerworks/">IBM developerWorks</a> eine großartige Anleitung (mit Beispiel-Code) geschrieben, <a href="https://web.archive.org/web/20130516000806/http://www.ibm.com:80/developerworks/xml/library/x-tipffoxmicroapi/">wie man die Microformats API in Firefox3 Extensions nutzen kann</a>.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p>The upcoming Firefox 3.0 release has built-in support for microformats in the form of an API that you can access from a Firefox extension. In this tip, you follow a simple example of how to use this API from within your extension code. You take a skeleton Hello World extension and give it the ability to store an hCard from any Web page and then use that stored hCard to populate a Web form.</p></blockquote>



<p>Die <a href="https://web.archive.org/web/20130516000806/http://www.ibm.com:80/developerworks/xml/library/x-tipffoxmicroapi/">Beispiel-Erweiterung</a> von Crowther nutzt hCard-Informationen um ein (im Beispiel beiliegendes) Profil-Formular auszufüllen.</p>



<div class="wp-block-image"><figure class="aligncenter"><img decoding="async" src="https://notiz.blog/wp-content/uploads/2008/06/hcardformfiller.jpg" alt="hcardformfiller.jpg"/></figure></div>



<p>Ablauf: Zuerst auf ne Seite mit hCard, linken Knopf drücken, dann auf das Fromular und rechten Knopf drücken.</p>



<h4 class="wp-block-heading">hCardFormFiller für WordPress</h4>



<p>Um dem Beispiel etwas mehr Nutzen zu geben, habe ich es testweise für das WordPress Kommentarformular umgeschrieben. Die Einzige notwendige Änderung ist, folgenden Code in der <code>overlay.js</code>:</p>


<pre class="wp-block-code"><span><code class="hljs language-javascript">onToolbarButtonPasteCommand: <span class="hljs-function"><span class="hljs-keyword">function</span>(<span class="hljs-params">e</span>) </span>{
 <span class="hljs-keyword">if</span> (<span class="hljs-keyword">this</span>.uF.fn) {
   content.document.getElementById(<span class="hljs-string">'name'</span>).value = <span class="hljs-keyword">this</span>.uF.fn;
   content.document.getElementById(<span class="hljs-string">'email'</span>).value = <span class="hljs-keyword">this</span>.uF.email&#91;<span class="hljs-number">0</span>].value;
   content.document.getElementById(<span class="hljs-string">'homepage'</span>).value = <span class="hljs-keyword">this</span>.uF.url&#91;<span class="hljs-number">0</span>];
   content.document.getElementById(<span class="hljs-string">'address1'</span>).value = <span class="hljs-keyword">this</span>.uF.adr&#91;<span class="hljs-number">0</span>]&#91;<span class="hljs-string">'street-address'</span>];
   content.document.getElementById(<span class="hljs-string">'address2'</span>).value = <span class="hljs-keyword">this</span>.uF.adr&#91;<span class="hljs-number">0</span>].locality;
   content.document.getElementById(<span class="hljs-string">'city'</span>).value = <span class="hljs-keyword">this</span>.uF.adr&#91;<span class="hljs-number">0</span>].region;
   content.document.getElementById(<span class="hljs-string">'postcode'</span>).value = <span class="hljs-keyword">this</span>.uF.adr&#91;<span class="hljs-number">0</span>]&#91;<span class="hljs-string">'postal-code'</span>];
 }
}</code></span></pre>


<p>durch folgenden Code:</p>


<pre class="wp-block-code"><span><code class="hljs language-javascript">onToolbarButtonPasteCommand: <span class="hljs-function"><span class="hljs-keyword">function</span>(<span class="hljs-params">e</span>) </span>{
 <span class="hljs-keyword">if</span> (<span class="hljs-keyword">this</span>.uF.fn) {
   content.document.getElementById(<span class="hljs-string">'author'</span>).value = <span class="hljs-keyword">this</span>.uF.fn;
   content.document.getElementById(<span class="hljs-string">'email'</span>).value = <span class="hljs-keyword">this</span>.uF.email&#91;<span class="hljs-number">0</span>].value;
   content.document.getElementById(<span class="hljs-string">'url'</span>).value = <span class="hljs-keyword">this</span>.uF.url&#91;<span class="hljs-number">0</span>];
 }
}</code></span></pre>


<p>zu ersetzen und das war&#8217;s. Jetzt könnt ihr mit einer <a href="http://microformats.org/wiki/hCard">hCard</a> bewaffnet losziehen und WordPress Blogs zuspammen 🙂</p>



<p>Wer das Addon mal ausprobieren möchte kann sich den angepassten <a href="https://notiz.blog/wp-content/uploads/2008/06/hcardformfiller.xpi">hCardFormFiller for WordPress</a> runterladen&#8230; den original Code findet man <a href="https://web.archive.org/web/20130516000806/http://www.ibm.com:80/developerworks/xml/library/x-tipffoxmicroapi/">hier</a>.</p>



<p><a href="https://notiz.blog/2008/05/21/wo-sind-die-microformats-im-firefox-3/">Nachdem die Microformats kein <abbr title="User Interface">UI</abbr> spendiert bekommen haben</a>, gibt es vielleicht demnächst einige Addons die diese Lücke füllen werden.</p>



<p>Interessante Links:</p>



<ul class="wp-block-list">
	<li><a href="https://web.archive.org/web/20130516000806/http://www.ibm.com:80/developerworks/xml/library/x-tipffoxmicroapi/">Use the new microformats API in your Firefox 3.0 Extensions</a></li>
	<li><a href="https://web.archive.org/web/20080701113514/http://www.kaply.com/weblog/2008/05/20/where-are-the-microformat-in-firefox-3/">Where are the microformats in Firefox 3?</a></li>
</ul>
<p>Hey there, RSS reader! You’re cool. Keep being awesome! 😎</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/06/04/microformats-api-in-firefox3-erweiterungen-nutzen/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Wo sind die Microformats im Firefox 3</title>
		<link>https://notiz.blog/2008/05/21/wo-sind-die-microformats-im-firefox-3/</link>
					<comments>https://notiz.blog/2008/05/21/wo-sind-die-microformats-im-firefox-3/#comments</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Wed, 21 May 2008 14:50:56 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[FediBlog]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Firefox 3]]></category>
		<category><![CDATA[Microformats]]></category>
		<category><![CDATA[Microformats API]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=868</guid>

					<description><![CDATA[Jetzt wo der Release Candidate 1 von Firefox 3 erhältlich ist, fragen sich einige wo denn die &#8222;versprochenen&#8220; Microformats sind. Michael Kaply, der Macher von Operator (und meines Wissens auch der Mann hinter der Firefox-Microformats-API) versucht diese Frage in seinem Weblog zu beantworten: The answer is that there is a microformats API in Firefox 3, [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>Jetzt wo der <a href="https://web.archive.org/web/20150928191434/http://webstandard.kulando.de/post/2008/05/18/ersten_release_candidate_von_firefox_3_downloaden">Release Candidate 1 von Firefox 3</a> erhältlich ist, <a href="https://notiz.blog/2007/10/26/microformats-verarbeitung-in-firefox-3/#comment-6865">fragen sich einige</a> wo denn die &#8222;<a href="https://notiz.blog/2007/10/26/microformats-verarbeitung-in-firefox-3/">versprochenen</a>&#8220; Microformats sind. Michael Kaply, der Macher von Operator (und meines Wissens auch der Mann hinter der <a href="https://web.archive.org/web/20080819033015/http://developer.mozilla.org:80/en/docs/Category:Microformats">Firefox-Microformats-API</a>) versucht diese Frage in seinem <a href="https://web.archive.org/web/20080701113514/http://www.kaply.com/weblog/2008/05/20/where-are-the-microformat-in-firefox-3/">Weblog</a> zu beantworten:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>The answer is that there is a microformats API in Firefox 3, but unfortunately there is nothing available in the UI for this release.[&#8230;]</p>
	<p>The primary reason that microformats aren’t exposed in the Firefox UI is that there was never any agreement as to how to expose them.</p>
</blockquote>



<p>Da hatte ich <a href="https://notiz.blog/2007/10/26/microformats-verarbeitung-in-firefox-3/#comment-6866">damals</a> ja gar nicht so unrecht:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>Ich bin mir nicht 100%ig sicher, aber ich glaub es wird nur eine API für das Parsen von Microformats gestellt, da es das Operator Plugin ja auch für Firefox 3 gibt.<br/> Wie das mit den oben genannten Selektoren aussieht weiß ich auch nicht.</p>
</blockquote>



<p>Wer sich für das Thema <a href="http://www.mozilla.org/products/firefox/">Firefox</a>, <a href="http://microformats.org">Microformats</a> und die Zukunft von <a href="https://web.archive.org/web/20101120155908/http://kaply.com:80/weblog/operator/">Operator</a> interessiert, sollte sich einfach mal Kaplys <a href="https://web.archive.org/web/20080701113514/http://www.kaply.com/weblog/2008/05/20/where-are-the-microformat-in-firefox-3/">kompletten Artikel</a> durchlesen.</p>
<p>Congratulations on being an RSS reader! You are part of an elite group of people who know how to stay updated in style.</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/05/21/wo-sind-die-microformats-im-firefox-3/feed/</wfw:commentRss>
			<slash:comments>4</slash:comments>
		
		
			</item>
		<item>
		<title>Operator Userscripts zukünftig im OpenService XML-Format</title>
		<link>https://notiz.blog/2008/04/30/operator-userscripts-zukuenftig-im-openservice-xml-format/</link>
					<comments>https://notiz.blog/2008/04/30/operator-userscripts-zukuenftig-im-openservice-xml-format/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Wed, 30 Apr 2008 10:47:38 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[Addon]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Microformats]]></category>
		<category><![CDATA[Operator]]></category>
		<category><![CDATA[Userscripts]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=838</guid>

					<description><![CDATA[Michael Kaply plant einige interessante neue Features für Operator (Firefox Microformats-Addon). Um User-Skripte vor der Installation nicht erst herunterladen zu müssen, sollen die Skripte von JS auf XML umgestellt werden. Als Basis für das XML-Modell wurde das, von Microsoft spezifizierte, OpenService Format angedacht. So könnte ein Script z.B. aussehen: Weitere Gedanken zu der &#8222;OpenService extension [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p><a href="https://mike.kaply.com/">Michael Kaply</a> plant einige interessante <a href="https://web.archive.org/web/20100926101724/http://kaply.com/weblog/2008/04/29/update-on-activities-microformats-and-operator/">neue Features für Operator</a> (Firefox Microformats-Addon).</p>



<p>Um User-Skripte vor der Installation nicht erst herunterladen zu müssen, sollen die Skripte von <abbr title="Java Script">JS</abbr> auf XML umgestellt werden. Als Basis für das XML-Modell wurde das, von Microsoft spezifizierte, <a href="https://web.archive.org/web/20080924143732/http://msdn.microsoft.com:80/en-us/library/cc304072(VS.85).aspx">OpenService Format</a> angedacht.</p>



<p>So könnte ein Script z.B. aussehen:</p>


<pre class="wp-block-code"><span><code class="hljs language-xml"><span class="hljs-meta">&lt;?xml version="1.0" encoding="utf-8"?&gt;</span>
<span class="hljs-tag">&lt;<span class="hljs-name">openServiceDescription</span>
  <span class="hljs-attr">xmlns</span>=<span class="hljs-string">"http://www.microsoft.com/schemas/openservicedescription/1.0"</span>&gt;</span>
  <span class="hljs-tag">&lt;<span class="hljs-name">display</span>&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">name</span>&gt;</span>Find with MapQuest<span class="hljs-tag">&lt;/<span class="hljs-name">name</span>&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">icon</span>&gt;</span>http://www.mapquest.com/favicon.ico<span class="hljs-tag">&lt;/<span class="hljs-name">icon</span>&gt;</span>
  <span class="hljs-tag">&lt;/<span class="hljs-name">display</span>&gt;</span>
  <span class="hljs-tag">&lt;<span class="hljs-name">homepageUrl</span>&gt;</span>http://www.mapquest.com<span class="hljs-tag">&lt;/<span class="hljs-name">homepageUrl</span>&gt;</span>
  <span class="hljs-tag">&lt;<span class="hljs-name">activity</span> <span class="hljs-attr">category</span>=<span class="hljs-string">"Map"</span>&gt;</span>
    <span class="hljs-tag">&lt;<span class="hljs-name">activityAction</span> <span class="hljs-attr">context</span>=<span class="hljs-string">"hCard.adr"</span>&gt;</span>
      <span class="hljs-tag">&lt;<span class="hljs-name">execute</span> <span class="hljs-attr">method</span>=<span class="hljs-string">"get"</span>
        <span class="hljs-attr">action</span>=<span class="hljs-string">"http://www.mapquest.com/maps/map.adp?searchtype=address"</span>&gt;</span>
        <span class="hljs-tag">&lt;<span class="hljs-name">parameter</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"address"</span> <span class="hljs-attr">value</span>=<span class="hljs-string">"{street-address}"</span>/&gt;</span>
        <span class="hljs-tag">&lt;<span class="hljs-name">parameter</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"city"</span> <span class="hljs-attr">value</span>=<span class="hljs-string">"{locality}"</span>/&gt;</span>
        <span class="hljs-tag">&lt;<span class="hljs-name">parameter</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"state"</span> <span class="hljs-attr">value</span>=<span class="hljs-string">"{region}"</span>/&gt;</span>
        <span class="hljs-tag">&lt;<span class="hljs-name">parameter</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"zipcode"</span> <span class="hljs-attr">value</span>=<span class="hljs-string">"{postal-code}"</span>/&gt;</span>
        <span class="hljs-tag">&lt;<span class="hljs-name">parameter</span> <span class="hljs-attr">name</span>=<span class="hljs-string">"country"</span> <span class="hljs-attr">value</span>=<span class="hljs-string">"{country-name}"</span>/&gt;</span>
      <span class="hljs-tag">&lt;/<span class="hljs-name">execute</span>&gt;</span>
    <span class="hljs-tag">&lt;/<span class="hljs-name">activityAction</span>&gt;</span>
  <span class="hljs-tag">&lt;/<span class="hljs-name">activity</span>&gt;</span>
<span class="hljs-tag">&lt;/<span class="hljs-name">openServiceDescription</span>&gt;</span></code></span></pre>


<p>Weitere Gedanken zu der <em>&#8222;OpenService extension for microformats contexts&#8220;</em> oder <em>&#8222;Automatic Discovery&#8220;</em> findet ihr im <a href="http://microformats.org/wiki/OpenService_Extensions">Microformats Wiki</a></p>
<p>Congratulations on being an RSS reader! You are part of an elite group of people who know how to stay updated in style.</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/04/30/operator-userscripts-zukuenftig-im-openservice-xml-format/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Firefox HTML Validator mit RDFa &#8211; Support</title>
		<link>https://notiz.blog/2008/04/24/firefox-html-validator-mit-rdfa-support/</link>
					<comments>https://notiz.blog/2008/04/24/firefox-html-validator-mit-rdfa-support/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Thu, 24 Apr 2008 07:01:04 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[Addon]]></category>
		<category><![CDATA[FediBlog]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[HTML Validator]]></category>
		<category><![CDATA[RDFa]]></category>
		<category><![CDATA[W3C]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=832</guid>

					<description><![CDATA[Nachdem sich Benjamin Nowack gestern (via twitter) noch gefragt hat ob es möglich ist, einem Firefox-HTML-Validator RDFa beizubringen&#8230; wondering if the FF HTML Validator extension could be hacked to support RDFa. Basic QA is a bit too complicated with only the w3.org checker &#8230;hat er ihn heute auf seiner Webseite veröffentlicht 🙂 Benjamin Nowacks angepasster [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>Nachdem sich <a href="https://web.archive.org/web/20211219062605/http://bnode.org/">Benjamin Nowack</a> gestern (<a href="http://twitter.com/bengee/statuses/795012932">via twitter</a>) noch gefragt hat ob es möglich ist, einem Firefox-<a href="https://notiz.blog/2008/03/02/rdfa-in-xhtml-10-verwenden/">HTML-Validator RDFa</a> beizubringen&#8230;</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow"><p>wondering if the FF HTML Validator extension could be hacked to support RDFa. Basic QA is a bit too complicated with only the w3.org checker</p></blockquote>



<p>&#8230;hat er ihn heute auf seiner Webseite veröffentlicht 🙂</p>



<p>Benjamin Nowacks angepasster Validator basiert auf der <a href="https://addons.mozilla.org/de/firefox/addon/html-validator/">HTML Validator Extension for Firefox</a> von Marc Gueury und funktioniert leider vorerst nur unter Windows.</p>



<p><a href="https://web.archive.org/web/20210514124903/https://www.bnode.org/blog/2008/04/23/adding-partial-rdfa-support-to-the-firefox-html-validator-extension">Zum Download</a></p>



<p>Weitere sehr interessante Projekte von Herrn Nowack die man sich auch unbedingt anschauen sollte:</p>



<ul class="wp-block-list"><li><a href="https://web.archive.org/web/20080912151917/http://arc.semsol.org/">ARC</a> &#8211; Easy RDF and SPARQL for LAMP systems</li><li><a href="https://web.archive.org/web/20080618010058/http://sparqlbot.semsol.org/">SPARQLBot</a> &#8211; Your Semantic Web Command Line</li></ul>
<p>Hey there, RSS reader! You’re one of a special few, choosing this old-school yet awesome way of staying informed. Kudos!</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/04/24/firefox-html-validator-mit-rdfa-support/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Webslices und Activities für Firefox</title>
		<link>https://notiz.blog/2008/04/18/webslices-und-activities-fuer-firefox/</link>
					<comments>https://notiz.blog/2008/04/18/webslices-und-activities-fuer-firefox/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Fri, 18 Apr 2008 16:14:54 +0000</pubDate>
				<category><![CDATA[nur mal kurz]]></category>
		<category><![CDATA[Activities]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[IE8]]></category>
		<category><![CDATA[Webslices]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=820</guid>

					<description><![CDATA[Webslices und Activities, zwei neue Features im IE8, gibt es jetzt auch als Firefox-Addons: Microsoft Activities for Firefox von Michael Kaply Webchunks (Webslices for Firefox) von Daniel Glazman]]></description>
										<content:encoded><![CDATA[
<p><a href="https://notiz.blog/2008/03/06/ueber-ie8s-webslices-und-hatom/">Webslices</a> und <a href="https://web.archive.org/web/20080327143806/http://ie.microsoft.com/activities/en-en/Default.aspx">Activities</a>, zwei neue Features im <abbr title="Internet Explorer">IE</abbr>8, gibt es jetzt auch als Firefox-Addons:</p>



<ul class="wp-block-list">
	<li><a href="https://web.archive.org/web/20101121014503/http://www.kaply.com:80/weblog/?s=Microsoft+Activities">Microsoft Activities for Firefox</a> von Michael Kaply</li>
	<li><a href="https://web.archive.org/web/20080912091640/http://www.glazman.org/weblog/dotclear/index.php?q=webchunks">Webchunks</a> (Webslices for Firefox) von Daniel Glazman</li>
</ul>
<p>RSS readers like you are the unsung heroes of the internet. Keep up the good work!</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/04/18/webslices-und-activities-fuer-firefox/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Operator 0.9 Final</title>
		<link>https://notiz.blog/2008/03/18/operator-09-final/</link>
					<comments>https://notiz.blog/2008/03/18/operator-09-final/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Tue, 18 Mar 2008 08:03:32 +0000</pubDate>
				<category><![CDATA[nur mal kurz]]></category>
		<category><![CDATA[Open Web]]></category>
		<category><![CDATA[Addon]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Microformats]]></category>
		<category><![CDATA[Opterator]]></category>
		<category><![CDATA[RDFa]]></category>
		<guid isPermaLink="false">http://notizblog.org/2008/03/18/operator-09-final/</guid>

					<description><![CDATA[Operator 0.9 ist in der finalen Version erhältlich. Neu in dieser Version ist unter anderem: Songbird support! A new RDFa parser based on the new spec (pages will need to be updated) mehr&#8230;]]></description>
										<content:encoded><![CDATA[
<p><a href="https://web.archive.org/web/20120630183520/http://mike.kaply.com/2008/03/17/operator-09-is-available/">Operator 0.9 ist in der finalen Version erhältlich</a>. Neu in dieser Version ist unter anderem:</p>



<ul class="wp-block-list">
	<li>Songbird support!</li>
	<li>A new RDFa parser based on the new spec (pages will need to be updated)</li>
	<li><a href="https://web.archive.org/web/20120630183520/http://mike.kaply.com/2008/03/17/operator-09-is-available/">mehr&#8230;</a></li>
</ul>
<p>Hey there, RSS reader! You’re one of a special few, choosing this old-school yet awesome way of staying informed. Kudos!</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/03/18/operator-09-final/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Operator 0.9g</title>
		<link>https://notiz.blog/2008/02/29/operator-09g/</link>
					<comments>https://notiz.blog/2008/02/29/operator-09g/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Fri, 29 Feb 2008 20:36:15 +0000</pubDate>
				<category><![CDATA[nur mal kurz]]></category>
		<category><![CDATA[Open Web]]></category>
		<category><![CDATA[Addon]]></category>
		<category><![CDATA[Firefox]]></category>
		<category><![CDATA[Microformats]]></category>
		<category><![CDATA[Operator]]></category>
		<guid isPermaLink="false">http://notizblog.org/2008/02/29/operator-09g/</guid>

					<description><![CDATA[Es gibt seit heute einen Release Candidate von Operator 0.9. Neben Performance-Verbesserungen und einigen Fixes wurde hauptsächlich die Erkennung von &#8222;Nested Microformats&#8220; verbessert.]]></description>
										<content:encoded><![CDATA[
<p>Es gibt seit heute einen Release Candidate von <a href="https://web.archive.org/web/20080509145953/http://www.kaply.com/weblog/2008/02/29/operator-09g-release-candidate-available/">Operator 0.9</a>. Neben Performance-Verbesserungen und einigen Fixes wurde hauptsächlich die Erkennung von &#8222;Nested Microformats&#8220; verbessert.</p>
<p>Hey there, RSS reader! You’re one of a special few, choosing this old-school yet awesome way of staying informed. Kudos!</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/02/29/operator-09g/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
