[html5] r4861 - [act] (0) Fix the text added for ISSUE-79 to use appropriate terminology and to [...]

whatwg at whatwg.org whatwg at whatwg.org
Tue Mar 23 01:45:52 PDT 2010


Author: ianh
Date: 2010-03-23 01:45:50 -0700 (Tue, 23 Mar 2010)
New Revision: 4861

Modified:
   complete.html
   index
   source
Log:
[act] (0) Fix the text added for ISSUE-79 to use appropriate terminology and to fit the style of the specification.
Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=7525

Modified: complete.html
===================================================================
--- complete.html	2010-03-23 07:12:02 UTC (rev 4860)
+++ complete.html	2010-03-23 08:45:50 UTC (rev 4861)
@@ -11531,21 +11531,74 @@
 
    <dd>
 
-    <p>Contains a comma-separated list of keywords relevant to the page.</p>
+    <p>The value must be a <a href=#set-of-comma-separated-tokens>set of comma-separated tokens</a>,
+    each of which is a keyword relevant to the page.</p>
 
-    <p>Note that many search engines have stopped to consider keyword
-    information as relevant because it has been used unreliably or even
-    misleading. Recipients are recommended to use this information only
-    when there's sufficient confidence in the reliability of this
-    information, for instance in controlled environments such as sites
-    generated from a content management system.</p>
+    <div class=example>
 
-    <p class=XXX>The text above is not in the right form for the
-    spec (no conformance criteria, the note uses the wrong writing
-    style, no examples, uses the wrong terminology for consistency
-    with this spec, etc), but is what the working group agreed. It
-    will be fixed momentarily.</p>
+     <p>This page about typefaces on British motorways uses a
+     <code><a href=#meta>meta</a></code> element to specify some keywords that users
+     might use to look for the page:</p>
 
+     <pre><!DOCTYPE HTML>
+<html>
+ <head>
+  <title>Typefaces on UK motorways</title>
+  <meta name="keywords" content="british,type face,font,fonts,highway,highways">
+ </head>
+ <body>
+  ...</pre>
+
+    </div>
+
+    <p class=note>Many search engines do not consider such keywords,
+    because this feature has historically been used unreliably and
+    even misleadingly as a way to spam search engine results in a way
+    that is not helpful for users.</p>
+
+    <div class=impl>
+
+    <p>To obtain the list of keywords that the author has specified as
+    applicable to the page, the user agent must run the following
+    steps:</p>
+
+    <ol><li><p>Let <var title="">keywords</var> be an empty
+     list.</li>
+
+     <li>
+
+      <p>For each <code><a href=#meta>meta</a></code> element with a <code title=attr-meta-name><a href=#attr-meta-name>name</a></code> attribute and a <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> attribute and whose
+      <code title=attr-meta-name><a href=#attr-meta-name>name</a></code> attribute's value is
+      <code title=meta-keywords><a href=#meta-keywords>keywords</a></code>, run the following
+      substeps:</p>
+
+      <ol><li><p><a href=#split-a-string-on-commas title="split a string on commas">Split the value
+       of the element's <code title=attr-meta-content>content</code>
+       attribute on commas</a>.</li>
+
+       <li><p>Add the resulting tokens, if any, to <var title="">keywords</var>.</li>
+
+      </ol></li>
+
+     <li><p>Remove any duplicates from <var title="">keywords</var>.</li>
+
+     <li><p>Return <var title="">keywords</var>. This is the list of
+     keywords that the author has specified as applicable to the
+     page.</li>
+
+    </ol><p>User agents should not use this information when there is
+    insufficient confidence in the reliability of the value.</p>
+
+    <p class=example>For instance, it would be reasonable for a
+    content management system to use the keyword information of pages
+    within the system to populate the index of a site-specific search
+    engine, but a large-scale content aggregator that used this
+    information would likely find that certain users would try to game
+    its ranking mechanism through the use of inappropriate
+    keywords.</p>
+
+    </div>
+
    </dd>
 
   </dl><h5 id=other-metadata-names><span class=secno>4.2.5.2 </span>Other metadata names</h5>

Modified: index
===================================================================
--- index	2010-03-23 07:12:02 UTC (rev 4860)
+++ index	2010-03-23 08:45:50 UTC (rev 4861)
@@ -11430,21 +11430,74 @@
 
    <dd>
 
-    <p>Contains a comma-separated list of keywords relevant to the page.</p>
+    <p>The value must be a <a href=#set-of-comma-separated-tokens>set of comma-separated tokens</a>,
+    each of which is a keyword relevant to the page.</p>
 
-    <p>Note that many search engines have stopped to consider keyword
-    information as relevant because it has been used unreliably or even
-    misleading. Recipients are recommended to use this information only
-    when there's sufficient confidence in the reliability of this
-    information, for instance in controlled environments such as sites
-    generated from a content management system.</p>
+    <div class=example>
 
-    <p class=XXX>The text above is not in the right form for the
-    spec (no conformance criteria, the note uses the wrong writing
-    style, no examples, uses the wrong terminology for consistency
-    with this spec, etc), but is what the working group agreed. It
-    will be fixed momentarily.</p>
+     <p>This page about typefaces on British motorways uses a
+     <code><a href=#meta>meta</a></code> element to specify some keywords that users
+     might use to look for the page:</p>
 
