<?xml version="1.0" encoding="UTF-8" ?>
<!--RDF based XML document generated By OpenLink Virtuoso-->
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#">
 <rss:channel xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/">
  <rss:title>Kingsley Idehen&#39;s Blog Data Space</rss:title>
  <rss:link>http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/</rss:link>
  <rss:description>I have seen the future and it&#39;s full of Linked Data! :-)</rss:description>
  <dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kidehen@openlinksw.com</dc:creator>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2026-03-06T06:25:59Z</dc:date>
  <rss:items>
   <rdf:Seq>
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2010-07-11#1625" />
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2010-03-02#1610" />
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2010-01-31#1590" />
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2009-04-22#1542" />
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2009-03-14#1531" />
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2008-11-28#1489" />
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2008-10-01#1447" />
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2008-07-28#1397" />
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2008-06-26#1391" />
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2008-04-10#1334" />
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2008-02-08#1314" />
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2008-01-17#1300" />
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2007-09-22#1261" />
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2007-03-01#1148" />
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2006-09-20#1048" />
      <rdf:li rdf:resource="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2005-10-26#882" />
   </rdf:Seq>
  </rss:items>
 </rss:channel>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2010-07-11#1625">
  <rss:title>Solving Real Problems by Leveraging Linked Data: Unambiguous &amp; Verifiable Identity for HTTP Networks</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2010-07-12T03:25:03Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Problem: Unambiguous Verifiable Network Identity. How Does Linked Data Address This Problem? It provides critical infrastructure for the WebID Protocol that enables an innovative tweak of SSL/TLS. What about OpenID? The WebID Protocol embraces and extends OpenID (in an open and positive way) via the WebID + OpenID Hybrid variant of the protocol -- basic effect is that OpenID calls are re-routed to the WebID aspect which simply removes Username and Password Authentication from the authentication challenge interaction pattern. WebID Components X.509 Certificate and Private Key Generator Structured Profile Document (e.g. a FOAF based Profile) published to an HTTP Network (e.g. World Wide Web) and accessible at an Address (URL) An Agent Identifier aka. WebID (an HTTP Name Reference re. URI variant) that&#39;s the Subject of a Structured Profile Document (actually a Descriptor Resource) Mechanism for persisting Public Key data from X.509 Certificate to Structured Profile Document and associating it with Subject WebID (e.g. SPARUL or other HTTP based methods) Mechanism for de-referencing Public Key data associated with a WebID (from its Structured Profile Document) for comparison against Public Key data following successful standard SSL/TLS protocol handshake (e.g. via SPARQL Query). Demo WebID + OpenID Hybrid Protocol Demo using ODS, Stackoverflow.com, and identi.ca. - YouTube Screencast Demo Part 1 using Firefox WebID + OpenID Hybrid Protocol Demo using ODS, Stackoverflow.com, and identi.ca. - YouTube Screencast Demo Part 2 using Safari Related Prior Posts about WebIDs Draft WebID Spec</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h3>Problem: Unambiguous Verifiable Network Identity.</h3>

<p>How Does <a href="http://dbpedia.org/resource/Linked_Data" id="link-id0x1b1ad1d0">Linked Data</a> Address This Problem? It provides critical infrastructure for the  WebID Protocol that enables an innovative tweak of SSL/TLS.
</p>
<p>What about OpenID? The WebID Protocol embraces and extends OpenID (<strong><em>in an open and positive way</em></strong>) via the WebID + OpenID Hybrid variant of the protocol -- basic effect is that OpenID calls are re-routed to the WebID aspect which simply removes Username and Password Authentication from the authentication challenge interaction pattern.</p>

<h3>WebID Components</h3>
<ol>
<li>
X.509 Certificate and Private Key Generator
</li>
<li>
Structured Profile Document (e.g. a <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id0x1a301338">FOAF</a> based Profile) published to an HTTP Network (e.g. <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id0x1ba50e10">World Wide Web</a>) and accessible at an Address (<a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id0x12ded2e0">URL</a>)
</li>
<li>
An Agent Identifier aka. WebID (an HTTP Name Reference re. <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id0x1b197378">URI</a> variant) that&#39;s the Subject of a Structured Profile Document (actually a Descriptor Resource)</li>
<li>
Mechanism for persisting Public Key data from X.509 Certificate to Structured Profile Document and associating it with Subject WebID (e.g. SPARUL or other HTTP based methods)
</li>
<li>
Mechanism for de-referencing Public Key data associated with a WebID (from its Structured Profile Document) for comparison against Public Key data following successful standard SSL/TLS protocol handshake (e.g. via <a href="http://dbpedia.org/resource/SPARQL" id="link-id0x16d26ec8">SPARQL</a> Query).
</li>
</ol>

<h3>Demo</h3>
<ul>
<li>
  <a href="http://www.youtube.com/watch?v=mjgXsjd8PDE" id="link-id0x1b9cc4d8">WebID + OpenID Hybrid Protocol Demo using ODS, Stackoverflow.com, and identi.ca.</a> - YouTube Screencast Demo Part 1 using Firefox</li>
<li>
<a href="http://www.youtube.com/watch?v=eXoxUo7Py4M " id="link-id0x1a2db140">WebID + OpenID Hybrid Protocol Demo using ODS, Stackoverflow.com, and identi.ca.</a> - YouTube Screencast Demo Part 2 using Safari
</li>
</ul> 

<h3>Related</h3>
<ul>
<li>
  <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&amp;q=webid&amp;type=text&amp;output=html" id="link-id0x1bc37a58">Prior Posts about WebIDs</a>
</li>
<li>
  <a href="http://payswarm.com/webid/drafts/ED-webid-20100711/" id="link-id0x1a0eecb8">Draft WebID Spec</a>
</li>
</ul>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2010-03-02#1610">
  <rss:title>Linked Data &amp; Socially Enhanced Collaboration (Enterprise or Individual) -- Update 1</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2010-03-02T20:47:54Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Socially enhanced enterprise and invididual collaboration is becoming a focal point for a variety of solutions that offer erswhile distinct content managment features across the realms of Blogging, Wikis, Shared Bookmarks, Discussion Forums etc.. as part of an integrated platform suite. Recently, Socialtext has caught my attention courtesy of its nice features and benefits page . In addition, I&#39;ve also found the Mike 2.0 portal immensely interesting and valuable, for those with an enterprise collaboration bent. Anyway, Socialtext and Mike 2.0 (they aren&#39;t identical and juxtaposition isn&#39;t seeking to imply this) provide nice demonstrations of socially enhanced collaboration for individuals and/or enterprises is all about: Identifying Yourself Identifying Others (key contributors, peers, collaborators) Serendipitous Discovery of key contributors, peers, and collaborators Serendipitous Discovery by key contributors, peers, and collaborators Develop and sustain relationships via socially enhanced professional network hybrid Utilize your new &quot;trusted network&quot; (which you&#39;ve personally indexed) when seeking help or propagating a meme. As is typically the case in this emerging realm, the critical issue of discrete &quot;identifiers&quot; (record keys in sense) for data items, data containers, and data creators (individuals and groups) is overlooked albeit unintentionally. How HTTP based Linked Data Addresses the Identifier Issue Rather than using platform constrained identifiers such as: email address (a &quot;mailto&quot; scheme identifier), a dbms user account, application specific account, or OpenID. It enables you to leverage the platform independence of HTTP scheme Identifiers (Generic URIs) such that Identifiers for: You, Your Peers, Your Groups, and Your Activity Generated Data, simply become conduits into a mesh of HTTP -- referencable and accessible -- Linked Data Objects endowed with High SDQ (Serendipitious Discovery Quotient). For example my Personal WebID is all anyone needs to know if they want to explore: My Profile (which includes references to data objects associated with my interests, social-network, calendar, bookmarks etc.) Data generated by my activities across various data spaces (via data objects associated with my online accounts e.g. Del.icio.us, Twitter, Last.FM) Linked Data Meshups via URIBurner (or any other Virtuoso instance) that provide an extend view of my profile How FOAF+SSL adds Socially aware Security Even when you reach a point of equilibrium where: your daily activities trigger orchestratestration of CRUD (Create, Read, Update, Delete) operations against Linked Data Objects within your socially enhanced collaboration network, you still have to deal with the thorny issues of security, that includes the following: Single Sign On, Authentication, and Data Access Policies. FOAF+SSL, an application of HTTP based Linked Data, enables you to enhance your Personal HTTP scheme based Identifer (or WebID) via the following steps (peformed by a FOAF+SSL compliant platform): Imprint WebID within a self-signed x.509 based public key (certificate) associated with your private key (generated by FOAF+SSL platform or manually via OpenSSL) Store public key components (modulous and exponent) into your FOAF based profile document which references your Personal HTTP Identifier as its primary topic Leverage HTTP URL component of WebID for making public key components (modulous and exponent) available for x.509 certificate based authentication challenges posed by systems secured by FOAF+SSL (directly) or OpenID (indirectly via FOAF+SSL to OpenID proxy services). Contrary to conventional experiences with all things PKI (Public Key Infrastructure) related, FOAF+SSL compliant platforms typically handle the PKI issues as part of the protocol implementation; thereby protecting you from any administrative tedium without compromising security. Conclusions Understanding how new technology innovations address long standing problems, or understanding how new solutions inadvertently fail to address old problems, provides time tested mechanisms for product selection and value proposition comprehension that ultimately save scarce resources such as time and money. If you want to understand real world problem solution #1 with regards to HTTP based Linked Data look no further than the issues of secure, socially aware, and platform independent identifiers for data objects, that build bridges across erstwhile data silos. If you want to cost-effectively experience what I&#39;ve outlined in this post, take a look at OpenLink Data Spaces (ODS) which is a distributed collaboration engine (enterprise of individual) built around the Virtuoso database engines. It simply enhances existing collaboration tools via the following capabilities: Addition of Social Dimensions via HTTP based Data Object Identifiers for all Data Items (if missing) Ability to integrate across a myriad of Data Source Types rather than a select few across RDBM Engines, LDAP, Web Services, and various HTTP accessible Resources (Hypermedia or Non Hypermedia content types) Addition of FOAF+SSL based authentication Addition of FOAF+SSL based Access Control Lists (ACLs) for policy based data access. Related: Get Yourself A WebID in 5 Minutes or Less via OpenLink Data Spaces (an application layer built atop Virtuoso) How To Share Resources Securely Using FOAF+SSL FOAF+SSL &amp; WebID Demonstration OpenLink Data Spaces &amp; Data Portability.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Socially enhanced enterprise and invididual collaboration is becoming a focal point for a variety of solutions that offer erswhile distinct content managment features across the realms of Blogging, Wikis, Shared Bookmarks, Discussion Forums etc.. as part of an integrated platform suite. Recently, <a href="http://www.socialtext.com/" id="link-id112be850">Socialtext</a> has caught my attention courtesy of its nice <a href="http://www.socialtext.com/products/socialnetworking.php" id="link-id145d9850">features and benefits page</a> . In addition, I&#39;ve also found the <a href="http://mike2.openmethodology.org/" id="link-id14103cc8">Mike 2.0 portal</a> immensely interesting and valuable, for those with an enterprise  collaboration bent.</p>
<p>Anyway, Socialtext and Mike 2.0  (they aren&#39;t identical and juxtaposition isn&#39;t seeking to imply this) provide nice demonstrations of socially enhanced collaboration for individuals and/or enterprises is all about:</p>
<ol>
  <li>Identifying Yourself</li>
  <li>Identifying Others (key contributors, peers, collaborators)</li>
  <li>Serendipitous Discovery of key contributors, peers, and collaborators</li>
  <li>Serendipitous Discovery by key contributors, peers, and collaborators</li>
  <li>Develop and sustain relationships via socially enhanced professional network hybrid</li>
  <li>Utilize your new &quot;trusted network&quot; (which you&#39;ve personally indexed) when seeking help or propagating a <a href="http://dbpedia.org/resource/Meme" id="link-id13ad00d0">meme</a>.</li>
</ol>
<p>As is typically the case in this emerging realm, the critical issue of discrete &quot;identifiers&quot; (record keys in sense) for <a href="http://dbpedia.org/resource/Data">data</a> items, data containers, and data creators (individuals and groups) is overlooked albeit unintentionally. </p>
<h3>How HTTP based <a href="http://dbpedia.org/resource/Linked_Data" id="link-id112e1ba8">Linked Data</a> Addresses the Identifier Issue</h3>
<p>Rather than using platform constrained identifiers such as: </p>
<ul>
  <li>email address (a &quot;mailto&quot; scheme identifier), </li>
  <li>a dbms user account, </li>
  <li>application specific account, or</li>
  <li>OpenID.</li>
</ul>
<p>It enables you to leverage the platform independence of HTTP scheme Identifiers (Generic URIs) such that Identifiers for: </p>
<ol>
  <li>You, </li>
  <li>Your Peers, </li>
  <li>Your Groups, and </li>
  <li>Your Activity Generated Data, </li>
</ol>
<p>simply become conduits into a mesh of <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/images/My_Data_Spaces.png" id="link-id13fe1168">HTTP -- referencable and accessible -- Linked Data Objects</a> endowed with High SDQ (Serendipitious Discovery Quotient). For example my <a href="http://kingsley.idehen.name/dataspace/person/kidehen#this" id="link-id13bdcc80">Personal WebID </a>is all anyone needs to know if they want to explore:</p>
<ol>
<li>My Profile (which includes references to data objects associated with my interests, social-network, calendar, bookmarks etc.)</li>
<li>Data generated by my activities across various data spaces (via data objects associated with my online accounts e.g. <a href="http://linkeddata.uriburner.com/about/id/entity/http/feeds.delicious.com/v2/rss/kidehen?count=15" id="link-id141cce38">Del.icio.us</a>, <a href="http://linkeddata.uriburner.com/about/id/entity/http/twitter.com/kidehen" id="link-id11802ce8">Twitter</a>, <a href="http://linkeddata.uriburner.com/about/id/entity/http/www.last.fm/user/kidehen" id="link-id118bf470">Last.FM</a>)</li>
<li>
  <a href="http://uriburner.com/fct/rdfdesc/usage.vsp?g=http%3A%2F%2Fkingsley.idehen.name%2Fdataspace%2Fperson%2Fkidehen%23this&amp;tp=4" id="link-id13c0f528">Linked Data Meshups via URIBurner</a> (or any other <a href="http://virtuoso.openlinksw.com" id="link-id11334f00">Virtuoso</a> instance) that provide an extend view of my profile</li>
</ol>
<h3>How <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id14324eb0">FOAF</a>+SSL adds Socially aware Security </h3>
<p>Even when you reach a point of equilibrium where: your daily activities trigger orchestratestration of CRUD (Create, Read, Update, Delete) operations against Linked Data Objects within your socially enhanced collaboration network, you still have to deal with the thorny issues of security, that includes the following: </p>
<ol>
  <li>Single Sign On, </li>
  <li>Authentication, and </li>
  <li>Data Access Policies.</li>
</ol>
<p>FOAF+SSL, an application of HTTP based Linked Data, enables you to enhance your Personal HTTP scheme based Identifer (or WebID) via the following steps (peformed by a FOAF+SSL compliant platform):</p>
<ol>
  <li>Imprint WebID within a self-signed x.509 based public key (certificate) associated with your private key (generated by FOAF+SSL platform or manually via OpenSSL)</li>
  <li>Store public key components (modulous and exponent) into your FOAF based profile document which references your Personal HTTP Identifier as its primary topic</li>
  <li>Leverage HTTP <a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id141f8b30">URL</a> component of WebID for making public key components (modulous and exponent) available for x.509 certificate based authentication challenges posed by systems secured by FOAF+SSL (directly) or OpenID (indirectly via FOAF+SSL to OpenID proxy services).</li>
</ol>
<p>Contrary to conventional experiences with all things PKI (Public Key Infrastructure) related, FOAF+SSL compliant platforms typically handle the PKI issues as part of the protocol implementation; thereby protecting you from any administrative tedium without compromising security.</p>
<h3>Conclusions</h3>
<p>Understanding how new technology innovations address long standing problems, or understanding how new solutions inadvertently fail to address old problems, provides time tested mechanisms for product selection and value proposition comprehension that ultimately save scarce resources such as time and money. </p>
<p>If you want to understand real world problem solution #1 with regards to HTTP based Linked Data look no further than the issues of secure, socially aware, and platform independent identifiers for data objects, that build bridges across erstwhile data silos.</p>
<p>If you want to cost-effectively experience what I&#39;ve outlined in this post, take a look at <a href="http://ods.openlinksw.com/wiki/ODS/" id="link-id13c21220">OpenLink Data Spaces</a> (<a href="http://ods.openlinksw.com/wiki/ODS/" id="link-id1422cdd8">ODS</a>) which is a distributed collaboration engine (enterprise of individual) built around the <a href="http://virtuoso.openlinksw.com" id="link-id14211c98">Virtuoso</a> database engines. It simply enhances existing collaboration tools via the following capabilities:</p>
<p>Addition of Social Dimensions via HTTP based <a href="http://dbpedia.org/resource/Identity_(object-oriented_programming)" id="link-id116ecd88">Data Object Identifiers</a> for all Data Items (if missing)</p>
<ol>
  <li>Ability to integrate across a myriad of Data Source Types rather than a select few across RDBM Engines, LDAP, <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> Services, and various HTTP accessible Resources (Hypermedia or Non Hypermedia content types)</li>
  <li>Addition of FOAF+SSL based authentication</li>
  <li>Addition of FOAF+SSL based Access Control Lists (ACLs) for policy based data access.</li>
</ol>
<h3>Related:</h3>
<ul>
  <li>
  <a href="http://ods.openlinksw.com/dataspace/dav/wiki/ODS/GetAPersonalURIIn5MinutesOrLess" id="link-id117b2610">Get Yourself A WebID in 5 Minutes or Less</a> via OpenLink Data Spaces (an application layer built atop Virtuoso)</li>
  <li>
  <a href="http://ods.openlinksw.com/dataspace/dav/wiki/ODS/ODSBriefcaseFOAFSSL" id="link-id140311a0">How To Share Resources Securely Using FOAF+SSL</a> </li>
  <li>
  <a href="http://www.youtube.com/watch?v=CRbdeNMPCug" id="link-id11ad5448">FOAF+SSL &amp; WebID Demonstration</a>
</li>
  <li>
  <a href="http://www.slideshare.net/kidehen/linked-data-spaces-data-portability-access" id="link-id141f43a8">OpenLink Data Spaces &amp; Data Portability</a>.</li>
  
</ul>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2010-01-31#1590">
  <rss:title>5 Game Changing Things about the OpenLink Virtuoso + AWS Cloud Combo</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2010-01-31T22:29:34Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Here are 5 powerful benefits you can immediately derive from the combination of Virtuoso and Amazon&#39;s AWS services (specifically the EC2 and EBS components): Acquire your own personal or service specific data space in the Cloud. Think DBase, Paradox, FoxPRO, Access of yore, but with the power of Oracle, Informix, Microsoft SQL Server etc.. using a Conceptual, as opposed to solely Logical, model based DBMS (i.e., a Hybrid DBMS Engine for: SQL, RDF, XML, and Full Text) Ability to share and control access to your resources using innovations like FOAF+SSL, OpenID, and OAuth, all from one place Construction of personal or organization based FOAF profiles in a matter of minutes; by simply creating a basic DBMS (or ODS application layer) account; and then using this profile to create strong links (references) to all your Data silos (esp. those from the Web 2.0 realm) Load data sets from the LOD cloud or Sponge existing Web resources (i.e., on the fly data transformation to RDF model based Linked Data) and then use the combination to build powerful lookup services that enrich the value of URLs (think: Web addressable reports holding query results) that you publish Bind all of the above to a domain that you own (e.g. a .Name domain) so that you have an attribution-friendly &quot;authority&quot; component for resource URLs and Entity URIs published from your Personal Linked Data Space on the Web (or private HTTP network). In a nutshell, the AWS Cloud infrastructure simplifies the process of generating Federated presence on the Internet and/or World Wide Web. Remember, centralized networking models always end up creating data silos, in some context, ultimately! :-)</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<p> Here are 5 powerful benefits you can immediately derive from the combination of <a href="http://virtuoso.openlinksw.com" id="link-id17eb8988">Virtuoso</a> and Amazon&#39;s AWS services (specifically the EC2 and EBS components): <br />
</p>  <ol> <li> Acquire your own personal or service specific <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id1423e520">data space</a> in the Cloud. Think DBase, Paradox, FoxPRO, Access of yore, but with the power of <a href="http://dbpedia.org/resource/Oracle_Database" id="link-id136c6290">Oracle</a>, <a href="http://dbpedia.org/resource/IBM_Informix" id="link-id11b269b8">Informix</a>, <a href="http://dbpedia.org/resource/Microsoft_SQL_Server" id="link-id138084b8">Microsoft SQL Server</a> etc.. using a Conceptual, as opposed to solely Logical, model based DBMS (i.e., a Hybrid DBMS Engine for: <a href="http://dbpedia.org/resource/SQL" id="link-id132a7938">SQL</a>, RDF, XML, and Full Text) </li> <li> Ability to share and control access to your resources using innovations like <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id17ee9d28">FOAF</a>+SSL, OpenID, and OAuth, all from one place </li> <li> Construction of personal or organization based FOAF profiles in a matter of minutes; by simply creating a basic DBMS (or <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id14784ae0">ODS</a> application layer) account; and then using this profile to create strong links (references) to all your Data silos (esp. those from the <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> 2.0 realm) </li> <li> Load data sets from the <a href="http://community.linkeddata.org/dataspace/organization/lod#this" id="link-id17e6ac98">LOD</a> cloud or Sponge existing Web resources (i.e., on the fly data transformation to RDF model based <a href="http://dbpedia.org/resource/Linked_Data" id="link-id17e65d38">Linked Data</a>) and then use the combination to build powerful lookup services that enrich the value of URLs (think: Web addressable reports holding query results) that you publish </li> <li> Bind all of the above to a domain that you own (e.g. a .Name domain) so that you have an attribution-friendly &quot;authority&quot; component for resource URLs and <a href="http://dbpedia.org/resource/Entity" id="link-id118a08d8">Entity</a> URIs published from your Personal Linked Data Space on the Web (or private HTTP network). </li> </ol> <p> In a nutshell, the AWS Cloud infrastructure simplifies the process of generating Federated presence on the <a href="http://dbpedia.org/resource/Internet" id="link-id1380af38">Internet</a> and/or <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id11633b10">World Wide Web</a>. Remember, centralized networking models always end up creating data silos, in some <a href="http://dbpedia.org/resource/Context_%28language_use%29" id="link-id142006f0">context</a>, ultimately! :-) </p>
]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2009-04-22#1542">
  <rss:title>Take N: Yet Another OpenLink Data Spaces Introduction</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2009-04-22T18:46:18Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Problem: Your Life, Profession, Web, and Internet do not need to become mutually exclusive due to &quot;information overload&quot;. Solution: A platform or service that delivers a point of online presence that embodies the fundamental separation of: Identity, Data Access, Data Representation, Data Presentation, by adhering to Web and Internet protocols. How: Typical post installation (Local or Cloud) task sequence: Identify myself (happens automatically by way of registration) If in an LDAP environment, import accounts or associate system with LDAP for account lookup and authentication Identify Online Accounts (by fleshing out profile) which also connects system to online accounts and their data Use Profile for granular description (Biography, Interests, WishList, OfferList, etc.) Optionally upstream or downstream data to and from my online accounts Create content Tagging Rules Create rules for associating Tags with formal URIs Create automatic Hyperlinking Rules for reuse when new content is created (e.g. Blog posts) Exploit Data Portability virtues of RSS, Atom, OPML, RDFa, RDF/XML, and other formats for imports and exports Automatically tag imported content Use function-specific helper application UIs for domain specific data generation e.g. AddressBook (optionally use vCard import), Calendar (optionally use iCalendar import), Email, File Storage (use WebDAV mount with copy and paste or HTTP GET), Feed Subscriptions (optionally import RSS/Atom/OPML feeds), Bookmarking (optionally import bookmark.html or XBEL) etc.. Optionally enable &quot;Conversation&quot; feature (today: Social Media feature) across the relevant application domains (manage conversations under covers using NNTP, the standard for this functionality realm) Generate HTTP based Entity IDs (URIs) for every piece of data in this burgeoning data space Use REST based APIs to perform CRUD tasks against my data (local and remote) (SPARQL, GData, Ubiquity Commands, Atom Publishing) Use OpenID, OAuth, FOAF+SSL, FOAF+SSL+OpenID for accessing data elsewhere Use OpenID, OAuth, FOAF+SSL, FOAF+SSL+OpenID for Controlling access to my data (Self Signed Certificate Generation, Browser Import of said Certificate &amp; associated Private Key, plus persistence of Certificate to FOAF based profile data space in &quot;one click&quot;) Have a simple UI for Entity-Attribute-Value or Subject-Predicate-Object arbitrary data annotations and creation since you can&#39;t pre model an &quot;Open World&quot; where the only constant is data flow Have my Personal URI (Web ID) as the single entry point for controlled access to my HTTP accessible data space I&#39;ve just outlined a snippet of the capabilities of the OpenLink Data Spaces platform. A platform built using OpenLink Virtuoso, architected to deliver: open, platform independent, multi-model, data access and data management across heterogeneous data sources. All you need to remember is your URI when seeking to interact with your data space. Related Get Yourself a URI (Web ID) in 5 Minutes or Less! Various posts over the years about Data Spaces Future of Desktop Post Simplify My Life Post by Bengee Nowack</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<h3>Problem:</h3>
<p>Your Life, Profession, <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a>, and <a href="http://dbpedia.org/resource/Internet" id="link-id0x1c6687f8">Internet</a> do not need to become mutually exclusive due to &quot;<a href="http://dbpedia.org/resource/Information" id="link-id0x1c6696e8">information</a> overload&quot;.</p>

<h3>Solution:</h3>
<p>
A platform or service that delivers a point of online presence that embodies the fundamental separation of: Identity, <a href="http://dbpedia.org/resource/Data">Data</a> Access, Data Representation, Data Presentation, by adhering to Web and Internet protocols.</p>

<h3>How:</h3>
<p>
Typical post installation (Local or Cloud) task sequence:</p>
<ol>
<li>
Identify myself (happens automatically by way of registration)</li>
<li>If in an LDAP environment, import accounts or associate system with LDAP for account lookup and authentication</li>
<li>
Identify Online Accounts (by fleshing out profile) which also connects system to online accounts and their data</li>
<li>Use Profile for granular description (Biography, Interests, WishList, OfferList, etc.)</li>
<li>Optionally upstream or downstream data to and from my online accounts</li>
<li>Create content Tagging Rules</li>
<li>Create rules for associating Tags with formal URIs</li>
<li>Create automatic Hyperlinking Rules for reuse when new content is created (e.g. <a href="http://dbpedia.org/resource/Blog" id="link-id11a7c660">Blog</a> posts)</li>
<li>Exploit Data Portability virtues of RSS, Atom, OPML, <a href="http://dbpedia.org/resource/RDFa" id="link-id13f54d50">RDFa</a>, RDF/XML, and other formats for imports and exports</li> 
<li>Automatically <a href="http://dbpedia.org/resource/Tag" id="link-id121ddff0">tag</a> imported content</li>
<li>Use function-specific helper application UIs for domain specific data generation e.g. AddressBook (optionally use vCard import), Calendar (optionally use iCalendar import), Email, File Storage (use WebDAV mount with copy and paste or HTTP GET), Feed Subscriptions (optionally import RSS/Atom/OPML feeds), Bookmarking (optionally import bookmark.html or XBEL) etc..</li>
<li>Optionally enable &quot;Conversation&quot; feature (today: Social Media feature) across the relevant application domains (manage conversations under covers using NNTP, the standard for this functionality realm)
</li>
<li>Generate HTTP based <a href="http://dbpedia.org/resource/Entity" id="link-id13d5d378">Entity</a> IDs (URIs) for every piece of data in this burgeoning <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id11a69670">data space</a>
</li>
<li>Use REST based APIs to perform CRUD tasks against my data (local and remote) (<a href="http://dbpedia.org/resource/SPARQL" id="link-id11a76e10">SPARQL</a>, GData, Ubiquity Commands, Atom Publishing)</li> 

<li>Use OpenID, OAuth, <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id11c9b3e0">FOAF</a>+SSL, FOAF+SSL+OpenID for accessing data elsewhere</li>
<li>Use OpenID, OAuth, FOAF+SSL, FOAF+SSL+OpenID for Controlling access to my data (Self Signed Certificate Generation, Browser Import of said Certificate &amp; associated Private Key, plus persistence of Certificate to FOAF based profile data space in &quot;one click&quot;)</li>
<li>Have a simple UI for <a href="http://dbpedia.org/resource/Entity-attribute-value_model" id="link-id14015bd0">Entity</a>-Attribute-Value or Subject-Predicate-Object arbitrary data annotations and creation since you can&#39;t pre model an &quot;<a href="http://dbpedia.org/resource/Open_world_assumption" id="link-id11cd8548">Open World</a>&quot; where the only constant is data flow</li>
<li>Have my Personal <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id142beee8">URI</a> (Web ID) as the single entry point for controlled access to my HTTP accessible data space</li>
</ol>
<p>
I&#39;ve just outlined a snippet of the capabilities of the <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id13d64740">OpenLink Data Spaces</a> platform. A platform built using OpenLink <a href="http://virtuoso.openlinksw.com" id="link-id13d74170">Virtuoso</a>, architected to deliver: open, platform independent, multi-model, data access and data management across heterogeneous data sources.
</p>
<p>
All you need to remember is your URI when seeking to interact with your data space.</p>

<h3>Related</h3>
<ol>
<li>
  <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/GetAPersonalURIIn5MinutesOrLess" id="link-id13c97948">Get Yourself a URI (Web ID) in 5 Minutes or Less!</a>
</li>
<li>
<a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&amp;q=%22data%20spaces%22&amp;type=text&amp;output=html" id="link-id1431e088">Various posts over the years about Data Spaces</a>
</li>
<li>
  <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1415" id="link-id11f837f0">Future of Desktop Post</a>
</li>
 <li>
  <a href="http://bnode.org/blog/2009/04/22/semantic-web-apps-to-simplify-my-life" id="link-id1393f8a8">Simplify My Life Post</a> by <a href="http://bnode.org/about" id="link-id11da0cc8">Bengee Nowack</a>
 </li>
</ol>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2009-03-14#1531">
  <rss:title>Simple Compare &amp; Contrast of Web 1.0, 2.0, and 3.0 (Update 1)</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2009-03-14T18:20:00Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Here is a tabulated &quot;compare and contrast&quot; of Web usage patterns 1.0, 2.0, and 3.0. Â  Web 1.0 Web 2.0 Web 3.0 Simple Definition Interactive / Visual Web Programmable Web Linked Data Web Unit of Presence Web Page Web Service Endpoint Data Space (named structured data enclave) Unit of Value Exchange Page URL Endpoint URL for API Resource / Entity / Object URI Data Granularity Low (HTML) Medium (XML) High (RDF) Defining Services Search Community (Blogs to Social Networks) Find Participation Quotient Low Medium High Serendipitous Discovery Quotient Low Medium High Data Referencability Quotient Low (Documents) Medium (Documents) High (Documents and their constituent Data) Subjectivity Quotient High Medium (from A-list bloggers to select source and partner lists) Low (everything is discovered via URIs) Transclusence Low Medium (Code driven Mashups) HIgh (Data driven Meshups) What You See Is What You Prefer (WYSIWYP) Low Medium High (negotiated representation of resource descriptions) Open Data Access (Data Accessibility) Low Medium (Silos) High (no Silos) Identity Issues Handling Low Medium (OpenID) High (FOAF+SSL) Solution Deployment Model Centralized Centralized with sprinklings of Federation Federated with function specific Centralization (e.g. Lookup hubs like LOD Cloud or DBpedia) Data Model Orientation Logical (Tree based DOM) Logical (Tree based XML) Conceptual (Graph based RDF) User Interface Issues Dynamically generated static interfaces Dyanically generated interafaces with semi-dynamic interfaces (courtesy of XSLT or XQuery/XPath) Dynamic Interfaces (pre- and post-generation) courtesy of self-describing nature of RDF Data Querying Full Text Search Full Text Search Full Text Search + Structured Graph Pattern Query Language (SPARQL) What Each Delivers Democratized Publishing Democratized Journalism &amp; Commentary (Citizen Journalists &amp; Commentators) Democratized Analysis (Citizen Data Analysts) Star Wars Edition Analogy Star Wars (original fight for decentralization via rebellion) Empire Strikes Back (centralization and data silos make comeback) Return of the JEDI (FORCE emerges and facilitates decentralization from &quot;Identity&quot; all the way to &quot;Open Data Access&quot; and &quot;Negotiable Descriptive Data Representation&quot;) Naturally, I am not expecting everyone to agree with me. I am simply making my contribution to what will remain facinating discourse for a long time to come :-) Related Web 3.0 The Best Official Definition Imaginable -- Nova Spivack&#39;s</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<p>Here is a tabulated &quot;compare and contrast&quot; of <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> usage patterns 1.0, 2.0, and 3.0.</p>  <table border="1" width="715" height="286">    <tbody>
  <tr>      <td>Â </td>      <td><strong>Web 1.0</strong></td>      <td><strong>Web 2.0</strong></td>      <td><strong>Web 3.0</strong></td>   </tr>    <tr>      <td><strong>Simple Definition</strong></td>      <td>Interactive / Visual Web</td>      <td>Programmable Web</td>      <td><a href="http://dbpedia.org/resource/Linked_Data" id="link-id117a9a98">Linked Data</a> <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id146bcdb0">Web</a></td>   </tr>    <tr>      <td><strong>Unit of Presence</strong></td>      <td>Web Page</td>      <td>Web Service Endpoint</td>      <td><a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id11a66c60">Data Space</a> (named structured data enclave)</td>   </tr>    <tr>      <td><strong>Unit of Value Exchange</strong></td>      <td>Page <a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id146083f8">URL</a></td>      <td>Endpoint URL for API</td>      <td>Resource / <a href="http://dbpedia.org/resource/Entity" id="link-id121b2148">Entity</a> / Object <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id1467ed00">URI</a></td>   </tr>    <tr>      <td><strong>Data Granularity</strong></td>      <td>Low (HTML)</td>      <td>Medium (XML)</td>      <td>High (RDF)</td>   </tr>    <tr>      <td><strong>Defining Services</strong></td>      <td>Search </td>      <td>Community (Blogs to Social Networks) </td>      <td>Find</td>   </tr>    <tr>      <td><strong>Participation Quotient</strong></td>      <td>Low</td>      <td>Medium</td>      <td>High</td>   </tr>    <tr>      <td><strong>Serendipitous Discovery Quotient </strong></td>      <td>Low</td>      <td>Medium</td>      <td>High</td>   </tr>    <tr>      <td><strong>Data Referencability Quotient </strong></td>      <td>Low (Documents)</td>      <td>Medium (Documents)</td>      <td>High (Documents and their constituent Data)</td>   </tr>    <tr>      <td><strong>Subjectivity Quotient</strong></td>      <td>High</td>      <td>Medium (from A-list bloggers to select source and partner lists)</td>      <td>Low (everything is discovered via URIs)</td>   </tr>    <tr>      <td>    <strong><a href="http://dbpedia.org/resource/Transclusion" id="link-id155308d8">Transclusence</a>    </strong></td>      <td>Low</td>      <td>Medium (Code driven Mashups)</td>      <td>HIgh (Data driven Meshups)</td>   </tr>    <tr>      <td><strong>What You See Is What You Prefer (WYSIWYP)</strong></td>      <td>Low</td>      <td>Medium </td>      <td>High (negotiated representation of resource descriptions)</td>   </tr>    <tr>      <td><strong>Open Data Access (Data Accessibility)</strong></td>      <td>Low</td>      <td>Medium (Silos)</td>      <td>High (no Silos)</td>   </tr>    <tr>      <td><strong>Identity Issues Handling</strong></td>      <td>Low</td>      <td>Medium (<a href="http://dbpedia.org/resource/OpenID" id="link-id119d77f8">OpenID</a>)</td>      <td><p>High (<a href="http://esw.w3.org/topic/foaf+ssl" id="link-id135cc348">FOAF+SSL</a>)</p></td>   </tr>    <tr>      <td><strong>Solution Deployment Model</strong></td>      <td>Centralized</td>      <td>Centralized with sprinklings of Federation</td>      <td>Federated with function specific Centralization (e.g. Lookup hubs like <a href="http://community.linkeddata.org/dataspace/organization/lod#this" id="link-id1496d1d0">LOD</a> Cloud or <a href="http://dbpedia.org/resource/DBpedia" id="link-id1571f690">DBpedia</a>)</td>   </tr>   <tr>     <td><strong>Data Model Orientation</strong></td>     <td>Logical (Tree based DOM)</td>     <td>Logical (Tree based XML)</td>     <td>Conceptual (Graph based RDF)</td>   </tr>   <tr>     <td><strong>User Interface Issues</strong></td>     <td>Dynamically generated static interfaces</td>     <td>Dyanically generated interafaces with semi-dynamic interfaces (courtesy of XSLT or <a href="http://dbpedia.org/resource/XQuery" id="link-id118399e8">XQuery</a>/<a href="http://dbpedia.org/resource/XPath" id="link-id14b00ba0">XPath</a>)</td>     <td>Dynamic Interfaces (pre- and post-generation) courtesy of self-describing nature of RDF</td>   </tr>   <tr>     <td><strong>Data Querying</strong></td>     <td><a href="http://dbpedia.org/resource/Full_text_search" id="link-id14fdd948">Full Text Search</a></td>     <td>Full Text Search</td>     <td>Full Text Search + Structured Graph Pattern Query Language (<a href="http://dbpedia.org/resource/SPARQL" id="link-id154a9368">SPARQL</a>)</td>   </tr>   <tr>     <td><strong>What Each Delivers</strong></td>     <td>Democratized Publishing</td>     <td>Democratized Journalism &amp; Commentary (Citizen Journalists &amp; Commentators)</td>     <td>Democratized Analysis (Citizen Data Analysts)</td>   </tr>     <tr>     <td>    <strong><a href="http://dbpedia.org/resource/Star_Wars" id="link-id155ce920">Star Wars Edition Analogy</a>    </strong></td>     <td>Star Wars (original fight for decentralization via rebellion)</td>     <td>Empire Strikes Back (centralization and data silos make comeback)</td>     <td>Return of the JEDI (<a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1474" id="link-id11706640">FORCE</a> emerges and facilitates decentralization from &quot;Identity&quot; all the way to &quot;Open Data Access&quot; and &quot;Negotiable Descriptive Data Representation&quot;)</td>   </tr> </tbody>
</table>  <p>Naturally, I am not expecting everyone to agree with <a href="http://myopenlink.net/dataspace/person/kidehen#this" id="link-id15be20c0">me</a>. I am simply making my contribution to what will remain facinating discourse for a long time to come :-)</p>  <h3>Related</h3>  <ul>    <li>    <a href="http://novaspivack.typepad.com/nova_spivacks_weblog/2007/10/web-30----the-a.html" id="link-id14a9d738">Web 3.0 The Best Official Definition Imaginable</a> -- Nova Spivack&#39;s </li>  </ul>
]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2008-11-28#1489">
  <rss:title>Introducing Virtuoso Universal Server (Cloud Edition) for Amazon EC2</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2008-11-28T19:27:12Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">What is it? A pre-installed edition of Virtuoso for Amazon&#39;s EC2 Cloud platform. What does it offer? From a Web Entrepreneur perspective it offers: Low cost entry point to a game-changing Web 3.0+ (and beyond) platform that combines SQL, RDF, XML, and Web Services functionality Flexible variable cost model (courtesy of EC2 DevPay) tightly bound to revenue generated by your services Delivers federated and/or centralized model flexibility for you SaaS based solutions Simple entry point for developing and deploying sophisticated database driven applications (SQL or RDF Linked Data Web oriented) Complete framework for exploiting OpenID, OAuth (including Role enhancements) that simplifies exploitation of these vital Identity and Data Access technologies Easily implement RDF Linked Data based Mail, Blogging, Wikis, Bookmarks, Calendaring, Discussion Forums, Tagging, Social-Networking as Data Space (data containers) features of your application or service offering Instant alleviation of challenges (e.g. service costs and agility) associated with Data Portability and Open Data Access across Web 2.0 data silos LDAP integration for Intranet / Extranet style applications. From the DBMS engine perspective it provides you with one or more pre-configured instances of Virtuoso that enable immediate exploitation of the following services: RDF Database (a Quad Store with SPARQL &amp; SPARUL Language &amp; Protocol support) SQL Database (with ODBC, JDBC, OLE-DB, ADO.NET, and XMLA driver access) XML Database (XML Schema, XQuery/Xpath, XSLT, Full Text Indexing) Full Text Indexing. From a Middleware perspective it provides: RDF Views (Wrappers / Semantic Covers) over SQL, XML, and other data sources accessible via SOAP or REST style Web Services Sponger Service for converting non RDF information resources into RDF Linked Data &quot;on the fly&quot; via a large collection of pre-installed RDFizer Cartridges. From the Web Server Platform perspective it provides an alternative to LAMP stack components such as MySQL and Apace by offering HTTP Web Server WebDAV Server Web Application Server (includes PHP runtime hosting) SOAP or REST style Web Services Deployment RDF Linked Data Deployment SPARQL (SPARQL Query Language) and SPARUL (SPARQL Update Language) endpoints Virtuoso Hosted PHP packages for MediaWiki, Drupal, Wordpress, and phpBB3 (just install the relevant Virtuoso Distro. Package). From the general System Administrator&#39;s perspective it provides: Online Backups (Backup Set dispatched to S3 buckets, FTP, or HTTP/WebDAV server locations) Synchronized Incremental Backups to Backup Set locations Backup Restore from Backup Set location (without exiting to EC2 shell). Higher level user oriented offerings include: OpenLink Data Explorer front-end for exploring the burgeoning Linked Data Web Ajax based SPARQL Query Builder (iSPARQL) that enables SPARQL Query construction by Example Ajax based SQL Query Builder (QBE) that enables SQL Query construction by Example. For Web 2.0 / 3.0 users, developers, and entrepreneurs it offers it includes Distributed Collaboration Tools &amp; Social Media realm functionality courtesy of ODS that includes: Point of presence on the Linked Data Web that meshes your Identity and your Data via URIs System generated Social Network Profile &amp; Contact Data via FOAF? System generated SIOC (Semantically Interconnected Online Community) Data Space (that includes a Social Graph) exposing all your Web data in RDF Linked Data form System generated OpenID and automatic integration with FOAF Transparent Data Integration across Facebook, Digg, LinkedIn, FriendFeed, Twitter, and any other Web 2.0 data space equipped with RSS / Atom support and/or REST style Web Services In-built support for SyncML which enables data synchronization with Mobile Phones. How Do I Get Going with It? Standard Installation Guide Personal or Service Specific DBpedia Installation Guide</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<h3>What is it?</h3>
