Index: openacs-4/packages/acs-core-docs/www/xml/engineering-standards/constraint-naming.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/engineering-standards/constraint-naming.xml,v
diff -u -r1.6.14.2 -r1.6.14.3
--- openacs-4/packages/acs-core-docs/www/xml/engineering-standards/constraint-naming.xml	23 Jun 2016 08:32:46 -0000	1.6.14.2
+++ openacs-4/packages/acs-core-docs/www/xml/engineering-standards/constraint-naming.xml	16 Jun 2017 17:19:52 -0000	1.6.14.3
@@ -29,7 +29,7 @@
 
 <para>
 <phrase>Why do we need a naming convention? </phrase>
-<ulink url="http://oradoc.photo.net/ora8doc/DOC/server803/A54647_01/ch2.htm#2956">Oracle limits names</ulink>, 
+<ulink url="https://docs.oracle.com/database/121/SQLRF/sql_elements008.htm#SQLRF00223">Oracle limits names</ulink>, 
 in general, to 30 characters, which is hardly enough for a human readable constraint name.
 </para>
 
@@ -40,9 +40,7 @@
 
 <para>
 We propose the following naming convention for all constraints, with
-the following abbreviations taken from Oracle Docs at 
-<ulink url="http://oradoc.photo.net/ora81/DOC/server.815/a67779/ch4e.htm#8953">
-http://oradoc.photo.net/ora81/DOC/server.815/a67779/ch4e.htm#8953</ulink>. 
+the following abbreviations taken from Oracle Docs. 
 Note that we shortened all of the constraint abbrevations to 
 two characters to save room.
 </para>