idnits 2.17.1
draft-ietf-html-spec-03.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-03-29) 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 -- however, there's a paragraph with a matching
beginning. Boilerplate error?
** 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
== The page length should not exceed 58 lines per page, but there was 1
longer page, the longest (page 1) being 3564 lines
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.)
** There are 11 instances of too long lines in the document, the longest
one being 4 characters in excess of 72.
== There are 1 instance of lines with non-RFC2606-compliant FQDNs in the
document.
Miscellaneous warnings:
----------------------------------------------------------------------------
-- 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 (May 31, 1995) is 10530 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 ' Some text. *wow*
311 |
312 \-"Some text. "
313 |
314 \-EM
315 | |
316 | \-
317 | |
318 | \-"*wow*"
319 | |
320 | \-
321 |
322 \-' 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)
-- Missing reference section? 'IMEDIA' on line 3042 looks like a reference
-- Missing reference section? 'MIME' on line 3025 looks like a reference
-- Missing reference section? 'SGML' on line 3073 looks like a reference
-- Missing reference section? 'IANA' on line 3046 looks like a reference
-- Missing reference section? 'RELURL' on line 3032 looks like a reference
-- Missing reference section? 'URL' on line 3012 looks like a reference
-- Missing reference section? 'URI' on line 3005 looks like a reference
-- Missing reference section? 'HTTP' on line 3018 looks like a reference
-- Missing reference section? 'GOLD90' on line 3038 looks like a reference
-- Missing reference section? 'SQ91' on line 3050 looks like a reference
-- Missing reference section? 'US-ASCII' on line 3054 looks like a reference
-- Missing reference section? 'ISO-8859-1' on line 3059 looks like a
reference
Summary: 8 errors (**), 0 flaws (~~), 3 warnings (==), 15 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
1 HTML Working Group T. Berners-Lee
2 INTERNET-DRAFT MIT/W3C
3
This is a Heading
398 Some elements only have a start-tag without an end-tag. For
399 example, to create a line break, you use the `
' tag.
400 Additionally, the end tags of some other elements, such as
401 Paragraph (`
', `', and `' are 424 equivalent, whereas `&' is different from `&'. 426 In a start-tag, the element name must immediately follow the 427 tag open delimiter `<'. 429 2.2.4. Attributes 431 In a start-tag, white space and attributes are allowed 432 between the element name and the closing delimiter. An 433 attribute typically consists of an attribute name, an equal 434 sign, and a value, though some attributes may be just a 435 value. White space is allowed around the equal sign. 437 The value of the attribute may be either: 439 * A string literal, delimited by single quotes or 440 double quotes and not containing any occurrences of the 441 delimiting character. 443 NOTE - Some historical implementations consider any 444 occurrence of the `>' character to signal the end of a 445 tag. For compatibility with such implementations, when 446 `>' appears in an attribute value, it should be 447 represented with a numeric character reference. For 448 example, `' should be 449 written `' or `'. 452 * A name token (a sequence of letters, digits, periods, 453 or hyphens). 455 NOTE - Some historical implementations allow any 456 character except space or `>' in a name token. 458 In this example, is the element name, src is the 459 attribute name, and `http://host/dir/file.gif' is the 460 attribute value: 462 464 A useful technique for computing an attribute value literal 465 for a given string is to replace each quote and space 466 character by an entity reference or numeric character 467 reference as follows: 469 ENTITY NUMERIC 470 CHARACTER REFERENCE CHAR REF CHARACTER DESCRIPTION 471 TAB Tab 472 LF Line Feed 473 CR Carriage Return 474 Space 475 " " " Quotation mark 476 & & & Ampersand 478 For example: 480 482 Note that the SGML declaration in section 13.3 limits the 483 length of an attribute value to 1024 characters. 485 Attributes such as ISMAP and COMPACT may be written using a 486 minimized syntax. The markup: 488490 can be written using a minimized syntax: 492
494 NOTE - Some historical implementations only understand 495 the minimized syntax. 497 2.2.5. Comments 499 To include comments in an HTML document, use a comment 500 declaration. A comment declaration consists of `'. Each comment 502 starts with `--' and includes all text up to and including 503 the next occurrence of `--'. In a comment declaration, white 504 space is allowed after each comment, but not before the 505 first comment. The entire comment declaration is ignored. 507 NOTE - Some historical HTML implementations incorrectly 508 consider any `>' character to be the termination of a 509 comment. 511 For example: 513 514
HTML Comment Example 515 516 517 518 519 520522 2.2.6. Example HTML Document 524 525 526 527
528Structural Example 529 530First Header
531This is a paragraph in the example HTML file. Keep in mind 532 that the title does not appear in the document text, but that 533 the header (defined by H1) does.
534535
544- First item in an ordered list. 536
- Second item in an ordered list. 537
538
542- Note that lists can be nested; 539
- Whitespace may be used to assist in reading the 540 HTML source. 541
- Third item in an ordered list. 543
This is an additional paragraph. Technically, end tags are 545 not required for paragraphs, although they are allowed. You can 546 include character highlighting in a paragraph. This sentence 547 of the paragraph is emphasized. Note that the </P> 548 end tag has been omitted. 549
550 551 Be sure to read these bold instructions. 552 554 3. HTML as an Internet Media Type 556 An HTML user agent allows users to interact with resources 557 which have HTML representations. At a minimum, it must allow 558 users to examine and navigate the content of HTML level 1 559 documents. HTML user agents should be able to preserve all 560 formatting distinctions represented in an HTML document, and 561 be able to simultaneously present resources referred to by 562 IMG elements (they may ignore some formatting distinctions 563 or IMG resources at the request of the user). Conforming 564 HTML user agents should support form entry and submission. 566 3.1. text/html media type 568 This specification defines the Internet Media Type[IMEDIA] 569 (formerly referred to as the Content Type[MIME]) called 570 `text/html'. The following is to be registered with [IANA]. 572 Media Type name 573 text 575 Media subtype 576 name 577 html 579 Required 580 parameters 581 none 583 Optional 584 parameters 585 level, charset 587 Encoding 588 considerations 589 any encoding is allowed 591 Security 592 considerations 593 see 3.3, "Security Considerations" 595 The optional parameters are defined as follows: 597 Level 598 The level parameter specifies the feature set used 599 in the document. The level is an integer number, 600 implying that any features of same or lower level 601 may be present in the document. Level 1 is all 602 features defined in this specification except 603 those that require the