Minor changes to the notice about fragment URIs and 303s.
--- a/spec/identity-respec.html Wed Feb 06 14:58:53 2013 +0100
+++ b/spec/identity-respec.html Wed Feb 06 16:18:56 2013 +0100
@@ -425,7 +425,7 @@
<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">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>
+<p class="note">Implementers are 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 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>