<p>A pre-installed edition of <a href="http://virtuoso.openlinksw.com" id="link-id14bea838">Virtuoso</a> for Amazon&#39;s EC2 Cloud platform.</p>

<h3>What does it offer?</h3>
From a <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> Entrepreneur perspective it offers:
<ol>
<li>
Low cost entry point to a game-changing Web 3.0+ (and beyond) platform that combines <a href="http://dbpedia.org/resource/SQL" id="link-id11309b38">SQL</a>, <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id135f7988">RDF</a>, XML, and Web Services functionality</li>
<li>
Flexible variable cost model (courtesy of <a href="http://aws.amazon.com/devpay/" id="link-id17941018">EC2 DevPay</a>) tightly bound to revenue generated by your services</li>
<li>
Delivers federated and/or centralized model flexibility for you SaaS based solutions</li>
<li>
Simple entry point for developing and deploying sophisticated database driven applications (SQL or RDF <a href="http://dbpedia.org/resource/Linked_Data" id="link-id14ea6b10">Linked Data Web</a> oriented)</li>
<li>
Complete framework for exploiting OpenID, OAuth (including Role enhancements) that simplifies exploitation of these vital Identity and <a href="http://dbpedia.org/resource/Data">Data</a> Access technologies</li>
<li>Easily implement RDF Linked Data based Mail, Blogging, Wikis, Bookmarks, Calendaring, Discussion Forums, Tagging, Social-Networking as <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id11519928">Data Space</a> (data containers) features of your application or service offering</li>
<li>Instant alleviation of challenges (e.g. service costs and agility) associated with <a href="http://dbpedia.org/resource/DataPortability" id="link-id111cb610">Data Portability</a> and Open Data Access across Web 2.0 data silos</li>
<li>
LDAP integration for <a href="http://dbpedia.org/resource/Intranet" id="link-id114a8270">Intranet</a> / <a href="http://dbpedia.org/resource/Extranet" id="link-id10fe4f08">Extranet</a> style applications.</li>
</ol>
<p>From the DBMS engine perspective it provides you with one or more pre-configured instances of Virtuoso that enable immediate exploitation of the following services:</p>
<ol>
<li>
RDF Database (a Quad Store with <a href="http://dbpedia.org/resource/SPARQL" id="link-id11911bf8">SPARQL</a> &amp; SPARUL Language &amp; Protocol support)</li>
<li>
  <a href="http://dbpedia.org/resource/SQL" id="link-id110544c8">SQL</a> Database (with <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id1524c7d0">ODBC</a>, <a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id14cfb658">JDBC</a>, OLE-DB, <a href="http://dbpedia.org/resource/ADO.NET" id="link-id110ec6c8">ADO</a>.NET, and XMLA driver access)</li>
<li>XML Database (XML Schema, <a href="http://dbpedia.org/resource/XQuery" id="link-id10ebf218">XQuery</a>/<a href="http://dbpedia.org/resource/XPath" id="link-id142a7898">Xpath</a>, XSLT, Full Text Indexing)</li>
<li>Full Text Indexing.</li>
</ol>

<p>From a Middleware perspective it provides:</p>
<ol>
<li>
RDF Views (Wrappers / Semantic Covers) over SQL, XML, and other data sources accessible via SOAP or REST style Web Services</li>
<li>
Sponger Service for converting non RDF <a href="http://dbpedia.org/resource/Information" id="link-id11931c60">information</a> resources into RDF <a href="http://dbpedia.org/resource/Linked_Data" id="link-id118f7168">Linked Data</a> &quot;on the fly&quot; via a large collection of pre-installed  RDFizer Cartridges.</li>
</ol>

<p>From the Web Server Platform perspective it provides an alternative to LAMP stack components such as <a href="http://dbpedia.org/resource/MySQL" id="link-id10f7b780">MySQL</a> and Apace by offering</p>
<ol>
<li>
HTTP Web Server</li>
<li>
WebDAV Server</li>
<li>
Web <a href="http://dbpedia.org/resource/Application_server" id="link-id1268daa8">Application Server</a> (includes <a href="http://dbpedia.org/resource/PHP" id="link-id1585d238">PHP</a> runtime hosting)</li>
<li>
SOAP or REST style Web Services Deployment</li>
<li>
RDF Linked Data Deployment</li>
<li>
SPARQL (SPARQL Query Language) and SPARUL (SPARQL Update Language) endpoints</li>
<li>Virtuoso Hosted PHP packages for <a href="http://dbpedia.org/resource/MediaWiki" id="link-id15568818">MediaWiki</a>, <a href="http://dbpedia.org/resource/Drupal" id="link-id110bd7a8">Drupal</a>, <a href="http://dbpedia.org/resource/WordPress" id="link-id10f66918">Wordpress</a>, and <a href="http://dbpedia.org/resource/PhpBB" id="link-id13fda4d0">phpBB3</a> (just install the relevant Virtuoso Distro. Package).
</li>
</ol>

<p>From the general System Administrator&#39;s perspective it provides:</p>
<ol>
<li>
Online Backups (Backup Set dispatched to S3 buckets, FTP, or HTTP/WebDAV server locations)</li>
<li>Synchronized Incremental Backups to Backup Set locations</li>
<li>Backup Restore from Backup Set location (without exiting to EC2 shell).</li>
</ol>

<p>Higher level user oriented offerings include:</p>
<ol>
<li>OpenLink Data Explorer front-end for exploring the burgeoning Linked Data <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id11646dc8">Web</a>
</li>
<li>
Ajax based SPARQL Query Builder (iSPARQL) that enables SPARQL Query construction by Example</li>
<li>Ajax based SQL Query Builder (QBE) that enables SQL Query construction by Example.</li>
</ol>

