--- a/ldp-ucr.html	Tue Sep 24 11:38:09 2013 +0100
+++ b/ldp-ucr.html	Tue Sep 24 11:49:13 2013 +0100
@@ -107,6 +107,11 @@
 				title:    "Constrained Application Protocol",
 				href:     "http://tools.ietf.org/html/draft-ietf-core-coap-18",
 				publisher:  "IETF"
+			},
+			"COAP-MAP": {
+				title:    "Best Practices for HTTP-CoAP Mapping Implementation",
+				href:     "http://tools.ietf.org/html/draft-castellani-core-http-mapping-07",
+				publisher:  "IETF"
 			}
 		  }
       };
@@ -617,12 +622,9 @@
 		interfaces also on resource constrained devices, adhering to the
 		Linked Data principles. Due to the limited resources available,
 		both on the device and in the network (such as bandwidth, energy,
-		and memory) a solution based on <em>SPARQL Update</em> is at the current point
+		and memory) a solution based on <em>SPARQL Update</em> [[RDF-SPARQL-UPDATE]] is at the current point
 		in time considered not to be useful and/or feasible. An approach
-		based on the <a
-			href="http://tools.ietf.org/html/draft-castellani-core-http-mapping"
-			title="http://tools.ietf.org/html/draft-castellani-core-http-mapping"
-			rel="nofollow">HTTP-CoAP Mapping</a> would enable constrained
+		based on the HTTP-CoAP Mapping [[COAP-MAP]] would enable constrained
 		devices to directly participate in a Linked Data-based
 		environment.
 	</p>