--- a/ldp-ucr.html	Tue Sep 24 10:56:08 2013 +0100
+++ b/ldp-ucr.html	Tue Sep 24 11:12:35 2013 +0100
@@ -83,6 +83,10 @@
 			"OSLC": {
 				title:    "Open Services for Lifecycle Collaboration",
 				href:     "http://open-services.net/"
+		    },
+			"XO": {
+				title:    "SemanticXO",
+				href:     "http://worldwidesemanticweb.org/projects/semanticxo/"
 		    }
 		  }
       };
@@ -164,7 +168,7 @@
 			This document redacts a number of user stories around the theme of read/writeable linked data.
 			Analysis of each user story reveals a
 			number of (functional) use cases and other non-functional
-			requirements. See <i>Device API Access Control Use Cases and Requirements</i> [[DAP-REQS]] for a good example
+			requirements. See <em>Device API Access Control Use Cases and Requirements</em> [[DAP-REQS]] for a good example
 			of user stories and their analysis.</li>
 	</ul>
 	<ul>
@@ -177,14 +181,14 @@
 			use case indexing in this document is based on rdb2rdf
 			use cases [[RDB2RDF-UC]]. A variety of styles may be used to capture use cases,
 			from a simple narrative to a structured description with actors,
-			pre/post conditions, step-by-step behaviors (as in <i>POWDER:
-			Use Cases and Requirements</i> [[POWDER-USE-CASES]]), and non-functional requirements
+			pre/post conditions, step-by-step behaviors (as in <em>POWDER:
+			Use Cases and Requirements</em> [[POWDER-USE-CASES]]), and non-functional requirements
 			raised by the use case.</li>
 	</ul>
 	<ul>
 		<li><b>Scenarios</b> are used to model the functional requirements of a use case and focus on a use case in action. Scenarios may range from
-			lightweight narratives as seen in <i>Use
-			cases and requirements for Media Fragments</i> [[MEDIA-FRAGMENTS-REQS]], to being formally
+			lightweight narratives as seen in <em>Use
+			cases and requirements for Media Fragments</em> [[MEDIA-FRAGMENTS-REQS]], to being formally
 			modeled as interaction diagrams. Each use case includes at
 			least a primary scenario, and possibly other alternative
 			scenarios.</li>
@@ -328,7 +332,7 @@
 	<h2 id="story-lld"><dfn>Library Linked Data</dfn></h2>
 	<p>
 		The W3C Library Linked Data Working Group has a number of use
-		cases cited in their <i>Use Case Report</i> [[LLD-UC]]. These referenced use cases focus on the
+		cases cited in their <em>Use Case Report</em> [[LLD-UC]]. These referenced use cases focus on the
 		need to extract and correlate library data from disparate sources.
 		Variants of these use cases that can provide consistent formats,
 		as well as ways to improve or update the data, would enable
@@ -508,7 +512,7 @@
 	<p>The transfer of an arbitrary payload of RDF data could be
 		implemented through a container mechanism, adding and removing
 		sets of RDF triples to it. Currently, the 
-		"SemanticXO" project uses named graphs and the graph store protocol to
+		SemanticXO [[XO]] project uses named graphs and the graph store protocol to
 		create/delete/copy graphs across the nodes but this (almost)
 		imposes the usage of a triple store. Unfortunately, triple stores
 		are rather demanding pieces of software that are not always usable
@@ -1387,9 +1391,9 @@
 <> xhv:next &lt;http://example.com/1234567890&gt;.
 		</pre>
 		
-<p>When the client requests the resource identified by <i>next</i>, the response includes additional content that can be merged with the earlier data to construct a more complete model of the originally requested resource. It may also contain further <i>next</i> links, which may be requested in turn.</p> 
+<p>When the client requests the resource identified by <em>next</em>, the response includes additional content that can be merged with the earlier data to construct a more complete model of the originally requested resource. It may also contain further <em>next</em> links, which may be requested in turn.</p> 
 		
-<p>The following representation is the response to the resource identified by <i>next</i>, completing the contacts list.</p>
+<p>The following representation is the response to the resource identified by <em>next</em>, completing the contacts list.</p>
 		
 		<pre class='example'>
 @prefix : &lt;http://example.com/people/&gt;.
@@ -1441,7 +1445,7 @@
 	<section id="s9.2">
 	<h3>Alternative scenario: media-resource attachments</h3>
 	<p>
-		A resource may have multiple <i>renditions</i>. For example, you
+		A resource may have multiple <em>renditions</em>. For example, you
 		can have a PDF and a JPEG representing the same thing. A user is
 		trying to create a work order along with an attached image showing
 		a faulty machine part. To the user and to the work order system,