manual-of-style/index.html

<!DOCTYPE html>
<html lang="en-US">
<head>
  <meta charset="utf-8">
  <title>W3C Manual of Style</title>
  <script src='https://www.w3.org/Tools/respec/respec-w3c.js' async class='remove'>
  </script>
  <script class='remove'>
    var respecConfig = {
      specStatus: "base",
      editors: [
        {
          name: "Philippe Le Hegaret",
          url: "https://www.w3.org/People/LeHegaret",
        },
        {
          name: "Coralie Mercier",
          url: "https://www.w3.org/People/Coralie",
        }
      ],
      latestVersion: "https://www.w3.org/guide/manual-of-style/",
      edDraftURI: null,
      license: 'w3c-software-doc',
      github: "w3c/guide",
      otherLinks: [{
        key: 'Mailing list',
        data: [{
          value: 'spec-prod@w3.org',
          href: 'https://lists.w3.org/Archives/Public/spec-prod/'
        }]
      }],
      xref: [ "i18n-glossary" ]
    };
  </script>
</head>

<body>

<section id='abstract'>
<p>This manual is a guide containing best current practice, written for editors and authors of W3C technical reports. No requirements
for W3C publications are in this document. All requirements for W3C
publications are in <a href="https://www.w3.org/pubrules/doc">W3C
Publication Rules</a>.</p>
</section>

<section id="sotd">

</section>
<section id="Introduction">
<h2>Introduction</h2>

<p>Written for editors and authors of W3C technical reports, this
document assumes that the reader is familiar with the <cite>Style Guide for Online
Hypertext</cite> [<cite><a href=
"#ref-STYLE-GUIDE">STYLE-GUIDE</a></cite>]. It is a companion to the
REQUIRED <cite>Technical Report Publication
Policy</cite> [<cite><a href="#ref-PUBRULES">PUBRULES</a></cite>],
called "pubrules" for short. Following the advice in this manual has
benefits:</p>

<ul>
<li>Non-native English readers, native English readers, and translators
will find your text easy to read and implement.</li>

<li>All audiences can concentrate on ideas rather than the mechanics of
reading.</li>

<li>Polished at early public maturity levels, clean copy eliminates
multiple "typo" reports.</li>
</ul>

<p>Bear in mind that our reports are used as world-class primary
reference material. Readability across a wide variety of browsers and
platforms is far more important than using jazzy features. At some
point, what we write becomes history and is preserved on the web
through the W3C <cite><a href=
"https://www.w3.org/policies/uri-persistence/">Persistence
Policy</a></cite> [<cite><a href=
"#ref-PERSISTENCE">PERSISTENCE</a></cite>].</p>
</section>
<section id="Validation">
<h2>Validation</h2>

<ul>
<li>Make sure there are no broken links in your documents at the time
of publication. Some services on the web may help you with this,
including the <cite>W3C Link Checker</cite> [<cite><a href=
"#ref-CHECKLINK">CHECKLINK</a></cite>]. Append ",checklink" to a W3C
<abbr title="Uniform Resource Identifier">URI</abbr> to invoke the link
checker.</li>

<li>Make sure your technical report validates in the <cite>W3C Markup
Validation Service</cite> [<cite><a href=
"#ref-VALIDATE">VALIDATE</a></cite>]. Append ",validate" to a W3C
<abbr title="Uniform Resource Identifier">URI</abbr> to invoke the
validator.</li>

<li>Make sure your technical report validates in the <cite>W3C
<abbr title="Cascading Style Sheets">CSS</abbr> Validation
Service</cite> [<cite><a href=
"#ref-CSSVALIDATE">CSSVALIDATE</a></cite>]. Append ",cssvalidate" to a
W3C <abbr title="Uniform Resource Identifier">URI</abbr> to invoke the
<abbr title="Cascading Style Sheets">CSS</abbr> validator.</li>

<li>Make sure any examples in your document validate as well.</li>
</ul>

<p><strong>Note.</strong> It is the editor's responsibility to ensure
that documents are valid before requesting publication.</p>
</section>
<section id="Accessibility">
<h2>Accessibility</h2>

<ul>
<li>Follow the <cite><a href="https://www.w3.org/WAI/standards-guidelines/wcag/">Web Content Accessibility Guidelines</a></cite>
(<abbr>WCAG</abbr>). Can
simpler words express your ideas? Is your text marked up with
structural elements? Are alternatives provided for auditory and visual
content? See also <a href="https://www.w3.org/WAI/test-evaluate/">evaluation tools</a>.</li>
</ul>
</section>
<section id="I18n">
<h2>Internationalization</h2>

<p>Follow the guidelines in <cite>Internationalization Best Practices for Spec Developers</cite> [[INTERNATIONAL-SPECS]] when producing your specification. You might also find it helpful to complete a <a href="https://www.w3.org/International/i18n-drafts/techniques/shortchecklist">self-review</a> early in the development process. If your specification touches on more complex issues, you can also reach out to the Internationalization Working Group for guidance.</p>

<p>Internationalization terminology, particularly terms related to Unicode, can be rather precise. To help avoid problems with the need to define these, import the [[Infra]] standard and [[I18N-GLOSSARY]]. Use the terms found in these documents instead of creating your own and link your use of these terms to the definitions found in these documents. Instructions on how to do this can be found in an appendix of the [[I18N-GLOSSARY]].</p>

