HTML Standard Tracker

Diff (omit for latest revision)
Filter

Short URL: http://html5.org/r/3907

File a bug

SVNBugCommentTime (UTC)
3907Clarify the registries for rel='', <meta name=''>, and http-equiv=''.2009-09-18 21:33
Index: source
===================================================================
--- source	(revision 3906)
+++ source	(revision 3907)
@@ -11436,11 +11436,12 @@
 
    <dt>Brief description</dt>
 
-   <dd><p>A short description of what the metadata name's meaning is,
-   including the format the value is required to be in.</p></dd>
+   <dd><p>A short non-normative description of what the metadata
+   name's meaning is, including the format the value is required to be
+   in.</p></dd>
 
 
-   <dt>Link to more details</dt>
+   <dt>Specification</dt>
 
    <dd>A link to a more detailed description of the metadata name's
    semantics and requirements. It could be another page on the Wiki,
@@ -11463,31 +11464,45 @@
 
     <dl>
 
-     <dt>Proposal</dt>
+     <dt>Proposed</dt>
 
      <dd>The name has not received wide peer review and
-     approval. Someone has proposed it and is using it.</dd>
+     approval. Someone has proposed it and is, or soon will be, using
+     it.</dd>
 
-     <dt>Accepted</dt>
+     <dt>Ratified</dt>
 
      <dd>The name has received wide peer review and approval. It has a
      specification that unambiguously defines how to handle pages that
      use the name, including when they use it in incorrect ways.</dd>
 
-     <dt>Unendorsed</dt>
+     <dt>Discontinued</dt>
 
      <dd>The metadata name has received wide peer review and it has
-     been found wanting. Existing pages are using this keyword, but
-     new pages should avoid it. The "brief description" and "link to
-     more details" entries will give details of what authors should
+     been found wanting. Existing pages are using this metadata name,
+     but new pages should avoid it. The "brief description" and
+     "specification" entries will give details of what authors should
      use instead, if anything.</dd>
 
     </dl>
 
-    <p>If a metadata name is added with the "proposal" status and
+    <p>If a metadata name is found to be redundant with existing
+    values, it should be removed and listed as a synonym for the
+    existing value.</p>
+
+    <p>If a metadata name is registered in the "proposed" state for a
+    period of a month or more without being used or specified, then it
+    may be removed from the registry.</p>
+
+    <p>If a metadata name is added with the "proposed" status and
     found to be redundant with existing values, it should be removed
-    and listed as a synonym for the existing value.</p>
+    and listed as a synonym for the existing value. If a metadata name
+    is added with the "proposed" status and found to be harmful, then
+    it should be changed to "discontinued" status.</p>
 
+    <p>Anyone can change the status at any time, but should only do so
+    in accordance with the definitions above.</p>
+
    </dd>
 
   </dl>
@@ -11495,22 +11510,21 @@
   <div class="impl">
 
   <p>Conformance checkers must use the information given on the WHATWG
-  Wiki MetaExtensions page to establish if a value not explicitly
-  defined in this specification is allowed or not. Conformance
-  checkers may cache this information (e.g. for performance reasons or
-  to avoid the use of unreliable network connectivity).</p>
+  Wiki MetaExtensions page to establish if a value is allowed or not:
+  values defined in this specification or marked as "proposed" or
+  "ratified" must be accepted, whereas values marked as "discontinued"
+  or not listed in either this specification or on the aforementioned
+  page must be rejected as invalid. Conformance checkers may cache
+  this information (e.g. for performance reasons or to avoid the use
+  of unreliable network connectivity).</p>
 
-  <p>When an author uses a new type not defined by either this
-  specification or the Wiki page, conformance checkers should offer to
-  add the value to the Wiki, with the details described above, with
-  the "proposal" status.</p>
+  <p>When an author uses a new metadata name not defined by either
+  this specification or the Wiki page, conformance checkers should
+  offer to add the value to the Wiki, with the details described
+  above, with the "proposed" status.</p>
 
   </div>
 
