W3C Manual of Style (original) (raw)

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 W3C Publication Rules.

Introduction

Written for editors and authors of W3C technical reports, this document assumes that the reader has mastered publishing on the W3C Web site, and is familiar with the Style Guide for Online Hypertext [STYLE-GUIDE]. It is a companion to the REQUIRED Technical Report Publication Policy [PUBRULES], called "pubrules" for short. Following the advice in this manual has benefits:

• Non-native English readers, native English readers, and translators will find your text easy to read and implement.
• All audiences can concentrate on ideas rather than the mechanics of reading.
• Polished at early public maturity levels, clean copy eliminates multiple "typo" reports.

Chapter 2 covers validation. Chapters 3 and 4 cover accessibility and internationalization. Chapter 5 describes parts of a W3C technical report. Chapters 6, 7, and 8 cover errata, references and revisions. Chapter 9 introduces editing tools. Chapter 10 addresses Normative and Informative requirements, in particular RFC 2119 key words. Chapter 11 presents editorial guidelines, and, finally, chapter 12 documents commonly misspelled terms.

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 Persistence Policy [PERSISTENCE].

Validation

• 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 W3C Link Checker [CHECKLINK]. Append ",checklink" to a W3CURI to invoke the link checker.
• Make sure your technical report validates in the W3C Markup Validation Service [VALIDATE]. Append ",validate" to a W3CURI to invoke the validator.
• Make sure your technical report validates in the W3CCSS Validation Service [CSSVALIDATE]. Append ",cssvalidate" to a W3C URI to invoke theCSS validator.
• Make sure any examples in your document validate as well.

Note. It is the editor's responsibility to ensure that documents are valid before requesting publication.

Accessibility

• Follow the Web Content Accessibility Guidelines(WCAG). Can simpler words express your ideas? Is your text marked up with structural elements? Are alternatives provided for auditory and visual content? See also evaluation tools.

Internationalization

Follow the guidelines in Internationalization Best Practices for Spec Developers [[INTERNATIONAL-SPECS]] when producing your specification. You might also find it helpful to complete a self-review 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.

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]].

Write for a global audience

Keep in mind that W3C documents serve a global audience.

• Avoid idioms that are U.S.- or English-specific in favor of more neutral language.
• Choose examples that reflect a global audience. For example:
  • When creating user stories or other examples that feature people, choose example names that come from different cultures and regions. You can find suggestions here in [[INTERNATIONAL-SPECS]].
  • 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".
• In general, use [=locale-neutral=] representations of data values, such as dates, numbers, currency values, and so forth.
• For time and date values, choose an unambiguous representation:
  • For date values that appear in prose, spell out the month (for example, 6 May 2003 or September 23, 2016). All numeric dates such as 5/6/03 or 6/5/03 are ambiguous. Some cultures will read the first example as "June 5" while other cultures will read the second example as that date.
  • For date values that appear in data, use a format derived from ISO8601, such as those found in [[RFC3339]] or those found in XML Schema Part 2: Datatypes ([[XMLSchema-2]].

Unicode

Use U+XXXX 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.

Use the Unicode character name to describe specific code points. Use of the character naming template is recommended.

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 U+XXXX notation) will help make your specification unambiguous.

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

Character naming template

Internationalization specifications use (and we recommend the use of) this template for character references:

&#xXXXX; [U+XXXX Unicode_character_name]

Some notes about the markup used. The bdi element is used to ensure that example characters that are [=right-to-left=] do not interfere with the layout of the page. The lang 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.

Translations

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.

• A central translation page includes links to pages that document translations of particular specifications [TRANSLATE].
• Read the W3C Intellectual Property FAQ, Can I translate one of your specifications into another language?and Can I create the "official" translation? ([IPRFAQ] sections 5.6 and 5.7).

Make your specification more readable by adding markup to distinguish common words from keywords in your language. Mark up every occurrence. Use translate="no" 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:

The title attribute of these elements may be used to provide the full or expanded form of the expression.

becomes:

The title attribute of these elements may be used to provide the full or expanded form of the expression.

A French translator would then know not to translate _title_to titre.

Do not invent elements to replace natural language. For example, do not use <must/> and a stylesheet to render MUST. Other languages may need grammatical agreement with the sentence's subject, e.g., in French, MUST will become_DOIT_ if the subject is singular, or_DOIVENT_ if it is plural. Use standard markup instead.

The Parts of a Technical Report

As of November 2005, pubrules [PUBRULES] includes a technical report template.

