6/29/2021
`
`RFC 1866
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`indistinctly from non-nested elements:
`
`plain <B>bold <I>italic</I></B> may be rendered
`the same as
`plain <B>bold </B><I>italic</I>
`
`5.7.1. Idiomatic Elements
`
`Phrases may be marked up to indicate certain idioms.
`-
`
`User agents may support the <DFN> element, not included in
`NOTE
`as it has been deployed to some extent. It is
`this specification,
`used to indicate the defining instance of a term, and it is
`typically rendered in italic or bold italic.
`
`5.7.1.1. Citation: CITE
`
`The <CITE> element is used to indicate the title of a book or
`other citation. It is typically rendered as italics. For example:
`
`He
`
`just couldn't get enough of <cite>The Grapes of Wrath</cite>.
`
`5.7.1.2. Code: CODE
`
`The <CODE> element indicates an
`example of code, typically
`rendered in a
`mono-spaced font. The <CODE> element is intended for
`short words or
`the <PRE> block structuring
`phrases of code;
`PRE") is more
`element (5.5.2, "Preformatted Text:
`appropriate
`For
`for multiple-line listings.
`example:
`
`The expression <code>x += 1</code>
`= x +
`is short for <code>x
`1</code>.
`
`5.7.1.3.
`
`Emphasis:
`
`EM
`
`The <EM> element indicates an
`emphasized phrase, typically
`rendered as italics. For example:
`
`A
`
`singular subject <em>always</em> takes a
`
`singular verb.
`
`5.7.1.4. Keyboard:
`
`KBD
`
`a user, typically
`The <KBD> element indicates text typed by
`rendered in a
`mono-spaced font. This is commonly used in
`instruction manuals. For example:
`
`Enter <kbd>FIND IT</kbd> to search the database.
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 31]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 31 of 77
`
`31/77
`
`Exhibit 1017
`Page 31 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`5.7.1.5. Sample: SAMP
`
`The <SAMP> element indicates a sequence of literal characters,
`typically rendered in a
`mono-spaced font. For example:
`
`The only word containing the letters <samp>mt</samp> is dreamt.
`
`5.7.1.6. Strong Emphasis: STRONG
`
`The <STRONG> element indicates strong emphasis, typically rendered
`in bold. For
`example:
`
`<strong>STOP</strong>,
`
`or I'll say "<strong>STOP</strong>" again!
`
`5.7.1.7. Variable: VAR
`
`The <VAR> element indicates a
`placeholder variable, typically
`rendered as italic. For example:
`
`Type <SAMP>html-check <VAR>file</VAR> | more</SAMP>
`errors.
`to check <VAR>file</VAR> for markup
`
`5.7.2.
`
`Typographic Elements
`
`Typographic elements are used to specify the format of marked
`text.
`
`Typical renderings for idiomatic elements may vary between user
`--
`agents. If a
`specific rendering is necessary
`for example, when
`referring to a--
`specific text attribute as in "The italic parts
`are
`
`a
`typographic element can be used to ensure that the
`mandatory"
`intended typography is used where possible.
`-
`
`some
`typographic elements not
`User agents may support
`NOTE
`as
`they have been deployed to some
`included in this specification,
`extent. The <STRIKE> element indicates horizontal line through the
`characters, and the <U> element indicates an underline.
`
`5.7.2.1. Bold: B
`
`The <B> element indicates bold text. Where bold typography is
`an alternative representation may be used.
`unavailable,
`
`5.7.2.2. Italic: I
`
`The <I> element indicates italic text. Where italic typography is
`an alternative representation may be used.
`unavailable,
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 32]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 32 of 77
`
`32/77
`
`Exhibit 1017
`Page 32 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`5.7.2.3. Teletype:
`
`TT
`
`The <TT> element indicates teletype (monospaced )text. Where a
`an alternative representation may be
`teletype font is unavailable,
`used.
`
`5.7.3. Anchor: A
`
`The <A> element indicates a
`hyperlink anchor (see 7, "Hyperlinks").
`At least one of the NAME and HREF attributes should be present.
`Attributes of the <A> element:
`
`HREF
`
`NAME
`
`TITLE
`
`REL
`
`REV
`
`gives the URI of the head anchor of a
`
`hyperlink.
`
`gives the name of the anchor, and makes it available as
`a head of a
`hyperlink.
`
`a title for the destination resource
`suggests
`advisory only. The TITLE attribute may be used:
`*
`
`--
`
`for display prior to
`accessing the destination
`as a
`margin note or ona
`resource, for example,
`or
`small box while the mouse is over the anchor,
`while the document is being loaded;
`*
`title, such as
`for resources that do not include a
`graphics, plain text and Gopher menus, for use as a
`window title.
`
`The REL attribute gives the relationship(s) described by
`the hyperlink. The value is a
`whitespace separated list
`names. The semantics of link
`of relationship
`are not specified in this document.
`relationships
`
`same as the REL attribute, but the semantics of the
`are in the reverse direction. A link from A
`relationship
`to B with REL="X" expresses the same
`as a
`relationship
`link from B to A with REV="X". An anchor may have both
`REL and REV attributes.
`
`a
`more
`persistent identifier for
`preferred,
`specifies
`the head anchor of the hyperlink. The syntax and
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 33]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 33 of 77
`
`33/77
`
`Exhibit 1017
`Page 33 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`METHODS
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`semantics of the URN attribute are not yet specified.
`
`specifies methods to be used in accessing the
`as a
`whitespace-separated list of names.
`destination,
`names is a function of the scheme
`The set of applicable
`in the HREF attribute. For similar reasons as
`of the URI
`for the TITLE attribute, it may be useful to include the
`information in advance in the link. For example,
`the
`HTML user
`agent may chose a different rendering
`as a
`function of the methods allowed; for example, something
`a different icon.
`that is searchable may get
`
`5.8. Line Break: BR
`
`a line break between words
`The <BR> element specifies
`For example:
`"Characters, Words, and Paragraphs").
`
`(see 6,
`
`<P> Pease porridge hot<BR>
`Pease
`porridge cold<BR>
`Pease porridge in the pot<BR>
`Nine days old.
`
`5.9. Horizontal Rule: HR
`
`The <HR> element is a divider between sections of text; typically
`full width horizontal rule or
`For
`equivalent graphic.
`example:
`
`a
`
`<HR>
`<ADDRESS>February 8, 1995, CERN</ADDRESS>
`</BODY>
`
`5.10.
`
`Image:
`
`IMG
`
`or icon via a
`The <IMG> element refers to an
`hyperlink (see
`image
`7.3, "Simultaneous Presentation of Image Resources").
`
`agents may process the value of the ALT attribute as an
`HTML user
`resource indicated by the SRC
`alternative to processing the image
`attribute.
`
`-
`
`can process graphics linked via
`Some HTML user
`NOTE
`agents
`anchors, but not <IMG> graphics. If a
`graphic is essential, it
`should be referenced from an <A> element rather than an <IMG>
`then the <IMG> element
`element. If the graphic is not essential,
`is appropriate.
`
`Attributes of the <IMG> element:
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 34]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 34 of 77
`
`34/77
`
`Exhibit 1017
`Page 34 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`ALIGN
`
`ALT
`
`ISMAP
`
`SRC
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`alignment of the image with respect to the text
`baseline.
`
`*
`~TOP' specifies that the top of the image aligns
`with the tallest item on the line containing the
`image.
`
`*
`
`~MIDDLE' specifies that the center of the image
`aligns with the baseline of the line containing the
`image.
`
`*
`
`~BOTTOM' specifies that the bottom of the image
`aligns with the baseline of the line containing the
`image.
`
`text to use in place of the referenced image resource,
`for example due to processing constraints or user
`preference.
`
`indicates an
`
`image map (see 7.6, "Image Maps").
`
`specifies the URI of the image
`-
`
`resource.
`
`In
`NOTE
`the media types of image
`practice,
`resources are limited to a few raster graphic
`formats: typically ~image/gif', ~image/jpeg'.
`particular, ~text/html" resources are not
`resources.
`intended to be used as
`image
`
`In
`
`Examples of use:
`
`<IMG
`SRC="triangle.xbm" ALT="Warning:">
`to read these instructions.
`
`Be sure
`
`<a
`href="http://machine/htbin/imagemap/sample">
`<IMG SRC="Sample.xbm" ISMAP>
`</a>
`
`6. Characters, Words, and Paragraphs
`
`agent should present the body of an HTML document as a
`An HTML user
`collection of typeset paragraphs and preformatted text. Except for
`preformatted elements (<PRE>, <XMP>, <LISTING>, <TEXTAREA>), each
`as a
`block structuring element is regarded
`paragraph by taking the
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 35]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 35 of 77
`
`35/77
`
`Exhibit 1017
`Page 35 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`data characters in its content and the content of its descendant
`elements, concatenating them, and splitting the result into words,
`or record end characters (and perhaps hyphen
`separated by space,
`tab,
`as a
`characters). The sequence of words is typeset
`paragraph by
`breaking it into lines.
`
`6.1. The HTML Document Character Set
`
`The document character set specified in 9.5,
`"SGML Declaration for
`HTML" must be supported by HTML user
`agents. It includes the graphic
`No. 1, or
`characters of Latin Alphabet
`simply Latin-1. Latin-1
`comprises 191 graphic characters,
`including the alphabets of most
`Western European languages.
`-
`
`NOTE
`Use of the non-breaking space and soft hyphen indicator
`characters is discouraged because support for them is not widely
`deployed.
`-
`
`a
`NOTE
`To support non-western writing systems,
`larger character
`repertoire will be specified in a future version of HTML. The
`or some subset that
`document character set will be [ISO-10646],
`in particular, all numeric character
`agrees with [ISO-10646];
`references must use code positions assigned by [ISO-10646].
`
`the use of control characters is limited in
`In SGML applications,
`over
`order to maximize the chance of successful interchange
`In the HTML document
`heterogeneous networks and operating systems.
`only three control characters are allowed: Horizontal
`character set
`Tab, Carriage Return, and Line Feed (code positions 9, 13, and 10).
`
`The HTML DTD references the Added Latin 1
`to allow
`entity set,
`mnemonic representation of selected Latin 1 characters using only the
`widely supported ASCII character repertoire. For example:
`
`Kurt G&ouml;del
`
`was a famous logician and mathematician.
`
`"ISO Latin 1 Character Entity Set" for a table of the
`See 9.7.2,
`"The HTML Coded Character Set" for
`"Added Latin 1" entities, and 13,
`a table of the code positions of [ISO 8859-1] and the control
`characters in the HTML document character set.
`
`Hyperlinks
`
`general purpose elements such as
`In addition to
`paragraphs and lists,
`An HTML user
`HTML documents can express hyperlinks.
`agent allows the
`user to navigate these hyperlinks.
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 36]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 36 of 77
`
`36/77
`
`Exhibit 1017
`Page 36 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`hyperlink is a
`A
`relationship between two anchors, called the head
`an
`and the tail of the hyperlink[DEXTER]. Anchors are identified by
`anchor address: an absolute Uniform Resource Identifier (URI),
`a '#' and a sequence of characters called a
`optionally followed by
`fragment identifier. For example:
`
`http: //www.w3.org/hypertext/www/TheProject. html
`http: //www.w3.org/hypertext/www/TheProject.html#z31
`
`the URI refers to a resource; it may be used in
`In an anchor address,
`a
`variety of information retrieval protocols to obtain an
`entity that
`represents the resource, such as an HTML document. The fragment
`identifier, if present, refers to some view on, or
`portion of the
`resource.
`
`Each of the following markup constructs indicates the tail anchor of
`a
`or set of hyperlinks:
`hyperlink
`
`*
`
`*
`
`*
`
`*
`
`*
`
`*
`
`<A> elements with HREF present.
`
`<LINK> elements.
`
`<IMG> elements.
`
`<INPUT> elements with the SRC attribute present.
`
`<ISINDEX> elements.
`
`<FORM> elements with ~METHOD=GET'.
`
`These markup constructs refer to head anchors by
`or a
`absolute or
`relative,
`fragment identifier,
`
`a URI, either
`or both.
`
`In the case of a relative URI,
`the absolute URI
`in the address of the
`head anchor is the result of combining the relative URI with a base
`absolute URI as in [RELURL]. The base document is taken from the
`document's <BASE> element, if present; else, it is determined as in
`[RELURL].
`
`7.1. Accessing Resources
`
`Once the address of the head anchor is determined,
`obtain a
`representation of the resource.
`
`the user
`
`agent may
`
`For example, if the base URI is ~http://host/x/y.html' and the
`document contains:
`
`<img src="../icons/abc.gif">
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 37]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 37 of 77
`
`37/77
`
`Exhibit 1017
`Page 37 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`uses the URI ~http://host/icons/abc.gif’ to
`then the user
`agent
`access the resource, as in [URL]..
`
`7.2. Activation of Hyperlinks
`
`agent allows the user to navigate the content of the
`An HTML user
`<A>
`document and request activation of hyperlinks denoted by
`elements. HTML user
`agents should also allow activation of <LINK>
`element hyperlinks.
`
`agent obtains a
`the user
`To activate a
`representation of the
`link,
`resource identified in the address of the head anchor. If the
`representation is another HTML document, navigation may begin again
`with this new document.
`
`7.3. Simultaneous Presentation of Image Resources
`
`An HTML user
`agent may activate hyperlinks indicated by <IMG> and
`<INPUT> elements concurrently with processing the document; that is,
`image hyperlinks may be processed without explicit request by the
`user.
`resources should be embedded in the presentation at the
`Image
`point of the tail anchor, that is the <IMG> or <INPUT> element.
`
`user
`<LINK> hyperlinks may also be processed without explicit
`request; for example, style sheet resources may be processed before
`or
`during the processing of the document.
`
`7.4. Fragment Identifiers
`
`a ~#' character in a
`hypertext address
`Any characters following
`an address of the
`constitute a
`In
`fragment identifier.
`particular,
`form ~#fragment' refers to an anchor in the same document.
`
`on the media type of the
`The meaning of fragment identifiers depends
`representation of the anchor's resource. For ~text/html'
`representations, it refers to the <A> element with a NAME attribute
`whose value is the same as the fragment identifier.
`The matching is
`one such element.
`case sensitive. The document should have exactly
`The user
`agent should indicate the anchor element, for example by
`to and/or highlighting the phrase.
`
`scrolling
`
`For example, if the base URI is ~http://host/x/y.html' and the user
`activated the link denoted by the following markup:
`
`<p> See: <a
`href="app1.html#bananas">appendix 1</a>
`for more detail on bananas.
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 38]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 38 of 77
`
`38/77
`
`Exhibit 1017
`Page 38 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`accesses the resource identified by
`Then the user
`agent
`~http://host/x/app1.htm1l'. Assuming the resource is represented using
`the user
`agent must locate the <A>
`the ~text/html' media type,
`element whose NAME attribute is ~bananas' and begin navigation there.
`
`7.5. Queries and Indexes
`
`a set of hyperlinks. The user can
`The <ISINDEX> element represents
`choose from the set by providing keywords to the user
`The
`agent.
`user
`agent computes the head URI by appending ~?' and the keywords to
`are
`the base URI. The keywords
`escaped according to [URL] and joined
`example, if a document contains:
`by ~+'. For
`
`<BASE
`HREF="http://host/index">
`<ISINDEX>
`
`and the user
`provides the keywords ~apple' and ~berry',
`user
`agent must access the resource
`“http://host/index?apple+berry'.
`
`then the
`
`<FORM> elements with ~METHOD=GET' also represent sets of
`See 8.2.2, "Query Forms: METHOD=GET" for details.
`hyperlinks.
`
`7.6.
`
`Image Maps
`
`on an <IMG> element,
`the <IMG>
`If the ISMAP attribute is present
`element must be contained in an <A> element with an HREF
`present.
`a set of hyperlinks. The user can choose
`This construct represents
`a
`pixel of the image. The user
`from the set by choosing
`agent
`computes the head URI by appending ~?" and the x and y coordinates of
`example, if a
`given in the <A> element.
`For
`the pixel to the URI
`document contains:
`
`<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
`<head><title>ImageMap Example</title>
`<BASE HREF="http://host/index"></head>
`<body>
`<p> Choose any of these icons:<br>
`<a
`href="/cgi-bin/imagemap"><img ismap src="icons.gif"></a>
`
`and the user chooses the upper-leftmost pixel,
`hyperlink is the one with the URI
`“http://host/cgi-bin/imagemap?@,Q'.
`
`the chosen
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 39]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 39 of 77
`
`39/77
`
`Exhibit 1017
`Page 39 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`8. Forms
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`template for a form data set and an associated
`A form is a
`method and action URI. A form data set is a sequence of
`on the NAME
`name/value pair fields. The names are
`specified
`attributes of form input elements, and the values are
`given
`initial values by various forms of markup and edited by the
`user. The resulting form data set is used to access an
`information service as a function of the action and method.
`
`Forms elements can be mixed in with document structuring
`a <PRE> element may contain a <FORM>
`elements. For
`example,
`or a <FORM> element may contain lists which contain
`element,
`<INPUT> elements. This gives considerable flexibility in
`designing the layout of forms.
`
`Form processing is a level 2 feature.
`
`8.1. Form Elements
`
`8.1.1. Form: FORM
`
`The <FORM> element contains a sequence of input elements, along
`with document structuring elements. The attributes are:
`
`ACTION
`
`METHOD
`
`ENCTYPE
`
`specifies the action URI for the form. The action URI of
`a form defaults to the base URI of the document (see 7,
`"Hyperlinks").
`
`selects a method of accessing the action URI. The set of
`applicable methods is a function of the scheme of the
`action URI of the form. See 8.2.2, "Query Forms:
`"Forms with Side-Effects:
`METHOD=GET" and 8.2.3,
`METHOD=POST".
`
`specifies the media type used to encode the name/value
`in case the protocol does not
`pairs for transport,
`a format. See 8.2.1,
`"The form-urlencoded
`itself impose
`Media Type".
`
`8.1.2. Input Field:
`
`INPUT
`
`a field for user
`input. The TYPE
`The <INPUT> element represents
`attribute discriminates between several variations of fields.
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 40]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 40 of 77
`
`40/77
`
`Exhibit 1017
`Page 40 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`The <INPUT> element has a number of attributes. The set of applicable
`on the value of the TYPE attribute.
`attributes depends
`
`8.1.2.1. Text Field:
`
`INPUT TYPE=TEXT
`
`a
`The default value of the TYPE attribute is ~TEXT',
`indicating
`(Use the <TEXTAREA> element for multi-
`single line text entry field.
`line text
`fields.)
`
`Required attributes are:
`
`NAME
`
`name for the form field corresponding
`
`to this element.
`
`The optional attributes are:
`
`MAXLENGTH
`constrains the number of characters that can be entered
`into a text input field. If the value of MAXLENGTH is
`greater the the value of the SIZE attribute,
`the field
`should scroll appropriately. The default number of
`characters is unlimited.
`
`SIZE
`
`VALUE
`
`specifies the amount of display space allocated to this
`input field according to its type. The default depends
`on the user
`agent.
`
`The initial value of the field.
`
`For
`
`example:
`
`<p>Street Address: <input name=street><br>
`Postal City code: <input name=city size=16 maxlength=16><br>
`Zip Code: <input name=zip size=10 maxlength=10 value="99999-9999"><br>
`
`8.1.2.2. Password Field:
`
`INPUT TYPE=PASSWORD
`
`is a text field as
`An <INPUT> element with ~TYPE=PASSWORD'
`above,
`except that the value is obscured as it is entered.
`(see also: 10,
`"Security Considerations").
`
`For example:
`
`<p>Name: <input name=login> Password: <input type=password name=passwd>
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 41]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 41 of 77
`
`41/77
`
`Exhibit 1017
`Page 41 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`8.1.2.3. Check Box:
`
`INPUT TYPE=CHECKBOX
`
`An <INPUT> element with ~TYPE=CHECKBOX' represents
`A set of such elements with the same name
`represents
`choice field. Required attributes are:
`
`a boolean choice.
`an
`
`n-of-many
`
`NAME
`
`VALUE
`
`name for the form field corresponding to this
`symbolic
`element or group of elements.
`
`The portion of the value of the field contributed by
`this element.
`
`Optional attributes are:
`
`CHECKED
`
`indicates that the initial state is on.
`
`For example:
`
`<p>What flavors do you like?
`<input type=checkbox name=flavor value=vanilla>Vanilla<br>
`<input type=checkbox name=flavor value=strawberry>Strawberry<br>
`<input type=checkbox name=flavor value=chocolate checked>Chocolate<br>
`
`8.1.2.4. Radio Button:
`
`INPUT TYPE=RADIO
`
`An <INPUT> element with ~TYPE=RADIO' represents
`set of such elements with the same name
`represents
`field. The NAME and VALUE attributes are
`required
`Optional attributes are:
`
`a boolean choice. A
`a
`1-of-many choice
`as for check boxes.
`
`CHECKED
`
`indicates that the initial state is on.
`one of the radio buttons in a set is checked.
`At all times, exactly
`If none of the <INPUT> elements of a set of radio buttons specifies
`then the user
`agent must check the first radio button of
`~CHECKED',
`the set initially.
`
`For example:
`
`<p>Which is your favorite?
`<input type=radio name=flavor value=vanilla>Vanilla<br>
`<input type=radio name=flavor value=strawberry>Strawberry<br>
`<input type=radio name=flavor value=chocolate>Chocolate<br>
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 42]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 42 of 77
`
`42/77
`
`Exhibit 1017
`Page 42 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`8.1.2.5.
`
`Image Pixel:
`
`INPUT TYPE=IMAGE
`
`an
`resource to
`An <INPUT> element with ~TYPE=IMAGE' specifies
`image
`display, and allows input of two form fields: the x and y coordinate
`of a
`pixel chosen from the image. The names of the fields are the
`name of the field with ~.x' and ~.y' appended.
`~TYPE=IMAGE'
`implies
`~TYPE=SUBMIT' processing; that is, when a
`pixel is chosen,
`the form
`as a whole is submitted.
`
`as for other input fields. The SRC
`The NAME attribute is required
`as for the <IMG>
`attribute is required and the ALIGN is optional
`element (see 5.10, "Image:
`IMG").
`
`For
`
`example:
`
`a
`
`on the map:
`point
`<p>Choose
`<input type=image name=point src="map.gif">
`
`8.1.2.6. Hidden Field:
`
`INPUT TYPE=HIDDEN
`
`a hidden field.The
`An <INPUT> element with ~TYPE=HIDDEN' represents
`user does not interact with this field;
`the VALUE attribute
`instead,
`specifies the value of the field. The NAME and VALUE attributes are
`required.
`
`For example:
`
`<input type=hidden name=context value="12k3j412k3j412k3j41k23">
`
`8.1.2.7. Submit Button:
`
`INPUT TYPE=SUBMIT
`
`an
`An <INPUT> element with ~TYPE=SUBMIT' represents
`input option,
`a
`button, that instructs the user
`agent to submit the form.
`typically
`Optional attributes are:
`
`NAME
`
`VALUE
`
`indicates that this element contributes a form field
`whose value is given by the VALUE attribute. If the NAME
`attribute is not present, this element does not
`contribute a form field.
`
`indicates a label for the input (button).
`
`You may submit this request internally:
`<input type=submit name=recipient value=internal><br>
`or to the external world:
`<input type=submit name=recipient value=world>
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 43]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 43 of 77
`
`43/77
`
`Exhibit 1017
`Page 43 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`8.1.2.8. Reset Button:
`
`INPUT TYPE=RESET
`
`an
`An <INPUT> element with ~TYPE=RESET' represents
`input option,
`a
`button, that instructs the user
`agent to reset the form's
`typically
`fields to their initial states. The VALUE attribute, if present,
`indicates a label for the input (button).
`
`When you are
`finished, you may submit this request:
`<input type=submit><br>
`You may clear the form and start over at any time: <input type=reset>
`
`8.1.3. Selection: SELECT
`
`The <SELECT> element constrains the form field to an enumerated list
`of values. The values are
`given in <OPTION> elements. Attributes
`are:
`
`MULTIPLE
`
`NAME
`
`SIZE
`
`indicates that more than one
`the value.
`
`option may be included in
`
`specifies the name of the form field.
`
`specifies the number of visible items. Select fields of
`size one are
`typically pop-down menus, whereas select
`fields with size greater than one are
`typically lists.
`
`For example:
`
`<SELECT NAME="flavor">
`<OPTION>Vanilla
`
`<OPTION>Strawberry
`<OPTION value="RumRasin">Rum and Raisin
`<OPTION selected>Peach and Orange
`</SELECT>
`
`The initial state has the first option selected, unless a SELECTED
`on any of the <OPTION> elements.
`attribute is present
`
`8.1.3.1. Option: OPTION
`
`occur within a Select element. It
`The Option element can
`only
`one
`choice, and has the following attributes:
`represents
`
`SELECTED
`
`Indicates that this option is initially selected.
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 44]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 44 of 77
`
`44/77
`
`Exhibit 1017
`Page 44 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`VALUE
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`indicates the value to be returned if this option is
`chosen. The field value defaults to the content of the
`<OPTION> element.
`
`The content of the <OPTION> element is presented to the user to
`represent the option. It is used as a returned value if the VALUE
`attribute is not present.
`
`8.1.4. Text Area: TEXTAREA
`
`The <TEXTAREA> element represents
`Attributes are:
`
`a multi-line text field.
`
`COLS
`
`NAME
`
`ROWS
`
`the number of visible columns to display for the text
`in characters.
`area,
`
`Specifies the name of the form field.
`
`The number of visible rows to display for the text area,
`in characters.
`
`For example:
`
`<TEXTAREA NAME="address" ROWS=6 COLS=64>
`HaL Computer Systems
`1315 Dell Avenue
`Campbell, California 95008
`</TEXTAREA>
`
`The content of the <TEXTAREA> element is the field's initial value.
`
`the ROWS and COLS attributes determine the visible
`Typically,
`dimension of the field in characters. The field is typically rendered
`in a fixed-width font. HTML user
`agents should allow text to extend
`as needed.
`beyond these limits by scrolling
`
`8.2. Form Submission
`
`a form by presenting the
`An HTML user
`agent begins processing
`document with the fields in their initial state. The user is allowed
`to modify the fields, constrained by the field type etc. When the
`a submit
`user indicates that the form should be submitted (using
`button or
`the form data set is processed according to
`image input),
`its method, action URI and enctype.
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 45]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 45 of 77
`
`45/77
`
`Exhibit 1017
`Page 45 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`one
`single-line text input field in a
`the
`When there is only
`form,
`user
`agent should accept Enter in that field as a
`request to submit
`the form.
`
`8.2.1. The form-urlencoded Media Type
`
`The default encoding for all forms is ~application/x-www-form-
`urlencoded'. A form data set is represented in this media type
`follows:
`
`as
`
`1. The form field names and values are
`escaped: space
`characters are
`replaced by ~+', and then reserved characters
`are
`as per [URL]; that is, non-alphanumeric
`escaped
`characters are
`a
`percent sign and two
`replaced by ~%HH',
`hexadecimal digits representing the ASCII code of the
`as in multi-line text field values,
`character. Line breaks,
`are
`as CR LF pairs, i.e. ~%@D%OA'.
`represented
`
`2. The fields are listed in the order they appear in the
`~=' and
`document with the name
`separated from the value by
`the pairs separated from each other by ~&'. Fields with null
`In
`values may be omitted.
`particular, unselected radio
`buttons and checkboxes should not appear in the encoded
`data, but hidden fields with VALUE attributes present
`should.
`
`-
`
`The URI from a query form submission can be
`NOTE
`used in a normal anchor style hyperlink.
`the use of the ~&' character to
`Unfortunately,
`separate form fields interacts with its use in SGML
`attribute values as an
`entity reference delimiter.
`For
`the URI
`must be
`example,
`~“http://host/?x=1&y=2'
`or ~<a
`written ~<a href="http://host/?x=18&#38;y=2"'
`href="http://host/?x=1&amp; y=2">'.
`
`HTTP server
`
`implementors, and in particular, CGI
`are
`encouraged to support the use of
`implementors
`to save users the trouble of
`in place of ~&'
`~;'
`escaping ~&' characters this way.
`
`8.2.2. Query Forms: METHOD=GET
`
`If the processing of a form is idempotent (i.e. it has no
`lasting
`observable effect on the state of the
`then the form method
`world),
`should be ~GET'. Many database searches have no visible side-effects
`and make ideal applications of query forms.
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 46]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 46 of 77
`
`46/77
`
`Exhibit 1017
`Page 46 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`To process a form whose action URL is an HTTP URL and whose method is
`the user
`a ~?'
`agent starts with the action URI and appends
`~GET',
`in ~“application/x-www-form-urlencoded'
`and the form data set,
`format
`as above. The user
`as
`agent then traverses the link to this URI just
`if it were an anchor (see 7.2, "Activation of Hyperlinks").
`-
`
`encoding may result in very long URIs, which cause
`The URL
`NOTE
`some historical HTTP server
`implementations to exhibit defective
`behavior. As a
`some HTML forms are written using
`result,
`~METHOD=POST' even
`though the form submission has no side-effects.
`
`8.2.3. Forms with Side-Effects: METHOD=POST
`
`If the service associated with the processing of a form has side
`subscription to a
`effects (for example, modification of a database or
`the method should be ~POST'.
`service),
`
`To process a form whose action URL is an HTTP URL and whose method is
`the user
`agent conducts an HTTP POST transaction using the
`~POST',
`action URI, and a message body of type ~application/x-www-form-
`format as above. The user
`urlencoded'
`agent should display the
`as it would display the
`response from the HTTP POST interaction just
`response from an HTTP GET above.
`
`8.2.4. Example Form Submission: Questionnaire Form
`
`Consider the following document:
`
`<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
`<title>Sample of HTML Form Submission</title>
`<H1i>Sample Questionnaire</H1>
`<P>Please fill out this questionnaire:
`<FORM METHOD="POST" ACTION="http: //www.w3.org/sample">
`<P>Your name: <INPUT NAME="name" size="48">
`<P>Male <INPUT
`NAME="gender" TYPE=RADIO VALUE="male">
`<P>Female <INPUT
`TYPE=RADIO VALUE="female">
`NAME="gender"
`in family: <INPUT NAME="family" TYPE=text>
`<P>Number
`<P>Cities in which you maintain a residence:
`<UL>
`<LI>Kent <INPUT NAME="city" TYPE=checkbox VALUE="kent">
`<LI>Miami <INPUT
`NAME="city" TYPE=checkbox VALUE="miami">
`<LI>Other <TEXTAREA NAME="other" cols=48 rows=4></textarea>
`</UL>
`Nickname: <INPUT NAME="nickname" SIZE="42">
`<P>Thank you for responding to this questionnaire.
`<P><INPUT TYPE=SUBMIT> <INPUT TYPE=RESET>
`
`</FORM>
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 47]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 47 of 77
`
`A7IT7
`
`Exhibit 1017
`Page 47 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`The initial state of the form data set is:
`
`name
`
`gender
`
`"male"
`
`family
`
`other
`
`nickname
`
`Note that the radio input has an initial value, while the
`checkbox has none.
`
`The user
`might edit the fields and request that the form be
`submitted. At that point, suppose the values are:
`
`name
`
`"John Doe"
`
`gender
`
`"male"
`
`family
`
`wo"
`
`"kent"
`
`"miami"
`
`city
`
`city
`
`other
`
`"abc\ndefk"
`
`nickname
`
`"7J&D"
`
`agent then conducts an HTTP POST transaction using the URI
`The user
`~http://www.w3.org/sample'. The message body would be (ignore the
`line break):
`
`Berners-Lee & Connolly
`
`Standards Track
`
`[Page 48]
`
`https://datatracker.ietf.org/doc/html/rfc1866
`Exhibit 1017
`Page 48 of 77
`
`48/77
`
`Exhibit 1017
`Page 48 of 77
`
`

`

`6/29/2021
`
`RFC 1866
`
`Hypertext Markup Language
`
`ric1866
`
`-
`
`2.0
`
`November 1995
`
`name=John+Doe&gender=male&family=5&city=kent&city=miami&
`other=abc%@D%eAde F&nickname=J%26D
`
`