+     <pre><!DOCTYPE HTML>
+<html>
+ <head>
+  <title>Typefaces on UK motorways</title>
+  <meta name="keywords" content="british,type face,font,fonts,highway,highways">
+ </head>
+ <body>
+  ...</pre>
+
+    </div>
+
+    <p class=note>Many search engines do not consider such keywords,
+    because this feature has historically been used unreliably and
+    even misleadingly as a way to spam search engine results in a way
+    that is not helpful for users.</p>
+
+    <div class=impl>
+
+    <p>To obtain the list of keywords that the author has specified as
+    applicable to the page, the user agent must run the following
+    steps:</p>
+
+    <ol><li><p>Let <var title="">keywords</var> be an empty
+     list.</li>
+
+     <li>
+
+      <p>For each <code><a href=#meta>meta</a></code> element with a <code title=attr-meta-name><a href=#attr-meta-name>name</a></code> attribute and a <code title=attr-meta-content><a href=#attr-meta-content>content</a></code> attribute and whose
+      <code title=attr-meta-name><a href=#attr-meta-name>name</a></code> attribute's value is
+      <code title=meta-keywords><a href=#meta-keywords>keywords</a></code>, run the following
+      substeps:</p>
+
+      <ol><li><p><a href=#split-a-string-on-commas title="split a string on commas">Split the value
+       of the element's <code title=attr-meta-content>content</code>
+       attribute on commas</a>.</li>
+
+       <li><p>Add the resulting tokens, if any, to <var title="">keywords</var>.</li>
+
+      </ol></li>
+
+     <li><p>Remove any duplicates from <var title="">keywords</var>.</li>
+
+     <li><p>Return <var title="">keywords</var>. This is the list of
+     keywords that the author has specified as applicable to the
+     page.</li>
+
+    </ol><p>User agents should not use this information when there is
+    insufficient confidence in the reliability of the value.</p>
+
+    <p class=example>For instance, it would be reasonable for a
+    content management system to use the keyword information of pages
+    within the system to populate the index of a site-specific search
+    engine, but a large-scale content aggregator that used this
+    information would likely find that certain users would try to game
+    its ranking mechanism through the use of inappropriate
+    keywords.</p>
+
+    </div>
+
    </dd>
 
   </dl><h5 id=other-metadata-names><span class=secno>4.2.5.2 </span>Other metadata names</h5>

Modified: source
===================================================================
--- source	2010-03-23 07:12:02 UTC (rev 4860)
+++ source	2010-03-23 08:45:50 UTC (rev 4861)
@@ -11975,21 +11975,86 @@
 
    <dd>
 
-    <p>Contains a comma-separated list of keywords relevant to the page.</p>
+    <p>The value must be a <span>set of comma-separated tokens</span>,
+    each of which is a keyword relevant to the page.</p>
 
-    <p>Note that many search engines have stopped to consider keyword
-    information as relevant because it has been used unreliably or even
-    misleading. Recipients are recommended to use this information only
-    when there's sufficient confidence in the reliability of this
-    information, for instance in controlled environments such as sites
-    generated from a content management system.</p>
+    <div class="example">
 
-    <p class="XXX">The text above is not in the right form for the
-    spec (no conformance criteria, the note uses the wrong writing
-    style, no examples, uses the wrong terminology for consistency
-    with this spec, etc), but is what the working group agreed. It
-    will be fixed momentarily.</p>
+     <p>This page about typefaces on British motorways uses a
+     <code>meta</code> element to specify some keywords that users
+     might use to look for the page:</p>
 
+     <pre><!DOCTYPE HTML>
+<html>
+ <head>
+  <title>Typefaces on UK motorways</title>
+  <meta name="keywords" content="british,type face,font,fonts,highway,highways">
+ </head>
+ <body>
+  ...</pre>
+
+    </div>
+
+    <p class="note">Many search engines do not consider such keywords,
+    because this feature has historically been used unreliably and
+    even misleadingly as a way to spam search engine results in a way
+    that is not helpful for users.</p>
+
+    <div class="impl">
+
+    <p>To obtain the list of keywords that the author has specified as
+    applicable to the page, the user agent must run the following
+    steps:</p>
+
+    <ol>
+
+     <li><p>Let <var title="">keywords</var> be an empty
+     list.</p></li>
+
+     <li>
+
+      <p>For each <code>meta</code> element with a <code
+      title="attr-meta-name">name</code> attribute and a <code
+      title="attr-meta-content">content</code> attribute and whose
+      <code title="attr-meta-name">name</code> attribute's value is
+      <code title="meta-keywords">keywords</code>, run the following
+      substeps:</p>
+
+      <ol>
+
+       <li><p><span title="split a string on commas">Split the value
+       of the element's <code title="attr-meta-content">content</code>
+       attribute on commas</span>.</p></li>
+
+       <li><p>Add the resulting tokens, if any, to <var
+       title="">keywords</var>.</p></li>
+
+      </ol>
+
+     </li>
+
+     <li><p>Remove any duplicates from <var
+     title="">keywords</var>.</p></li>
+
+     <li><p>Return <var title="">keywords</var>. This is the list of
+     keywords that the author has specified as applicable to the
+     page.</p></li>
+
+    </ol>
+
+    <p>User agents should not use this information when there is
+    insufficient confidence in the reliability of the value.</p>
+
+    <p class="example">For instance, it would be reasonable for a
+    content management system to use the keyword information of pages
+    within the system to populate the index of a site-specific search
+    engine, but a large-scale content aggregator that used this
+    information would likely find that certain users would try to game
+    its ranking mechanism through the use of inappropriate
+    keywords.</p>
+
+    </div>
+
    </dd>
 
   </dl>




More information about the Commit-Watchers mailing list