Skip to content

Commit

Permalink
[e] (0) Remove use of the word 'recommended'.
Browse files Browse the repository at this point in the history 
Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=18761
Affected topics: DOM APIs, HTML, HTML Syntax and Parsing, Security, Web Storage

git-svn-id: http://svn.whatwg.org/webapps@7507 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
@Hixie
Hixie committed Nov 6, 2012
1 parent afa251e commit 1e4754a
Show file tree
Hide file tree
Showing 3 changed files with 97 additions and 133 deletions.
78 changes: 33 additions & 45 deletions complete.html
View file
Expand Up @@ -248,7 +248,7 @@

<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 5 November 2012</h2>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 6 November 2012</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
Expand Down Expand Up @@ -308,7 +308,7 @@ <h2 class="no-num no-toc">Living Standard &mdash; Last Updated 5 November 2012</
<li><a href=#presentational-markup><span class=secno>1.12.1 </span>Presentational markup</a></li>
<li><a href=#syntax-errors><span class=secno>1.12.2 </span>Syntax errors</a></li>
<li><a href=#restrictions-on-content-models-and-on-attribute-values><span class=secno>1.12.3 </span>Restrictions on content models and on attribute values</a></ol></li>
<li><a href=#recommended-reading><span class=secno>1.13 </span>Recommended reading</a></ol></li>
<li><a href=#suggested-reading><span class=secno>1.13 </span>Suggested reading</a></ol></li>
<li><a href=#infrastructure><span class=secno>2 </span>Common infrastructure</a>
<ol>
<li><a href=#terminology><span class=secno>2.1 </span>Terminology</a>
Expand Down Expand Up @@ -3154,7 +3154,7 @@ <h4 id=restrictions-on-content-models-and-on-attribute-values><span class=secno>

</dd>

</dl><h3 id=recommended-reading><span class=secno>1.13 </span>Recommended reading</h3>
</dl><h3 id=suggested-reading><span class=secno>1.13 </span>Suggested reading</h3>

<p><i>This section is non-normative.</i></p>

Expand Down Expand Up @@ -3605,13 +3605,11 @@ <h3 id=conformance-requirements><span class=secno>2.2 </span>Conformance require
non-normative, as are all sections explicitly marked non-normative.
Everything else in this specification is normative.</p>

<p>The key words "MUST", "MUST NOT", "REQUIRED", <!--"SHALL", "SHALL
NOT",--> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in the normative parts of this document are to be
interpreted as described in RFC2119. The key word "OPTIONALLY" in
the normative parts of this document is to be interpreted with the
same normative meaning as "MAY" and "OPTIONAL". For readability,
these words do not appear in all uppercase letters in this
<p>The key words "MUST", "MUST NOT", "REQUIRED", <!--"SHALL", "SHALL NOT",--> "SHOULD", "SHOULD
NOT", <!--"RECOMMENDED", "NOT RECOMMENDED",--> "MAY", and "OPTIONAL" in the normative parts of
this document are to be interpreted as described in RFC2119. The key word "OPTIONALLY" in the
normative parts of this document is to be interpreted with the same normative meaning as "MAY" and
"OPTIONAL". For readability, these words do not appear in all uppercase letters in this
specification. <a href=#refsRFC2119>[RFC2119]</a></p>

<div class=impl>
Expand Down Expand Up @@ -26213,16 +26211,13 @@ <h6 id=an-image-in-an-e-mail-or-private-document-intended-for-a-specific-person-
known to the author, such as documents on a Web site, e-mails sent
to public mailing lists, or software documentation.</i></p>

