<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://xml.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Articles by Coco Jaenicke</title>
 <link>http://xml.sys-con.com/</link>
 <description>Latest articles from Coco Jaenicke</description>
 <language>en</language>
 <copyright>Copyright 2008 </copyright>
 <generator></generator>
 <lastBuildDate>Mon, 01 Dec 2008 19:09:42 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>10</ttl>
<item>
 <title>Canonical Message Formats</title>
 <link>http://xml.sys-con.com/node/46310</link>
 <description>As the scope of enterprise integration grows, IT organizations are demanding greater efficiency and agility from their architectures and are moving away from point-to-point integration,which is proving to be increasingly cumbersome to build and maintain.&lt;p&gt;&lt;a href=&quot;http://xml.sys-con.com/node/46310&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 10 Sep 2004 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://xml.sys-con.com/node/46310</guid>
</item>
<item>
 <title>Don&#039;t Define a Data Model</title>
 <link>http://xml.sys-con.com/node/40507</link>
 <description>Traditional application development dictates that you define your data model first, and then design your applications around the data. As information changes and moves at ever-increasing speeds, being dependent on a rigid data model places a limit on how sophisticated integrated applications can get. But with extensible XML, that limitation is removed - applications can be separated from the information model in the same way that HTML and XML separate presentation from content.&lt;p&gt;&lt;a href=&quot;http://xml.sys-con.com/node/40507&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 24 Oct 2002 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://xml.sys-con.com/node/40507</guid>
</item>
<item>
 <title>The Object</title>
 <link>http://xml.sys-con.com/node/40491</link>
 <description>The object is certainly not a new concept, but Web services are considered new, difficult, and intimidating. Since a Web service can be thought of as a glorified object with standard interfaces, why isn&#039;t this old hat? Many of the difficulties of implementing services of any kind should be old hat, but in fact we&#039;ve been cheating all these years.&lt;p&gt;&lt;a href=&quot;http://xml.sys-con.com/node/40491&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 27 Sep 2002 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://xml.sys-con.com/node/40491</guid>
</item>
<item>
 <title>Middle-Tier Data Management</title>
 <link>http://xml.sys-con.com/node/40377</link>
 <description>XML databases are different from traditional databases, and they require a new set of features and metrics for evaluating them. In my last column  (XML-J, Vol. 3, issue 2) I talked about native XML database management systems (XDBMS), and I&#039;d like to follow up with how they differ from traditional databases and why this is significant.&lt;p&gt;&lt;a href=&quot;http://xml.sys-con.com/node/40377&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 25 Mar 2002 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://xml.sys-con.com/node/40377</guid>
</item>
<item>
 <title>Going Native</title>
 <link>http://xml.sys-con.com/node/40333</link>
 <description>As XML is put into production more frequently, many of the XML software product categories are beginning to gain clarity. One area that has seen several new entries is the XML database management system, or XDBMS. The word native is frequently used when describing XML database management systems. (It seems that the only adjective used more freely is first. And just for the record, the first three ship dates I found are eXcelon 3/1999, Software AG 10/1999, and IXIASOFT 1/2000 - all claiming to be first.)&lt;p&gt;&lt;a href=&quot;http://xml.sys-con.com/node/40333&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 25 Jan 2002 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://xml.sys-con.com/node/40333</guid>
</item>
<item>
 <title>Code Reuse: From Objects to Components to Services</title>
 <link>http://xml.sys-con.com/node/40289</link>
 <description>Now that the age of limitless optimism is over and it&#039;s trendy to be cynical, I hear many Web services cynics remark that there&#039;s nothing new here. They&#039;re just components. Been there, done that, and in fact we called it CORBA (or COM). This leads to the inevitable questions about what truly is new and different, and what is empty hype for yesterday&#039;s news.&lt;p&gt;&lt;a href=&quot;http://xml.sys-con.com/node/40289&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 03 Dec 2001 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://xml.sys-con.com/node/40289</guid>
</item>
<item>
 <title>Maximizing The Potential Of Web Services</title>
 <link>http://xml.sys-con.com/node/40251</link>
 <description>As the hype surrounding Web services continues to swirl, I&#039;d like to talk about when to choose a Web service over the many other communication options available. I&#039;ll start at the abstract level, looking at appropriate business objectives, and then sum up with a divide-and-conquer approach to getting there.&lt;p&gt;&lt;a href=&quot;http://xml.sys-con.com/node/40251&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 20 Sep 2001 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://xml.sys-con.com/node/40251</guid>
