<?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/blog/kidehen@openlinksw.com/blog/">
  <rss:title>Kingsley Idehen&#39;s Blog Data Space</rss:title>
  <rss:link>http://www.openlinksw.com/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/">2010-08-01T03:08:43Z</dc:date>
  <rss:items>
   <rdf:Seq>
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2007-04-01#1175" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2006-05-05#968" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2006-04-13#957" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2006-04-11#951" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2005-10-27#885" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2005-05-01#828" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2005-04-21#793" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2005-03-26#766" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2004-11-19#642" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-10-23#395" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-08-05#232" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-07-31#226" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-07-07#201" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-06-25#187" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-06-25#183" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-06-08#108" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-06-08#261" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-06-05#100" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-06-05#253" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-30#346" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-28#336" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-23#330" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-23#59" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-22#52" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-20#308" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-18#305" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-15#298" />
      <rdf:li rdf:resource="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-14#360" />
   </rdf:Seq>
  </rss:items>
 </rss:channel>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2007-04-01#1175">
  <rss:title>Open Source and Open Data Movements</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2007-04-01T22:02:15Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Dare Obasanjo&#39;s post about the issue of Open Data (or Open Data Access), indicates that the &quot;Open Data&quot; issue is gradually beginning to resonate across a broader audience. From my perspective on things I prefer to align my articulation of the changes that are occurring across our industry (courtesy of the Internet Inflection) to the MVC pattern. Re. the Web Versions (or Dimensions of Interaction): Web 1.0 - (V)iewer (Interactive Web experienced via Browser) Web 2.0 - (C)ontroller Web (via Web Services API) Web 3.0 - (M)odel (via the RDF Data Model as the basis for an Open and Standards based Concrete Conceptual Data Model) The same applies to evolution of Openness: Early work by Sun and other early UNIX Vendors - (V)iewer (Interaction with the same OS across different hardware platforms) Open Source Movement - (C)ontroller (Open Access to Application Source Code ) Open Data - (M)odel (*where we are now* Freeing the Date from the Applications and Services while moving the application development focus to a Concrete Conceptual Data Model focus. The Data Web is a classic example.) In the (C)ontroller realm where the focal point is Application Logic, data access issues aren&#39;t obvious (*I recall my battles with Richard Stallman re. the appropriate Open Source License variant for iODBC during the embryonic years of database and data access technology on Linux*). Data is an enigma in this realm, unfortunately. This implies that &quot;Data Lock-in&quot; occurs deliberately, but in most cases, inadvertently when we make Application Logic the focal point of everything. Another example is Web 2.0 in which the norm (unfortunately) is to suck in your data, and then refuse to give you complete ownership over how it is used (including the fact that you may want to share it elsewhere). Open Data is a really big deal which is why the SWEO supported Linking Open Data Project is a very big deal. The good news is that this movement is gathering moment at an exponential rate :-)</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>
<a href="http://www.25hoursaday.com/weblog/PermaLink.aspx?guid=69141977-7514-443d-800b-1f95c1ff8dbe">Dare Obasanjo&#39;s post about the issue of Open Data</a> (or Open Data Access), indicates that the &quot;<a href="http://en.wikipedia.org/wiki/Open_Data">Open Data</a>&quot; issue is gradually beginning to resonate across a broader audience.</p>
<p>From my perspective on things I prefer to align my articulation of the changes that are occurring across our industry (courtesy of the Internet Inflection) to the <a href="http://en.wikipedia.org/wiki/Model-view-controller">MVC pattern</a>.</p>

<p>Re. the Web Versions (or Dimensions of Interaction):</p>
<ul>
Web 1.0 - (V)iewer (Interactive Web experienced via Browser)
</ul>
<ul>
Web 2.0 - (C)ontroller Web (via Web Services API)
</ul>
<ul>
Web 3.0 - (M)odel (via the RDF Data Model as the basis for an Open and Standards based Concrete Conceptual Data Model)</ul>

<p>The same applies to evolution of Openness:</p>
<ul>
Early work by Sun and other early UNIX Vendors - (V)iewer (Interaction with the same OS across different hardware platforms)</ul>
<ul>Open Source Movement - (C)ontroller (Open Access to Application Source Code )</ul>
<ul>Open Data - (M)odel (*where we are now* Freeing the Date from the Applications and Services while moving the application development focus to a Concrete Conceptual Data Model focus. The Data Web is a classic example.)</ul>

<p>In the (C)ontroller realm where the focal point is Application Logic, data access issues aren&#39;t obvious (*I recall <a href="http://207.22.26.166/bytecols/1999-11-03.html">my battles with Richard Stallman re. the appropriate Open Source License variant for iODBC</a> during the embryonic years of database and data access technology on Linux*). Data is an enigma in this realm, unfortunately. This implies that &quot;Data Lock-in&quot; occurs deliberately, but in most cases, inadvertently when we make Application Logic the focal point of everything. Another example is Web 2.0 in which the norm (unfortunately) is to suck in your data, and then refuse to give you complete ownership over how it is used (including the fact that you may want to share it elsewhere).</p>