<p>When an image is included in a private communication (such as an
HTML e-mail) aimed at a specific person who is known to be able to
view images, the <code title=attr-img-alt><a href=#attr-img-alt>alt</a></code> attribute may
be omitted. However, even in such cases it is strongly recommended
that alternative text be included (as appropriate according to the
kind of image involved, as described in the above entries), so that
the e-mail is still usable should the user use a mail client that
does not support images, or should the document be forwarded on to
other users whose abilities might not include easily seeing
images.</p>
<p>When an image is included in a private communication (such as an HTML e-mail) aimed at a
specific person who is known to be able to view images, the <code title=attr-img-alt><a href=#attr-img-alt>alt</a></code>
attribute may be omitted. However, even in such cases authors are strongly urged to include
alternative text (as appropriate according to the kind of image involved, as described in the
above entries), so that the e-mail is still usable should the user use a mail client that does not
support images, or should the document be forwarded on to other users whose abilities might not
include easily seeing images.</p>



Expand Down Expand Up @@ -60707,9 +60702,8 @@ <h4 id=downloading-resources><span class=secno>4.12.4 </span>Downloading resourc
<a href=#as-a-download>as a download</a>, it should select one using the following
algorithm.</p>

<p class=warning>This algorithm is intended to mitigate security
dangers involved in downloading files from untrusted sites, and user
agents are strongly recommended to follow it.</p> <!-- but it's
<p class=warning>This algorithm is intended to mitigate security dangers involved in downloading
files from untrusted sites, and user agents are strongly urged to follow it.</p> <!-- but it's
optional, since it's not really an interoperability issue -->

<ol><li><p>Let <var title="">filename</var> be the void value.</li>
Expand Down Expand Up @@ -62434,7 +62428,7 @@ <h4 id=conversations><span class=secno>4.13.4 </span>Conversations</h4>
<h4 id=footnotes><span class=secno>4.13.5 </span>Footnotes</h4>

<p>HTML does not have a dedicated mechanism for marking up
footnotes. Here are the recommended alternatives.</p>
footnotes. Here are the suggested alternatives.</p>

<hr><p>For short inline annotations, the <code title=attr-title><a href=#attr-title>title</a></code> attribute could <!-- SHOULD, modulo
title-warning --> be used.</p>
Expand Down Expand Up @@ -77453,11 +77447,10 @@ <h5 id=security-and-privacy><span class=secno>7.5.1.3 </span>Security and privac
trivially tracked, and would allow user information, even in secure
connections, to be collected.</p>

<p><strong>Hijacking defaults.</strong> It is strongly recommended
that user agents do not automatically change any defaults, as this
could lead the user to send data to remote hosts that the user is
not expecting. New handlers registering themselves should never
automatically cause those sites to be used.</p>
<p><strong>Hijacking defaults.</strong> User agents are strongly urged to not automatically change
any defaults, as this could lead the user to send data to remote hosts that the user is not
expecting. New handlers registering themselves should never automatically cause those sites to be
used.</p>

<p><strong>Registration spamming.</strong> User agents should
consider the possibility that a site will attempt to register a
Expand Down Expand Up @@ -87261,10 +87254,8 @@ <h3 id=disk-space-0><span class=secno>11.3 </span>Disk space</h3>
title="dom-Storage-setItem">setItem()</code> call, the method will
throw an exception.</p>-->

<p>A mostly arbitrary limit of five megabytes per
<a href=#origin>origin</a> is recommended. Implementation feedback is
welcome and will be used to update this suggestion in the
future.</p>
<p>A mostly arbitrary limit of five megabytes per <a href=#origin>origin</a> is suggested. Implementation
feedback is welcome and will be used to update this suggestion in the future.</p>


<h3 id=privacy><span class=secno>11.4 </span>Privacy</h3>
Expand Down Expand Up @@ -87417,12 +87408,10 @@ <h4 id=dns-spoofing-attacks><span class=secno>11.5.1 </span>DNS spoofing attacks

<h4 id=cross-directory-attacks><span class=secno>11.5.2 </span>Cross-directory attacks</h4>

<p>Different authors sharing one host name, for example users
hosting content on <code>geocities.com</code>, all share one local
storage object. There is no feature to restrict the access by
pathname. Authors on shared hosts are therefore recommended to avoid
using these features, as it would be trivial for other authors to
read the data and overwrite it.</p>
<p>Different authors sharing one host name, for example users hosting content on
<code>geocities.com</code>, all share one local storage object. There is no feature to restrict
the access by pathname. Authors on shared hosts are therefore urged to avoid using these features,
as it would be trivial for other authors to read the data and overwrite it.</p>