-  <p>This specification does not define how new values will get
-  approved. It is expected that the Wiki will have a community that
-  addresses this.</p>
-
   <p>Metadata names whose values are to be <span
   title="URL">URLs</span> must not be proposed or accepted. Links must
   be represented using the <code>link</code> element, not the
@@ -11518,7 +11532,6 @@
 
 
 
-
   <h5>Pragma directives</h5>
 
   <p>When the <dfn
@@ -11960,7 +11973,7 @@
   <p>Such extensions must use a name that is identical to a
   previously-registered HTTP header defined in an RFC, and must have
   behavior identical to that described for the HTTP header. Pragma
-  directions corresponding to headers describing metadata, or not
+  directives corresponding to headers describing metadata, or not
   requiring specific user agent processing, must not be registered;
   instead, use <span title="concept-meta-extensions">metadata
   names</span>. Pragma directions corresponding to headers that affect
@@ -11976,13 +11989,15 @@
 
    <dt>Keyword</dt>
 
-   <dd><p>The actual name being defined.</p></dd>
+   <dd><p>The actual name being defined. The name must match a
+   previously-registered HTTP name with the same
+   requirements.</p></dd>
 
 
    <dt>Brief description</dt>
 
-   <dd><p>A short description of the purpose of the pragma
-   directive.</p></dd>
+   <dd><p>A short non-normative description of the purpose of the
+   pragma directive.</p></dd>
 
 
    <dt>Specification</dt>
@@ -11994,14 +12009,19 @@
   <div class="impl">
 
   <p>Conformance checkers must use the information given on the WHATWG
-  Wiki PragmaExtensions page to establish if a value not explicitly
-  defined in this specification is allowed or not. Conformance
-  checkers may cache this information (e.g. for performance reasons or
-  to avoid the use of unreliable network connectivity).</p>
+  Wiki PragmaExtensions page to establish if a value is allowed or
+  not: values defined in this specification or listed on the
+  aforementioned page must be accepted, whereas values not listed in
+  either this specification or on the aforementioned page must be
+  rejected as invalid. Conformance checkers may cache this information
+  (e.g. for performance reasons or to avoid the use of unreliable
+  network connectivity).</p>
 
   </div>
 
 
+
+
   <h5 id="charset">Specifying the document's character encoding</h5>
 
   <!-- READ ME WHEN EDITING: if we ever move this to the "writing
@@ -65440,12 +65460,10 @@
 
   <h5>Other link types</h5>
 
-  <p>Other than the types defined above, only types defined as
-  extensions in the <a
+  <p><dfn title="concept-rel-extensions">Extensions to the predefined
+  set of link types</dfn> may be registered in the <a
   href="http://wiki.whatwg.org/wiki/RelExtensions">WHATWG Wiki
-  RelExtensions page</a> may be used with the <code
-  title="">rel</code> attribute on <code>link</code>, <code>a</code>,
-  and <code>area</code> elements. <a
+  RelExtensions page</a>. <a
   href="#refsWHATWGWIKI">[WHATWGWIKI]</a></p>
 
   <p>Anyone is free to edit the WHATWG Wiki RelExtensions page at any
@@ -65516,10 +65534,11 @@
 
    <dt>Brief description</dt>
 
-   <dd><p>A short description of what the keyword's meaning is.</p></dd>
+   <dd><p>A short non-normative description of what the keyword's
+   meaning is.</p></dd>
 
 
-   <dt>Link to more details</dt>
+   <dt>Specification</dt>
 
    <dd><p>A link to a more detailed description of the keyword's
    semantics and requirements. It could be another page on the Wiki,
@@ -65529,7 +65548,7 @@
    <dt>Synonyms</dt>
 
    <dd><p>A list of other keyword values that have exactly the same
-   processing requirements. Authors must not use the values defined to
+   processing requirements. Authors should not use the values defined to
    be synonyms, they are only intended to allow user agents to support
    legacy content.</p></dd>
 
