idnits 2.17.1
draft-ietf-html-spec-04.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-18) 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 59 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.)
** The document seems to lack separate sections for Informative/Normative
References. All references will be assumed normative when checking for
downward references.
** There are 19 instances of too long lines in the document, the longest
one being 18 characters in excess of 72.
== There are 1 instance of lines with non-RFC2606-compliant FQDNs in the
document.
== There are 2 instances of lines with non-RFC6890-compliant IPv4 addresses
in the document. If these are example addresses, they should be changed.
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 (June 16, 1995) is 10534 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*
532 |
533 \-"Some text. "
534 |
535 \-EM
536 | |
537 | \-
538 | |
539 | \-"*wow*"
540 | |
541 | \-
542 |
543 \-' 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: 'ISO 8859-1' is mentioned on line 1711, but not
defined
== Unused Reference: 'URI' is defined on line 3279, but no explicit
reference was found in the text
== Unused Reference: 'HTTP' is defined on line 3292, but no explicit
reference was found in the text
== Unused Reference: 'GOLD90' is defined on line 3310, but no explicit
reference was found in the text
== Unused Reference: 'SQ91' is defined on line 3329, but no explicit
reference was found in the text
** Downref: Normative reference to an Informational RFC: RFC 1630 (ref.
'URI')
** Obsolete normative reference: RFC 1738 (ref. 'URL') (Obsoleted by RFC
4248, RFC 4266)
-- Possible downref: Non-RFC (?) normative reference: ref. 'HTTP'
** Obsolete normative reference: RFC 1521 (ref. 'MIME') (Obsoleted by RFC
2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049)
-- Possible downref: Non-RFC (?) normative reference: ref. 'RELURL'
-- Possible downref: Non-RFC (?) normative reference: ref. 'GOLD90'
-- Possible downref: Non-RFC (?) normative reference: ref. 'DEXTER'
** Obsolete normative reference: RFC 1590 (ref. 'IMEDIA') (Obsoleted by RFC
2045, RFC 2046, RFC 2047, RFC 2048, RFC 2049)
** Obsolete normative reference: RFC 1700 (ref. 'IANA') (Obsoleted by RFC
3232)
-- Possible downref: Non-RFC (?) normative reference: ref. 'SQ91'
-- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-646'
-- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-10646'
-- Possible downref: Non-RFC (?) normative reference: ref. 'ISO-8859-1'
-- Possible downref: Non-RFC (?) normative reference: ref. 'SGML'
Summary: 14 errors (**), 0 flaws (~~), 9 warnings (==), 12 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 HTML Working Group T. Berners-Lee
3 INTERNET-DRAFT MIT/W3C
4
This is a Heading
624 Some elements only have a start-tag without an end-tag. For
625 example, to create a line break, you use the `
' tag.
626 Additionally, the end tags of some other elements, such as
627 Paragraph (`
', `', and `' 652 are equivalent, whereas `&' is different from `&'. 654 In a start-tag, the element name must immediately follow the tag 655 open delimiter `<'. 657 3.2.4. Attributes 659 In a start-tag, white space and attributes are allowed between 660 the element name and the closing delimiter. An attribute 661 specification typically consists of an attribute name, an equal 662 sign, and a value, though some attribute specifications may be 663 just a name token. White space is allowed around the equal sign. 665 The value of the attribute may be either: 667 * A string literal, delimited by single quotes or double 668 quotes and not containing any occurrences of the delimiting 669 character. 671 NOTE - Some historical implementations consider any 672 occurrence of the `>' character to signal the end of 673 a tag. For compatibility with such implementations, 674 when `>' appears in an attribute value, it should be 675 represented with a numeric character reference. For 676 example, `' should be 677 written `' or `'. 680 * A name token (a sequence of letters, digits, periods, or 681 hyphens). Name tokens are not case sensitive. 683 NOTE - Some historical implementations allow any 684 character except space or `>' in a name token. 686 In this example, is the element name, src is the attribute 687 name, and `http://host/dir/file.gif' is the attribute value: 689 691 A useful technique for computing an attribute value literal for 692 a given string is to replace each quote and white space 693 character by an entity reference or numeric character reference 694 as follows: 696 ENTITY NUMERIC 697 CHARACTER REFERENCE CHAR REF CHARACTER DESCRIPTION 698 --------- ---------- ----------- --------------------- 699 HT Tab 700 LF Line Feed 701 CR Carriage Return 702 SP Space 703 " " " Quotation mark 704 & & & Ampersand 706 For example: 708 710 The `NAMELEN' parameter in the SGML declaration (9.5, "SGML 711 Declaration for HTML") limits the length of an attribute value 712 to 1024 characters. 714 Attributes such as ISMAP and COMPACT may be written using a 715 minimized syntax (see 7.9.1.2 ``Omitted Attribute Name'' in 716 [SGML]). The markup: 718720 can be written using a minimized syntax: 722
724 NOTE - Some historical implementations only understand 725 the minimized syntax. 727 3.2.5. Comments 729 To include comments in an HTML document, use a comment 730 declaration. A comment declaration consists of `'. Each comment starts with 732 `--' and includes all text up to and including the next 733 occurrence of `--'. In a comment declaration, white space is 734 allowed after each comment, but not before the first comment. 735 The entire comment declaration is ignored. 737 NOTE - Some historical HTML implementations incorrectly 738 consider any `>' character to be the termination of a 739 comment. 741 For example: 743 744 745
HTML Comment Example 746 747 748 749 750 751753 3.3. HTML Public Text Identifiers 755 To identify information as an HTML document conforming to this 756 specification, each document should start with one of the 757 following document type declarations. 759 761 This document type declaration refers to the HTML DTD in 9.1, 762 "HTML DTD". 764 NOTE - If the body of a `text/html' message entity does 765 not begin with a document type declaration, an HTML user 766 agent should infer the above document type declaration. 768 770 This document type declaration also refers to the HTML DTD which 771 appears in 9.1, "HTML DTD". 773 775 This document type declaration refers to the level 1 HTML DTD in 776 9.3, "Level 1 HTML DTD". Form elements must not occur in level 1 777 documents. 779 780 782 These two document type declarations refer to the HTML DTD in 783 9.2, "Strict HTML DTD" and 9.4, "Strict Level 1 HTML DTD". They 784 refer to the more structurally rigid definition of HTML. 786 HTML user agents may support other document types. In 787 particular, they may support other formal public identifiers, or 788 other document types altogether. They may support an internal 789 declaration subset with supplemental entity, element, and other 790 markup declarations. 792 3.4. Example HTML Document 794 795 796 797
798Structural Example 799 800First Header
801This is a paragraph in the example HTML file. Keep in mind 802 that the title does not appear in the document text, but that 803 the header (defined by H1) does.
804805
814- First item in an ordered list. 806
- Second item in an ordered list. 807
808
812- Note that lists can be nested; 809
- Whitespace may be used to assist in reading the 810 HTML source. 811
- Third item in an ordered list. 813
This is an additional paragraph. Technically, end tags are 815 not required for paragraphs, although they are allowed. You can 816 include character highlighting in a paragraph. This sentence 817 of the paragraph is emphasized. Note that the </P> 818 end tag has been omitted. 819
820 821 Be sure to read these bold instructions. 822 824 4. HTML as an Internet Media Type 826 An HTML user agent allows users to interact with resources which 827 have HTML representations. At a minimum, it must allow users to 828 examine and navigate the content of HTML level 1 documents. HTML 829 user agents should be able to preserve all formatting 830 distinctions represented in an HTML document, and be able to 831 simultaneously present resources referred to by IMG elements 832 (they may ignore some formatting distinctions or IMG resources 833 at the request of the user). Level 2 HTML user agents should 834 support form entry and submission. 836 4.1. text/html media type 838 This specification defines the Internet Media Type[IMEDIA] 839 (formerly referred to as the Content Type[MIME]) called 840 `text/html'. The following is to be registered with [IANA]. 842 Media Type name 843 text 845 Media subtype name 846 html 848 Required parameters 849 none 851 Optional parameters 852 level, charset 854 Encoding considerations 855 any encoding is allowed 857 Security considerations 858 see 10, "Security Considerations" 860 The optional parameters are defined as follows: 862 Level 863 The level parameter specifies the feature set used in 864 the document. The level is an integer number, implying 865 that any features of same or lower level may be present 866 in the document. Level 1 is all features defined in this 867 specification except those that require the