--- a/spec/identity-respec.html	Thu Nov 22 14:08:25 2012 -0500
+++ b/spec/identity-respec.html	Thu Nov 22 14:12:26 2012 -0500
@@ -349,9 +349,9 @@
 <h1>Introduction</h1>
 
 <p>
-A WebID is an HTTP URI containing a URI fragment identifier (i.e. a # symbol) and which uniquely denotes an Agent (Person, Organization, Group, Device, etc.). The URI without the fragment identifier denotes the WebID <tref>Profile Page</tref> document.</p>
+A WebID is an HTTP URI which uniquely denotes an Agent (Person, Organization, Group, Device, etc.). A description of the WebID can be found by dereferencing the WebID in the associated <tref>Profile Page</tref>, a type of web page that any Social Network user is familiar with.</p>
 <p>
-A WebID Profile is a Web resource that MUST be available as Turtle [[!TURTLE-TR]], but MAY be available in other RDF serialization formats (e.g. [[!RDFA-CORE]]) if requested through content negotiation. 
+A WebID <tref>Profile Page</tref> is a Web resource that MUST be available as Turtle [[!TURTLE-TR]], but MAY be available in other RDF serialization formats (e.g. [[!RDFA-CORE]]) if requested through content negotiation.
 </p>
 <p>
 WebIDs can be used to build a Web of trust using vocabularies such as FOAF [[!FOAF]] by allowing people to link together their profiles in a public or protected manner. 
@@ -383,12 +383,12 @@
 <dd>A Service is a an agent listening for requests at a given IP address on a given Server.</dd>  
 
 <dt><tdef>WebID</tdef></dt>
-<dd>A WebID is a URI with an HTTP or HTTPS scheme, containing a URI fragment identifier (i.e. a # symbol) and which uniquely denotes an Agent (Person, Organization, Group, Device, etc.). The URI without the fragment identifier denotes the WebID <tref>Profile page</tref>.
+<dd>A WebID is a URI with an HTTP or HTTPS scheme which uniquely denotes an Agent (Person, Organization, Group, Device, etc.).
 </dd>
 
 <dt><tdef>WebID Profile</tdef> or <tdef>Profile Page</tdef></dt>
 <dd>
-A WebID Profile is an RDF document that MUST be available as Turtle [[!TURTLE-TR]]. The document MAY be available in other RDF serialization formats, such as RDFa [[!RDFA-CORE]], RDF/XML [[!RDF-PRIMER]], or N3 [[!N3]] if so requested through content negotiation.
+A WebID Profile is an RDF document that is found by dereferencing the WebID HTTP URI. This document MUST be available as Turtle [[!TURTLE-TR]]. This document MAY be available in other RDF serialization formats, such as RDFa [[!RDFA-CORE]], RDF/XML [[!RDF-PRIMER]], or N3 [[!N3]] if so requested through content negotiation.
 
 Any other serializations that intend to be used by WebID MUST be transformable automatically and in a standard manner to an RDF Graph, using technologies such as GRDDL [[!GRDDL-PRIMER]].
 </dd>
@@ -416,13 +416,13 @@
 </section>
 
 <section class='normative'>
-<h1>The HTTP URI</h1>
+<h1>The WebID HTTP URI</h1>
 
-<p>This URI must be one that dereferences to a document the user controls.</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="issue">Due to legacy support for URIs which do not contain URI fragment identifiers, verifiers MUST NOT fail when dereferencing hashless URIs, though they MAY flag them as potentially impacting on performance. Implementors need to take into account that the use of hashless URIs is deprecated and they must be avoided when creating new WebIDs.</p>
+<p class="note">Implementers are highly encouraged to use hash URIs for the WebID HTTP URI. Even though 303 redirects have been used in the past, experience has shown that they can be difficult to deploy and can have an impact on performance. However WebID Verifiers MUST NOT fail when dereferencing hashless URIs, though they MAY flag them as potentially impacting on performance.</p>
 
 </section>
 
@@ -450,8 +450,6 @@
 Technologies such as GRDDL [[!GRDDL-PRIMER]] for example permit any XML format to be transformed automatically to a graph of relations.
 HTTP Content Negotiation can be employed to aid in publication and discovery of multiple distinct serializations of the same graph at the same URL, as explained by the working group note <a href="http://www.w3.org/TR/2008/NOTE-swbp-vocab-pub-20080828/">Best Practice Recipes for Publishing RDF Vocabularies</a> [[!SWBP-VOCAB-PUB]]</p>
 
-<p class="issue">HTTP 303 redirects should be avoided (needs further discussion). Since WebIDs contain a URI fragment identifier, it is not nessary to use HTTP 303 redirects in order to make the difference between the identifier and the document it points to; the relationship becomes obvious.</p>
-
 <p>It is particularly useful to have one of the representations be in HTML
 even if it is not marked up in RDFa as this allows people using a
 web browser to understand what the information at that URI represents.</p>