--- a/trig/index.html	Sun Dec 22 22:41:04 2013 +0100
+++ b/trig/index.html	Sun Dec 22 22:53:17 2013 +0100
@@ -839,8 +839,8 @@
           <dd>TriG is used to express arbitrary application data; security considerations will vary by domain of use. Security tools and protocols applicable to text (e.g. PGP encryption, MD5 sum validation, password-protected compression) may also be used on TriG documents. Security/privacy protocols must be imposed which reflect the sensitivity of the embedded information.</dd>
           <dd>TriG can express data which is presented to the user, for example, RDF Schema labels. Application rendering strings retrieved from untrusted TriG documents must ensure that malignant strings may not be used to mislead the reader. The security considerations in the media type registration for XML ([[!RFC3023]] section 10) provide additional guidance around the expression of arbitrary data and markup.</dd>
           <dd>TriG uses IRIs as term identifiers. Applications interpreting data expressed in TriG should address the security issues of
-      <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a> [[!RFC3987]] Section 8, as well as
-      <a class="norm" href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource Identifier (URI): Generic Syntax</a> [[!RFC3986]] Section 7.</dd>
+      <em>Internationalized Resource Identifiers (IRIs)</em> [[!RFC3987]] Section 8, as well as
+      <em>Uniform Resource Identifier (URI): Generic Syntax</em> [[!RFC3986]] Section 7.</dd>
 
           <dd>Multiple IRIs may have the same appearance. Characters in different scripts may
     look similar (a Cyrillic &quot;&#1086;&quot; may appear similar to a Latin &quot;o&quot;). A character followed