idnits 2.17.1 draft-ietf-html-spec-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-24) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 132 instances of lines with control characters in the document. == There are 2 instances of lines with non-RFC2606-compliant FQDNs in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 11 has weird spacing: '...as, and its w...' == Line 1456 has weird spacing: '...ered as monos...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 8, 1995) is 10668 days in the past. Is this intentional? -- Found something which looks like a code comment -- if you have code sections in the document, please surround them with '' and '' lines. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 9 errors (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET DRAFT February 8, 1995 2 Expires in six months 4 HyperText Markup Language Specification - 2.0 5 7 STATUS OF THIS MEMO 9 This document is an Internet draft. Internet drafts are 10 working documents of the Internet Engineering Task Force 11 (IETF), its areas, and its working groups. Note that 12 other groups may also distribute working documents as 13 Internet drafts. 15 Internet drafts are draft documents valid for a maximum 16 of six months and may be updated, replaced, or obsoleted 17 by other documents at any time. It is inappropriate to 18 use Internet drafts as reference material or to cite 19 them other than as "work in progress." 21 To learn the current status of any Internet-Draft, 22 please check the "1id-abstracts.txt" listing contained 23 in the Internet- Drafts Shadow Directories on 24 ftp.is.co.za (Africa), nic.nordu.net (Europe), 25 munnari.oz.au (Pacific Rim), ds.internic.net (US East 26 Coast), or ftp.isi.edu (US West Coast). 28 Distribution of this document is unlimited. Please send 29 comments to the HTML working group (HTML-WG) of the 30 Internet Engineering Task Force (IETF) at . Discussions of the group are archived at 32 URL: http://www.acl.lanl.gov/HTML_WG/archives.html. 34 Abstract 36 The HyperText Markup Language (HTML) is a simple markup 37 language used to create hypertext documents that are 38 portable from one platform to another. HTML documents 39 are SGML documents with generic semantics that are 40 appropriate for representing information from a wide 41 range of applications. HTML markup can represent 42 hypertext news, mail, documentation, and hypermedia; 43 menus of options; database query results; simple 44 structured documents with in-lined graphics; and 45 hypertext views of existing bodies of information. 47 HTML has been in use by the World Wide Web (WWW) global 48 information initiative since 1990. This specification 49 roughly corresponds to the capabilities of HTML in 50 HTML 2.0 February 8, 1995 52 common use prior to June 1994. It is defined as an 53 application of ISO Standard 8879:1986 Information 54 Processing Text and Office Systems; Standard Generalized 55 Markup Language (SGML). 57 The "text/html; version=2.0" Internet Media Type (RFC 1590) and 58 MIME Content Type (RFC 1521) is defined by this specification. 60 Contents 62 Overview of HTML Specification........................ 2 64 HTML Specification.................................... 11 66 Security Considerations............................... 52 68 Obsolete and Proposed Features........................ 53 70 HTML Document Type Definitions........................ 56 72 Glossary.............................................. 74 74 References............................................ 77 76 Acknowledgments....................................... 78 78 Author's Addresses.................................... 80 80 1. Overview of HTML Specification 82 This chapter is a summary of the HTML specification. See 83 Section 2. for the complete specification. 85 HTML describes the structure and organization of a 86 document. It only suggests appropriate presentations of 87 the document when processed. 89 In HTML documents, tags define the start and end of 90 headings, paragraphs, lists, character highlighting and 91 links. Most HTML elements are identified in a document 92 as a start tag, which gives the element name and 93 attributes, followed by the content, followed by the end 94 tag. Start tags are delimited by < and >, and end tags 95 are delimited by . 97 Example: 99 HTML 2.0 February 8, 1995 101

This is a heading

103 Every HTML document starts with a HTML document 104 identifier which contains two sections, a head and a 105 body. The head contains HTML elements which describe the 106 documents title, usage and relationship with other 107 documents. The body contains other HTML elements with 108 the entire text and graphics of the document. 110 This overview briefly describes the syntax of HTML 111 elements and provides an example HTML document. 113 NOTE: The term "HTML user agent" is used in this 114 document to describe applications that are used with 115 HTML documents. 117 1.1 HTML Elements 119 1.1.1 Document Structure Elements 121 HTML Identifier 123 ... 125 The HTML identifier defines the document as containing 126 HTML elements. It contains only the Head and Body 127 elements. 129 Head 131 ... 133 The Head element contains HTML elements that describe 134 the documents title, usage and relationship with other 135 documents. 137 Body 139 ... 141 The Body element contains the text and its associated 142 HTML elements of the document. 144 Example of Document Structure Elements 146 147 148 The Document's Title 149 150 151 HTML 2.0 February 8, 1995 153 The document's text. 154 156 1.1.2 Anchor Element 158 Anchor 160 ... 162 An anchor specifies a link to another location () or the value to use when linking to this location 164 from another location (): 166 See HaL's 167 information for more details. 169 Section B describes... 170 ... 171 See Section B for more information. 173 1.1.3 Block Formatting Elements 175 Address 177
...
179
180 Newsletter editor
181 J.R. Brown
182 JimquickPost News, Jumquick, CT 01234
183 Tel (123) 456 7890 184
186 Body 188 ... 190 Place the and tags above and below the 191 body of the text (not including the head) of your HTML 192 document. 194 Blockquote 196
...
197 I think it ends 198
199