<a href="http://en.wikipedia.org/wiki/Open_Data">Open Data</a> is a really big deal which is why the <a href="http://www.w3.org/2001/sw/sweo/">SWEO</a> supported <a href="http://esw.w3.org/topic/SweoIG/TaskForces/CommunityProjects/LinkingOpenData">Linking Open Data Project</a> is a very big deal. The good news is that this movement is gathering moment at an exponential rate :-)]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2006-05-05#968">
  <rss:title>&quot;Free&quot; Databases: Express vs. Open-Source RDBMSs</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2006-05-05T16:02:17Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Very detailed and insightful peek into the state of affairs re. database engines (Open &amp; Closed Source). I added the missing piece regarding the &quot;Virtuoso Conductor&quot; (the Web based Admin UI for Virtuoso) to the original post below. I also added a link to our live SPARQL Demo so that anyone interested can start playing around with SPARQL and SPARQL integrated into SQL right away. Another good thing about this post is the vast amount of valuable links that it contains. To really appreciate this point simply visit my Linkblog (excuse the current layout :-) - a Tab if you come in via the front door of this Data Space (what I used to call My Weblog Home Page). &quot;Free&quot; Databases: Express vs. Open-Source RDBMSs: &quot;Open-source relational database management systems (RDBMSs) are gaining IT mindshare at a rapid pace. As an example, BusinessWeek&#39;s February 6, 2006 &#39; Taking On the Database Giants &#39; article asks &#39;Can open-source upstarts compete with Oracle, IBM, and Microsoft?&#39; and then provides the answer: &#39;It&#39;s an uphill battle, but customers are starting to look at the alternatives.&#39; There&#39;s no shortage of open-source alternatives to look at. The BusinessWeek article concentrates on MySQL, which BW says &#39;is trying to be the Ikea of the database world: cheap, needs some assembly, but has a sleek, modern design and does the job.&#39; The article also discusses Postgre[SQL] and Ingres, as well as EnterpriseDB, an Oracle clone created from PostgreSQL code*. Sun includes PostgreSQL with Solaris 10 and, as of April 6, 2006, with Solaris Express.** *Frank Batten, Jr., the investor who originally funded Red Hat, invested a reported $16 million into Great Bridge with the hope of making a business out of providing paid support to PostgreSQL users. Great Bridge stayed in business only 18 months , having missed an opportunity to sell the business to Red Hat and finding that selling $50,000-per-year support packages for an open-source database wasn&#39;t easy. As Batten concluded, &#39;We could not get customers to pay us big dollars for support contracts.&#39; Perhaps EnterpriseDB will be more successful with a choice of $5,000, $3,000, or $1,000 annual support subscriptions . **Interestingly, Oracle announced in November 2005 that Solaris 10 is &#39;its preferred development and deployment platform for most x64 architectures, including x64 (x86, 64-bit) AMD Opteron and Intel Xeon processor-based systems and Sun&#39;s UltraSPARC(R)-based systems.&#39; There is a surfeit of reviews of current MySQL, PostgreSQL andâto a lesser extentâIngres implementations. These three open-source RDBMSs come with their own or third-party management tools. These systems compete against free versions of commercial (proprietary) databases: SQL Server 2005 Express Edition (and its MSDE 2000 and 1.0 predecessors), Oracle Database 10g Express Edition, IBM DB2 Express-C, and Sybase ASE Express Edition for Linux where database size and processor count limitations aren&#39;t important. Click here for a summary of recent InfoWorld reviews of the full versions of these four databases plus MySQL, which should be valid for Express editions also. The FTPOnline Special Report article, &#39;Microsoft SQL Server Turns 17,&#39; that contains the preceding table is here (requires registration.) SQL Server 2005 Express Edition SP-1 Advanced Features SQL Server 2005 Express Edition with Advanced Features enhances SQL Server 2005 Express Edition (SQL Express or SSX) dramatically, so it deserves special treatment here. SQL Express gains full text indexing and now supports SQL Server Reporting Services (SSRS) on the local SSX instance. The SP-1 with Advanced Features setup package, which Microsoft released on April 18, 2006, installs the release version of SQL Server Management Studio Express (SSMSE) and the full version of Business Intelligence Development Studio (BIDS) for designing and editing SSRS reports. My &#39;Install SP-1 for SQL Server 2005 and Express&#39; article for FTPOnline&#39;s SQL Server Special Report provides detailed, illustrated installation instructions for and related information about the release version of SP-1. SP-1 makes SSX the most capable of all currently available Express editions of commercial RDBMSs for Windows. OpenLink Software&#39;s Virtuoso Open-Source Edition OpenLink Software announced an open-source version of it&#39;s Virtuoso Universal Server commercial DBMS on April 11, 2006. On the initial date of this post, May 2, 2006, Virtuoso Open-Source Edition (VOS) was virtually under the radar as an open-source product. According to this press release, the new edition includes: SPARQL compliant RDF Triple Store SQL-200n Object-Relational Database Engine (SQL, XML, and Free Text) Integrated BPEL Server and Enterprise Service Bus WebDAV and Native File Server Web Application Server that supports PHP, Perl, Python, ASP.NET, JSP, etc. Runtime Hosting for Microsoft .NET, Mono, and Java VOS only lacks the virtual server and replication features that are offered by the commercial edition. VOS includes a Web-based administration tool called the &quot;Virtuoso Conductor&quot; According to Kingsley Idehen&#39;s Weblog, &#39;The Virtuoso build scripts have been successfully tested on Mac OS X (Universal Binary Target), Linux, FreeBSD, and Solaris (AIX, HP-UX, and True64 UNIX will follow soon). A Windows Visual Studio project file is also in the works (ETA some time this week).&#39; InfoWorld&#39;s Jon Udell has tracked Virtuoso&#39;s progress since 2002, with an additional article in 2003 and a one-hour podcast with Kingsley Idehen on April 26, 2006. A major talking point for Virtuoso is its support for Atom 0.3 syndication and publication, Atom 1.0 syndication and (forthcoming) publication, and future support for Google&#39;s GData protocol, as mentioned in this Idehen post. Yahoo!&#39;s Jeremy Zawodny points out that the &#39;fingerprints&#39; of Adam Bosworth, Google&#39;s VP of Engineering and the primary force behind the development of Microsoft Access, &#39;are all over GData.&#39; Click here to display a list of all OakLeaf posts that mention Adam Bosworth. One application for the GData protocol is querying and updating the Google Base database independently of the Google Web client, as mentioned by Jeremy: &#39;It&#39;s not about building an easier onramp to Google Base. ... Well, it is. But, again, that&#39;s the small stuff.&#39; Click here for a list of posts about my experiences with Google Base. Watch for a future OakLeaf post on the subject as the GData APIs gain ground. Open-Source and Free Embedded Database Contenders Open-source and free embedded SQL databases are gaining importance as the number and types of mobile devices and OSs proliferate. Embedded databases usually consist of Java classes or Windows DLLs that are designed to minimize file size and memory consumption. Embedded databases avoid the installation hassles, heavy resource usage and maintenance cost associated with client/server RDBMSs that run as an operating system service. Andrew Hudson&#39;s December 2005 &#39;Open Source databases rounded up and rodeoed&#39; review for The Enquirer provides brief descriptions of one commercial and eight open source database purveyors/products: Sleepycat, MySQL, PostgreSQL, Ingres, InnoBase, Firebird, IBM Cloudscape (a.k.a, Derby), Genezzo, and Oracle. Oracle Sleepycat* isn&#39;t an SQL Database, Oracle InnoDB* is an OEM database engine that&#39;s used by MySQL, and Genezzo is a multi-user, multi-server distributed database engine written in Perl. These special-purpose databases are beyond the scope of this post. * Oracle purchased Sleepycat Software, Inc. in February 2006 and purchased Innobase OY in October 2005 . The press release states: &#39;Oracle intends to continue developing the InnoDB technology and expand our commitment to open source software.&#39; Derby is an open-source release by the Apache Software Foundation of the Cloudscape Java-based database that IBM acquired when it bought Informix in 2001. IBM offers a commercial release of Derby as IBM Cloudscape 10.1. Derby is a Java class library that has a relatively light footprint (2 MB), which make it suitable for client/server synchronization with the IBM DB2 Everyplace Sync Server in mobile applications. The IBM DB2 Everyplace Express Edition isn&#39;t open source or free*, so it doesn&#39;t qualify for this post. The same is true for the corresponding Sybase SQL Anywhere components.** * IBM DB2 Everyplace Express Edition with synchronization costs $379 per server (up to two processors) and $79 per user. DB2 Everyplace Database Edition (without DB2 synchronization) is $49 per user. (Prices are based on those when IBM announced version 8 in November 2003.) ** Sybase&#39;s iAnywhere subsidiary calls SQL Anywhere &#39;the industry&#39;s leading mobile database.&#39; A Sybase SQL Anywhere Personal DB seat license with synchronization to SQL Anywhere Server is $119; the cost without synchronization wasn&#39;t available from the Sybase Web site. Sybase SQL Anywhere and IBM DB2 Everyplace perform similar replication functions. Sun&#39;s Java DB, another commercial version of Derby, comes with the Solaris Enterprise Edition, which bundles Solaris 10, the Java Enterprise System, developer tools, desktop infrastructure and N1 management software. A recent Between the Lines blog entry by ZDNet&#39;s David Berlind waxes enthusiastic over the use of Java DB embedded in a browser to provide offline persistence. RedMonk analyst James Governor and eWeek&#39;s Lisa Vaas wrote about the use of Java DB as a local data store when Tim Bray announced Sun&#39;s Derby derivative and Francois Orsini demonstrated Java DB embedded in the Firefox browser at the ApacheCon 2005 conference. Firebird is derived from Borland&#39;s InterBase 6.0 code, the first commercial relational database management system (RDBMS) to be released as open source. Firebird has excellent support for SQL-92 and comes in three versions: Classic, SuperServer and Embedded for Windows, Linux, Solaris, HP-UX, FreeBSD and MacOS X. The embedded version has a 1.4-MB footprint. Release Candidate 1 for Firebird 2.0 became available on March 30, 2006 and is a major improvement over earlier versions. Borland continues to promote InterBase, now at version 7.5, as a small-footprint, embedded database with commercial Server and Client licenses. SQLite is a featherweight C library for an embedded database that implements most SQL-92 entry- and transitional-level requirements (some through the JDBC driver) and supports transactions within a tiny 250-KB code footprint. Wrappers support a multitude of languages and operating systems, including Windows CE, SmartPhone, Windows Mobile, and Win32. SQLite&#39;s primary SQL-92 limitations are lack of nested transactions, inability to alter a table design once committed (other than with RENAME TABLE and ADD COLUMN operations), and foreign-key constraints. SQLite provides read-only views, triggers, and 256-bit encryption of database files. A downside is the the entire database file is locked when while a transaction is in progress. SQLite uses file access permissions in lieu of GRANT and REVOKE commands. Using SQLite involves no license; its code is entirely in the public domain. The Mozilla Foundation&#39;s Unified Storage wiki says this about SQLite: &#39;SQLite will be the back end for the unified store [for Firefox]. Because it implements a SQL engine, we get querying &#39;for free&#39;, without having to invent our own query language or query execution system. Its code-size footprint is moderate (250k), but it will hopefully simplify much existing code so that the net code-size change should be smaller. It has exceptional performance, and supports concurrent access to the database. Finally, it is released into the public domain, meaning that we will have no licensing issues.&#39; Vieka Technology, Inc.&#39;s eSQL 2.11 is a port of SQLite to Windows Mobile (Pocket PC and Smartphone) and Win32, and includes development tools for Windows devices and PCs, as well as a .NET native data provider. A conventional ODBC driver also is available. eSQL for Windows (Win32) is free for personal and commercial use; eSQL for Windows Mobile requires a license for commercial (for-profit or business) use. HSQLDB isn&#39;t on most reviewers&#39; radar, which is surprising because it&#39;s the default database for OpenOffice.org (OOo) 2.0&#39;s Base suite member. HSQLDB 1.8.0.1 is an open-source (BSD license) Java dembedded database engine based on Thomas Mueller&#39;s original Hypersonic SQL Project. Using OOo&#39;s Base feature requires installing the Java 2.0 Runtime Engine (which is not open-source) or the presence of an alternative open-source engine, such as Kaffe. My prior posts about OOo Base and HSQLDB are here, here and here. The HSQLDB 1.8.0 documentation on SourceForge states the following regarding SQL-92 and later conformance: HSQLDB 1.8.0 supports the dialect of SQL defined by SQL standards 92, 99 and 2003. This means where a feature of the standard is supported, e.g. left outer join, the syntax is that specified by the standard text. Many features of SQL92 and 99 up to Advanced Level are supported and here is support for most of SQL 2003 Foundation and several optional features of this standard. However, certain features of the Standards are not supported so no claim is made for full support of any level of the standards. Other less well-known embedded databases designed for or suited to mobile deployment are Mimer SQL Mobile and VistaDB 2.1 . Neither product is open-source and require paid licensing; VistaDB requires a small up-front payment by developers but offers royalty-free distribution. Java DB, Firebird embedded, SQLite and eSQL 2.11 are contenders for lightweight PC and mobile device database projects that aren&#39;t Windows-only. SQL Server 2005 Everywhere If you&#39;re a Windows developer, SQL Server Mobile is the logical embedded database choice for mobile applications for Pocket PCs and Smartphones. Microsoft&#39;s April 19, 2006 press release delivered the news that SQL Server 2005 Mobile Editon (SQL Mobile or SSM) would gain a big brotherâSQL Server 2005 Everywhere Edition. Currently, the SSM client is licensed (at no charge) to run in production on devices with Windows CE 5.0, Windows Mobile 2003 for Pocket PC or Windows Mobile 5.0, or on PCs with Windows XP Tablet Edition only. SSM also is licensed for development purposes on PCs running Visual Studio 2005. Smart Device replication with SQL Server 2000 SP3 and later databases has been the most common application so far for SSM. By the end of 2006, Microsoft will license SSE for use on all PCs running any Win32 version or the preceding device OSs. A version of SQL Server Management Studio Express (SSMSE)âupdated to support SSEâis expected to release by the end of the year. These features will qualify SSE as the universal embedded database for Windows client and smart-device applications. For more details on SSE, read John Galloway&#39;s April 11, 2006 blog post and my &#39;SQL Server 2005 Mobile Goes Everywhere&#39; article for the FTPOnline Special Report on SQL Server.&quot; (Via OakLeaf Systems.)</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
 <p>Very detailed and insightful peek into the state of affairs re. database engines (Open &amp; Closed Source).</p>   <p>I added the missing piece regarding the &quot;Virtuoso Conductor&quot; (the Web based Admin UI for Virtuoso) to the original post below. I also added a link to our live SPARQL Demo so that anyone interested can start playing around with SPARQL and SPARQL integrated into SQL right away.</p>  <p>Another good thing about this post is the vast amount of valuable links that it contains. To really appreciate this point simply visit my Linkblog (excuse the current layout :-) - a Tab if you come in via the front door of this <a href="http://www.infoworld.com/opinions/index.html">Data Space</a> (what I used to call <a href="http://www.openlinksw.com/blog/%7Ekidehen/">My Weblog Home Page</a>).</p>   <blockquote>  <p>   <a href="http://oakleafblog.blogspot.com/2006/05/free-databases-express-vs-open-source.html">&quot;Free&quot; Databases: Express vs. Open-Source RDBMSs</a>: &quot;<span style="font-family: verdana;">Open-source relational database management systems (RDBMSs) are gaining IT mindshare at a rapid pace. As an example, <em>BusinessWeek</em>&#39;s February 6, 2006 &#39;</span>   <a href="http://www.businessweek.com/technology/content/feb2006/tc20060206_918648.htm"><span style="font-family: verdana;">Taking On the Database Giants</span>   </a><span style="font-family: verdana;">&#39; article asks &#39;Can open-source upstarts compete with Oracle, IBM, and Microsoft?&#39; and then provides the answer: &#39;It&#39;s an uphill battle, but customers are starting to look at the alternatives.&#39;</span>   <br />   <span style="font-family: Verdana;"></span>   <br />   <span style="font-family: Verdana;">There&#39;s no shortage of open-source alternatives to look at. The <em>BusinessWeek</em> article concentrates on <a href="http://www.mysql.com/">MySQL</a>, which <em>BW</em> says &#39;is trying to be the Ikea of the database world: cheap, needs some assembly, but has a sleek, modern design and does the job.&#39; The article also discusses <a href="http://www.postgresql.org/">Postgre[SQL]</a> and <a href="http://www.ingres.com/products/Prod_Ingres_2006.html">Ingres</a>, as well as <a href="http://www.enterprisedb.com/">EnterpriseDB</a>, an Oracle clone created from PostgreSQL code*. Sun includes <a href="http://www.sun.com/software/solaris/postgres.jsp">PostgreSQL with Solaris 10</a> and, as of April 6, 2006, with <a href="http://docs.sun.com/app/docs/doc/819-2183/6n4g726uc?a=view">Solaris Express</a>.**</span>   <br />   <span style="font-family: Verdana;"></span>   <br />   <span style="font-family: Verdana;"><span style="font-size: 85%;">*Frank Batten, Jr., the investor who originally funded Red Hat, invested a reported </span>    <a href="http://www.theinquirer.net/?article=28201"><span style="font-size: 85%;">$16 million into Great Bridge</span>    </a><span style="font-size: 85%;"> with the hope of making a business out of providing paid support to PostgreSQL users. </span>    <a href="http://news.com.com/2100-1001-272715.html"><span style="font-size: 85%;">Great Bridge stayed in business only 18 months</span>    </a><span style="font-size: 85%;">, having </span>    <a href="http://news.com.com/2100-1001-268915.html"><span style="font-size: 85%;">missed an opportunity to sell the business to Red Hat</span>    </a><span style="font-size: 85%;"> and finding that selling </span>    <a href="http://news.com.com/2100-1001-269729.html"><span style="font-size: 85%;">$50,000-per-year support packages</span>    </a><span style="font-size: 85%;"> for an open-source database wasn&#39;t easy. As Batten concluded, &#39;We could not get customers to pay us big dollars for support contracts.&#39; Perhaps EnterpriseDB will be more successful with a choice of </span>    <a href="http://www.enterprisedb.com/shop.do?cID=10000&pID=10001"><span style="font-size: 85%;">$5,000, $3,000, or $1,000 annual support subscriptions</span>    </a><span style="font-size: 85%;">.</span>   </span>   <br />   <span style="font-family: Verdana;"></span><span style="font-family: Verdana;"></span><span style="font-family: Verdana;"></span>   <br />   <span style="font-family: Verdana; font-size: 85%;">**Interestingly, <a href="http://www.sun.com/smi/Press/sunflash/2005-11/sunflash.20051115.4.xml">Oracle announced in November 2005</a> that Solaris 10 is &#39;its preferred development and deployment platform for most x64 architectures, including x64 (x86, 64-bit) AMD Opteron and Intel Xeon processor-based systems and Sun&#39;s UltraSPARC(R)-based systems.&#39;</span>   <br />   <br />   <span style="font-family: Verdana;">There is a surfeit of reviews of current MySQL, PostgreSQL andâto a lesser extentâIngres implementations. These three open-source RDBMSs come with their own or third-party management tools. These systems compete against free versions of commercial (proprietary) databases: <a href="http://msdn.microsoft.com/vstudio/express/sql/">SQL Server 2005 Express Edition</a> (and its MSDE 2000 and 1.0 predecessors), <a href="http://www.oracle.com/technology/products/database/xe/index.html" target="_blank">Oracle Database 10g Express Edition</a>, <a href="http://www-306.ibm.com/software/data/db2/udb/db2express/download.html" target="_blank">IBM DB2 Express-C</a>, and <a href="http://www.sybase.com/linux_promo" target="_blank">Sybase ASE Express Edition for Linux</a> where database size and processor count limitations aren&#39;t important. Click <a href="http://www.ftponline.com/special/sqlserver/rjennings-overview/table4.aspx">here</a> for a summary of recent <em>InfoWorld</em> reviews of the full versions of these four databases plus MySQL, which should be valid for Express editions also. The <a href="http://www.ftponline.com/special/sqlserver/">FTPOnline Special Report</a> article, &#39;Microsoft SQL Server Turns 17,&#39; that contains the preceding table is <a href="http://www.ftponline.com/special/sqlserver/rjennings-overview/">here</a> (requires registration.)</span>   <br />   <br />  </p>  <p>   <strong><span style="font-family: verdana;">SQL Server 2005 Express Edition SP-1 Advanced Features</span>   </strong>  </p>  <p>   <span style="font-family: Verdana;"><a href="http://www.microsoft.com/downloads/details.aspx?familyid=4C6BA9FD-319A-4887-BC75-3B02B5E48A40&displaylang=en">SQL Server 2005 Express Edition with Advanced Features</a> enhances SQL Server 2005 Express Edition (SQL Express or SSX) dramatically, so it deserves special treatment here. SQL Express gains full text indexing and now supports SQL Server Reporting Services (SSRS) on the local SSX instance. The SP-1 with Advanced Features setup package, which Microsoft released on April 18, 2006, installs the release version of SQL Server Management Studio Express (SSMSE) and the full version of Business Intelligence Development Studio (BIDS) for designing and editing SSRS reports. My &#39;<a href="http://www.ftponline.com/special/sqlserver/rjennings-sp1/">Install SP-1 for SQL Server 2005 and Express</a>&#39; article for FTPOnline&#39;s <a href="http://www.ftponline.com/special/sqlserver/">SQL Server Special Report</a> provides detailed, illustrated installation instructions for and related information about the release version of SP-1. SP-1 makes SSX the most capable of all currently available Express editions of commercial RDBMSs for Windows.</span>  </p>  <p>   <strong><span style="font-family: verdana;">OpenLink Software&#39;s Virtuoso Open-Source Edition</span>   </strong>   <br />   <span style="font-family: verdana;"></span>   <br />   <span style="font-family: verdana;"><a href="http://openlinksw.com/">OpenLink Software</a> announced an <a href="http://virtuoso.openlinksw.com/wiki/main/Main/">open-source version</a> of it&#39;s <a href="http://virtuoso.openlinksw.com/">Virtuoso Universal Server</a> commercial DBMS on April 11, 2006. On the initial date of this post, May 2, 2006, Virtuoso Open-Source Edition (VOS) was virtually under the radar as an open-source product. According to <a href="http://www.openlinksw.com/press/VOSPressRelease.htm">this press release</a>, the new edition includes:</span> <span style="font-family: Verdana;"></span>  </p>  <blockquote>   <span style="font-family: Verdana;"></span>  </blockquote> <blockquote></blockquote> <blockquote></blockquote>  <ul>   <li>     <a href="http://demo.openlinksw.com/sparql_demo/">SPARQL compliant RDF Triple Store</a> </li>   <li>SQL-200n Object-Relational Database Engine (SQL, XML, and Free Text) </li>   <li>Integrated BPEL Server and Enterprise Service Bus</li>   <li>WebDAV and Native File Server </li>   <li>Web Application Server that supports PHP, Perl, Python, ASP.NET, JSP, etc. </li>   <li>Runtime Hosting for Microsoft .NET, Mono, and Java </li>  </ul>VOS only lacks the virtual server and replication features that are offered by the commercial edition. VOS includes a Web-based administration tool called the &quot;Virtuoso Conductor&quot; According to <a href="http://www.openlinksw.com/blog/%7Ekidehen/index.vspx?page=&id=951&sid=&realm=">Kingsley Idehen&#39;s Weblog</a>, &#39;The Virtuoso build scripts have been successfully tested on Mac OS X (Universal Binary Target), Linux, FreeBSD, and Solaris (AIX, HP-UX, and True64 UNIX will follow soon). A Windows Visual Studio project file is also in the works (ETA some time this week).&#39;<br /> <br /> <em>InfoWorld</em>&#39;s Jon Udell has tracked Virtuoso&#39;s progress since <a href="http://www.infoworld.com/article/02/04/12/020415plvirtuoso_1.html">2002</a>, with an <a href="http://www.infoworld.com/article/03/03/21/12virtuoso_1.html">additional article in 2003</a> and a <a href="http://weblog.infoworld.com/udell/2006/04/28.html#a1437">one-hour podcast with Kingsley Idehen</a> on April 26, 2006. A major talking point for Virtuoso is its support for Atom 0.3 syndication and publication, Atom 1.0 syndication and (forthcoming) publication, and future support for Google&#39;s <a href="http://code.google.com/apis/gdata/overview.html">GData protocol</a>, as mentioned in <a href="http://www.openlinksw.com/blog/%7Ekidehen/index.vspx?page=&id=965">this Idehen post</a>. Yahoo!&#39;s <a href="http://jeremy.zawodny.com/blog/archives/006687.html">Jeremy Zawodny</a> points out that the &#39;fingerprints&#39; of <a href="http://oakleafblog.blogspot.com/2005/11/adam-bosworth-learning-from-web-and.html">Adam Bosworth</a>, Google&#39;s VP of Engineering and the primary force behind the development of Microsoft Access, &#39;are all over GData.&#39; Click <a href="http://search.blogger.com/?as_q=bosworth&ie=UTF-8&ui=blg&amp;bl_url=oakleafblog.blogspot.com&x=50&y=10">here</a> to display a list of all OakLeaf posts that mention Adam Bosworth.<br /> <br />One application for the GData protocol is querying and updating the Google Base database independently of the Google Web client, as mentioned by Jeremy: &#39;It&#39;s not about building an easier onramp to Google Base. ... Well, it is. But, again, that&#39;s the small stuff.&#39; Click <a href="http://search.blogger.com/?as_q=%22google+base%22&ie=UTF-8&x=50&y=9&q=%22google+base%22+blogurl:oakleafblog.blogspot.com&filter=0&ui=blg&sa=N&start=0">here</a> for a list of posts about my experiences with Google Base. Watch for a future OakLeaf post on the subject as the GData APIs gain ground.<br /> <span style="font-family: Verdana;"></span> <br />  <span style="font-family: Verdana;"><strong>Open-Source and Free Embedded Database Contenders</strong>  </span> <br /> <span style="font-family: Verdana;"></span> <br /> <span style="font-family: Verdana;">Open-source and free embedded SQL databases are gaining importance as the number and types of mobile devices and OSs proliferate. Embedded databases usually consist of Java classes or Windows DLLs that are designed to minimize file size and memory consumption. Embedded databases avoid the installation hassles, heavy resource usage and maintenance cost associated with client/server RDBMSs that run as an operating system service.</span> <br /> <br /> <span style="font-family: Verdana;">Andrew Hudson&#39;s December 2005 &#39;<a href="http://www.theinquirer.net/?article=28201">Open Source databases rounded up and rodeoed</a>&#39; review for The Enquirer provides brief descriptions of one commercial and eight open source database purveyors/products: Sleepycat, MySQL, PostgreSQL, Ingres, InnoBase, Firebird, IBM Cloudscape (a.k.a, Derby), Genezzo, and Oracle. Oracle <a href="http://www.sleepycat.com/">Sleepycat</a>* isn&#39;t an SQL Database, Oracle <a href="http://www.innodb.com/index.php">InnoDB</a>* is an OEM database engine that&#39;s used by MySQL, and <a href="http://www.genezzo.com/">Genezzo</a> is a multi-user, multi-server distributed database engine written in Perl. These special-purpose databases are beyond the scope of this post.</span> <br /> <br />  <span style="font-family: Verdana;"><span style="font-size: 85%;">* Oracle <a href="http://www.oracle.com/sleepycat/index.html">purchased Sleepycat Software, Inc. in February 2006</a> and </span>   <a href="http://www.oracle.com/innodb/index.html"><span style="font-size: 85%;">purchased Innobase OY in October 2005</span>   </a><span style="font-size: 85%;">. The press release states: &#39;Oracle intends to continue developing the InnoDB technology and expand our commitment to open source software.&#39; </span>  </span> <br /> <span style="font-family: Verdana; font-size: 85%;"></span> <br /> <span style="font-family: Verdana;">   <a href="http://db.apache.org/derby/"><strong>Derby</strong>   </a> is an open-source release by the <a href="http://www.apache.org/">Apache Software Foundation</a> of the <a href="http://www.infoworld.com/article/04/08/03/HNcloudscape_1.html">Cloudscape Java-based database that IBM acquired</a> when it bought Informix in 2001. IBM offers a commercial release of Derby as <a href="http://www-128.ibm.com/developerworks/db2/library/techarticle/dm-0408cline/">IBM Cloudscape 10.1</a>. Derby is a Java class library that has a relatively light footprint (2 MB), which make it suitable for <a href="http://www-128.ibm.com/developerworks/db2/library/techarticle/dm-0503stumpf/">client/server synchronization</a> with the IBM DB2 Everyplace Sync Server in <a href="http://www-128.ibm.com/developerworks/library/wi-cloud/">mobile applications</a>. The IBM DB2 Everyplace Express Edition isn&#39;t open source or free*, so it doesn&#39;t qualify for this post. The same is true for the corresponding Sybase SQL Anywhere components.**</span> <br /> <br /> <br />  <p>   <span style="font-family: verdana; font-size: 85%;">* IBM DB2 Everyplace Express Edition with synchronization costs $379 per server (up to two processors) and $79 per user. DB2 Everyplace Database Edition (without DB2 synchronization) is $49 per user. (Prices are based on those when </span>   <a href="http://news.earthweb.com/wireless/article.php/3107101"><span style="font-family: verdana; font-size: 85%;">IBM announced version 8</span>   </a><span style="font-family: verdana; font-size: 85%;"> in November 2003.)</span>  </p>  <p>   <span style="font-family: verdana; font-size: 85%;">** Sybase&#39;s iAnywhere subsidiary calls SQL Anywhere &#39;the industry&#39;s leading mobile database.&#39; A Sybase SQL Anywhere Personal DB seat license with synchronization to SQL Anywhere Server is $119; the cost without synchronization wasn&#39;t available from the Sybase Web site. Sybase SQL Anywhere and IBM DB2 Everyplace perform similar replication functions.</span>  </p>  <p>   <span style="font-family: Verdana;">Sun&#39;s <a href="http://developers.sun.com/prodtech/javadb/"><strong>Java DB</strong></a>, another commercial version of Derby, comes with the <a href="http://www.sun.com/software/solaris/">Solaris Enterprise Edition</a>, which bundles Solaris 10, the Java Enterprise System, developer tools, desktop infrastructure and N1 management software. A recent Between the Lines blog entry by ZDNet&#39;s David Berlind waxes enthusiastic over the use of <a href="http://blogs.zdnet.com/BTL/?p=2298">Java DB embedded in a browser</a> to provide offline persistence. RedMonk analyst <a href="http://www.redmonk.com/jgovernor/archives/001151.html">James Governor</a> and <em>eWeek</em>&#39;s <a href="http://www.eweek.com/article2/0,1895,1902407,00.asp">Lisa Vaas</a> wrote about the use of Java DB as a local data store when <a href="http://www.sauria.com/blog/2005/12/13#1440">Tim Bray announced Sun&#39;s Derby derivative</a> and <a href="http://blogs.sun.com/roller/page/FrancoisOrsini?entry=derby_apachecon_demo">Francois Orsini</a> demonstrated Java DB embedded in the Firefox browser at the ApacheCon 2005 conference.</span>   <br />   <span style="font-family: Verdana;"></span>   <br />   <span style="font-family: Verdana;">    <a href="http://www.firebirdsql.org/"><strong>Firebird</strong>    </a> is derived from Borland&#39;s InterBase 6.0 code, the first commercial relational database management system (RDBMS) to be released as open source. Firebird has excellent support for SQL-92 and comes in three versions: Classic, SuperServer and Embedded for Windows, Linux, Solaris, HP-UX, FreeBSD and MacOS X. The embedded version has a 1.4-MB footprint. Release Candidate 1 for Firebird 2.0 became available on March 30, 2006 and is a major improvement over earlier versions. <a href="http://www.borland.com/us/products/interbase/index.html">Borland continues to promote InterBase</a>, now at version 7.5, as a small-footprint, embedded database with commercial Server and Client licenses.</span>   <br />   <span style="font-family: Verdana;"></span>   <br />   <span style="font-family: Verdana;">    <a href="http://www.sqlite.org/index.html"><strong>SQLite</strong>    </a> is a featherweight C library for an embedded database that implements most SQL-92 entry- and transitional-level requirements (some through the JDBC driver) and supports transactions within a tiny 250-KB code footprint. <a href="http://www.sqlite.org/cvstrac/wiki?p=SqliteWrappers">Wrappers</a> support a multitude of languages and operating systems, including Windows CE, SmartPhone, Windows Mobile, and Win32. SQLite&#39;s primary <a href="http://www.sqlite.org/omitted.html">SQL-92 limitations</a> are lack of nested transactions, inability to alter a table design once committed (other than with RENAME TABLE and ADD COLUMN operations), and foreign-key constraints. SQLite provides read-only views, triggers, and 256-bit encryption of database files. A downside is the the entire database file is <a href="http://weblogs.asp.net/jgalloway/archive/2006/04/12/442615.aspx">locked when while a transaction is in progress</a>. SQLite uses file access permissions in lieu of GRANT and REVOKE commands. Using SQLite involves no license; its code is entirely in the public domain.</span>  </p>  <p>   <span style="font-family: Verdana; font-size: 85%;">The Mozilla Foundation&#39;s <a href="http://wiki.mozilla.org/Mozilla2:Unified_Storage">Unified Storage wiki</a> says this about SQLite: &#39;SQLite will be the back end for the unified store [for Firefox]. Because it implements a SQL engine, we get querying &#39;for free&#39;, without having to invent our own query language or query execution system. Its code-size footprint is moderate (250k), but it will hopefully simplify much existing code so that the net code-size change should be smaller. It has exceptional performance, and supports concurrent access to the database. Finally, it is released into the public domain, meaning that we will have no licensing issues.&#39;</span>  </p>  <p>   <span style="font-family: verdana;">Vieka Technology, Inc.&#39;s <a href="http://vieka.com/esql.htm"><strong>eSQL 2.11</strong></a> is a port of SQLite to Windows Mobile (Pocket PC and Smartphone) and Win32, and includes development tools for Windows devices and PCs, as well as a .NET native data provider. A conventional ODBC driver also is available. eSQL for Windows (Win32) is free for personal and commercial use; eSQL for Windows Mobile requires a license for commercial (for-profit or business) use.</span>  </p>  <p>   <span style="font-family: verdana;">    <a href="http://hsqldb.org/"><strong>HSQLDB</strong>    </a> isn&#39;t on most reviewers&#39; radar, which is surprising because it&#39;s the default database for <a href="http://www.openoffice.org/">OpenOffice.org</a> (OOo) 2.0&#39;s <a href="http://www.openoffice.org/product/base.html">Base</a> suite member. HSQLDB 1.8.0.1 is an open-source (BSD license) Java dembedded database engine based on Thomas Mueller&#39;s original Hypersonic SQL Project. Using OOo&#39;s Base feature requires installing the Java 2.0 Runtime Engine (which is not open-source) or the presence of an alternative open-source engine, such as Kaffe. My prior posts about OOo Base and HSQLDB are <a href="http://oakleafblog.blogspot.com/2005/10/openoffice-base-20-vs-microsoft-access.html">here</a>, <a href="http://oakleafblog.blogspot.com/2005/10/openoffice-base-20-vs-microsoft-access_22.html">here</a> and <a href="http://oakleafblog.blogspot.com/2005/10/openoffice-20-base-matches-microsoft.html">here</a>.</span>  </p>  <p>   <span style="font-family: verdana;">The <a href="http://hsqldb.sourceforge.net/web/hsqlDocsFrame.html">HSQLDB 1.8.0 documentation</a> on SourceForge states the following regarding SQL-92 and later conformance:</span>  </p>  <span style="font-family: verdana;">   <blockquote>    <p>     <span style="font-family: verdana;">HSQLDB 1.8.0 supports the dialect of SQL defined by SQL standards 92, 99 and 2003. This means where a feature of the standard is supported, e.g. left outer join, the syntax is that specified by the standard text. Many features of SQL92 and 99 up to Advanced Level are supported and here is support for most of SQL 2003 Foundation and several optional features of this standard. However, certain features of the Standards are not supported so no claim is made for full support of any level of the standards. </span>    </p>   </blockquote>   <span style="font-family: verdana;"><span style="font-size: 85%;">Other less well-known embedded databases designed for or suited to mobile deployment are </span>    <a href="http://www.mimer.com/leftright.asp?secId=172"><span style="font-size: 85%;">Mimer SQL Mobile</span>    </a><span style="font-size: 85%;"> and </span>    <a href="http://www.vistadb.net/"><span style="font-size: 85%;">VistaDB 2.1</span>    </a><span style="font-size: 85%;">. Neither product is open-source and require paid licensing; VistaDB requires a small up-front payment by developers but offers royalty-free distribution.</span>   </span> <br /> <br /> <span style="font-family: Verdana;">Java DB, Firebird embedded, SQLite and eSQL 2.11 are contenders for lightweight PC and mobile device database projects that aren&#39;t Windows-only.</span> <br /> <br />   <strong>    <span style="font-family: verdana;">SQL Server 2005 Everywhere<br />    </span><span style="font-family: Verdana;"></span>   </strong> <br /> <span style="font-family: verdana;">If you&#39;re a Windows developer, SQL Server Mobile is the logical embedded database choice for mobile applications for Pocket PCs and Smartphones. Microsoft&#39;s April 19, 2006 press release delivered the news that SQL Server 2005 Mobile Editon (SQL Mobile or SSM) would gain a big brotherâSQL Server 2005 Everywhere Edition. </span> <br /> <span style="font-family: verdana;"></span> <br /> <span style="font-family: verdana;">Currently, the SSM client is licensed (at no charge) to run in production on devices with Windows CE 5.0, Windows Mobile 2003 for Pocket PC or Windows Mobile 5.0, or on PCs with Windows XP Tablet Edition only. SSM also is licensed for development purposes on PCs running Visual Studio 2005.</span>   <span style="font-family: verdana;"> Smart Device replication with SQL Server 2000 SP3 and later databases has been the most common application so far for SSM.<br /> <br />   </span><span style="font-family: verdana;">By the end of 2006, Microsoft will license SSE for use on <em>all</em> PCs running any Win32 version or the preceding device OSs. A version of SQL Server Management Studio Express (SSMSE)âupdated to support SSEâis expected to release by the end of the year. These features will qualify SSE as <em>the universal embedded database</em> for Windows client and smart-device applications. </span> <br /> <br /> <span style="font-family: verdana;">For more details on SSE, read <a href="http://weblogs.asp.net/jgalloway/archive/2006/04/11/442451.aspx">John Galloway&#39;s April 11, 2006 blog post</a> and my &#39;<a href="http://www.ftponline.com/special/sqlserver/rjennings-mobile/">SQL Server 2005 Mobile Goes Everywhere</a>&#39; article for the <a href="http://www.ftponline.com/special/sqlserver/">FTPOnline Special Report on SQL Server</a>.</span><span style="font-family: verdana;"></span>&quot;  <p>(Via <a href="http://oakleafblog.blogspot.com">OakLeaf Systems</a>.)</p>  </span> </blockquote> 
]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2006-04-13#957">
  <rss:title>Prerelational DBMS vendors &amp;mdash; a quick overview</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2006-04-13T19:04:34Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Prerelational DBMS vendors â a quick overview: &quot; IBM. With BOMP and D-BOMP, IBM was probably the first company to commercialize precursors to DBMS. (BOMP stood for Bill Of Materials Planning, foreshadowing the hierarchical architecture of IMS.) Out of those grew DL/1 and IMS, IBMâs flagship hierarchical DBMS, and the worldâs first dominant DBMS product(s). Of course, IBM also innovated relational DBMS, via the research of E. F. âTedâ Codd, then some prototype products, and eventual the mainframe version of DB2. To this day DB2 on the mainframe remains one of the worldâs major DBMS, as does the separate but related product of DB2 for âopen systems.â Cincom. In the 1970s, Cincom was probably the most successful independent software product company. Its flagship product was Total, a shallow-network DBMS that was a little more general than the strictly hierarchical IMS. Whatâs more, Total ran on almost any brand of computer hardware. Cincom remains independent and privately held to this day. Cullinane/Cullinet. Charlie Bachman innovated a true network DBMS at Honeywell, but it didnât turn into a serious product at that time. B. F. Goodrich, however, ran a version. This is what John Cullinaneâs company bought and turned into IDMS, which at least on the mainframe supplanted Total as the technical, mind share, and probably revenue market leader. Cullinet (as it was then called) ran into technical difficulties, however, losing ground to the more flexible index-based DBMS. It was eventually sold to Computer Associates. A lot of software industry leaders cut their teeth at Cullinet, notably Andrew âFlipâ Filipowski, later the colorful founder of Platinum. Other alumni include Renato âRonâ Zambonini, Dave Litwack, Dave Ireland, and the original PowerBuilder development team. John Landry and Bob Weiler ran the firm for a while toward the end, but they donât really count; rather, theyâre the most prominent alumni of applications pioneer McCormack &amp; Dodge. Note: Index-based is a term I used in and probably coined for my first report in 1982, comprising both inverted-list and relational RDBMS, as opposed to the link(ed)-list hierarchical and network products such as IMS, Total, and IDBMS. The companies that beat Cullinet were long-time rival Software AG, and then especially Applied Data Research; then all three of those independents were blown out by IBMâs DB2. And then the whole mainframe DBMS business was in turn obsoleted by the rise of UNIX â¦ but Iâm getting ahead of my story. Software AG. Like Cincom, Germany-based Software AG is a 1970s DBMS pioneer that has always remained independent and privately held. Sort of. Twice, Software AG of North America was spun off as a separate, eventually public company. Software AGâs flagship DBMS was the inverted list product ADABAS. SAPâs MaxDB was also owned by Software AG for a while (and seemingly by every other significant German computer company as well â or more precisely, by Nixdorf where it was developed, and by Siemens after it bought Nixdorf). I actually visited Software AG in Darmstadt once. Founder Peter Schnell and key techie Peter Page were both gracious hosts. Schnell was proud of their new building, and especially of the hexagon-based wooden dual desks heâd personally designed. General analytic rule â when the CEO is focused on the dÃ©cor, this is not a good sign for the companyâs near-term prospects. (I call this having an âedifice complex.â) Applied Data Research (ADR). ADR is often credited as being the first independent software company, having introduced products in the late 1960s and prevailed in antitrust struggles against IBM to allow the business to survive. Basically, it sold programmer productivity tools. This led it to acquire Datacom/DB, an inverted-list DBMS developed in the Dallas area. In the early 1980s, Datacom/DB began to boom, and was on a track to surpass both IDMS and ADABAS in market share until DB2 showed up and blew them all away. ADR was particularly aided by its fourth-generation language (4GL) IDEAL, which was an excellent product notwithstanding the famous State of New Jersey fiasco. (As John Landry said to me about that one, â4GLs are powerful tools. In particular, they allow you to write bad programs really quickly.â) ADR was an underappreciated powerhouse, boasting all of the Fortune 100 as customers way back in the early 1980s (yes, even archrival IBM). When the DBMS business stalled, however, ADR was quickly sold â first to Ameritech (the Illinois-based Baby Bell company), and soon thereafter to Computer Associates. Computer Corporation of America (CCA). CCAâs DBMS Model 204 may have been the best of the prerelational products, boasting an inverted-list architecture akin to that of ADABAS and Datacom/DB. The company was also interesting in that it was first and foremost a government contract research shop, and hence did all sorts of interesting prototype work that sadly never got commercialized. In about 1983 it became that the company wasnât going anywhere, and it put itself up for sale. I was personally instrumental in that decision. Our investment banker pretended he was considering taking CCA public. CCA President Jim Rothnie showed us revenue projections. I asked how he had gotten them. He replied that he had taken the market size projection 5 years out, assumed 10%, and drawn a âplausible curve.â However, I quickly got Socratic with him. âHow many salesmen do you have?â âHow much revenue does the average experienced salesman produce?â âHow many experienced salesmen do you expect to have next year?â âHow high do you think their average productivity can grow?â âLet us multiply.â (Yes, I really said that. I can be a jerk. And anyway Jim was the sort of analytic guy one can say that to without giving serious offense.) CCA was sold to a Canadian insurance company whose name Iâve now forgotten. Eventually, it was spun back out (perhaps after some intermediate changes of ownership), and resurfaced as primarily a data integration company, called Praxis. In the real old days (mid 1970s, perhaps), Model 204 was resold by Informatics (later Informatics General, later the hostile takeover that became the guts of Sterling Software, which like so many other companies was eventually absorbed into Computer Associates). I know this because Richard Currier used to sell the product when he worked at Informatics. That probably makes Richard and me about the only two people who still remember the fact. Hmm. I forgot to mention Intelâs System 2000. Well, truth be told it was a dying product even back when I first became an analyst in 1981, and I recall nothing about it, except Gene Lowenthalâs observation that Intel had had trouble selling chips and DBMS through the same salesforce. I think Al Sisto, who I probably met when he was head of sales at RTI (Relational Technology, Inc. â later called Ingres), came out of that business, but Iâm not 100% sure. I remember Pete Tierney from that RTI management team more clearly anyway, although thatâs mainly because we stayed in touch at subsequent companies over the years.&quot; (Via Software Memories.)</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>
