add in powder's describedby content
authorJohn Arwe
Tue, 15 Apr 2014 14:46:50 -0400
changeset 550 58d6a84e5f10
parent 549 084cb71ce842
child 551 962b81033167
add in powder's describedby content
--- a/ldp.html	Tue Apr 15 14:08:54 2014 -0400
+++ b/ldp.html	Tue Apr 15 14:46:50 2014 -0400
@@ -128,6 +128,15 @@
 				,   status:   "Editor's Working Draft"
 				,   publisher:  "W3C"
+				"POWDER": {
+					title:    "Protocol for Web Description Resources (POWDER): Description Resources"
+				,   href:     ""
+				,   authors:  [
+						"Phil Archer", "Kevin Smith", "Andrea Perego"
+					]
+				,   status:   "W3C Recommendation"
+				,   publisher:  "W3C"
+				},
 				"Prefer": {
 					title:    "Prefer"
 				,   href:     ""
@@ -2160,6 +2169,40 @@
 </section> <!-- status code defns -->
+<section id='link-relations'>
+<h1>Link Relations</h1>
+	The intent is that these link relations will be registered with IANA per [[RFC5988]] section 6.2.1.
+<section id='link-relation-describedby'>
+	The contents of this section were originally taken from [[POWDER]] appendix D.
+<p>The following Link Relationship will be submitted to IANA for review, approval, and inclusion in the IANA Link Relations registry.</p>
+<dt>Attribute Value:</dt>
+The relationship <code>A describedby B</code> asserts that resource B provides a description of resource A. There are no constraints on the format or representation of either A or B, neither are there any further constraints on either resource. 
+<dt>Expected display characteristics:</dt>
+<dt>Security considerations:</dt>
+    Descriptions of resources may be socially sensitive, may require processing to be understood and may or may not not be accurate. Consumers of descriptive resources should be aware of the source and chain of custody of the data. Security considerations for URIs (Section 7 of RFC 3986) and IRIs (Section 8 of RFC 3987) apply to the extent that describing resources may affect consumers' decisions about how or whether to retrieve those resources.
+	This specification.
 <section class='informative' id='security'>
 <h1>Security Considerations</h1>
 <p>As with any protocol that is implemented leveraging HTTP, implementations should take advantage of the many 
@@ -2196,11 +2239,15 @@
 	<li>Resolved Last Call 2 comments</li>
 	<li>Removed references to RDF named graphs</li>
+	<li>Duplication (with intent to supersede) of the <code>describedby</code> relation type, incorporating POWDER's relevant errata</li>
 <h2>Detailed history</h2>
 <!-- <blockquote><em><a href="">Candidate Recommendation Draft</a></em></blockquote> -->
+	<li>2014-04-15 - Add describedby (JA) </li>
+	<li>2014-04-15 - Removal of named graph references (JA) </li>
+	<li>2014-04-15 - Fixed typos (JA) </li>
 	<li>2014-04-15 - Fixed LC-2840 clarity on "burden of constraint" (SS) </li>
 	<li>2014-03-30 - Updated references to RFC5988 to first time Link header is used (SS) </li>
 	<li>2014-03-29 - Fixed error in Example 8 (SS) </li>