W3C home > Mailing lists > Public > public-html-diffs@w3.org > March 2010

hixie: Fix the text added for ISSUE-79 to use appropriate terminology and to fit the style of the specification. (whatwg r4861)

From: poot <cvsmail@w3.org>
Date: Tue, 23 Mar 2010 17:46:59 +0900 (JST)
To: public-html-diffs@w3.org
Message-Id: <20100323084659.A73F52BC06@toro.w3.mag.keio.ac.jp>
hixie: Fix the text added for ISSUE-79 to use appropriate terminology
and to fit the style of the specification. (whatwg r4861)


RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3893
retrieving revision 1.3894
diff -u -d -r1.3893 -r1.3894
--- Overview.html	23 Mar 2010 07:12:08 -0000	1.3893
+++ Overview.html	23 Mar 2010 08:46:28 -0000	1.3894
@@ -9865,20 +9865,73 @@
-    <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>&lt;!DOCTYPE HTML&gt;
+ &lt;head&gt;
+  &lt;title&gt;Typefaces on UK motorways&lt;/title&gt;
+  &lt;meta name="keywords" content="british,type face,font,fonts,highway,highways"&gt;
+ &lt;/head&gt;
+ &lt;body&gt;
+  ...</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>
Received on Tuesday, 23 March 2010 08:47:28 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:46 UTC