<section id="general-i18n">
	<h3>Write for a global audience</h3>
	
	<p>Keep in mind that W3C documents serve a global audience.</p>
	
	<ul>
		<li>Avoid idioms that are U.S.- or English-specific in favor of more descriptive language.</li>
		<li>Choose examples that reflect a global audience. For example:
		<ul>
			<li>When creating user stories or other examples that feature people, choose example names that come from different cultures and regions. You can find suggestions <a href="https://www.w3.org/TR/international-specs/#personal_name_examples">here</a> in [[INTERNATIONAL-SPECS]].</li>
			<li>Choose more generic terms for field names, such as "postal code" instead of (U.S.-specific) "ZIP code" or "given name" instead of "first name".</li>
		</ul>
		<li>In general, use [=locale-neutral=] representations of data values, such as dates, numbers, currency values, and so forth.</li>
		<!-- EDNOTE: A previous edition had a section with the id of `Dates`. The id is preserved here to avoid problems
		     with any links to the older edition.
		  -->
		<li id="Dates">For time and date values, choose an unambiguous representation:
		<ul>
			<li>For date values that appear in prose, spell out the month (for example, <kbd>6 May 2003</kbd> or <kbd>September 23, 2016</kbd>). All numeric dates such as <kbd translate="no">5/6/03</kbd> or <kbd translate="no">6/5/03</kbd> are ambiguous. Some cultures will read the first example as "June 5" while other cultures will read the second example as that date.</li>
			<li>For date values that appear in data, use a format derived from ISO8601, such as those found in [[RFC3339]] or those found in <cite><a href="https://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#date" title="Section 3.2.9 of the XML Schema Datatypes">XML Schema Part 2: Datatypes</a></cite> ([[XMLSchema-2]].</li>
		</ul></li>
	</ul>
</section>

<section id="Unicode">
<h3>Unicode</h3>

<p>Use <code translate="no">U+XXXX</code> syntax to represent [=Unicode code points=] in the specification. These are space separated when appearing in a sequence. No additional decoration is needed. Note that a [=code point=] may contain four, five, or six hexadecimal digits. When fewer than four digits are needed, the code point number is zero filled.</p>

<aside class="example" title="Code point examples">
	<table>
		<thead>
			<tr>
				<th>Character</th>
				<th>Name</th>
				<th>U+XXXX syntax</th>
			</tr>
		</thead>
		<tbody>
			<tr>
				<td style="text-align:center">&#xa0;</td>
				<td class="uname">SPACE</td>
				<td>U+0020</td>
			</tr>
			<tr>
				<td style="text-align:center">&#xe9;</td>
				<td class="uname">LATIN SMALL LETTER E WITH ACUTE</td>
				<td>U+00E9</td>
			</tr>
			<tr>
				<td style="text-align:center">&#xa8a;</td>
				<td class="uname">GUJURATI LETTER UU</td>
				<td>U+0A8A</td>
			</tr>
			<tr>
				<td style="text-align:center">&#xfffd;</td>
				<td class="uname">REPLACEMENT CHARACTER</td>
				<td>U+FFFD</td>
			</tr>
			<tr>
				<td style="text-align:center">&#x1f62e;</td>
				<td class="uname">FACE WITH OPEN MOUTH</td>
				<td>U+1F62E</td>
			</tr>
		</tbody>
	</table>
</aside>

<p>Use the Unicode character name to describe specific code points. Use of the <a href="#char_ref_template">character naming template</a> is recommended.</p>

<p>Unicode assigns unique, immutable names to each assigned [=Unicode code point=]. Using these names in your specification when referring to specific characters (along with the code point in <code class="uname" translate="no">U+XXXX</code> notation) will help make your specification unambiguous.</p>

<p>There are cases where doing this is overly pedantic and detracts from usability, but be cautious about being so informal as to impair meaning.</p>

<section id="char_ref_template">
<h5>Character naming template</h5>

	<div class="xref"><span class="seealso">See also</span>
	<p>[<a href="https://www.w3.org/International/i18n-activity/guidelines/editing#codepoints">I18N Editing Guidelines</a>].</p>
	</div>
	
<p>Internationalization specifications use (and we recommend the use of) this template for character references:</p>

<pre>
&lt;span class="codepoint" translate="no">&lt;bdi lang="??">&#xXXXX;&lt;/bdi> 
[&lt;span class="uname">U+XXXX Unicode_character_name&lt;/span>]&lt;/span>
</pre>

<aside class="example" title="Example of a character reference">
<p>Filling in the above template like this:</p>

<pre>
&lt;span class="codepoint" translate="no">&lt;bdi lang="fr">&#x00E9;&lt;/bdi> 
[&lt;span class="uname">U+00E9 LATIN SMALL LETTER E WITH ACUTE&lt;/span>]&lt;/span>
</pre>

<p>Produces output in the page like this: <span class="codepoint" translate="no"><bdi lang="fr">é</bdi> [<span class="uname">U+00E9 LATIN SMALL LETTER E WITH ACUTE</span>]</span>.</p>
</aside>

<p>Some notes about the markup used. The <code translate=no>bdi</code> element is used to ensure that example characters that are [=right-to-left=] do not interfere with the layout of the page. The <code translate=no>lang</code> attribute should be filled in with the most appropriate [[BCP47]] [=language tag=] to get the correct font selection (and other processing) for a given context. Examples in East Asian languages (such as Chinese, Japanese, or Korean) or in the Arabic script can sometimes require greater care in choosing a language tag.</p>

</section>

</section>
<section id="Translations">
<h3>Translations</h3>

<p>W3C has no official translations of its technical reports. W3C does
encourage people to translate the technical reports and helps to track
translators and translations.</p>

<ul>
<li>A central translation page includes links to pages that document
translations of particular specifications [<cite><a href=
"#ref-TRANSLATE">TRANSLATE</a></cite>].</li>

<li>Read the <cite>W3C Intellectual Property <abbr title=
"Frequently Asked Questions list">FAQ</abbr></cite>, <cite><a href=
"https://www.w3.org/copyright/intellectual-rights/#translate">Can I
translate one of your specifications into another language?</a></cite>
and <cite><a href=
"https://www.w3.org/copyright/intellectual-rights/#official">Can I
create the "official" translation?</a></cite> ([<cite><a href=
"#ref-IPRFAQ">IPRFAQ</a></cite>] sections 5.6 and 5.7).</li>
</ul>


<p>Make your specification more readable by adding markup to distinguish common words from keywords in your language. Mark up every occurrence. Use <code>translate="no"</code> as an attribute to communicate to translators that the keyword is part of the [=vocabulary=] of a formal language rather than part of the [=natural language=] text of the document. For example:</p>
<pre class="html">
&lt;p&gt;The title attribute of these elements may be used 
to provide the full or expanded form of the expression.
</pre>

<p>becomes:</p>
<pre>
&lt;p&gt;The &lt;code translate="no"&gt;title&lt;/code&gt; attribute of these elements may be used 
to provide the full or expanded form of the expression.
</pre>

<p>A French translator would then know not to translate <em>title</em>
to <em lang="fr">titre</em>.</p>

<p>Do not invent elements to replace natural language. For example, do
not use <code>&lt;must/&gt;</code> and a style sheet to render MUST.
Other languages may need grammatical agreement with the sentence's
subject, <span class="not-en">e.g.</span>, in French, MUST will become
<em xml:lang="fr" lang="fr">DOIT</em> if the subject is singular, or
<em xml:lang="fr" lang="fr">DOIVENT</em> if it is plural. Use standard
markup instead.</p>
</section>

</section>

<section id="Parts">
<h2>The Parts of a Technical Report</h2>

<p id="Template">As of November 2005, <a href=
"https://www.w3.org/pubrules/doc">pubrules</a> [<cite><a href=
"#ref-PUBRULES">PUBRULES</a></cite>] includes a technical report
template.</p>

<section id="Title">
<h3>Document Title</h3>

<p>The title of your document in the document head and on the technical
reports index [<cite><a href="#ref-TR">TR</a></cite>] will read as
follows. Optional elements are in square brackets.</p>

<p>Title [(ACRONYM)] ["Specification"] ["Part" Part_Number] [:
Subtitle] ["Module"] [(nth "Edition")] ["Version" Version_Number]</p>

<p>See pubrules [<cite><a href="#ref-PUBRULES">PUBRULES</a></cite>] for
information about the use of "version" and "edition". "Level" and
"revised" are deprecated. Try not to invent a new titling
convention.</p>

<p>Capitalize title words following U.S. usage.</p>
</section>

<section id="Editors">
<h3>Editors and Authors</h3>

<section id="affs">
<h4>Managing Changing Affiliations</h4>

<p>Editor/Author affiliations change over time. Here are examples that
illustrate the suggested approach for managing them.</p>

<dl>
<dt>Still editor</dt>

<dd>Richard Ishida, W3C (and before at Xerox)</dd>

<dd>François Yergeau, Invited Expert (and before at Alis
Technologies)</dd>

<dd>Jane Doe, MyCompany (and before at ThierCompany, and at HisCompany,
and at HerCompany)</dd>

<dt>No longer editor</dt>

<dd>Martin J. Dürst (until Dec 2004 while at W3C)</dd>

<dd>Misha Wolf (until Dec 2002 while at Reuters Ltd.)</dd>

<dd>Tex Texin (until Dec 2004 while an Invited Expert, and before at
Progress Software)</dd>

<dd>FitzChivalry Farseer (until Oct 2005 while at AnyCompany, and
before at ThisCompany, and at ThatCompany)</dd>
</dl>
</section>
</section>
<section id="tAbstract">
  <h3>Abstract</h3>

<p><dfn id="must-abstract" class="lint-ignore">Give each document an
Abstract</dfn> (a few paragraphs at most) that summarizes what the
document is about. The Communications Team may use the Abstract as a
whole or in part to publicize your work. Write it for a non-technical
audience.</p>
</section>
<section id="Status">
  <h3>Status Section</h3>

<p>The "Status of This Document" section describes the document status
and publication context on the publication date. Pubrules
[<cite><a href="#ref-PUBRULES">PUBRULES</a></cite>] states the
requirements for the status section of each type of technical report
(<span class="not-en">e.g.</span>, use of customized and boilerplate text).</p>

<p>Since the status section does not change over time, express it in
terms that will be valid over time (<span class="not-en">e.g.</span>,
avoid the word "new"). Indicate the anticipated stability of the
document while recognizing that the future is unknown. Readers are
responsible for discovering the latest status information (<span class=
"not-en">e.g.</span>, by following the latest version link, or visiting
the W3C standards and drafts index [<cite><a href=
"#ref-TR">TR</a></cite>].</p>

<p>The custom paragraph is very important as it actually contains
information! In it, you should explain where a part of the energy of
the group has been invested. The custom paragraph should help a reader
decide "I really should read this draft." This implies that you
shouldn't paste it in from somewhere else. It should be very specific
to this document.</p>

<p>Tim Berners-Lee expressed the goal of the custom paragraph this way, "Don't be
afraid of being honest about the relevant techno-political situation."
In the custom paragraph, make the case for why someone should read this
draft.</p>

<p>In the custom paragraph, include what you would reply to a Member or
colleague who asked you such things as:</p>

<ul>
<li>Are we requesting that people implement this specification? If so,
where should experience reports be sent?</li>

<li>Are we requesting people do <em>not</em> implement the
specification until a later date? What sort of damage do we expect to
inflict on those who do by future changes to the document?</li>

<li>Does it reflect the consensus of a W3C Working Group? (Pay
attention to the authors and acknowledgments.)</li>

<li>Are there any changes expected?</li>

<li>Do we maintain a page of background information?</li>

<li>For pre-release drafts, state in the status section any limits on
redistribution, such as "Member confidential."</li>
</ul>
</section>
</section>
<section id="Errata">
  <h2>Errata</h2>

<p>All Recommendations have errors in them. They link to an errata page
that evolves over time. Since the errata page changes over time but a
specific version of a Recommendation does not, place the errata page
<strong>outside</strong> of the <kbd>/TR</kbd> hierarchy. There is an
expectation that documents in the "<abbr title=
"technical report">TR</abbr> zone" will not evolve over time
[<cite><a href="#ref-PERSISTENCE">PERSISTENCE</a></cite>]. For example,
locate errata pages in the portion of the web space dedicated to the
relevant Working Group or activity.</p>

<p>Clearly indicate on the errata page:</p>

<ul>
<li>The last modified date for the errata page.</li>

<li>The <abbr title="Uniform Resource Identifier">URI</abbr> of the
source document (<span class="not-en">i.e.</span>, the one with the
errata).</li>

<li>Where to find the latest version of the source document.</li>
</ul>

<p>For example (shown here without links):</p>

<dl style="margin-left: 10%">
<dt>This document:</dt>

<dd>https://www.w3.org/Style/css2-updates/REC-CSS2-19980512-errata</dd>

<dt>Last revised:</dt>

<dd>$Date: 2016/07/10 16:55:10 $</dd>

<dt>This document records known errors in the document:</dt>

<dd>https://www.w3.org/TR/1998/REC-CSS2-19980512</dd>

<dt>The latest version of the CSS 2 Recommendation:</dt>

<dd>https://www.w3.org/TR/REC-CSS2</dd>
</dl>

<p>On the errata page, list the newest entries nearer to the top.</p>

<section id='entries'>
<h3>Entries on an errata
page</h3>

<p>For each entry on the errata page, provide:</p>

<ol>
<li>A unique identifier</li>

<li>The date it was added to the errata page</li>

<li>A classification of the error (<span class="not-en">e.g.</span>, editorial, clarification, bug,
known problem with the document itself)</li>

<li>A short description of the problem and what part of the
Recommendation is affected.</li>

<li>Any proposed corrections and whether those corrections would affect
conformance of documents or software</li>

<li>Any normative corrections; see the section on <a href=
"https://www.w3.org/policies/process/20231103/#errata">Errata
Management</a> in the <cite>W3C Process Document</cite>
([<cite><a href="#ref-PROCESS">PROCESS</a></cite>] section 6.2.4) for
more information about normative corrections</li>
</ol>

<p>Do no remove entries from the errata page; if a correction turns out
to be incorrect, just add another entry (with a cross reference).</p>
</section>
</section>
<section id="References">
  <h2>References</a></h2>

<section id="extractor">
  <h3>Bibliography Extractor</h3>

<p>The <a href="https://www.specref.org/">SpecRef</a> tool, an open-source, community-maintained database of
web standards &amp; related references, contains an exhaustive of references.</p>

<p>The <cite><a href=
"http://www.w3.org/2002/01/tr-automation/tr-biblio-ui">W3C Bibliography
Extractor</a></cite> [<cite><a href=
"#ref-BIB-EXTRACT">BIB-EXTRACT</a></cite>] will automatically generate
a list of references in W3C style.</p>

</section>
<section id="citation">
  <h3>Citation</h3>

<p>Reference links (<span class="not-en">e.g.</span>, "[<abbr title=
"Extensible Markup Language">XML</abbr>]") link at least the first mention of a source to the References
section and take the form:</p>
<pre>
&lt;cite&gt;&lt;a href="http://www.example.org/example"&gt;Full Name&lt;/a&gt;&lt;/cite&gt; [&lt;cite&gt;&lt;a href="#ref-REFNAME"&gt;REFNAME&lt;/a&gt;&lt;/cite&gt;]
</pre>

<p>Parentheses around square brackets can be omitted unless the
parentheses would contain a section number.</p>

<p>References links occur at minimum at the first mention of the
source. Spell out what the reference link refers to at least in the
first occurrence, <span class="not-en">e.g.</span>,:</p>
<pre>
This is discussed in <cite>Namespaces in XML</cite> [XMLName].
</pre>

<p>or</p>
<pre>
This is discussed in the XML namespaces specification [XMLName].
</pre>

<p>and not</p>
<pre>
This is discussed in [XMLName].
</pre>
</section>
<section id="linking-within">
  <h3>Citing a Reference From Within a Document</h3>

<p>When linking from the middle of the document to an external
resource:</p>

<ol>
<li>Ensure that the link text, title, and context indicate you are
leaving the document, and</li>

<li>After the link, link to the reference in the references section,
and indicate section, page, or whatever is useful for those when the
link is unavailable (<span class="not-en">e.g.</span>, when printed).</li>
</ol>

<p>Thus, for example:</p>
<pre>
...as is done for the <a href=
"https://www.w3.org/TR/css-ui-3/#outline"
title=
"Section 4.1 of ">'outline' property of CSS Basic User Interface Module Level 3</a> ([<cite><a href=
"#ref-CSS3UI">CSS3UI</a></cite>], section 4.1).
</pre>
</section>
<section id="ref-section">
  <h3>References Section</h3>

<ul>
<li>All entries in a references section should be referred to in the
prose. If an entry is not referred to from the body of the document,
make it clear why it is in the References section.</li>

<li>If a reference is a W3C Recommendation track technical report that
has not reached Recommendation, state in the References section that it
is "work in progress."</li>

<li>It is helpful to include references to both persistent resources
and their latest version. Use titles for links. If there is an
institutionalized identifier (<abbr title=
"Uniform Resource Identifier">URI</abbr>) for a document, cite the most
specific identifier. For example, usually you would link the title to
<kbd>https://www.w3.org/TR/1999/REC-html401-19991224</kbd> rather than
to <kbd>https://www.w3.org/TR/html4/</kbd>. For more information on
using versioned and unversioned identifiers, refer to the
<cite><a href="https://www.w3.org/TR/charmod/#sec-RefUnicode">Character
Model for the World Wide Web 1.0: Fundamentals</a></cite>
([[CHARMOD]] section 8).</li>

<li>An entry in a references section takes this form:

<ul>
<li>Title, inside <code>a</code> (if available), inside
<code>cite</code></li>

<li>Comma-delimited list of authors' names</li>

<li>If there are no authors, use editors instead if available.
Following the last family name, say "eds." or "Editors."</li>

<li>Publisher, followed by the date of publication in the form DD Month
YYYY</li>

<li>A sentence containing a text-only <abbr title=
"Uniform Resource Identifier">URI</abbr></li>

<li>When available, a sentence ending in the latest version
<abbr title="Uniform Resource Identifier">URI</abbr></li>
</ul>

<p>Example:</p>

<dl>
<dt>[XML1]</dt>

<dd><cite><a href="https://www.w3.org/TR/2006/REC-xml-20060816/">Extensible Markup Language (XML) 1.0 (Fourth Edition)</a></cite>, T. Bray, J. Paoli, E. Maler, C. M. Sperberg-McQueen, F. Yergeau, Editors. World Wide Web Consortium, 16 August 2006, edited in place 29 September 2006. This edition of the XML 1.0 Recommendation is https://www.w3.org/TR/2006/REC-xml-20060816/. The <a href="https://www.w3.org/TR/xml/">latest edition of XML 1.0</a> is available at https://www.w3.org/TR/xml/.</dd>
</dl>

<p>Markup for the example above:</p>
<pre>
&lt;dl&gt;
&lt;dt&gt;&lt;a id="ref-XML1" name="ref-XML1"&gt;[XML1]&lt;/a&gt;&lt;/dt&gt;

&lt;dd&gt;&lt;cite&gt;&lt;a href="https://www.w3.org/TR/2006/REC-xml-20060816/"&gt;Extensible
Markup Language (XML) 1.0 (Fourth Edition)&lt;/a&gt;&lt;/cite&gt;,
T. Bray, J. Paoli, E. Maler, C. M. Sperberg-McQueen, F. Yergeau,
Editors. World Wide Web Consortium, 16 August 2006, edited in place
29 September 2006. This edition of the XML 1.0 Recommendation is
https://www.w3.org/TR/2006/REC-xml-20060816/. The &lt;a
href="https://www.w3.org/TR/xml/"&gt;latest edition of XML 1.0&lt;/a&gt;
is available at https://www.w3.org/TR/xml/.&lt;/dd&gt;
</pre>
</li>

<li>Reference titles are recommended, not the "<abbr title=
"Uniform Resource Identifier">URI</abbr>-in-your-face" idiom, as link
text; see [<cite><a href="#ref-REF-TITLES">REF-TITLES</a></cite>]. For
example, <strong>Do use</strong>: <kbd>&lt;cite&gt;&lt;a
href="https://www.w3.org/TR/2016/REC-html51-20161101/"&gt;HTML 5.1
Specification&lt;/a&gt;&lt;/cite&gt;</kbd>. Do not use:
<kbd>&lt;cite&gt;&lt;a
href="https://www.w3.org/TR/2016/REC-html51-20161101/"&gt;http://www.w3.org/TR/1999/REC-html401-19991224&lt;/a&gt;&lt;/cite&gt;</kbd>.</li>
</ul>
</section>
<section id="normative">

  <h3>Normative and Informative
References</h3>

<p>See <a href="https://www.w3.org/guide/process/tilt/normative-references.html">Normative References</a> and considerations by the Team.</p>

</section>
</section>
<section id="Revisions">
  <h2>Revisions</h2>

<p>See the <cite><a href=
"https://www.w3.org/policies/process/20231103/#rec-modify">W3C Process
Document</a></cite> ([<cite><a href="#ref-PROCESS">PROCESS</a></cite>]
section 6.3.11) for instructions on modifying a W3C Recommendation.</p>

<p><strong>Note:</strong> When a document is revised, the original
publication date remains the same (and on the W3C standards and drafts index
[<cite><a href="#ref-TR">TR</a></cite>] as well); see pubrules
[<cite><a href="#ref-PUBRULES">PUBRULES</a></cite>] for more
detail.</p>

<p>Be careful not to break links in revisions. If your document uses
latest version <abbr title="Uniform Resource Identifier">URI</abbr>s
with a fragment identifier, unless those anchors are maintained across
versions, links will break.</p>

</section>
<section id="Production">
  <h2>Editing tools</h2>

<p>Though the <abbr title="HyperText Markup Language">HTML</abbr> or
<abbr title="Extensible HyperText Markup Language">XHTML</abbr> version
of your specification is always the definitive one, many editors find the use of a tool easier
to work with.</p>
<p>The most popular editing tools are <a href='https://speced.github.io/bikeshed/'>Bikeshed</a> and <a href='https://github.com/speced/respec/wiki'>respec</a>.</p>
<p>For help with this process, you can ask
the experts on the public mailing list spec-prod@w3.org [<cite><a href=
"#ref-SPEC-PROD">SPEC-PROD</a></cite>].</p>

</section>
<section id="Normative">
  <h2>Normative material</h2>
  <section id="N-I-sections">
      <h3>Normative &amp; Informative sections</h3>

  <p>It is important that informative (non-normative) material
    is clearly distinguished from normative material. To this end:</p>
    <ul>
      <li>If the entire document is informative, say so at the top and
        do not reference RFC 2119 or use <a href="#RFC">RFC 2119 keywords</a>
      </li>
      <li>If some sections are informative, say so at the
        start of each section, and do not
        use <a href="#RFC">RFC 2119 keywords</a> in those sections
      </li>
      <li>Figures, examples and notes are assumed to always be informative.
        To avoid repetition, each figure, example or note does not say this.
        <span id="consistent-expectations">Thus,
          to avoid breaking user expectations,
          document editors <em class="rfc2119">MUST NOT</em> make any
          figure, example or note normative.</span>
      </li>
    </ul>
  </section>

<section id="RFC">
  <h3><abbr title=
"Request for Comments">RFC</abbr> 2119 Key Words</h3>

<p>Adhere to and credit <cite><abbr title=
"Request for Comments">RFC</abbr> 2119 Key words for use in
<abbr title="Request for Comments">RFC</abbr>s to Indicate Requirement
Levels</cite> [<cite><a href="#ref-KEYWORDS">KEYWORDS</a></cite>]
(<span class="not-en">e.g.</span>, "<em class="rfc2119">MUST</em>", "<em class="rfc2119">MUST NOT</em>", "<em class="rfc2119">REQUIRED</em>").</p>

<p>When these key words are used in the <abbr title=
"Request for Comments">RFC</abbr> sense, make them UPPERCASE, enclose
them in the <code>em</code> element, and style them with <abbr title=
"Cascading Style Sheets">CSS</abbr> class of rfc2119 to make the <em class=
"RFC2119">UPPERCASE</em> readable.</p>
<pre>
&lt;em title="MUST in RFC 2119 context"
       class="rfc2119"&gt;MUST&lt;/em&gt;

.rfc2119 {
  font-style: normal;
  font-size: 0.875em;
}
</pre>

<p>The author may explain why, if these key words are not used in the
<abbr title="Request for Comments">RFC</abbr> sense.</p>

<p>Where they are not <em><q cite=
"ftp://ftp.rfc-editor.org/in-notes/rfc2119.txt">required for
interoperation or to limit behavior which has potential for causing
harm</q></em> these key words <em><q cite=
"ftp://ftp.rfc-editor.org/in-notes/rfc2119.txt">must not be used to try
to impose a particular method on implementors where the method is not
required for interoperability.</q></em></p>

</section>
</section>

<section id="Editorial">
  <h2>Editorial Guidelines</h2>

<p>This section refers to editorial practice at W3C. It touches on
grammar, spelling, punctuation, case, linking, appearance and
markup.</p>

<section id="Grammar">
  <h3>Grammar</h3>

<ul>
<li>Delete repeated words.</li>

<li>Check subject-verb agreement.</li>

<li>Break long sentences.</li>

</ul>
</section>
<section id="Spelling">
  <h3>Spelling</h3>

<ul>
<li>Spell-check using a U.S. English dictionary. Append ",spell" to a
W3C <abbr title="Uniform Resource Identifier">URI</abbr> to invoke
W3C's spell checker.</li>

<li>Free dictionaries are also available on the <a title=
"Ispell home page" href=
"https://www.cs.hmc.edu/~geoff/ispell.html">Ispell home
page</a> [<cite><a href="#ref-ISPELL">ISPELL</a></cite>] for UNIX and
the <a title="Excalibur home page at Bucknell" href=
"http://www.eg.bucknell.edu/~excalibr/excalibur.html">Excalibur home
page</a> [<cite><a href="#ref-EXCAL">EXCAL</a></cite>] for Mac OS.</li>

<li>W3C uses <cite>Merriam-Webster's
Collegiate<sup><small>®</small></sup> Dictionary</cite>, 10th Edition
[<cite><a href="#ref-M-W">M-W</a></cite>], on the web as the spelling
arbiter because it is free, online, and available to every technical
report author and editor. </li>

<li>W3C uses U.S. English (<span class="not-en">e.g.</span>,
"standardise" should read "standardize" and "colour" should read
"color").</li>

<li>Form the plural of abbreviations, initialisms and acronyms without
an apostrophe (<span class="not-en">e.g.</span>, the plural of
<abbr title="Uniform Resource Identifier">URI</abbr> is <abbr title=
"Uniform Resource Identifiers">URIs</abbr> not <abbr title=
"Uniform Resource Identifiers">URI's</abbr>). See the FAQ
<cite>"Infrequently Asked Questions Concerning the Proper Spelling of
'DTD' in its Plural Form"</cite> [<cite><a href=
"#ref-PLURAL">PLURAL</a></cite>].</li>
</ul>
</section>
<section id="Punctuation">
  <h3>Punctuation</h3>

<ul>
<li>Use correct punctuation. A hard copy of <cite>The Chicago Manual of
Style</cite> or <cite>The Gregg Reference Manual</cite> may be of some
help.</li>

<li>Remember you are typing <abbr title=
"HyperText Markup Language">HTML</abbr> or <abbr title=
"Extensible Markup Language">XML</abbr> not TeX. Use quotation marks
rather than grave accents and apostrophes to quote text (<span class=
"not-en">e.g.</span>, ``value'' should read "value").</li>
</ul>

</section>
<section id="Case">
  <h3>Case, Combining Words, and Hyphenation</h3>

<ul>
<li>Capitalize W3C entities to match the <cite>W3C Process
Document</cite> [<cite><a href="#ref-PROCESS">PROCESS</a></cite>]
(<span class="not-en">e.g.</span>, Working Group, Recommendation).</li>

<li>Make the case, number of words, and hyphenation in terms match
<a href="#Terms">chapter 13</a>.</li>
</ul>

</section>
<section id="Misc">
  <h3>Miscellaneous</h3>

<ul>
<li>Spell out acronyms and initialisms in their first occurrence in
prose, for example, "Internet Engineering Task Force
(<abbr>IETF</abbr>)" or "Internationalization (<abbr>I18N</abbr>)." In
subsequent occurrences when they do not need to be spelled out, use
<code>abbr</code> elements, and give them
<code>title</code> attributes.</li>

<li>Check references (most commonly, for no full stop after the
<span class="not-en" xml:lang="la" lang="la">et</span> in et al.). </li>
</ul>

</section>
<section id="Linking">
  <h3>Linking</h3>

<ul>
<li>Unless intentionally referring to the latest document in a series,
always refer to specific W3C documents by using the "this version"
<abbr title="Uniform Resource Identifier">URI</abbr>.</li>

<li>If you are referring to a W3C document using either its this
version or latest version <abbr title=
"Uniform Resource Identifier">URI</abbr>, note whether the <abbr title=
"Uniform Resource Identifier">URI</abbr> ends in a slash or not. These
identifiers do not end in an extension such as "<kbd>.html</kbd>".
Include the extension when intentionally referring to a specific
version (<span class="not-en">e.g.</span>, a <abbr title=
"Graphics Interchange Format">GIF</abbr> image where <abbr title=
"Graphics Interchange Format">GIF</abbr> and <abbr title=
"Portable Network Graphics">PNG</abbr> are both available through
content negotiation).</li>

<li>Visible <abbr title="Uniform Resource Identifier">URI</abbr>s and
<code>href</code> attributes should have the same value.</li>
</ul>
</section>
<section id="Examples">
  <h3>Using Examples</h3>

<ul>
<li>Domains in examples adhere to section 3, "Reserved Example Second
Level Domain Names," in <cite><abbr title=
"Request for Comments">RFC</abbr> 2606</cite> [<cite><a href=
"#ref-DOMAINS">DOMAINS</a></cite>]. Use the domains
<kbd>example.com</kbd>, <kbd>example.org</kbd>, and
<kbd>example.net</kbd> for all examples. The Internet Assigned Numbers
Authority (IANA) reserves them for this purpose. If you need an
evocative name or the name of a business, use a machine name (<span
class="not-en">e.g.</span>, <kbd>https://cats.example.org</kbd>).</li>

<li>When not addressed by second level example domains, top level
domains (<abbr title="top level domain">TLD</abbr>s) adhere to section
2, "TLDs for Testing, &amp; Documentation Examples," in
<cite><abbr title="Request for Comments">RFC</abbr> 2606</cite>
[<cite><a href="#ref-DOMAINS">DOMAINS</a></cite>]. Use
<kbd>.test</kbd>, <kbd>.example</kbd>, <kbd>.invalid</kbd> or
<kbd>.localhost</kbd>.</li>

<li>Remember to validate markup in examples. Escaped characters pass
through routine validation.</li>

<li>W3C publications are copyrighted by W3C, and W3C liability,
trademark and document use rules apply. Note that in general, one
should not use material (text, photo, audio) in examples when the
copyright is not held by W3C. If the group wishes to publish
copyrighted materials, it should contact the Team legal staff (team-legal@w3.org).</li>

<li>
<p>Use <abbr title="Cascading Style Sheets">CSS</abbr> with
<code>div</code> elements to mark up examples, as is done in the
<a href="https://html.spec.whatwg.org/multipage/semantics.html#document-metadata"
title="Section 4.2. Document metadata">HTML Living Standard</a>
([<cite><a href="#ref-HTML">HTML</a></cite>], section
4.2):</p>
</li>
</ul>

</section>
<section id="Images">
  <h3>Images</h3>

<ul>
<li>We recommend that each image be available as PNG, even if you use
content negotiation to serve alternative formats.</li>

<li>Give images a background color (<span class="not-en">e.g.</span>,
white) so your technical report can be read with any style sheet
(<span class="not-en">e.g.</span>, with W3C's dark on light style
sheets, or a user style sheet that specifies a dark background).</li>

<li>Match image size to markup <code>width</code> and
<code>height</code> (or images will be distorted).</li>

<li>See the <a href="https://www.w3.org/TR/WCAG20-TECHS/">Web Content Accessibility
Guidelines Techniques</a> for information about providing alternative
text (<code>alt</code>) and long descriptions (<code>longdesc</code>)
for images. Also, don't forget to spell-check your alternative
text.</li>
</ul>

</section>
<section id="Markup">
  <h3>Markup</h3>

<ul>
<li>Use markup as it is intended. The <code>blockquote</code> and
<code>ul</code> and <code>li</code> elements were designed for
quotations and lists and not for indentation. Use <abbr title=
"Cascading Style Sheets">CSS</abbr> instead.</li>

<li>Remove extraneous non-breaking spaces.</li>

<li>Mark up attributes and elements consistently.</li>

<li>Make sure there are no <code>font</code> or <code>basefont</code>
elements in your document.</li>

<li>Make sure all <code>table</code> elements in your document are real
data tables, not tables used for layout.</li>

<li>Make sure there are no <code>bgcolor</code>,
<code>background</code>, <code>color</code>, <code>face</code>,
<code>marginheight</code>, <code>marginwidth</code> or
<code>size</code> attributes.</li>

<li>Give each page <code>lang="en-US"</code> on the <code>html</code>
element for <abbr title="HyperText Markup Language">HTML</abbr>, or
<code>xml:lang="en-US" lang="en-US"</code> on the <code>html</code>
element for <abbr title=
"Extensible HyperText Markup Language">XHTML</abbr> syntax.</li>

<li>Use the <code>span</code> element and <code>lang</code> and
<code>xml:lang</code> attributes for language changes within a
page.</li>

<li>Make semantic distinctions using more than only color, for example,
a font-style change, so that color-blind individuals can see a
difference.</li>

<li>Links with the anchor text "Click here" provide no context. The
visitor may become lost not knowing where "here" is. See also
<cite><a href="https://www.w3.org/QA/Tips/noClickHere">Don't use "click
here" as link text</a></cite> [<cite><a href=
"#ref-CLICK-HERE">CLICK-HERE</a></cite>].</li>

<li>Mark up data <code>table</code> headers with <code>th</code> not by
bolding a <code>td</code>.</li>
</ul>

</section>
<section id="Large">
  <h3>Large Documents</h3>

<p>Large single files that may be easy to print and search may not be
easy to download. For large documents:</p>

<ul>
<li>Divide the document logically, storing chapters in separate
files.</li>

<li>Offer a single-page, printable, searchable version of the
specification. This format may be compressed if large.</li>

<li>You can offer an archived version (zip, tar, tgz) of the separate
files. Provide all necessary file in archived versions including the
relevant style sheets. Don't link to images or style sheets not
included in the archive.</li>
</ul>

</section>
<section id="inclusive">
  <h3>Inclusive terminology</h3>

<p>Following the <a
  href="https://www.w3.org/policies/code-of-conduct/#expected-behavior">W3C Code of Conduct</a>,
<abbr title="World Wide Web Consortium">W3C</abbr> specifications are expected to be
inclusive and facilitate diversity. As such, editors and authors are strongly encouraged
to use a neutral and inclusive language to ensure the best environment possible for the
whole <abbr title="World Wide Web Consortium">W3C</abbr> community.</p>

<p>Here are proposed alternatives for some terms that <a
  href="https://www.w3.org/pubrules/">PubRules</a> (see <a
  href="https://www.w3.org/pubrules/badterms.json">list of terms in JSON</a>) shows a
warning about:</p>

<table id="neutrallanguage" class="data">
  <thead>
    <tr>
      <th>Terms to avoid</th>
      <th>Possible alternatives</th>
    </tr>
  </thead>
  <tbody>
  </tbody>
</table>

</ul>

</section>

</section>
<section id="MediaTypes">
  <h2>Internet Media Types</h2>

<ul>
<li>For information about defining a new Internet media type (formerly known as <abbr title="Multipurpose Internet Mail Extensions">MIME</abbr> type) in your specification, see <cite><a href=
"https://www.w3.org/guide/editor/mediatypes">Register an Internet Media Type for a W3C Specification</a></cite> [<cite><a href="#ref-REGISTER-1">REGISTER-1</a></cite>].</li>

<li>For information about referring to existing Internet media types (registered or not), see the email message <cite><a href=
"https://lists.w3.org/Archives/Public/www-tag/2006Aug/0012">TAG Position on Use of Unregistered Media Types in W3C Recommendations</a></cite> [<cite><a href="#ref-REGISTER-2">REGISTER-2</a></cite>].</li>
</ul>

</section>
<section id="Terms">
  <h2>Commonly Misspelled Terms</h2>

<p>W3C has reviewed its technical reports one by one since November
1999, for typographical errors. The following words appear often in
those reviews.</p>

<dl class="terms">
<dt>anti-alias</dt>

<dd>hyphenate</dd>

<dt><abbr title=
"American Standard Code for Information Interchange">ASCII</abbr></dt>

<dd>all caps</dd>

<dt>base64</dt>

<dd>lowercase, one word</dd>

<dt>Bézier</dt>

<dd>always capitalize, and accent the first e</dd>

<dt>braille</dt>

<dd>capitalize only when talking about Louis Braille</dd>

<dt>built-in</dt>

<dd>hyphenate when used as an adjective or noun, not when built is a
verb</dd>

<dt>color space</dt>

<dd>two words</dd>

<dt><abbr title="document type definition">DTDs</abbr></dt>

<dd>no apostrophe (see [<cite><a href=
"#ref-PLURAL">PLURAL</a></cite>])</dd>

<dt>dingbat</dt>

<dd>one word</dd>

<dt>ECMAScript</dt>

<dd>one word, cap S</dd>

<dt><span xml:lang="la" lang="la">et al.</span></dt>

<dd>no <span class="UnicodeName">full stop</span> after "et"</dd>

<dt><span class="UnicodeName">full stop</span> (.)</dt>

<dd><span class="UnicodeName">Full stop</span> is the formal name.
<span class="UnicodeAlias">Dot</span> and <span class=
"UnicodeAlias">period</span> are good aliases.</dd>

<dt><span class="UnicodeName">hash</span> (#)</dt>

<dd>also <span class="UnicodeAlias">number sign</span>, usually not <span class="UnicodeAlias">pound sign</span>, <span class="UnicodeAlias">crosshatch</span> or <span class="UnicodeAlias">octothorpe</span></dd>

<dt>heading</dt>

<dd>Term for <code>h1</code>-<code>h6</code>. Tables and HTTP have
headers.</dd>

<dt>HTTP/1.0</dt>

<dd>needs slash when referred to as a protocol, none in free text</dd>

<dt>HTTP/1.1</dt>

<dd>needs slash when referred to as a protocol, none in free text</dd>

<dt>homepage, home page</dt>

<dd>one word preferred, both allowed</dd>

<dt>Java</dt>

<dd>cap J</dd>

<dt>JavaScript</dt>

<dd>cap S</dd>

<dt>Level 1, 2, 3</dt>

<dd>cap L when referring to a W3C technical report</dd>

<dt>line feed</dt>

<dd>two words</dd>

<dt>lowercase</dt>

<dd>one word</dd>

<dt>markup</dt>

<dd>one word when used as a noun, two words when used as a verb</dd>

<dt><abbr title="Multipurpose Internet Mail Extensions">MIME</abbr> type</dt>

<dd>now Internet media type (MIME type is two words. MIME is all caps.)</dd>

<dt>namespace</dt>

<dd>lowercase unless referring to the <cite>Namespaces in XML</cite>
specification by name</dd>

<dt><span class="UnicodeName">number sign</span> (#)</dt>

<dd>also <span class="UnicodeAlias">hash</span>, usually not <span class="UnicodeAlias">pound sign</span>, <span class="UnicodeAlias">crosshatch</span> or <span class="UnicodeAlias">octothorpe</span></dd>

<dt>online</dt>

<dd>one word, no hyphen</dd>

<dt>PDF</dt>

<dd>all caps</dd>

<dt>PostScript</dt>

<dd>cap S</dd>

<dt>read-only</dt>

<dd>hyphenate</dd>

<dt>Real-Time Communication, real-time communication, real-time communications, RTC</dt>

<dd>In titles and headings, capitalize all words = Real-Time Communication</dd>
<dd>For the generic idea in sentences, lowercase = real-time communication or real-time communications &mdash; including with the acronym = real-time communications (RTC)</dd>

<dt>ruby</dt>

<dd>lowercase for the typographic convention. Uppercase for the programming language.</dd>

<dt>schema</dt>

<dd>lowercase</dd>

<dt>schemas</dt>

<dd>preferred to schemata</dd>

<dt>semicolon</dt>

<dd>one word</dd>

<dt>standalone, stand-alone</dt>

<dd>one word preferred, both allowed</dd>

<dt>stylesheet, style sheet</dt>

<dd>two words preferred, both allowed</dd>

<dt>subset</dt>

<dd>no hyphen</dd>

<dt>superset</dt>

<dd>no hyphen</dd>

<dt>uppercase</dt>

<dd>one word</dd>

<dt><abbr title="Uniform Resource Identifier">URI</abbr> reference</dt>

<dd>usually not <abbr title="Uniform Resource Identifier">URI</abbr>
Reference or <abbr title=
"Uniform Resource Identifier">URI</abbr>-Reference</dd>

<dt><abbr title="Uniform Resource Identifiers">URIs</abbr></dt>

<dd>no apostrophe (see [<cite><a href=
"#ref-PLURAL">PLURAL</a></cite>])</dd>

<dt>user agent</dt>

<dd>lowercase</dd>

<dt>user interface</dt>

<dd>lowercase</dd>

<dt>web (on its own)</dt>

<dd>lowercase</dd>

<dt>Web (as part of a phrase)

<dd>always capitalize in "World Wide Web", "World Wide Web Consortium", "Web Consortium"</dd>

<dt>Webmaster, webmaster</dt>

<dd>one word, either capitalize or lowercase</dd>

<dt>webpage, web page</dt>

<dd>both allowed, lowercase "web"</dd>

<dt>website, web site</dt>

<dd>one word preferred, both allowed. lowercase "web"</dd>

<dt>well-formed</dt>

<dd>hyphenate</dd>

<dt>white space</dt>

<dd>two words</dd>

<dt>worldwide</dt>

<dd>one word</dd>

<dt>World Wide Web</dt>

<dd>three words, no hyphen</dd>

<dt>W3C, the World Wide Web Consortium, the Web Consortium</dt>
<dd>refer to us as "the World Wide Web Consortium", "the Web Consortium", or "W3C" but not "the W3C"</dd>
<dd>when using the acronym, treat it as a proper noun and use "W3C" but not "the W3C" unless it's used as an adjective, <span class="not-en">e.g.</span>, "The W3C Team is small but mighty"</dd>

<dt>W3C Note</dt>

<dd>not W3C NOTE</dd>
</dl>
</section>
<section id="ACK">
  <h2>Acknowledgments</h2>

<p>Thank you to Karl Dubost (until December 2009 while at W3C). Thank you to Philip Gallo and to Paul Harmon and to E.K. for artwork used in earlier
versions. The following people contributed to this compilation:</p>

<ul>
<li>All affiliated with W3C at the time, Dan Connolly, Ian Jacobs,
Joseph Reagle, Tim Berners-Lee, Philippe Le Hégaret, Karen MacArthur, Coralie Mercier and Håkon Wium Lie
wrote the majority of this guide in various incarnations since it
started in 1995.</li>

<li><!-- alphabetized by Romanized family name -->
Judy Brewer (until January 2023 while at W3C), 
David Carlisle,
Mark Davis, 
Martin Dürst (until April 2005 while at W3C), 
Max Froumentin (until February 2007 while at W3C), 
Hugo Haas (until May 2006 while at W3C), 
Dominique Hazaël-Massieux (W3C),
Björn Höhrmann, 
Bob Hopgood (Oxford Brookes University), 
Paul Grosso (Arbortext), 
Daniel Dardailler (until December 2018 while at W3C), 
Richard Ishida (W3C), 
Charles McCathieNevile (until January 2005 while at W3C), 
Steven Pemberton (until June 2011 while at W3C), 
Addison Phillips (Invited Expert),
Stuart Williams (Hewlett-Packard), 
and François Yergeau (Alis Technologies)
all contributed valuable comments.</li>
</ul>
</section>
<section id="REF">
  <h2>References</h2>

<dl class="ref">

<dt id="ref-BIB-EXTRACT">[BIB-EXTRACT]</dt>

<dd><a href="https://www.w3.org/2002/01/tr-automation/tr-biblio-ui">W3C
Bibliography Extractor</a>, Dominique Hazaël-Massieux, 2003. This tool
is online at
https://www.w3.org/2002/01/tr-automation/tr-biblio-ui.</dd>

<!--
<dt id="ref-CHARMOD">[CHARMOD]</dt>

<dd><cite><a href=
"http://www.w3.org/TR/2004/WD-charmod-20040225/">Character Model for
the World Wide Web 1.0: Fundamentals</a></cite>, M. Dürst, F. Yergeau,
R. Ishida, M. Wolf, and T. Texin, Editors. W3C work in progress, 2004.
This version of the Character Model Fundamentals is
https://www.w3.org/TR/2004/WD-charmod-20040225/. The <a href=
"https://www.w3.org/TR/charmod/">latest version of the Character Model
Fundamentals</a> is available at https://www.w3.org/TR/charmod.</dd>
-->

<dt id="ref-CHARNAMES">[CHARNAMES]</dt>

<dd><a href=
"https://lists.w3.org/Archives/Public/www-international/2001JulSep/0133.html">
Unicode character names</a>, M. Davis, M. Dürst, et al., 25-27 August
2001. This email thread is online at
https://lists.w3.org/Archives/Public/www-international/2001JulSep/thread.html#133.</dd>

<dt id="ref-CHARTS">[CHARTS]</dt>

<dd><a href="http://www.unicode.org/charts/About.html">About the Online
Code Charts</a>, <cite>The Unicode Standard</cite>, Version 1.1 or
later. The Unicode Consortium, 2001. Unicode code charts are online at
http://www.unicode.org/charts/About.html.</dd>

<dt id="ref-CHECKLINK">[CHECKLINK]</dt>

<dd><a href="https://validator.w3.org/checklink">W3C Link Checker</a>,
W3C. This service is online at
https://validator.w3.org/checklink.</dd>

<dt id="ref-CLICK-HERE">[CLICK-HERE]</dt>

<dd><a href="https://www.w3.org/QA/Tips/noClickHere">Don't use "click
here" as link text</a>, Aaron Swartz. W3C Quality Assurance Activity, 2001. This QA tip is
online at https://www.w3.org/QA/Tips/noClickHere.</dd>

<dt id="ref-CSSVALIDATE">[CSSVALIDATE]</dt>

<dd><a href="https://jigsaw.w3.org/css-validator/">W3C CSS Validation
Service</a>, W3C. This service is online at
https://jigsaw.w3.org/css-validator.</dd>

<dt id="ref-DOMAINS">[DOMAINS]</dt>

<dd><cite><a href="https://www.ietf.org/rfc/rfc2606.txt">Reserved Top
Level DNS Names</a></cite>, D. Eastlake, and A. Panitz. The Internet
Society, June 1999. This <abbr title="Request for Comments">RFC</abbr>
is available at https://www.ietf.org/rfc/rfc2606.txt.</dd>

<dt id="ref-EDITORS">[EDITORS]</dt>

<dd><a href="https://www.w3.org/guide/editor/">W3C Editors Home
Page</a>, 2024. This list of resources for editors is online at
https://www.w3.org/guide/editor/.</dd>

<dt id="ref-GRM">[GRM]</dt>

<dd><a href="http://www.glencoe.com/ps/grm/faqs/">Frequently Asked
Questions</a>, <cite>The Gregg Reference Manual Instructor Site</cite>,
Glencoe/McGraw-Hill, 2000. This FAQ is online at
http://www.glencoe.com/ps/grm/faqs.</dd>

<dt id="ref-IPRFAQ">[IPRFAQ]</dt>

<dd><a href=
"https://www.w3.org/copyright/intellectual-rights/">Intellectual
Property FAQ</a>, W3C, 2024. The latest version of this
document is https://www.w3.org/copyright/intellectual-rights/.</dd>

<dt id="ref-KEYWORDS">[KEYWORDS]</dt>

<dd><cite><a href="https://www.ietf.org/rfc/rfc2119.txt">Key words for
use in RFCs to Indicate Requirement Levels</a></cite>, S. Bradner. The
Internet Society, March 1997. This <abbr title=
"Request for Comments">RFC</abbr> is available at
https://www.ietf.org/rfc/rfc2119.txt.</dd>

<dt id="ref-M-W">[M-W]</dt>

<dd><cite><a href="https://www.merriam-webster.com/">Merriam-Webster OnLine:
Collegiate Dictionary</a></cite>, 10th Edition. Merriam-Webster,
Incorporated, 2000. This book is online at https://www.merriam-webster.com/.</dd>

<dt id="ref-MANAGE">[MANAGE]</dt>

<dd><cite><a href="https://www.w3.org/MarkUp/SGML/spec-mgmt">Document
Management for Web Specs</a></cite>, D. Connolly. W3C, 1995-1999. This
guide is online at http://www.w3.org/MarkUp/SGML/spec-mgmt.</dd>

<dt id="ref-PERSISTENCE">[PERSISTENCE]</dt>

<dd><cite><a href=
"https://www.w3.org/policies/uri-persistence/">Persistence
Policy</a></cite>, T. Berners-Lee, 1999. This policy is online at
https://www.w3.org/policies/uri-persistence/.</dd>

<dt id="ref-PLURAL">[PLURAL]</dt>

<dd><a href=
"http://xml.coverpages.org/properSpellingForPluralOfDTD.html">Infrequently
Asked Questions Concerning the Proper Spelling of 'DTD' in its Plural
Form</a>, R. Cover, updated 4 January 2001 or later. This document is
online at
http://xml.coverpages.org/properSpellingForPluralOfDTD.html.</dd>

<dt id="ref-PROCESS">[PROCESS]</dt>

<dd><cite><a href="https://www.w3.org/policies/process/20231103/">World
Wide Web Consortium Process Document</a></cite>, Elika J. Etemad / fantasai,
Florian Rivoal, Editors.
W3C, 3 November 2023. The latest version of this document is
https://www.w3.org/policies/process/.</dd>

<dt id="ref-PRONOUNS">[PRONOUNS]</dt>

<dd><a href=
"https://lists.w3.org/Archives/Public/www-international/2000AprJun/0058">
Personal pronouns in specifications</a>, M. Dürst, 13 May 2000. This
email message is online at
https://lists.w3.org/Archives/Public/www-international/2000AprJun/0058.</dd>

<dt id="ref-PUBRULES">[PUBRULES]</dt>

<dd><cite><a href="https://www.w3.org/pubrules/doc">Technical Report
Publication Policy</a></cite>, the W3C Team. W3C,
2000-2025. This document is online at
https://www.w3.org/pubrules/doc.</dd>

<dt id="ref-REF-TITLES">[REF-TITLES]</dt>

<dd><a href=
"https://lists.w3.org/Archives/Public/www-html-editor/2000JanMar/0103">please
use titles, not addresses, as link text</a>, D. Connolly, 10 February
2000. This email message is online at
https://lists.w3.org/Archives/Public/www-html-editor/2000JanMar/0103.</dd>

<dt id="ref-REGISTER-1">[REGISTER-1]</dt>

<dd><a href=
"https://www.w3.org/guide/editor/mediatypes">Register an Internet Media Type for a W3C Specification</a>, Philippe Le Hégaret, 2019. This Web page is online at
"https://www.w3.org/guide/editor/mediatypes.</dd>

<dt id="ref-REGISTER-2">[REGISTER-2]</dt>

<dd><a href=
"https://lists.w3.org/Archives/Public/www-tag/2006Aug/0012">TAG Position on Use of Unregistered Media Types in W3C Recommendations</a>, N. Mendelsohn, 4 August 2006. This email message is online at
https://lists.w3.org/Archives/Public/www-tag/2006Aug/0012.</dd>

<dt id="ref-SPEC-PROD">[SPEC-PROD]</dt>

<dd>spec-prod@w3.org. W3C, 1998-2001. <a href=
"https://lists.w3.org/Archives/Public/">Subscribe</a> to this public mailing
list at https://lists.w3.org/Archives/Public/ and view its <a href=
"https://lists.w3.org/Archives/Public/spec-prod/">archive</a> at
https://lists.w3.org/Archives/Public/spec-prod/.</dd>

<dt id="ref-STYLE-GUIDE">[STYLE-GUIDE]</dt>

<dd><cite><a href="https://www.w3.org/Provider/Style/">Style Guide for
Online Hypertext</a></cite>, T. Berners-Lee. 1992-1998. This guide is
online at https://www.w3.org/Provider/Style.</dd>

<dt id="ref-TR">[TR]</dt>

<dd><a href="https://www.w3.org/TR/">W3C standards and drafts</a>, W3C, 1995-2024. This web page is online at
https://www.w3.org/TR.</dd>

<dt id="ref-TRANSLATE">[TRANSLATE]</dt>

<dd><a href="https://www.w3.org/Consortium/Translation/">Translations at
W3C</a>, W3C, 1997-2003. This Web page is online at
https://www.w3.org/Consortium/Translation.</dd>

<!--
<dt id="ref-UNICODE">[UNICODE]</dt>

<dd><a href=
"http://www.unicode.org/unicode/standard/versions/">Citations and
References</a>, The Unicode Consortium, 2001. These instructions for
citing Unicode are online at
http://www.unicode.org/unicode/standard/versions/.</dd>
-->

<dt id="ref-VALIDATE">[VALIDATE]</dt>

<dd><a href="https://validator.w3.org/">W3C Markup Validation
Service</a>, 1994-2013. This service is online at
https://validator.w3.org.</dd>

</dl>
</section>
<section id="External">
  <h3>External Links</h3>

<p>The prose links to the following references as illustrations. They
are informative, listed here for print use.</p>

<dl>
<dt id="ref-CSS3UI">[CSS3UI]</dt>

<dd><cite><a href=
"https://www.w3.org/TR/css-ui-3/#outline">CSS Basic User Interface Module Level 3 (CSS3 UI) section 4.1</a></cite>, Tantek Çelik,
Florian Rivoal, Editors. W3C, 2018. This example is online at
https://www.w3.org/TR/css-ui-3/#outline.</dd>

<dt id="ref-EXCAL">[EXCAL]</dt>

<dd><a href=
"http://www.eg.bucknell.edu/~excalibr/excalibur.html">Excalibur</a>, R.
Zaccone, 2001. The Excalibur home page is
http://www.eg.bucknell.edu/~excalibr/excalibur.html.</dd>

<dt id="ref-HTML">[HTML]</dt>

<dd><cite><a href="https://www.w3.org/TR/2016/REC-html51-20161101/">HTML 5.1</a></cite>.
Steve Faulkner, et al., Editors, W3C, 2016. The <a href="https://www.w3.org/TR/html/">latest version of the HTML</a> is available at https://www.w3.org/TR/html/.</dd>

<dt id="ref-ISPELL">[ISPELL]</dt>

<dd><a href=
"https://www.cs.hmc.edu/~geoff/ispell.html">International
Ispell</a>, G. Kuenning et al. 1971-2001. The Ispell home page is
https://www.cs.hmc.edu/~geoff/ispell.html.</dd>

<dt id="ref-SCHEMA-DATATYPES">[SCHEMA-DATATYPES]</dt>

<dd><cite><a href=
"https://www.w3.org/TR/2001/REC-xmlschema-2-20010502/#date">XML Schema
Part 2: Datatypes sections 3.2.9 through 3.2.14.1</a></cite>, P. V.
Biron, and A. Malhotra, Editors. W3C, 2001. The <a href=
"https://www.w3.org/TR/xmlschema-2/">latest version of XML Schema:
Datatypes</a> is available at https://www.w3.org/TR/xmlschema-2.</dd>


<dt id="ref-XML">[XML]</dt>

<dd><cite><a href=
"https://www.w3.org/TR/2006/REC-xml-20060816/#sec-comments">Extensible
Markup Language (XML) 1.0 (Fourth Edition) section 2.5</a></cite>, , T. Bray, J. Paoli, E. Maler, C. M. Sperberg-McQueen, F. Yergeau, Editors. W3C,
2006. This example is online at
https://www.w3.org/TR/2006/REC-xml-20060816/#sec-comments.</dd>

<dt id="ref-XML1">[XML1]</dt>

<dd><cite><a href="https://www.w3.org/TR/2006/REC-xml-20060816/">Extensible Markup Language (XML) 1.0 (Fourth Edition)</a></cite>, T. Bray, J. Paoli, E. Maler, C. M. Sperberg-McQueen, F. Yergeau, Editors. World Wide Web Consortium, 16 August 2006, edited in place 29 September 2006. This edition of the XML 1.0 Recommendation is http://www.w3.org/TR/2006/REC-xml-20060816/. The <a href="https://www.w3.org/TR/xml/">latest edition of XML 1.0</a> is available at http://www.w3.org/TR/xml/.</dd>
</dl>
</section>

<script>
// get list of bad terms
fetch("https://www.w3.org/pubrules/badterms.json").then(res => res.json()).then(terms => {
  let tbody = document.querySelector("#neutrallanguage > tbody")
  terms.forEach(t => {
    let row = document.createElement('tr');
    let termCell = document.createElement('td');
    termCell.innerText = t.term.join('/');
    let altCell = document.createElement('td');
    altCell.innerText = t.alternatives.join('/');
    row.appendChild(termCell);
    row.appendChild(altCell);
    tbody.appendChild(row);
  });
});
</script>
</body>
</html>