the text was suggesting that all formats of the profile document had to be parseable using a GRDDL like mechanism. This would mean that one could NOT publish text documents which is too strong. (from a discussion about Mo McRoberts)
authorHenry Story <henry.story@bblfish.net>
Mon, 16 Jan 2012 17:26:17 +0100
changeset 282 f4c672b54ea0
parent 281 459085ee72a7
child 283 029f115c08a5
the text was suggesting that all formats of the profile document had to be parseable using a GRDDL like mechanism. This would mean that one could NOT publish text documents which is too strong. (from a discussion about Mo McRoberts)
spec/index-respec.html
--- a/spec/index-respec.html	Tue Jan 10 23:18:40 2012 +0100
+++ b/spec/index-respec.html	Mon Jan 16 17:26:17 2012 +0100
@@ -469,7 +469,7 @@
 Dereferencing the <tref>WebID</tref> should return the Profile Page in one of a number of formats. 
 The Server MUST publish the document in at least the XHTML+RDFa [[!XHTML-RDFA]] serialization format or in Turtle [[!TURTLE-TR]].
 The document may be published in a number of other RDF serialization formats, such as RDF-XML [[!RDF-PRIMER]], or N3 [[!N3]].
-Any other serialisation MUST be transformable automatically and in a standard manner to an RDF Graph, using technologies such as GRDDL [[!GRDDL-PRIMER]].
+Any other serialisation that intend to be used by the WebID Protocol MUST be transformable automatically and in a standard manner to an RDF Graph, using technologies such as GRDDL [[!GRDDL-PRIMER]].
 <p class="issue">Most profiles are currently written out in either of those formats. Whether or not XHTML+RDFa 1.1, both either serialization of RDF should be required serialization formats in the specification is currently under heavy debate and is open to change. </p>
 </dd>