diff --git a/AssurancePolicy.html b/AssurancePolicy.html
index d1adf69..f5e1141 100644
--- a/AssurancePolicy.html
+++ b/AssurancePolicy.html
@@ -186,149 +186,6 @@ different language or country variations,
 and transliterations of characters in a name.
 </p>
 
-
-<!--
-FOLLOWING GOES TO ASSURER HANDBOOK
-<h3><a name=""> </a>Comparison of names</h3>
-<p><a href="http://en.wikipedia.org/wiki/Transliteration" target="_blank">Transliteration</a>
-of characters as defined in the transliteration character table (<a href="http://svn.cacert.org/CAcert/Policies/transtab.utf" target="_blank">UTF
-Transtab</a>) for names is permitted, but the result must be
-7-bit
-ASCII for the full name. Transliteration is one way and is towards
-7-bit ASCII. Transliteration is a way to compare two names. However
-transliteration of a Name makes the Name less discriminative.</p>
-<p>In general names are handled case insensitively.</p>
-<p>Abbreviation of second given name(s), middle name(s),
-titles and name extensions in the name of an individual to one
-character and the dot indicating the abbreviation, is permitted. If
-the first given name in the ID document is abbreviated, the first
-given name in the web account Name may be abbreviated. Abbreviation
-of a name makes the name less discriminative.</p>
-<p>A Name on an ID which has initials (abbreviations) for
-titles, name extensions and given names, and/or transliterations as
-defined in the transliteration table can be taken into account for
-assurance for a Name in the account which is not abbreviated or
-transliterated.</p>
-<p>Titles and name extensions in the name of an individual
-may be omitted.</p>
-<p>The assurance ambition is to pursue
-a highly discriminative assured Name in the account. The ambition is
-to have only a Name in the account which has no abbreviation(s), no
-transliteration and is case sensitive.</p>
-
-FOLLOWING GOES TO Certficate Implementation Policy
-<h3><a name=""> </a>Names on the certificate issued by CAcert</h3>
-<p>The Certificate Implementation Policy (<a href="http://svn.cacert.org/CAcert/Policies/CertificateImplementationPolicy.html" target="_blank">CIP</a>)
-will define the fields added by CAcert on the issued certificate on
-request of the Member.</p>
-<p>The Common Name and related certificate fields in the
-issued certificate is dependent on the assurance of the Name in the
-web account. Abbreviation and transliteration handling in the CN is
-defined in the Certificate Implementation Policy and is similar to
-the name comparison as defined in this policy. However the Common
-Name may become less discriminative as than
-the assured Name as the unique certificate serial number will lead to
-the account of the individual in a unique way, and in this way to the
-Name and email address of the individual or organisation. The first
-given name in the Common Name may be abbreviated on request.</p>
-<p>The certificate issued by CAcert can have on request of
-the Member the SubjAltName field. The name as defined by the Member
-is not checked by CAcert.</p>
-<table border="1" cellpadding="2" cellspacing="0">
-<tbody>
-<tr>
-<th width="25%">
-<p><i>name on the ID</i></p>
-</th>
-<th width="25%">
-<p><i>assured Name in the account</i></p>
-</th>
-<th width="25%">
-<p><i>name in the certificate request</i></p>
-</th>
-<th width="25%">
-<p><i>name on the issued certificate</i></p>
-</th>
-</tr>
-<tr>
-<td>
-<p>Maria Kate Märvel-Java  </p>
-</td>
-<td>
-<p>Maria K. Maervel-Java</p>
-</td>
-<td>
-<p>M. K. Märvel-Java</p>
-</td>
-<td>
-<p>Maria K. Maervel-Java</p>
-</td>
-</tr>
-<tr>
-<td>
-<p>prof. dr. John K. Marvel</p>
-</td>
-<td>
-<p>John K. Marvel</p>
-</td>
-<td>
-<p>John K. Marvel</p>
-</td>
-<td>
-<p>John K. Marvel</p>
-</td>
-</tr>
-<tr>
-<td>
-<p>Moeria Koete v. Java</p>
-</td>
-<td>
-<p>Möria Kœté von Java</p>
-</td>
-<td>
-<p>Möria K. v. Java</p>
-</td>
-<td>
-<p>Möria K. v. Java</p>
-</td>
-</tr>
-<tr>
-<td>
-<p>Jamé de Häring sr</p>
-</td>
-<td>
-<p>Jame de Haering</p>
-</td>
-<td>
-<p>J. d. Häring</p>
-</td>
-<td>
-<p>J. d. Haering</p>
-</td>
-</tr>
-<tr>
-<td>
-<p>Jame d. Haering sr</p>
-</td>
-<td>
-<p>dr Jamé de Häring</p>
-</td>
-<td>
-<p>John de Haering</p>
-</td>
-<td>
-<p>dr Jamé de Häring</p>
-</td>
-</tr>
-</tbody>
-</table>
-<p align="center"><font size="2">table
-Examples of names in
-different contexts</font></p>
--->
-
-
-
 <h3><a name="2.3">2.3.</a> Status and Capabilities</h3>
 <p>
 A Name which has reached
