ldp.html
changeset 20 ff2208593c27
parent 19 52d63fdf6ae8
child 21 0a04ba606cb6
--- a/ldp.html	Sat Nov 03 05:31:12 2012 -0400
+++ b/ldp.html	Sat Nov 03 05:37:02 2012 -0400
@@ -273,53 +273,22 @@
 	</div>
 	</div>
 
-	
-	<div id="ldpr-4_1_9" class="rule">4.1.9 LDPR representations MUST use only the following standard datatypes.
-		RDF does not by itself define datatypes to be used for literal
-		property values, therefore a set of standard datatypes based on [[!XMLSCHEMA11-2]] and [[!RDF-PRIMER]] are to be used: </div>
-		<table border="1" cellspacing="5" summary="Datatype to use with RDF literals">
-		<thead>
-		<tr><th>URI</th><th>Description</th></tr>
-		</thead>
-		<tbody>
-		<tr><td><code>http://www.w3.org/2001/XMLSchema#boolean</code></td><td>Boolean type as specified by XSD Boolean</td></tr>
-		<tr><td><code>http://www.w3.org/2001/XMLSchema#date</code></td><td>Date type as specified by XSD date</td></tr>
-		<tr><td><code>http://www.w3.org/2001/XMLSchema#dateTime</code></td><td>Date and Time type as specified
-			by XSD dateTime</td></tr>
-		<tr><td><code>http://www.w3.org/2001/XMLSchema#decimal</code></td><td>Decimal number type as specified
-			by XSD Decimal</td></tr>
-		<tr><td><code>http://www.w3.org/2001/XMLSchema#double</code></td><td>Double floating-point number type as
-		specified by XSD Double</td></tr>
-		<tr><td><code>http://www.w3.org/2001/XMLSchema#float</code></td><td>Floating-point number type as
-		specified by XSD Float</td></tr>
-		<tr><td><code>http://www.w3.org/2001/XMLSchema#integer</code></td><td>Integer number type as specified by
-		XSD Integer</td></tr>
-		<tr><td><code>http://www.w3.org/2001/XMLSchema#string</code></td><td>String type as specified by XSD String</td></tr>
-		<tr><td><code>http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral</code></td><td>Literal XML value as specified by RDF</td></tr>							
-	   </tbody>
-	  </table>
-	  
-	<div class="ldp-issue">
-	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/6">ISSUE-6</a></div>
-	Should LDBP say that any kind of user-defined simple data type is disallowed?
-	</div>
-
-	<div id="ldpr-4_1_10" class="rule">4.1.10 LDPRs MUST use at least one RDF triple to represent a link
+	<div id="ldpr-4_1_9" class="rule">4.1.9 LDPRs MUST use at least one RDF triple to represent a link
 		(relationship) to another resource. In other words, having the source
 		resource’s URI as the subject and the target resource’s URI as the
 		object of the triple represent the link (relationship) is enough and
 		does not require the creation of an intermediate link resource to
 		describe the relationship.
 	</div>
-	<div id="ldpr-4_1_11" class="rule">4.1.11 LDPR servers MAY support additional standard representations. These
+	<div id="ldpr-4_1_10" class="rule">4.1.10 LDPR servers MAY support additional standard representations. These
 		could be other RDF formats, like N3 or NTriples, but non-RDF formats
 		like HTML [[!HTML401]] and JSON [[!RFC4627]] would be likely be common.
 		
-	<div id="ldpr-4_1_12" class="rule">4.1.12 LDPRs MAY be created, updated and deleted using methods not defined in
+	<div id="ldpr-4_1_11" class="rule">4.1.11 LDPRs MAY be created, updated and deleted using methods not defined in
 		this document, for example through application-specific means, SPARQL
 		UPDATE, etc. [[!SPARQL-UPDATE]]
 	</div>
-	<div id="ldpr-4_1_13" class="rule">4.1.13 LDPR server responses MUST contain accurate response <code>ETag</code>
+	<div id="ldpr-4_1_12" class="rule">4.1.12 LDPR server responses MUST contain accurate response <code>ETag</code>
 		header values.
 		
 	<div class="ldp-issue">
@@ -1266,6 +1235,7 @@
 	<li>2012-11-03 - ISSUE-22, ISSUE-23: changed sections 4.2.3 and 5.4.7. Removed closed issues. (SS)</li>
 	<li>2012-11-03 - ISSUE-24 Delete the phrase in 4.5.1 that nays "until ...Request URI" 
 	and adding a sentence, "Clients should note that severs may reuse a Request-URI under some circumstances."</li>
+	<li>2012-11-03 - aISSUE-6 Removed section 4.1.9.  Shifted up sections .10 through .13.</li>
 </ul></section>
 
 <section class='appendix informative' id="todos">