<?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>Building-Blocks &#8211; notizBlog</title>
	<atom:link href="https://notiz.blog/tag/building-blocks/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, 28 Oct 2021 11:44:30 +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>Building-Blocks &#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/building-blocks/feed/"/>
<atom:link rel="search" type="application/opensearchdescription+xml" title="Search notizBlog" href="https://notiz.blog/wp-api/opensearch/1.1/document" />	<item>
		<title>Microformats und die Portable Contacts API</title>
		<link>https://notiz.blog/2008/10/17/microformats-und-die-portable-contacts-api/</link>
					<comments>https://notiz.blog/2008/10/17/microformats-und-die-portable-contacts-api/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Fri, 17 Oct 2008 17:13:48 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[Building-Blocks]]></category>
		<category><![CDATA[hCard]]></category>
		<category><![CDATA[hResume]]></category>
		<category><![CDATA[Microformats]]></category>
		<category><![CDATA[Portable Contacts]]></category>
		<category><![CDATA[ufXtract]]></category>
		<category><![CDATA[XFN]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=1209</guid>

					<description><![CDATA[Dass sich das Portable Contacts Schema trotz der Aussage: Third, we&#8217;re reusing existing standards wherever possible, including vCard, OpenSocial, XRDS-Simple, OAuth, etc. von dem des v/hCard Schema unterscheidet, habe ich ja schon vor einigen Wochen erläutert: Schade dass die vCard nicht zu 100% übernommen wurde… sonst hätte man ohne größere Änderungen auch die JSON-Serialisierte hCard [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>Dass sich das <a href="https://web.archive.org/web/20080927040423/http://portablecontacts.net/draft-spec.html#structure">Portable Contacts Schema</a> trotz der Aussage:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>Third, we&#8217;re reusing existing standards wherever possible, including vCard, OpenSocial, XRDS-Simple, OAuth, etc.</p>
</blockquote>



<p>von dem des <a href="http://microformats.org/wiki/jcard">v/hCard Schema</a> unterscheidet, habe ich ja schon <a href="https://notiz.blog/2008/08/08/portable-contacts-schicker-als-ich-dachte/#portable-microformats">vor einigen Wochen erläutert</a>:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>Schade dass die vCard nicht zu 100% übernommen wurde… sonst hätte man ohne größere Änderungen auch die JSON-Serialisierte hCard (jCard) in den Prozess integrieren können. Spannend wäre es vor allem für Services wie Twitter, die das Freundesnetzwerk sowieso mit hCards auszeichnen.</p>
</blockquote>



<p>Aber das schöne an Standards ist, dass sie sich ohne großen Aufwand in andere transformieren lassen. <a href="https://web.archive.org/web/20120617182505/http://lab.madgex.com:80/">Magdex</a> (die Firma hinter <a href="https://web.archive.org/web/20120629201057/http://lab.madgex.com:80/ufxtract/">UfXtract</a> und <a href="">OAuth.net</a>) bietet eine <a href="https://web.archive.org/web/20120629203231/http://lab.madgex.com:80/portablecontacts/">Reihe dieser Transformatoren</a> um z.B. <a href="https://web.archive.org/web/20120629201053/http://lab.madgex.com:80/portablecontacts/hcardtopoco.aspx">hCards</a>, <a href="https://web.archive.org/web/20120629195117/http://lab.madgex.com:80/portablecontacts/hcardxfntopoco.aspx">hCards + XFN</a> oder <a href="https://web.archive.org/web/20120629201640/http://lab.madgex.com:80/portablecontacts/hresumetopoco.aspx">hResumes</a> in das <em>Portable Contacts</em> &#8211; Format zu bringen.</p>



<p>&#8230;jetzt das ganze nur noch mit <a href="https://web.archive.org/web/20080927040423/http://portablecontacts.net/draft-spec.html#anchor10">OAuth</a> schützen und fertig ist die <em>Portable Contacts</em> API 🙂</p>



<p>(<a href="https://web.archive.org/web/20101105035301/http://www.glennjones.net:80/Post/838/MicroformatstoPortableContactsAPIconverters.htm">via</a>)</p>
<p>Hey there, RSS reader! You’re cool. Keep being awesome! 😎</p>]]></content:encoded>
					
					<wfw:commentRss>https://notiz.blog/2008/10/17/microformats-und-die-portable-contacts-api/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Interessante Portable-Contacts ankündigungen</title>
		<link>https://notiz.blog/2008/09/18/interessante-portable-contacts-ankuendigungen/</link>
					<comments>https://notiz.blog/2008/09/18/interessante-portable-contacts-ankuendigungen/#respond</comments>
		
		<dc:creator><![CDATA[Matthias Pfefferle]]></dc:creator>
		<pubDate>Thu, 18 Sep 2008 08:23:45 +0000</pubDate>
				<category><![CDATA[Open Web]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[Building-Blocks]]></category>
		<category><![CDATA[myOpenID]]></category>
		<category><![CDATA[Open Standard]]></category>
		<category><![CDATA[OpenID]]></category>
		<category><![CDATA[Plaxo]]></category>
		<category><![CDATA[Portable Contacts]]></category>
		<category><![CDATA[PortableContacts]]></category>
		<guid isPermaLink="false">http://notizblog.org/?p=1157</guid>

					<description><![CDATA[Plaxo setzt voll auf den neuen (großen?) Building-Block Portable Contacts (Portable Contacts is now Plaxo&#8217;s primary API): We&#8217;ve been early adopters and evangelists for several of these building blocks, including OpenID, OAuth, OpenSocial, and microformats. And recently we&#8217;ve also helped lead the charge to build another key piece of the &#8222;open stack&#8220;: a common API [&#8230;]]]></description>
										<content:encoded><![CDATA[
<p>Plaxo setzt voll auf den neuen (<a href="https://notiz.blog/2008/09/11/portable-contacts-der-neue-grosse-building-block/">großen?</a>) Building-Block <em>Portable Contacts</em> (<a href="https://web.archive.org/web/20090129223952/http://blog.plaxo.com:80/archives/2008/09/portable_contac_1.html">Portable Contacts is now Plaxo&#8217;s primary API</a>):</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>We&#8217;ve been early adopters and evangelists for several of these building blocks, including OpenID, OAuth, OpenSocial, and microformats. And recently we&#8217;ve also helped lead the charge to build another key piece of the &#8222;open stack&#8220;: a common API standard for accessing address book, profile, and friends-list data called &#8222;Portable Contacts&#8220;.</p>
</blockquote>



<p>Die <a href="https://web.archive.org/web/20120228152140/http://www.plaxo.com:80/api">API-Section von Plaxo</a> weist jetzt eine beachtliche Anzahl an offenen Standards auf:</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>We&#8217;ve revamped Plaxo&#8217;s developer section to focus primarily on the open building blocks we&#8217;re using. Starting now, developers should consider OAuth and Portable Contacts the primary way to access profile, address book, and pulse connections data from Plaxo.</p>
</blockquote>



<p>Vorbildlich!</p>



<p>Eine weitere Ankündigung (via Newsletter) kommt vom OpenID-Provider <a href="https://web.archive.org/web/20140529235912/https://www.myopenid.com/">myOpenID</a>, der (in Person von <a href="https://web.archive.org/web/20080120192815/http://brianellin.com/">Brian Ellin</a> von JanRain) ja schon auf dem <a href="https://notiz.blog/2008/09/11/portablecontacts-hacks/">PortableContacts Hackathon</a> eine umfassende Demo zum besten geben konnte.</p>



<blockquote class="wp-block-quote is-layout-flow wp-block-quote-is-layout-flow">
	<p>Portable Contacts is an emerging standard for transferring profile data and social connections across websites. Look for upcoming support of this new standard in myOpenID!</p>
</blockquote>



<p>Dieses Feature würde mich dann doch davon abhalten <a href="https://notiz.blog/2008/09/17/wordpress-wird-openid-provider/">mein eigener OpenID-Provider</a> zu sein 🙂</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/09/18/interessante-portable-contacts-ankuendigungen/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