<p class=note>Even if a path-restriction feature was made
available, the usual DOM scripting security model would make it
Expand Down Expand Up @@ -89177,11 +89166,11 @@ <h5 id=character-encodings-0><span class=secno>12.2.2.2 </span>Character encodin
<hr><p>User agents must not support the CESU-8, UTF-7, BOCU-1 and SCSU
encodings. <a href=#refsCESU8>[CESU8]</a> <a href=#refsUTF7>[UTF7]</a> <a href=#refsBOCU1>[BOCU1]</a> <a href=#refsSCSU>[SCSU]</a></p>

<p>Support for encodings based on EBCDIC is not recommended. This
encoding is rarely used for publicly-facing Web content.</p>
<p>Support for encodings based on EBCDIC is discouraged. This encoding is rarely used for
publicly-facing Web content.</p>

<p>Support for UTF-32 is not recommended. This encoding is rarely
used, and frequently implemented incorrectly.</p>
<p>Support for UTF-32 is also discouraged. This encoding is rarely used, and frequently
implemented incorrectly.</p>

<p class=note>This specification does not make any attempt to
support EBCDIC-based encodings and UTF-32 in its algorithms; support
Expand Down Expand Up @@ -101039,8 +101028,7 @@ <h4 id=other-elements,-attributes-and-apis><span class=secno>15.3.4 </span>Other
&lt;meta name="eGMS.subject.keyword" scheme="LGCL" content="Abandoned vehicles"&gt;
&lt;meta name="eGMS.subject.keyword" scheme="ORLY" content="Mah car: kthxbye"&gt;</pre>

<p>The recommended processing of this markup, however, would be
equivalent to the following:</p>
<p>The suggested processing of this markup, however, would be equivalent to the following:</p>

<pre>&lt;meta name="eGMS.subject.keyword" content="Abandoned vehicles"&gt;
&lt;meta name="eGMS.subject.keyword" content="Mah car: kthxbye"&gt;</pre>
Expand Down
78 changes: 33 additions & 45 deletions index
View file
Expand Up @@ -248,7 +248,7 @@

<header class=head id=head><p><a class=logo href=http://www.whatwg.org/><img alt=WHATWG height=101 src=/images/logo width=101></a></p>
<hgroup><h1 class=allcaps>HTML</h1>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 5 November 2012</h2>
<h2 class="no-num no-toc">Living Standard &mdash; Last Updated 6 November 2012</h2>
</hgroup><dl><dt><strong>Web developer edition:</strong></dt>
<dd><strong><a href=http://developers.whatwg.org/>http://developers.whatwg.org/</a></strong></dd>
<dt>Multiple-page version:</dt>
Expand Down Expand Up @@ -308,7 +308,7 @@
<li><a href=#presentational-markup><span class=secno>1.12.1 </span>Presentational markup</a></li>
<li><a href=#syntax-errors><span class=secno>1.12.2 </span>Syntax errors</a></li>
<li><a href=#restrictions-on-content-models-and-on-attribute-values><span class=secno>1.12.3 </span>Restrictions on content models and on attribute values</a></ol></li>
<li><a href=#recommended-reading><span class=secno>1.13 </span>Recommended reading</a></ol></li>
<li><a href=#suggested-reading><span class=secno>1.13 </span>Suggested reading</a></ol></li>
<li><a href=#infrastructure><span class=secno>2 </span>Common infrastructure</a>
<ol>
<li><a href=#terminology><span class=secno>2.1 </span>Terminology</a>
Expand Down Expand Up @@ -3154,7 +3154,7 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d

</dd>

</dl><h3 id=recommended-reading><span class=secno>1.13 </span>Recommended reading</h3>
</dl><h3 id=suggested-reading><span class=secno>1.13 </span>Suggested reading</h3>

