add describedby registration, per wg resolution
authorJohn Arwe
Tue, 15 Apr 2014 15:11:02 -0400
changeset 551 962b81033167
parent 550 58d6a84e5f10
child 552 4d99968383f2
add describedby registration, per wg resolution
ldp.html
--- a/ldp.html	Tue Apr 15 14:46:50 2014 -0400
+++ b/ldp.html	Tue Apr 15 15:11:02 2014 -0400
@@ -2177,28 +2177,29 @@
 <section id='link-relation-describedby'>
 <h2>describedby</h2>
 <p>
-	The contents of this section were originally taken from [[POWDER]] appendix D.
+	The contents of this section were originally taken from [[POWDER]] appendix D, and then modified to comply with the current registration template.
+	The pre-LDP IANA link relation registry entry for 
+	<code>describedby</code> refers to a different section of [[POWDER]] that was substantively updated in 
+	<a href="http://www.w3.org/2007/powder/powder-errata#describedby">an erratum</a>, and that section was not
+	actually the normative definition of the link relation.  Since we expect no update to [[POWDER]] that incorporates the erratum 
+	or fixes the registry link, this superseding registration approach is being taken.
 </p>
 <p>The following Link Relationship will be submitted to IANA for review, approval, and inclusion in the IANA Link Relations registry.</p>
 <dl>
-<dt>Attribute Value:</dt>
-<dd>describedby</dd>
+<dt>Relation Name:</dt>
+<dd><code>describedby</code></dd>
 <dt>Description:</dt>
 <dd>
 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. 
 </dd>
-<dt>Expected display characteristics:</dt>
+<dt>Reference:</dt>
 <dd>
-None
+	The W3C <a href="http://www.w3.org/TR/ldp/">Linked Data Platform specification</a>.
 </dd>
-<dt>Security considerations:</dt>
+<dt>Notes:</dt>
 <dd>
     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.
 </dd>
-<dt>Documentation:</dt>
-<dd>
-	This specification.
-</dd>
 </dl>
 </section>
 </section>
@@ -2245,7 +2246,7 @@
 <h2>Detailed history</h2>
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130930/">Candidate Recommendation Draft</a></em></blockquote> -->
 <ul>
-	<li>2014-04-15 - Add describedby (JA) </li>
+	<li>2014-04-15 - Add describedby chapter (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>