<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://javiermariscal.sys-con.com"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Latest News from Javier Mariscal</title>
 <link>http://javiermariscal.sys-con.com/</link>
 <description>Latest News from Javier Mariscal</description>
 <language>en</language>
 <copyright>Copyright 2009 Ulitzer.com</copyright>
 <generator>Ulitzer.com</generator>
 <lastBuildDate>Mon, 07 Dec 2009 09:27:42 EST</lastBuildDate>
 <docs>http://backend.userland.com/rss</docs>
 <ttl>360</ttl>
<item>
 <title>Pragmatic SOA Interoperability</title>
 <link>http://javiermariscal.sys-con.com/node/393668</link>
 <description>A well-planned Web Service interoperability environment begins by clearly defining who your Web Service consumers are now and in the future. There was a time not so long ago when you could count on a fairly homogenous consumer population. This was about the same time that you were happy just to be able to get a Web Service running in the first place and finding a consumer who could actually interact with your Web Service was cause for celebration. Those days have changed however and Web Services interoperability, once a &#039;fancy&#039; addition to your SOA design, is now a key and indispensable requirement in most SOA scenarios.&lt;p&gt;&lt;a href=&quot;http://javiermariscal.sys-con.com/node/393668&quot; target=&quot;_blank&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <pubDate>Tue, 03 Jul 2007 06:30:00 EDT</pubDate>
 <guid isPermaLink="true">http://javiermariscal.sys-con.com/node/393668</guid>
 <comments>http://javiermariscal.sys-con.com/node/393668#feedback</comments>
</item>
</channel>
</rss>