diff --git a/X509ImplementationPolicy.html b/X509ImplementationPolicy.html
index 61237bf..2e82649 100644
--- a/X509ImplementationPolicy.html
+++ b/X509ImplementationPolicy.html
@@ -34,9 +34,16 @@ type="value" (e.g. "CN=Saskia the Mystical/emailAddress=sky@limit.net") on the i
 Subject and SubjectAlternativeName may be used in the Certificate Signing Request (CSR) sent to CAcert.
 CAcert will use this information as well information checked from assurances and other means to assemble the Subject and SubjectAlternativeName records.
 </p>
-<P>
-Other documents: RFC 3039 Qualified Certificate Profile.
-</p>
+		<h3>
+			0.1 Other Documents
+		</h3>
+<ul>
+     <li> See also for the current working documentation
+          for this subject:
+          <a href="http://svn.cacert.org/CAcert/policy.htm#p3.1">
+          CPS (wip) 3.1 Naming </a>. </li>
+     <li> RFC 3039 Qualified Certificate Profile. </li>
+</ul>
 		<h2>
 			1. Information Policies
 		</h2>
@@ -251,5 +258,119 @@ guaranteed). CSR can have user provided "Subject" X.501 information.
 		<p>
 			<a href="http://validator.w3.org/check?uri=referer"><img src="../Images/valid-xhtml11-blue" alt="Valid XHTML 1.1" height="31" width="88" style="border-style: none;" /></a>
 		</p>
+
+		<h2>
+			A1. Notes on Transliterations in Names
+		</h2>
+<p align="center"> <font color="green"><i>
+   Following notes were in the Assurance Policy but now moved to here
+   for consideration.
+</font></i></p>
+
+<p>The Common Name and related certificate fields in the
+issued certificate is dependent on the assurance of the Name in the
+web account. Abbreviation and transliteration handling in the CN is
+defined in the Certificate Implementation Policy and is similar to
+the name comparison as defined in this policy. However the Common
+Name may become less discriminative as than
+the assured Name as the unique certificate serial number will lead to
+the account of the individual in a unique way, and in this way to the
+Name and email address of the individual or organisation. The first
+given name in the Common Name may be abbreviated on request.</p>
+<p>The certificate issued by CAcert can have on request of
+the Member the SubjAltName field. The name as defined by the Member
+is not checked by CAcert.</p>
+<table border="1" cellpadding="2" cellspacing="0">
+<tbody>
+<tr>
+<th width="25%">
+<p><i>name on the ID</i></p>
+</th>
+<th width="25%">
+<p><i>assured Name in the account</i></p>
+</th>
+<th width="25%">
+<p><i>name in the certificate request</i></p>
+</th>
+<th width="25%">
+<p><i>name on the issued certificate</i></p>
+</th>
+</tr>
+<tr>
+<td>
+<p>Maria Kate Märvel-Java  </p>
+</td>
+<td>
+<p>Maria K. Maervel-Java</p>
+</td>
+<td>
+<p>M. K. Märvel-Java</p>
+</td>
+<td>
+<p>Maria K. Maervel-Java</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>prof. dr. John K. Marvel</p>
+</td>
+<td>
+<p>John K. Marvel</p>
+</td>
+<td>
+<p>John K. Marvel</p>
+</td>
+<td>
+<p>John K. Marvel</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Moeria Koete v. Java</p>
+</td>
+<td>
+<p>Möria Kœté von Java</p>
+</td>
+<td>
+<p>Möria K. v. Java</p>
+</td>
+<td>
+<p>Möria K. v. Java</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Jamé de Häring sr</p>
+</td>
+<td>
+<p>Jame de Haering</p>
+</td>
+<td>
+<p>J. d. Häring</p>
+</td>
+<td>
+<p>J. d. Haering</p>
+</td>
+</tr>
+<tr>
+<td>
+<p>Jame d. Haering sr</p>
+</td>
+<td>
+<p>dr Jamé de Häring</p>
+</td>
+<td>
+<p>John de Haering</p>
+</td>
+<td>
+<p>dr Jamé de Häring</p>
+</td>
+</tr>
+</tbody>
+</table>
+<p align="center"><font size="2"><b>table XXXX:</b>
+Examples of names in
+different contexts</font></p>
+
 	</body>
 </html>