<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>John's Examples</title><link>http://www.objectech.com/exblog/exblogrss.xml</link><description>OO, SOA, XML and other examples and tutorials</description><language>en</language><docs>http://blogs.law.harvard.edu/tech/rss</docs><generator>exblog/1.0</generator><item><title>Five SOA Pitfalls</title><pubDate>2009-04-25T10:33:00</pubDate><link>http://www.objectech.com/exblog/5SOAPitfalls.html</link><category/><guid isPermaLink="true">http://www.objectech.com/exblog/5SOAPitfalls.html</guid><description>
                Service Oriented Architecture (SOA) is one of the most important developments 
                in recent IT history. There is a strong sense of urgency to get started. There are, 
                however, several pitfalls which can seriously delay or completely derail an effort 
                to implement an SOA.
            </description></item><item><title>XSLT 2.0 - Invoice example</title><pubDate>2009-04-22T19:47:00</pubDate><link>http://www.objectech.com/exblog/xsl_2.0_invoice.html</link><category/><guid isPermaLink="true">http://www.objectech.com/exblog/xsl_2.0_invoice.html</guid><description>
                We create an invoice XML and schema, and an XSL stylesheet to 
                render the XML in HTML. In the process we use some very handy XSLT and 
                XPATH 2.0 additions.
                &lt;br/&gt;&lt;br/&gt;
                We also deal with derived data - subtotals and totals. 
            </description></item></channel></rss>
