--- a/spec/identity-respec.html Thu Apr 11 11:32:43 2013 +0200
+++ b/spec/identity-respec.html Tue Apr 23 11:38:19 2013 +0200
@@ -354,7 +354,7 @@
<p>
A WebID is an HTTP URI which refers to an Agent (Person, Organization, Group, Device, etc.). A description of the WebID can be found in the <tref>Profile Document</tref>, a type of web page that any Social Network user is familiar with.</p>
<p>
-A WebID <tref>Profile Document</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.
+A WebID <tref>Profile Document</tref> is a Web resource that MUST be available as text/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.
@@ -392,9 +392,7 @@
<dt><tdef>WebID Profile</tdef> or <tdef>Profile Document</tdef></dt>
<dd>
-A WebID Profile is an RDF document which MUST uniquely describe the Agent denoted by the WebID in relation to that WebID. This document MUST be available as Turtle [[!TURTLE-TR]]. This document MAY be available in other RDF serialization formats, such as RDFa [[!RDFA-CORE]], or [[!RDF-XML]] if so requested through content negotiation.
-
-Any other serializations MUST be transformable automatically and in a standard manner to an RDF Graph, using technologies such as GRDDL [[!GRDDL-PRIMER]].
+A WebID Profile is an RDF document which uniquely describes the Agent denoted by the WebID in relation to that WebID. The server MUST provide a text/turtle [[!TURTLE-TR]] representation of the requested profile. This document MAY be available in other RDF serialization formats, such as RDFa [[!RDFA-CORE]], or [[!RDF-XML]] if so requested through content negotiation.
</dd>
</dl>
@@ -451,7 +449,6 @@
<p>
WebID requires that servers MUST at least be able to provide Turtle representation of profile documents, but other serialization formats of the graph are allowed, provided that agents are able to parse that serialization and obtain the graph automatically.
-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>It is particularly useful to have one of the representations be in HTML