<p><i>This section is non-normative.</i></p>

Expand Down Expand Up @@ -3605,13 +3605,11 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
non-normative, as are all sections explicitly marked non-normative.
Everything else in this specification is normative.</p>

<p>The key words "MUST", "MUST NOT", "REQUIRED", <!--"SHALL", "SHALL
NOT",--> "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in the normative parts of this document are to be
interpreted as described in RFC2119. The key word "OPTIONALLY" in
the normative parts of this document is to be interpreted with the
same normative meaning as "MAY" and "OPTIONAL". For readability,
these words do not appear in all uppercase letters in this
<p>The key words "MUST", "MUST NOT", "REQUIRED", <!--"SHALL", "SHALL NOT",--> "SHOULD", "SHOULD
NOT", <!--"RECOMMENDED", "NOT RECOMMENDED",--> "MAY", and "OPTIONAL" in the normative parts of
this document are to be interpreted as described in RFC2119. The key word "OPTIONALLY" in the
normative parts of this document is to be interpreted with the same normative meaning as "MAY" and
"OPTIONAL". For readability, these words do not appear in all uppercase letters in this
specification. <a href=#refsRFC2119>[RFC2119]</a></p>

<div class=impl>
Expand Down Expand Up @@ -26213,16 +26211,13 @@ href="?audio"&gt;audio&lt;/a&gt; test instead.)&lt;/p&gt;</pre>
known to the author, such as documents on a Web site, e-mails sent
to public mailing lists, or software documentation.</i></p>

<p>When an image is included in a private communication (such as an
HTML e-mail) aimed at a specific person who is known to be able to
view images, the <code title=attr-img-alt><a href=#attr-img-alt>alt</a></code> attribute may
be omitted. However, even in such cases it is strongly recommended
that alternative text be included (as appropriate according to the
kind of image involved, as described in the above entries), so that
the e-mail is still usable should the user use a mail client that
does not support images, or should the document be forwarded on to
other users whose abilities might not include easily seeing
images.</p>
<p>When an image is included in a private communication (such as an HTML e-mail) aimed at a
specific person who is known to be able to view images, the <code title=attr-img-alt><a href=#attr-img-alt>alt</a></code>
attribute may be omitted. However, even in such cases authors are strongly urged to include
alternative text (as appropriate according to the kind of image involved, as described in the
above entries), so that the e-mail is still usable should the user use a mail client that does not
support images, or should the document be forwarded on to other users whose abilities might not
include easily seeing images.</p>



Expand Down Expand Up @@ -60707,9 +60702,8 @@ fur
<a href=#as-a-download>as a download</a>, it should select one using the following
algorithm.</p>

<p class=warning>This algorithm is intended to mitigate security
dangers involved in downloading files from untrusted sites, and user
agents are strongly recommended to follow it.</p> <!-- but it's
<p class=warning>This algorithm is intended to mitigate security dangers involved in downloading
files from untrusted sites, and user agents are strongly urged to follow it.</p> <!-- but it's
optional, since it's not really an interoperability issue -->

<ol><li><p>Let <var title="">filename</var> be the void value.</li>
Expand Down Expand Up @@ -62434,7 +62428,7 @@ fur
<h4 id=footnotes><span class=secno>4.13.5 </span>Footnotes</h4>

<p>HTML does not have a dedicated mechanism for marking up
footnotes. Here are the recommended alternatives.</p>
footnotes. Here are the suggested alternatives.</p>

