HTML 4.0 Specification
`
` REC-html40-971218
`
`HTML 4.0 Specification
`W3C Recommendation 18-Dec-1997
`
`This version:
`http://www.w3.org/TR/REC-html40-971218
`Latest version:
`http://www.w3.org/TR/REC-html40
`Previous version:
`http://www.w3.org/TR/PR-html40-971107
`Editors:
`Dave Raggett <dsr@w3.org>
`Arnaud Le Hors <lehors@w3.org>
`Ian Jacobs <ij@w3.org>
`
`Abstract
`
`This specification defines the HyperText Markup Language (HTML), version 4.0, the publishing language
`of the World Wide Web. In addition to the text, multimedia, and hyperlink features of the previous
`versions of HTML, HTML 4.0 supports more multimedia options, scripting languages, style sheets, better
`printing facilities, and documents that are more accessible to users with disabilities. HTML 4.0 also takes
`great strides towards the internationalization of documents, with the goal of making the Web truly World
`Wide.
`
`HTML 4.0 is an SGML application conforming to International Standard ISO 8879 -- Standard
`Generalized Markup Language [ISO8879] [p.323] .
`
`Status of this document
`
`This document has been reviewed by W3C Members and other interested parties and has been endorsed
`by the Director as a W3C Recommendation. It is a stable document and may be used as reference material
`or cited as a normative reference from another document. W3C’s role in making the Recommendation is
`to draw attention to the specification and to promote its widespread deployment. This enhances the
`functionality and interoperability of the Web.
`
`W3C recommends that user agents and authors (and in particular, authoring tools) produce HTML 4.0
`documents rather than HTML 3.2 documents (see [HTML32] [p.325] ). For reasons of backwards
`compatibility, W3C also recommends that tools interpreting HTML 4.0 continue to support HTML 3.2
`and HTML 2.0 as well.
`
`1
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`Available formats
`
`A list of current W3C Recommendations and other technical documents can be found at
`http://www.w3.org/TR.
`
`Public discussion on HTML features takes place on www-html@w3.org.
`
`Available formats
`
`The HTML 4.0 W3C Recommendation is also available in the following formats:
`
`A plain text file:
`http://www.w3.org/TR/REC-html40-971218/html40.txt (723Kb),
`A gzip’ed tar file containing HTML documents:
`http://www.w3.org/TR/REC-html40-971218/html40.tgz (339Kb),
`A zip file containing HTML documents (this is a ’.zip’ file not an ’.exe’):
`http://www.w3.org/TR/REC-html40-971218/html40.zip (372Kb),
`A Postscript file:
`http://www.w3.org/TR/REC-html40-971218/html40.ps (4.4Mb, 363 pages),
`A PDF file:
`http://www.w3.org/TR/REC-html40-971218/html40.pdf (2.1Mb) file.
`
`In case of a discrepancy between electronic and printed forms of the specification, the electronic version is
`the definitive version.
`
`Available languages
`
`The English version of this specification is the only normative version. However, for translations of this
`document, see http://www.w3.org/MarkUp/html40-updates/translations.html.
`
`Errata
`
`The list of known errors in this specification is available at
`http://www.w3.org/MarkUp/html40-updates/html40-errata.html
`
`Please report errors in this document to www-html-editor@w3.org.
`
`2
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`Table of Contents
`
`Table of Contents
`
`1. About the HTML 4.0 Specification [p.13]
`1. How the specification is organized [p.13]
`2. Document conventions [p.14]
`1. Elements and attributes [p.14]
`2. Notes and examples [p.15]
`3. Acknowledgments [p.15]
`4. Copyright Notice [p.16]
`2. Introduction to HTML 4.0 [p.17]
`1. What is the World Wide Web? [p.17]
`1. Introduction to URIs [p.17]
`2. Fragment identifiers [p.18]
`3. Relative URIs [p.18]
`2. What is HTML? [p.19]
`1. A brief history of HTML [p.19]
`3. HTML 4.0 [p.20]
`1. Internationalization [p.20]
`2. Accessibility [p.20]
`3. Tables [p.21]
`4. Compound documents [p.21]
`5. Style sheets [p.21]
`6. Scripting [p.22]
`7. Printing [p.22]
`4. Authoring documents with HTML 4.0 [p.22]
`1. Separate structure and presentation [p.22]
`2. Consider universal accessibility to the Web [p.22]
`3. Help user agents with incremental rendering [p.22]
`3. On SGML and HTML [p.23]
`1. Introduction to SGML [p.23]
`2. SGML constructs used in HTML [p.24]
`1. Elements [p.24]
`2. Attributes [p.25]
`3. Character references [p.26]
`4. Comments [p.26]
`3. How to read the HTML DTD [p.27]
`1. DTD Comments [p.27]
`2. Parameter entity definitions [p.27]
`3. Element declarations [p.28]
`Content model definitions [p.28]
`4. Attribute declarations [p.30]
`DTD entities in attribute definitions [p.30]
`Boolean attributes [p.31]
`
`3
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`Table of Contents
`
`4. Conformance: requirements and recommendations [p.33]
`1. Definitions [p.33]
`2. SGML [p.34]
`3. The text/html content type [p.35]
`5. HTML Document Representation [p.37] - Character sets, character encodings, and entities
`1. The Document Character Set [p.37]
`2. Character encodings [p.38]
`1. Choosing an encoding [p.38]
`Notes on specific encodings [p.39]
`2. Specifying the character encoding [p.39]
`3. Character references [p.40]
`1. Numeric character references [p.41]
`2. Character entity references [p.41]
`4. Undisplayable characters [p.42]
`6. Basic HTML data types [p.43] - Character data, colors, lengths, URIs, content types, etc.
`1. Case information [p.43]
`2. SGML basic types [p.44]
`3. Text strings [p.44]
`4. URIs [p.44]
`5. Colors [p.45]
`1. Notes on using colors [p.45]
`6. Lengths [p.46]
`7. Content types (MIME types) [p.46]
`8. Language codes [p.47]
`9. Character encodings [p.47]
`10. Single characters [p.47]
`11. Dates and times [p.47]
`12. Link types [p.48]
`13. Media descriptors [p.49]
`14. Script data [p.50]
`15. Style sheet data [p.51]
`16. Frame target names [p.51]
`7. The global structure of an HTML document [p.53] - The HEAD and BODY of a document
`1. Introduction to the structure of an HTML document [p.53]
`2. HTML version information [p.54]
`3. The HTML element [p.55]
`4. The document head [p.55]
`1. HEAD element [p.55]
`2. The TITLE element [p.56]
`3. The title attribute [p.57]
`4. Meta data [p.57]
`Specifying meta data [p.58]
`The META element [p.58]
`
`4
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`Table of Contents
`
`Meta data profiles [p.61]
`5. The document body [p.62]
`1. The BODY element [p.62]
`2. Element identifiers: the id and class attributes [p.65]
`3. Block-level and inline elements [p.66]
`4. Grouping elements: the DIV and SPAN elements [p.67]
`5. Headings: The H1, H2, H3, H4, H5, H6 elements [p.68]
`6. The ADDRESS element [p.70]
`8. Language information and text direction [p.71] - International considerations for text
`1. Specifying the language of content: the lang attribute [p.71]
`1. Language codes [p.72]
`2. Inheritance of language codes [p.72]
`3. Interpretation of language codes [p.73]
`2. Specifying the direction of text and tables: the dir attribute [p.73]
`1. Introduction to the bidirectional algorithm [p.74]
`2. Inheritance of text direction information [p.75]
`3. Setting the direction of embedded text [p.75]
`4. Overriding the bidirectional algorithm: the BDO element [p.76]
`5. Character references for directionality and joining control [p.78]
`6. The effect of style sheets on bidirectionality [p.79]
`9. Text [p.81] - Paragraphs, Lines, and Phrases
`1. White space [p.81]
`2. Structured text [p.82]
`1. Phrase elements: EM, STRONG, DFN, CODE, SAMP, KBD, VAR, CITE, ABBR, and
`ACRONYM [p.82]
`2. Quotations: The BLOCKQUOTE and Q elements [p.84]
`Rendering quotations [p.85]
`3. Subscripts and superscripts: the SUB and SUP elements [p.86]
`3. Lines and Paragraphs [p.86]
`1. Paragraphs: the P element [p.87]
`2. Controlling line breaks [p.87]
`Forcing a line break: the BR element [p.87]
`Prohibiting a line break [p.88]
`3. Hyphenation [p.88]
`4. Preformatted text: The PRE element [p.88]
`5. Visual rendering of paragraphs [p.90]
`4. Marking document changes: The INS and DEL elements [p.91]
`10. Lists [p.93] - Unordered, Ordered, and Definition Lists
`1. Introduction to lists [p.93]
`2. Unordered lists (UL), ordered lists (OL), and list items (LI) [p.94]
`3. Definition lists: the DL, DT, and DD elements [p.96]
`1. Visual rendering of lists [p.97]
`4. The DIR and MENU elements [p.99]
`
`5
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`Table of Contents
`
`11. Tables [p.101]
`1. Introduction to tables [p.101]
`2. Elements for constructing tables [p.103]
`1. The TABLE element [p.103]
`Table directionality [p.105]
`2. Table Captions: The CAPTION element [p.105]
`3. Row groups: the THEAD, TFOOT, and TBODY elements [p.106]
`4. Column groups: the COLGROUP and COL elements [p.108]
`The COLGROUP element [p.108]
`The COL element [p.110]
`Calculating the number of columns in a table [p.111]
`Calculating the width of columns [p.112]
`5. Table rows: The TR element [p.114]
`6. Table cells: The TH and TD elements [p.114]
`Cells that span several rows or columns [p.117]
`3. Table formatting by visual user agents [p.119]
`1. Borders and rules [p.119]
`2. Horizontal and vertical alignment [p.121]
`Inheritance of alignment specifications [p.123]
`3. Cell margins [p.124]
`4. Table rendering by non-visual user agents [p.125]
`1. Associating header information with data cells [p.125]
`2. Categorizing cells [p.128]
`3. Algorithm to find heading information [p.131]
`5. Sample table [p.132]
`12. Links [p.135] - Hypertext and Media-Independent Links
`1. Introduction to links and anchors [p.135]
`1. Visiting a linked resource [p.135]
`2. Other link relationships [p.137]
`3. Specifying anchors and links [p.137]
`4. Link titles [p.138]
`5. Internationalization and links [p.138]
`2. The A element [p.138]
`1. Syntax of anchor names [p.141]
`2. Nested links are illegal [p.142]
`3. Anchors with the id attribute [p.142]
`4. Unavailable and unidentifiable resources [p.143]
`3. Document relationships: the LINK element [p.143]
`1. Forward and reverse links [p.144]
`2. Links and external style sheets [p.144]
`3. Links and search engines [p.145]
`4. Path information: the BASE element [p.146]
`1. Resolving relative URIs [p.147]
`
`6
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`Table of Contents
`
`13. Objects, Images, and Applets [p.149]
`1. Introduction to objects, images, and applets [p.149]
`2. Including an image: the IMG element [p.150]
`3. Generic inclusion: the OBJECT element [p.152]
`1. Rules for rendering objects [p.154]
`2. Object initialization: the PARAM element [p.156]
`3. Global naming schemes for objects [p.158]
`4. Object declarations and instantiations [p.158]
`4. Including an applet: the APPLET element [p.160]
`5. Notes on embedded documents [p.162]
`6. Image maps [p.162]
`1. Client-side image maps: the MAP and AREA elements [p.163]
`Client-side image map examples [p.165]
`2. Server-side image maps [p.167]
`7. Visual presentation of images, objects, and applets [p.168]
`1. Width and height [p.168]
`2. White space around images and objects [p.168]
`3. Borders [p.168]
`4. Alignment [p.169]
`8. How to specify alternate text [p.169]
`14. Style Sheets [p.171] - Adding style to HTML documents
`1. Introduction to style sheets [p.171]
`2. Adding style to HTML [p.173]
`1. Setting the default style sheet language [p.173]
`2. Inline style information [p.174]
`3. Header style information: the STYLE element [p.174]
`4. Media types [p.177]
`3. External style sheets [p.177]
`1. Preferred and alternate style sheets [p.178]
`2. Specifying external style sheets [p.178]
`4. Cascading style sheets [p.179]
`1. Media-dependent cascades [p.180]
`2. Inheritance and cascading [p.180]
`5. Hiding style data from user agents [p.181]
`6. Linking to style sheets with HTTP headers [p.181]
`15. Alignment, font styles, and horizontal rules [p.183]
`1. Formatting [p.183]
`1. Background color [p.183]
`2. Alignment [p.183]
`3. Floating objects [p.185]
`Float an object [p.185]
`Float text around an object [p.186]
`2. Fonts [p.187]
`
`7
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`Table of Contents
`
`1. Font style elements: the TT, I, B, BIG, SMALL, STRIKE, S, and U elements [p.187]
`2. Font modifier elements: FONT and BASEFONT [p.188]
`3. Rules: the HR element [p.190]
`16. Frames [p.193] - Multi-view presentation of documents
`1. Introduction to frames [p.193]
`2. Layout of frames [p.194]
`1. The FRAMESET element [p.194]
`Rows and columns [p.195]
`Nested frame sets [p.196]
`Sharing data among frames [p.196]
`2. The FRAME element [p.197]
`Setting the initial contents of a frame [p.198]
`Visual rendering of a frame [p.199]
`3. Specifying target frame information [p.200]
`1. Setting the default target for links [p.201]
`2. Target semantics [p.202]
`4. Alternate content [p.202]
`1. The NOFRAMES element [p.202]
`2. Long descriptions of frames [p.203]
`5. Inline frames: the IFRAME element [p.204]
`17. Forms [p.207] - User-input Forms: Text Fields, Buttons, Menus, and more
`1. Introduction to forms [p.207]
`2. Controls [p.208]
`1. Control types [p.208]
`3. The FORM element [p.210]
`4. The INPUT element [p.211]
`1. Control types created with INPUT [p.213]
`2. Examples of forms containing INPUT controls [p.214]
`5. The BUTTON element [p.215]
`6. The SELECT, OPTGROUP, and OPTION elements [p.217]
`1. Preselected options [p.218]
`7. The TEXTAREA element [p.221]
`8. The ISINDEX element [p.222]
`9. Labels [p.223]
`1. The LABEL element [p.223]
`10. Adding structure to forms: the FIELDSET and LEGEND elements [p.225]
`11. Giving focus to an element [p.227]
`1. Tabbing navigation [p.228]
`2. Access keys [p.229]
`12. Disabled and read-only controls [p.230]
`1. Disabled controls [p.230]
`2. Read-only controls [p.231]
`13. Form submission [p.231]
`
`8
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`Table of Contents
`
`1. Form submission method [p.231]
`2. Successful controls [p.232]
`3. Processing form data [p.232]
`Step one: Identify the successful controls [p.233]
`Step two: Build a form data set [p.233]
`Step three: Encode the form data set [p.233]
`Step four: Submit the encoded form data set [p.233]
`4. Form content types [p.233]
`application/x-www-form-urlencoded [p.233]
`multipart/form-data [p.234]
`18. Scripts [p.237] - Animated Documents and Smart Forms
`1. Introduction to scripts [p.237]
`2. Designing documents for user agents that support scripting [p.238]
`1. The SCRIPT element [p.238]
`2. Specifying the scripting language [p.239]
`The default scripting language [p.239]
`Local declaration of a scripting language [p.239]
`References to HTML elements from a script [p.240]
`3. Intrinsic events [p.240]
`4. Dynamic modification of documents [p.243]
`3. Designing documents for user agents that don’t support scripting [p.244]
`1. The NOSCRIPT element [p.244]
`2. Hiding script data from user agents [p.245]
`19. SGML reference information for HTML [p.247] - Formal definition of HTML and validation
`1. document Document Validation [p.247]
`2. Sample SGML catalog [p.248]
`20. SGML Declaration of HTML 4.0 [p.249]
`1. SGML Declaration [p.249]
`21. Document Type Definition [p.251]
`22. Transitional Document Type Definition [p.267]
`23. Frameset Document Type Definition [p.287]
`24. Character entity references in HTML 4.0 [p.289]
`1. Introduction to character entity references [p.289]
`2. Character entity references for ISO 8859-1 characters [p.289]
`1. The list of characters [p.290]
`3. Character entity references for symbols, mathematical symbols, and Greek letters [p.293]
`1. The list of characters [p.294]
`4. Character entity references for markup-significant and internationalization characters [p.298]
`1. The list of characters [p.298]
`
`A. Changes between HTML 3.2 and HTML 4.0 [p.301]
`1. Changes to elements [p.301]
`1. New elements [p.301]
`2. Deprecated elements [p.301]
`
`9
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`Table of Contents
`
`3. Obsolete elements [p.301]
`2. Changes to attributes [p.302]
`3. Changes for accessibility [p.302]
`4. Changes for meta data [p.302]
`5. Changes for text [p.302]
`6. Changes for links [p.302]
`7. Changes for tables [p.302]
`8. Changes for images, objects, and image maps [p.303]
`9. Changes for forms [p.303]
`10. Changes for style sheets [p.304]
`11. Changes for frames [p.304]
`12. Changes for scripting [p.304]
`13. Changes for internationalization [p.304]
`B. Performance, Implementation, and Design Notes [p.305]
`1. Notes on invalid documents [p.306]
`2. Special characters in URI attribute values [p.306]
`1. Non-ASCII characters in URI attribute values [p.306]
`2. Ampersands in URI attribute values [p.307]
`3. SGML implementation notes [p.307]
`1. Line breaks [p.307]
`2. Specifying non-HTML data [p.308]
`Element content [p.308]
`Attribute values [p.309]
`3. SGML features with limited support [p.309]
`4. Boolean attributes [p.309]
`5. Marked Sections [p.309]
`6. Processing Instructions [p.310]
`7. Shorthand markup [p.310]
`4. Notes on helping search engines index your Web site [p.311]
`1. Search robots [p.312]
`The robots.txt file [p.312]
`Robots and the META element [p.313]
`5. Notes on tables [p.313]
`1. Design rationale [p.313]
`Dynamic reformatting [p.314]
`Incremental display [p.314]
`Structure and presentation [p.314]
`Row and column groups [p.315]
`Accessibility [p.315]
`2. Recommended Layout Algorithms [p.315]
`Fixed Layout Algorithm [p.316]
`Autolayout Algorithm [p.316]
`6. Notes on forms [p.318]
`
`10
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`Table of Contents
`
`1. Incremental display [p.318]
`2. Future projects [p.319]
`7. Notes on scripting [p.319]
`1. Reserved syntax for future script macros [p.319]
`Current Practice for Script Macros [p.319]
`8. Notes on frames [p.321]
`9. Notes on accessibility [p.321]
`10. Notes on security [p.321]
`1. Security issues for forms [p.322]
`
`References [p.323]
`1. Normative references [p.323]
`2. Informative references [p.325]
`Index of Elements [p.329]
`Index of Attributes [p.333]
`Index [p.349]
`
`Copyright [p.16] © 1997 W3C (MIT, INRIA, Keio ), All Rights Reserved.
`
`11
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`Table of Contents
`
`12
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`1 About the HTML 4.0 Specification
`
`1 About the HTML 4.0 Specification
`
`Contents
`
`1. How the specification is organized [p.13]
`2. Document conventions [p.14]
`1. Elements and attributes [p.14]
`2. Notes and examples [p.15]
`3. Acknowledgments [p.15]
`4. Copyright Notice [p.16]
`
`1.1 How the specification is organized
`
`This specification is divided into the following sections:
`
`Sections 2 and 3: Introduction to HTML 4.0
`The introduction describes HTML’s place in the scheme of the World Wide Web, provides a brief
`history of the development of HTML, highlights what can be done with HTML 4.0, and provides
`some HTML authoring tips.
`
`The brief SGML tutorial gives readers some understanding of HTML’s relationship to SGML and
`gives summary information on how to read the HTML Document Type Definition (DTD).
`Sections 4 - 24: HTML 4.0 reference manual
`The bulk of the reference manual consists of the HTML language reference, which defines all
`elements and attributes of the language.
`
`This document has been organized by topic rather than by the grammar of HTML. Topics are
`grouped into three categories: structure, presentation, and interactivity. Although it is not easy to
`divide HTML constructs perfectly into these three categories, the model reflects the HTML Working
`Group’s experience that separating a document’s structure from its presentation produces more
`effective and maintainable documents.
`
`The language reference consists of the following information:
`
`What characters [p.37] may appear in an HTML document.
`
`Basic data types [p.43] of an HTML document.
`
`Elements that govern the structure of an HTML document, including text [p.81] , lists [p.93] ,
`tables [p.101] , links [p.135] , and included objects, images, and applets [p.149] .
`
`Elements that govern the presentation of an HTML document, including style sheets [p.171] ,
`fonts, colors, rules, and other visual presentation [p.183] , and frames for multi-windowed
`presentations [p.193] .
`
`13
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`1.2 Document conventions
`
`Elements that govern interactivity with an HTML document, including forms for user input
`[p.207] and scripts for active documents [p.237] .
`
`The SGML formal definition of HTML:
`The SGML declaration of HTML [p.249] .
`Three DTDs: strict [p.251] , transitional [p.267] , and frameset [p.287] .
`The list of character references [p.289] .
`
`Appendixes
`The first appendix contains information about changes from HTML 3.2 [p.301] to help authors and
`implementors with the transition to HTML 4.0. The second appendix contains performance and
`implementation notes [p.305] , and is primarily intended to help implementors create user agents for
`HTML 4.0.
`References
`A list of normative and informative references.
`Indexes
`Three indexes give readers rapid access to the definition of key concepts [p.349] , elements [p.329]
`and attributes [p.333] .
`
`1.2 Document conventions
`
`This document has been written with two types of readers in mind: authors and implementors. We hope
`the specification will provide authors with the tools they need to write efficient, attractive, and accessible
`documents, without over-exposing them to HTML’s implementation details. Implementors, however,
`should find all they need to build conforming user agents.
`
`The specification may be approached in several ways:
`
`Read from beginning to end. The specification begins with a general presentation of HTML and
`becomes more and more technical and specific towards the end.
`Quick access to information. In order to get information about syntax and semantics as quickly as
`possible, the online version of the specification includes the following features:
`1. Every reference to an element or attribute is linked to its definition in the specification. Each
`element or attribute is defined in only one location.
`2. Every page includes links to the indexes, so you never are more than two links away from
`finding the definition of an element [p.329] or attribute [p.333] .
`
`3. The front pages of the three sections of the language reference manual extend the initial table of
`contents with more detail about each section.
`
`1.2.1 Elements and attributes
`
`Element names are written in upper case letters (e.g., BODY). Attribute names are written in lower case
`letters (e.g., lang, onsubmit). Recall that in HTML, element and attribute names are case-insensitive; the
`convention is meant to encourage readability.
`
`14
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`1.3 Acknowledgments
`
`Element and attribute names in this document have been marked up and may be rendered specially by
`some user agents.
`
`Each attribute definition specifies the type of its value. If the type allows a small set of possible values, the
`definition lists the set of values, separated by a bar (|).
`
`After the type information, each attribute definition indicates the case-sensitivity of its values, between
`square brackets ("[]"). See the section on case information [p.43] for details.
`
`1.2.2 Notes and examples
`
`Informative notes are emphasized to stand out from surrounding text and may be rendered specially by
`some user agents.
`
`All examples illustrating deprecated [p.34] usage are marked as "DEPRECATED EXAMPLE".
`Deprecated examples also include recommended alternate solutions. All examples that illustrates illegal
`usage are clearly marked "ILLEGAL EXAMPLE".
`
`Examples and notes have been marked up and may be rendered specially by some user agents.
`
`1.3 Acknowledgments
`
`Thanks to everyone who has helped to author the working drafts that went into the HTML 4.0
`specification, and to all those who have sent suggestions and corrections.
`
`Many thanks to the Web Accessibility Initiative task force (WAI HC group) for their work on improving
`the accessibility of HTML and to T.V. Raman (Adobe) for his early work on developing accessible forms.
`
`The authors of this specification, the members of the W3C HTML Working Group, deserve much
`applause for their diligent review of this document, their constructive comments, and their hard work:
`John D. Burger (MITRE), Steve Byrne (JavaSoft), Martin J. Dürst (University of Zurich), Daniel Glazman
`(Electricité de France), Scott Isaacs (Microsoft), Murray Maloney (GRIF), Steven Pemberton (CWI),
`Robert Pernett (Lotus), Jared Sorensen (Novell), Powell Smith (IBM), Robert Stevahn (HP), Ed Tecot
`(Microsoft), Jeffrey Veen (HotWired), Mike Wexler (Adobe), Misha Wolf (Reuters), and Lauren Wood
`(SoftQuad).
`
`Thank you Dan Connolly (W3C) for rigorous and bountiful input as part-time editor and thoughtful
`guidance as chairman of the HTML Working Group. Thank you Sally Khudairi (W3C) for your
`indispensable work on press releases.
`
`Thanks to David M. Abrahamson and Roger Price for their careful reading of the specification and
`constructive comments.
`
`Thanks to Jan Kärrman, author of html2ps for helping so much in creating the Postscript version of the
`specification.
`
`15
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`1.4 Copyright Notice
`
`Of particular help from the W3C at Sophia-Antipolis were Janet Bertot, Bert Bos, Stephane Boyera,
`Daniel Dardailler, Yves Lafon, Håkon Lie, Chris Lilley, and Colas Nahaboo (Bull).
`
`Lastly, thanks to Tim Berners-Lee without whom none of this would have been possible.
`
`1.4 Copyright Notice
`
`Copyright © 1997 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut
`National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved.
`
`Documents on the W3C site are provided by the copyright holders under the following license. By
`obtaining, using and/or copying this document, or the W3C document from which this statement is linked,
`you agree that you have read, understood, and will comply with the following terms and conditions:
`
`Permission to use, copy, and distribute the contents of this document, or the W3C document from which
`this statement is linked, in any medium for any purpose and without fee or royalty is hereby granted,
`provided that you include the following on ALL copies of the document, or portions thereof, that you use:
`
`1. A link or URI to the original W3C document.
`2. The pre-existing copyright notice of the original author, if it doesn’t exist, a notice of the form:
`"Copyright © World Wide Web Consortium, (Massachusetts Institute of Technology, Institut
`National de Recherche en Informatique et en Automatique, Keio University). All Rights Reserved."
`3. If it exists, the STATUS of the W3C document.
`
`When space permits, inclusion of the full text of this NOTICEshould be provided. In addition, credit shall
`be attributed to the copyright holders for any software, documents, or other items or products that you
`create pursuant to the implementation of the contents of this document, or any portion thereof.
`
`No right to create modifications or derivatives is granted pursuant to this license.
`
`THIS DOCUMENT IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
`REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT
`LIMITED TO, WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
`PURPOSE, NON-INFRINGEMENT, OR TITLE; THAT THE CONTENTS OF THE
`DOCUMENT ARE SUITABLE FOR ANY PURPOSE; NOR THAT THE IMPLEMENTATION
`OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS,
`COPYRIGHTS, TRADEMARKS OR OTHER RIGHTS.
`
`COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL
`OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR
`THE PERFORMANCE OR IMPLEMENTATION OF THE CONTENTS THEREOF.
`
`The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to
`this document or its contents without specific, written prior permission. Title to copyright in this
`document will at all times remain with copyright holders.
`
`16
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`2 Introduction to HTML 4.0
`
`2 Introduction to HTML 4.0
`
`Contents
`
`1. What is the World Wide Web? [p.17]
`1. Introduction to URIs [p.17]
`2. Fragment identifiers [p.18]
`3. Relative URIs [p.18]
`2. What is HTML? [p.19]
`1. A brief history of HTML [p.19]
`3. HTML 4.0 [p.20]
`1. Internationalization [p.20]
`2. Accessibility [p.20]
`3. Tables [p.21]
`4. Compound documents [p.21]
`5. Style sheets [p.21]
`6. Scripting [p.22]
`7. Printing [p.22]
`4. Authoring documents with HTML 4.0 [p.22]
`1. Separate structure and presentation [p.22]
`2. Consider universal accessibility to the Web [p.22]
`3. Help user agents with incremental rendering [p.22]
`
`2.1 What is the World Wide Web?
`
`The World Wide Web (Web) is a network of information resources. The Web relies on three mechanisms
`to make these resources readily available to the widest possible audience:
`
`1. A uniform naming scheme for locating resources on the Web (e.g., URIs).
`2. Protocols, for access to named resources over the Web (e.g., HTTP).
`3. Hypertext, for easy navigation among resources (e.g., HTML).
`
`The ties between the three mechanisms are apparent throughout this specification.
`
`2.1.1 Introduction to URIs
`
`Every resource available on the Web -- HTML document, image, video clip, program, etc. -- has an
`address that may be encoded by a Universal Resource Identifier, or "URI".
`
`URIs typically consist of three pieces:
`
`1. The naming scheme of the mechanism used to access the resource.
`2. The name of the machine hosting the resource.
`3. The name of the resource itself, given as a path.
`
`17
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`2.1.2 Fragment identifiers
`
`Consider the URI that designates the current HTML specification:
`
` http://www.w3.org/TR/PR-html4/cover.html
`
`This URI may be read as follows: There is a document available via the HTTP protocol (see [RFC2068]
`[p.324] ), residing on the machine www.w3.org, accessible via the path "/TR/PR-html4/cover.html". Other
`schemes you may see in HTML documents include "mailto" for email and "ftp" for FTP.
`
`Here is another example of a URI. This one refers to a user’s mailbox:
`
` ...this is text...
` For all comments, please send email to
` <A href="mailto:joe@someplace.com">Joe Cool</A>.
`
`Note. Most readers may be familiar with the term "URL" and not the term "URI". URLs form a subset of
`the more general URI naming scheme.
`
`2.1.2 Fragment identifiers
`
`Some URIs refer to a location within a resource. This kind of URI ends with "#" followed by an anchor
`identifier (called the fragment identifier). For instance, here is a URI pointing to an anchor named
`section_2:
`
`http://somesite.com/html/top.html#section_2
`
`2.1.3 Relative URIs
`
`A relative URI doesn’t contain any naming scheme information. Its path generally refers to a resource on
`the same machine as the current document. Relative URIs may contain relative path components (e.g., ".."
`means one level up in the hierarchy defined by the path), and may contain fragment identifiers [p.18] .
`
`Relative URIsare resolved to full URIs [p.147] using a base URI. As an example of relative URI
`resolution, assume we have the base URI "http://www.acme.com/support/intro.html". The relative URI in
`the following markup for a hypertext link:
`
` <A href="suppliers.html">Suppliers</A>
`
`would expand to the full URI "http://www.acme.com/support/suppliers.html", while the relative URI in
`the following markup for an image
`
` <IMG src="../icons/logo.gif" alt="logo">
`
`would expand to the full URI "http://www.acme.com/icons/logo.gif".
`
`In HTML, URIs are used to:
`
`Link to another document or resource, (see the A and LINK elements).
`Link to an external style sheet or script (see the LINK and SCRIPT elements).
`Include an image, object, or applets in a page, (see the IMG, OBJECT, APPLET and INPUT
`elements).
`
`18
`
`Starbucks, Ex. 1106
`Starbucks v. Ameranth, CBM2015-00091
`
`

`
`2.2 What is HTML?
`
`Create an image map (see the MAP and AREA elements).
`Submit a form (see FORM).
`Create a frame document (see the FRAME and IFRAME elements).
`Cite an external reference (see the Q, BLOCKQUOTE, INS and DEL elements).
`Refer to metadata conventions describing a document (see the HEAD element).
`
`Please consult the section on the URI [p.44] typ