</item>
<item>
 <title>Web Services and XML</title>
 <link>http://xml.sys-con.com/node/40197</link>
 <description>In my last column (XML-J, Vol. 2, issue 1) I talked about Web services and how they can change the way we think about e-business and application development. This month I&#039;d like to elaborate on a few points and examine some of the market benefits in greater depth.&lt;p&gt;&lt;a href=&quot;http://xml.sys-con.com/node/40197&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 22 May 2001 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://xml.sys-con.com/node/40197</guid>
</item>
<item>
 <title>XML: Continuing to be Revolutionary</title>
 <link>http://xml.sys-con.com/node/40129</link>
 <description>I was looking through my previous column and was struck by two things. First, how there always seems to be a next level - it wasn&#039;t too long ago that we were awestruck by the fact that XML could represent actual data with those neat little tags. Now we&#039;re talking about representing entire partnerships in XML.&lt;p&gt;&lt;a href=&quot;http://xml.sys-con.com/node/40129&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 08 Jan 2001 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://xml.sys-con.com/node/40129</guid>
</item>
<item>
 <title>XML: Integrating E-Business</title>
 <link>http://xml.sys-con.com/node/40098</link>
 <description>In my last column, instead of talking about XML as a technology, I discussed the business benefits of this wonderful and distinctly different language and  focused on B2B applications as that&#039;s where XML has established a firm foothold. Now I&#039;d like to continue the discussion in that vein.&lt;p&gt;&lt;a href=&quot;http://xml.sys-con.com/node/40098&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 16 Oct 2000 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://xml.sys-con.com/node/40098</guid>
</item>
<item>
 <title>XML: True Collaboration</title>
 <link>http://xml.sys-con.com/node/40076</link>
 <description>Lo and behold! XML has found a home and is beginning to make an impact on the enterprise. XML used to be considered fabulously interesting (like a degree in philosophy); now it&#039;s considered an essential item in everyone&#039;s bag of tools (like a wrench). As this technology hits the next level of maturity, it&#039;s time to focus on its unique business benefits.&lt;p&gt;&lt;a href=&quot;http://xml.sys-con.com/node/40076&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Fri, 18 Aug 2000 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://xml.sys-con.com/node/40076</guid>
</item>
<item>
 <title>Extensibility or Fragmentation</title>
 <link>http://xml.sys-con.com/node/40063</link>
 <description>In my last column (XML-J, Vol. 1, issue 1) I talked about XML&#039;s extensibility and how it&#039;s the key to building dynamic systems. But that begs the question: Does the freedom to extend a data structure create new opportunities, or is it another example of flexibility run amok?&lt;p&gt;&lt;a href=&quot;http://xml.sys-con.com/node/40063&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Thu, 15 Jun 2000 00:00:00 EDT</pubDate>
 <guid isPermaLink="true">http://xml.sys-con.com/node/40063</guid>
</item>
<item>
 <title>XML: It&#039;s The &#039;X&#039; That Matters</title>
 <link>http://xml.sys-con.com/node/40034</link>
 <description>As XML survives its debutante ball and begins to be accepted by mainstream IT shops, it&#039;s being put to work, creating excitement among CIOs with its extensibility. Having had first-hand experience with several next-generation XML e-business application deployments, I&#039;d like to describe how the extensibility of XML is revolutionizing e-business, making it possible to finally develop applications that are flexible enough to keep pace with today&#039;s constantly changing business requirements.&lt;p&gt;&lt;a href=&quot;http://xml.sys-con.com/node/40034&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 28 Feb 2000 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://xml.sys-con.com/node/40034</guid>
</item>
<item>
 <title>SYS-CON Radio Interview with Coco Jaenicke</title>
 <link>http://xml.sys-con.com/node/40031</link>
 <description>XML-J: Would you care to comment on the state of XML technology in the industry today? Jaenicke: The official &#039;state&#039; of XML is that it&#039;s been accepted, but I don&#039;t think it&#039;s well understood. Most IT managers and project leaders have XML on some checklist somewhere, but few have yet incorporated IT in a strategic way.&lt;p&gt;&lt;a href=&quot;http://xml.sys-con.com/node/40031&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Mon, 28 Feb 2000 00:00:00 EST</pubDate>
 <guid isPermaLink="true">http://xml.sys-con.com/node/40031</guid>
</item>
</channel>
</rss>
