Prepare article for publication

Author: ploeh

_posts/2024-03-03-service-compatibility-is-determined-based-on-policy.html _posts/2024-04-29-service-compatibility-is-determined-based-on-policy.html

@@ -2,7 +2,7 @@
 layout: post
 title: "Service compatibility is determined based on policy"
 description: "A reading of the fourth Don Box tenet, with some commentary."
-date: 2024-03-03 18:49 UTC
+date: 2024-04-29 11:12 UTC
 tags: [Services, Architecture]
 ---
 {% include JB/setup %}
@@ -12,7 +12,7 @@
         <em>{{ page.description }}</em>
     </p>
     <p>
-        This article is part of a series titled <a href="">The four tenets of SOA revisited</a>. In each of these articles, I'll pull one of <a href="https://en.wikipedia.org/wiki/Don_Box">Don Box</a>'s <em>four tenets of service-oriented architecture</em> (SOA) out of the <a href="https://learn.microsoft.com/en-us/archive/msdn-magazine/2004/january/a-guide-to-developing-and-running-connected-systems-with-indigo">original MSDN Magazine article</a> and add some of my own commentary. If you're curious why I do that, I cover that in the introductory article.
+        This article is part of a series titled <a href="/2024/03/04/the-four-tenets-of-soa-revisited">The four tenets of SOA revisited</a>. In each of these articles, I'll pull one of <a href="https://en.wikipedia.org/wiki/Don_Box">Don Box</a>'s <em>four tenets of service-oriented architecture</em> (SOA) out of the <a href="https://learn.microsoft.com/en-us/archive/msdn-magazine/2004/january/a-guide-to-developing-and-running-connected-systems-with-indigo">original MSDN Magazine article</a> and add some of my own commentary. If you're curious why I do that, I cover that in the introductory article.
     </p>
     <p>
         In this article, I'll go over the fourth tenet, quoting from the MSDN Magazine article unless otherwise indicated.
@@ -32,13 +32,13 @@ <h3 id="57382e74449c40409a7d73d91bc5fd14">
         </p>
     </blockquote>
     <p>
-        As you can tell, this description is the shortest of the four. This is also the point where I begin to suspect that my reading of <a href="">the third tenet</a> may deviate from what Don Box originally had in mind.
+        As you can tell, this description is the shortest of the four. This is also the point where I begin to suspect that my reading of <a href="/2024/04/15/services-share-schema-and-contract-not-class">the third tenet</a> may deviate from what Don Box originally had in mind.
     </p>
     <p>
-        This tenet is also the most baffling to me. As I understand it, the motivation behind the four tenets was to describe the assumptions about the systems that people would develop with <a href="https://en.wikipedia.org/wiki/Windows_Communication_Foundation">Windows Communication Foundation</a> (WCF), or <a href="https://en.wikipedia.org/wiki/SOAP">SOAP</a> in general.
+        This tenet is also the most baffling to me. As I understand it, the motivation behind the four tenets was to describe assumptions about the kind of systems that people would develop with <a href="https://en.wikipedia.org/wiki/Windows_Communication_Foundation">Windows Communication Foundation</a> (WCF), or <a href="https://en.wikipedia.org/wiki/SOAP">SOAP</a> in general.
     </p>
     <p>
-        While I worked with WCF for a decade, the above description doesn't ring a bell. Reading it now, the description of <em>policy</em> sounds more like a system such as <a href="https://clojure.org/about/spec">clojure.spec</a>, although that's not something I now much about either. I don't recall WCF ever having a machine-readable policy subsystem, and if it had, I never encountered it.
+        While I worked with WCF for a decade, the above description doesn't ring a bell. Reading it now, the description of <em>policy</em> sounds more like a system such as <a href="https://clojure.org/about/spec">clojure.spec</a>, although that's not something I know much about either. I don't recall WCF ever having a machine-readable policy subsystem, and if it had, I never encountered it.
     </p>
     <p>
         It does seem, however, as though what I interpret as <em>contract</em>, Don Box called <em>policy</em>.