<a href="http://www.softwarememories.com/2006/02/09/prerelational-dbms-vendors-a-quick-overview/">Prerelational DBMS vendors â a quick overview</a>: &quot;</p>
<p>
<strong>IBM. </strong> With BOMP and D-BOMP, IBM was probably the first company to commercialize precursors to DBMS.  (BOMP stood for Bill Of Materials Planning, foreshadowing the hierarchical architecture of IMS.)  Out of those grew DL/1 and IMS, IBMâs flagship hierarchical DBMS, and the worldâs first dominant DBMS product(s).  Of course, IBM also innovated relational DBMS, via the research of E. F. âTedâ Codd, then some prototype products, and eventual the mainframe version of DB2.  To this day DB2 on the mainframe remains one of the worldâs major DBMS, as does the separate but related product of DB2 for âopen systems.â</p>
	<p>
<strong>Cincom. </strong> In the 1970s, Cincom was probably the most successful independent software product company.  Its flagship product was Total, a shallow-network DBMS that was a little more general than the strictly hierarchical IMS.  Whatâs more, Total ran on almost any brand of computer hardware.  Cincom remains independent and privately held to this day.</p>
	<p>
<strong>Cullinane/Cullinet.</strong>  Charlie Bachman innovated a true network DBMS at Honeywell, but it didnât turn into a serious product at that time.  B. F. Goodrich, however, ran a version.  This is what John Cullinaneâs company bought and turned into IDMS, which at least on the mainframe supplanted Total as the technical, mind share, and probably revenue market leader. Cullinet (as it was then called) ran into technical difficulties, however, losing ground to the more flexible index-based DBMS.  It was eventually sold to Computer Associates.   </p>
	<p>A lot of software industry leaders cut their teeth at Cullinet, notably Andrew âFlipâ Filipowski, later the colorful founder of Platinum.  Other alumni include Renato âRonâ Zambonini, Dave Litwack, Dave Ireland, and the original PowerBuilder development team.  John Landry and Bob Weiler ran the firm for a while toward the end, but they donât really count; rather, theyâre the most prominent alumni of applications pioneer McCormack &amp; Dodge.</p>
	<p>
<strong>Note:</strong>  <em>Index-based</em> is a term I used in and probably coined for my first report in 1982, comprising both inverted-list and relational RDBMS, as opposed to the link(ed)-list hierarchical and network products such as IMS, Total, and IDBMS.  The companies that beat Cullinet were long-time rival Software AG, and then especially Applied Data Research; then all three of those independents were blown out by IBMâs DB2.  And then the whole mainframe DBMS business was in turn obsoleted by the rise of UNIX â¦ but Iâm getting ahead of my story.</p>
	<p>
<strong>Software AG.</strong>   Like Cincom, Germany-based Software AG is a 1970s DBMS pioneer that has always remained independent and privately held.  Sort of.  Twice, Software AG of North America was spun off as a separate, eventually public company.  Software AGâs flagship DBMS was the inverted list product ADABAS.  SAPâs MaxDB was also owned by Software AG for a while (and seemingly by every other significant German computer company as well â or more precisely, by Nixdorf where it was developed, and by Siemens after it bought Nixdorf).</p>
	<p>I actually visited Software AG in Darmstadt once.  Founder Peter Schnell and key techie Peter Page were both gracious hosts.  Schnell was proud of their new building, and especially of the hexagon-based wooden dual desks heâd personally designed.    General analytic rule â when the CEO is focused on the dÃ©cor, this is not a good sign for the companyâs near-term prospects.  (I call this having an âedifice complex.â)</p>
	<p>
<strong>Applied Data Research (ADR). </strong> ADR is often credited as being the first independent software company, having introduced products in the late 1960s and prevailed in antitrust struggles against IBM to allow the business to survive.  Basically, it sold programmer productivity tools.  This led it to acquire Datacom/DB, an inverted-list DBMS developed in the Dallas area.   In the early 1980s, Datacom/DB began to boom, and was on a track to surpass both IDMS and ADABAS in market share until DB2 showed up and blew them all away.  ADR was particularly aided by its fourth-generation language (4GL) IDEAL, which was an excellent product notwithstanding the famous State of New Jersey fiasco.  (As John Landry said to me about that one, â4GLs are powerful tools.  In particular, they allow you to write bad programs really quickly.â)</p>
	<p>ADR was an underappreciated powerhouse, boasting all of the Fortune 100 as customers way back in the early 1980s (yes, even archrival IBM).  When the DBMS business stalled, however, ADR was quickly sold â first to Ameritech (the Illinois-based Baby Bell company), and soon thereafter to Computer Associates.</p>
	<p>
<strong>Computer Corporation of America (CCA). </strong> CCAâs DBMS Model 204 may have been the best of the prerelational products, boasting an inverted-list architecture akin to that of ADABAS and Datacom/DB.  The company was also interesting in that it was first and foremost a government contract research shop, and hence did all sorts of interesting prototype work that sadly never got commercialized.  In about 1983 it became that the company wasnât going anywhere, and it put itself up for sale.  </p>
	<p>I was personally instrumental in that decision.  Our investment banker pretended he was considering taking CCA public.  CCA President Jim Rothnie showed us revenue projections.  I asked how he had gotten them.  He replied that he had taken the market size projection 5 years out, assumed 10%, and drawn a âplausible curve.â  However, I quickly got Socratic with him.  âHow many salesmen do you have?â âHow much revenue does the average experienced salesman produce?â  âHow many experienced salesmen do you expect to have next year?â âHow high do you think their average productivity can grow?â  âLet us multiply.â  (Yes, I really said that.  I can be a jerk.  And anyway Jim was the sort of analytic guy one can say that to without giving serious offense.)</p>
	<p>CCA was sold to a Canadian insurance company whose name Iâve now forgotten.  Eventually, it was spun back out (perhaps after some intermediate changes of ownership), and resurfaced as primarily a data integration company, called Praxis.</p>
	<p>In the real old days (mid 1970s, perhaps), Model 204 was resold by Informatics (later Informatics General, later the hostile takeover that became the guts of Sterling Software, which like so many other companies was eventually absorbed into Computer Associates).  I know this because Richard Currier used to sell the product when he worked at Informatics.  That probably makes Richard and me about the only two people who still remember the fact.</p>
	<p>Hmm.  I forgot to mention <strong>Intelâs System 2000. </strong> Well, truth be told it was a dying product even back when I first became an analyst in 1981, and I recall nothing about it, except Gene Lowenthalâs observation that Intel had had trouble selling chips and DBMS through the same salesforce.  I think Al Sisto, who I probably met when he was head of sales at RTI (Relational Technology, Inc. â later called Ingres), came out of that business, but Iâm not 100% sure.  I remember Pete Tierney from that RTI management team more clearly anyway, although thatâs mainly because we stayed in touch at subsequent companies over the years.</p>&quot;

