--- a/spec/identity-respec.html	Mon Jul 01 15:29:51 2013 +0200
+++ b/spec/identity-respec.html	Wed Jul 17 13:51:13 2013 +0200
@@ -414,12 +414,12 @@
 
 <section class='normative'>
 <h1>The WebID HTTP URI</h1>
-
+<p>When using URIs, it is possible to identify both a thing (which may exist outside of the Web) and a Web document describing the thing. For example the person Bob is described on his homepage. Alice may not like the look of the homepage, but may want to link to the person Bob. Therefore, two URIs are needed, one for Alice and one for the homepage or a RDF document describing Alice.</p>
 <p>The WebID HTTP URI must be one that dereferences to a document the user controls.</p>
 <p>For example, if a user Bob controls <code>https://bob.example/profile</code>,
 then his WebID can be <code>https://bob.example/profile#me</code>.</p>
 
-<p class="note">Hash URIs are encouraged when choosing a WebID since 303 redirects require an extra HTTP request for an Agent to get from the <tref>WebID</tref> to the <tref>WebID Profile</tref>. All examples in the spec will use such hash URIs.</p>
+<p class="note">There are two solutions that meet our requirements for identifying real-world objects: 303 redirects and hash URIs. Which one to use depends on the situation, both have advantages and disadvantages, as presented in [[!COOLURIS]]. All examples in this spec will use such hash URIs.</p>
 
 </section>