<p>For Web 2.0 / 3.0 users, developers, and entrepreneurs it offers it includes Distributed Collaboration Tools &amp; Social Media realm functionality courtesy of <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id11009930">ODS</a> that includes:</p>
<ol>
<li>
Point of presence on the Linked Data Web that meshes your Identity and your Data via URIs</li>
<li>
System generated Social Network Profile &amp; Contact Data via <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id1185a1c0">FOAF</a>?</li>
<li>
System generated <a href="http://dbpedia.org/resource/SIOC" id="link-id14791890">SIOC</a> (Semantically Interconnected Online Community) <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id1577cad8">Data Space</a> (that includes a Social Graph) exposing all your Web data in RDF Linked Data form</li>
<li>
System generated OpenID and automatic integration with FOAF</li>
<li>
Transparent Data Integration across Facebook, Digg, LinkedIn, FriendFeed, Twitter, and any other Web 2.0 data space equipped with RSS / Atom support and/or REST style Web Services</li>
<li>
In-built support for SyncML which enables data synchronization with Mobile Phones.</li>
</ol>
<h3>How Do I Get Going with It?</h3>
<ul>
<li>
<a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/ODSInstallationEC2" id="link-id114e1600">Standard Installation Guide</a>
</li>
<li>
<a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VirtEC2AMIDBpediaInstall" id="link-id110a98e8">Personal or Service Specific DBpedia Installation Guide</a>
</li>
</ul>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2008-10-01#1447">
  <rss:title>Where Are All the RDF-based Semantic Web Applications?</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2008-10-01T23:09:00Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">In response to the &quot;Semantic Web Technology&quot; application classification scheme espoused by ReadWriteWeb (RWW), emphasized in the post titled: Where are all the RDF-based Semantic Web Apps?, here is my attempt to clarify and reintroduce what OpenLink Software offers (today) in relation to Semantic Web technology. From the RWW Top-Down category, which I interpret as: technologies that produce RDF from non RDF data sources. Our product portfolio is comprised of the following; Virtuoso Universal Server, OpenLink Data Spaces, OpenLink Ajax Toolkit, and OpenLink Data Explorer (which includes ubiquity commands). Virtuoso Universal Server functionality summary: Generation of RDF Linked Data Views of SQL, XML, and Web Services in general Deployment of RDF Linked Data &quot;On the Fly&quot; generation of RDF Linked Data from Document Web information resources (i.e. distillation of entities from their containers e.g. Web pages) via Cartridges / Drivers SPARQL query language support SPARQL extensions that bring SPARQL closer to SQL e.g Aggregates, Update, Insert, Delete Named Graph support (i.e. use of logical names to partition RDF data within Virtuoso&#39;s multi-model dbms engine) Inference Engine (currently in use re. DBpedia via Yago and UMBEL) Host and exposes data from Drupal, Wordpress, MediaWiki, phpBB3 as RDF Linked Data via in-built support for PHP runtime Available as an EC2 AMI etc.. OpenLink Data Spaces functionality summary: Simple mechanism for Linked Data Web enabling yourself by giving you an HTTP based User ID (a de-referencable URI) that is linked to a FOAF based Profile page and OpenID Binds all your data sources (blogs, wikis, bookmarks, photos, calendar items etc. ) to your URI so can &quot;Find&quot; things by only remembering your URI Makes your profile page and personal URI the focal point of Linked Data Web presence Delivers Data Portability (using data access by value or data access by reference) across data silos (e.g. Web 2.0 style social networks) Allows you make annotations about anything in your own Data Space(s) on the Web without exposure to RDF markup A Briefcase feature that provides a WebDAV driven RDF Linked Data variant of functionality seen in Mac OS X Spotlight and WinFS with the addition of SPARQL compliance Automatically generates RDFa in its (X)HTML pages Blog, Wiki, WebDAV File Server, Shared Bookmarks, Calendar, and other applications that look and feel like Web 2.0 counterparts but emitt RDF Linked Data amongst a plethora of data exchange formats Available as an EC2 AMI etc.. OpenLink Ajax Toolkit functionality summary: Provides binding to SQL, RDF, XML, and Web Services via Ajax Database Connectivity Layer (you only need an ODBC, JDBC, OLE-DB, ADO.NET, XMLA Driver, or Web Service on the backend for dynamic data access from Javascript) All controls are Ajax Database Connectivity bound (widgets get their data from Ajax Database Connectivity data sources) Bundled with Virtuoso and ODS installations. etc. OpenLink Data Explorer functionality summary Distills entities associated with information resource style containers (e.g. Web Pages or files) as RDF Linked Data Exposes the RDF based Linked Data graph associated with information resources (see the Linked Data behind Web pages) Ubiquity commands for invoking the above Available as a Hosted Service or Firefox Extension Bundled with Virtuoso and ODS installations etc. Note: Of course you could have simply looked up OpenLink Software&#39;s FOAF based Profile page (*note the Linked Data Explorer tab*), or simply passed the FOAF profile page URL to a Linked Data aware client application such as: OpenLink Data Explorer, Zitgist Data Viewer, Marbles, and Tabulator, and obtained information. Remember, OpenLink Software is an Entity of Type: foaf:Organization, on the burgeoning Linked Data Web :-) Related Linked Data Planet Keynote (RDFa based remix edition) On The Cusp: A Global Review of the Semantic Web Industry.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>
In response to the &quot;<a href="http://dbpedia.org/resource/Semantic_Web" id="link-id15971040">Semantic Web</a> Technology&quot; application classification scheme espoused by <a href="http://www.readwriteweb.com" id="link-id16391540">ReadWriteWeb</a> (RWW), emphasized in the post titled:  <a href="http://www.readwriteweb.com/archives/rdf_semantic_web_apps.php" id="link-id1157eaa0">Where are all the RDF-based Semantic Web Apps?</a>, here is my attempt to clarify and reintroduce what <a href="http://www.openlinksw.com/dataspace/organization/openlink#this" id="link-id15a43758">OpenLink Software</a> offers (today) in relation to Semantic Web technology.
</p>
<p>
From the RWW Top-Down category, which I interpret as: technologies that produce RDF from non RDF <a href="http://dbpedia.org/resource/Data">data</a> sources. Our product portfolio is comprised of the following; <a href="http://virtuoso.openlinksw.com" id="link-id14f05818">Virtuoso Universal Server</a>, <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id162c8630">OpenLink Data Spaces</a>, <a href="http://oat.openlinksw.com" id="link-id134e1a00">OpenLink Ajax Toolkit</a>, and <a href="http://ode.openlinksw.com" id="link-id160b3bf8">OpenLink Data Explorer</a> (which includes ubiquity commands).</p>

<h3>Virtuoso Universal Server functionality summary:</h3>

<ol>
  <li>Generation of RDF <a href="http://dbpedia.org/resource/Linked_Data" id="link-id161d5f50">Linked Data</a> Views of <a href="http://dbpedia.org/resource/SQL" id="link-id161d5978">SQL</a>, XML, and <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> Services in general </li>
  <li>Deployment of RDF Linked Data </li>
  <li>&quot;On the Fly&quot; generation of RDF Linked Data from Document Web <a href="http://www.w3.org/TR/webarch/" id="link-id178bbc08">information resources</a> (i.e. distillation of entities from their containers e.g. Web pages) via Cartridges / Drivers</li>
  <li>
  <a href="http://dbpedia.org/resource/SPARQL" id="link-id162c2118">SPARQL</a> query language support </li>
  <li>SPARQL extensions that bring SPARQL closer to SQL e.g Aggregates, Update, Insert, Delete
    Named Graph support (i.e. use of logical names to partition RDF data within Virtuoso&#39;s multi-model dbms engine)    </li>
  <li>Inference Engine (currently in use re. <a href="http://dbpedia.org/resource/DBpedia" id="link-id14f563c0">DBpedia</a> via Yago and <a href="http://umbel.org/about/" id="link-id113273b8">UMBEL</a>)</li>
  <li>Host and exposes data from <a href="http://dbpedia.org/resource/Drupal" id="link-id123d3bd8">Drupal</a>, <a href="http://dbpedia.org/resource/WordPress" id="link-id141adf40">Wordpress</a>, <a href="http://dbpedia.org/resource/MediaWiki" id="link-id1604b450">MediaWiki</a>, <a href="http://dbpedia.org/resource/PhpBB" id="link-id141013a8">phpBB3</a> as RDF Linked Data via in-built support for <a href="http://dbpedia.org/resource/PHP" id="link-id14661e58">PHP</a> runtime</li>
  <li>
  <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/ODSInstallationEC2" id="link-id146c84d0">Available as an EC2 AMI</a>
</li>
  <li>etc..</li>
</ol>
<h3>OpenLink Data Spaces functionality summary:</h3>
<ol>
  <li>Simple mechanism for Linked Data <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id15473770">Web</a> enabling yourself by giving you an <a href="http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/GetAPersonalURIIn5MinutesOrLess" id="link-id15f6d278">HTTP based User ID</a> (a de-referencable <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id15aaeb68">URI</a>) that is linked to a <a href="http://myopenlink.net/dataspace/person/kidehen" id="link-id15a7a840">FOAF based Profile page</a> and OpenID</li>
  <li>Binds all your data sources (blogs, wikis, bookmarks, photos, calendar items etc. ) to your URI so can &quot;Find&quot; things by only remembering your URI</li>
  <li>Makes your profile page and personal URI the focal point of Linked Data Web presence</li>
  <li>Delivers Data Portability (using data access by value or <a href="http://dbpedia.org/resource/Reference_(computer_science)" id="link-id16212838">data access by reference</a>) across data silos (e.g. Web 2.0 style social networks)</li>
  <li>Allows you make annotations about anything in your own <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id14668010">Data Space</a>(s) on the Web without exposure to RDF markup</li>
  <li>A Briefcase feature that provides a WebDAV driven RDF Linked Data variant of functionality seen in Mac OS X Spotlight and WinFS with the addition of SPARQL compliance</li>
  <li>Automatically generates <a href="http://dbpedia.org/resource/RDFa" id="link-id14691440">RDFa</a> in its (X)HTML pages</li>
  <li>
  <a href="http://dbpedia.org/resource/Blog" id="link-id14fae7b8">Blog</a>, Wiki, WebDAV File Server, Shared Bookmarks, Calendar, and other applications that look and feel like Web 2.0 counterparts but emitt RDF Linked Data amongst a plethora of data exchange formats</li>
  <li>Available as an EC2 AMI</li>
  <li>etc..</li>
</ol>
<h3>OpenLink Ajax Toolkit functionality summary:</h3>
<ol>
  <li>Provides binding to SQL, RDF, XML, and Web Services via Ajax Database Connectivity Layer (you only need an <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id11550548">ODBC</a>, <a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id13ae5f68">JDBC</a>, OLE-DB, <a href="http://dbpedia.org/resource/ADO.NET" id="link-id162803e8">ADO</a>.NET,  XMLA Driver, or Web Service on the backend for dynamic data access from Javascript)</li>
  <li>All controls are Ajax Database Connectivity bound (widgets get their data from Ajax Database Connectivity data sources)</li>
  <li>Bundled with Virtuoso and <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces" id="link-id161dfe90">ODS</a> installations.</li>
  <li>etc.</li>
</ol>
<h3>OpenLink Data Explorer functionality summary</h3>
<ol>
  <li>Distills entities associated with information resource style containers (e.g. Web Pages or files) as RDF Linked Data</li>
  <li>Exposes the RDF based <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id12a42ed8">Linked Data graph</a> associated with information resources (see the Linked Data behind Web pages)</li>
  <li>Ubiquity commands for invoking the above</li>
  <li>Available as a <a href="http://linkeddata.uriburner.com/ode" id="link-id15a0d2b0">Hosted Service</a> or <a href="http://ode.openlinksw.com" id="link-id138b9fa8">Firefox Extension</a>
</li>
  <li>Bundled with Virtuoso and ODS installations</li>
  <li>etc.</li>
</ol>
<h3>Note:</h3>
<p>Of course you could have simply looked up <a href="http://www.openlinksw.com/dataspace/organization/openlink" id="link-id14ef2c10">OpenLink Software&#39;s FOAF based Profile page</a> (*note the Linked Data Explorer tab*), or simply passed the <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id14cbf5c8">FOAF</a> profile page <a href="http://dbpedia.org/resource/Uniform_Resource_Locator" id="link-id16453e28">URL</a> to a Linked Data aware client application such as: <a href="http://linkeddata.uriburner.com/ode" id="link-id15a80500">OpenLink Data Explorer</a>, <a href="http://zitgist.com/about/" id="link-id1586a360">Zitgist</a> <a href="http://dataviewer.zitgist.com" id="link-id16249f60">Data Viewer</a>, <a href="http://beckr.org/marbles" id="link-id15993fb0">Marbles</a>, and <a href="http://dig.csail.mit.edu/2005/ajar/release/tabulator/0.8/tab.html" id="link-id14d63048">Tabulator</a>, and obtained information. Remember, <a href="http://www.openlinksw.com/dataspace/organization/openlink#this" id="link-id138ba838">OpenLink Software</a> is an <a href="http://dbpedia.org/resource/Entity" id="link-id1173e120">Entity</a> of Type: <a href="http://xmlns.com/foaf/0.1/Organization" id="link-id138b87b8">foaf:Organization</a>, on the burgeoning Linked Data Web :-)</p>

<h3>Related</h3>
<ul>
<li>
  <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2_TimBL_v3.html" id="link-id163a0c88">Linked Data Planet Keynote</a> (RDFa based remix edition)</li>
<li>
  <a href="http://semanticbusiness.blogspot.com/2008/09/report-on-cusp-global-review-of.html" id="link-id11471a40">On The Cusp: A Global Review of the Semantic Web Industry.</a>
</li>
</ul>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2008-07-28#1397">
  <rss:title>WUPnP Cheatsheet</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2008-07-29T03:37:55Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">WUPnP Cheatsheet: &quot; The Web Universal Plug and Play (WUPnP) Cheatsheet: Essentially, if you build an application and use the technologies suggested in the ‘glue section’ then your web application/service (whether it’s front-end or back-end) will fit into many many other web applications/services… and therefore also more manageable for the future! This is WUPnP. Key technologies for making your services/applications as sticky as possible: Dereferenceable URI’s (which indicate HTTP networking) OpenID OAuth SPARQL Linked Data RDF (or RDFa) and OWL Web-based plug and play fun!&quot; (Via Daniel Lewis.)</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p> <a href="http://vanirsystems.com/danielsblog/2008/07/28/wupnp-cheatsheet/#comments" id="link-id133b9048">WUPnP Cheatsheet</a>: &quot;</p> <p>The <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id0x1ccdfc68">Web</a> Universal Plug and Play (<acronym title="Web Universal Plug and Play">WUPnP</acronym>) Cheatsheet:</p> <p> <img src="http://vanirsystems.com/images/wupnparch.png" alt="Web Universal Plug and Play (WUPnP) Cheatsheet" width="50%" />  </p> <p>Essentially, if you build an application and use the technologies suggested in the ‘glue section’ then your <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id0x1d626818">web</a> application/service (whether it’s front-end or back-end) will fit into many many other <a href="http://dbpedia.org/resource/World_Wide_Web">web</a> applications/services… and therefore also more manageable for the future! This is WUPnP.</p> <p>Key technologies for making your services/applications as sticky as possible:</p> <ul> <li> <a href="http://en.wikipedia.org/wiki/Dereferenceable_Uniform_Resource_Identifier" id="link-id1016cbd8">Dereferenceable URI’s</a> (which indicate <a href="http://en.wikipedia.org/wiki/Hypertext_Transfer_Protocol" id="link-id101d7790">HTTP</a> networking)</li> <li> <a href="http://en.wikipedia.org/wiki/OpenID" id="link-id12ea5e68">OpenID</a> </li> <li> <a href="http://en.wikipedia.org/wiki/OAuth" id="link-id12e1acf0">OAuth</a> </li> <li> <a href="http://en.wikipedia.org/wiki/SPARQL" id="link-id133d34e0">SPARQL</a> </li> <li> <a href="http://en.wikipedia.org/wiki/Linked_Data" id="link-id106a7040">Linked Data</a> <a href="http://en.wikipedia.org/wiki/Resource_Description_Framework" id="link-id1072d890">RDF</a> (or <a href="http://en.wikipedia.org/wiki/RDFa" id="link-id14040c38">RDFa</a>) and <a href="http://en.wikipedia.org/wiki/Web_Ontology_Language" id="link-id1044dda8">OWL</a> </li> </ul> <p>Web-based plug and play fun!</p>&quot; <p>(Via <a href="http://vanirsystems.com/danielsblog" id="link-id10a15838">Daniel Lewis</a>.)</p>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2008-06-26#1391">
  <rss:title>Response to: Where&#39;s the Killer Semantic Web Application (Update #2)</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2008-06-26T18:28:14Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">As is often the case these days, it&#39;s much easier to drop a blog post than it is to make a simple comment in an &quot;old media&quot; style data space :-( My use of &quot;old media&quot; implies: a place that still seeks subscriber data (no OpenID etc..), for the umpteenth time, as the toll fee for discourse development and participation on the Web. Anyway, here is what I attempted to post as a comment to Dan Grigorovici&#39;s post titled: Where is the Semantic Web Killer App? Dan, An intriguing post to say the least :-) &quot;Linked Data&quot; and &quot;Semantic Web&quot; aren&#39;t synonymous, they are simply connected, infrastructure DNA-wise. You can have &quot;Semantic Web&quot; style graphs (i.e RDF Data) and not have &quot;Linked Data&quot; as per Linked Data deployment tenets and best practices, a very important point. I&#39;ve stated repeatedly, the &quot;Linked Data&quot; emphasis has more to do with focusing on a point of crystallization within the larger &quot;Semantic Web&quot; vision, so here is a quick recap: What is Linked Data? A term coined by TimBL that describes an application of HTTP to the time-tested process of &quot;Data Access by Reference&quot;. &quot;Linked Data&quot; adds vital items to the &quot;Data Access by Reference&quot; pattern that have been erstwhile unattainable: The use of a Data Source Naming scoped to Database / Data Container Records as opposed to Tables, Views, Stored Procedures, Databases, and other Record Container tuple collections. Example: in ODBC / JDBC, a Data Source Name&#39;s scope stops at the Table / View level. In the Linked Data realm you get an added layer of granularity due to record level name scope Incorporation of HTTP into the Data Source Naming scheme, which injects the expanse of the Web into the Data Access Range of the Data Source Name (i.e. a Named Record); so you can reference a record&#39;s description directly via HTTP which is simply a major deal (to put things mildly). So we have HTTP based URIs as the Data Sources Names for a &quot;Linked Data Web&quot; i.e a Web of inter-connected Data Source Names that de-emphasize the importance of their host containers (Compound Documents / Information Resources). The business case or value proposition of &quot;Linked Data&quot; is synonymous with the value proposition of data access technologies such as ODBC, JDBC. ADO.NET, OLE-DB, XMLA, and others (enterprise or consumer) in relation to the Individual and Enterprise pursuit of agility; in a realm where data is growing exponentially, and the maximum processing time in a single day remains 24 hrs. Data Access &amp; Data Integration are timeless challenges due to the following constants: Structured Data Schema Heterogeneity - we will always model the same things differently Dirtiness of Data within Structured Data Containers - we are error prone due to laziness / sloppiness, time constraints, and the inherent limitation of our DNA based CPUs when dealing with large volumes of data. Note: The line between the Enterprise &amp; Individuals continue to blur by the second, this is something I covered during my Linked Data Planet keynote, which is like most things I put on the Web (via this blog data space), is a live and practical demonstration of the virtues of Linked Data courtesy of RDFa, the Bibliographic Ontology, and dereferencable URIs (i.e. HTTP based Data Source Names for Documents and the Entities they host). Related Linked Data FAQ - by Mike Bergman The Planetary Computer from Wired Magazine - which is basically the effect of Linked Data under a different label (note to Wired: &quot;Tired of old Media repetitive Registrations&quot; when seeking to make comments in the OpenID era!).</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>As is often the case these days, it&#39;s much easier to drop a <a href="http://dbpedia.org/resource/Blog" id="link-id13519b98">blog</a> post than it is to make a simple comment in an &quot;old media&quot; style<a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id134e92c8"> data space </a>:-(</p> <blockquote>
 <p>
  <cite>My use of &quot;old media&quot; implies: a place that still seeks subscriber data (no OpenID etc..), for the umpteenth time, as the toll fee for discourse development and participation on the Web.</cite>
 </p>
</blockquote>
<p>Anyway, here is what I attempted to post as a comment to Dan Grigorovici&#39;s post titled: <a href="http://www.semanticweb.com/article.php/12160_3753806_2" id="link-id134dfb80">Where is the Semantic Web Killer App?</a>
</p>


<p>Dan,</p>

<p>An intriguing post to say the least :-) </p>

<p>&quot;<a href="http://dbpedia.org/resource/Linked_Data" id="link-id134265c0">Linked Data</a>&quot; and &quot;<a href="http://dbpedia.org/resource/Semantic_Web" id="link-id133d7048">Semantic Web</a>&quot; aren&#39;t synonymous, they are simply connected, infrastructure DNA-wise. You can have &quot;<a href="http://dbpedia.org/resource/Semantic_Web" id="link-id1096cb70">Semantic Web</a>&quot; style graphs (i.e RDF Data) and not have &quot;<a href="http://dbpedia.org/resource/Linked_Data" id="link-id133f0f48">Linked Data</a>&quot; as per <a href="http://dbpedia.org/resource/Linked_Data" id="link-id134fc7c0">Linked Data</a> deployment tenets and best practices, a very important point.</p>

<p>I&#39;ve stated repeatedly, the &quot;<a href="http://dbpedia.org/resource/Linked_Data" id="link-id134f03e8">Linked Data</a>&quot; emphasis has more to do with focusing on a point of crystallization within the larger &quot;<a href="http://dbpedia.org/resource/Semantic_Web" id="link-id134104f0">Semantic Web</a>&quot; vision, so here is a quick recap:</p>

<h3>What is <a href="http://dbpedia.org/resource/Linked_Data" id="link-id133decd0">Linked Data</a>?</h3>
<p>A term coined by <a href="http://www.w3.org/People/Berners-Lee/card#i" id="link-id1340dd28">TimBL</a> that describes an application of HTTP to the time-tested process of &quot;<a href="http://dbpedia.org/resource/Reference_(computer_science)">Data Access by Reference</a>&quot;. &quot;<a href="http://dbpedia.org/resource/Linked_Data" id="link-id10695c20">Linked Data</a>&quot; adds vital items to the &quot;Data Access by Reference&quot; pattern that have been erstwhile unattainable:</p>
<ul>
<li>
The use of a Data Source Naming scoped to Database / Data Container Records as opposed to Tables, Views, Stored Procedures, Databases, and other Record Container tuple collections.  Example: in <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-idd9c8af8">ODBC</a> / <a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id130b0df0">JDBC</a>, a Data Source Name&#39;s scope stops at the Table / View level. In the <a href="http://dbpedia.org/resource/Linked_Data">Linked Data</a> realm you get an added layer of granularity due to record level name scope</li>

<li>Incorporation of HTTP into the Data Source Naming scheme, which injects the expanse of the Web into the Data Access Range of the Data Source Name (i.e. a Named Record); so you can reference a record&#39;s description directly via HTTP which is simply a major deal (to put things mildly).</li>
</ul>

<p>So we have HTTP based URIs as the Data Sources Names for a &quot;Linked Data <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id1044a2d8">Web</a>&quot; i.e a Web of inter-connected Data Source Names that de-emphasize the importance of their host containers (Compound Documents / <a href="http://dbpedia.org/resource/Information" id="link-id134e0d38">Information</a> Resources).</p>

<p>The business case or value proposition of &quot;Linked Data&quot; is synonymous with the value proposition of data access technologies such as <a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id13400500">ODBC</a>, <a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id134f0250">JDBC</a>. <a href="http://dbpedia.org/resource/ADO.NET" id="link-id10923840">ADO</a>.<a href="http://dbpedia.org/resource/ADO.NET" id="link-id134ef878">NET</a>, OLE-DB, XMLA, and others (enterprise or consumer) in relation to the Individual and Enterprise pursuit of agility; in a realm where data is growing exponentially, and the maximum processing time in a single day remains 24 hrs. Data Access &amp; Data Integration are timeless challenges due to the following constants:</p>