<p>(Via <a href="http://www.softwarememories.com">Software Memories</a>.)</p>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2006-04-11#951">
  <rss:title>Virtuoso is Officially Open Source!</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2006-04-11T18:01:44Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">I am pleased to unveil (officially) the fact that Virtuoso is now available in Open Source form. What Is Virtuoso? A powerful next generation server product that implements otherwise distinct server functionality within a single server product. Think of Virtuoso as the server software analog of a dual core processor where each core represents a traditional server functionality realm. Where did it come from? The Virtuoso History page tells the whole story. What Functionality Does It Provide? The following: 1. Object-Relational DBMS Engine (ORDBMS like PostgreSQL and DBMS engine like MySQL) 2. XML Data Management (with support for XQuery, XPath, XSLT, and XML Schema) 3. RDF Triple Store (or Database) that supports SPARQL (Query Language, Transport Protocol, and XML Results Serialization format) 4. Service Oriented Architecture (it combines a BPEL Engine with an ESB) 5. Web Application Server (supports HTTP/WebDAV) 6. NNTP compliant Discussion Server And more. (see: Virtuoso Web Site) 90% of the aforementioned functionality has been available in Virtuoso since 2000 with the RDF Triple Store being the only 2006 item. What Platforms are Supported The Virtuoso build scripts have been successfully tested on Mac OS X (Universal Binary Target), Linux, FreeBSD, and Solaris (AIX, HP-UX, and True64 UNIX will follow soon). A Windows Visual Studio project file is also in the works (ETA some time this week). Why Open Source? Simple, there is no value in a product of this magnitude remaining the &quot;best kept secret&quot;. That status works well for our competitors, but absolutely works against the legions of new generation developers, systems integrators, and knowledge workers that need to be aware of what is actually achievable today with the right server architecture. What Open Source License is it under? GPL version 2. What&#39;s the business model? Dual licensing. The Open Source version of Virtuoso includes all of the functionality listed above. While the Virtual Database (distributed heterogeneous join engine) and Replication Engine (across heterogeneous data sources) functionality will only be available in the commercial version. Where is the Project Hosted? On SourceForge. Is there a product Blog? Of course! Up until this point, the Virtuoso Product Blog has been a covert live demonstration of some aspects of Virtuoso (Content Management). My Personal Blog and the Virtuoso Product Blog are actual Virtuoso instances, and have been so since I started blogging in 2003. Is There a product Wiki? Sure! The Virtuoso Product Wiki is also an instance of Virtuoso demonstrating another aspect of the Content Management prowess of Virtuoso. What About Online Documentation? Yep! Virtuoso Online Documentation is hosted via yet another Virtuoso instance. This particular instance also attempts to demonstrate Free Text search combined with the ability to repurpose well formed content in a myriad of forms (Atom, RSS, RDF, OPML, and OCS). What about Tutorials and Demos? The Virtuoso Online Tutorial Site has operated as a live demonstration and tutorial portal for a numbers of years. During the same timeframe (circa. 2001) we also assembled a few Screencast style demos (their look feel certainly show their age; updates are in the works). BTW - We have also updated the Virtuoso FAQ and also released a number of missing Virtuoso White Papers (amongst many long overdue action items).</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<p>I am pleased to unveil (officially) the fact that <a href="http://www.prnewswire.com/cgi-bin/stories.pl?ACCT=104&STORY=/www/story/04-11-2006/0004338324&EDATE=">Virtuoso is now available in Open Source form</a>.</p> <p></p> <h4>What Is Virtuoso?</h4> <p>A powerful next generation server product that implements otherwise distinct server functionality within a single server product. Think of Virtuoso as the server software analog of a dual core processor where each core represents a traditional server functionality realm.</p> <p></p> <h4>Where did it come from?</h4> <p>The <a href="http://virtuoso.openlinksw.com/wiki/main/Main/VOSHistory">Virtuoso History page</a> tells the whole story.</p> <p></p> <h4>What Functionality Does It Provide?</h4>  The following: <ul> 1. Object-Relational DBMS Engine (ORDBMS like PostgreSQL and DBMS engine like MySQL) </ul> <ul> 2. XML Data Management (with support for XQuery, XPath, XSLT, and XML Schema) </ul> <ul> 3. RDF Triple Store (or Database) that supports SPARQL (Query Language, Transport Protocol, and XML Results Serialization format) </ul> <ul> 4. Service Oriented Architecture (it combines a BPEL Engine with an ESB) </ul> <ul> 5. Web Application Server (supports HTTP/WebDAV) </ul> <ul> 6. NNTP compliant Discussion Server </ul>  And more. (see: <a href="http://virtuoso.openlinksw.com">Virtuoso Web Site</a>) <p> 90% of the aforementioned functionality has been available in Virtuoso since 2000 with the RDF Triple Store being the only 2006 item.</p> <p></p> <h4>What Platforms are Supported</h4> <p> The Virtuoso build scripts have been successfully tested on Mac OS X (Universal Binary Target), Linux, FreeBSD, and Solaris (AIX, HP-UX, and True64 UNIX will follow soon). A Windows Visual Studio project file is also in the works (ETA some time this week).</p> <p></p> <h4>Why Open Source?</h4> <p>Simple, there is no value in a product of this magnitude remaining the &quot;best kept secret&quot;. That status works well for our competitors, but absolutely works against the legions of new generation developers, systems integrators, and knowledge workers that need to be aware of what is actually achievable today with the right server architecture.</p> <p></p> <h4>What Open Source License is it under?</h4> <p>GPL version 2.</p> <p></p> <h4>What&#39;s the business model?</h4> <p>Dual licensing.</p> <p>The Open Source version of Virtuoso includes all of the functionality listed above. While the Virtual Database (distributed heterogeneous join engine) and Replication Engine (across heterogeneous data sources) functionality will only be available in the commercial version. </p> <p></p> <h4>Where is the Project Hosted?</h4> <p>On <a href="http://sourceforge.net/projects/virtuoso">SourceForge.</a> </p> <p></p> <h4>Is there a product Blog?</h4> <p>Of course! </p> <p>Up until this point, the <a href="http://virtuoso.openlinksw.com/blog/">Virtuoso Product Blog</a> has been a covert live demonstration of some aspects of Virtuoso (Content Management). My Personal Blog and the Virtuoso Product Blog are actual Virtuoso instances, and have been so since I started blogging in 2003.</p> <p>Is There a product Wiki?</p> <p>Sure! <a href="http://virtuoso.openlinksw.com/wiki/main/">The Virtuoso Product Wiki</a> is also an instance of Virtuoso demonstrating another aspect of the Content Management prowess of Virtuoso.</p> <p></p> <h4>What About Online Documentation?</h4> <p>Yep! <a href="http://docs.openlinksw.com/virtuoso/">Virtuoso Online Documentation</a> is hosted via yet another Virtuoso instance. This particular instance also attempts to demonstrate Free Text search combined with the ability to repurpose well formed content in a myriad of forms (Atom, RSS, RDF, OPML, and OCS).</p> <p></p> <h4>What about Tutorials and Demos?</h4> <p>The <a href="http://demo.openlinksw.com/tutorial/">Virtuoso Online Tutorial</a> Site has operated as a live demonstration and tutorial portal for a numbers of years. During the same timeframe (circa. 2001) we also assembled a few Screencast style demos (their look feel certainly show their age; updates are in the works).</p> <p>BTW - We have also updated the <a href="http://virtuoso.openlinksw.com/FAQ/">Virtuoso FAQ</a> and also released a number of missing <a href="http://virtuoso.openlinksw.com/Whitepapers/">Virtuoso White Papers</a> (amongst many long overdue action items).</p>
]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2005-10-27#885">
  <rss:title>You want disruptive? Here&#39;s disruptive...</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2005-10-27T23:34:25Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">&quot;...Also today I came across the latest project of a man who wants to tear down Tim Berners-Lee&#39;s World Wide Web and replace it with his own vision. It used to be known as Xanadu, but has since morphed into Transliterature, A Humanist Design. I am of course referring to Ted Nelson, who invented the term &#39;hypertext&#39; in 1965 and is generally regarded as a computing pioneer.Ted Nelson recently wrote an essay about &#39;Indirect Documents&#39;, which got Slashdotted today. In the essay Nelson outlines why (in his opinion) the Xanadu project failed and he explains his new vision for Transliterature. He takes a number of potshots at Tim Berners-Lee&#39;s WWW on the way, e.g.:&#39;Why don&#39;t I like the web? I hate its flapping and screeching and emphasis on appearance; its paper-simulation rectangles of Valuable Real Estate, artifically created by the NCSA browser, now hired out to advertisers; its hierarchies exposed and imposed; its untyped one-way links only from inside the document. (The one-way links hidden under text were a regrettable simplification of hypertext which I assented to in &#39;68 on the HES project. But that&#39;s another story.) Only trivial links are possible; there is nothing to support careful annotation and study; and, of course, there is no transclusion.&#39;Ted Nelson is certainly an original and I&#39;m glad he&#39;s still around to throw spanners in the works. I&#39;ve written about him before and I&#39;m sure I will again, Web 2.0 or not.&quot; (Excerpted From: Read/Write Web.)My thoughts on the commentary above:There is nothing fundamentally incompatible between Ted Nelson&#39;s pursuits and future incarnation&#39;s of the Web. None whatsoever -- we are simply working our way through an process. The process in question is what I call &quot;standards driven ubiquity&quot; (becoming de facto at Internet Speed). Remember Sun&#39;s &quot;The Network is the Computer&quot; vision? Well, without a &quot;Computer&quot; in mind-space you can&#39;t think in terms of &quot;Operating Systems&quot;. Thats all changing, because today we are gradually beginning to accept the imminent reality that &quot;The Internet is the Operating System&quot; and not Windows/UNIX/Mac OS X/Others. Ahem! And after the Operating System what comes next? I think a set of Application Programming Interfaces (APIs), and I think we know what that is (in all of its controversial glory), the very thing we refer to as Web 2.0 (the APIs for the Internet Operating System). Note: In addition to the Computer, Operating System, and Application Programming Interfaces, we also have those frequently misunderstood and under-appreciated workhorses called &quot;Databases&quot; in place (but we still call them Web Sites for now). And by the way, &quot;Internet Filesystem&quot; has been there forever, but for some reason we can&#39;t see WebDAV in all its current and future glory (that will change very soon also!).Ted and TBL are cool with each (whether they know it or not)! I see no mutual exclusivity in their collective visions (IMHO) :-)</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[
<blockquote><p>&quot;...Also today I came across the latest project of a man who wants to tear down <a href="http://www.w3.org/People/Berners-Lee/">Tim Berners-Lee</a>&#39;s World Wide Web and replace it with his own vision. It used to be known as Xanadu, but has since morphed into  <a href="http://transliterature.org/">Transliterature, A Humanist Design</a>. I am of course referring to <a href="http://en.wikipedia.org/wiki/Ted_Nelson">Ted Nelson</a>, who invented the term &#39;hypertext&#39; in 1965 and is generally regarded as a computing pioneer.</p><p>Ted Nelson recently <a href="http://hyperland.com/trollout.txt">wrote an essay</a> about &#39;Indirect Documents&#39;, which got <a href="http://it.slashdot.org/article.pl?sid=05/10/24/1054214&tid=230&tid=218">Slashdotted</a> today. In the essay Nelson outlines why (in his opinion) the Xanadu project failed and he explains his new vision for Transliterature. He takes a number of potshots at Tim Berners-Lee&#39;s WWW on the way, e.g.:</p><blockquote><p>&#39;Why don&#39;t I like the web? I hate its flapping and screeching and emphasis on appearance; its paper-simulation rectangles of Valuable Real Estate, artifically created by the NCSA browser, now hired out to advertisers; its hierarchies exposed and imposed; its untyped one-way links only from inside the document. (The one-way links hidden under text were a regrettable simplification of hypertext which I assented to in &#39;68 on the HES project. But that&#39;s another story.) Only trivial links are possible; there is nothing to support careful annotation and study; and, of course, there is no transclusion.&#39;</p></blockquote><p>Ted Nelson is certainly an original and I&#39;m glad he&#39;s still around to throw spanners in the works. <a href="http://www.readwriteweb.com/archives/001721.php">I&#39;ve written about him before</a> and I&#39;m sure I will again, Web 2.0 or not.</p><img src="http://feeds.feedburner.com/readwriteweb?g=272" />&quot;  <p>(Excerpted From: <a href="http://www.readwriteweb.com/">Read/Write Web</a>.)</p></blockquote><p>My thoughts on the commentary above:</p><p>There is nothing fundamentally incompatible between Ted Nelson&#39;s pursuits and future incarnation&#39;s of the Web. None whatsoever -- we are simply working our way through an process. The process in question is what I call &quot;standards driven ubiquity&quot; (becoming de facto at Internet Speed). Remember Sun&#39;s &quot;The Network is the Computer&quot; vision? Well, without a &quot;Computer&quot; in mind-space you can&#39;t think in terms of &quot;Operating Systems&quot;. Thats all changing, because today we are gradually beginning to accept the imminent reality that &quot;The Internet is the Operating System&quot; and not Windows/UNIX/Mac OS X/Others. Ahem! And after the Operating System what comes next? I think a set of Application Programming Interfaces (APIs), and I think we know what that is (in all of its <a href="http://en.wikipedia.org/wiki/Web_2.0">controversial glory</a>), the very thing we refer to as <a href="http://www.openlinksw.com/weblog/public/search.vspx?blogid=127&q=#39web%202.0#39&type=text&output=html">Web 2.0</a> (the APIs for the Internet Operating System).</p><p> Note: In addition to the Computer, Operating System, and Application Programming Interfaces, we also have those frequently misunderstood and under-appreciated workhorses called &quot;Databases&quot; in place (but we still call them Web Sites for now). And by the way, &quot;Internet Filesystem&quot; has been there forever, but for some reason we can&#39;t see <a href="http://www.webdav.org/">WebDAV</a> in all its current and future glory (that will change very soon also!).</p><p>Ted and TBL are cool with each (whether they know it or not)! I see no mutual exclusivity in their collective visions (IMHO) :-) </p>
]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2005-05-01#828">
  <rss:title>Point, Counterpoint: Mac OS X Is Great for Fortysomething Unix Hackers</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2005-05-01T14:31:01Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">There has been a lot of well deserved attention going the way of &quot;Mac OS X Tiger&quot;. A the current time, a lot of this attention tends to focus on the consumer constituency comprised of Aunt Milly et al, designers, and new media aficionados. The Daring Fireball posts an article titled: Point, Counterpoint: Mac OS X Is Great for Fortysomething Unix Hackers . This particular post applies to OpenLink Software in general across a myriad of fronts, especially the essence of this excerpt: On the surface, Grahamâs piece seems like a nice pat on the back to the Mac platform. But thereâs an implication in his piece that the worldâs most prodigiously talented programmers are only now switching (or switching back) to the Mac, when in fact some of them have been here all along. GUI programming is hard, and for GUI programmers, the Mac has always been, in Brent Simmonsâs words, âThe Showâ. I.e. the idea that by the mid-â90s the Mac user base had been whittled down to âgraphic designers and grandmasâ is demonstrably false â someone must have been writing the software the designers and grandmas were using, no? â but I donât think itâs worth pressing the point, because I suspect it wasnât really what Graham meant to imply. And the main thrust of his point is true: there is a certain class of hackers â your prototypical Unix nerds â who not only werenât using Macs a decade ago, but whose antipathy toward Macs was downright hostile. And it is remarkable that these hackers are now among Mac OS Xâs strongest adherents. Itâs another sign of Mac OS Xâs dual nature: from the perspective of your typical user (and particularly long-time Mac users), it is the Mac OS with a modern Unix architecture encapsulated under the hood; from the perspective of the hackers Graham writes of, it is Unix with a vastly superior GUI. Read on....</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[There has been a lot of well deserved attention going the way of "Mac OS X Tiger". A&nbsp;the current time, a lot of&nbsp;this attention tends to focus on the consumer constituency comprised of Aunt Milly et al, designers, and new media aficionados. The <a href="http://daringfireball.net/">Daring Fireball</a>&nbsp;posts an article titled:&nbsp;<a href="http://daringfireball.net/2005/04/point_counterpoint">Point, Counterpoint: Mac OS X Is Great for Fortysomething Unix Hackers</a> . This particular&nbsp;post applies to OpenLink Software in general&nbsp;across a myriad of fronts, especially the essence of this excerpt:
<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
<p>On the surface, Grahamâs piece seems like a nice pat on the back to the Mac platform. But thereâs an implication in his piece that the worldâs most prodigiously talented programmers are only now switching (or switching back) to the Mac, when in fact some of them have been here all along. GUI programming is hard, and for GUI programmers, the Mac has always been, <a href="http://www.shapeofdays.com/2005/01/interview_with_.html">in Brent Simmonsâs words</a>, âThe Showâ.</p>
<p>I.e. the idea that by the mid-â90s the Mac user base had been whittled down to âgraphic designers and grandmasâ is demonstrably false â someone must have been writing the software the designers and grandmas were using, no? â but I donât think itâs worth pressing the point, because I suspect it wasnât really what Graham meant to imply. And the main thrust of his point is true: there is a certain class of hackers â your prototypical Unix nerds â who not only werenât using Macs a decade ago, but whose antipathy toward Macs was downright hostile. And it is remarkable that these hackers are now among Mac OS Xâs strongest adherents.</p>
<p>Itâs another sign of Mac OS Xâs dual nature: from the perspective of your typical user (and particularly long-time Mac users), it is the Mac OS with a modern Unix architecture encapsulated under the hood; from the perspective of the hackers Graham writes of, it is Unix with a vastly superior GUI.</p></blockquote>
<p dir="ltr"><a href="http://daringfireball.net/2005/04/point_counterpoint">Read on....</a></p>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2005-04-21#793">
  <rss:title>Mac OS X and its potential impact on Windows</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2005-04-21T20:25:16Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">We are at an interesting crossroads in the computer industry (IMHO) . Apple is about to unleash Tiger (ETA: one week from now), and this operating system release could end up being the crucial round of the titanic battle between Apple and Microsoft. The battle which starts at the Operating System level reminds me of the &quot;Rumble In The Jungle&quot; (circa. 1974, Kinshasa, Zaire); Apple in the role of Ali (aka &quot;The Greatest&quot; who was the overwhelming underdog at time) and Microsoft in the role of George Foreman (who at the time was logically invincible). The shakesperian tale of Macbeth also comes to mind as depicted in the excerpt below: &quot;.... Macbeth goes to visit the witches in their cavern. There, they show him a sequence of demons and spirits who present him with further prophecies: he must beware of Macduff, a Scottish nobleman who opposed Macbeth&#39;s accession to the throne; he is incapable of being harmed by any man born of woman; and he will be safe until Birnam Wood comes to Dunsinane Castle. &quot; Having used all the major operating systems on a serious basis for a number of years in a variety of modes; user, developer, and administrator. I have always felt that a RISC based UNIX operating system (of BSD genealogical branch extraction), if somehow combined with a user interface that is superior to Windows, would ultimately unravel the Windows Desktop Monopoly. That operating system exists today in the form of Mac OS X (its lastest Tiger release simply kicks the differential up a notch). Back to the Macbeth correlation: &quot;Birnam Woods coming to Dunsinane&quot; is the metaphoric equivalent of desktop users and first time computer users being forced (by the scourge of virus and spyware) to revaluate Windows as the only choice for productive desktop computing. What would you recommend to &quot;Aunt Milly&quot; when she tells you she wants to get on the Internet? Especially if &quot;Aunt Milly&quot; isn&#39;t living with you? &quot;Man not born of a woman&quot; is no different to saying: UNIX with a superior user interface to Windows! I don&#39;t think you need me to tell who play the characters of Macbeth and Macduff in this drama :-) The Windows security vulnerabilities quagmire (google juice on this phrase is currently 6,620 pages) has basically created an inflection of monumental proportions adversely affecting Windows and creating great visibility and evaluation building opportunities for Mac OS X (&quot;once users experience a Mac they don&#39;t come back to Windows!&quot;). Paul Murphy of cio-today.com has also written a great article sheds light on the often overlooked hardware aspect to the security problem for Windows Here is a poignant excerpt: Software and Hardware Vulnerabilities At present, attacks on Microsoft&#39;s Windows products are generally drawn from a different population of possible attacks than those on Unix variants such as BSD, Linux and Solaris. From a practical perspective, the key difference is that attacks on Wintel tend to have two parts: A software vulnerability is exploited to give a remote attacker access to the x86 hardware and that access is then used to gain control of the machine. In contrast, attacks on Unix generally require some form of initial legal access to the machine and focus on finding software ways to upgrade priveleges illegally. Consider, for example, CAN-2004-1134 in the NIST vulnerabilities database: Summary: Buffer overflow in the Microsoft W3Who ISAPI (w3who.dll) allows remote attackers to cause a denial of service and possibly execute arbitrary code via a long query string. Published Before: 1/10/2005 Severity: High The vulnerability exists in Microsoft&#39;s code, but the exploit depends on the rigid stack-order execution and limited page protection inherent in the x86 architecture. If Windows ran on Risc, that vulnerability would still exist, but it would be a non-issue because the exploit opportunity would be more theoretical than practical. Linux and open-source applications are thought to have far fewer software vulnerabilities than Microsoft&#39;s products, but Linux on Intel (Nasdaq: INTC - news) is susceptible to the same kind of attacks as those now predominantly affecting Wintel users. For real long-term security improvements, therefore, the right answer is to look at Linux, or any other Unix, on non x86 hardware. One such option is provided by Apple&#39;s (Nasdaq: AAPL - news) BSD-based products on the PowerPC-derived G4 and G5 CPUs. Linus Torvalds, for example, apparently now runs Linux on a Mac G5 and there are several Linux distributions for this hardware -- all of which are immune to the typical x86-oriented exploit. This may even been the nullifier of that age old argument about porting Mac OS X to the x86 in order to broaden its adoption potential? Mac OS X is certainly a breath of fresh air for anyone who needs to simply get stuff done with their desktops and notebooks.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p dir="ltr">We are at an interesting crossroads in the computer industry (IMHO) . Apple is about to unleash <a href="http://www.apple.com/macosx/">Tiger</a> (ETA: one week from now), and this operating system release could end up being the crucial round of the titanic battle between Apple and Microsoft. The battle which starts&nbsp;at the Operating System level reminds me of the&nbsp;"<a href="http://home.sandiego.edu/~murphy2/jungle.html">Rumble In The Jungle</a>" (circa. 1974, <a href="http://www.answers.com/main/ntquery?s=Kinshasa&method=2&gwp=13">Kinshasa</a>, <a href="http://www.answers.com/topic/congo-country-zaire&method=6">Zaire</a>); Apple in the role of <a href="http://www.answers.com/topic/muhammad-ali-boxer&method=6">Ali</a> (aka "The Greatest" who was the overwhelming underdog at time) and Microsoft in the role of <a href="http://www.answers.com/topic/george-foreman&method=6">George Foreman</a> (who at the time was logically invincible). </p>
