Index: openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp,v
diff -u -N -r1.2 -r1.3
--- openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp	7 Aug 2017 23:47:49 -0000	1.2
+++ openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp	8 Nov 2017 09:42:10 -0000	1.3
@@ -10,10 +10,7 @@
 		<div class="sect1">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="eng-standards-constraint-naming" id="eng-standards-constraint-naming"></a>Constraint naming
-standard</h2></div></div></div><div class="authorblurb">
-<p>By Michael Bryzek</p>
-OpenACS docs are written by the named authors, and may be edited by
-OpenACS documentation staff.</div><div class="sect2">
+standard</h2></div></div></div><span style="color: red">&lt;authorblurb&gt;</span><p><span style="color: red">By Michael Bryzek</span></p><span style="color: red">&lt;/authorblurb&gt;</span><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="eng-standards-constraint-naming-big-picture" id="eng-standards-constraint-naming-big-picture"></a>The Big
 Picture</h3></div></div></div><p>Constraint naming standard is important for one reason: The
@@ -22,8 +19,8 @@
 associate a particular constraint with our data model. This gives
 us two real advantages:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
 <li class="listitem"><p>We can quickly identify and fix any errors.</p></li><li class="listitem"><p>We can reliabily modify or drop constraints</p></li>
-</ul></div><div>Why do we need a naming convention?</div><p>
-<a class="ulink" href="https://docs.oracle.com/database/121/SQLRF/sql_elements008.htm#SQLRF00223" target="_top">Oracle limits names</a>, in general, to 30
+</ul></div><p>
+<span class="phrase">Why do we need a naming convention?</span><a class="ulink" href="https://docs.oracle.com/database/121/SQLRF/sql_elements008.htm#SQLRF00223" target="_top">Oracle limits names</a>, in general, to 30
 characters, which is hardly enough for a human readable constraint
 name.</p>
 </div><div class="sect2">
@@ -122,12 +119,13 @@
 constraints is optional...</h3></div></div></div><p>People disagree on whether or not we should be naming not null
 constraints. So, if you want to name them, please do so and follow
 the above naming standard. But, naming not null constraints is not
-a requirement.</p><div>About Naming the not null constraints</div><p>Though naming "not null" constraints doesn&#39;t help
+a requirement.</p><p><span class="phrase">About Naming the not null
+constraints</span></p><p>Though naming "not null" constraints doesn&#39;t help
 immeditately in error debugging (e.g. the error will say something
 like "Cannot insert null value into column"), we
 recommend naming not null constraints to be consistent in our
-naming of all constraints.</p><div class="cvstag">($&zwnj;Id: constraint-naming.xml,v 1.6.14.3
-2017/06/16 17:19:52 gustafn Exp $)</div>
+naming of all constraints.</p><p><span class="cvstag">($&zwnj;Id: constraint-naming.xml,v 1.7
+2017/08/07 23:47:54 gustafn Exp $)</span></p>
 </div>
 </div>
 <include src="/packages/acs-core-docs/lib/navfooter"