<ul>
<li>
Structured Data Schema Heterogeneity - we will always model the same things differently</li>
<li>Dirtiness of Data within Structured Data Containers - we are error prone due to laziness / sloppiness, time constraints, and the inherent limitation of our DNA based CPUs when dealing with large volumes of data.</li>
</ul>
<p>
Note: The line between the Enterprise &amp; Individuals continue to blur by the second, this is something I covered during my <a href="http://virtuoso.openlinksw.com/presentations/Creating_Deploying_Exploiting_Linked_Data2/Creating_Deploying_Exploiting_Linked_Data2.html" id="link-id13479488">Linked Data Planet keynote</a>, which is like most things I put on the Web (via this <a href="http://dbpedia.org/resource/Blog" id="link-id130ac870">blog</a> <a href="http://en.wikipedia.org/wiki/Data_Spaces" id="link-id10923ba8">data space</a>), is a live and practical demonstration of the virtues of Linked Data courtesy of <a href="http://dbpedia.org/resource/RDFa" id="link-id133fd270">RDFa</a>, the <a href="http://bibliontology.com/" id="link-id134248d8">Bibliographic Ontology</a>, and dereferencable URIs (i.e. HTTP based Data Source Names for Documents and the Entities they host).</p>
<h3>Related</h3>
<ul>
<li>
  <a href="http://zitgist.com/labs/linked_data.html" id="link-id104778a8">Linked Data FAQ</a> - by <a href="http://community.linkeddata.org/dataspace/person/mkbergman#this" id="link-idd8e71b0">Mike Bergman</a>
</li>
<li>
  <a href="http://www.wired.com/special_multimedia/2008/st_infoporn_1607" id="link-id134c1e80">The Planetary Computer</a> from <a href="http://www.wired.com" id="link-id13416518">Wired Magazine</a> - which is basically the effect of Linked Data under a different label (note to Wired: &quot;Tired of old Media repetitive Registrations&quot; when seeking to make comments in the OpenID era!).</li>
</ul>
]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2008-04-10#1334">
  <rss:title>Linked Data enabling PHP Applications</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2008-04-10T18:09:49Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Daniel lewis has penned a variation of post about Linked Data enabling PHP applications such as: Wordpress, phpBB3, MediaWiki etc. Daniel simplifies my post by using diagrams to depict the different paths for PHP based applications exposing Linked Data - especially those that already provide a significant amount of the content that drives Web 2.0. If all the content in Web 2.0 information resources are distillable into discrete data objects endowed with HTTP based IDs (URIs), with zero &quot;RDF handcrafting Tax&quot;, what do we end up with? A Giant Global Graph of Linked Data; the Web as a Database. So, what used to apply exclusively, within enterprise settings re. Oracle, DB2, Informix, Ingres, Sybase, Microsoft SQL Server, MySQL, PostrgeSQL, Progress Open Edge, Firebird, and others, now applies to the Web. The Web becomes the &quot;Distributed Database Bus&quot; that connects database records across disparate databases (or Data Spaces). These databases manage and expose records that are remotely accessible &quot;by reference&quot; via HTTP. As I&#39;ve stated at every opportunity in the past, Web 2.0 is the greatest thing that every happened to the Semantic Web vision :-) Without the &quot;Web 2.0 Data Silo Conundrum&quot; we wouldn&#39;t have the cry for &quot;Data Portability&quot; that brings a lot of clarity to some fundamental Web 2.0 limitations that end-users ultimately find unacceptable. In the late &#39;80s, the SQL Access Group (now part of X/Open) addressed a similar problem with RDBMS silos within the enterprise that lead to the SAG CLI which is exists today as Open Database Connectivity. In a sense we now have WODBC (Web Open Database Connectivity), comprised of Web Services based CLIs and/or traditional back-end DBMS CLIs (ODBC, JDBC, ADO.NET, OLE-DB, or Native), Query Language (SPARQL Query Language), and a Wire Protocol (HTTP based SPARQL Protocol) delivering Web infrastructure equivalents of SQL and RDA, but much better, and with much broader scope for delivering profound value due to the Web&#39;s inherent openness. Today&#39;s PHP, Python, Ruby, Tcl, Perl, ASP.NET developer is the enterprise 4GL developer of yore, without enterprise confinement. We could even be talking about 5GL development once the Linked Data interaction is meshed with dynamic languages (delivering higher levels of abstraction at the language and data interaction levels). Even the underlying schemas and basic design will evolve from Closed World (solely) to a mesh of Closed &amp; Open World view schemas.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>
<a href="http://myopenlink.net/dataspace/person/danieljohnlewis#this" id="link-id10820610">Daniel lewis</a> has penned a variation of post about <a href="http://vanirsystems.com/danielsblog/2008/04/10/simplified-adding-wordpress-blogs-into-the-linked-data-web-using-virtuoso/" id="link-id10827948">Linked Data enabling PHP applications</a> such as: <a href="http://dbpedia.org/resource/WordPress" id="link-id10426278">Wordpress</a>, <a href="http://dbpedia.org/resource/PhpBB" id="link-id13f431c0">phpBB3</a>, <a href="http://dbpedia.org/resource/MediaWiki" id="link-id10dd8760">MediaWiki</a> etc.</p>

<p>Daniel simplifies my post by using diagrams to depict the different paths for <a href="http://dbpedia.org/resource/PHP" id="link-id10adcc08">PHP</a> based applications exposing <a href="http://dbpedia.org/resource/Linked_Data" id="link-id107b4e60">Linked Data</a> - especially those that already provide a significant amount of the content that drives <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id13b0ab48">Web</a> 2.0.</p>

<p>If all the content in <a href="http://dbpedia.org/resource/World_Wide_Web" id="link-id0x1d499470">Web</a> 2.0 <a href="http://dbpedia.org/resource/Information" id="link-id12bd3b10">information</a> resources are distillable into discrete <a href="http://dbpedia.org/resource/Data" id="link-id10962060">data</a> objects endowed with <a href="http://dbpedia.org/resource/Hypertext_Transfer_Protocol" id="link-id176a30e8">HTTP</a> based IDs (URIs), with zero &quot;<a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=rdf%20tax&type=text&output=html" id="link-id1098bcd8">RDF handcrafting Tax</a>&quot;, what do we end up with? A <a href="http://dbpedia.org/resource/Giant_Global_Graph" id="link-id1372ce88">Giant Global Graph</a> of <a href="http://dbpedia.org/resource/Linked_Data" id="link-id0xa29f0658">Linked Data</a>; the <a href="http://dbpedia.org/resource/World_Wide_Web">Web</a> as a Database.</p> <p>So, what used to apply exclusively, within enterprise settings re. <a href="http://dbpedia.org/resource/Oracle_Database" id="link-id12d91448">Oracle</a>, <a href="http://dbpedia.org/resource/IBM_DB2" id="link-id13dd27d8">DB2</a>, <a href="http://dbpedia.org/resource/IBM_Informix" id="link-id108e6b98">Informix</a>, <a href="http://dbpedia.org/resource/Ingres" id="link-id13383708">Ingres</a>, <a href="http://dbpedia.org/resource/Sybase" id="link-idfed8aa8">Sybase</a>, <a href="http://dbpedia.org/resource/Microsoft_SQL_Server" id="link-id10b8b190">Microsoft SQL Server</a>, <a href="http://dbpedia.org/resource/MySQL" id="link-id13066ea8">MySQL</a>, PostrgeSQL, Progress Open Edge, <a href="http://dbpedia.org/resource/Firebird_database_server" id="link-id104f0a78">Firebird</a>, and others, now applies to the Web. The Web becomes the &quot;<a href="http://dbpedia.org/resource/federated_database_system" id="link-id105a5340">Distributed Database</a> Bus&quot; that connects database records across disparate databases (or <a href="http://dbpedia.org/resource/Data" id="link-id0xc706c68">Data</a> Spaces). These databases manage and expose records that are remotely accessible &quot;by reference&quot; via <a href="http://dbpedia.org/resource/Hypertext_Transfer_Protocol" id="link-id0x1c8f7fe0">HTTP</a>.</p>

<p>As I&#39;ve stated at every opportunity in the past, Web 2.0 is the greatest thing that every happened to the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id13d65278">Semantic Web</a> vision :-) Without the &quot;<a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=Web%202.0%20%20conundrum&type=text&output=html" id="link-id100d16d0">Web 2.0 Data Silo Conundrum</a>&quot; we wouldn&#39;t have the cry for &quot;<a href="http://dbpedia.org/resource/Data">Data</a> Portability&quot; that brings a lot of clarity to some fundamental Web 2.0 limitations that end-users ultimately find unacceptable.</p> 
<p>
In the late &#39;80s, the <a href="http://dbpedia.org/resource/SQL" id="link-idff4f0d0">SQL</a> <a href="http://dbpedia.org/resource/SQL_Access_Group" id="link-id138fbd40">Access Group</a> (now part of <a href="http://dbpedia.org/resource/X/Open" id="link-id104ee010">X</a>/<a href="http://dbpedia.org/resource/X/Open" id="link-id0xac9eab8">Open</a>) addressed a similar problem with <a href="http://dbpedia.org/resource/Relational_database_management_system" id="link-id106d2008">RDBMS</a> silos within the enterprise that lead to the SAG <a href="http://dbpedia.org/resource/Call_Level_Interface" id="link-id105d45d0">CLI</a> which is exists today as Open Database Connectivity.</p>

<p>In a sense we now have WODBC (Web Open Database Connectivity), comprised of Web Services based CLIs and/or traditional back-end DBMS CLIs (<a href="http://dbpedia.org/resource/Open_Database_Connectivity" id="link-id13f58708">ODBC</a>, <a href="http://dbpedia.org/resource/Java_Database_Connectivity" id="link-id10aa81e0">JDBC</a>, <a href="http://dbpedia.org/resource/ADO.NET" id="link-id5fddb68">ADO</a>.<a href="http://dbpedia.org/resource/ADO.NET" id="link-id0x9f085a10">NET</a>, OLE-DB, or Native),  Query Language (<a href="http://dbpedia.org/resource/SPARQL" id="link-id10adb5c8">SPARQL</a> Query Language), and a Wire Protocol (<a href="http://dbpedia.org/resource/Hypertext_Transfer_Protocol">HTTP</a> based <a href="http://www.w3.org/TR/rdf-sparql-protocol/" id="link-id126fa068">SPARQL Protocol</a>) delivering Web infrastructure equivalents of <a href="http://dbpedia.org/resource/SQL" id="link-id0x1d0a5fc8">SQL</a> and RDA, but much better, and with much broader scope for delivering profound value due to the Web&#39;s inherent openness. Today&#39;s <a href="http://dbpedia.org/resource/PHP" id="link-id0xc88ed68">PHP</a>, <a href="http://dbpedia.org/resource/Python_programming_language" id="link-id10a70530">Python</a>, <a href="http://dbpedia.org/resource/Ruby_programming_language" id="link-id13d9da18">Ruby</a>, <a href="http://dbpedia.org/resource/Tcl" id="link-id10a3c2a8">Tcl</a>, <a href="http://dbpedia.org/resource/Perl" id="link-id13e1b6f0">Perl</a>, <a href="http://dbpedia.org/resource/ASP.NET" id="link-id10810388">ASP</a>.<a href="http://dbpedia.org/resource/ASP.NET" id="link-id0xa22ce378">NET</a>  developer is the enterprise <a href="http://dbpedia.org/resource/4GL" id="link-id1396a500">4GL</a> developer of yore, without enterprise confinement. We could even be talking about <a href="http://dbpedia.org/resource/5GL" id="link-id1077f250">5GL</a> development once the <a href="http://dbpedia.org/resource/Linked_Data">Linked Data</a> interaction is meshed with dynamic languages (delivering higher levels of abstraction at the language and data interaction levels). Even the underlying schemas and  basic design will evolve from <a href="http://dbpedia.org/resource/Closed_world_assumption" id="link-id10b280c8">Closed World</a> (solely) to a mesh of Closed &amp; <a href="http://dbpedia.org/resource/Open_world_assumption" id="link-id104b9978">Open World</a> view schemas.</p>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2008-02-08#1314">
  <rss:title>10 Reasons to use OpenLink Data Spaces (ODS)</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2008-02-08T17:33:45Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Via post by Daniel Lewis, titled:10 Reasons to use OpenLink Data Spaces There are quite a few reasons to use OpenLink Data Spaces (ODS). Here are 10 of the reasons why I use ODS: Its native support of DataPortability Recommendations such as RSS, Atom, APML, Yadis, OPML, Microformats, FOAF, SIOC, OpenID and OAuth. Its native support of Semantic Web Technologies such as: RDF and SPARQL/SPARUL for querying. Everything in ODS is an Object with its own URI, this is due to the underlying Object-Relational Architecture provided by Virtuoso. It has all the social media components that you could need, including: blogs, wikis, social networks, feed readers, CRM and a calendar. It is expandable by installing pre-configured components (called VADs), or by re-configuring a LAMP application to use Virtuoso. Some examples of current VADs include: MediaWiki, Wordpress and Drupal. It works with external webservices such as: Facebook, del.icio.us and Flickr. Everything within OpenLink Data Spaces is Linked Data, which provides more meaningful information than just plain structural information. This meaningful information could be used for complex inferencing systems, as ODS can be seen as a Knowledge Base. ODS builds bridges between the existing static-document based web (aka âWeb 1.0â), the more dynamic,Â  services-oriented, social and/or user-orientated webs (aka âWeb 2.0â) and the web which we are just going into, which is more data-orientated (aka âWeb 3.0â or âLinked Data Webâ). It is fully supportive of Cloud Computing, and can be installed on Amazon EC2. Its released free under the GNU General Public License (GPL). [note]However, it is technically dual licensed as it lays on top of the Virtuoso Universal Server which has both Commercial and GPL licensing[/note] The features above collectively provide users with a Linked Data Junction Box that may reside with corporate intranets or &quot;out in the clouds&quot; (Internet). You can consume, share, and publish data in a myriad of formats using a plethora of protocols, without any programming. ODS is simply about exposing the data from your Web 1.0, 2.0, 3.0 application interactions in structured from, with Linking, Sharing, and ultimately Meshing (not Mashing) in mind. Note: Although ODS is equipped with a broad array of Web 2.0 style Applications, you do not need to use native ODS apps in order to exploit it&#39;s power. It binds to anything that supports the relevant protocols and data formats.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Via post by <a href="http://vanirsystems.com/danielsblog" id="link-id1480d7c0">Daniel Lewis</a>, titled:<a href="http://vanirsystems.com/danielsblog/2008/02/08/10-reasons-to-use-openlink-data-spaces/#comments" id="link-id1320a618">10 Reasons to use OpenLink Data Spaces</a>
</p>
<blockquote>
<p>There are quite a few reasons to use <a href="http://en.wikipedia.org/wiki/OpenLink_Data_Space" id="link-id103eb060">OpenLink Data Spaces (ODS)</a>. Here are 10 of the reasons why I use ODS:</p>
<ol>
<li>Its native support of DataPortability Recommendations such as <a href="http://dbpedia.org/resource/RSS" id="link-id18957e88">RSS</a>, <a href="http://dbpedia.org/resource/Atom_%28standard%29" id="link-id1410a9c0">Atom</a>, <a href="http://www.apml.org/" id="link-idfde4b90">APML</a>, <a href="http://dbpedia.org/resource/Yadis" id="link-id1328c260">Yadis</a>, <a href="http://dbpedia.org/resource/OPML" id="link-id10133f70">OPML</a>, <a href="http://dbpedia.org/resource/Microformat" id="link-id16e19be0">Microformats</a>, <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id12deef98">FOAF</a>, <a href="http://dbpedia.org/resource/SIOC" id="link-id15fb99b0">SIOC</a>, <a href="http://dbpedia.org/resource/OpenID" id="link-id1390ae10">OpenID</a> and <a href="http://en.wikipedia.org/wiki/OAuth" id="link-id14dcce70">OAuth</a>.</li>
<li>Its native support of Semantic Web Technologies such as: <a href="http://dbpedia.org/resource/Resource_Description_Framework" id="link-id15fc75a0">RDF</a> and <a href="http://dbpedia.org/resource/SPARQL" id="link-id14255238">SPARQL</a>/<a href="http://jena.hpl.hp.com/~afs/SPARQL-Update.html" id="link-id15fe2e40">SPARUL</a> for querying.</li>
<li>Everything in ODS is an <a href="http://dbpedia.org/resource/Object_%28computer_science%29" id="link-id11c204a0">Object</a> with its own <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier" id="link-id14812560">URI</a>, this is due to the underlying <a href="http://dbpedia.org/resource/Object-relational_database" id="link-idf663e08">Object-Relational</a> Architecture provided by <a href="http://dbpedia.org/resource/Virtuoso_Universal_Server" id="link-id1484e4c8">Virtuoso</a>.</li>
<li>It has all the social media components that you could need, including: <a href="http://dbpedia.org/resource/Blog" id="link-id10120b58">blogs</a>, <a href="http://dbpedia.org/resource/Wiki" id="link-id14d9a608">wikis</a>, <a href="http://dbpedia.org/resource/Social_network_service" id="link-idf0b3a30">social networks</a>, <a href="http://dbpedia.org/resource/Aggregator" id="link-id188d7c78">feed readers</a>, <a href="http://dbpedia.org/resource/Customer_relationship_management" id="link-id134a2c48">CRM</a> and a <a href="http://dbpedia.org/resource/Calendar" id="link-idf66af80">calendar</a>.</li>
<li>It is expandable by installing pre-configured components (called VADs), or by re-configuring a <a href="http://dbpedia.org/resource/LAMP_%28software_bundle%29" id="link-id102e8008">LAMP</a> application to use <a href="http://dbpedia.org/resource/Virtuoso_Universal_Server" id="link-id13fe2b68">Virtuoso</a>. Some examples of current VADs include: <a href="http://dbpedia.org/resource/MediaWiki" id="link-id1011d9f0">MediaWiki</a>, <a href="http://dbpedia.org/resource/WordPress" id="link-id13624060">Wordpress</a> and <a href="http://dbpedia.org/resource/Drupal" id="link-id100c4510">Drupal</a>.</li>
<li>It works with external webservices such as: <a href="http://dbpedia.org/resource/Facebook" id="link-id131fe6d0">Facebook</a>, <a href="http://dbpedia.org/resource/Del.icio.us" id="link-idfdd1580">del.icio.us</a> and <a href="http://dbpedia.org/resource/Flickr" id="link-id1496aff0">Flickr.</a>
  </li>
<li>Everything within OpenLink Data Spaces is <a href="http://dbpedia.org/resource/Linked_Data" id="link-id17114c00">Linked Data</a>, which provides more meaningful information than just plain structural information. This meaningful information could be used for complex inferencing systems, as ODS can be seen as a <a href="http://dbpedia.org/resource/Expert_system" id="link-id15ea4108">Knowledge Base</a>.</li>
<li>ODS builds bridges between the existing static-document based web (aka â<a href="http://dbpedia.org/resource/Web_1.0" id="link-idf08b338">Web 1.0</a>â), the more dynamic,Â  services-oriented, social and/or user-orientated webs (aka â<a href="http://dbpedia.org/resource/Web_2.0" id="link-idfde26e0">Web 2.0</a>â) and the web which we are just going into, which is more data-orientated (aka â<a href="http://dbpedia.org/resource/Web_3.0" id="link-idf9b7328">Web 3.0</a>â or âLinked Data Webâ).</li>
<li>It is fully supportive of <a href="http://dbpedia.org/resource/Cloud_computing" id="link-id189480d0">Cloud Computing</a>, and can be installed on <a href="http://dbpedia.org/resource/Amazon_Elastic_Compute_Cloud" id="link-id10026778">Amazon EC2</a>.</li>
<li>Its released free under the GNU <a href="http://dbpedia.org/resource/GNU_General_Public_License" id="link-id16002fb0">General Public License (GPL)</a>. [note]However, it is technically dual licensed as it lays on top of the <a href="http://en.wikipedia.org/wiki/Virtuoso_Universal_Server" id="link-id132d4238">Virtuoso Universal Server</a> which has both Commercial and GPL licensing[/note]</li>
</ol>
</blockquote>
<p>The features above collectively provide users with a Linked Data Junction Box that may reside with corporate intranets or &quot;out in the clouds&quot; (Internet). You can consume, share, and publish data in a myriad of formats using a plethora of protocols, without any programming. ODS is simply about exposing the data from your Web 1.0, 2.0, 3.0 application interactions in structured from, with Linking, Sharing, and ultimately Meshing (not Mashing) in mind.</p>

<p>
<strong>Note:</strong> Although ODS is equipped with a broad array of Web 2.0 style Applications, you do not need to use native ODS apps in order to exploit it&#39;s power. It binds to anything that supports the relevant protocols and data formats.</p>

]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2008-01-17#1300">
  <rss:title>Semantic Data Web Epiphanies: One Node at a Time</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2008-01-17T22:59:00Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">In 2006, I stumbled across Jason Kolb (online) via a 4-part series of posts titled: Reinventing the Internet. At the time, I realized that Jason was postulating about what is popularly known today as &quot;Data Portability&quot;, so I made contact with him (blogosphere style) via a post of my own titled: Data Spaces, Internet Reinvention, and the Semantic Web. Naturally, I tried to unveil to Jason the connection between his vision and the essence of the Semantic Web. Of course, he was skeptical :-) Jason recently moved to Massachusetts which lead to me pinging him about our earlier blogosphere encounter and the emergence of a Data Portability Community. I also informed him about the fact that TimBL, myself, and a number of other Semantic Web technology enthusiasts, frequently meet on the 2nd Tuesday of each month at the MIT hosted Cambridge Semantic Web Gatherings, to discuss, demonstrate, debate all aspects of the Semantic Web. Luckily (for both of us), Jason attended the last event, and we got to meet each other in person. Following our face to face meeting in Cambridge, a number of follow-on conversations ensued covering, Linked Data and practical applications of the Semantic Web vision. Jason writes about our exchanges a recent post titled: The Semantic Web. His passion for Data Portability enabled me to use OpenID and FOAF integration to connect the Semantic Web and Data Portability via the Linked Data concept. During our conversations, Jason also eluded to the fact that he had already encountered OpenLink Software while working with our ODBC Drivers (part of or UDA product family) for IBM Informix (Single-Tier or Multi-Tier Editions) a few years ago (interesting random connection). As I&#39;ve stated in the past, I&#39;ve always felt that the Semantic Web vision will materialize by way of a global epiphany. The count down to this inevitable event started at the birth of the blogosphere, ironically. And accelerated more recently, through the emergence of Web 2.0 and Social Networking, even more ironically :-) The blogosphere started the process of Data Space coalescence via RSS/Atom based semi-strucutured data enclaves, Web 2.0 RDFpropagated Web Service usage en route to creating service provider controlled, data and information silosRDF, Social NetworkingRDF brought attention to the fact that User Generated Data wasn&#39;t actually owned or controlled by the Data Creators etc. The emergence of &quot;Data Portability&quot; has created a palatable moniker for a clearly defined, and slightly easier to understand, problem: the meshing of Data and Identity in cyberspace i.e. individual points of presence in cyberspace, in the form of &quot;Personal Data Spaces in the Clouds&quot; (think: doing really powerful stuff with .name domains). In a sense, this is the critical inflection point between the document centric &quot;Web of Linked Documents&quot; and the data centric &quot;Web or Linked Data&quot;. There is absolutely no other way solve this problem in a manner that alleviates the imminent challenges presented by information overload -- resulting from the exponential growth of user generated data across the Internet and enterprise Intranets.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>In 2006, I stumbled across <a href="http://www.jasonkolb.com" id="link-id17165b98">Jason Kolb</a> (online) via a 4-part series of posts titled: <a href="http://www.jasonkolb.com/weblog/2006/08/reinventing_the_1.html" id="link-id14204cf8">Reinventing the Internet</a>. At the time, I realized that Jason was postulating about what is popularly known today as &quot;<a href="http://en.wikipedia.org/wiki/Data_portability" id="link-id1412b280">Data Portability</a>&quot;, so I made contact with him (blogosphere style) via a post of my own titled: <a href="http://www.openlinksw.com/dataspace/kidehen@openlinksw.com/weblog/kidehen@openlinksw.com%27s%20BLOG%20%5B127%5D/1033" id="link-id13b1cb20">Data Spaces, Internet Reinvention, and the Semantic Web</a>. Naturally, I tried to unveil to Jason the connection between his vision and the essence of the <a href="http://dbpedia.org/resource/Semantic_Web" id="link-id143117f0">Semantic Web</a>. Of course, he was skeptical :-)</p>