<p dir="ltr">The shakesperian tale of Macbeth also comes to mind as depicted in the excerpt below:</p>
<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
<p dir="ltr">".... Macbeth goes to visit the witches in their cavern. There, they show him a sequence of demons and spirits who present him with further prophecies: he must beware of Macduff, a Scottish nobleman who opposed Macbeth's accession to the throne; he is incapable of being harmed by any man born of woman; and he will be safe until Birnam Wood comes to Dunsinane Castle. "</p></blockquote>
<p dir="ltr">Having used all the major operating systems on a serious basis for a number of years in a variety of&nbsp;modes;&nbsp;user, developer, and administrator. I have always felt that a RISC based UNIX operating system (of BSD genealogical branch extraction), if somehow combined with a user interface that is superior to Windows,&nbsp;would ultimately&nbsp;unravel the Windows Desktop Monopoly. That&nbsp;operating system exists today in the form of Mac OS X (its lastest Tiger release simply <a href="http://www.apple.com/macosx/newfeatures/">kicks the differential up a notch</a>). </p>
<p dir="ltr">Back to the Macbeth correlation:</p>
<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
<p dir="ltr"><u>"Birnam Woods coming to Dunsinane"</u> is the metaphoric equivalent of desktop users and first time computer users being forced (by the scourge of virus and spyware) to revaluate Windows as the only choice for productive desktop computing. What would you recommend to "Aunt Milly" when she tells you she wants to get on the Internet? Especially if "Aunt Milly" isn't living with you?</p>
<p dir="ltr">"<u>Man not born of a woman"</u> is no different to saying: UNIX with a superior user interface to Windows!</p>
<p dir="ltr">I don't think you need me to tell who play the characters of Macbeth and Macduff in this drama :-)</p></blockquote>
<p dir="ltr">The Windows security vulnerabilities quagmire (<a href="http://www.google.com/search?q=Windows+security+vulnerabilities+quagmire&sourceid=mozilla-search&start=0&start=0&ie=utf-8&oe=utf-8&client=firefox-a&rls=org.mozilla:en-US:official">google juice</a> on this phrase is currently 6,620 pages)&nbsp;has basically created an inflection of monumental proportions adversely affecting Windows and creating great visibility and evaluation building opportunities for Mac OS X ("once users&nbsp;experience a&nbsp;Mac they don't come back to Windows!").</p>
<p dir="ltr">Paul Murphy of <a href="http://www.cio-today.com/">cio-today.com</a>&nbsp;has also written a great article&nbsp;sheds light on the&nbsp;often overlooked hardware aspect to the security problem for Windows&nbsp;Here is a poignant excerpt:</p>
<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
<p><font face="arial" size="-1"><b>Software and Hardware Vulnerabilities</b> </font></p>
<p><font face="arial" size="-1"></font></p>
<p><font face="arial" size="-1">At present, attacks on Microsoft's Windows products are generally drawn from a different population of possible attacks than those on <span class="keyword"><a href="http://us.rd.yahoo.com/DailyNews/manual/nf/bs_nf/33272/14945921/*http://news.search.yahoo.com/search/news?fr=news-storylinks&p=%22Unix%22&c=&n=20&yn=c&c=news&cs=nw">Unix</a></span> variants such as BSD, Linux and Solaris. From a practical perspective, the key difference is that attacks on Wintel tend to have two parts: A software vulnerability is exploited to give a remote attacker access to the x86 hardware and that access is then used to gain control of the machine. </font></p>
<p><font face="arial" size="-1"></font></p>
<p><font face="arial" size="-1">In contrast, attacks on Unix generally require some form of initial legal access to the machine and focus on finding software ways to upgrade priveleges illegally. </font></p>
<p><font face="arial" size="-1"></font></p>
<p><font face="arial" size="-1">Consider, for example, CAN-2004-1134 in the NIST vulnerabilities database: </font></p>
<p><font face="arial" size="-1"></font></p>
<p><font face="arial" size="-1">Summary: Buffer overflow in the Microsoft W3Who ISAPI (w3who.dll) allows remote attackers to cause a denial of service and possibly execute arbitrary code via a long query string. </font></p>
<p><font face="arial" size="-1"></font></p>
<p><font face="arial" size="-1">Published Before: 1/10/2005 </font></p>
<p><font face="arial" size="-1"></font></p>
<p><font face="arial" size="-1">Severity: High </font></p>
<p><font face="arial" size="-1"></font></p>
<p><font face="arial" size="-1">The vulnerability exists in Microsoft's code, but the exploit depends on the rigid stack-order execution and limited page protection inherent in the x86 architecture. If Windows ran on Risc, that vulnerability would still exist, but it would be a non-issue because the exploit opportunity would be more theoretical than practical. </font></p>
<p><font face="arial" size="-1"></font></p>
<p><font face="arial" size="-1">Linux and open-source applications are thought to have far fewer software vulnerabilities than Microsoft's products, but Linux on Intel (<a href="http://us.rd.yahoo.com/dailynews/finance/nf/bs_nf/storytext/33272/14945921/*http://finance.yahoo.com/q?s=intc&d=t">Nasdaq: INTC</a> - <a href="http://us.rd.yahoo.com/dailynews/biz/nf/bs_nf/storytext/33272/14945921/*http://biz.yahoo.com/n/i/intc.html">news</a>) is susceptible to the same kind of attacks as those now predominantly affecting Wintel users. For real long-term security improvements, therefore, the right answer is to look at Linux, or any other Unix, on non x86 hardware. </font></p>
<p><font face="arial" size="-1"></font></p>
<p><font face="arial" size="-1">One such option is provided by Apple's (<a href="http://us.rd.yahoo.com/dailynews/finance/nf/bs_nf/storytext/33272/14945921/*http://finance.yahoo.com/q?s=aapl&d=t">Nasdaq: AAPL</a> - <a href="http://us.rd.yahoo.com/dailynews/biz/nf/bs_nf/storytext/33272/14945921/*http://biz.yahoo.com/n/a/aapl.html">news</a>) BSD-based products on the PowerPC-derived G4 and G5 CPUs. <span class="keyword"><a href="http://us.rd.yahoo.com/DailyNews/manual/nf/bs_nf/33272/14945921/*http://news.search.yahoo.com/search/news?fr=news-storylinks&p=%22Linus%20Torvalds%22&c=&n=20&yn=c&c=news&cs=nw">Linus Torvalds</a></span>, for example, apparently now runs Linux on a Mac G5 and there are several Linux distributions for this hardware -- all of which are immune to the typical x86-oriented exploit. </font></p></blockquote>
<p dir="ltr">This may even been the nullifier of that age old argument about porting Mac OS X to the x86 in order to broaden its adoption potential?</p>
<p dir="ltr">Mac OS X is certainly a breath of fresh air for anyone who needs to simply get stuff&nbsp;done with their&nbsp;desktops and notebooks. </p>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2005-03-26#766">
  <rss:title>Back To The Future: Hypermedia</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2005-03-26T20:24:30Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">If a picture speaks a thousand words, I sometimes wonder how many words we attribute to a multimedia clip? Especially one that is now openly accessible to many who don&#39;t quite understand the high degree of: &quot;Back To The Future&quot; quotient of most of what we see today. The Internet Archive initiative is building up an amazing collection of content that includes this &quot;must watch&quot; movie about the somewhat forgotten hypercard development environment. As I watched the hypercard movie I obtained clear reassurance that my vision of Web 2.0 as critical infrastructure for a future Semantic Web isn&#39;t unfounded. The solution building methodology espoused by hypercard is exactly how Semantic Web applications will be built, and this will be done by orchestrating the componentary of Web 2.0. When watching this clip make the following mental adjustments: Swap hypercard stacks for discrete and/or composite services that have published endpoints exposed by Web 2.0 points of presence Think of information taking the form of XML based content e.g. RSS, Atom, RDF, FOAF, XFN, and other future XML based data contextualization formats; all accessible via URIs When the Apple Mac operating system is mentioned (or infered) think of the Internet (you don&#39;t need Windows, Mac OS, Linux, UNIX etc. to realize the vision, the network provided by the Internet is the Operating System) When the Apple computer is mentioned simply think about a plethora of function specific devices (computers, mobile phones, PDAs etc.) that overtly or covertly provide conduits to the new operating environment (the Internet) As you hear term &quot;whole new body of people that are non programmers contributing there ideas&quot; think about yourself and the increasing ease of participation that&#39;s beginning to take shape in this emerging frontier! As for &quot;Whole Earth Catalog&quot;, think Wikipedia or more recent efforts such as Answers.com. Web 2.0 is a reflection of the web taking its first major step out of the technology stone age (certainly the case relative to the hypercard movie and &quot;pre web&quot; application development in general).  </dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>If a picture speaks a thousand words, I sometimes wonder how many words we attribute to a multimedia clip? Especially one that is now openly accessible to many who don't quite understand the high degree of: "Back To The Future" quotient of most of what we see today.</p>
<p>The Internet&nbsp;Archive initiative is building up an amazing&nbsp;collection of content&nbsp;that includes this <a href="http://www.archive.org/movies/details-db.php?collection=computerchronicles&collectionid=CC501_hypercard">"must watch" movie</a> about the somewhat forgotten <a href="http://en.wikipedia.org/wiki/Hypercard">hypercard</a> development environment.</p>
<p>As I watched the hypercard movie I obtained clear reassurance that my vision of <a href="http://en.wikipedia.org/wiki/Web_2.0">Web 2.0</a> as critical infrastructure for a future Semantic Web isn't unfounded. The solution building methodology espoused by hypercard is exactly how Semantic Web applications will be built, and this will be done by orchestrating&nbsp;the componentary of Web 2.0.</p>
<p>When watching this clip make the following mental adjustments:</p>
<ol>
<li>Swap hypercard stacks for discrete and/or composite services that have published endpoints exposed by Web 2.0 points of presence<br><br></li>
<li>Think of information taking the form of XML based content e.g. RSS, Atom, RDF, FOAF, XFN, and other future&nbsp;XML based data contextualization&nbsp;formats; all accessible via URIs<br><br></li>
<li>When the Apple Mac operating system is mentioned (or infered) think of the Internet&nbsp;(you don't need Windows, Mac OS, Linux,&nbsp;UNIX etc.&nbsp;to realize the vision, the network provided by the Internet&nbsp;is the Operating System)<br><br></li>
<li>When the Apple computer is mentioned simply think about a plethora of function specific devices (computers, mobile phones, PDAs etc.) that overtly or covertly provide conduits to the new operating environment (the Internet)<br><br></li>
<li>As you hear term "whole new body of people that are non programmers contributing there ideas" think about yourself and the increasing ease of participation&nbsp;that's beginning to take shape in this&nbsp;emerging frontier!<br><br></li>
<li>As for "<a href="http://www.wholeearthmag.com/about.html">Whole Earth Catalog", </a>think <a href="http://en.wikipedia.org">Wikipedia</a>&nbsp;or more recent efforts such as <a href="http://www.answers.com">Answers.com</a>.</li></ol>
<p>Web 2.0 is a reflection of the web taking its first major step out of the technology stone age (certainly the case relative to the hypercard movie and "pre web" application development in general). </p>
<p>&nbsp;</p>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2004-11-19#642">
  <rss:title>MacSOS Releases SyBrowser 6.2</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2004-11-19T17:40:38Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">MacSOS Releases SyBrowser 6.2 Dr. Gerard Hammond of MacSOS announced the release of SyBrowser 6.2, a Macintosh application that can query Sybase, FrontBase, PostgreSQL, Oracle, ODBC and MS SQL databases hosted on OSX, UNIX, Linux, and Windows servers. SyBrowser v6.2 features include: - Added FrontBase database support. - Added &quot;Bachman&quot; style ERD features (Tridents for &#39;Many&#39; arms of a relationship, open circles for optional entities) - The arms of a relationship now track their entities correctly in all directions. - The arm of the selected relationship can be moved using the mouse or the keyboard - Fixed bug with SQL auto-completion popup with multiple monitors. - Enhanced the &quot;Edit Relationships Info...&quot; dialog. This dialog allows the properties of the selected relationship to be edited. - The mouse cursor changes to reflect the draggable direction when resizing ERD tables, or dragging the various arms of a relationship. The selected arm of the selected relationship now has a circle for a handle. - Documentation added. - Printing the ERD panel has been improved. - The Find dialog allows searching the returned datasets on the SQL panel and Results windows as well as the code in Sybase stored procedures. SyBrowser Overview SyBrowser is a table browser and alternative &quot;isql&quot; client for Sybase databases. It facilitates SQL generation thorough a point and click interface. SyBrowser also provides an overview of the tables in ODBC, MySQL, Oracle, FrontBase, PostgreSQL and MS SQL databases. Complex queries can be saved to disk for reuse. An ERD module allows the creation of visual representations of data models. $89 Shareware from MacSOS, Australia $49 upgrade from any previous version http://www.macsos.com.au [via RB Garage News Feed]</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<a href="http://feeds.feedburner.com/rbgarage?m=93">MacSOS Releases SyBrowser 6.2</a> 
<div xmlns="http://www.w3.org/1999/xhtml">Dr. Gerard Hammond of MacSOS announced the release of SyBrowser 6.2, a Macintosh application that can query Sybase, FrontBase, PostgreSQL, Oracle, ODBC and MS SQL databases hosted on OSX, UNIX, Linux, and Windows servers. <br><br>SyBrowser v6.2 features include: <br><br>- Added FrontBase database support. <br>- Added "Bachman" style ERD features (Tridents for 'Many' arms of a relationship, open circles for optional entities) <br>- The arms of a relationship now track their entities correctly in all directions. <br>- The arm of the selected relationship can be moved using the mouse or the keyboard <br>- Fixed bug with SQL auto-completion popup with multiple monitors. <br>- Enhanced the "Edit Relationships Info..." dialog. This dialog allows the properties of the selected relationship to be edited. <br>- The mouse cursor changes to reflect the draggable direction when resizing ERD tables, or dragging the various arms of a relationship. The selected arm of the selected relationship now has a circle for a handle. <br>- Documentation added. <br>- Printing the ERD panel has been improved. <br>- The Find dialog allows searching the returned datasets on the SQL panel and Results windows as well as the code in Sybase stored procedures. <br><br>SyBrowser Overview <br>SyBrowser is a table browser and alternative "isql" client for Sybase databases. It facilitates SQL generation thorough a point and click interface. SyBrowser also provides an overview of the tables in ODBC, MySQL, Oracle, FrontBase, PostgreSQL and MS SQL databases. Complex queries can be saved to disk for reuse. An ERD module allows the creation of visual representations of data models. <br><br>$89 Shareware from MacSOS, Australia <br>$49 upgrade from any previous version <br><br><a href="http://www.macsos.com.au/">http://www.macsos.com.au</a> </div>
<div align="right">[via <a href="http://rbgarage.blogspot.com/">RB Garage News Feed</a>]</div>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-10-23#395">
  <rss:title>A Virtuoso of a Server</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-10-23T21:57:48Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">NETWORK WORLD NEWSLETTER: MARK GIBBS ON WEB APPLICATIONS Today&#39;s focus: A Virtuoso of a server By Mark Gibbs One of the bigger drags of Web applications development is that building a system of even modest complexity is a lot like herding cats - you need a database, an applications server, an XML engine, etc., etc. And as they all come from different vendors you are faced with solving the constellation of integration issues that inevitably arise. If you are lucky, your integration results in a smoothly functioning system. If not, you have a lot of spare parts flying in loose formation with the risk of a crash and burn at any moment. An alternative is to look for all of these features and services in a single package but you&#39;ll find few choices in this arena. One that is available and looks very promising is OpenLink&#39;s Virtuoso (see links below). Virtuoso is described as a cross platform (runs on Windows, all Unix flavors, Linux, and Mac OS X) universal server that provides databases, XML services, a Web application server and supporting services all in a single package. OpenLink&#39;s list of supported standards is impressive and includes .Net, Mono, J2EE, XML Web Services (Simple Object Application Protocol, Web Services Description Language, WS-Security, Universal Description, Discovery and Integration), XML, XPath, XQuery, XSL-T, WebDav, HTTP, SMTP, LDAP, POP3, SQL-92, ODBC, JDBC and OLE-DB. Virtuoso provides an HTTP-compliant Web Server; native XML document creation, storage and management; a Web services platform for creation, hosting and consumption of Web services; content replication and synchronization services; free text index server, mail delivery and storage and an NNTP server. Another interesting feature is that with Virtuoso you can create Web services from existing SQL Stored Procedures, Java classes, C++ classes, and &#39;C&#39; functions as well as create dynamic XML documents from ODBC and JDBC data sources. This is an enormous product and implies a serious commitment on the part of adopters due to its scope and range of services. Virtuoso is enormous by virtue of its architectural ambitions, but actual disk requirements are</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<font size="2">
<p><a href="http://www.nwfusion.com/index.html">NETWORK WORLD</a> NEWSLETTER: MARK GIBBS ON WEB APPLICATIONS </p>
<p><font size="2">Today&#39;s focus: A Virtuoso of a server</font></p>
<p>By <a href="http://www.nwfusion.com/columnists/gibbs.html">Mark Gibbs</a></p>
<p>One of the bigger drags of Web applications development is that building a system of even modest complexity is a lot like herding cats - you need a database, an applications server, an XML engine, etc., etc. And as they all come from different vendors you are faced with solving the constellation of integration issues that inevitably arise.</p>
<p>If you are lucky, your integration results in a smoothly functioning system. If not, you have a lot of spare parts flying in loose formation with the risk of a crash and burn at any moment.</p>
<p>An alternative is to look for all of these features and services in a single package but you&#39;ll find few choices in this arena.</p>
<p>One that is available and looks very promising is OpenLink&#39;s Virtuoso (see links below).</p>
<p>Virtuoso is described as a cross platform (runs on Windows, all Unix flavors, Linux, and Mac OS X) universal server that provides databases, XML services, a Web application server and supporting services all in a single package.</p>
<p>OpenLink&#39;s list of supported standards is impressive and includes .Net, Mono, J2EE, XML Web Services (Simple Object Application Protocol, Web Services Description Language, WS-Security, Universal Description, Discovery and Integration), XML, XPath, XQuery, XSL-T, WebDav, HTTP, SMTP, LDAP, POP3, SQL-92, ODBC, JDBC and OLE-DB.</p>
<p>Virtuoso provides an HTTP-compliant Web Server; native XML document creation, storage and management; a Web services platform for creation, hosting and consumption of Web services; content replication and synchronization services; free text index server, mail delivery and storage and an NNTP server.</p>
<p>Another interesting feature is that with Virtuoso you can create Web services from existing SQL Stored Procedures, Java classes,</p>
<p>C++ classes, and &#39;C&#39; functions as well as create dynamic XML</p>
<p>documents from ODBC and JDBC data sources.</p>
<p>This is an enormous product and implies a serious commitment on the part of adopters due to its scope and range of services.</p>
<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
<p><em>Virtuoso is enormous by virtue of its architectural ambitions, but actual disk requirements are</em></p></blockquote></font>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-08-05#232">
  <rss:title>Howl is Rendezvous for Windows and Linux</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-08-05T19:18:55Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Very interesting, we have basically ported Zeroconfig as released by Apple (in Open Source) too, and used it in both our Virtuoso 3.x and UDA 5.x products. Howl is Rendezvous for Windows and Linux. [via Scripting News] In the case of UDA you can configure ODBC and JDBC consumable data source names that are hosted on the server. Users can nownbspsimply picknbspDSNs from anbspcombo box and they are ready to make connections to remote databases from any ODBC, JDBC, OLE DB, or ADO.NET application.nbspAnother benefit ofnbspZeroconfignbspis that it facilitates centralized server side configuration which further enhances our server side session rules book;nbspwhich serves all our Multi-Tier data access drivers. In the case of Virtuoso you are able to bind to pre-configured Virtuoso instances in exactly the same way. Our Zeroconfig support has beennbspimplemented across Solaris, AIX, Digital UNIX, IRIX, HP-UX amongst others, but this is a project of interest all the same, and we may end up contributing to this effort.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p dir="ltr">Very interesting, we have basically ported Zeroconfig as released by Apple (in Open Source) too, and used it in both our <a href="http://www.openlinksw.com/virtuoso/whatis.htm">Virtuoso</a> 3.x and <a href="http://www.openlinksw.com/product.htm">UDA</a> 5.x products.</p>
<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
<p><a href="http://www.swampwolf.com/products/">Howl</a> is Rendezvous for Windows and Linux. [via <a href="http://www.scripting.com/">Scripting News</a>]</p></blockquote>
<p dir="ltr">In the case of UDA you can configure ODBC and JDBC consumable data source names that are hosted on the server. Users can nownbspsimply picknbspDSNs from anbspcombo box and they are ready to make connections to remote databases from any ODBC, JDBC, OLE DB, or ADO.NET application.nbspAnother benefit ofnbspZeroconfignbspis that it facilitates centralized server side configuration which further enhances our server side session rules book;nbspwhich serves all our Multi-Tier data access drivers.</p>
<p dir="ltr">In the case of Virtuoso you are able to bind to pre-configured Virtuoso instances in exactly the same way.</p>
<p dir="ltr">Our Zeroconfig support has beennbspimplemented across Solaris, AIX, Digital UNIX, IRIX, HP-UX amongst others, but this is a project of interest all the same, and we may end up contributing to this effort.</p>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-07-31#226">
  <rss:title>Blogs as Disruptive Tech</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-08-01T01:22:52Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">How weblogs are flying under the radar of the Content Management Giants The term &quot;Disruptive Technology&quot; has always kinds irked me, pretty much in the same way the word &quot;Proprietary Technology&quot; has in the past. The problem I had with &quot;Proprietary Technology&quot; is that I&#39;ve spent a lot of my professional career on the &quot;Open....&quot; side of the fence. I am a firm beliver in &quot;Open Systems&quot; (in all its historic forms; UNIX, Client-Server, Internet Protocols etc.), so describing OpenLink Software (even the company name gives me away!) product as being proprietary is really difficult, especially as I believe in the concept of our value proposition being the only thing that should actually be proprietary. Back to &quot;Disruptive Technology&quot;. Prior to reading the piece below [Blogs as Disruptive Tech - How weblogs are flying under the radar of the Content Management Giants] I had similar conflicts, and strangely enough I simply forgotthat old principle of physics which states; &quot;for every action, there is an equal and opposite reaction&quot;. Disruputive technology in most use cases describes how new technologies and paradigms create market inflections amongst vendors in a particular market segment. Ironically, this is the basis of everything I do (spot new technologies and paradigms and then look at how they can be used produce valuable solutions). It doesn&#39;t mean that I can&#39;t deliver &quot;Market Disruptive Technology&quot; to my customers in such a way that it minimizes the&quot;Disruption&quot;to their existing IT infrastructures (at least to the degree this is feasible in a given situation). For what it&#39;s worth I blogged this piece using a &quot;Disruptive&quot; utlility called Mozblog (I&#39;ve had some problems using this plugin until now). The keys to getting this Blog plugin working are as follows: Download and follow instructions at: http://mozblog.mozdev.org/installation.html Use the Moveable Type or Other option when setting up your Blog Server&#39;s XML-RPC endpoint That&#39;s it.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>How weblogs are flying under the radar of the Content Management Giants</p>
<p>The term "Disruptive Technology" has always kinds irked me, pretty much in the same way the word "Proprietary Technology" has in the past. The problem I had with "Proprietary Technology" is that I've spent a lot of my professional career on the "Open...." side of the fence. I am a firm beliver in "Open Systems" (in all its historic forms; UNIX, Client-Server, Internet Protocols etc.), so describing OpenLink Software (even the company name gives me away!) product as being proprietary is really difficult, especially as I believe in the concept of our value proposition being the only thing that should actually be proprietary.</p>
<p>Back to "Disruptive Technology". Prior to reading the piece below </p>
<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
<p>[<a href="http://www.webcrimson.com/ourstories/blogsdisruptivetech.htm">Blogs as Disruptive Tech - How weblogs are flying under the radar of the Content Management Giants</a>]</p></blockquote>
<p>I had similar conflicts, and strangely enough I simply forgotthat old principle of physics which states; "for every action, there is an equal and opposite reaction". </p>
<p>Disruputive technology in most use cases describes how new technologies and paradigms create market inflections amongst vendors in a particular market segment. Ironically, this is the basis of everything I do (spot new technologies and paradigms and then look at how they can be used produce valuable solutions). It doesn't mean that I can't deliver "Market Disruptive Technology" to my customers in such a way that it minimizes the"Disruption"to their existing IT infrastructures (at least to the degree this is feasible in a given situation). </p>
<p>For what it's worth I blogged this piece using a "Disruptive" utlility called <a href="http://mozblog.mozdev.org/">Mozblog</a> (I've had some problems using this plugin until now). </p>
<p>The keys to getting this Blog plugin working are as follows:<br></p>
<ol>
<li>Download and follow instructions at: <a href="http://mozblog.mozdev.org/installation.html">http://mozblog.mozdev.org/installation.html</a></li>
<li>Use the Moveable Type or Other option when setting up your Blog Server's XML-RPC endpoint 