<hr><p>For short inline annotations, the <code title=attr-title><a href=#attr-title>title</a></code> attribute could <!-- SHOULD, modulo
title-warning --> be used.</p>
Expand Down Expand Up @@ -77453,11 +77447,10 @@ interface <dfn id=navigatorcontentutils>NavigatorContentUtils</dfn> {
trivially tracked, and would allow user information, even in secure
connections, to be collected.</p>

<p><strong>Hijacking defaults.</strong> It is strongly recommended
that user agents do not automatically change any defaults, as this
could lead the user to send data to remote hosts that the user is
not expecting. New handlers registering themselves should never
automatically cause those sites to be used.</p>
<p><strong>Hijacking defaults.</strong> User agents are strongly urged to not automatically change
any defaults, as this could lead the user to send data to remote hosts that the user is not
expecting. New handlers registering themselves should never automatically cause those sites to be
used.</p>

<p><strong>Registration spamming.</strong> User agents should
consider the possibility that a site will attempt to register a
Expand Down Expand Up @@ -87261,10 +87254,8 @@ dictionary <dfn id=storageeventinit>StorageEventInit</dfn> : <a href=#eventinit>
title="dom-Storage-setItem">setItem()</code> call, the method will
throw an exception.</p>-->

<p>A mostly arbitrary limit of five megabytes per
<a href=#origin>origin</a> is recommended. Implementation feedback is
welcome and will be used to update this suggestion in the
future.</p>
<p>A mostly arbitrary limit of five megabytes per <a href=#origin>origin</a> is suggested. Implementation
feedback is welcome and will be used to update this suggestion in the future.</p>


<h3 id=privacy><span class=secno>11.4 </span>Privacy</h3>
Expand Down Expand Up @@ -87417,12 +87408,10 @@ dictionary <dfn id=storageeventinit>StorageEventInit</dfn> : <a href=#eventinit>

<h4 id=cross-directory-attacks><span class=secno>11.5.2 </span>Cross-directory attacks</h4>

<p>Different authors sharing one host name, for example users
hosting content on <code>geocities.com</code>, all share one local
storage object. There is no feature to restrict the access by
pathname. Authors on shared hosts are therefore recommended to avoid
using these features, as it would be trivial for other authors to
read the data and overwrite it.</p>
<p>Different authors sharing one host name, for example users hosting content on
<code>geocities.com</code>, all share one local storage object. There is no feature to restrict
the access by pathname. Authors on shared hosts are therefore urged to avoid using these features,
as it would be trivial for other authors to read the data and overwrite it.</p>

<p class=note>Even if a path-restriction feature was made
available, the usual DOM scripting security model would make it
Expand Down Expand Up @@ -89177,11 +89166,11 @@ dictionary <dfn id=storageeventinit>StorageEventInit</dfn> : <a href=#eventinit>
<hr><p>User agents must not support the CESU-8, UTF-7, BOCU-1 and SCSU
encodings. <a href=#refsCESU8>[CESU8]</a> <a href=#refsUTF7>[UTF7]</a> <a href=#refsBOCU1>[BOCU1]</a> <a href=#refsSCSU>[SCSU]</a></p>

<p>Support for encodings based on EBCDIC is not recommended. This
encoding is rarely used for publicly-facing Web content.</p>
<p>Support for encodings based on EBCDIC is discouraged. This encoding is rarely used for
publicly-facing Web content.</p>

<p>Support for UTF-32 is not recommended. This encoding is rarely
used, and frequently implemented incorrectly.</p>
<p>Support for UTF-32 is also discouraged. This encoding is rarely used, and frequently
implemented incorrectly.</p>

<p class=note>This specification does not make any attempt to
support EBCDIC-based encodings and UTF-32 in its algorithms; support
Expand Down Expand Up @@ -101039,8 +101028,7 @@ if (s = prompt('What is your name?')) {
&lt;meta name="eGMS.subject.keyword" scheme="LGCL" content="Abandoned vehicles"&gt;
&lt;meta name="eGMS.subject.keyword" scheme="ORLY" content="Mah car: kthxbye"&gt;</pre>

<p>The recommended processing of this markup, however, would be
equivalent to the following:</p>
<p>The suggested processing of this markup, however, would be equivalent to the following:</p>

<pre>&lt;meta name="eGMS.subject.keyword" content="Abandoned vehicles"&gt;
&lt;meta name="eGMS.subject.keyword" content="Mah car: kthxbye"&gt;</pre>
Expand Down

0 comments on commit 1e4754a

Please sign in to comment.