Added best practice covering ISSUE-77
authorcburleso
Sat, 06 Jul 2013 16:37:19 -0500
changeset 141 1fa8ececcf03
parent 140 7b8b634fbce8
child 142 3ac7871e4714
Added best practice covering ISSUE-77
ldp-bp/include-rdf-type.ttl
ldp-bp/ldp-bp.html
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/ldp-bp/include-rdf-type.ttl	Sat Jul 06 16:37:19 2013 -0500
@@ -0,0 +1,8 @@
[email protected] rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
[email protected] contact: <http://www.w3.org/2000/10/swap/pim/contact#>.
+
+<http://www.w3.org/People/EM/contact#me> 
+  rdf:type contact:Person;
+  contact:fullName "Eric Miller";
+  contact:mailbox <mailto:[email protected]>;
+  contact:personalTitle "Dr.".
\ No newline at end of file
--- a/ldp-bp/ldp-bp.html	Sat Jul 06 14:11:16 2013 -0500
+++ b/ldp-bp/ldp-bp.html	Sat Jul 06 16:37:19 2013 -0500
@@ -86,6 +86,20 @@
 		// Team Contact.
 		wgPatentURI : "http://www.w3.org/2004/01/pp-impl/55082/status",
 	};
+	
+	// Replaces HTML characters (brackets and quotes) with legal HTML representations
+	// The following example would include a code example from another file and then 
+	// call this function to make the included code renderable in a browser.
+	//
+	// <pre class='example' data-include='include-rdf-type.ttl' data-oninclude='fixCode'></pre>
+	
+	function fixCode(r, content) {
+        var result = content;
+        result = result.replace(/</g,"&lt;").replace(/>/g,"&gt;");
+        result = result.replace(/'/g, "&apos;").replace(/"/g, "&quot;");
+        return result;
+    }
+
 </script>
 </head>
 <body>
@@ -155,7 +169,21 @@
 			(&quot;dereferenced&quot;). It is therefor ideal that predicate URIs identify LDPRs with representations that are retrievable. LDP servers should at least provide [[RDF-SCHEMA]] representations of these predicates where possible.</p>
 
 			<p>Of course, it is also a common practice to reuse properties from vocabularies that you don't own. In this case, you typically have no control over the result when attempting to dereference the URI. For this reason, publishers who wish to make their vocabularies useful for linking data should strive to provide a retrievable representation of the properties their vocabularies define. Consequently, implementers are also expected to use this standard as a benchmark for which to judge the efficacy of a vocabulary's use for linking data.</p>
-			
+
+		</section>
+
+		<section>
+
+			<h3>Use and include the predicate rdf:type to represent the concept of type in LDPRs</h3>
+
+			<p>It is often very useful to know the type (class) of an LDPR, though it is not essential to work with the interaction capabilities that LDP offers. Still, to make your data more useful in the broadest context, you should explicitly 
+				define the type when possible and appropriate and you should use the <code>rdf:type</code> predicate defined by [[RDF-SCHEMA]] when doing so.</p>
+
+			<p>This provides a way for clients to easily determine the type of a resource without having to perform additional 
+				processing or make additional HTTP requests. For example, clients that cannot infer the type because they do not support inferencing can benefit from this explicit declaration.</p>
+
+			<pre title="Turtle With Explicit Declaration of rdf:type" class='example' data-include='include-rdf-type.ttl' data-oninclude='fixCode'></pre>
+		
 		</section>
 
 		<section>