<p>That's it.<br></p>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-07-07#201">
  <rss:title>Tim O&#39;Reilly about network aware software</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-07-07T20:51:35Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Tim O&#39;Reilly about network aware software Tim O&#39;Reilly wrote some thoughts about network aware software. Good sumup and nice ideas, why not only blogs should be net-aware (and where even blogs can be improved ;) ) &quot;For the desktop, my personal vision is to see existing software instrumented to become increasingly web aware. It seems that Apple are doing a good job with this. (What does web aware mean for me? Being able to grok URIs, speaking WebDAV, and using open standard data formats.)&quot; -- Edd Dumbill [via Bitflux Blog] I agree, but you do have to add Open Data Access formats (such as ODBC and to some degree JDBC) to this mix otherwise the you will need to create data for Open Standard Data Formats from sratch (tough for any enterprise irrespective of size). Tim O&#39;Reilly added the following items to Edd&#39;s list: Rendezvous-like functionality for automatic discovery of and potential synchronization with other instances of the application on other computers. Apple is showing the power of this idea with iChat and iTunes, but it really could be applied in so many other places. For example, if every PIM supported this functionality, we could have the equivalent of &quot;phonester&quot; where you could automatically ask peers for contact information. Of course, that leads to guideline 2. Another application is discovery of ODBC data sources, and database servers. Rendezvous can also simply security and administration of data sources accessible by either one of these standards data access mechanisms. It can also apply to XML databases and data sources exposed by XML Databases. If you assume ad-hoc networking, you have to automatically define levels of access. I&#39;ve always thought that the old Unix ugo (user, group, other) three-level permission system was simple and elegant, and if you replace the somewhat arbitrary &quot;group&quot; with &quot;on my buddy list&quot;, you get something quite powerful. Which leads me to... Buddy lists ought to be supported as a standard feature of many apps, and in a consistent way. What&#39;s more, our address books really ought to make it easy to indicate who is in a &quot;buddy list&quot; and support numerous overlapping lists for different purposes. Every application ought to expose some version of its data as an XML feed via some well-defined and standard access mechanism. It strikes me that one of the really big wins that fueled the early web was a simple naming scheme: you could go to a site called www.foo.com, and you&#39;d find a web server there. While it wasn&#39;t required, it made web addresses eminently guessable. We missed the opportunity for xml.foo.com to mean &quot;this is where you get the data feed&quot; but it&#39;s probably still possible to come up with a simple, consistent naming scheme. And of course, if we can do it for web sites, we also need to think about how to do it for local applications, since... The very point I continue to make about Internet Points of Presence beingactual data acces points, in short these end points should be served by database serverprocesses. This is the very basis of Virtuoso, the inevitability of this realization remains the undepinings of this product. There are other products out there that have some sense of this vision too, but there is a little snag (at least so far in my research efforts), and that is the tendency to create dedicated independent server per protocol (an ultimate integration, administration, and maintenance nightmare). We ought to be able to have the expectation that all applications, whether local or remote (web) will be set up for two-way interactions. That is, they can be either a source or sink of online data. So, for example, the natural complement to amazon&#39;s web services data feeds is data input (for example, the ability to comment on a book on your local blog, and syndicate the review via RSS to amazon&#39;s detail page for the book.) And that leads to: We really need to understand who owns what, and come up with mechanisms that protect the legitimate rights of individuals and businesses to their own data, while creating the &quot;liquidity&quot; and free movement of data that will fuel the next great revolution in computer functionality. (I&#39;m doing a panel on this subject at next week&#39;s Open Source Convention, entitled &quot;We Need a Bill of Rights for Web Services.&quot;) We need easy gateways between different application domains. I was recently in Finland at a Nokia retreat, and we used camera-enabled cell phones to create a mobile photoblog. That was great. But even more exciting was the ease with which I could send a photo from the phone not just to another phone but also to an email address. This is the functionality that enabled the blog gateway, but it also made it trivial to send photos home to my family and friends. Similarly, I often blog things that I hear on mailing lists, and read many web sites via screen-scraping enabled email lists. It would be nice to have cross-application gateways be a routine part of software, rather than something that has to be hacked on after the fact. The wish list is pretty much a clear articulation of key items that should matter most to decision makers (CTOs and CIOs) ; in particular those that continue to wrestle with the identification and isolation of relevantcomponentsfor their enterprisearchitectures.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p><a href="http://blog.bitflux.ch/p1077.html">Tim O'Reilly about network aware software</a> </p>
<p>Tim O'Reilly wrote some thoughts about network aware software. Good sumup and nice ideas, why not only blogs should be net-aware (and where even blogs can be improved ;) ) </p>
<blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
<div align="left">"<i>For the desktop, my personal vision is to see existing software instrumented to become increasingly web aware. It seems that Apple are doing a good job with this. (What does web aware mean for me? Being able to grok URIs, speaking WebDAV, and using open standard data formats.)</i>" -- <strong>Edd Dumbill</strong> </div>
<div align="left"></div>
<div align="left">[via <a href="http://blog.bitflux.ch/">Bitflux Blog</a>]</div></blockquote>
<div align="left">I agree, but you do have to add Open Data Access formats (such as ODBC and to some degree JDBC) to this mix otherwise the you will need to create data for Open Standard Data Formats from sratch (tough for any enterprise irrespective of size).</div>
<div align="left"></div>
<div align="left">Tim O'Reilly added the following items to Edd's list:</div>
<div align="left">
<ul>
<li>
<p>Rendezvous-like functionality for automatic discovery of and potential synchronization with other instances of the application on other computers. Apple is showing the power of this idea with iChat and iTunes, but it really could be applied in so many other places. For example, if every PIM supported this functionality, we could have the equivalent of "phonester" where you could automatically ask peers for contact information. Of course, that leads to guideline 2. </p></li></ul></div>
<p>Another application is discovery of <a href="http://www.openlinksw.com/info/docs/uda50/mt/features.html#features">ODBC data sources</a>, and database servers. Rendezvous can also simply security and administration of data sources accessible by either one of these standards data access mechanisms. It can also apply to XML databases and data sources exposed by <a href="http://www.openlinksw.com/virtuoso/whatis.htm">XML Databases</a>.</p>
<p></p>
<p></p>
<ul>
<li>If you assume ad-hoc networking, you have to automatically define levels of access. I've always thought that the old Unix ugo (user, group, other) three-level permission system was simple and elegant, and if you replace the somewhat arbitrary "group" with "on my buddy list", you get something quite powerful. Which leads me to... 
<p></p>
<p></p></li>
<ul>
<li>Buddy lists ought to be supported as a standard feature of many apps, and in a consistent way. What's more, our address books really ought to make it easy to indicate who is in a "buddy list" and support numerous overlapping lists for different purposes. <br></li></ul>
<li>Every application ought to expose some version of its data as an XML feed via some well-defined and standard access mechanism. It strikes me that one of the really big wins that fueled the early web was a simple naming scheme: you could go to a site called www.foo.com, and you'd find a web server there. While it wasn't required, it made web addresses eminently guessable. We missed the opportunity for xml.foo.com to mean "this is where you get the data feed" but it's probably still possible to come up with a simple, consistent naming scheme. And of course, if we can do it for web sites, we also need to think about how to do it for local applications, since... </li></ul>
<p>The very point I continue to make about Internet Points of Presence beingactual data acces points, in short these end points should be served by database serverprocesses. This is the very basis of <a href="http://www.openlinksw.com/virtuoso">Virtuoso</a>, the inevitability of this realization remains the undepinings of this product. There are other products out there that have some sense of this vision too, but there is a little snag (at least so far in my research efforts), and that is the tendency to create dedicated independent server per protocol (an ultimate integration, administration, and maintenance nightmare).</p>
<ul>
<li>We ought to be able to have the expectation that all applications, whether local or remote (web) will be set up for two-way interactions. That is, they can be either a source or sink of online data. So, for example, the natural complement to amazon's web services data feeds is data input (for example, the ability to comment on a book on your local blog, and syndicate the review via RSS to amazon's detail page for the book.) And that leads to: 
<p></p>
<p></p></li>
<li>We really need to understand who owns what, and come up with mechanisms that protect the legitimate rights of individuals and businesses to their own data, while creating the "liquidity" and free movement of data that will fuel the next great revolution in computer functionality. (I'm doing a panel on this subject at next week's Open Source Convention, entitled "<a href="http://conferences.oreillynet.com/cs/os2003/view/e_sess/4526">We Need a Bill of Rights for Web Services</a>.") 
<p></p>
<p></p></li>
<li>We need easy gateways between different application domains. I was recently in Finland at a Nokia retreat, and we used camera-enabled cell phones to create a mobile photoblog. That was great. But even more exciting was the ease with which I could send a photo from the phone not just to another phone but also to an email address. This is the functionality that enabled the blog gateway, but it also made it trivial to send photos home to my family and friends. Similarly, I often blog things that I hear on mailing lists, and read many web sites via screen-scraping enabled email lists. It would be nice to have cross-application gateways be a routine part of software, rather than something that has to be hacked on after the fact.</li></ul>
<div align="left">The wish list is pretty much a clear articulation of key items that should matter most to decision makers (CTOs and CIOs) ; in particular those that continue to wrestle with the identification and isolation of relevantcomponentsfor their enterprisearchitectures. </div>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-06-25#187">
  <rss:title>OpenLink Software Announces Virtuoso 3.2 </rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-06-25T21:35:54Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">OpenLink Software Announces Virtuoso 3.2 This Blog Site is actually powered by Virtuoso 3.2 (has been doing so prior to the announcement). Hmm. product utilization preceding press release? Why not? OpenLink adds Weblog client and server functionality to Virtual Database Engine for SQL, XML, and Web Services Burlington, MA. June 25, 2003 - OpenLink Software, Inc., a leading provider of universal data access and enterprise information integration middleware, announces Virtuoso 3.2  the latest edition of its cross platform Virtual Database for SQL, XML, and Web Services  for Mac® OS X. The new release incorporates full client and server support for the Blogger, Moveable Type, and MetaWeblog APIs, providing users with choice over location, format, data storage, development environment, and host operating system, for personal, community, and corporate Weblogs. The new release also facilitates the transparent integration of Weblog data with other enterprise data sources. Full Press Release Putting together the community site took 5 minutes and it basically involved the following steps: 1. Standard installation from installer program (Mac OS X in this case, but Windows, Linux, and UNIX supported) 2. Creation of WebDAV user account for WebDAV repository (where all the gems reside) 3. Clicking on the &quot;Generate Web Site&quot; button situated in the Weblog menu tree with the Virtuoso HTML based Admin UI 4. Filled up my channel and blogrolls by asking Virtuoso to use its very old web content aggregation functionality 5. Setup my upstreams (so that I post once and propagate to my numerous blog sites on a conditional basis) 6. Create a Virtuoso HTTP Virtual Domain for the community/personal Blog 7. Start blogging using any Blog Client that supports; Blogger API, MetaWeblog, or Moveable Type No more no less. Most importantly I have a choice of programming languages (VSP, VSX, PHP, ASP.NET, JSP, Perl, Python), operating systems, and databases that constitute the shape and form of my blog home. See the Virtuoso FAQ for how this all comes together.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<P><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><A href="http://www.openlinksw.com/press/virt32_wwdc1.htm">OpenLink Software Announces Virtuoso 3.2 </a></span></p>
<P><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">This <A href="http://wwdc2003.openlinksw.com/"><SPAN style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'"><FONT face=Arial size=2>Blog Site</font></span></a> is actually powered by <A href="http://www.openlinksw.com/virtuoso">Virtuoso</a> 3.2 (has been doing so prior to the announcement). Hmm. product utilization preceding press release? Why not?</span><B><SPAN style="FONT-FAMILY: Arial"><FONT size=3></font></span></b></p>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<P><B><SPAN style="FONT-FAMILY: Arial">OpenLink adds Weblog client and server functionality to <BR>Virtual Database Engine for SQL, XML, and Web Services</span></b><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> <BR><BR><B>Burlington, MA. June 25, 2003</b> - OpenLink Software, Inc., a leading provider of universal data access and enterprise information integration middleware, announces Virtuoso 3.2  the latest edition of its cross platform Virtual Database for SQL, XML, and Web Services  for Mac® OS X. <BR><BR>The new release incorporates full client and server support for the Blogger, Moveable Type, and MetaWeblog APIs, providing users with choice over location, format, data storage, development environment, and host operating system, for personal, community, and corporate Weblogs. The new release also facilitates the transparent integration of Weblog data with other enterprise data sources. </span></p>
<P><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"><A href="http://www.openlinksw.com/press/virt32_wwdc1.htm"><SPAN style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'"><FONT face=Arial size=2>Full Press Release</font></span></a></span></p></blockquote>
<P dir=ltr><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">Putting together the community site took 5 minutes and it basically involved the following steps:</span></p>
<P dir=ltr><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">1. Standard installation from installer program (Mac OS X in this case, but Windows, Linux, and UNIX supported)</span></p>
<P dir=ltr><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">2. Creation of WebDAV user account for WebDAV repository (where all the gems reside)</span></p>
<P dir=ltr><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">3. Clicking on the "Generate Web Site" button situated in the Weblog menu tree with the Virtuoso HTML based Admin UI</span></p>
<P dir=ltr><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">4. Filled up my channel and blogrolls by asking Virtuoso to use its <U>very old web</u> content aggregation functionality </span></p>
<P dir=ltr><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">5. Setup my upstreams (so that I post once and propagate to my numerous blog sites on a conditional basis)</span></p>
<P dir=ltr><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">6. Create a Virtuoso HTTP Virtual Domain for the community/personal Blog </span></p>
<P dir=ltr><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">7. Start blogging using any Blog Client that supports; Blogger API, MetaWeblog, or Moveable Type</span></p>
<P dir=ltr><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">No more no less. Most importantly I have a choice of programming languages (VSP, VSX, PHP, ASP.NET, JSP, Perl, Python), operating systems, and databases that constitute the shape and form of my blog home. </span></p>
<P dir=ltr><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Arial">See the<A href="http://www.openlinksw.com/virtuoso/faqs.htm"> Virtuoso FAQ </a>for how this all comes together.</span></p>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-06-25#183">
  <rss:title>&lt;p&gt;We all know that the only benchmark that matters, is the one that you run in-house using the systems that comprise your IT infrastructure. &lt;/p&gt;</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-06-25T13:27:02Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">We all know that the only benchmark that matters, is the one that you run in-house using the systems that comprise your IT infrastructure. Apple&#39;s benchmarks under fire ZDNet Jun 25 2003 7:13AM ET [via Moreover - ZDNet] OpenLink Software has provided an Open Source benchmark utility that support Mac OS X, Linux, and UNIX. Thus, if mission critical database oriented performance is what is most relevant to your needs (as opposed to Photoshop) then simply download either one, or both of the following: OpenLink ODBC Bench (you can test TPC-A and TPC-C like performance of the G5 and compare against other platforms) via ODBC) OpenLink JDBC Bench (same thing using JDBC)</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<P>We all know that the only benchmark that matters, is the one that you run in-house using the systems that comprise your IT infrastructure. </P>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<P><A href="http://c.moreover.com/click/here.pl?r77267478">Apple's benchmarks under fire</A> ZDNet Jun 25 2003 7:13AM ET </P>
<P>[via <A href="http://www.moreover.com/">Moreover - ZDNet</A>]</P></BLOCKQUOTE>
<P>OpenLink Software has provided an Open Source benchmark utility that support Mac OS X, Linux, and UNIX. Thus, if mission critical database oriented performance is what is most relevant to your needs (as opposed to Photoshop) then simply download either one, or both of the following:</P>
<P><A href="http://oplweb2.openlinksw.com:8080/download/util.vsp">OpenLink ODBC Bench</A> (you can test TPC-A and TPC-C like performance of the G5 and compare against other platforms) via ODBC)</P>
<P><A href="http://oplweb2.openlinksw.com:8080/download/util.vsp">OpenLink JDBC Bench </A>(same thing using JDBC)</P>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-06-08#108">
  <rss:title>&lt;p&gt;When Mono is completed, Linux is the option for the desktop.&lt;/p&gt;</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-06-08T18:51:20Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">When Mono is completed, Linux is the option for the desktop. [From Frans Bouma&#39;s blog in Boldface, My comments in italics] Randy Holloway wrote about his vision on Linux and then especially about Linux on the desktop. I disagree with his vision, I think Linux is definitely an option for the desktop at the moment and thus also in the foreseably future. It will become the option for the desktop when Mono is completed. The reason for this is simple: a lot of Windows programs will be written using .NET. If you can run these programs on Linux too, using Mono, what&#39;s keeping you on Windows? Perhaps the games. But definitely not the business applications, since the Linux version for spreadsheets, browsers, wordprocessors, emailprograms and other every-day software are solid today, even when compared to Microsoft Office XP. Linux desktop office applications do not rival those of Windows, in particular Office 2003. We have to be careful when we make generic statements such as this becuase the end result is disappointment and frustation for corporate Linux neophyte. Imagine a corporate power user that has used Excel to produce Pivot tables (like I do) that provide me with a critical success factors dashboard for my enterprise. If I was to move to any of the incarnations of open office this would be lost. Now, for the corporate user -knowledge, information worker- that I believe Randy has in mind this remains a problem re. Linux as a desktop offering today. On the other hand, how true is the position that I presented above? By this I mean, how many knowledge workers actually make use of Pivot Tables in Excel? Something tells me I am the exception rather than the norm. Thus, moving away from Desktop productivity tools of type &quot;Office 200x&quot;, and looking at email, and web browsing etc. Linux certainly matches Windows pound for pound, but is this enough? What is the current &quot;activation threshold&quot; for Windows vs. Linux for a Desktop user (who just wants email and web browsing)? I think this is Linux distribution dependent, now the last time I attempted this experiment (at least over a year ago) Windows won flat out becuase I had to wrestle with X Configuration en route to getting a graphical desktop (I believe this has improved vastly of late, but I need to perform this experiment using current 8.x and higher Linux distros.). I&#39;ve hated Linux and especially its most hardcore supporters, for years. However, you can&#39;t have an unbiased vision on what is best for a given company to use as the OS of choice if you are biased yourself. Mono changed me, I really think Mono is the best Linux has ever experienced: it makes transitions of software written for the Windows platform to a free (as in beer, I don&#39;t believe in the GPL-philosophy) OS possible. Mono is going to be the most significant Linux &lt;--&gt; Windows harmonization effort over the long term. This is because parity will no longer be about getting the likes of Open Office to reach functional parity with &quot;Office 200x&quot; as future Windows applications will be &quot;managed code&quot; in nature (a strategic Microsoft goal over the long term), and Mono&#39;s goal is to run &quot;managed code&quot; outside the Windows platform (this applies to Linux, UNIX, and other platforms). Besides Mono, I do think Linux is a good platform to use for everyday business applications today, because the office tools can use Exchange, they can read/write MS Office documents, so why bother investing in MS software when you can save that money and choose the alternative? The only problem is: when you have a lot of desktops to admin as a sysadmin, and you want to do that with the easy tools in Windows server 2003, you&#39;re out of luck.  Linux is a good platform for everday business applications, but not quite good enough in the area of unravelling it&#39;s value proposition to the point of obvious simplification for corporate decision makers. This is the current hump in the road to this critical destination in my humble opinion. Randy and Frans are making very good points that shed light on some of the less covered aspects of the Linux vs. Windows debate.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<P>When Mono is completed, Linux is the option for the desktop.</P>
