Resolve Issue-42 by removing 4.8 (moved to deployment guide on wiki)
authorjMithrandir@ADMINIB-6VK90F5.pok.ibm.com
Wed, 13 Feb 2013 13:43:07 -0500
changeset 64 555e00343af1
parent 63 ab17a2fc579a
child 65 b0b7c7b7c034
Resolve Issue-42 by removing 4.8 (moved to deployment guide on wiki)
ldp.html
--- a/ldp.html	Wed Feb 13 11:12:03 2013 -0500
+++ b/ldp.html	Wed Feb 13 13:43:07 2013 -0500
@@ -297,7 +297,7 @@
 	<div id="ldpr-4_1_6" class="rule">4.1.6 LDPRs MUST use the predicate <code>rdf:type</code> to
 		represent the concept of type. The use of non-standard type
 		predicates, as well as <code>dcterms:type</code>, is
-		discouraged (see <a href="#ldpr-prop">4.8 Common Properties</a>), as it is not recommended
+		discouraged, as it is not recommended
 		by the Dublin Core Metadata Initiative for use with RDF resources [[!DC-RDF]]. 
 	</div>
 	<div id="ldpr-4_1_7" class="rule">4.1.7 LDPR representations SHOULD have at least one <code>rdf:type</code>
@@ -510,137 +510,6 @@
 	</div>
 </section>
 
-<section>
-<h2 id="ldpr-prop">Common Properties</h2>
-	<p>
-		This section summarizes some well-known RDF vocabularies that MUST be
-		used in Linked Data Platform Resources wherever a resource needs to use a
-		predicate whose meaning matches one of these. For example, if an LDPR
-		 has a <em>description</em>, and the application semantic of that
-		<em>description</em> is compatible with <code>dcterms:description</code>,
-		then <code>dcterms:description</code> MUST be used. If
-		needed, additional application-specific predicates MAY be used. A
-		specification based on <abbr title="Linked Data Platform">LDP</abbr> may require one or
-		more of these properties for a particular resource type. The Range
-		column in the tables below identifies the RECOMMENDED <code>rdfs:range</code>
-		for the properties.
-	</p>
-	<div id="ldpr-4_8_1" class="rule">4.8.1 From Dublin Core</div>
-	<p>
-		URI: <code>http://purl.org/dc/terms/</code>
-	</p>
-	<table border="1" cellspacing="5" summary="Dublin Core properties recommended">
-		<tr>
-			<td>Property</td>
-			<td>Range/DataType</td>
-			<td>Comment</td>
-		</tr>
-		<tr>
-			<td><code>dcterms:contributor</code></td>
-			<td><code>dcterms:Agent</code></td>
-			<td></td>
-		</tr>
-		<tr>
-			<td><code>dcterms:creator</code></td>
-			<td><code>dcterms:Agent</code></td>
-			<td></td>
-		</tr>
-		<tr>
-			<td><code>dcterms:created</code></td>
-			<td><code>xsd:dateTime</code></td>
-			<td></td>
-		</tr>
-		<tr>
-			<td><code>dcterms:description</code></td>
-			<td><code>rdf:XMLLiteral</code></td>
-			<td>
-					Descriptive text about the resource represented as rich text in
-					XHTML format. SHOULD include only content that is valid and suitable inside an XHTML
-					<code>&lt;div&gt;</code> element.
-			</td>
-		</tr>
-		<tr>
-			<td><code>dcterms:identifier</code></td>
-			<td><code>rdfs:Literal</code></td>
-			<td></td>
-		</tr>
-		<tr>
-			<td><code>dcterms:modified</code></td>
-			<td><code>xsd:dateTime</code></td>
-			<td></td>
-		</tr>
-		<tr>
-			<td><code>dcterms:relation</code></td>
-			<td><code>rdfs:Resource</code></td>
-			<td>The HTTP URI of a related resource. This is the
-					predicate to use when you don't know what else to use. If you know
-					more specifically what sort of relationship it is, use a more
-					specific predicate.</td>
-		</tr>
-		<tr>
-			<td><code>dcterms:subject</code></td>
-			<td><code>rdfs:Resource</code></td>
-			<td></td>
-		</tr>
-		<tr>
-			<td><code>dcterms:title</code></td>
-			<td><code>rdf:XMLLiteral</code></td>
-			<td>A name given to the resource. Represented as rich text in XHTML
-					format. SHOULD include only content that is valid inside an XHTML <code>&lt;span&gt;</code>
-					element.</td>
-		</tr>
-	</table>
-
-	<div id="ldpr-4_8_1_1" class="rule">4.8.1.1 From Dublin Core
-	<p>
-		The predicate <code>dcterms:type</code> SHOULD NOT be
-		used in LDPRs, instead use <code>rdf:type</code> [[!DC-RDF]].
-		See also <a href="#ldpr-4_1_6">4.1.6 LDPRs MUST use <code>rdf:type</code></a>.
-	</p>
-	</div>
-	
-	<div id="ldpr-4_8_2" class="rule">4.8.2 From RDF</div>
-	<p>
-		URI: <code>http://www.w3.org/1999/02/22-rdf-syntax-ns#</code>
-	</p>
-	<table border="1" cellspacing="5" summary="RDF properties recommended">
-		<tr>
-			<td>Property</td>
-			<td>Range</td>
-			<td>Comment</td>
-		</tr>
-		<tr>
-			<td><code>rdf:type</code></td>
-			<td><code>rdfs:Class</code></td>
-			<td>The type or types of the resource</td>
-		</tr>
-	</table>
-	
-	<div id="ldpr-4_8_3" class="rule">4.8.3 From RDF Schema</div>
-	<p>
-		URI: <code>http://www.w3.org/2000/01/rdf-schema#</code>
-	</p>
-	
-	
-	<table border="1" cellspacing="5" summary="RDF Schema properties recommended">
-		<tr>
-			<td>Property</td>
-			<td>Range</td>
-			<td>Comment</td>
-		</tr>
-		<tr>
-			<td><code>rdfs:member</code></td>
-			<td><code>rdfs:Resource</code></td>
-			<td></td>
-		</tr>
-		<tr>
-			<td><code>rdfs:label</code></td>
-			<td><code>rdfs:Literal</code></td>
-			<td>Only use this in vocabulary documents, to define
-					the name of the vocabulary term.</td>
-		</tr>
-	</table>		
-</section>
 </section>
 
 <section>