Document Title

The title of your document in the document head and on the technical reports index [TR] will read as follows. Optional elements are in square brackets.

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

See pubrules [PUBRULES] for information about the use of "version" and "edition". "Level" and "revised" are deprecated. Try not to invent a new titling convention.

Capitalize title words following U.S. usage.

Editors and Authors

Managing Changing Affiliations

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

Still editor

Richard Ishida, W3C (and before at Xerox)

François Yergeau, Invited Expert (and before at Alis Technologies)

Jane Doe, MyCompany (and before at ThierCompany, and at HisCompany, and at HerCompany)

No longer editor

Martin J. Dürst (until Dec 2004 while at W3C)

Misha Wolf (until Dec 2002 while at Reuters Ltd.)

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

FitzChivalry Farseer (until Oct 2005 while at AnyCompany, and before at ThisCompany, and at ThatCompany)

Abstract

Give each document an Abstract (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.

Status Section

The "Status of This Document" section describes the document status and publication context on the publication date. Pubrules [PUBRULES] states the requirements for the status section of each type of technical report (e.g., use of customized and boilerplate text).

Since the status section does not change over time, express it in terms that will be valid over time (e.g., 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 (e.g., by following the latest version link, or visiting the W3C technical reports index [TR].

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.

TimBL 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 th case for why someone should read this draft.

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

• Are we requesting that people implement this specification? If so, where should experience reports be sent?
• Are we requesting people do not 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?
• Does it reflect the consensus of a W3C Working Group? (Pay attention to the authors and acknowledgments.)
• Are there any changes expected?
• Do we maintain a page of background information?
• For pre-release drafts, state in the status section any limits on redistribution, such as "Member confidential."

Errata

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 pageoutside of the /TR hierarchy. There is an expectation that documents in the "TR zone" will not evolve over time [PERSISTENCE]. For example, locate errata pages in the portion of the Web space dedicated to the relevant Working Group or Activity.

Clearly indicate on the errata page:

• The last modified date for the errata page.
• The URI of the source document (i.e., the one with the errata).
• Where to find the latest version of the source document.

For example (shown here without links):

This document:

http://www.w3.org/Style/css2-updates/REC-CSS2-19980512-errata

Last revised: Date:2016/07/1016:55:10Date: 2016/07/10 16:55:10 Date:2016/07/1016:55:10

This document records known errors in the document:

http://www.w3.org/TR/1998/REC-CSS2-19980512

The latest version of the CSS 2 Recommendation:

http://www.w3.org/TR/REC-CSS2

On the errata page, list the newest entries nearer to the top.

Entries on an errata page

For each entry on the errata page, provide:

1. A unique identifier
2. The date it was added to the errata page
3. A classification of the error (e.g., editorial, clarification, bug, known problem with the document itself)
4. A short description of the problem and what part of the Recommendation is affected.
5. Any proposed corrections and whether those corrections would affect conformance of documents or software
6. Any normative corrections; see the section on Errata Management in the W3C Process Document([PROCESS] section 6.2.4) for more information about normative corrections

Do no remove entries from the errata page; if a correction turns out to be incorrect, just add another entry (with a cross reference).

References

Citation

Reference links (e.g., "[XML]") link at least the first mention of a source to the References section and take the form:

Full Name [REFNAME]

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

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, e.g.:

This is discussed in Namespaces in XML [XMLName].

or

This is discussed in the XML namespaces specification [XMLName].

and not

This is discussed in [XMLName].

Citing a Reference From Within a Document

When linking from the middle of the document to an external resource:

1. Ensure that the link text, title, and context indicate you are leaving the document, and
2. 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 (e.g., when printed).

Thus, for example:

...as is done for the 'outline' property of CSS Basic User Interface Module Level 3 ([CSS3UI], section 4.1).

References Section

• 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.
• 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."
• It is helpful to include references to both persistent resources and their latest version. Use titles for links. If there is an institutionalized identifier (URI) for a document, cite the most specific identifier. For example, usually you would link the title tohttp://www.w3.org/TR/1999/REC-html401-19991224 rather than to http://www.w3.org/TR/html4/. For more information on using versioned and unversioned identifiers, refer to theCharacter Model for the World Wide Web 1.0: Fundamentals([[CHARMOD]] section 8).
• An entry in a references section takes this form:
  • Title, inside a (if available), insidecite
  • Comma-delimited list of authors' names
  • If there are no authors, use editors instead if available. Following the last family name, say "eds." or "Editors."
  • Publisher, followed by the date of publication in the form DD Month YYYY
  • A sentence containing a text-only URI.
  • When available, a sentence ending in the latest versionURI
    Example:
    [XML1]
    Extensible Markup Language (XML) 1.0 (Fourth Edition), 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 latest edition of XML 1.0 is available at http://www.w3.org/TR/xml/.
    Markup for the example above:

    [XML1]

    Extensible Markup Language (XML) 1.0 (Fourth Edition), 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 latest edition of XML 1.0 is available at http://www.w3.org/TR/xml/.

• Reference titles are recommended, not the "URI-in-your-face" idiom, as link text; see [REF-TITLES]. For example, Do use: HTML 5.1 Specification. Do not use:http://www.w3.org/TR/1999/REC-html401-19991224.

Normative and Informative References

See Normative References and considerations by the Team.

Revisions

See the W3C Process Document ([PROCESS] section 6.3.11) for instructions on modifying a W3C Recommendation.

Note. When a document is revised, the original publication date remains the same (and on the technical reports index [TR] as well); see pubrules [PUBRULES] for more detail.

Be careful not to break links in revisions. If your document uses latest version URIs with a fragment identifier, unless those anchors are maintained across versions, links will break.

Editing tools

Though the HTML orXHTML version of your specification is always the definitive one, many editors find the use of a tool easier to work with.

The most popular editing tools are Bikeshed and respec.

For help with this process, you can ask the experts on the public mailing list spec-prod@w3.org [SPEC-PROD].

Normative material

Normative & Informative sections

It is important that informative (non-normative) material is clearly distinguished from normative material. To this end:

• If the entire document is informative, say so at the top and do not reference RFC 2119 or use RFC 2119 keywords
• If some sections are informative, say so at the start of each section, and do not use RFC 2119 keywords in those sections
• Figures, examples and notes are assumed to always be informative. To avoid repetition, each figure, example or note does not say this.Thus, to avoid breaking user expectations, document editors MUST NOT make any figure, example or note normative.

RFC 2119 Key Words

Adhere to and credit RFC 2119 Key words for use inRFCs to Indicate Requirement Levels [KEYWORDS] (e.g., "MUST", "MUST NOT", "REQUIRED").

When these key words are used in the RFC sense, make them UPPERCASE, enclose them in the em element, and style them with CSS class of rfc2119 to make the UPPERCASE readable.

MUST

.rfc2119 { font-style: normal; font-size: 0.875em; }

The author may explain why if these key words are not used in theRFC sense.

Where they are not required for interoperation or to limit behavior which has potential for causing harm these key words must not be used to try to impose a particular method on implementors where the method is not required for interoperability.

Editorial Guidelines

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

Grammar

• Delete repeated words.
• Check subject-verb agreement.
• Break long sentences.
• Eliminate contractions (e.g., "don't" should read "do not")?

Spelling

• Spell-check using a U.S. English dictionary. Append ",spell" to a W3C URI to invoke W3C's spell checker.
• Free dictionaries are also available on the Ispell home page [ISPELL] for UNIX and the Excalibur home page [EXCAL] for Mac OS.
• W3C uses Merriam-Webster's Collegiate® Dictionary, 10th Edition [M-W], on the Web as the spelling arbiter because it is free, on-line, and available to every technical report author and editor. If a word does not appear there, use theAmerican Heritage® Dictionary, 4th Edition [AH]. Other dictionaries are used as needed (for example, Random House and Webster's unabridged, Oxford and Oxford Concise).
• W3C uses U.S. English (e.g., "standardise" should read "standardize" and "behaviour" should read "behavior").
• Form the plural of abbreviations, initialisms and acronyms without an apostrophe (e.g., the plural ofURI is URIs not URI's). See the FAQ"Infrequently Asked Questions Concerning the Proper Spelling of 'DTD' in its Plural Form" [PLURAL].

Punctuation

• Use correct punctuation. A hard copy of The Chicago Manual of Style or The Gregg Reference Manual may be of some help.
• Remember you are typing HTML or XML not TeX. Use quotation marks rather than grave accents and apostrophes to quote text (e.g., ``value'' should read "value").

Case, Combining Words, and Hyphenation

• Capitalize W3C entities to match the W3C Process Document [PROCESS] (e.g., Working Group, Recommendation).
• Make the case, number of words, and hyphenation in terms matchchapter 12.

Miscellaneous

• Spell out acronyms and initialisms in their first occurrence in prose, for example, "Internet Engineering Task Force (IETF)" or "Internationalization (I18N)." In subsequent occurrences when they are not spelled out, useabbr elements, and give themtitle attributes.
• Check references (most commonly, for no full stop after theet in et al.). Do the entries match?

Linking

• Unless intentionally referring to the latest document in a series, always refer to specific W3C documents by using the "this version"URI.
• If you are referring to a W3C document using either its this version or latest version URI, note whether the URI ends in a slash or not. These identifiers do not end in an extension such as ".html". Include the extension when intentionally referring to a specific version (e.g., a GIF image where GIF and PNG are both available through content negotiation).
• Visible URIs andhref attributes should have the same value.

Using Examples

• Domains in examples adhere to section 3, "Reserved Example Second Level Domain Names," in RFC 2606 [DOMAINS]. Use the domainsexample.com, example.org, andexample.net 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 (e.g., http://cats.example.org).
• When not addressed by second level example domains, top level domains (TLDs) adhere to section 2, "TLDs for Testing, & Documentation Examples," inRFC 2606[DOMAINS]. Use.test, .example, .invalid or.localhost.
• Remember to validate markup in examples. Escaped characters pass through routine validation.
• 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).
• Use CSS withdiv elements to mark up examples, as is done in theHTML 5.1([HTML], section 4.2):

Images

• We recommend that each image be available as PNG, even if you use content negotiation to serve alternative formats.
• Give images a background color (e.g., white) so your technical report can be read with any style sheet (e.g., with W3C's dark on light style sheets, or a user style sheet that specifies a dark background).
• Match image size to markup width andheight (or images will be distorted).
• See the Web Content Accessibility Guidelines Techniques for information about providing alternative text (alt) and long descriptions (longdesc) for images. Also, don't forget to spell-check your alternative text.

Markup

• Use markup as it is intended. The blockquote andul and li elements were designed for quotations and lists and not for indentation. Use CSS instead.
• Remove extraneous non-breaking spaces.
• Mark up attributes and elements consistently.
• Make sure there are no font or basefontelements in your document.
• Make sure all table elements in your document are real data tables, not tables used for layout.
• Make sure there are no bgcolor,background, color, face,marginheight, marginwidth orsize attributes.
• Give each page lang="en-US" on the htmlelement for HTML, orxml:lang="en-US" lang="en-US" on the htmlelement for XHTML syntax.
• Use the span element and lang andxml:lang attributes for language changes within a page.
• Make semantic distinctions using more than only color, for example, a font-style change, so that color-blind individuals can see a difference.
• Links with the anchor text "Click here" provide no context. The visitor may become lost not knowing where "here" is. See alsoDon't use "click here" as link text [CLICK-HERE].
• Mark up data table headers with th not by bolding a td.

Large Documents

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

• Divide the document logically, storing chapters in separate files.
• Offer a single-page, printable, searchable version of the specification. This format may be compressed if large.
• 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.

Inclusive terminology

Following the W3C Code of Conduct,W3C 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 W3C community.

Here are proposed alternatives for some terms that PubRules (see list of terms in JSON) shows a warning about:

Internet Media Types

• For information about defining a new Internet media type (formerly known as MIME type) in your specification, see How to Register an Internet Media Type for a W3C Specification [REGISTER-1].
• For information about referring to existing Internet media types (registered or not), see the email message TAG Position on Use of Unregistered Media Types in W3C Recommendations [REGISTER-2].

Commonly Misspelled Terms

W3C has reviewed its technical reports one by one since November 1999, for typographical errors. The following words appear often in those reviews and are easy to misspell.

anti-alias

hyphenate

ASCII

all caps

base64

lowercase, one word

Bézier

always capitalize, and accent the first e

braille

capitalize only when talking about Louis Braille

built-in

hyphenate when used as an adjective or noun, not when built is a verb

color space

two words

DTDs

no apostrophe (see [PLURAL])

dingbat

one word

ECMAScript

one word, cap S

et al.

no full stop after "et"

full stop (.)

Full stop is the formal name.Dot and period are good aliases.

hash (#)

also number sign, usually not pound sign, crosshatch or octothorpe

heading

Term for h1-h6. Tables and HTTP have headers.

HTTP/1.0

needs slash when referred to as a protocol, none in free text

HTTP/1.1

needs slash when referred to as a protocol, none in free text

home page

two words

Java

cap J

JavaScript

cap S

Level 1, 2, 3

cap L when referring to a W3C technical report

line feed

two words

lowercase

one word

markup

one word

MIME type

now Internet media type (MIME type is two words. MIME is all caps.)

namespace

lowercase unless referring to the Namespaces in XMLspecification by name

number sign (#)

also hash, usually not pound sign, crosshatch or octothorpe

on-line

hyphenate

PDF

all caps

PostScript

cap S

read-only

hyphenate

Real-Time Communication, real-time communication, real-time communications, RTC

In titles and headings, capitalize all words = Real-Time Communication

For the generic idea in sentences, lowercase = real-time communication or real-time communications — including with the acronym = real-time communications (RTC)

ruby

lowercase for the typographic convention. Uppercase for the programming language.

schema

lowercase

schemas

preferred to schemata

semicolon

one word

stand-alone

hyphenate

style sheet

two words

subset

no hyphen

superset

no hyphen

uppercase

one word

URI reference

usually not URIReference or URI-Reference

URIs

no apostrophe (see [PLURAL])

user agent

lowercase

user interface

lowercase

Web (on its own)

always capitalize

Web (as part of a phrase)

Either capitalize or lower case "Web" (e.g., Web developer or web developer, Web project or web project, Web page or web page, Web application or web application

Webmaster, webmaster

one word, either capitalize or lower case

Web page, web page

two words, either capitalize or lower case "Web"

Web site, web site, website

two words (capitalize or lower case "Web") or one (lower case)

well-formed

hyphenate

white space

two words

worldwide

one word

World Wide Web

three words, no hyphen

W3C Note

not W3C NOTE

Acknowledgments

Thank you to Karl Dubost (W3C). Thank you to Philip Gallo for the pencil image and to Paul Harmon and to E.K. for artwork used in earlier versions. The following people contributed to this compilation:

• All affiliated with W3C at the time, Dan Connolly, Ian Jacobs, Joseph Reagle, Tim Berners-Lee, Karen MacArthur, and Håkon Wium Lie wrote the majority of this guide in various incarnations since it started in 1995.
• Judy Brewer (W3C), David Carlisle, Mark Davis, Martin Dürst (W3C), Max Froumentin (W3C), Hugo Haas (W3C), Dominique Hazaël-Massieux (W3C), Björn Höhrmann, Bob Hopgood (Oxford Brookes University), Paul Grosso (Arbortext), Daniel Dardailler (W3C), Richard Ishida (W3C), Charles McCathieNevile (W3C), Steven Pemberton (W3C), Addison Phillips (Invited Expert), Stuart Williams (Hewlett-Packard), and François Yergeau (Alis Technologies) all contributed valuable comments.

References

[AH]

American Heritage® Dictionary, 4th Edition. Houghton Mifflin Company, 2000. This book is on-line at http://www.bartleby.com/61.

W3C Bibliography Extractor, Dominique Hazaël-Massieux, 2003. This tool is on-line at https://www.w3.org/2002/01/tr-automation/tr-biblio-ui.

[CHARNAMES]

Unicode character names, M. Davis, M. Dürst, et al., 25-27 August 2001. This email thread is on-line at https://lists.w3.org/Archives/Public/www-international/2001JulSep/thread.html#133.

[CHARTS]

About the Online Code Charts, The Unicode Standard, Version 1.1 or later. The Unicode Consortium, 2001. Unicode code charts are on-line at http://www.unicode.org/charts/About.html.

[CHECKLINK]

W3C Link Checker, W3C QA Activity, 1999-2011. This service is on-line at https://validator.w3.org/checklink.

[CLICK-HERE]

Don't use "click here" as link text, Aaron Swartz. W3C QA Team, 2001. This QA tip is on-line at https://www.w3.org/QA/Tips/noClickHere.

[CSSVALIDATE]

W3C CSS Validation Service, W3C QA Activity, 1997-2004. This service is on-line at https://jigsaw.w3.org/css-validator.

[DOMAINS]

Reserved Top Level DNS Names, D. Eastlake, and A. Panitz. The Internet Society, June 1999. This RFCis available at https://www.ietf.org/rfc/rfc2606.txt.

[EDITORS]

W3C Editors Home Page, 2024. This list of resources for editors is on-line at https://www.w3.org/Guide/editor/.

[GRM]

Frequently Asked Questions, The Gregg Reference Manual Instructor Site, Glencoe/McGraw-Hill, 2000. This FAQ is on-line at http://www.glencoe.com/ps/grm/faqs.

[IPRFAQ]

Intellectual Property FAQ, W3C, 2024. The latest version of this document is https://www.w3.org/copyright/intellectual-rights/.

[KEYWORDS]

Key words for use in RFCs to Indicate Requirement Levels, S. Bradner. The Internet Society, March 1997. This RFC is available at https://www.ietf.org/rfc/rfc2119.txt.

[M-W]

Merriam-Webster OnLine: Collegiate Dictionary, 10th Edition. Merriam-Webster, Incorporated, 2000. This book is on-line at http://www.m-w.com.

[MANAGE]

Document Management for Web Specs, D. Connolly. W3C, 1995-1999. This guide is on-line at http://www.w3.org/MarkUp/SGML/spec-mgmt.

[PERSISTENCE]

Persistence Policy, T. Berners-Lee, 1999. This policy is on-line at https://www.w3.org/policies/uri-persistence/.

[PLURAL]

Infrequently Asked Questions Concerning the Proper Spelling of 'DTD' in its Plural Form, R. Cover, updated 4 January 2001 or later. This document is on-line at http://xml.coverpages.org/properSpellingForPluralOfDTD.html.

[PROCESS]

World Wide Web Consortium Process Document, Elika J. Etemad / fantasai, Florian Rivoal, Editors. W3C, 3 November 2023. The latest version of this document is https://www.w3.org/policies/process/.

[PRONOUNS]

Personal pronouns in specifications, M. Dürst, 13 May 2000. This email message is https://lists.w3.org/Archives/Public/www-international/2000AprJun/0058.

[PUBRULES]

Technical Report Publication Policy, the W3C Team. W3C, 2000-2017. This document is on-line at https://www.w3.org/Guide/pubrules.

[REF-TITLES]

please use titles, not addresses, as link text, D. Connolly, 10 February 2000. This email message is on-line at https://lists.w3.org/Archives/Public/www-html-editor/2000JanMar/0103.

[REGISTER-1]

How to Register an Internet Media Type for a W3C Specification, Philippe Le Hégaret, 2019. This Web page is on-line at https://www.w3.org/2020/01/registering-mediatypes.html.

[REGISTER-2]

TAG Position on Use of Unregistered Media Types in W3C Recommendations, N. Mendelsohn, 4 August 2006. This email message is https://lists.w3.org/Archives/Public/www-tag/2006Aug/0012.

[SPEC-PROD]

spec-prod@w3.org. W3C, 1998-2001. Subscribe to this public mailing list at http://www.w3.org/Mail/Lists and view its archive at https://lists.w3.org/Archives/Public/spec-prod.

[STYLE-GUIDE]

Style Guide for Online Hypertext, T. Berners-Lee. 1992-1998. This guide is on-line at https://www.w3.org/Provider/Style.

[TR]

W3C Technical Reports and Publications, W3C, 1995-2024. This Web page is on-line at https://www.w3.org/TR.

[TRANSLATE]

Translations at W3C, W3C, 1997-2003. This Web page is on-line at https://www.w3.org/Consortium/Translation.

[VALIDATE]

W3C Markup Validation Service, 1994-2013. This service is on-line at https://validator.w3.org.

External Links

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

[CSS3UI]

CSS Basic User Interface Module Level 3 (CSS3 UI) section 4.1, Tantek Çelik, Florian Rivoal, Editors. W3C, 2018. This example is on-line at https://www.w3.org/TR/css-ui-3/#outline.

[EXCAL]

Excalibur, R. Zaccone, 2001. The Excalibur home page is http://www.eg.bucknell.edu/\~excalibr/excalibur.html.

[HTML]

HTML 5.1. Steve Faulkner, et al., Editors, W3C, 2016. The latest version of the HTML is available at https://www.w3.org/TR/html/.

[ISPELL]

International Ispell, G. Kuenning et al. 1971-2001. The Ispell home page is http://fmg-www.cs.ucla.edu/fmg-members/geoff/ispell.html.

[SCHEMA-DATATYPES]

XML Schema Part 2: Datatypes sections 3.2.9 through 3.2.14.1, P. V. Biron, and A. Malhotra, Editors. W3C, 2001. The latest version of XML Schema: Datatypes is available at https://www.w3.org/TR/xmlschema-2.

[XML]

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

[XML1]

Extensible Markup Language (XML) 1.0 (Fourth Edition), 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 latest edition of XML 1.0 is available at http://www.w3.org/TR/xml/.