<P>[From <A href="http://weblogs.asp.net/fbouma/">Frans Bouma's blog</A>&nbsp;in Boldface, <EM>My comments in italics</EM>]</P>
<P>Randy Holloway <A href="http://weblogs.asp.net/rholloway/posts/8369.aspx">wrote</A> about his <A href="http://weblogs.asp.net/rholloway/posts/8370.aspx">vision on Linux</A> and then especially about Linux on the desktop. I disagree with his vision, I think Linux is definitely an option for the desktop at the moment and thus also in the foreseably future. It will become <EM>the</EM> option for the desktop when Mono is completed. The reason for this is simple: a lot of Windows programs will be written using .NET. If you can run these programs on Linux too, using Mono, what's keeping you on Windows? Perhaps the games. But definitely not the business applications, since the Linux version for spreadsheets, browsers, wordprocessors, emailprograms and other every-day software are solid <EM>today</EM>, even when compared to Microsoft Office XP. </P>
<P><EM>Linux desktop office applications do not rival those of Windows, in particular Office 2003. We have to be careful when we make generic statements such as this becuase the end result is disappointment and frustation for corporate Linux neophyte.</EM></P>
<P><EM>Imagine a corporate power user that has used Excel to produce Pivot tables (like I do) that provide me with a critical success factors dashboard for my enterprise. If I was to move to any of the incarnations of open office this would be lost. Now, for the corporate user -knowledge, information worker- that I believe Randy has in mind this remains a problem re. Linux as a desktop offering today.</EM></P>
<P><EM>On the other hand, how true is the position that I presented above? By this I mean, how many knowledge workers actually make use of Pivot Tables in Excel? Something tells me I am the exception rather than the norm. Thus, moving away from Desktop productivity tools of type "Office 200x", and looking at email, and web browsing etc. Linux certainly matches Windows pound for pound, but is this enough? What is the current "activation threshold" for Windows vs. Linux for a Desktop user (who just wants email and web browsing)? I think this is Linux distribution dependent, now the last time I attempted this experiment (at least over a year ago) Windows won flat out becuase I had to wrestle with X Configuration en route to getting a graphical desktop (I believe this has improved vastly of late, but I need to perform this experiment using current 8.x and higher Linux distros.).</EM></P>
<P>I've hated Linux and especially its most hardcore supporters, for years. However, you can't have an unbiased vision on what is best for a given company to use as the OS of choice if you are biased yourself. Mono changed me, I really think Mono is the best Linux has ever experienced: it makes transitions of software written for the Windows platform to a free (as in beer, I don't believe in the GPL-philosophy) OS possible.</P>
<P><EM>Mono is going to be the most significant Linux &lt;--&gt; Windows harmonization effort over the long term. This is because parity will no longer be about getting the likes of Open Office to reach functional parity with "Office 200x" as future Windows applications will be "managed code" in nature (a strategic Microsoft goal over the long term), and Mono's goal is to run "managed code" outside the Windows platform (this applies to Linux, UNIX, and other platforms).</EM></P>
<P>Besides Mono, I do think Linux is a good platform to use for everyday business applications today, because the office tools can use Exchange, they can read/write MS Office documents, so why bother investing in MS software when you can save that money and choose the alternative? The only problem is: when you have a lot of desktops to admin as a sysadmin, and you want to do that with the easy tools in Windows server 2003, you're out of luck.&nbsp;</P>
<P><EM>Linux is a good platform for everday business applications, but not quite good&nbsp;enough in the area of unravelling it's value proposition to the point of obvious simplification for&nbsp;corporate decision makers. This is the current hump in the road to this critical destination in my humble opinion.</EM></P>
<P><EM>Randy and Frans are making very good points that shed light on some of the less covered aspects of the Linux vs. Windows debate.</EM></P>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-06-08#261">
  <rss:title>&lt;p&gt;When Mono is completed, Linux is the option for the desktop.&lt;/p&gt;</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-06-08T18:51:20Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">When Mono is completed, Linux is the option for the desktop. [From Frans Bouma&#39;s blog in Boldface, My comments in italics] Randy Holloway wrote about his vision on Linux and then especially about Linux on the desktop. I disagree with his vision, I think Linux is definitely an option for the desktop at the moment and thus also in the foreseably future. It will become the option for the desktop when Mono is completed. The reason for this is simple: a lot of Windows programs will be written using .NET. If you can run these programs on Linux too, using Mono, what&#39;s keeping you on Windows? Perhaps the games. But definitely not the business applications, since the Linux version for spreadsheets, browsers, wordprocessors, emailprograms and other every-day software are solid today, even when compared to Microsoft Office XP. Linux desktop office applications do not rival those of Windows, in particular Office 2003. We have to be careful when we make generic statements such as this becuase the end result is disappointment and frustation for corporate Linux neophyte. Imagine a corporate power user that has used Excel to produce Pivot tables (like I do) that provide me with a critical success factors dashboard for my enterprise. If I was to move to any of the incarnations of open office this would be lost. Now, for the corporate user -knowledge, information worker- that I believe Randy has in mind this remains a problem re. Linux as a desktop offering today. On the other hand, how true is the position that I presented above? By this I mean, how many knowledge workers actually make use of Pivot Tables in Excel? Something tells me I am the exception rather than the norm. Thus, moving away from Desktop productivity tools of type &quot;Office 200x&quot;, and looking at email, and web browsing etc. Linux certainly matches Windows pound for pound, but is this enough? What is the current &quot;activation threshold&quot; for Windows vs. Linux for a Desktop user (who just wants email and web browsing)? I think this is Linux distribution dependent, now the last time I attempted this experiment (at least over a year ago) Windows won flat out becuase I had to wrestle with X Configuration en route to getting a graphical desktop (I believe this has improved vastly of late, but I need to perform this experiment using current 8.x and higher Linux distros.). I&#39;ve hated Linux and especially its most hardcore supporters, for years. However, you can&#39;t have an unbiased vision on what is best for a given company to use as the OS of choice if you are biased yourself. Mono changed me, I really think Mono is the best Linux has ever experienced: it makes transitions of software written for the Windows platform to a free (as in beer, I don&#39;t believe in the GPL-philosophy) OS possible. Mono is going to be the most significant Linux &lt;--&gt; Windows harmonization effort over the long term. This is because parity will no longer be about getting the likes of Open Office to reach functional parity with &quot;Office 200x&quot; as future Windows applications will be &quot;managed code&quot; in nature (a strategic Microsoft goal over the long term), and Mono&#39;s goal is to run &quot;managed code&quot; outside the Windows platform (this applies to Linux, UNIX, and other platforms). Besides Mono, I do think Linux is a good platform to use for everyday business applications today, because the office tools can use Exchange, they can read/write MS Office documents, so why bother investing in MS software when you can save that money and choose the alternative? The only problem is: when you have a lot of desktops to admin as a sysadmin, and you want to do that with the easy tools in Windows server 2003, you&#39;re out of luck.  Linux is a good platform for everday business applications, but not quite good enough in the area of unravelling it&#39;s value proposition to the point of obvious simplification for corporate decision makers. This is the current hump in the road to this critical destination in my humble opinion. Randy and Frans are making very good points that shed light on some of the less covered aspects of the Linux vs. Windows debate.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<P>When Mono is completed, Linux is the option for the desktop.</P>
<P>[From <A href="http://weblogs.asp.net/fbouma/">Frans Bouma's blog</A>&nbsp;in Boldface, <EM>My comments in italics</EM>]</P>
<P>Randy Holloway <A href="http://weblogs.asp.net/rholloway/posts/8369.aspx">wrote</A> about his <A href="http://weblogs.asp.net/rholloway/posts/8370.aspx">vision on Linux</A> and then especially about Linux on the desktop. I disagree with his vision, I think Linux is definitely an option for the desktop at the moment and thus also in the foreseably future. It will become <EM>the</EM> option for the desktop when Mono is completed. The reason for this is simple: a lot of Windows programs will be written using .NET. If you can run these programs on Linux too, using Mono, what's keeping you on Windows? Perhaps the games. But definitely not the business applications, since the Linux version for spreadsheets, browsers, wordprocessors, emailprograms and other every-day software are solid <EM>today</EM>, even when compared to Microsoft Office XP. </P>
<P><EM>Linux desktop office applications do not rival those of Windows, in particular Office 2003. We have to be careful when we make generic statements such as this becuase the end result is disappointment and frustation for corporate Linux neophyte.</EM></P>
<P><EM>Imagine a corporate power user that has used Excel to produce Pivot tables (like I do) that provide me with a critical success factors dashboard for my enterprise. If I was to move to any of the incarnations of open office this would be lost. Now, for the corporate user -knowledge, information worker- that I believe Randy has in mind this remains a problem re. Linux as a desktop offering today.</EM></P>
<P><EM>On the other hand, how true is the position that I presented above? By this I mean, how many knowledge workers actually make use of Pivot Tables in Excel? Something tells me I am the exception rather than the norm. Thus, moving away from Desktop productivity tools of type "Office 200x", and looking at email, and web browsing etc. Linux certainly matches Windows pound for pound, but is this enough? What is the current "activation threshold" for Windows vs. Linux for a Desktop user (who just wants email and web browsing)? I think this is Linux distribution dependent, now the last time I attempted this experiment (at least over a year ago) Windows won flat out becuase I had to wrestle with X Configuration en route to getting a graphical desktop (I believe this has improved vastly of late, but I need to perform this experiment using current 8.x and higher Linux distros.).</EM></P>
<P>I've hated Linux and especially its most hardcore supporters, for years. However, you can't have an unbiased vision on what is best for a given company to use as the OS of choice if you are biased yourself. Mono changed me, I really think Mono is the best Linux has ever experienced: it makes transitions of software written for the Windows platform to a free (as in beer, I don't believe in the GPL-philosophy) OS possible.</P>
<P><EM>Mono is going to be the most significant Linux &lt;--&gt; Windows harmonization effort over the long term. This is because parity will no longer be about getting the likes of Open Office to reach functional parity with "Office 200x" as future Windows applications will be "managed code" in nature (a strategic Microsoft goal over the long term), and Mono's goal is to run "managed code" outside the Windows platform (this applies to Linux, UNIX, and other platforms).</EM></P>
<P>Besides Mono, I do think Linux is a good platform to use for everyday business applications today, because the office tools can use Exchange, they can read/write MS Office documents, so why bother investing in MS software when you can save that money and choose the alternative? The only problem is: when you have a lot of desktops to admin as a sysadmin, and you want to do that with the easy tools in Windows server 2003, you're out of luck.&nbsp;</P>
<P><EM>Linux is a good platform for everday business applications, but not quite good&nbsp;enough in the area of unravelling it's value proposition to the point of obvious simplification for&nbsp;corporate decision makers. This is the current hump in the road to this critical destination in my humble opinion.</EM></P>
<P><EM>Randy and Frans are making very good points that shed light on some of the less covered aspects of the Linux vs. Windows debate.</EM></P>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-06-05#100">
  <rss:title>Linux vs SCO: An opinion from the BSD point of view.</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-06-06T02:47:06Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Linux vs SCO: An opinion from the BSD point of view. &lt;P&gt; Greg Lehey has written an excellent article for Daemon News on the Linux versus SCO debacle from the point of view of a BSD user. (Or at least from the point of view of one BSD user). &lt;P&gt; One particularly interesting idea: &lt;P&gt; &lt;blockquote&gt; &lt;quote&gt; Linux source code is freely available. UnixWare source code is not, even less than many other proprietary UNIX implementations. Thus it would be easier to copy code from Linux to UnixWare then from UnixWare to Linux. &lt;/quote&gt; &lt;/blockquote&gt; &lt;P&gt; Lehey also has a page tracking the debate. [via Meerkat: An Open Wire Service: O&#39;Reilly Network Weblogs]</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<A href="http://www.oreillynet.com/pub/wlg/3268">Linux vs SCO: An opinion from the BSD point of view.</A> &lt;P&gt; Greg Lehey has written an excellent article for Daemon News on the Linux versus SCO debacle from the point of view of a BSD user. (Or at least from the point of view of one BSD user). &lt;P&gt; One particularly interesting idea: &lt;P&gt; &lt;blockquote&gt; &lt;quote&gt; Linux source code is freely available. UnixWare source code is not, even less than many other proprietary UNIX implementations. Thus it would be easier to copy code from Linux to UnixWare then from UnixWare to Linux. &lt;/quote&gt; &lt;/blockquote&gt; &lt;P&gt; Lehey also has a page tracking the debate. [via <A href="http://meerkat.oreillynet.com/">Meerkat: An Open Wire Service: O'Reilly Network Weblogs</A>]
<DIV></DIV>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-06-05#253">
  <rss:title>Linux vs SCO: An opinion from the BSD point of view.</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-06-06T02:47:06Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Linux vs SCO: An opinion from the BSD point of view. &lt;P&gt; Greg Lehey has written an excellent article for Daemon News on the Linux versus SCO debacle from the point of view of a BSD user. (Or at least from the point of view of one BSD user). &lt;P&gt; One particularly interesting idea: &lt;P&gt; &lt;blockquote&gt; &lt;quote&gt; Linux source code is freely available. UnixWare source code is not, even less than many other proprietary UNIX implementations. Thus it would be easier to copy code from Linux to UnixWare then from UnixWare to Linux. &lt;/quote&gt; &lt;/blockquote&gt; &lt;P&gt; Lehey also has a page tracking the debate. [via Meerkat: An Open Wire Service: O&#39;Reilly Network Weblogs]</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<A href="http://www.oreillynet.com/pub/wlg/3268">Linux vs SCO: An opinion from the BSD point of view.</A> &lt;P&gt; Greg Lehey has written an excellent article for Daemon News on the Linux versus SCO debacle from the point of view of a BSD user. (Or at least from the point of view of one BSD user). &lt;P&gt; One particularly interesting idea: &lt;P&gt; &lt;blockquote&gt; &lt;quote&gt; Linux source code is freely available. UnixWare source code is not, even less than many other proprietary UNIX implementations. Thus it would be easier to copy code from Linux to UnixWare then from UnixWare to Linux. &lt;/quote&gt; &lt;/blockquote&gt; &lt;P&gt; Lehey also has a page tracking the debate. [via <A href="http://meerkat.oreillynet.com/">Meerkat: An Open Wire Service: O'Reilly Network Weblogs</A>]
<DIV></DIV>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-30#346">
  <rss:title>Microsoft Linux? Or Microsoft Unix?</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-05-30T21:25:37Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Microsoft Linux? Or Microsoft Unix? Ryan writes &quot;Microsoft working on a version of Linux? Mike Elgan writes that the Redmond company is losing its grip on the government market, and when the corporate market falls it will be motivated to release its own Linux distribution. Microsoft Linux may soon be more than just a hoax!&quot; Of course, the argument isn&#39;t based on any actual knowledge, but just a reasoned guess. This rumor/prediction seems to pop up every few months, and I usually just ignore it. However, now, the latest I, Cringely column has a much more well reasoned analysis of why he thinks Microsoft is going to launch their own Unix. He thinks that&#39;s the real reason behind their recent licensing of Unix IP from SCO. They realized that if they&#39;re going to launch their own Unix-style operating system, why not make it actually Unix, instead of Linux? As I said, these rumors (and hoaxes) have been around for ages, so I wouldn&#39;t put too much weight into them at this point. [via Techdirt]</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<a href="http://techdirt.com/articles/20030530/1425224.shtml">Microsoft Linux? Or Microsoft Unix?</a> <b>Ryan</b> writes <i>&quot;Microsoft working on a version of Linux? Mike Elgan writes that the Redmond company is losing its grip on the government market, and when the corporate market falls it will be motivated to release its own Linux distribution. <a href="http://www.mikeslist.com/65.htm">Microsoft Linux</a> may soon be more than just a <a href="http://www.mslinux.org/">hoax</a>!&quot;</i> Of course, the argument isn&#39;t based on any actual knowledge, but just a reasoned guess. This rumor/prediction seems to pop up every few months, and I usually just ignore it. However, now, the latest I, Cringely column has a much more well reasoned analysis of why he thinks <a href="http://www.pbs.org/cringely/pulpit/pulpit20030529.html">Microsoft is going to launch their own Unix</a>. He thinks that&#39;s the real reason behind their recent licensing of Unix IP from SCO. They realized that if they&#39;re going to launch their own Unix-style operating system, why not make it actually Unix, instead of Linux? As I said, these rumors (and hoaxes) have been around for ages, so I wouldn&#39;t put too much weight into them at this point. [via <a href="http://www.techdirt.com/">Techdirt</a>]
<div></div>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-28#336">
  <rss:title>Novell Claims Ownership of UNIX System V</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-05-28T13:46:25Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Novell Claims Ownership of UNIX System V A must read.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<P><A href="http://slashdot.org/article.pl?sid=03/05/28/1252229">Novell Claims Ownership of UNIX System V</A> </P>
<P><EM>A must read. </EM></P>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-23#330">
  <rss:title>&lt;a href=&quot;http://www.xulplanet.com/cgi-bin/ndeakin/homeN.cgi?ai=133&quot;&gt;Data Structures and RDF&lt;/a&gt;</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-05-24T02:27:45Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Data Structures and RDF Time to chime in on the RDF debate. There are four general ways of storing information: A list, in which one has a number of items, which may or not be related to one another. A table, in which one has a number of items (records), each with a distinct set of properties or columns. A tree, in which one has a hierarchy of items. A graph, in which one has a number of items (nodes), with the nodes connected to each other in some way. There are others, but they are more or less just variations of the same. There are examples all over of each type. Arrays are examples of lists. Of course, they are used all over the place. Relational databases typically store all of their data in tables. So do spreadsheets. Trees are used for mail or news messages and your bookmarks. XML is a syntax for specifying trees of information. The Windows and Classic Macintosh file systems are presented and/or stored as a tree. The Unix file system however isn&#39;t a tree. It&#39;s a graph. RDF is a graph. The Web is also a graph -- it&#39;s a bunch of pages connected via links. Each of the four storage methods, lists, tables, trees, and graphs, increase in complexity as you go up. Lists are simple to store. Graphs are the most difficult. Actually, that doesn&#39;t need to be the case. But, very few programming languages come with any kind of Graph structure ready to use. Due to the complexity, you should probably store data in the lowest type possible, depending on the kind of data you have. You can always use one of the structures higher than what is necessary. A list could be stored in a table with only one column, a table can be stored in a tree, where a root node has a set of records, each with a set of properties, and a tree is really a specialized form of graph. However, the reverse is not true. You can&#39;t store a graph in a tree, you can&#39;t store a tree in a table, and you can&#39;t store a table in a list. Any place where you see someone trying to is a hack. Many people don&#39;t know this though. So they just store everything in a tabular database or in XML, regardless of what it is. This has two problems. First, you get data that can be stored in a simpler format, stored in some more complex format. So you get people passing lists of things around using XML. Or, configuration files stored in XML. Second, you get people trying to coerce more complex data into a simpler format, so you might see people trying to shove trees of data into a database. Or you get serialized RDF written as XML. Many people think that XML is the ultimate format for storing data. It isn&#39;t. It can represent trees nicely, and it can do tables and lists if you really wanted it to, but it can&#39;t represent graphs, not cleanly anyway. Perhaps what is needed is an eXtensible Graph Language, which represents graphs of data. There is RDF-XML, and XGMML but both use a language for describing trees. Actually, it shouldn&#39;t be called the eXtensible Graph Language, because then people will get confused thinking it&#39;s like XML. Because a tree can be represented as a graph, all data could be represented in the Graph Language (not that it should be, of course), unlike XML which can&#39;t. Of course, this assumes there isn&#39;t some higher level structure above the graph. Long, long ago, people stored data in lists, because that was all that was available. Then, someone came up with the idea of storing data in tables. So relational databases came along and people moved up the ladder to tables. A few years ago, XML came along so data moved up again to trees. Can you guess what will happen next? The Semantic Web folks want us to move to using graphs. Should we move to graphs? Seems to be the next logical step in information evolution. What&#39;s holding us back? Well, it&#39;s probably too soon. The world is still in the tree phase. One day, graphs will start to become more popular -- it will just take time. In 30 years, someone might come up with something beyond graphs, and we&#39;ll all slowly switch to it as well. There&#39;s also the RSS in RDF debate. Many people don&#39;t see the value in storing RSS data in RDF. This is because the information stored in a single RSS file isn&#39;t a graph -- it&#39;s a tree, so plain-old XML actually makes more sense. Of course, the Semantic Web folks don&#39;t agree. Why? Because they aren&#39;t thinking in terms of a single RSS file - they are thinking of building giant collections of RSS data, all linked together so that it forms one giant - hey, it&#39;s not a tree - it&#39;s a graph. Then, you can search and navigate it like you can with the existing Web. But of course, the Semantic Web lets the servers and the software you&#39;re using, know more about what you&#39;re talking about. This is unlike current popular search engines like Google which are pretty much just guessing. You can make it better, sure, but the best way to acheive accuracy is if someone tells it the answer to begin with.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<a href="http://www.xulplanet.com/cgi-bin/ndeakin/homeN.cgi?ai=133">Data Structures and RDF</a> Time to chime in on the RDF debate. There are four general ways of storing information: A list, in which one has a number of items, which may or not be related to one another. A table, in which one has a number of items (records), each with a distinct set of properties or columns. A tree, in which one has a hierarchy of items. A graph, in which one has a number of items (nodes), with the nodes connected to each other in some way. There are others, but they are more or less just variations of the same. There are examples all over of each type. Arrays are examples of lists. Of course, they are used all over the place. Relational databases typically store all of their data in tables. So do spreadsheets. Trees are used for mail or news messages and your bookmarks. XML is a syntax for specifying trees of information. The Windows and Classic Macintosh file systems are presented and/or stored as a tree. The Unix file system however isn&#39;t a tree. It&#39;s a graph. RDF is a graph. The Web is also a graph -- it&#39;s a bunch of pages connected via links. Each of the four storage methods, lists, tables, trees, and graphs, increase in complexity as you go up. Lists are simple to store. Graphs are the most difficult. Actually, that doesn&#39;t need to be the case. But, very few programming languages come with any kind of Graph structure ready to use. Due to the complexity, you should probably store data in the lowest type possible, depending on the kind of data you have. You can always use one of the structures higher than what is necessary. A list could be stored in a table with only one column, a table can be stored in a tree, where a root node has a set of records, each with a set of properties, and a tree is really a specialized form of graph. However, the reverse is not true. You can&#39;t store a graph in a tree, you can&#39;t store a tree in a table, and you can&#39;t store a table in a list. Any place where you see someone trying to is a hack. Many people don&#39;t know this though. So they just store everything in a tabular database or in XML, regardless of what it is. This has two problems. First, you get data that can be stored in a simpler format, stored in some more complex format. So you get people passing lists of things around using XML. Or, configuration files stored in XML. Second, you get people trying to coerce more complex data into a simpler format, so you might see people trying to shove trees of data into a database. Or you get serialized RDF written as XML. Many people think that XML is the ultimate format for storing data. It isn&#39;t. It can represent trees nicely, and it can do tables and lists if you really wanted it to, but it can&#39;t represent graphs, not cleanly anyway. Perhaps what is needed is an eXtensible Graph Language, which represents graphs of data. There is RDF-XML, and XGMML but both use a language for describing trees. Actually, it shouldn&#39;t be called the eXtensible Graph Language, because then people will get confused thinking it&#39;s like XML. Because a tree can be represented as a graph, all data could be represented in the Graph Language (not that it should be, of course), unlike XML which can&#39;t. Of course, this assumes there isn&#39;t some higher level structure above the graph. Long, long ago, people stored data in lists, because that was all that was available. Then, someone came up with the idea of storing data in tables. So relational databases came along and people moved up the ladder to tables. A few years ago, XML came along so data moved up again to trees. Can you guess what will happen next? The Semantic Web folks want us to move to using graphs. Should we move to graphs? Seems to be the next logical step in information evolution. What&#39;s holding us back? Well, it&#39;s probably too soon. The world is still in the tree phase. One day, graphs will start to become more popular -- it will just take time. In 30 years, someone might come up with something beyond graphs, and we&#39;ll all slowly switch to it as well. There&#39;s also the RSS in RDF debate. Many people don&#39;t see the value in storing RSS data in RDF. This is because the information stored in a single RSS file isn&#39;t a graph -- it&#39;s a tree, so plain-old XML actually makes more sense. Of course, the Semantic Web folks don&#39;t agree. Why? Because they aren&#39;t thinking in terms of a single RSS file - they are thinking of building giant collections of RSS data, all linked together so that it forms one giant - hey, it&#39;s not a tree - it&#39;s a graph. Then, you can search and navigate it like you can with the existing Web. But of course, the Semantic Web lets the servers and the software you&#39;re using, know more about what you&#39;re talking about. This is unlike current popular search engines like Google which are pretty much just guessing. You can make it better, sure, but the best way to acheive accuracy is if someone tells it the answer to begin with.]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-23#59">
  <rss:title>&lt;a href=&quot;http://www.xulplanet.com/cgi-bin/ndeakin/homeN.cgi?ai=133&quot;&gt;Data Structures and RDF&lt;/a&gt;</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-05-24T02:27:45Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Data Structures and RDF Time to chime in on the RDF debate. There are four general ways of storing information: A list, in which one has a number of items, which may or not be related to one another. A table, in which one has a number of items (records), each with a distinct set of properties or columns. A tree, in which one has a hierarchy of items. A graph, in which one has a number of items (nodes), with the nodes connected to each other in some way. There are others, but they are more or less just variations of the same. There are examples all over of each type. Arrays are examples of lists. Of course, they are used all over the place. Relational databases typically store all of their data in tables. So do spreadsheets. Trees are used for mail or news messages and your bookmarks. XML is a syntax for specifying trees of information. The Windows and Classic Macintosh file systems are presented and/or stored as a tree. The Unix file system however isn&#39;t a tree. It&#39;s a graph. RDF is a graph. The Web is also a graph -- it&#39;s a bunch of pages connected via links. Each of the four storage methods, lists, tables, trees, and graphs, increase in complexity as you go up. Lists are simple to store. Graphs are the most difficult. Actually, that doesn&#39;t need to be the case. But, very few programming languages come with any kind of Graph structure ready to use. Due to the complexity, you should probably store data in the lowest type possible, depending on the kind of data you have. You can always use one of the structures higher than what is necessary. A list could be stored in a table with only one column, a table can be stored in a tree, where a root node has a set of records, each with a set of properties, and a tree is really a specialized form of graph. However, the reverse is not true. You can&#39;t store a graph in a tree, you can&#39;t store a tree in a table, and you can&#39;t store a table in a list. Any place where you see someone trying to is a hack. Many people don&#39;t know this though. So they just store everything in a tabular database or in XML, regardless of what it is. This has two problems. First, you get data that can be stored in a simpler format, stored in some more complex format. So you get people passing lists of things around using XML. Or, configuration files stored in XML. Second, you get people trying to coerce more complex data into a simpler format, so you might see people trying to shove trees of data into a database. Or you get serialized RDF written as XML. Many people think that XML is the ultimate format for storing data. It isn&#39;t. It can represent trees nicely, and it can do tables and lists if you really wanted it to, but it can&#39;t represent graphs, not cleanly anyway. Perhaps what is needed is an eXtensible Graph Language, which represents graphs of data. There is RDF-XML, and XGMML but both use a language for describing trees. Actually, it shouldn&#39;t be called the eXtensible Graph Language, because then people will get confused thinking it&#39;s like XML. Because a tree can be represented as a graph, all data could be represented in the Graph Language (not that it should be, of course), unlike XML which can&#39;t. Of course, this assumes there isn&#39;t some higher level structure above the graph. Long, long ago, people stored data in lists, because that was all that was available. Then, someone came up with the idea of storing data in tables. So relational databases came along and people moved up the ladder to tables. A few years ago, XML came along so data moved up again to trees. Can you guess what will happen next? The Semantic Web folks want us to move to using graphs. Should we move to graphs? Seems to be the next logical step in information evolution. What&#39;s holding us back? Well, it&#39;s probably too soon. The world is still in the tree phase. One day, graphs will start to become more popular -- it will just take time. In 30 years, someone might come up with something beyond graphs, and we&#39;ll all slowly switch to it as well. There&#39;s also the RSS in RDF debate. Many people don&#39;t see the value in storing RSS data in RDF. This is because the information stored in a single RSS file isn&#39;t a graph -- it&#39;s a tree, so plain-old XML actually makes more sense. Of course, the Semantic Web folks don&#39;t agree. Why? Because they aren&#39;t thinking in terms of a single RSS file - they are thinking of building giant collections of RSS data, all linked together so that it forms one giant - hey, it&#39;s not a tree - it&#39;s a graph. Then, you can search and navigate it like you can with the existing Web. But of course, the Semantic Web lets the servers and the software you&#39;re using, know more about what you&#39;re talking about. This is unlike current popular search engines like Google which are pretty much just guessing. You can make it better, sure, but the best way to acheive accuracy is if someone tells it the answer to begin with.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<a href="http://www.xulplanet.com/cgi-bin/ndeakin/homeN.cgi?ai=133">Data Structures and RDF</a> Time to chime in on the RDF debate. There are four general ways of storing information: A list, in which one has a number of items, which may or not be related to one another. A table, in which one has a number of items (records), each with a distinct set of properties or columns. A tree, in which one has a hierarchy of items. A graph, in which one has a number of items (nodes), with the nodes connected to each other in some way. There are others, but they are more or less just variations of the same. There are examples all over of each type. Arrays are examples of lists. Of course, they are used all over the place. Relational databases typically store all of their data in tables. So do spreadsheets. Trees are used for mail or news messages and your bookmarks. XML is a syntax for specifying trees of information. The Windows and Classic Macintosh file systems are presented and/or stored as a tree. The Unix file system however isn&#39;t a tree. It&#39;s a graph. RDF is a graph. The Web is also a graph -- it&#39;s a bunch of pages connected via links. Each of the four storage methods, lists, tables, trees, and graphs, increase in complexity as you go up. Lists are simple to store. Graphs are the most difficult. Actually, that doesn&#39;t need to be the case. But, very few programming languages come with any kind of Graph structure ready to use. Due to the complexity, you should probably store data in the lowest type possible, depending on the kind of data you have. You can always use one of the structures higher than what is necessary. A list could be stored in a table with only one column, a table can be stored in a tree, where a root node has a set of records, each with a set of properties, and a tree is really a specialized form of graph. However, the reverse is not true. You can&#39;t store a graph in a tree, you can&#39;t store a tree in a table, and you can&#39;t store a table in a list. Any place where you see someone trying to is a hack. Many people don&#39;t know this though. So they just store everything in a tabular database or in XML, regardless of what it is. This has two problems. First, you get data that can be stored in a simpler format, stored in some more complex format. So you get people passing lists of things around using XML. Or, configuration files stored in XML. Second, you get people trying to coerce more complex data into a simpler format, so you might see people trying to shove trees of data into a database. Or you get serialized RDF written as XML. Many people think that XML is the ultimate format for storing data. It isn&#39;t. It can represent trees nicely, and it can do tables and lists if you really wanted it to, but it can&#39;t represent graphs, not cleanly anyway. Perhaps what is needed is an eXtensible Graph Language, which represents graphs of data. There is RDF-XML, and XGMML but both use a language for describing trees. Actually, it shouldn&#39;t be called the eXtensible Graph Language, because then people will get confused thinking it&#39;s like XML. Because a tree can be represented as a graph, all data could be represented in the Graph Language (not that it should be, of course), unlike XML which can&#39;t. Of course, this assumes there isn&#39;t some higher level structure above the graph. Long, long ago, people stored data in lists, because that was all that was available. Then, someone came up with the idea of storing data in tables. So relational databases came along and people moved up the ladder to tables. A few years ago, XML came along so data moved up again to trees. Can you guess what will happen next? The Semantic Web folks want us to move to using graphs. Should we move to graphs? Seems to be the next logical step in information evolution. What&#39;s holding us back? Well, it&#39;s probably too soon. The world is still in the tree phase. One day, graphs will start to become more popular -- it will just take time. In 30 years, someone might come up with something beyond graphs, and we&#39;ll all slowly switch to it as well. There&#39;s also the RSS in RDF debate. Many people don&#39;t see the value in storing RSS data in RDF. This is because the information stored in a single RSS file isn&#39;t a graph -- it&#39;s a tree, so plain-old XML actually makes more sense. Of course, the Semantic Web folks don&#39;t agree. Why? Because they aren&#39;t thinking in terms of a single RSS file - they are thinking of building giant collections of RSS data, all linked together so that it forms one giant - hey, it&#39;s not a tree - it&#39;s a graph. Then, you can search and navigate it like you can with the existing Web. But of course, the Semantic Web lets the servers and the software you&#39;re using, know more about what you&#39;re talking about. This is unlike current popular search engines like Google which are pretty much just guessing. You can make it better, sure, but the best way to acheive accuracy is if someone tells it the answer to begin with.]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-22#52">
  <rss:title>&lt;a href=&quot;http://www.go-mono.com/index.html#May20th,2003:OpenLinkreleasesWineLibpatches.&quot;&gt;May 20th, 2003: OpenLink releases WineLib patches.&lt;/a&gt;</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-05-22T20:13:33Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">May 20th, 2003: OpenLink releases WineLib patches. OpenLink announced the release of Vladimir&#39;s work to turn Wine into a library that can be used dynamically from Mono. This work simplifies the work on System.Windows.Forms as it is no longer necessary have a special version of the GC, nor have a stub program.  [via Mono Project News]   What has happened here is that we have created an  a Linux/UNIX shared library based API for WINE (which is a WIN32 emulation layer). This will accelerate (via development simplication) the System.Windows.Forms namespace implementation within Mono.  </dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<A href="http://www.go-mono.com/index.html#May20th,2003:OpenLinkreleasesWineLibpatches.">May 20th, 2003: OpenLink releases WineLib patches.</A> OpenLink <A href="http://lists.ximian.com/archives/public/mono-winforms-list/2003-May/000284.html">announced</A> the release of Vladimir's work to turn Wine into a library that can be used dynamically from Mono. This work simplifies the work on System.Windows.Forms as it is no longer necessary have a special version of the GC, nor have a stub program.&nbsp; [via <A href="http://www.go-mono.com/">Mono Project News</A>]
<DIV><EM></EM>&nbsp;</DIV>
<DIV><EM>What has happened here is that we have created an&nbsp; a Linux/UNIX shared library based API for <A href="http://www.winehq.com">WINE</A> (which is a WIN32 emulation layer). This&nbsp;will accelerate (via development simplication) the System.Windows.Forms namespace implementation within Mono.</EM></DIV>
<DIV><EM></EM>&nbsp;</DIV>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-20#308">
  <rss:title>&lt;h2 class=&quot;title&quot; style=&quot;CLEAR: both&quot;&gt;The meaning of &lt;/h2&gt;</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-05-20T14:35:44Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">0</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[0]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-18#305">
  <rss:title>&lt;a href=&quot;http://c.moreover.com/click/here.pl?r72328568&quot;&gt;Microsoft to license SCO Group Unix rights&lt;/a&gt;</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-05-18T18:25:00Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Microsoft to license SCO Group Unix rights ZDNet May 19 2003 2:37AM ET [via Moreover - ZDNet] Houston! We have a problem.Note, that Bill Gates was an early backer of the Original SCO company (the one that licensed the AT&amp;T UNIX license), and this was prior to SCO acquiring Unixware (the AT&amp;T UNIX IP vehicle).  I think IBM and the other large Linux stake holders may have screwed up here, and Microsoft is going make this clearer in the not to distant future.</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<A href="http://c.moreover.com/click/here.pl?r72328568">Microsoft to license SCO Group Unix rights</A> ZDNet May 19 2003 2:37AM ET 
<DIV align=right>[via <A href="http://www.moreover.com/">Moreover - ZDNet</A>]
<DIV></DIV></DIV>Houston! We have a problem.<BR>Note, that Bill Gates was an early backer of the Original SCO company (the one that licensed the AT&amp;T UNIX license), and this was prior to SCO acquiring Unixware (the AT&amp;T UNIX IP vehicle).&nbsp; I think IBM and the other large Linux stake holders may have screwed up here, and Microsoft is going make this clearer in the not to distant future.]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-15#298">
  <rss:title>&lt;a href=&quot;http://chkpt.zdnet.com/chkpt/emailvideonews/www.cnet.com/video/synd/mail_redir2.html?page=http://www.news.com/,vid_win=http://news.com.com/1601-2-1000672.html&quot;&gt;Video&lt;/a&gt;</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-05-16T03:57:33Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Enjoy the Video . Virtuoso 64-Bit is becoming a priority, larger addressable memory space (we are talking about 512GB memory re. 64-Bit systems). You can now do on Windows what you could have done many years ago on IRIX and Digital UNIX :-)</dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<p>Enjoy the <a href="http://chkpt.zdnet.com/chkpt/emailvideonews/www.cnet.com/video/synd/mail_redir2.html?page=http://www.news.com/,vid_win=http://news.com.com/1601-2-1000672.html">Video</a> .</p>
<p>Virtuoso 64-Bit is becoming a priority, larger addressable memory space (we are talking about 512GB memory re. 64-Bit systems). </p>
<p>You can now do on Windows what you could have done many years ago on IRIX and Digital UNIX :-)</p>
<p></p>]]></content:encoded>
 </rss:item>
 <rss:item xmlns:rss="http://purl.org/rss/1.0/" rdf:about="http://www.openlinksw.com/blog/kidehen@openlinksw.com/blog/?date=2003-05-14#360">
  <rss:title>&lt;a href=&quot;http://chkpt.zdnet.com/chkpt/emailvideonews/www.cnet.com/video/synd/mail_redir2.html?page=http://www.news.com/,vid_win=http://news.com.com/1601-2-1000672.html&quot;&gt;Video&lt;/a&gt;</rss:title>
  <dc:date xmlns:dc="http://purl.org/dc/elements/1.1/">2003-05-14T16:55:05Z</dc:date>
  <dc:description xmlns:dc="http://purl.org/dc/elements/1.1/">Enjoy the Video . Virtuoso 64-Bit is becoming a priority, larger addressable memory space (we are talking about 512GB memory re. 64-Bit systems). You can now do on Windows what you could have done many years ago on IRIX and Digital UNIX :-)  </dc:description>
  <content:encoded xmlns:content="http://purl.org/rss/1.0/modules/content/"><![CDATA[<P>Enjoy the <A href="http://chkpt.zdnet.com/chkpt/emailvideonews/www.cnet.com/video/synd/mail_redir2.html?page=http://www.news.com/,vid_win=http://news.com.com/1601-2-1000672.html">Video</A> .</P>
<P>Virtuoso 64-Bit is becoming a priority, larger addressable memory space (we are talking about 512GB memory re. 64-Bit systems). </P>
<P>You can now do on Windows what you could have done many years ago on IRIX and Digital UNIX :-)</P>
<P>&nbsp;</P>]]></content:encoded>
 </rss:item>
</rdf:RDF>