<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.itworld.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>data format</title>
 <link>http://www.itworld.com/taxonomy/term/461/all</link>
 <description></description>
 <language>xx</language>
<item>
 <title>Connecting A to B: APIs or data formats?</title>
 <link>http://www.itworld.com/api-data-format-nlstipsm-080306</link>
 <description>Normally in enterprise application integration, when we say &quot;send X to Y&quot;, there are two distinct aspects to be ironed out. The first is the &quot;how&quot; part. The second is the &quot;what&quot; part. When thinking of the &quot;how&quot; part, thoughts turn to things like interfaces and APIs and function calls and so on. When thinking of the &quot;what&quot; part, thoughts turn to things like strings and tables and integers and data structures. All successful examples of interconnecting A and B in EAI feature both &quot;how&quot; and &quot;what&quot;. Unfortunately, the two can get terribly inter-twined leading to integration strategies that are difficult to develop, deploy and debug.
</description>
 <comments>http://www.itworld.com/api-data-format-nlstipsm-080306#comments</comments>
 <category domain="http://www.itworld.com/software">Software</category>
 <category domain="http://www.itworld.com/how">How-to</category>
 <category domain="http://www.itworld.com/api">API</category>
 <category domain="http://www.itworld.com/data-format">data format</category>
 <category domain="http://www.itworld.com/temporal-coupling">temporal coupling</category>
 <pubDate>Thu, 06 Mar 2008 20:46:05 -0500</pubDate>
 <dc:creator>jnaze</dc:creator>
 <guid isPermaLink="false">873 at http://www.itworld.com</guid>
</item>
</channel>
</rss>