Soft you now, the fair Ophelia. Nymph, in thy 200 orisons, 201 be all my sins remembered. 202

203 HTML 2.0 February 8, 1995 205 but I am not sure. 207 Head 209 ... 211 Every HTML document must have a head, which provides a 212 title. Example: 214 215 216 Introduction to HTML 217 219 Headings 221

This is a first level heading

222

There are six levels of headings. 223

Second level heading

224

This text appears under the second level heading 226 Horizontal Rule 228


230 Inserts a horizontal rule that spans the width of the 231 document. Example: 233
234
February 8, 1995, CERN
235 237 HTML Identifier 239 ... 241 An HTML document begins with an tag and ends with 242 the tag. 244 Line Break 246
248 Forces a line break: 250 Name
251 Street address
252 City, State Zip 254 Paragraph 255 HTML 2.0 February 8, 1995 257

...

259

This Heading Precedes the Paragraph

260

This is the text of the first paragraph. 261

This is the text of the second paragraph. Although 262 you do not need to start paragraphs on new lines, 263 maintaining this convention facilitates document 264 maintenance. 265

This is the text of a third paragraph. 267 Preformatted Text 269

 ... 
271
272	            This is an example of preformatted text.
273	            
275 Title 277 ... 279 Title of document 281 1.1.4 List Elements 283 Definition List 285
...
term
definition...
287
288
Term
This is the first definition. 289
Term
This is the second definition. 290
292 Directory List 294 ...
  • List item...
  • 296 297
  • A-H
  • I-M 298
  • M-R
  • S-Z 299
  • 301 Menu List 303 ...
  • List item...
  • 305 306 HTML 2.0 February 8, 1995 308
  • First item in the list. 309
  • Second item in the list. 310
  • Third item in the list. 311
  • 313 Ordered List 315
      ...
    1. List item...
    317
      318
    1. Click the Web button to open the Open the URL 319 window. 320
    2. Enter the URL number in the text field of the Open 321 URL window. The Web document you specified is displayed. 322
    3. Click highlighted text to move from one link to 323 another. 324
    326 Unordered List 328
      ...
    • List item...
    330
      331
    • This is the first item in the list. 332
    • This is the second item in the list. 333
    • This is the third item in the list. 334
    336 1.1.5 Information Type and Character Formatting Elements 338 Bold 340 ... 342 Suggests the rendering of the text in boldface. If 343 boldface is not available, alternative mapping is 344 allowed. 346 Citation 348 ... 350 Specifies a citation; typically rendered as italic. 352 Code 354 ... 356 Indicates an inline example of code; typically rendered 357 as monospaced.. Do not confuse with the
     tag.
    
    359	                                HTML 2.0                February 8, 1995
    
    361	         Emphasis
    
    363	             ... 
    
    365	            Provides typographic emphasis; typically rendered as
    366	            italics.
    
    368	         Italics
    
    370	             ... 
    
    372	            Suggests the rendering of text in italic font, or
    373	            slanted if italic is not available.
    
    375	         Keyboard
    
    377	             ... 
    
    379	            Indicates text typed by a user; typically rendered as
    380	            monospaced.
    
    382	         Sample
    
    384	             ... 
    
    386	            Indicates a sequence of literal characters; typically
    387	            rendered as monospaced..
    
    389	         Strong
    
    391	             ... 
    
    393	            Provides strong typographic emphasis; typically rendered
    394	            as bold.
    
    396	         Typetype
    
    398	             ... 
    
    400	            Specifies that the text be rendered in fixed-width font.
    
    402	         Variable
    
    404	             ... 
    
    406	            Indicates a variable name; typically rendered as italic.
    
    408	       1.1.6 Image Element
    409	                                HTML 2.0                February 8, 1995
    
    411	         Image
    
    413	            
    
    415	            Inserts the referenced graphic image into the document
    416	            at the location where the element occurs.
    
    418	            Example:
    
    420	            Warning: Be sure to read
    421	            these instructions.
    
    423	      1.1.7 Form Elements
    
    425	         Form
    
    427	            
    ...
    429 The Form element contains nested elements (described 430 below) which define user input controls and allow 431 descriptive text to be displayed when the document is 432 processed. 434 Input 436 438 Takes these attributes: ALIGN, MAXLENGTH, NAME, SIZE, 439 SRC, TYPE, VALUE. The type attribute can define these 440 field types: CHECKBOX, HIDDEN, IMAGE, PASSWORD, RADIO, 441 RESET, SUBMIT, TEXT. 443 Example: 445
    446

    Your name: 447

    Male 448

    Female 450

    452 Option 454