<p>Jason recently moved to <a href="http://dbpedia.org/resource/Massachusetts" id="link-id13c4a470">Massachusetts</a> which lead to me pinging him about our earlier blogosphere encounter and the emergence of a <a href="http://dataportability.org/" id="link-id17395c60">Data Portability Community</a>. I also informed him about the fact that <a href="http://dbpedia.org/resource/Tim_Berners-Lee" id="link-id105507f0">TimBL</a>, myself, and a number of other Semantic Web technology enthusiasts, frequently meet on the 2nd Tuesday of each month at the <a href="http://dbpedia.org/resource/Massachusetts_Institute_of_Technology" id="link-id1719f798">MIT</a> hosted <a href="http://esw.w3.org/topic/CambridgeSemanticWebGatherings" id="link-id1734d460">Cambridge Semantic Web Gatherings</a>, to discuss, demonstrate, debate all aspects of the Semantic Web. Luckily (for both of us), Jason attended the last event, and we got to meet each other in person.</p>

<p>Following our face to face meeting in Cambridge,  a number of follow-on conversations ensued covering,  Linked Data and practical applications of the Semantic Web vision. Jason writes about our exchanges a recent post titled: <a href="http://www.jasonkolb.com/weblog/2008/01/the-semantic-we.html" id="link-id13be6280">The Semantic Web</a>. His passion for Data Portability enabled me to use <a href="http://esw.w3.org/topic/FoafOpenid" id="link-id141516a8">OpenID and FOAF integration</a> to connect the Semantic Web and Data Portability via the Linked Data concept.</p>

<p>During our conversations, Jason also eluded to the fact that he had already encountered <a href="http://en.wikipedia.org/wiki/OpenLink_Software" id="link-id17038218">OpenLink Software</a> while working with our <a href="http://data.openlinksw.com/oplweb/product_category/odbc#this" id="link-id14325f08">ODBC Drivers</a> (part of or <a href="http://data.openlinksw.com/oplweb/product_family/uda#this" id="link-id11ab1008">UDA product family</a>) for <a href="http://dbpedia.org/resource/Informix" id="link-id125858d0">IBM Informix</a> (<a href="http://data.openlinksw.com/oplweb/product/odbc-informix-st#this" id="link-id13b85e30">Single-Tier</a> or <a href="http://data.openlinksw.com/oplweb/product/odbc-informix-mt#this" id="link-id13edceb0">Multi-Tier</a> Editions) a few years ago (interesting random connection).</p>

<p>As I&#39;ve stated in the past, I&#39;ve always felt that the Semantic Web vision will materialize by way of a global epiphany. The count down to this inevitable event started at the birth of the blogosphere, ironically. And accelerated more recently, through the emergence of <a href="http://dbpedia.org/resource/Web_2.0" id="link-id171d4ec8">Web 2.0</a> and <a href="http://dbpedia.org/page/Social_network" id="link-id140da830">Social Networking</a>, even more ironically :-)</p>

<p>The blogosphere started the process of Data Space coalescence via RSS/Atom based semi-strucutured data enclaves, Web 2.0 RDFpropagated Web Service usage en route to creating service provider controlled, data and information silosRDF, Social NetworkingRDF brought attention to the fact that User Generated Data wasn&#39;t actually owned or controlled by the Data Creators etc.</p>