@@ -1361,6 +1230,9 @@
 	<li>2013-02-12 - Fixed up previous publication links (SS) </li>
 	<li>2013-02-12 - ISSUE-10 - 4.1.12 to be MUST use entity tags (either weak or strong ones) (SS) </li>
 	<li>2013-02-12 - ISSUE-11 - 4.4.1 Relaxed the MUST ignore dc:modified/creator to MAY (SS) </li>
+	<li>2013-02-13 - ISSUE-42 - 4.8 Common Properties moved to 
+			<a href="http://www.w3.org/2012/ldp/wiki/Deployment_Guide#Re-use_established_linked_data_vocabularies_instead_of_.28re-.29inventing_duplicates">Deploment Guide</a> 
+			(JA) </li>
 </ul></section>
 
 <section class='appendix informative' id="todos">
@@ -1388,7 +1260,8 @@
 	</li>
 	<li>4.4.4/4.4.5 could be read to overlap/dup one another
 	</li>
-	<li>4.8 talks about rdfs:Range which implies inferencing.  4.1.7 spec says want to avoid putting that reqt on clients.
+	<li>Deployment guide (was: 4.8 Common Properties) talks about rdfs:Range which implies inferencing.  
+	4.1.7 spec says want to avoid putting that reqt on clients.
 	</li>
 	<li>5.2.1: 4.1.6.1 issue linked to this text
 	</li>