@@ -65542,37 +65561,46 @@
 
     <dl>
 
-     <dt>Proposal</dt>
+     <dt>Proposed</dt>
 
      <dd>The keyword has not received wide peer review and
-     approval. It is included for completeness because pages use the
-     keyword. Pages should not use the keyword.</dd>
+     approval. Someone has proposed it and is, or soon will be, using
+     it.</dd>
 
-     <dt>Accepted</dt>
+     <dt>Ratified</dt>
 
      <dd>The keyword has received wide peer review and approval. It
      has a specification that unambiguously defines how to handle
-     pages that use the keyword, including when they use them in
-     incorrect ways. Pages may use the keyword.</dd>
+     pages that use the keyword, including when they use it in
+     incorrect ways.</dd>
 
-     <dt>Rejected</dt>
+     <dt>Discontinued</dt>
 
      <dd>The keyword has received wide peer review and it has been
-     found to have significant problems. Pages must not use the
-     keyword. When a keyword has this status, the "Effect
-     on... <code>link</code>" and "Effect on... <code>a</code> and
-     <code>area</code>" information should be set to "not
-     allowed".</dd>
+     found wanting. Existing pages are using this keyword, but new
+     pages should avoid it. The "brief description" and
+     "specification" entries will give details of what authors should
+     use instead, if anything.</dd>
 
     </dl>
 
-    <p>If a keyword is added with the "proposal" status and found to
+    <p>If a keyword is found to be redundant with existing values, it
+    should be removed and listed as a synonym for the existing
+    value.</p>
+
+    <p>If a keyword is registered in the "proposed" state for a
+    period of a month or more without being used or specified, then it
+    may be removed from the registry.</p>
+
+    <p>If a keyword is added with the "proposed" status and found to
     be redundant with existing values, it should be removed and listed
     as a synonym for the existing value. If a keyword is added with
-    the "proposal" status and found to be harmful, then it should be
-    changed to "rejected" status, and its "Effect on..." information
-    should be changed accordingly.</p>
+    the "proposed" status and found to be harmful, then it should be
+    changed to "discontinued" status.</p>
 
+    <p>Anyone can change the status at any time, but should only do so
+    in accordance with the definitions above.</p>
+
    </dd>
 
   </dl>
@@ -65580,21 +65608,30 @@
   <div class="impl">
 
   <p>Conformance checkers must use the information given on the WHATWG
-  Wiki RelExtensions page to establish if a value not explicitly
-  defined in this specification is allowed or not. Conformance
-  checkers may cache this information (e.g. for performance reasons or
-  to avoid the use of unreliable network connectivity).</p>
+  Wiki RelExtensions page to establish if a value is allowed or not:
+  values defined in this specification or marked as "proposed" or
+  "ratified" must be accepted when used on the elements for which they
+  apply as described in the "Effect on..." field, whereas values
+  marked as "discontinued" or not listed in either this specification
+  or on the aforementioned page must be rejected as invalid.
+  Conformance checkers may cache this information (e.g. for
+  performance reasons or to avoid the use of unreliable network
+  connectivity).</p>
 
   <p>When an author uses a new type not defined by either this
   specification or the Wiki page, conformance checkers should offer to
   add the value to the Wiki, with the details described above, with
-  the "proposal" status.</p>
+  the "proposed" status.</p>
 
   </div>
 
-  <p>This specification does not define how new values will get
-  approved. It is expected that the Wiki will have a community that
-  addresses this.</p>
+  <p>Types defined as extensions in the <a
+  href="http://wiki.whatwg.org/wiki/RelExtensions">WHATWG Wiki
+  RelExtensions page</a> with the status "proposed" or "ratified" may
+  be used with the <code title="">rel</code> attribute on
+  <code>link</code>, <code>a</code>, and <code>area</code> elements in
+  accordance to the "Effect on..." field. <a
+  href="#refsWHATWGWIKI">[WHATWGWIKI]</a></p>
 
 
 

|