<p>The emergence of &quot;Data Portability&quot; has created a palatable moniker for a clearly defined, and slightly easier to understand, problem: the meshing of Data and Identity in cyberspace i.e. individual points of presence in cyberspace, in the form of &quot;Personal Data Spaces in the Clouds&quot; (think: doing really powerful stuff with .name domains). In a sense, this is the critical inflection point between the document centric &quot;Web of Linked Documents&quot; and the data centric &quot;Web or Linked Data&quot;.  There is absolutely no other way solve this problem in a manner that alleviates the imminent challenges presented by information overload -- resulting from the exponential growth of user generated data across the Internet and enterprise Intranets.</p>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2007-09-22#1261">
  <rss:title>Fourth Platform: Data Spaces in The Cloud (Update)</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2007-09-22T23:43:00Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">I&#39;ve written extensively on the subject of Data Spaces in relation to the Data Web for while. I&#39;ve also written sparingly about OpenLink Data Spaces (a Data Web Platform that build using Virtuoso). On the other hand, I haven&#39;t shed much light on installation and deployment of OpenLink Data Spaces. Jon Udell recently penned a post titled: The Fourth Platform. The post arrives at a spookily coincidental time (this happens quite often between Jon and I as demonstrated last year during our podcast; the &quot;Fourth&quot; in his Innovators Podcast series). The platform that Jon describes is &quot;Cloud Based&quot; and comprised of Storage and Computation. I would like to add Data Access and Management (native and virtual) under the fourth platform banner with the end product called: &quot;Cloud based Data Spaces&quot;. As I write, we are releasing a Virtuoso AMI (Amazon Image) labeled: virtuoso-dataspace-server. This edition of Virtuoso includes the OpenLink Data Spaces Layer and all of the OAT applications we&#39;ve been developing for a while. What Benefits Does this offer? Personal Data Spaces in the Cloud - a place where you can control and consolidate data across your Blogs, Wikis, RSS/Atom Feed Subscriptions, Shared Bookmarks, Shared Calendars, Discussion Threads, Photo Galleries etc All the data in your Data Space is SPARQL or GData accessible. All of the data in your Personal Data Space is Linked Data from the get go. Each Item of data is URI addressable SIOC support - your Blogs, Wikis, Bookmarks etc.. are based on the SIOC ontology for Semantically Interlinking Online Communities (think: Open social-graph++) FOAF support - your FOAF Profile page provides a URI that is an in-road to all Data in your Data Space. OpenID support - your Personal Data Space ID is usable wherever OpenID is supported. OpenID and FOAF are integrated as per latest FOAF specs Two Integration with Facebook - You can access your Data Space from Facebook or access Facebook from your Data Space Unified Storage - The WebDAV based filesystem provides Cloud Storage that&#39;s integrated with Amazon S3; It also exposes all of your Data Space data via a traditional filesystem UI (think virtual Spotlight); You can also mount this drive to your local filesystem via your native operating system&#39;s WebDAV support SyncML - you can sync calendar and contact details with your Data Space in the cloud from your Mobile phone. A practical Semantic Data Web solution - based on Web Infrastructure and doesn&#39;t require you to do anything beyond exposing URIs for data in your Data Spaces. EC2-AMI Details: AMI ID: ami-e2ca2f8b Manifest file: virtuoso-images/virtuoso-dataspace-server.manifest.xml Installation Guide: Get an Amazon Web Services (AWS) account Signup for S3 and EC2 services Install the EC2 plugin for Firefox Start the EC2 plugin Locate the row containingÂ ami-7c31d515Â Â ManifestÂ virtuoso-test/virtuoso-cloud-beta-9-i386.manifest.xmlÂ (sort using the AMI ID or Manifest Columns or search on pattern: virtuoso, due to name flux) Start the Virtuoso Data Space Server AMI Wait 4-5 minutes (*take a few minutes to create the pre-configured Linux Image*) Connect to http://http://your-ec2-instance-cname:8890/ Log in with user/password dba/dba Go to the Admin UI (Virtuoso Conductor) and change the PWDs for the &#39;dba&#39; and &#39;dav&#39; accounts (*Important!*) Give the &quot;SPARQL&quot; user &quot;SPARQL_UPDATE&quot; privileges (required if you want to exploit the in-built Sponger Middleware) Click on the ODS (OpenLink Data Spaces) link to start an Personal Editon of OpenLink Data Spaces (or go to: http://your-ec2-instance-cname/dataspace/ods/index.html) Log-in using the username and password credentials for the &#39;dav&#39; account (or register a new user note: OpenID is an option here also) Create an Data Space Application Instance by clicking on a Data Space App. Tab Import data from your existing Web 2.0 style applications into OpenLink Data Spaces e.g. subscribe to a few RSS/Atom feeds via the &quot;Feeds Manager&quot; application or import some Bookmarks using the &quot;Bookmarks&quot; application Then look at the imported data in Linked Data form via your ODS generated URIs based on the patterns: http://your-ec2-instance-cname/dataspace/person/your-ods-id#this (URI for You the Person), http://your-ec2-instance-cname/dataspace/person/your-ods-id (FOAF File URI), http://your-ec2-instance-cname/dataspace/your-ods-id (SIOC File URI) (OAT) from your Data Space instanceInstall the OAT VAD package via the Admin UI and then apply the URI patterns below within your browser: http://:8890/oatdemo - Entire OAT Demo Collection http://:8890/rdfbrowser - RDF Browser http://:8890/isparql - SPARQL Query Builder (iSPARQL) http://:8890/qbe - SQL Query Builder (iSQL) http://:8890/formdesigner - Forms Builder (for building Meshups based on RDF, SQL, or Web Servives Data Souces) http://:8890/dbdesigner - SQL DB Schema Designer (note a Visual SQL-RDF Mapper is also on it&#39;s way http://:8890/DAV/JS/ - To view the OAT Tree (there are some experimental demos that are missing from the main demo app etc..) There&#39;s more to come!</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<p>I&#39;ve written extensively on the subject of <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&amp;q=data%20spaces&amp;type=text&amp;output=html" id="link-id134c2280">Data Spaces</a> in relation to the <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&amp;q=data%20web%0D%0A&amp;type=text&amp;output=html" id="link-id105aef90">Data Web</a> for while. I&#39;ve also written sparingly about <a href="http://virtuoso.openlinksw.com/wiki/main/Main/OdsIndex" id="link-id105bd100">OpenLink Data Spaces</a> (a Data Web Platform that build using Virtuoso). On the other hand, I haven&#39;t shed much light on installation and deployment of OpenLink Data Spaces.</p> <p> <a href="http://blog.jonudell.net" id="link-id14347f20">Jon Udell</a> recently penned a post titled: <a href="http://blog.jonudell.net/2007/09/21/the-fourth-platform/" id="link-id1439ed48">The Fourth Platform</a>. The post arrives at a spookily coincidental time (this happens quite often between Jon and I as demonstrated last year during our <a href="http://weblog.infoworld.com/udell/gems/ju_idehen.mp3" id="link-id107d17a8">podcast</a>; the &quot;Fourth&quot; in his Innovators Podcast series).</p> <p>The platform that Jon describes is &quot;Cloud Based&quot; and comprised of Storage and Computation. I would like to add Data Access and Management (native and virtual) under the fourth platform banner with the end product called: &quot;Cloud based Data Spaces&quot;. </p> <p>As I write, we are releasing a Virtuoso AMI (Amazon Image) labeled: virtuoso-dataspace-server. This edition of<a href="http://virtuoso.openlinksw.com" id="link-id13543210"> Virtuoso</a> includes the OpenLink Data Spaces Layer and all of the OAT applications we&#39;ve been developing for a while.</p> <h2>What Benefits Does this offer?</h2> <ol> <li>Personal Data Spaces in the Cloud - a place where you can control and consolidate data across your Blogs, Wikis, RSS/Atom Feed Subscriptions, Shared Bookmarks, Shared Calendars, Discussion Threads, Photo Galleries etc</li> <li>All the data in your Data <a href="http://en.wikipedia.org/wiki/Data_Spaces">Space</a> is <a href="http://dbpedia.org/resource/SPARQL" id="link-id1149a4f8">SPARQL</a> or <a href="http://dbpedia.org/resource/GData" id="link-id107a9f28">GData</a> accessible.</li> <li>All of the data in your Personal Data Space is <a href="http://dbpedia.org/resource/Linked_Data">Linked Data</a> from the get go. Each Item of data is <a href="http://dbpedia.org/resource/Uniform_Resource_Identifier">URI</a> addressable</li> <li> <a href="http://dbpedia.org/resource/SIOC" id="link-id104f4160">SIOC</a> support - your Blogs, Wikis, Bookmarks etc.. are based on the SIOC ontology for Semantically Interlinking Online Communities (think: Open social-graph++) </li> <li> <a href="http://dbpedia.org/resource/Friend_of_a_friend" id="link-id105beb78">FOAF</a> support - your FOAF Profile page provides a URI that is an in-road to all Data in your Data Space.</li> <li> <a href="http://dbpedia.org/resource/OpenID" id="link-id1144e138">OpenID</a> support - your Personal Data Space ID is usable wherever OpenID is supported. OpenID and FOAF are integrated as per latest FOAF specs</li> <li>Two Integration with Facebook - You can access your Data Space from Facebook or access Facebook from your Data Space</li> <li>Unified Storage - The WebDAV based filesystem provides Cloud Storage that&#39;s integrated with Amazon S3; It also exposes all of your Data Space data via a traditional filesystem UI (think virtual Spotlight); You can also mount this drive to your local filesystem via your native operating system&#39;s WebDAV support</li> <li> <a href="http://dbpedia.org/resource/SyncML" id="link-id11128f48">SyncML</a> - you can sync calendar and contact details with your Data Space in the cloud from your Mobile phone.</li> <li>A practical Semantic Data Web solution - based on Web Infrastructure and doesn&#39;t require you to do anything beyond exposing URIs for data in your Data Spaces.</li> </ol> <h2> <a href="http://dbpedia.org/resource/Amazon_Elastic_Compute_Cloud" id="link-id115d1920">EC2</a>-AMI Details:</h2> <ul>AMI ID: ami-e2ca2f8b</ul> <ul>Manifest file: virtuoso-images/virtuoso-dataspace-server.manifest.xml</ul> <h2>Installation Guide:</h2> <ol> <li>Get an Amazon Web Services (AWS) account</li> <li>Signup for S3 and EC2 services</li> <li>Install the EC2 plugin for Firefox</li> <li>Start the EC2 plugin</li> <li>Locate the row containingÂ <b>ami-7c31d515Â Â ManifestÂ virtuoso-test/virtuoso-cloud-beta-9-i386.manifest.xmlÂ </b>(sort using the AMI ID or Manifest Columns or search on pattern: virtuoso, due to name flux)</li> <li>Start the Virtuoso Data Space Server AMI</li> <li>Wait 4-5 minutes (*take a few minutes to create the pre-configured Linux Image*)</li> <li>Connect to http://<public_dns_name_of_your_instance>http://your-ec2-instance-cname:8890/ Log in with user/password dba/dba</public_dns_name_of_your_instance> </li> <li>Go to the Admin UI (Virtuoso Conductor) and change the PWDs for the &#39;dba&#39; and &#39;dav&#39; accounts (*Important!*)</li> <li>Give the &quot;SPARQL&quot; user &quot;SPARQL_UPDATE&quot; privileges (required if you want to exploit the in-built Sponger Middleware)</li> <li>Click on the <a href="http://dbpedia.org/resource/OpenLink_Data_Spaces">ODS</a> (OpenLink Data Spaces) link to start an Personal Editon of OpenLink Data Spaces (or go to: http://your-ec2-instance-cname/dataspace/ods/index.html)</li> <li>Log-in using the username and password credentials for the &#39;dav&#39; account (or register a new user note: OpenID is an option here also) Create an Data Space Application Instance by clicking on a Data Space App. Tab</li> <li>Import data from your existing Web 2.0 style applications into OpenLink Data Spaces e.g. subscribe to a few RSS/Atom feeds via the &quot;Feeds Manager&quot; application or import some Bookmarks using the &quot;Bookmarks&quot; application</li> <li>Then look at the imported data in Linked Data form via your ODS generated URIs based on the patterns: http://your-ec2-instance-cname/dataspace/person/your-ods-id#this (URI for You the Person), http://your-ec2-instance-cname/dataspace/person/your-ods-id (FOAF File URI), http://your-ec2-instance-cname/dataspace/your-ods-id (SIOC File URI)<br /> </li> </ol> <h2> (OAT) from your Data Space instance</h2>Install the OAT VAD package via the Admin UI and then apply the URI patterns below within your browser:<br /> <ol> <li>http://<public_dns_name_of_your_instance>:8890/oatdemo - Entire OAT Demo Collection</public_dns_name_of_your_instance> </li> <li>http://<public_dns_name_of_your_instance>:8890/rdfbrowser - RDF Browser</public_dns_name_of_your_instance> </li> <li>http://<public_dns_name_of_your_instance>:8890/isparql - SPARQL Query Builder (iSPARQL)</public_dns_name_of_your_instance> </li> <li>http://<public_dns_name_of_your_instance>:8890/qbe - SQL Query Builder (iSQL)</public_dns_name_of_your_instance> </li> <li>http://<public_dns_name_of_your_instance>:8890/formdesigner - Forms Builder (for building Meshups based on RDF, SQL, or Web Servives Data Souces)</public_dns_name_of_your_instance> </li> <li>http://<public_dns_name_of_your_instance>:8890/dbdesigner - SQL DB Schema Designer (note a Visual SQL-RDF Mapper is also on it&#39;s way</public_dns_name_of_your_instance> </li> <li>http://<public_dns_name_of_your_instance>:8890/DAV/JS/ - To view the OAT Tree (there are some experimental demos that are missing from the main demo app etc..) </public_dns_name_of_your_instance> </li> </ol> <p>There&#39;s more to come!</p>

]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2007-03-01#1148">
  <rss:title>Personal URIs &amp; Data Spaces</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2007-03-01T19:42:41Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Linking personal posted content across communities: &quot; With the help of Kingsley, Uldis and I have been looking at how SIOC can be used to link the content that a single person posts to a number of community sites. The picture below shows an example of stuff that Iâve created on Flickr, YouTube, etc. through my various user identities on those sites (these match some SIOC types that we want to add to a separate module). We can also say that each Web 2.0 content item is a user-contributed post, with some attached or embedded content (e.g. a file or maybe just some metadata). This is part of a new discussion on the sioc-dev mailing list, and weâd value your contributions. Edit: The inner layer is a person (semantically described in FOAF), the next layer is their user accounts (described in FOAF, SIOC) and the outer layer is the posted content - text, files, associated metadata - on community sites (again described using SIOC). No Tags&quot; (Via John Breslin - Cloudlands.) The point that John is making about the Data Web and Interlinked Data Spaces exposed via URIs (e.g Personal URIs), crystallizes a number of very important issues about the Data Web that may remain unclear. I am hoping that by digesting the post excerpt above, in conjunction with the items below, aids the pursuit of clarity and comprehension about the all important Data Web (Semantic Web - Layer 1): Your OpenID can be Your Personal URI (as noted by Henry Story&#39;s post about: The Many Uses of OpenID). That that&#39;s what I have courtesy of OpenLink Data Spaces (ODS) The above only works unobtrusively (i.e. OpenID and Personal sharing a URI) if Content Negotiation is exploited on the Client and Server sides. TimBL&#39;s call out to Share Your Data and Link to Other Data via URIs via post titled: Give Yourself a URI. W3C&#39;s Best Practice Recipes for Publishing RDF Vocabularies W3C&#39;s Architecture of the World Wide Web - Vol 1 which covers URI Dereferencing (HTTP GET-ing the data that a URI points to) Richard Cyganiak&#39;s post titled: Debugging Semantic Web Sites with Curl. Examples of some of these principles in practice: Chris Bizer, Tobias Gaub, and Richard&#39;s Javascript based Semantic Web Client Library DISCO RDF Browser OpenLink Ajax Toolkit&#39;s (OAT) RDF Browser OpenLink Interactive SPARQL Query by Example (iSPARQL QBE) Dynamic Data Web Pages from my prior posts [1][2][3] dbpedia (Wikipedia as a Data Web oriented Data Source) And of course this blog post&#39;s permalink is a bona fide dereferencable URI. And of course there is more to come such as Grandma&#39;s Semantic Web Browser which is coming from Zitgist LLC (pronounced: Zeitgeist) a joint venture of OpenLink Software and Frederick Giasson.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<blockquote>
<p>
  <a href="http://www.johnbreslin.com/blog/2007/03/01/linking-personal-posted-content-across-communities/#comments">Linking personal posted content across communities</a>: &quot;</p>
<p>With the help of Kingsley, Uldis and I have been looking at how <a href="http://sioc-project.org/">SIOC</a> can be used to link the content that a single person posts to a number of community sites.  The picture below shows an example of stuff that Iâve created on Flickr, YouTube, etc. through my various user identities on those sites (these match some <a href="http://wiki.sioc-project.org/index.php/TypesModule">SIOC types</a> that we want to add to a separate module).  We can also say that each Web 2.0 content item is a user-contributed post, with some attached or embedded content (e.g. a file or maybe just some metadata).  This is part of a new discussion on the <a href="http://groups.google.com/group/sioc-dev">sioc-dev</a> mailing list, and weâd value your contributions.</p>
<p>
  <img id="image1178" src="http://www.johnbreslin.com/blog/wp-content/uploads/2007/03/20070228a.png" alt="20070228a.png" />
</p>
<p>Edit: The inner layer is a person (semantically described in FOAF), the next layer is their user accounts (described in FOAF, SIOC) and the outer layer is the posted content - text, files, associated metadata - on community sites (again described using SIOC).
</p>
No Tags&quot;

<p>(Via <a href="http://www.johnbreslin.com/blog">John Breslin - Cloudlands</a>.)</p>
</blockquote>
<p>The point that John is making about the Data Web and Interlinked <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q='data%20spaces'&type=text&output=html">Data Spaces</a> exposed via <a href="http://en.wikipedia.org/wiki/Uniform_Resource_Identifier">URI</a>s (e.g Personal URIs), crystallizes a number of very important issues about the Data Web that may remain unclear. I am hoping that by digesting the post excerpt above, in conjunction with the items below, aids the pursuit of clarity and comprehension about the all important Data Web (Semantic Web - Layer 1):</p>
<ol>
<li>
  <a href="http://kidehen.idehen.net/dataspace/kidehen">Your OpenID can be Your Personal URI</a> (as noted by <a href="http://blogs.sun.com/bblfish/">Henry Story</a>&#39;s post about: <a href="http://blogs.sun.com/bblfish/entry/openid_for_blogs_sun_com">The Many Uses of OpenID</a>). That that&#39;s what I have courtesy of OpenLink Data Spaces (ODS)</li>
<li>The above only works unobtrusively (i.e. OpenID and Personal sharing a URI) if Content Negotiation is exploited on the Client and Server sides.</li>
<li>
  <a href="http://www.w3.org/People/Berners-Lee/card.rdf">TimBL</a>&#39;s call out to <a href="http://www.w3.org/DesignIssues/LinkedData.html">Share Your Data and Link to Other Data</a> via URIs via post titled: <a href="http://dig.csail.mit.edu/breadcrumbs/node/71">Give Yourself a URI</a>.</li>
<li>
  <a href="http://www.w3.org/TR/swbp-vocab-pub/">W3C&#39;s Best Practice Recipes for Publishing RDF Vocabularies</a>
</li>
<li>
  <a href="http://www.w3.org/TR/2004/REC-webarch-20041215/#dereference-uri">W3C&#39;s Architecture of the World Wide Web - Vol 1</a> which covers URI Dereferencing (HTTP GET-ing the data that a URI points to)</li>
<li>
  <a href="http://www4.wiwiss.fu-berlin.de/is-group/page/persons/Person6">Richard Cyganiak</a>&#39;s post titled: <a href="http://dowhatimean.net/2007/02/debugging-semantic-web-sites-with-curl">Debugging Semantic Web Sites with Curl</a>.</li>
</ol>
<p>Examples of some of these principles in practice:</p>
<ol>
<li>Chris Bizer, Tobias Gaub, and Richard&#39;s Javascript based<a href="http://sites.wiwiss.fu-berlin.de/suhl/bizer/ng4j/semwebclient/"> Semantic Web Client Library</a>
</li>
<li>
  <a href="http://sites.wiwiss.fu-berlin.de/suhl/bizer/ng4j/disco/">DISCO RDF Browser</a>
</li>
<li>
  <a href="http://oat.openlinksw.com">OpenLink Ajax Toolkit</a>&#39;s (OAT) <a href="http://demo.openlinksw.com/DAV/JS/tests/rdfbrowser/index.html">RDF Browser</a>
</li>
<li>OpenLink <a href="http://demo.openlinksw.com/isparql">Interactive SPARQL Query by Example</a> (iSPARQL QBE)</li>
<li>Dynamic Data Web Pages from my prior posts [<a href="http://www.openlinksw.com/blog/~kidehen/?id=1144">1</a>][<a href="http://www.openlinksw.com/blog/~kidehen/index.vspx?page=&id=1145">2</a>][<a href="http://www.openlinksw.com/blog/~kidehen/index.vspx?page=&id=1146">3</a>]</li>
<li>
  <a href="http://dbpedia.org/docs/">dbpedia</a> (Wikipedia as a Data Web oriented Data Source)</li>
<li>And of course this blog post&#39;s permalink is a bona fide dereferencable URI.</li>
</ol>
<p>And of course there is more to come such as Grandma&#39;s Semantic Web Browser which is coming from <a href="http://fgiasson.com/blog/index.php/2007/02/18/zitgist_a_semantic_web_search_engine">Zitgist LLC</a> (pronounced: Zeitgeist) a joint venture of OpenLink Software and <a href="http://fgiasson.com/blog/">Frederick Giasson</a>.</p>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2006-09-20#1048">
  <rss:title>OpenID meets Data Spaces etc..</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2006-09-20T14:47:17Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">I have written extensively about &quot;Presence&quot;, &quot;Data Spaces&quot;, and &quot;Open Access to Data&quot;. What I haven&#39;t emphasized is how &quot;Identity&quot; brings this together, primarily becuase I didn&#39;t have something to demonstrate, or point to, coherently etc.. Anyway, we now have OpenID support in OpenLink Data Spaces (ODS) which coincides nicely with the growing support of OpenID across the web. The beauty of OpenID support in ODS is that I now have a URL that meshes with my identity (at least in line with what I have chosed to share with the public via the Web). For instance, http://www.openlinksw.com/dataspace/kidehen@openlinksw.com is my OpenID as well as my personal URI (you look closer at this link and you have a map of my Data Space). To really understand what I am getting at here you should open up My OpenID URL using one of the following: Semantic Radar PiggyBank SIOC Enabled Wiki To be continued....</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<p>I have written extensively about &quot;<a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=presence%0D%0A&type=text&output=html">Presence</a>&quot;, &quot;<a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=%27data%20spaces%27&type=text&output=html">Data Spaces</a>&quot;, and &quot;<a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=open%20data%20access&type=text&output=html">Open Access to Data</a>&quot;. What I haven&#39;t emphasized is how &quot;Identity&quot; brings this together, primarily becuase I didn&#39;t have something to demonstrate, or point to, coherently etc..</p>  <p>Anyway, we now have <a href="http://openid.net/">OpenID</a> support in OpenLink Data Spaces (ODS) which coincides nicely with the <a href="http://www.openidenabled.com/software">growing support of OpenID</a> across the web. </p>  <p>The beauty of OpenID support in ODS is that I now have a URL that meshes with my identity (at least in line with what I have chosed to share with the public via the Web). For instance, http://www.openlinksw.com/dataspace/kidehen@openlinksw.com is my OpenID as well as my personal URI (you look closer at this link and you have a map of my Data Space).</p>  <p>To really understand what I am getting at here you should open up <a href="http://www.openlinksw.com/dataspace/kidehen@openlinkswl.com">My OpenID URL</a> using one of the following:</p> <ol> <li>   <a href="http://sioc-project.org/firefox">Semantic Radar</a> </li>  <li>   <a href="http://simile.mit.edu/piggy-bank/">PiggyBank</a> </li>  <li>   <a href="http://esw.w3.org/topic/SIOC/Implementations">SIOC Enabled Wiki</a> </li>  </ol> <p> To be continued.... </p> <p>  </p>
]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?date=2005-10-26#882">
  <rss:title>Breaking the Web Wide Open! </rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2005-10-26T19:28:47Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Marc Canter&#39;s Breaking the Web Wide Open! article is something I found pretty late (by my normal discovery standards). This was partly due to the pre- and post- Web 2.0 event noise levels that have dumped the description of an important industry inflection into the &quot;Bozo Bin&quot; of many. Personally, I think we shouldn&#39;t confuse the Web 2.0 traditional-pitch-fest conference with an attempt to identify an important industry inflection). Anyway, Marc&#39;s article is a very refreshing read because it provides a really good insight into the general landscape of a rapidly evolving Web alongside genuine appreciation of our broader timeless pursuit of &quot;Openness&quot;. To really help this document provide additional value have scrapped the content of the original post and dumped it below so that we can appreciate the value of the links embedded within the article (note: thanks to Virtuoso I only had to paste the content into my blog, the extraction to my Linkblog and Blog Summary Pages are simply features of my Virtuoso based Blog Engine):Breaking the Web Wide Open! (complete story)Even the web giants like AOL, Google, MSN, and Yahoo need to observe these open standards, or they&#39;ll risk becoming the &quot;walled gardens&quot; of the new web and be coolio no more.Marc Canter [Broadband Mechanics, Inc.] | POSTED: 09.26.05 @12:00Editorial Note: Several months ago, AlwaysOn got a personal invitation from Yahoo founder Jerry Yang &quot;to see and give us feedback on our new social media product, y!360.&quot; We were happy to oblige and dutifully showed up, joining a conference room full of hard-core bloggers and new, new media types. The geeks gave Yahoo 360 an overwhelming thumbs down, with comments like, &quot;So the only services I can use within this new network are Yahoo services? What if I don&#39;t use Yahoo IM?&quot; In essence, the Yahoo team was booed for being &quot;closed web,&quot; and we heartily agreed. With Yahoo 360, Yahoo continues building its own &quot;walled garden&quot; to control its 135 million customersÂan accusation also hurled at AOL in the early 1990s, before AOL migrated its private network service onto the web. As theÂ  Economist recently noted, &quot;Yahoo, in short, has old media plans for the new-media era.&quot;The irony to our view here is, of course, that today&#39;s AO Network is also a &quot;closed web.&quot; In the end, Mr. Yang&#39;s thoughtful invitation and our ensuing disappointment in his new service led to the assignment of this article. It also confirmed our existing plan to completely revamp the AO Network around open standards. To tie it all together, we recruited the chief architect of our new site, the notorious Marc Canter, to pen this piece. We look forward to our reader feedback.Breaking the Web Wide Open!By Marc CanterFor decades, &quot;walled gardens&quot; of proprietary standards and content have been the strategy of dominant players in mainframe computer software, wireless telecommunications services, and the World Wide WebÂit was their successful lock-in strategy of keeping their customers theirs. But like it or not, those walls are tumbling down. Open web standards are being adopted so widely, with such value and impact, that the web giantsÂAmazon, AOL, eBay, Google, Microsoft, and YahooÂare facing the difficult decision of opening up to what they don&#39;t control.The online world is evolving into a new open web (sometimes called the Web 2.0), which is all about being personalized and customized for each user. Not only open source software, but open standardsÂ are becoming an essential component. Many of the web giants have been using open source software for years. Most of them use at least parts of the LAMP (Linux, Apache, MySQL, Perl/Python/PHP) stack, even if they aren&#39;t well-known for giving back to the open source community. For these incumbents that grew big on proprietary web services, the methods, practices, and applications of open source software development are difficult to fully adopt. And the next open source movementsÂwhich will be as much about open standards as about codeÂwill be a lot harder for the incumbents to exploit.While the incumbents use cheap open source software to run their back-ends systems, their business models largely depend on proprietary software and algorithms. But our view a new slew of open software, open protocols, and open standards will confront the incumbents with the classic Innovator&#39;s Dilemma.Â  Should they adopt these tools and standards, painfully cannibalizing their existing revenue for a new unproven concept, or should they stick with their currently lucrative model with the risk that eventually a bunch of upstarts eat their lunch? Credit should go to several of the web giants who have been making efforts to &quot;open up.&quot; Google, Yahoo, eBay, and Amazon all have Open APIs (Application Programming Interfaces) built into their data and systems. Any software developer can access and use them for whatever creative purposes they wish. This means that the API provider becomes an open platform for everyone to use and build on top of. This notion has expanded like wildfire throughout the blogosphere, so nowadays, Open APIs are pretty much required.Other incumbents also have open strategies. AOL has got the RSS religion, providing a feedreader and RSS search in order to escape the &quot;walled garden of content&quot; stigma. Apple now incorporates podcasts, the &quot;personal radio shows&quot; that are latest rage in audio narrowcasting, into iTunes. Even Microsoft is supporting open standards, for example by endorsing SIP (Session Initiation Protocol) for internet telephony and conferencing over Skype&#39;s proprietary format or one of its own devising.But new open standards and protocols are in use, under construction, or being proposed every day, pushing the envelope of where we are right now. Many of these standards are coming from startup companies and small groups of developers, not from the giants. Together with the Open APIs, those new standards will contribute to a new, open infrastructure. Tens of thousands of developers will use and improve this open infrastructure to create new kinds of web-based applications and services, to offer web users a highly personalized online experience.A Brief History of OpennessAt this point, I have to admit that I am not just a passive observer, full-time journalist or &quot;just some blogger&quot;Âbut an active evangelist and developer of these standards. It&#39;s the vision of &quot;open infrastructure&quot; that&#39;s driving my company and the reason why I&#39;m writing this article. This article will give you some of the background behind on these standards, and what the evolution of the next generation of open standards will look like.Starting back in the 1980s, establishing a software standard was a key strategy for any software company. My former company, MacroMind (which became Macromedia), achieved this goal early on with Director. As Director evolved into Flash, the world saw that other companies besides Microsoft, Adobe, and Apple could establish true cross-platform, independent media standards.Then Tim Berners-Lee and Marc Andreessen came along, and changed the rules of the software business and of entrepreneurialism. No matter how entrenched and &quot;standardized&quot; software was, the rug could still get pulled out from under it. Netscape did it to Microsoft, and then Microsoft did it backÂ  to Netscape. The web evolved, and lots of standards evolved with it. The leading open source standards (such as the LAMP stack) became widely used alternatives to proprietary closed-source offerings. Open standards are more than just technology. Open standards mean sharing, empowering, and community support. Someone floats a new idea (or meme) and the community runs with it â with each person making their own contributions to the standard â evolving it without a moment&#39;s hesitation about &quot;giving away their intellectual property.&quot;One good example of this was Dave Sifry, who built the Technorati blog-tracking technology inspired by the Blogging Ecosystem, a weekend project by young hacker Phil Pearson. Dave liked what he saw and he ran with itÂturning Technorati into what it is today.Dave Winer has contributed enormously to this area of open standards. He defined and personally created several open standards and protocolsÂsuch as RSS, OPML, and XML-RPC. Dave has also helped build the blogosphere through his enthusiasm and passion.By 2003, hundreds of programmers were working on creating and establishing new standards for almost everything. The best of these new standards have evolved into compelling web services platforms â such as del.icio.us, Webjay, or Flickr. Some have even spun off formal standards â like XSPF (a standard for playlists) or instant messaging standard XMPP (also known as Jabber).Today&#39;s Open APIs are complemented by standardized SchemasÂthe structure of the data itself and its associated meta-data. Take for example a podcasting feed. It consists of: a) the radio show itself, b) information on who is on the show, what the show is about and how long the show is (the meta-data) and also c) API calls to retrieve a show (a single feed item) and play it from a specified server. The combination of Open APIs, standardized schemas for handling meta-data, and an industry which agrees on these standards are breaking the web wide open right now. So what new open standards should the web incumbentsÂand youÂbe watching? Keep an eye on the following developments:IdentityAttentionOpen MediaMicrocontent PublishingOpen Social NetworksTagsPinging RoutingOpen CommunicationsDevice Management and Control1. IdentityRight now, you don&#39;t really control your own online identity. At the core of just about every online piece of software is a membership system. Some systems allow you to browse a site anonymouslyÂbut unless you register with the site you can&#39;t do things like search for an article, post a comment, buy something, or review it. The problem is that each and every site has its own membership system. So you constantly have to register with new systems, which cannot share dataÂeven you&#39;d want them to. By establishing a &quot;single sign-on&quot; standard, disparate sites can allow users to freely move from site to site, and let them control the movement of their personal profile data, as well as any other data they&#39;ve created. With Passport, Microsoft unsuccessfully attempted to force its proprietary standard on the industry. Instead, a world is evolving where most people assume that users want to control their own data, whether that data is their profile, their blog posts and photos, or some collection of their past interactions, purchases, and recommendations. As long as users can control their digital identity, any kind of service or interaction can be layered on top of it.Identity 2.0 is all about users controlling their own profile data and becoming their own agents. This way the users themselves, rather than other intermediaries, will profit from their ID info. Once developers start offering single sign-on to their users, and users have trusted places to store their dataÂwhich respect the limits and provide access controls over that data, users will be able to access personalized services which will understand and use their personal data.Identity 2.0 may seem like some geeky, visionary future standard that isn&#39;t defined yet, but by putting each user&#39;s digital identity at the core of all their online experiences, Identity 2.0 is becoming the cornerstone of the new open web. The Initiatives:Right now, Identity 2.0 is under construction through various efforts from Microsoft (the &quot;InfoCard&quot; component built into the Vista operating system and its &quot;Identity Metasystem&quot;), Sxip Identity, Identity Commons, Liberty Alliance, LID (NetMesh&#39;s Lightweight ID), and SixApart&#39;s OpenID.More Movers and Shakers:Identity Commons and Kaliya Hamlin, Sxip Identity and Dick Hardt, the Identity Gang and Doc Searls, Microsoft&#39;s Kim Cameron, Craig Burton, Phil Windley, and Brad Fitzpatrick, to name a few.2. AttentionHow many readers know what their online attention is worth? If you don&#39;t, Google and Yahoo doÂthey make their living off our attention. They know what we&#39;re searching for, happily turn it into a keyword, and sell that keyword to advertisers. They make money off our attention. We don&#39;t. Technorati and friends proposed an attention standard, Attention.xml, designed to &quot;help you keep track of what you&#39;ve read, what you&#39;re spending time on, and what you should be paying attention to.&quot; AttentionTrust is an effort by Steve Gillmor and Seth Goldstein to standardize on how captured end-user performance, browsing, and interest data are used. Blogger Peter Caputa gives a good summary of AttentionTrust: &quot;As we use the web, we reveal lots of information about ourselves by what we pay attention to. Imagine if all of that information could be stored in a nice neat little xml file. And when we travel around the web, we can optionally share it with websites or other people. We can make them pay for it, lease it ... we get to decide who has access to it, how long they have access to it, and what we want in return. And they have to tell us what they are going to do with our Attention data.&quot;So when you give your attention to sites that adhere to the AttentionTrust, your attention rights (you own your attention, you can move your attention, you can pay attention and be paid for it,Â  and you can see how your attention is used) are guaranteed. Attention data is crucial to the future of the open web, and Steve and Seth are making sure that no one entity or oligopoly controls it. Movers and Shakers:Steve Gillmor, Seth Goldstein, Dave Sifry and the other Attention.xml folks. 3. Open MediaProprietary media standardsÂFlash, Windows Media, and QuickTime, to name a few Âhelped liven up the web. But they are proprietary standards that try to keep us locked in, and they weren&#39;t created from scratch to handle today&#39;s online content. That&#39;s why, for many of us, an Open Media standard has been a holy grail. Yahoo&#39;s new Media RSS standard brings us one step closer to achieving open media, as do Ogg Vorbis audio codecs, XSPF playlists, or MusicBrainz. And several sites offer digital creators not only a place to store their content, but also to sell it. Media RSS (being developed by Yahoo with help from the community) extends RSS and combines it with &quot;RSS enclosures&quot; Âadds metadata to any media itemÂto create a comprehensive solution for media &quot;narrowcasters.&quot; To gain acceptance for Media RSS, Yahoo knows it has to work with the community. As an active member of this community, I can tell you that we&#39;ll create Media RSS equivalents for rdf (an alternative subscription format) and Atom (yet anotherÂ  subscription format), so no one will be able to complain that Yahoo is picking sides in format wars.When Yahoo announced the purchase of Flickr, Yahoo founder Jerry Yang insinuated that Yahoo is acquiring &quot;open DNA&quot; to turn Yahoo into an open standards player. Yahoo is showing what happens when you take a multi-billion dollar company and make openness one of its core valuesÂso Google, beware, even if Google does have more research fellows and Ph.D.s. The open media landscape is far and wide, reaching from game machine hacks and mobile phone downloads to PC-driven bookmarklets, players, and editors, and it includes many other standardization efforts. XSPF is an open standard for playlists, and MusicBrainz is an alternative to the proprietary (and originally effectively stolen) database that Gracenote licenses. Ourmedia.org is a community front-end to Brewster Kahle&#39;s Internet Archive. Brewster has promised free bandwidth and free storage forever to any content creators who choose to share their content via the Internet Archive. Ourmedia.org is providing an easy-to-use interface and community to get content in and out of the Internet Archive, giving ourmedia.org users the ability to share their media anywhere they wish, without being locked into a particular service or tool. Ourmedia plans to offer open APIs and an open media registry that interconnects other open media repositories into a DNS-like registry (just like the www domain system), so folks can browse and discover open content across many open media services. Systems like Brightcove and Odeo support the concept of an open registry, and hope to work with digital creators to sell their work to fulfill the financial aspect of the &quot;Long Tail.&quot;More Movers and Shakers:Creative Commons, the Open Media Network, Jay Dedman, Ryanne Hodson, Michael Verdi, Eli Chapman, Kenyatta Cheese, Doug Kaye, Brad Horowitz, Lucas Gonze, Robert Kaye, Christopher Allen, Brewster Kahle, JD Lasica, and indeed, Marc Canter, among others.4. Microcontent PublishingUnstructured content is cheap to create, but hard to search through. Structured content is expensive to create, but easy to search. Microformats resolve the dilemma with simple structures that are cheap to use and easy to search.The first kind of widely adopted microcontent is blogging. Every post is an encapsulated idea, addressable via a URL called a permalink. You can syndicate or subscribe to this microcontent using RSS or an RSS equivalent, and news or blog aggregators can then display these feeds in a convenient readable fashion. But a blog post is just a block of unstructured textânot a bad thing, but just a first step for microcontent. When it comes tostructuredÂ data, such as personal identity profiles, product reviews, or calendar-type event data, RSS was not designed to maintain the integrity of the structures. Right now, blogging doesn&#39;t have the underlying structure necessary for full-fledged microcontent publishing. But that will change. Think of local information services (such as movie listings, event guides, or restaurant reviews) that any college kid can access and use in her weekend programming project to create new services and tools.Today&#39;s blogging tools will evolve into microcontent publishing systems, and will help spread the notion of structured data across the blogosphere. New ways to store, represent and produce microcontent will create new standards, such as Structured Blogging and Microformats. Microformats differ from RSS feeds in that you can&#39;t subscribe to them. Instead, Microformats are embedded into webpages and discovered by search engines like Google or Technorati. Microformats are creating common definitions for &quot;What is a review or event? What are the specific fields in the data structure?&quot; They can also specify what we can do with all this information.OPML (Outline Processor Markup Language) is a hierarchical file format for storing microcontent and structured data. It was developed by Dave Winer of RSS and podcast fame.Events are one popular type of microcontent. OpenEvents is already working to create shared databases of standardized events, which would get used by a new generation of event portalsâsuch as Eventful/EVDB, Upcoming.org, and WhizSpark. The idea of OpenEvents is that event-oriented systems and services can work together to establish shared events databases (and associated APIs) that any developer could then use to create and offer their own new service or application. OpenReviews is still in the conceptual stage, but it would make it possible to provide open alternatives to closed systems like Epinions, and establish a shared database of local and global reviews. Its shared open servers would be filled with all sorts of reviews for anyone to access. Why is this important? Because I predict that in the future, 10 times more people will be writing reviews than maintaining their own blog. The list of possible microcontent standards goes on: OpenJobpostings, OpenRecipes, and even OpenLists. Microsoft recently revealed that it has been working on an important new kind of microcontent: Listsâso OpenLists will attempt to establish standards for the kindÂ of lists we all use, such as lists of Links, lists of To Do Items, lists of People, Wish Lists, etc.Movers and Shakers:Tantek Ãelik and Kevin Marks of Technorati, Danny Ayers, Eric Meyer, Matt Mullenweg, Rohit Khare, Adam Rifkin, Arnaud Leene, Seb Paquet, Alf Eaton, Phil Pearson, Joe Reger, Bob Wyman among others.5. Open Social NetworksI&#39;ll never forget the first time I met Jonathan Abrams, the founder of Friendster. He was arrogant and brash and he claimed he &quot;owned&quot;Â  all his users, and that he was going to monetize them and make a fortune off them. This attitude robbed Friendster of its momentum, letting MySpace, Facebook, and other social networks take Friendster&#39;s place.Jonathan&#39;s notion of social networks as a way to control users is typical of the Web 1.0 business model and its attitude towards users in general. Social networks have become one of the battlegrounds between old and new ways of thinking. Open standards for Social Networking will define those sides very clearly. Since meeting Jonathan, I have been working towards finding and establishing open standards for social networks. Instead of closed, centralized social networks with 10 million people in them, the goal is making it possible to have 10 million social networks that each have 10 people in them.FOAF (which stands for Friend Of A Friend, and describes people and relationships in a way that computers can parse) is a schema to represent not only your personal profile&#39;s meta-data, but your social network as well. Thousands of researchers use the FOAF schema in their &quot;Semantic Web&quot; projects to connect people in all sorts of new ways. XFN is a microformat standard for representing your social network, while vCard (long familiar to users of contact manager programs like Outlook) is a microformat that contains your profile information. Microformats are baked into any xHTML webpage, which means thatanyÂ blog, social network page, or any webpage in general can &quot;contain&quot; your social network in itÂand be used byanyÂ compatible tool, service or application. PeopleAggregator is an earlier project now being integrated into open content management framework Drupal. The PeopleAggregator APIs will make it possible to establish relationships, send messages, create or join groups, and post between different social networks. (Sneak preview: this technology will be available in the upcoming GoingOn Network.) All of these open social networking standards mean that inter-connected social networks will form a mesh that will parallel the blogosphere. This vibrant, distributed, decentralized world will be driven by open standards: personalized online experiences are what the new open web will be all aboutÂand what could be more personalized than people&#39;s networks?Movers and Shakers:Eric Sigler, Joel De Gan, Chris Schmidt, Julian Bond, Paul Martino, Mary Hodder, Drummond Reed, Dan Brickley, Randy Farmer, and Kaliya Hamlin, to name a few.6. TagsNowadays, no self-respecting tool or service can ship without tags. Tags are keywords or phrases attached to photos, blog posts, URLs, or even video clips. These user- and creator-generated tags are an open alternative to what used to be the domain of librarians and information scientists: categorizing information and content using taxonomies. Tags are instead creating &quot;folksonomies.&quot;The recently proposed OpenTags concept would be an open, community-owned version of the popular Technorati Tags service. It would aggregate the usage of tags across a wide range of services, sites, and content tools. In addition to Technorati&#39;s current tag features, OpenTags would let groups of people share their tags in &quot;TagClouds.&quot; Open tagging is likely to include some of the open identity features discussed above, to create a tag system that is resilient to spam, and yet trustable across sites all over the web.OpenTags owes a debt to earlier versions of shared tagging systems, which include Topic Exchange and something called the k-collectorÂa knowledge management tag aggregatorÂfrom Italian company eVectors. Movers &amp; Shakers:Phil Pearson, Matt Mower , Paolo Valdemarin, and Mary Hodder and Drummond Reed again, among others.7. PingingWebsites used to be mostly static. Search engines that crawled (or &quot;spidered&quot;) them every so often did a good enough job to show reasonably current versions of your cousin&#39;s homepage or even TimeÂ magazine&#39;s weekly headlines. But when blogging took off, it became hard for search engines to keep up. (Google has only just managed to offer blog-search functionality, despite buying Blogger back in early 2003.)To know what was new in the blogosphere, users couldn&#39;t depend on services that spidered webpages once in a while. The solution: a way for blogs themselves to automatically notify blog-tracking sites that they&#39;d been updated. Weblogs.com was the first blog &quot;ping service&quot;: it displayed the name of a blog whenever that blog was updated. Pinging sites helped the blogosphere grow, and more tools, services, and portals started using pinging in new and different ways. Dozens of pinging services and sitesÂmost of which can&#39;t talk to each otherÂsprang up. Matt Mullenweg (the creator of open source blogging software WordPress) decided that a one-stop service for pinging was needed. He created Ping-o-MaticÂwhich aggregates ping services and simplifies the pinging process for bloggers and tool developers. With Ping-o-Matic, any developer can alert all of the industry&#39;s blogging tools and tracking sites at once. This new kind of open standard, with shared infrastructure, is a critical to the scalability of Web 2.0 services.As Matt said:There are a number of services designed specifically for tracking and connecting blogs. However it would be expensive for all the services to crawl all the blogs in the world all the time. By sending a small ping to each service you let them know you&#39;ve updated so they can come check you out. They get the freshest data possible, you don&#39;t get a thousand robots spidering your site all the time. Everybody wins.Movers and Shakers:Matt Mullenweg, Jim Winstead, Dave Winer8. RoutingBloggers used to have to manually enter the links and content snippets of blog posts or news items they wanted to blog. Today, some RSS aggregators can send a specified post directly into an associated blogging tool: as bloggers browse through the feeds they subscribe to, they can easily specify and send any post they wish to &quot;reblog&quot; from their news aggregator or feed reader into their blogging tool. (This is usually referred to as &quot;BlogThis.&quot;) As structured blogging comes into its own (see the section on Microcontent Publishing), it will be increasingly important to maintain the structural integrity of these pieces of microcontent when reblogging them. Promising standard RedirectThis will combine a &quot;BlogThis&quot;-like capability while maintaining the integrity of the microcontent. RedirectThis will let bloggers and content developers attach a simple &quot;PostThis&quot; button to their posts. Clicking on that button will send that post to the reader/blogger&#39;s favorite blogging tool. This favorite tool is specified at the RedirectThis web service, where users register their blogging tool of choice. RedirectThis also helps maintain the integrity and structure of microcontentÂthen it&#39;s just up to the user to prefer a blogging tool that also attains that lofty goal of microcontent integrity. OutputThis is another nascent web services standard, to let bloggers specify what &quot;destinations&quot; they&#39;d like to have as options in their blogging tool. As new destinations are added to the service, more checkboxes would get added to their blogging toolÂallowing them to route their published microcontent to additional destinations.Movers and Shakers:Michael Migurski, Lucas Gonze9. Open CommunicationsLikely, you&#39;ve experienced the joys of finding friends on AIM or Yahoo Messenger, or the convenience of Skyping with someone overseas. Not that you&#39;re about to throw away your mobile phone or BlackBerry, but for many, also having access to Instant Messaging (IM) and Voice over IP (VoIP) is crucial. IM and VoIP are mainstream technologies that already enjoy the benefits of open standards. Entire industries are bornÂright this secondÂbased around these open standards. Jabber has been an open IM technology for yearsÂin fact, as XMPP, it was officially dubbed a standard by the IETF. Although becoming an official IETF standard is usually the kiss of death, Jabber looks like it&#39;ll be around for a while, as entire generations of collaborative, work-group applications and services have been built on top of its messaging protocol. For VoIP, Skype is clearly the leading standard todayÂthough one could argue just how &quot;open&quot; it is (and defenders of the IETF&#39;s SIP standard often do). But it is free and user-friendly, so there won&#39;t be much argument from usersÂ  about it being insufficiently open. Yet there may be a cloud on Skype&#39;s horizon: web behemoth Google recently released a beta of Google Talk, an IM client committed to open standards. It currently supports XMPP, and will support SIP for VoIP calls.Movers and Shakers:Jeremie Miller, Henning Schulzrinne, Jon Peterson, Jeff Pulver10. Device Management and ControlTo access online content, we&#39;re using more and more devices. BlackBerrys, iPods, Treos, you name it. As the web evolves, more and more different devices will have to communicate with each other to give us the content we want when and where we want it. No-one wants to be dependent on one vendor anymoreÂlike, say, SonyÂfor their laptop, phone, MP3 player, PDA, and digital camera, so that it all works together. We need fully interoperable devices, and the standards to make that work. And to fully make use of how content is moving online content and innovative web services, those standards need to be open.MIDI (musical instrument digital interface), one of the very first open standards in music, connected disparate vendors&#39; instruments, post-production equipment, and recording devices. But MIDI is limited, and MIDI II has been very slow to arrive. Now a new standard for controlling musical devices has emerged: OSC (Open SoundControl). This protocol is optimized for modern networking technology and inter-connects music, video and controller devices with &quot;other multimedia devices.&quot; OSC is used by a wide range of developers, and is being taken up in the mainstream MIDI marketplace.Another open-standards-based device management technology is ZigBee, for building wireless intelligence and network monitoring into all kinds of devices. ZigBee is supported by many networking, consumer electronics, and mobile device companies.Â  Â  Â  Â· Â· Â· Â· Â· Â· Â  Â  The Change to OpennessThe rise of open source software and its &quot;architecture of participation&quot; are completely shaking up the old proprietary-web-services-and-standards approach. Sun MicrosystemsÂwhose proprietary Java standard helped define the Web 1.0Âis opening its Solaris OS and has even announced the apparent paradox of an open-source Digital Rights Management system.Today&#39;s incumbents will have to adapt to the new openness of the Web 2.0. If they stick to their proprietary standards, code, and content, they&#39;ll become the new walled gardensÂplaces users visit briefly to retrieve data and content from enclosed data silos, but not where users &quot;live.&quot; The incumbents&#39; revenue models will have to change. Instead of &quot;owning&quot; their users, users will know they own themselves, and will expect a return on their valuable identity and attention. Instead of being locked into incompatible media formats, users will expect easy access to digital content across many platforms. Yesterday&#39;s web giants and tomorrow&#39;s users will need to find a mutually beneficial new balanceÂbetween open and proprietary, developer and user, hierarchical and horizontal, owned and shared, and compatible and closed. Marc Canter is an active evangelist and developer of open standards. Early in his career, Marc founded MacroMind, which became Macromedia. These days, he is CEO of Broadband Mechanics, a founding member of the Identity Gang and of ourmedia.org. Broadband Mechanics is currently developing the GoingOn Network (with the AlwaysOn Network), as well as an open platform for social networking called the PeopleAggregator.A version of the above post appears in the Fall 2005 issue of AlwaysOn&#39;s quarterly print blogozine, and ran as a four-part series on the AlwaysOn Network website.(Via Marc&#39;s Voice.)</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p><a href="http://marc.blogs.it/">Marc Canter</a>&#39;s <a href="http://marc.blogs.it/archives/2005/10/breaking_the_we.html">Breaking the Web Wide Open! </a> article is something I found pretty late (by my normal discovery standards). This was partly due to the pre- and post- Web 2.0 event noise levels that have dumped the description of an important industry inflection into the &quot;Bozo Bin&quot; of many. Personally, I think we shouldn&#39;t confuse the Web 2.0 traditional-pitch-fest conference with an attempt to identify an important industry inflection).</p><p> Anyway, Marc&#39;s article is a very refreshing read because it provides a really good insight into the general landscape of a rapidly evolving Web alongside genuine appreciation of our broader timeless pursuit of &quot;Openness&quot;. </p><p>To really help this document provide additional value have scrapped the content of the original post and dumped it below so that we can appreciate the value of the links embedded within the article (note: thanks to Virtuoso I only had to paste the content into my blog, the extraction to my <a href="http://www.openlinksw.com/blog/~kidehen/index.vspx?page=linkblog">Linkblog</a> and <a href="http://www.openlinksw.com/blog/~kidehen/index.vspx?page=summary">Blog Summary</a> Pages are simply features of my <a href="http://www.openlinksw.com/virtuos">Virtuoso </a>based Blog Engine):</p><blockquote><h3 class="hed2" style="padding-bottom: 10px">Breaking the Web Wide Open! (complete story)</h3><p>Even the web giants like AOL, Google, MSN, and Yahoo need to observe these open standards, or they&#39;ll risk becoming the &quot;walled gardens&quot; of the new web and be coolio no more.</p><p class="byline"><b><a href="http://community.alwayson-network.com/cgi-bin/WebObjects/AlwaysOn.woa/wa/display?id=9254:Person">Marc Canter</a></b> [<a href="http://community.alwayson-network.com/cgi-bin/WebObjects/AlwaysOn.woa/wa/display?id=9254:Person"><b>Broadband Mechanics, Inc.</b></a>] | POSTED: 09.26.05 @12:00</p><table width="100%" border="0" cellspacing="0" cellpadding="0"><tr><td valign="TOP" class="copy1"><img src="http://community.alwayson-network.com/ao/images/thumb/19433429363e7cd6b1ecfb7.jpg" align="LEFT" border="0" width="80" style="margin: 0px 10px 5px 0px" alt="" /><i><b>Editorial Note:</b> Several months ago, AlwaysOn got a personal invitation from Yahoo founder Jerry Yang &quot;to see and give us feedback on our new social media product, y!360.&quot; We were happy to oblige and dutifully showed up, joining a conference room full of hard-core bloggers and new, new media types. The geeks gave Yahoo 360 an overwhelming thumbs down, with comments like, &quot;So the only services I can use within this new network are Yahoo services? What if I don&#39;t use Yahoo IM?&quot; In essence, the Yahoo team was booed for being &quot;closed web,&quot; and we heartily agreed. With Yahoo 360, Yahoo continues building its own &quot;walled garden&quot; to control its 135 million customersÂan accusation also hurled at AOL in the early 1990s, before AOL migrated its private network service onto the web. As the</i>Â  <a href="http://bernardmoon.blogspot.com/2005/08/yahoos-personality-crisis.html" target="_blank">Economist<i> recently noted</i></a>, &quot;Yahoo, in short, has old media plans for the new-media era.&quot;<br /><br />The irony to our view here is, of course, that today&#39;s AO Network is also a &quot;closed web.&quot; In the end, Mr. Yang&#39;s thoughtful invitation and our ensuing disappointment in his new service led to the assignment of this article. It also confirmed our existing plan to completely revamp the AO Network around open standards. To tie it all together, we recruited the chief architect of our new site, <a href="http://www.corante.com/amateur/articles/20030211-3564.html" target="_blank">the notorious Marc Canter</a>, to pen this piece. We look forward to our reader feedback.<br /><br /><b>Breaking the Web Wide Open!</b><br />By Marc Canter<br /><br />For decades, &quot;walled gardens&quot; of proprietary standards and content have been the strategy of dominant players in mainframe computer software, wireless telecommunications services, and the World Wide WebÂit was their successful lock-in strategy of keeping their customers theirs. But like it or not, those walls are tumbling down. Open web standards are being adopted so widely, with such value and impact, that the web giantsÂAmazon, AOL, eBay, Google, Microsoft, and YahooÂare facing the difficult decision of opening up to what they don&#39;t control.<br /><br />The online world is evolving into a new open web (sometimes called the Web 2.0), which is all about being personalized and customized for each user. Not only open source software, but <i>open standards</i>Â are becoming an essential component. <br /><br />Many of the web giants have been using open source software for years. Most of them use at least parts of the <a href="http://www.onlamp.com/pub/a/onlamp/2001/01/25/lamp.html" target="_blank">LAMP</a> (Linux, Apache, MySQL, Perl/Python/PHP) stack, even if they aren&#39;t well-known for giving back to the open source community. For these incumbents that grew big on proprietary web services, the methods, practices, and applications of open source software development are difficult to fully adopt. And the next open source movementsÂwhich will be as much about open standards as about codeÂwill be a lot harder for the incumbents to exploit.<br /><br />While the incumbents use cheap open source software to run their back-ends systems, their business models largely depend on proprietary software and algorithms. But our view a new slew of open software, open protocols, and open standards will confront the incumbents with the classic <i><a href="http://www.businessweek.com/chapter/christensen.htm" target="_blank">Innovator&#39;s Dilemma</a></i>.Â  Should they adopt these tools and standards, painfully cannibalizing their existing revenue for a new unproven concept, or should they stick with their currently lucrative model with the risk that eventually a bunch of upstarts eat their lunch? <br /><br />Credit should go to several of the web giants who have been making efforts to &quot;open up.&quot; Google, Yahoo, eBay, and Amazon all have Open APIs (Application Programming Interfaces) built into their data and systems. Any software developer can access and use them for whatever creative purposes they wish. This means that the API provider becomes an open platform for everyone to use and build on top of. This notion has expanded like wildfire throughout the blogosphere, so nowadays, Open APIs are pretty much required.<br /><br />Other incumbents also have open strategies. AOL has got the RSS religion, <a href="http://www.siliconbeat.com/entries/2005/07/27/aol_gets_rss_religion_with_my_aoland_feedsters_help.html" target="_blank">providing a feedreader and RSS search</a> in order to escape the &quot;walled garden of content&quot; stigma. <a href="http://www.apple.com/podcasting/" target="_blank">Apple now incorporates podcasts</a>, the &quot;personal radio shows&quot; that are latest rage in audio narrowcasting, into iTunes. Even Microsoft is supporting open standards, for example <a href="http://www.microsoft.com/technet/prodtechnol/winxppro/plan/rtcprot.mspx#EKAA" target="_blank">by endorsing SIP (Session Initiation Protocol) for internet telephony and conferencing</a> over Skype&#39;s proprietary format or one of its own devising.<br /><br />But new open standards and protocols are in use, under construction, or being proposed every day, pushing the envelope of where we are right now. Many of these standards are coming from startup companies and small groups of developers, not from the giants. Together with the Open APIs, those new standards will contribute to a new, open infrastructure. Tens of thousands of developers will use and improve this open infrastructure to create new kinds of web-based applications and services, to offer web users a highly personalized online experience.<br /><br /><b>A Brief History of Openness</b><br /><br />At this point, I have to admit that I am not just a passive observer, full-time journalist or &quot;just some blogger&quot;Âbut an active evangelist and developer of these standards. It&#39;s the vision of &quot;open infrastructure&quot; that&#39;s driving <a href="http://www.broadbandmechanics.com/bbm2005.htm" target="_blank">my company </a> and the reason why I&#39;m writing this article. This article will give you some of the background behind on these standards, and what the evolution of the next generation of open standards will look like.<br /><br />Starting back in the 1980s, establishing a software standard was a key strategy for any software company. My former company, MacroMind (which became Macromedia), achieved this goal early on with Director. As <a href="http://webmonkey.wired.com/webmonkey/99/27/index3a_page6.html?tw=multimedia" target="_blank">Director evolved into Flash</a>, the world saw that other companies besides Microsoft, Adobe, and Apple could establish true cross-platform, independent media standards.<br /><br />Then <a href="http://www.w3.org/People/Berners-Lee/" target="_blank">Tim Berners-Lee</a> and <a href="http://www.ibiblio.org/pioneers/andreesen.html" target="_blank">Marc Andreessen</a> came along, and changed the rules of the software business and of entrepreneurialism. No matter how entrenched and &quot;standardized&quot; software was, the rug could still get pulled out from under it. <a href="http://geekphilosopher.com/MainPage/WebBrowserWars.htm?q=Stocks" target="_blank">Netscape did it to Microsoft, and then Microsoft did it <i>back</i>Â  to Netscape</a>. The web evolved, and lots of standards evolved with it. The leading open source standards (such as the LAMP stack) became widely used alternatives to proprietary closed-source offerings. <br /><br />Open standards are more than just technology. Open standards mean sharing, empowering, and community support. Someone floats a new idea (or <a href="http://en.wikipedia.org/wiki/Meme" target="_blank">meme</a>) and the community runs with it â with each person making their own contributions to the standard â evolving it without a moment&#39;s hesitation about &quot;giving away their intellectual property.&quot;<br /><br />One good example of this was <a href="http://www.sifry.com/alerts/" target="_blank">Dave Sifry</a>, who built the Technorati blog-tracking technology inspired by the <a href="http://www.myelin.co.nz/ecosystem/" target="_blank">Blogging Ecosystem</a>, a weekend project by young hacker <a href="http://marc.blogs.it/archives/2005/07/phil_pearson_jo.html" target="_blank">Phil Pearson</a>. Dave liked what he saw and he ran with itÂturning Technorati into what it is today.<br /><br /><a href="http://en.wikipedia.org/wiki/Dave_Winer" target="_blank">Dave Winer</a> has contributed enormously to this area of open standards. He defined and personally created several open standards and protocolsÂsuch as RSS, OPML, and XML-RPC. Dave has also <a href="http://newhome.weblogs.com/historyOfWeblogs" target="_blank">helped build</a> the blogosphere through his enthusiasm and passion.<br /><br />By 2003, hundreds of programmers were working on creating and establishing new standards for almost everything. The best of these new standards have evolved into compelling web services platforms â such as <a href="http://del.icio.us/" target="_blank">del.icio.us</a>, <a href="http://webjay.org/about" target="_blank">Webjay</a>, or <a href="http://www.flickr.com/photos/tags/ao2005/" target="_blank">Flickr</a>. Some have even spun off formal standards â like XSPF (a standard for playlists) or instant messaging standard XMPP (also known as Jabber).<br /><br />Today&#39;s Open APIs are complemented by standardized SchemasÂthe structure of the data itself and its associated meta-data. Take for example a <a href="http://www.ipodder.org/whatIsPodcasting" target="_blank">podcasting feed</a>. It consists of: a) the radio show itself, b) information on who is on the show, what the show is about and how long the show is (the meta-data) and also c) API calls to retrieve a show (a single feed item) and play it from a specified server. <br /><br />The combination of Open APIs, standardized schemas for handling meta-data, and an industry which agrees on these standards are breaking the web wide open right now. So what new open standards should the web incumbentsÂand youÂbe watching? Keep an eye on the following developments:<br /><br /><b>Identity<br />Attention<br />Open Media<br />Microcontent Publishing<br />Open Social Networks<br />Tags<br />Pinging <br />Routing<br />Open Communications<br />Device Management and Control</b><br /><br /><br /><b>1.	Identity</b><br /><br />Right now, you don&#39;t really control your own online identity. At the core of just about every online piece of software is a membership system. Some systems allow you to browse a site anonymouslyÂbut unless you register with the site you can&#39;t do things like search for an article, post a comment, buy something, or review it. The problem is that each and every site has its own membership system. So you constantly have to register with new systems, which cannot share dataÂeven you&#39;d want them to. By establishing a <a href="http://www.wired.com/news/privacy/0,1848,68329-2,00.html?tw=wn_story_page_next1" target="_blank">&quot;single sign-on&quot; standard</a>, disparate sites can allow users to freely move from site to site, and let them control the movement of their personal profile data, as well as any other data they&#39;ve created. <br /><br />With <a href="http://www.thehindubusinessline.com/2005/01/03/stories/2005010301440200.htm" target="_blank">Passport, Microsoft unsuccessfully attempted</a> to force its proprietary standard on the industry. Instead, a world is evolving where most people assume that users want to control their own data, whether that data is their profile, their blog posts and photos, or some collection of their past interactions, purchases, and recommendations. As long as users can control their digital identity, any kind of service or interaction can be layered on top of it.<br /><br /><a href="http://www.identity20.com/media/OSCON2005/" target="_blank">Identity 2.0</a> is all about users controlling their own profile data and becoming their own agents. This way the users themselves, rather than other intermediaries, will profit from their ID info. Once developers start offering single sign-on to their users, and users have trusted places to store their dataÂwhich respect the limits and provide access controls over that data, users will be able to access personalized services which will understand and use their personal data.<br /><br />Identity 2.0 may seem like some geeky, visionary future standard that isn&#39;t defined yet, but by putting each user&#39;s digital identity at the core of all their online experiences, Identity 2.0 is becoming the cornerstone of the new open web. <br /><br /><b>The Initiatives:</b><br />Right now, Identity 2.0 is under construction through various efforts from Microsoft (the <a href="http://msdn.microsoft.com/webservices/webservices/understanding/advancedwebservices/default.aspx?pull=/library/en-us/dnwebsrv/html/identitymetasystem.asp" target="_blank">&quot;InfoCard&quot; component built into the Vista operating system</a> and its &quot;<a href="http://garage.docsearls.com/node/605" target="_blank">Identity Metasystem</a>&quot;), <a href="http://sxip.com" target="_blank">Sxip Identity</a>, <a href="http://www.identtycommons.net" target="_blank">Identity Commons</a>, <a href="http://www.projectliberty.org/" target="_blank">Liberty Alliance</a>, <a href="http://lid.netmesh.org/" target="_blank">LID</a> (NetMesh&#39;s Lightweight ID), and SixApart&#39;s <a href="http://openid.net/" target="_blank">OpenID</a>.<br /><br /><b>More Movers and Shakers:</b><br />Identity Commons and <a href="http://www.identitywoman.net" target="_blank">Kaliya Hamlin</a>, Sxip Identity and <a href="http://blame.ca/dick/" target="_blank">Dick Hardt</a>, the <a href="http://www.identitygang.org/" target="_blank"> Identity Gang</a> and <a href="http://www.searls.com/dochome.html#Bio" target="_blank">Doc Searls</a>, Microsoft&#39;s <a href="http://www.identityblog.com/" target="_blank">Kim Cameron</a>, <a href="http://www.craigburton.com/" target="_blank">Craig Burton</a>, <a href="http://phil.windley.org/" target="_blank">Phil Windley</a>, and <a href="http://slashdot.org/article.pl?sid=05/07/05/2020221&from=rss" target="_blank">Brad Fitzpatrick</a>, to name a few.<br /><br /><br /><b>2.	Attention</b><br /><br />How many readers know what their online attention is worth? If you don&#39;t, Google and Yahoo doÂthey make their living off our attention. They know what we&#39;re searching for, happily turn it into a keyword, and sell that keyword to advertisers. They make money off our attention. We don&#39;t. <br /><br />Technorati and friends proposed <a href="http://blogs.zdnet.com/Gillmor/index.php?p=74" target="_blank">an attention standard, Attention.xml</a>, designed to &quot;help you keep track of what you&#39;ve read, what you&#39;re spending time on, and what you should be paying attention to.&quot; <a href="http://attentiontrust.org/" target="_blank">AttentionTrust</a> is an effort by <a href="http://blogs.zdnet.com/Gillmor/?p=132" target="_blank">Steve Gillmor</a> and <a href="http://majestic.typepad.com/seth/2005/07/attentiontrusto.html" target="_blank">Seth Goldstein </a>to standardize on how captured end-user performance, browsing, and interest data are used. <br /><br />Blogger <a href="http://worcester.typepad.com/pc4media/2005/07/attentiontrusto_1.html" target="_blank">Peter Caputa gives a good summary</a> of AttentionTrust: <blockquote>&quot;As we use the web, we reveal lots of information about ourselves by what we pay attention to. Imagine if all of that information could be stored in a nice neat little xml file. And when we travel around the web, we can optionally share it with websites or other people. We can make them pay for it, lease it ... we get to decide who has access to it, how long they have access to it, and what we want in return. And they have to tell us what they are going to do with our Attention data.&quot;</blockquote><br />So when you give your attention to sites that adhere to the AttentionTrust, your attention rights (<i>you own your attention, you can move your attention, you can pay attention and be paid for it</i>,Â  and <i>you can see how your attention is used</i>) are guaranteed. Attention data is crucial to the future of the open web, and Steve and Seth are making sure that no one entity or oligopoly controls it. <br /><br /><b>Movers and Shakers:</b><br /><a href="http://blogs.zdnet.com/Gillmor/" target="_blank">Steve Gillmor</a>, <a href="http://majestic.typepad.com/about.html" target="_blank">Seth Goldstein</a>, <a href="http://www.sifry.com/alerts/" target="_blank">Dave Sifry</a> and the <a href="http://developers.technorati.com/wiki/attentionxml" target="_blank">other Attention.xml folks</a>. <br /><br /><br /><b>3.	Open Media</b><br /><br />Proprietary media standardsÂFlash, Windows Media, and QuickTime, to name a few Âhelped liven up the web. But they are proprietary standards that try to keep us locked in, and they weren&#39;t created from scratch to handle today&#39;s online content. That&#39;s why, for many of us, an Open Media standard has been a holy grail. Yahoo&#39;s new Media RSS standard brings us one step closer to achieving open media, as do <a href="http://www.vorbis.com/faq/#what" target="_blank">Ogg Vorbis</a> audio codecs, <a href="http://webjay.org/" target="_blank">XSPF playlists</a>, or <a href="http://musicbrainz.org/" target="_blank">MusicBrainz</a>. And several sites offer digital creators not only a place to store their content, but also to sell it. <br /><br /><a href="http://search.yahoo.com/mrss" target="_blank">Media RSS </a>(being developed by Yahoo with help from the community) extends RSS and combines it with &quot;RSS enclosures&quot; Âadds metadata to any media itemÂto create a comprehensive solution for media &quot;narrowcasters.&quot; To gain acceptance for Media RSS, Yahoo knows it has to work with the community. As an active member of this community, I can tell you that we&#39;ll create Media RSS equivalents for <a href="http://www.xml.com/pub/a/2001/01/24/rdf.html" target="_blank">rdf</a> (an alternative subscription format) and <a href="http://www.atomenabled.org/" target="_blank">Atom</a> (yet <i>another</i>Â  subscription format), so no one will be able to complain that Yahoo is picking sides in format wars.<br /><br />When Yahoo announced the purchase of Flickr, Yahoo founder Jerry Yang insinuated that Yahoo is acquiring &quot;open DNA&quot; to turn Yahoo into <a href="http://www.flickr.com/services/api/" target="_blank">an open standards player</a>. Yahoo is showing what happens when you take a multi-billion dollar company and make openness one of its core valuesÂso Google, beware, even if Google does have more research fellows and Ph.D.s. <br /><br />The open media landscape is far and wide, reaching from game machine hacks and mobile phone downloads to PC-driven bookmarklets, players, and editors, and it includes many other standardization efforts. <a href="http://www.xspf.org/" target="_blank">XSPF</a> is an open standard for playlists, and MusicBrainz is an alternative to the proprietary (and originally effectively stolen) database that <a href="http://en.wikipedia.org/wiki/Gracenote" target="_blank">Gracenote</a> licenses. <br /><br /><a href="http://www.ourmedia.org/" target="_blank">Ourmedia.org</a> is a community front-end to Brewster Kahle&#39;s <a href="http://www.archive.org" target="_blank">Internet Archive</a>. Brewster has promised free bandwidth and free storage forever to any content creators who choose to share their content via the Internet Archive. Ourmedia.org is providing an easy-to-use interface and community to get content in and out of the Internet Archive, giving ourmedia.org users the ability to share their media anywhere they wish, without being locked into a particular service or tool. Ourmedia plans to offer open APIs and an open media registry that interconnects other open media repositories into a DNS-like registry (just like the www domain system), so folks can browse and discover open content across many open media services. Systems like <a href="http://www.brightcove.com/" target="_blank">Brightcove</a> and <a href="http://www.evhead.com/2005/02/how-odeo-happened.asp" target="_blank">Odeo</a> support the concept of an open registry, and hope to work with digital creators to sell their work to fulfill the financial aspect of <a href="http://en.wikipedia.org/wiki/The_Long_Tail" target="_blank">the &quot;Long Tail.&quot;</a><br /><br /><b>More Movers and Shakers:</b><br /><a href="http://creativecommons.org/about/people" target="_blank">Creative Commons</a>, the <a href="http://www.omn.org/" target="_blank">Open Media Network</a>, <a href="http://www.momentshowing.net/about.html" target="_blank">Jay Dedman</a>, <a href="http://ryanedit.blogspot.com/" target="_blank">Ryanne Hodson</a>, <a href="http://michaelverdi.com/index.php" target="_blank">Michael Verdi</a>, <a href="http://www.chapmanlogic.com/blog/aboutEli.html" target="_blank">Eli Chapman</a>, <a href="http://www.unmediated.org/" target="_blank">Kenyatta Cheese</a>, <a href="http://www.itconversations.com/about.html" target="_blank">Doug Kaye</a>, <a href="http://www.wired.com/wired/archive/13.09/yahoo.html" target="_blank">Brad Horowitz</a>, <a href="http://webjay.org/about#colophon" target="_blank">Lucas Gonze</a>, <a href="http://musicbrainz.org/wd/MusicBrainzBio" target="_blank">Robert Kaye</a>,  <a href="http://www.lifewithalacrity.com/" target="_blank">Christopher Allen</a>, <a href="http://en.wikipedia.org/wiki/Brewster_Kahle" target="_blank">Brewster Kahle</a>, <a href="http://www.newmediamusings.com/" target="_blank">JD Lasica</a>, and indeed, <a href="http://www.corante.com/amateur/articles/20030211-3564.html" target="_blank">Marc Canter</a>, among others.<br /><br /><br /><b>4.	Microcontent Publishing</b><br /><br />Unstructured content is cheap to create, but hard to search through. Structured content is expensive to create, but easy to search. <a href="http://developers.technorati.com/wiki/MicroFormats" target="_blank">Microformats</a> resolve the dilemma with simple structures that are cheap to use and easy to search.<br /><br />The first kind of widely adopted microcontent is blogging. Every post is an encapsulated idea, addressable via a URL called a permalink. You can syndicate or subscribe to this microcontent using RSS or an RSS equivalent, and news or blog aggregators can then display these feeds in a convenient readable fashion. But a blog post is just a block of unstructured textânot a bad thing, but just a first step for microcontent. When it comes to<i>structured</i>Â data, such as personal identity profiles, product reviews, or calendar-type event data, RSS was not designed to maintain the integrity of the structures. <br /><br />Right now, blogging doesn&#39;t have the underlying structure necessary for full-fledged microcontent publishing. But that will change. Think of local information services (such as movie listings, event guides, or restaurant reviews) that any college kid can access and use in her weekend programming project to create new services and tools.<br /><br />Today&#39;s blogging tools will evolve into microcontent publishing systems, and will help spread the notion of structured data across the blogosphere. New ways to store, represent and produce microcontent will create new standards, such as <a href="http://structuredblogging.org/" target="_blank">Structured Blogging</a> and <a href="http://microformats.org/" target="_blank">Microformats</a>. Microformats differ from RSS feeds in that you can&#39;t subscribe to them. Instead, Microformats are embedded into webpages and discovered by search engines like Google or Technorati. Microformats are creating common definitions for &quot;What is a review or event? What are the specific fields in the data structure?&quot; They can also specify what we can do with all this information.<a href="http://www.opml.org/spec" target="_blank">OPML (Outline Processor Markup Language)</a> is a hierarchical file format for storing microcontent and structured data. It was developed by <a href="http://en.wikipedia.org/wiki/Dave_Winer" target="_blank">Dave Winer</a> of RSS and podcast fame.<br /><br />Events are one popular type of microcontent. <a href="http://www.openevents.com" target="_blank">OpenEvents</a> is already working to create shared databases of standardized events, which would get used by a new generation of event portalsâsuch as <a href="http://eventful.com/gotevents/" target="_blank">Eventful/EVDB</a>, <a href="http://upcoming.org/" target="_blank">Upcoming.org</a>, and <a href="http://www.whizspark.com/" target="_blank">WhizSpark</a>. The idea of OpenEvents is that event-oriented systems and services can work together to establish shared events databases (and associated APIs) that any developer could then use to create and offer their own new service or application. <a href="http://marc.blogs.it/archives/2005/04/rvw_redux_openr.html" target="_blank">OpenReviews</a> is still in the conceptual stage, but it would make it possible to provide open alternatives to closed systems like Epinions, and establish a shared database of local and global reviews. Its shared open servers would be filled with all sorts of reviews for anyone to access. <br /><br />Why is this important? Because I predict that in the future, 10 times more people will be writing reviews than maintaining their own blog. The list of possible microcontent standards goes on: OpenJobpostings, OpenRecipes, and even OpenLists. Microsoft <a href="http://www.reallysimplesyndication.com/2005/06/22" target="_blank">recently revealed</a> that it has been working on an important new kind of microcontent: Listsâso OpenLists will attempt to establish standards for the <i>kind</i>Â of lists we all use, such as lists of Links, lists of To Do Items, lists of People, Wish Lists, etc.<br /><br /><b>Movers and Shakers:</b><br /><a href="http://tantek.com/log/2005/09.html" target="_blank">Tantek Ãelik</a> and <a href="http://en.wikipedia.org/wiki/Kevin_Marks" target="_blank">Kevin Marks</a> of <a href="http://developers.technorati.com/wiki/MicroFormats" target="_blank">Technorati</a>, <a href="http://dannyayers.com/" target="_blank">Danny Ayers</a>, <a href="http://www.meyerweb.com/" target="_blank">Eric Meyer</a>, <a href="http://photomatt.net/" target="_blank">Matt Mullenweg</a>, <a href="http://zlab.commerce.net/" target="_blank">Rohit Khare</a>, <a href="http://ifindkarma.typepad.com/relax/" target="_blank">Adam Rifkin</a>, <a href="http://www.sivas.com/aleene/" target="_blank">Arnaud Leene</a>, <a href="http://radio.weblogs.com/0110772/" target="_blank">Seb Paquet</a>, <a href="http://hublog.hubmed.org/" target="_blank">Alf Eaton</a>, <a href="http://www.myelin.co.nz/post/" target="_blank">Phil Pearson</a>, <a href="http://www.joereger.com/" target="_blank">Joe Reger</a>, <a href="http://bobwyman.pubsub.com/" target="_blank">Bob Wyman</a> among others.<br /><br /><br /><b>5.	Open Social Networks</b><br /><br />I&#39;ll never forget the first time I met <a href="http://www.jabrams.com/" target="_blank">Jonathan Abrams</a>, the founder of Friendster. He was arrogant and brash and he claimed he &quot;<i>owned</i>&quot;Â  all his users, and that he was going to monetize them and make a fortune off them. This attitude robbed Friendster of its momentum, letting MySpace, Facebook, and other social networks take Friendster&#39;s place.<br /><br />Jonathan&#39;s notion of social networks as a way to control users is typical of the Web 1.0 business model and its attitude towards users in general. Social networks have become one of the battlegrounds between old and new ways of thinking. Open standards for Social Networking will define those sides very clearly. Since meeting Jonathan, I have been working towards finding and establishing open standards for social networks. Instead of closed, centralized social networks with 10 million people in them, the goal is making it possible to have 10 million social networks that each have 10 people in them.<br /><br />FOAF (which stands for Friend Of A Friend, and describes people and relationships in a way that computers can parse) is a schema to represent not only your personal profile&#39;s meta-data, but your social network as well. Thousands of researchers use the <a href="http://www.foaf-project.org/" target="_blank">FOAF schema</a> in their &quot;Semantic Web&quot; projects to connect people in all sorts of new ways. <a href="http://gmpg.org/xfn/" target="_blank">XFN</a> is a microformat standard for representing your social network, while <a href="http://www.imc.org/pdi/" target="_blank">vCard</a> (long familiar to users of contact manager programs like Outlook) is a microformat that contains your profile information. Microformats are baked into any xHTML webpage, which means that<i>any</i>Â blog, social network page, or any webpage in general can &quot;contain&quot; your social network in itÂand be used by<i>any</i>Â compatible tool, service or application. <br /><br />PeopleAggregator is an earlier project now being integrated into <a href="http://drupal.org/" target="_blank">open content management framework Drupal</a>. The <a href="http://www.broadbandmechanics.com/PeopleAggregator/" target="_blank">PeopleAggregator APIs</a> will make it possible to establish relationships, send messages, create or join groups, and post between different social networks. (Sneak preview: this technology will be available in the upcoming GoingOn Network.) <br /><br />All of these open social networking standards mean that inter-connected social networks will form a mesh that will parallel the blogosphere. This vibrant, distributed, decentralized world will be driven by open standards: personalized online experiences are what the new open web will be all aboutÂand what could be more personalized than people&#39;s networks?<br /><br /><b>Movers and Shakers:</b><br /><a href="http://esigler.2nw.net/" target="_blank">Eric Sigler</a>, <a href="http://lucifer.intercosmos.net/index.php?view=about" target="_blank">Joel De Gan</a>, <a href="http://crschmidt.net/" target="_blank">Chris Schmidt</a>, <a href="http://voidstar.com/" target="_blank">Julian Bond</a>, <a href="http://people.tribe.net/paul?_click_path=Application%5Btribe%5D.Person%5Bf2232c95-e123-43a3-b48d-24a5f11f09dc%5D&r=10535" target="_blank">Paul Martino</a>, <a href="http://napsterization.org/stories/archives/000513.html" target="_blank">Mary Hodder</a>, <a href="http://public.2idi.com/=Drummond.Reed" target="_blank">Drummond Reed</a>, <a href="http://danbri.org/" target="_blank">Dan Brickley</a>, <a href="http://360.yahoo.com/profile-9lciejI3aafX1stHPoIRNmkmv4EowQ--" target="_blank">Randy Farmer</a>, and <a href="http://www.kaliyasblogs.net/Iwoman/" target="_blank">Kaliya Hamlin</a>, to name a few.<br /><br /><br /><b>6.	Tags</b><br /><br />Nowadays, no self-respecting tool or service can ship without <a href="http://www.salon.com/tech/feature/2005/02/08/tagging/index_np.html" target="_blank">tags</a>. Tags are keywords or phrases attached to photos, blog posts, URLs, or even video clips. These user- and creator-generated tags are an open alternative to what used to be the domain of librarians and information scientists: categorizing information and content using taxonomies. Tags are instead creating <a href="http://www.wired.com/wired/archive/13.04/view.html?pg=4" target="_blank">&quot;folksonomies.&quot;</a><br /><br />The recently proposed OpenTags concept would be an open, community-owned version of the popular <a href="http://www.technorati.com/tag/" target="_blank">Technorati Tags service</a>. It would aggregate the usage of tags across a wide range of services, sites, and content tools. In addition to Technorati&#39;s current tag features, OpenTags would let groups of people share their tags in &quot;<a href="http://www.zeldman.com/daily/0405d.shtml/" target="_blank">TagClouds</a>.&quot; Open tagging is likely to include some of the open identity features discussed above, to create a tag system that is resilient to spam, and yet trustable across sites all over the web.<br /><br />OpenTags owes a debt to earlier versions of shared tagging systems, which include <a href="http://www.topicexchange.com/" target="_blank">Topic Exchange</a> and something called the <a href="http://www.evectors.com/itkcollector/" target="_blank">k-collector</a>Âa knowledge management tag aggregatorÂfrom Italian company eVectors. <br /><br /><b>Movers &amp; Shakers:</b><br /><a href="http://www.myelin.co.nz/notes/" target="_blank">Phil Pearson</a>, <a href="http://matt.blogs.it/" target="_blank">Matt Mower </a>, <a href="http://paolo.evectors.it/" target="_blank">Paolo Valdemarin</a>, and <a href="http://marc.blogs.it/archives/2005/03/opentopics.html" target="_blank">Mary Hodder</a> and <a href="http://www.equalsdrummond.name/index.php?p=39" target="_blank"> Drummond Reed</a> again, among others.<br /><br /><br /><b>7. Pinging</b><br /><br />Websites used to be mostly static. Search engines that <a href="http://en.wikipedia.org/wiki/Web_crawler" target="_blank">crawled</a> (or &quot;spidered&quot;) them every so often did a good enough job to show reasonably current versions of your cousin&#39;s homepage or even <i>Time</i>Â magazine&#39;s weekly headlines. But when blogging took off, it became hard for search engines to keep up. (Google has only <a href="http://searchenginewatch.com/searchday/article.php/3548411" target="_blank">just managed</a> to offer <a href="http://www.google.com/help/about_blogsearch.html" target="_blank">blog-search functionality</a>, despite <a href="http://www.alwayson-network.com/comments.php?id=325_0_2_0_C" target="_blank">buying Blogger</a> back in early 2003.)<br /><br />To know what was new in the blogosphere, users couldn&#39;t depend on services that spidered webpages once in a while. The solution: a way for blogs themselves to automatically notify blog-tracking sites that they&#39;d been updated. <a href="http://weblogs.com/" target="_blank">Weblogs.com</a> was the first blog &quot;ping service&quot;: it displayed the name of a blog whenever that blog was updated. Pinging sites helped the blogosphere grow, and <a href="http://blo.gs/" target="_blank">more tools</a>, services, and portals started using pinging in new and different ways. Dozens of pinging services and sitesÂmost of which can&#39;t talk to each otherÂsprang up. <br /><br />Matt Mullenweg (the creator of open source blogging software WordPress) decided that a one-stop service for pinging was needed. He created <a href="http://pingomatic.com/" target="_blank">Ping-o-Matic</a>Âwhich aggregates ping services and simplifies the pinging process for bloggers and tool developers. With Ping-o-Matic, any developer can alert all of the industry&#39;s blogging tools and tracking sites at once. This new kind of open standard, with shared infrastructure, is a critical to the scalability of Web 2.0 services.<br /><br />As <a href="http://pingomatic.com/about/" target="_blank">Matt said</a>:<br /><blockquote>There are a number of services designed specifically for tracking and connecting blogs. However it would be expensive for all the services to crawl all the blogs in the world all the time. By sending a small ping to each service you let them know you&#39;ve updated so they can come check you out. They get the freshest data possible, you don&#39;t get a thousand robots spidering your site all the time. Everybody wins.</blockquote><br /><b>Movers and Shakers:</b><br /><a href="http://photomatt.net/about/" target="_blank">Matt Mullenweg</a>, <a href="http://trainedmonkey.com/entry/2251" target="_blank">Jim Winstead</a>, <a href="http://newhome.weblogs.com/faq" target="_blank">Dave Winer</a><br /><br /><br /><b>8. Routing</b><br /><br />Bloggers used to have to manually enter the links and content snippets of blog posts or news items they wanted to blog. Today, some RSS aggregators can send a specified post directly into an associated blogging tool: as bloggers browse through the feeds they subscribe to, they can easily specify and send any post they wish to &quot;<a href="http://www.microsoftmonitor.com/archives/010209.html" target="_blank">reblog</a>&quot; from their news aggregator or feed reader into their blogging tool. (This is usually referred to as &quot;<a href="http://help.blogger.com/bin/answer.py?answer=152&topic=17" target="_blank">BlogThis</a>.&quot;) As structured blogging comes into its own (see the section on Microcontent Publishing), it will be increasingly important to maintain the structural integrity of these pieces of microcontent when reblogging them. <br /><br />Promising standard <a href="http://redirectthis.com/" target="_blank">RedirectThis</a> will combine a &quot;BlogThis&quot;-like capability while maintaining the integrity of the microcontent. RedirectThis will let bloggers and content developers attach a simple &quot;PostThis&quot; button to their posts. Clicking on that button will send that post to the reader/blogger&#39;s favorite <a href="http://ecto.kung-foo.tv/archives/000990.php" target="_blank">blogging tool</a>. This favorite tool is specified at the RedirectThis web service, where users register their blogging tool of choice. RedirectThis also helps maintain the integrity and structure of microcontentÂthen it&#39;s just up to the user to prefer a blogging tool that also attains that lofty goal of microcontent integrity. <br /><br />OutputThis is another nascent web services standard, to let bloggers specify what &quot;destinations&quot; they&#39;d like to have as options in their blogging tool. As new destinations are added to the service, more checkboxes would get added to their blogging toolÂallowing them to route their published microcontent to additional destinations.<br /><br /><b>Movers and Shakers:</b><br /><a href="http://reblog.org/" target="_blank">Michael Migurski</a>, <a href="http://www.gonze.com/about" target="_blank">Lucas Gonze</a><br /><br /><br /><b>9. Open Communications</b><br /><br />Likely, you&#39;ve experienced the joys of finding friends on AIM or Yahoo Messenger, or the convenience of Skyping with someone overseas. Not that you&#39;re about to throw away your mobile phone or BlackBerry, but for many, also having access to Instant Messaging (IM) and Voice over IP (VoIP) is crucial. <br /><br />IM and VoIP are mainstream technologies that already enjoy the benefits of open standards. Entire industries are bornÂright this secondÂbased around these open standards. <a href="http://www.jabber.org/" target="_blank">Jabber</a> has been an open IM technology for yearsÂin fact, <a href="http://www.xmpp.org/history.html" target="_blank">as XMPP</a>, it was officially dubbed a standard by <a href="http://www.ietf.org/overview.html" target="_blank">the IETF</a>. Although becoming an <a href="http://en.wikipedia.org/wiki/IETF" target="_blank">official IETF standard</a> is usually the kiss of death, Jabber looks like it&#39;ll be around for a while, as entire generations of collaborative, work-group applications and services have been built on top of its messaging protocol. For VoIP, <a href="http://skype.com/helloagain.html" target="_blank">Skype</a> is clearly the leading standard todayÂthough one could <a href="http://socialsoftware.weblogsinc.com/entry/1234000923058521/" target="_blank">argue just how &quot;open&quot; it is</a> (and defenders of the IETF&#39;s <a href="http://www.cs.columbia.edu/sip/" target="_blank">SIP standard</a> often do). But it is free and user-friendly, so there won&#39;t be much argument from <i>users</i>Â  about it being insufficiently open. Yet there may be a cloud on Skype&#39;s horizon: web behemoth Google recently released a beta of <a href="http://www.google.com/talk/developer.html" target="_blank">Google Talk, an IM client committed to open standards</a>. It currently <a href="http://radar.oreilly.com/archives/2005/08/google_talk_rel.html" target="_blank">supports XMPP, and will support SIP</a> for VoIP calls.<br /><br /><b>Movers and Shakers:</b><br /><a href="http://www.jabber.org/people/jer.shtml" target="_blank">Jeremie Miller</a>, <a href="http://www.cs.columbia.edu/~hgs/" target="_blank">Henning Schulzrinne</a>, <a href="http://www.von.com/schedule_eos11114704148.html" target="_blank">Jon Peterson</a>, <a href="http://www.pulver.com/jeff/" target="_blank">Jeff Pulver</a><br /><br /><br /><b>10. Device Management and Control</b><br /><br />To access online content, we&#39;re using more and more devices. BlackBerrys, iPods, Treos, you name it. As the web evolves, more and more different devices will have to communicate with each other to give us the content we want when and where we want it. No-one wants to be dependent on one vendor anymoreÂlike, <a href="http://www.alwayson-network.com/comments.php?id=P9409_0_6_0_C" target="_blank">say, Sony</a>Âfor their laptop, phone, MP3 player, PDA, and digital camera, so that it all works together. We need fully interoperable devices, and the standards to make that work. And to fully make use of how content is moving online content and innovative web services, those standards need to be open.<br /><br /><a href="http://en.wikipedia.org/wiki/Midi" target="_blank">MIDI (musical instrument digital interface)</a>, one of the very first open standards in music, connected disparate vendors&#39; instruments, post-production equipment, and recording devices. But MIDI is limited, and <a href="http://www.oreillynet.com/pub/wlg/8015" target="_blank">MIDI II has been very slow to arrive</a>. Now a new standard for controlling musical devices has emerged: <a href="http://www.cnmat.berkeley.edu/OpenSoundControl/" target="_blank">OSC (Open SoundControl)</a>. This protocol is optimized for modern networking technology and inter-connects music, video and controller devices with &quot;other multimedia devices.&quot; OSC is used by a wide range of developers, and is being taken up in the mainstream MIDI marketplace.<br /><br />Another open-standards-based device management technology is <a href="http://www.zigbee.org" target="_blank">ZigBee</a>, for building wireless intelligence and network monitoring into all kinds of devices. ZigBee is supported by many networking, consumer electronics, and mobile device companies.<br /><br /><br />Â  Â  Â  Â· Â· Â· Â· Â· Â· Â  Â  <br /><br /><b>The Change to Openness</b><br /><br />The rise of open source software and its &quot;<a href="http://www.oreillynet.com/pub/a/oreilly/tim/articles/architecture_of_participation.html" target="_blank">architecture of participation</a>&quot; are completely shaking up the old proprietary-web-services-and-standards approach. Sun MicrosystemsÂwhose proprietary Java standard helped define the Web 1.0Âis opening its Solaris OS and has even announced the apparent paradox of an <a href="http://blogs.zdnet.com/open-source/?p=418" target="_blank">open-source Digital Rights Management</a> system.<br /><br />Today&#39;s incumbents will have to adapt to the new openness of the Web 2.0. If they stick to their <a href="http://www.gartner.com/DisplayDocument?doc_cd=131038" target="_blank">proprietary standards</a>, code, and content, they&#39;ll become the new walled gardensÂplaces users visit briefly to retrieve data and content from enclosed data silos, but not where users &quot;live.&quot; The incumbents&#39; revenue models will have to change. Instead of &quot;owning&quot; their users, users will know they own themselves, and will expect a return on their valuable identity and attention. Instead of being locked into incompatible media formats, users will expect easy access to digital content across many platforms. <br /><br />Yesterday&#39;s web giants and tomorrow&#39;s users will need to find a mutually beneficial new balanceÂbetween open and proprietary, developer and user, hierarchical and horizontal, owned and shared, and compatible and closed. <br /><br /><br /><i>Marc Canter is an active evangelist and developer of open standards. Early in his career, Marc founded MacroMind, which became Macromedia. These days, he is CEO of Broadband Mechanics, a founding member of the Identity Gang and of ourmedia.org. Broadband Mechanics is currently developing the <a href="http://www.alwayson-network.com/comments.php?id=11262_0_1_0_C" target="_blank">GoingOn Network</a> (with the AlwaysOn Network), as well as an open platform for social networking called the PeopleAggregator.</i><br /><br />A version of the above post appears in the Fall 2005 issue of AlwaysOn&#39;s quarterly print blogozine, and ran as <a href="http://www.alwayson-network.com/comments.php?id=12063_0_1_0_C" target="_blank">a four-part series</a> on the AlwaysOn Network website.</td></tr></table><br /><p>(Via <a href="http://marc.blogs.it/">Marc&#39;s Voice</a>.)</p></blockquote>]]></content:encoded>
 </rss:item>
</rdf:RDF>