merge two redundant points in relation to OpenID: they were both about the benefits of building on Web Standards
--- a/index-respec.html Mon Jul 26 20:36:14 2010 -0400
+++ b/index-respec.html Mon Jul 26 21:04:51 2010 -0400
@@ -440,8 +440,11 @@
<p>WebID builds on a number of well established Internet and Web standards;
<a href="http://en.wikipedia.org/wiki/REST">REST</a>,
RDF [[RDF-PRIMER]], RDFa [[!RDFA-CORE]], RDF/XML [[!RDF-SYNTAX-GRAMMAR]],
-TLS [[!HTTP-TLS]], and X.509 [[!X509V3]]. By building on previous standards,
-it makes both explaining and implementing WebID easier on developers.</p>
+TLS [[!HTTP-TLS]], and X.509 [[!X509V3]]. By building on proven technologies
+which have been integrated into Web browsers for many years,
+it makes both explaining and implementing WebID easier on developers.
+As a matter of fact, there were already three interoperable implementations
+of WebID before this specification was written.</p>
<p>Since WebID is RESTful, you can perform basic HTTP operations to
<code>GET</code> your WebID, and if you needed update it, you can use
@@ -469,11 +472,6 @@
adding more HTML to the developer's page. OpenID does not provide any type of
distributed innovation akin to RDF.</p>
-<p>Implementing WebID is easier than OpenID because all of the basic
-technologies have been working and integrated into Web browsers for many years.
-There were already three interoperable implementations of WebID before this
-specification was written.</p>
-
<p>WebID is truly decentralized - with WebID you get a web of trust.
OpenID only supports the Web of Trust model if you indirectly trust the
OpenID provider. In other words - OpenID is not truly decentralized. In OpenID