<?xml version="1.0" encoding="utf-8"?>
<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"
	>

<channel>
	<title>2idi i-broker weblog</title>
	<atom:link href="http://blog.2idi.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.2idi.com</link>
	<description>giving people control of their identity</description>
	<pubDate>Tue, 11 Nov 2008 22:53:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
	<language>en</language>
			<item>
		<title>Past and Future</title>
		<link>http://blog.2idi.com/2005/12/04/past-and-future/</link>
		<comments>http://blog.2idi.com/2005/12/04/past-and-future/#comments</comments>
		<pubDate>Sun, 04 Dec 2005 23:56:50 +0000</pubDate>
		<dc:creator>=victor.grey</dc:creator>
		
		<category><![CDATA[Identity Services]]></category>

		<guid isPermaLink="false">http://blog.2idi.com/?p=11</guid>
		<description><![CDATA[October 25th was the one year milestone for the Early Global Services (EGS) Program, the first i-name registry and i-broker service. On October 25th, 2004 at 17:08:02 PDT the very first global i-name (=mmell) was registered, followed eleven seconds later by =victor.grey, and 38 seconds after that by =fen.labalme. Three other i-names were also registered [...]]]></description>
			<content:encoded><![CDATA[<p>October 25th was the one year milestone for the Early Global Services (EGS) Program, the first i-name registry and i-broker service. On October 25th, 2004 at 17:08:02 PDT the very first global i-name (=mmell) was registered, followed eleven seconds later by =victor.grey, and 38 seconds after that by =fen.labalme. Three other i-names were also registered in that first minute.</p>
<p>With the new year coming up, I&#8217;m feeling motivated to blog a bit about where I see 2idi going in the next year. The first quarter of next year will see the launch of the &#8220;Global Registry Services for I-Names and I-Numbers&#8221; (GRS) by Cordance and Neustar, under the governance of XDI.org. At that point, the EGS program will officially come to an end, and global i-name resolution will be transferred to the Neustar authority servers. 2idi plans to continue to offer i-broker services to the EGS registrants, and will very likely be grandfathered in as a global i-names accredited registrar.</p>
<p>Meanwhile, under the covers changes have been brewing. We have had a year of real life experience with i-names, and we&#8217;ve come to some tentative conclusions. The most important of these conclusions is that selling identity services to end users is still a very immature market, and may take longer than we thought to become viable. Meanwhile there are compelling opportunities in the immediate future, through which we will develop required infrastructure, while at the same time providing much needed services, educating and inspiring end users, and sustaining our business.</p>
<p>The real interest in identity services that we are seeing right now is from organizations and businesses who see it as a means to accomplish two things. The first serves an immediate need, to glue web service applications together within and across organizations.</p>
<blockquote><p>Imagine that you are a non-profit organization that has created a website where you can sign up members, and allow them to log in and create a personal profile. Now you wish to provide them with collaboration tools - blogs, wiki, mailing lists, etc. There are many excellent open source versions of these tools, so it would be pointless to recreate them yourself, except for one reason: you want your users to be able to log into the main website, and then access these tools as logged in users. The user experience should be that it&#8217;s all part of the same organizational website. </p>
<p>Third party authentication (an i-broker) solves this problem. Log in at any entry point in this constellation of online tools, and your experience is that you are logged in everywhere. Each tool has a menu of links to the other tools and the main website, and each one of these external menu items encodes the i-name you logged in with. When you arrive at another part of the site, the presence of that i-name in the link triggers an authentication redirect to the i-broker. Because you are already logged in, the i-broker instantly redirects you back to the application &#8212; the experience is that you are just logged in everywhere. (The exact methodology is described at http://ibroker.idcommons.net/moin.cgi/SingleSignOn - it will be evolving in the near future.)</p>
<p>In most cases, you will also have a need to ascertain that your user, now that you are sure of their identity, is authorized to access the particular service. This can be accomplished as a background request between applications and the main site, but for this to work, you must have robustly identified your user first, in a way that the authorizing agent understands. I-names and their associated i-numbers make this easy. (I-numbers are non-reassignable permanent identifiers.)</p>
<p>There is one more point I&#8217;d like to make about this, and it is the part that excites me the most. There is no reason why gluing applications together as I have described cannot happen just as seamlessly across organizational boundaries when desired, enabling various organizations to work collaboratively on projects in a very agile manner.</p></blockquote>
<p><font style="position: absolute;overflow: hidden;height: 0;width: 0"><a href="http://sikongroup.com/rentacar/index.htm">rent a car bulgaria</a></font></p>
<p>The second opportunity is more forward looking - to bust community based reputation out of the single web service jail.</p>
<blockquote><p>I have described how robust identity facilitates authorization across applications and even across organizational domains. Authorization can be thought of as a very limited form of reputation. If org B asks org A if a certain user is authorized to access a wiki, a positive response is in effect saying that this user is a member in good standing of org A - a little chunk of reputation.</p>
<p>It&#8217;s an easy leap to imagine aggregating my membership-in-good-standing in various organizations with my seller&#8217;s reputation on Ebay, my reviewer&#8217;s reputation on Amazon, and my proxies on Smartocracy to produce a kind of community credit rating (or Whuffie, if you&#8217;re a fan of &#8220;Down and Out in the Magic Kingdom&#8221;).</p>
<p>Of course, this is very sensitive and must absolutely be under the user&#8217;s control. There are parts of my life that I may not wish to share in other settings. There is a balance that free societies must achieve between what others must be able to know about you to make an informed trust decision, and what you must be able to keep to yourself in order to live your life as you choose. 2idi is dedicated to guiding the evolution of this technology in a direction that supports this balance.</p></blockquote>
<p>There is a lot of architecture and coding work happening behind the scenes right now to facilitate these possibilities. We see community i-brokers being less monolithic, more modular, and more distributed and tightly bound to specific organizations while able to share authentication with each other under the user&#8217;s control. We see various services as modules, talking to the i-broker but not part of it. I&#8217;ll be blogging more about the specifics in the near future.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.2idi.com/2005/12/04/past-and-future/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Platform Usability Release</title>
		<link>http://blog.2idi.com/2005/07/26/10/</link>
		<comments>http://blog.2idi.com/2005/07/26/10/#comments</comments>
		<pubDate>Wed, 27 Jul 2005 05:08:36 +0000</pubDate>
		<dc:creator>=fen</dc:creator>
		
		<category><![CDATA[Identity Services]]></category>

		<guid isPermaLink="false">http://blog.2idi.com/?p=10</guid>
		<description><![CDATA[2idi Corporation has released stable-0.7.6 of the Identity Commons Core I-Broker, now powering its public i-broker servers at http://2idi.com/.
This is primarily a (technical) usability release with many small changes in the Service Provider Interface Toolkit (aka SPIT) API, contact page enhancements including a new reply capability, and a normalized i-number database (harmonizing the first three [...]]]></description>
			<content:encoded><![CDATA[<p>2idi Corporation has released stable-0.7.6 of the Identity Commons Core I-Broker, now powering its public i-broker servers at <a href="http://2idi.com/">http://2idi.com/</a>.</p>
<p>This is primarily a (technical) usability release with many small changes in the Service Provider Interface Toolkit (aka SPIT) API, contact page enhancements including a new reply capability, and a normalized i-number database (harmonizing the first three versions into what we believe is a solid fourth version of the i-number specification).  In addition, this blog is i-name enabled (via the SPIT API and a <a href="http://www.planetwork.net/downloads/">Wordpress plugin</a> that Mike wrote) allowing comments from anyone with an i-name.</p>
<p>Big shout-outs to <a href="http://public.xdi.org/=michael.mell">Michael Mell</a> and <a href="http://public.xdi.org/=Victor.Grey">Victor Grey</a> who led the way towards the creation of what may be the last pre-SAML F/OSS (Free and Open Source Software) i-broker code releases.  Look for big things coming down the pike as we upgrade our single sign-on protocols to be SAML-2.0 compliant.  (And for those looking at the UI and not seeing much -if any- improvement, have no fear as that&#8217;s where we&#8217;re headed with the next release.)</p>
<p>As usual, the code can be downloaded from our subversion repository using the commands found at <a href="http://ibroker.idcommons.net/moin.cgi/SubVersion#head-e1dd13400b35d79e168d42c98e36c1bd91272bce">this link</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.2idi.com/2005/07/26/10/feed/</wfw:commentRss>
		</item>
		<item>
		<title>F/OSS I-Broker Available</title>
		<link>http://blog.2idi.com/2005/05/11/new-i-broker-software-available/</link>
		<comments>http://blog.2idi.com/2005/05/11/new-i-broker-software-available/#comments</comments>
		<pubDate>Wed, 11 May 2005 19:40:44 +0000</pubDate>
		<dc:creator>=fen</dc:creator>
		
		<category><![CDATA[Identity Services]]></category>

		<guid isPermaLink="false">/?p=8</guid>
		<description><![CDATA[2idi Corporation has released stable-0.7.5, of the Identity Commons Core I-Broker Free and Open Source Software.  This release marks another milestone in development as we&#8217;re now able to integrate community sites more effectively, bringing the goal of the widespread adoption of free community i-names one step closer to reality.  2idi has created this [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://2idi.com/">2idi Corporation</a> has released stable-0.7.5, of the Identity Commons Core I-Broker Free and Open Source Software.  This release marks another milestone in development as we&#8217;re now able to integrate community sites more effectively, bringing the goal of the widespread adoption of free community i-names one step closer to reality.  2idi has created this software and uses it to power the only i-broker offering global and community i-names currently in operation.</p>
<p>2idi is committed to the creation of a free and open source implementation of a dataweb services provider, also known as an <i>i-broker</i>, unencumbered by intellectual property or other restrictions.  Simply put, in order for people to have control, they must have a choice regarding not only who can see their data, for what purpose and how that data is used, but also where it is stored and by whom it will be managed. So our software MUST be open source in order to ensure that our customers have that choice. If we did anything to &#8220;lock in&#8221; our customers, it would be against this very purpose.</p>
<p>It is through this transparency that we plan to prosper - by creating a brand that is stable, secure, open and thus deserving of trust. We understand that anyone making disclosures of personal or otherwise sensitive information must feel safe from harm, real or imagined. Once people have a place they can trust, they can choose to &#8220;open up&#8221; in order to receive desired services, make better connections and work together more effectively.</p>
<p>Our goal is to make this technology so safe that even we - the owners of this system - could not pry into people&#8217;s lives - or retrieve their Real Names - without their consent.  Such trust and safety offers unparalleled opportunities for matching, social networking, cooperation and true, permission-based marketing in ways as yet unavailable without total loss of control over one&#8217;s personal information.</p>
<p>All of our &#8220;proprietary&#8221; software extensions will be licensed under the <a href="http://www.affero.org/oagpl.html">Affero General Public License</a> that will guarantee that even our premium services are not capable of locking in our customers should they choose - for whatever reason - to migrate their data elsewhere.  We plan to gain our customer&#8217;s trust because we are trust <i>worthy</i>.</p>
<p>2idi has actively engaged with partners spanning the corporate and non-profit worlds to get them up and running with our free and open source code base.  Our plan is to see some other i-brokers in operation this summer, which will help to fulfil our purpose of giving people increased choice.</p>
<p>Technical highlights of this release:</p>
<ul>
<li>We can now register community i-names and i-name enable sites</li>
<li>Single sign-on has been substantially revamped, including:</li>
</ul>
<ul>
<li>simplified installation for service providers</li>
<li>a new single-click logout process</li>
<li>architectural changes for increased SAML interoperability</li>
</ul>
<li>The resolver is now compatible with the <a href="http://www.oasis-open.org/apps/org/workgroup/xri/">OASIS XRI 2.0</a> (proposed) standard currently in Committee Draft</li>
<li>Updated FAQ and Help pages</li>
<p>Code and developer information is available on our <a href="http://ibroker.idcommons.net/moin.cgi/IdentityCommonsIbroker">wiki</a>.  Contact us via our <a href="http://public.xdi.org/@2idi*contact">@2idi*contact</a> page.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.2idi.com/2005/05/11/new-i-broker-software-available/feed/</wfw:commentRss>
		</item>
		<item>
		<title>open source release</title>
		<link>http://blog.2idi.com/2005/02/10/open-source-release/</link>
		<comments>http://blog.2idi.com/2005/02/10/open-source-release/#comments</comments>
		<pubDate>Fri, 11 Feb 2005 07:30:41 +0000</pubDate>
		<dc:creator>=fen</dc:creator>
		
		<category><![CDATA[Identity Services]]></category>

		<guid isPermaLink="false">/?p=7</guid>
		<description><![CDATA[  Today marked a milestone in our code development as 2idi released (beta) 0.7.1 of the Identity Commons Core I-Broker open source software, and in addition, moved our live site onto this base.  Big thanks to Identity Commons for making this possible, as well as to Victor Grey and Mike Mell for all [...]]]></description>
			<content:encoded><![CDATA[<p>  Today marked a milestone in our code development as 2idi released (beta) 0.7.1 of the Identity Commons Core I-Broker <a href="http://svn.idcommons.net:2460/cgi-bin/viewcvs.cgi/">open source</a> software, and in addition, moved our <a href="http://2idi.com/">live site</a> onto this base.  Big thanks to <a href="http://identitycommons.net/">Identity Commons</a> for making this possible, as well as to <a href="http://public.xdi.org/=Victor.Grey">Victor Grey</a> and <a href="http://public.xdi.org/=Michael.Mell">Mike Mell</a> for all their hard work.  While there are not many visible changes (and we need them - the UI and text copy need loads of updating) the cool stuff is under the hood:</p>
<ul>
<li>I-name single sign-on (ISSO) is fully functional and ready to be integrated into other service providers.  Watch this space for news of sites that go live with ISSO.</li>
<li>Community registries are enabled and ready to go.  This means free i-names for communities!  The UI to administer these still needs some work, but we can authenticate community i-names wherever global i-names can be used.</li>
<li>More modular code base.  The resolver, service provider interface toolkit, and various services modules have been separated from the main branch.  And install script has been written and the code has even been known to run on Windows 2000 Server and IIS (not always sure that is a good thing, but hey - we&#8217;re into inter-operability).</li>
<li>And many more code tweaks and features aimed towards portability and general usage.  (We still have some UI areas then need to be factored into e.g. MVC <i>hint hint</i> <img src='http://blog.2idi.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' /> )</li>
</ul>
<p>  The code is all still beta, but i-names created now will be usable for as long as you wish to keep them.  With this release we start down the path towards being a fully decentralized platform with no required central points of control - other than local authorities that you and your communities may agree upon.</p>
<p>    Where are we going with this?  Our goal - first and foremost - is to create a system that gives people total control over their <a href="http://2idi.com/help/ibroker/id-transactions.php">identity related transactions</a>.  Beyond that, check out our <a href="http://blog.fen.net/archives/000029.html">open source vision</a>.  Let <a href="http://public.xdi.org/=Fen.Labalme">us</a> know if you&#8217;d like to help!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.2idi.com/2005/02/10/open-source-release/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Welcome to the 2idi blog</title>
		<link>http://blog.2idi.com/2004/12/18/welcome-to-the-2idi-blog/</link>
		<comments>http://blog.2idi.com/2004/12/18/welcome-to-the-2idi-blog/#comments</comments>
		<pubDate>Sat, 18 Dec 2004 19:25:59 +0000</pubDate>
		<dc:creator>=fen</dc:creator>
		
		<category><![CDATA[Identity Services]]></category>

		<guid isPermaLink="false">/?p=2</guid>
		<description><![CDATA[We&#8217;ve created this blog so that we can have a place to put news and information as we develop and deploy i-broker software - which is key to creating a decentralized network providing users with total control over their personal profile information.  The technology is based on open standards (OASIS XRI, XDI and SAML) [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve created this blog so that we can have a place to put news and information as we develop and deploy i-broker software - which is key to creating a decentralized network providing users with total control over their personal profile information.  The technology is based on open standards (OASIS XRI, XDI and SAML) and the software will be released on SourceForge (under a dual BSD/GPL license) before the end of this year.  At the same time, we will be enabling the registration of free, community i-names, lowering the barrier of entry to zero.  (But during the limited EGS time period, you can <a href="http://2idi.com/registrar/index.html?referral_code=2idi">register a global i-name</a> for 50 years for only $25 - a great deal.)</p>
<p>Our commitment is to creating tools that create a win-win for the world - giving people control over their personal information while lowering barriers to entry for service providers, through single sign-on and i-broker negotiated data sharing.  We will also be working closely with <a href="http://identitycommons.net/">Identity Commons</a> to develop mechanisms for community feedback and <i>chaordic</i> governance so that we can create the most useful tools.   There&#8217;s a lot more coming down the pike - stay tuned!</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.2idi.com/2004/12/18/welcome-to-the-2idi-blog/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
