<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: pete-lacey</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/pete-lacey.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2007-10-06T01:44:26+00:00</updated><author><name>Simon Willison</name></author><entry><title>Quoting Pete Lacey</title><link href="https://simonwillison.net/2007/Oct/6/pete/#atom-tag" rel="alternate"/><published>2007-10-06T01:44:26+00:00</published><updated>2007-10-06T01:44:26+00:00</updated><id>https://simonwillison.net/2007/Oct/6/pete/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://wanderingbarque.com/nonintersecting/2007/10/05/what-is-soa/"&gt;&lt;p&gt;SOA [...] is the generally held belief that when implementing systems one should expose system functionality for general consumption directly from the network, as well as or instead of burying it behind a user interface.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://wanderingbarque.com/nonintersecting/2007/10/05/what-is-soa/"&gt;Pete Lacey&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/definitions"&gt;definitions&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/pete-lacey"&gt;pete-lacey&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/service-oriented-architecture"&gt;service-oriented-architecture&lt;/a&gt;&lt;/p&gt;



</summary><category term="definitions"/><category term="pete-lacey"/><category term="service-oriented-architecture"/></entry></feed>