1 |
|
2 |
HTML Working Group T. Berners-Lee |
3 |
INTERNET-DRAFT MIT/W3C |
4 |
<draft-ietf-html-spec-05.txt> D. Connolly |
5 |
Expires: In six months August 8, 1995 |
6 |
|
7 |
|
8 |
Hypertext Markup Language - 2.0 |
9 |
|
10 |
|
11 |
Status of this Memo |
12 |
|
13 |
This document is an Internet-Draft. Internet-Drafts are working |
14 |
documents of the Internet Engineering Task Force (IETF), its areas, and |
15 |
its working groups. Note that other groups may also distribute working |
16 |
documents as Internet-Drafts. |
17 |
|
18 |
Internet-Drafts are draft documents valid for a maximum of six months |
19 |
and may be updated, replaced, or obsoleted by other documents at any |
20 |
time. It is inappropriate to use Internet-Drafts as reference material |
21 |
or to cite them other than as ``work in progress.'' |
22 |
|
23 |
To learn the current status of any Internet-Draft, please check the |
24 |
1id-abstracts.txt listing contained in the Internet-Drafts Shadow |
25 |
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), |
26 |
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or |
27 |
ftp.isi.edu (US West Coast). |
28 |
|
29 |
Distribution of this document is unlimited. Please send comments to the |
30 |
HTML working group (HTML-WG) of the Internet Engineering Task Force |
31 |
(IETF) at <html-wg@oclc.org>. Discussions of the group are archived at |
32 |
<URL:http://www.acl.lanl.gov/HTML_WG/archives.html>. |
33 |
|
34 |
|
35 |
ABSTRACT |
36 |
|
37 |
The Hypertext Markup Language (HTML) is a simple markup language |
38 |
used to create hypertext documents that are platform |
39 |
independent. HTML documents are SGML documents with generic |
40 |
semantics that are appropriate for representing information from |
41 |
a wide range of domains. HTML markup can represent hypertext |
42 |
news, mail, documentation, and hypermedia; menus of options; |
43 |
database query results; simple structured documents with |
44 |
in-lined graphics; and hypertext views of existing bodies of |
45 |
information. |
46 |
|
47 |
HTML has been in use by the World Wide Web (WWW) global |
48 |
information initiative since 1990. This specification roughly |
49 |
corresponds to the capabilities of HTML in common use prior to |
50 |
June 1994. HTML is an application of ISO Standard 8879:1986 |
51 |
Information Processing Text and Office Systems; Standard |
52 |
Generalized Markup Language (SGML). |
53 |
|
54 |
The `text/html' Internet Media Type (RFC 1590) and MIME Content |
55 |
Type (RFC 1521) is defined by this specification. |
56 |
|
57 |
|
58 |
|
59 |
Berners-Lee, Connolly [Page 1] |
60 |
|
61 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
62 |
|
63 |
CONTENTS |
64 |
|
65 |
|
66 |
1 Introduction .......................................... 3 |
67 |
1.1 Scope ................................................. 3 |
68 |
1.2 Conformance ........................................... 3 |
69 |
2 Terms ................................................. 5 |
70 |
3 HTML as an Application of SGML ........................ 9 |
71 |
3.1 SGML Documents ........................................ 9 |
72 |
3.2 HTML Lexical Syntax .................................. 11 |
73 |
3.3 HTML Public Text Identifiers ......................... 15 |
74 |
3.4 Example HTML Document ................................ 16 |
75 |
4 HTML as an Internet Media Type ....................... 16 |
76 |
4.1 text/html media type ................................. 16 |
77 |
4.2 HTML Document Representation ......................... 17 |
78 |
5 Document Structure ................................... 18 |
79 |
5.1 Document Element: HTML ............................... 19 |
80 |
5.2 Head: HEAD ........................................... 19 |
81 |
5.3 Body: BODY ........................................... 22 |
82 |
5.4 Headings: H1 ... H6 .................................. 22 |
83 |
5.5 Block Structuring Elements ........................... 23 |
84 |
5.6 List Elements ........................................ 25 |
85 |
5.7 Phrase Markup ........................................ 28 |
86 |
5.8 Line Break: BR ....................................... 31 |
87 |
5.9 Horizontal Rule: HR .................................. 31 |
88 |
5.10 Image: IMG ........................................... 31 |
89 |
6 Characters, Words, and Paragraphs .................... 33 |
90 |
6.1 The HTML Document Character Set ...................... 33 |
91 |
7 Hyperlinks ........................................... 34 |
92 |
7.1 Accessing Resources .................................. 34 |
93 |
7.2 Activation of Hyperlinks ............................. 35 |
94 |
7.3 Simultaneous Presentation of Image Resources ......... 35 |
95 |
7.4 Fragment Identifiers ................................. 36 |
96 |
7.5 Queries and Indexes .................................. 36 |
97 |
7.6 Image Maps ........................................... 37 |
98 |
8 Forms ................................................ 37 |
99 |
8.1 Form Elements ........................................ 37 |
100 |
8.2 Form Submission ...................................... 42 |
101 |
9 HTML Public Text ..................................... 45 |
102 |
9.1 HTML DTD ............................................. 46 |
103 |
9.2 Strict HTML DTD ...................................... 57 |
104 |
9.3 Level 1 HTML DTD ..................................... 57 |
105 |
9.4 Strict Level 1 HTML DTD .............................. 58 |
106 |
9.5 SGML Declaration for HTML ............................ 59 |
107 |
9.6 Sample SGML Open Entity Catalog for HTML ............. 61 |
108 |
9.7 Character Entity Sets ................................ 62 |
109 |
10 Security Considerations .............................. 64 |
110 |
11 References ........................................... 64 |
111 |
12 Acknowledgments ...................................... 66 |
112 |
12.1 Authors' Addresses ................................... 66 |
113 |
13 The HTML Coded Character Set ......................... 66 |
114 |
14 Proposed Entities .................................... 69 |
115 |
|
116 |
|
117 |
|
118 |
Berners-Lee, Connolly [Page 2] |
119 |
|
120 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
121 |
|
122 |
1. Introduction |
123 |
|
124 |
The HyperText Markup Language (HTML) is a simple data format |
125 |
used to create hypertext documents that are portable from one |
126 |
platform to another. HTML documents are SGML documents with |
127 |
generic semantics that are appropriate for representing |
128 |
information from a wide range of domains. |
129 |
|
130 |
As HTML is an application of SGML, this specification assumes a |
131 |
working knowledge of [SGML]. |
132 |
|
133 |
|
134 |
1.1. Scope |
135 |
|
136 |
HTML has been in use by the World-Wide Web (WWW) global |
137 |
information initiative since 1990. This specification |
138 |
corresponds to the capabilities of HTML in common use prior to |
139 |
June 1994 and referred to as ``HTML 2.0''. |
140 |
|
141 |
HTML is an application of ISO Standard 8879:1986 _Information |
142 |
Processing Text and Office Systems; Standard Generalized Markup |
143 |
Language_ (SGML). The HTML Document Type Definition (DTD) is a |
144 |
formal definition of the HTML syntax in terms of SGML. |
145 |
|
146 |
This specification also defines HTML as an Internet Media |
147 |
Type[IMEDIA] and MIME Content Type[MIME] called `text/html'. As |
148 |
such, it defines the semantics of the HTML syntax and how that |
149 |
syntax should be interpreted by user agents. |
150 |
|
151 |
|
152 |
1.2. Conformance |
153 |
|
154 |
This specification governs the syntax of HTML documents and |
155 |
aspects of the behavior of HTML user agents. |
156 |
|
157 |
|
158 |
1.2.1. Documents |
159 |
|
160 |
A document is a conforming HTML document if: |
161 |
|
162 |
* It is a conforming SGML document, and it conforms to the |
163 |
HTML DTD (see 9.1, "HTML DTD"). |
164 |
|
165 |
NOTE - There are a number of syntactic idioms that |
166 |
are not supported or are supported inconsistently in |
167 |
some historical user agent implementations. These |
168 |
idioms are identified in notes like this throughout |
169 |
this specification. |
170 |
|
171 |
* It conforms to the application conventions in this |
172 |
specification. For example, the value of the HREF attribute |
173 |
of the <A> element must conform to the URI syntax. |
174 |
|
175 |
* Its document character set includes [ISO-8859-1] and |
176 |
|
177 |
Berners-Lee, Connolly [Page 3] |
178 |
|
179 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
180 |
|
181 |
agrees with [ISO-10646]; that is, each code position listed |
182 |
in 13, "The HTML Coded Character Set" is included, and each |
183 |
code position in the document character set is mapped to the |
184 |
same character as [ISO-10646] designates for that code |
185 |
position. |
186 |
|
187 |
NOTE - The document character set is somewhat |
188 |
independent of the character encoding scheme used to |
189 |
represent a document. For example, the `ISO-2022-JP' |
190 |
character encoding scheme can be used for HTML |
191 |
documents, since its repertoire is a subset of the |
192 |
[ISO-10646] repertoire. The critical distinction is |
193 |
that numeric character references agree with |
194 |
[ISO-10646] regardless of how the document is |
195 |
encoded. |
196 |
|
197 |
|
198 |
1.2.2. Feature Test Entities |
199 |
|
200 |
The HTML DTD defines a standard HTML document type and several |
201 |
variations, by way of feature test entities. Feature test |
202 |
entities are declarations in the HTML DTD that control the |
203 |
inclusion or exclusion of portions of the DTD. |
204 |
|
205 |
HTML.Recommended |
206 |
Certain features of the language are necessary for |
207 |
compatibility with widespread usage, but they may |
208 |
compromise the structural integrity of a document. This |
209 |
feature test entity selects a more prescriptive document |
210 |
type definition that eliminates those features. It is |
211 |
set to `IGNORE' by default. |
212 |
|
213 |
For example, in order to preserve the structure of a |
214 |
document, an editing user agent may translate HTML |
215 |
documents to the recommended subset, or it may require |
216 |
that the documents be in the recommended subset for |
217 |
import. |
218 |
|
219 |
HTML.Deprecated |
220 |
Certain features of the language are necessary for |
221 |
compatibility with earlier versions of the |
222 |
specification, but they tend to be used and implemented |
223 |
inconsistently, and their use is deprecated. This |
224 |
feature test entity enables a document type definition |
225 |
that allows these features. It is set to `INCLUDE' by |
226 |
default. |
227 |
|
228 |
Documents generated by translation software or editing |
229 |
software should not contain deprecated idioms. |
230 |
|
231 |
|
232 |
1.2.3. User Agents |
233 |
|
234 |
An HTML user agent conforms to this specification if: |
235 |
|
236 |
Berners-Lee, Connolly [Page 4] |
237 |
|
238 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
239 |
|
240 |
|
241 |
* It parses the characters of an HTML document into data |
242 |
characters and markup according to [SGML]. |
243 |
|
244 |
NOTE - In the interest of robustness and |
245 |
extensibility, there are a number of widely deployed |
246 |
conventions for handling non-conforming documents. |
247 |
See 4.2.1, "Undeclared Markup Error Handling" for |
248 |
details. |
249 |
|
250 |
* It supports the `ISO-8859-1' character encoding scheme and |
251 |
processes each character in the ISO Latin Alphabet No. 1 as |
252 |
specified in 6.1, "The HTML Document Character Set". |
253 |
|
254 |
NOTE - To support non-western writing systems, HTML |
255 |
user agents are encouraged to support |
256 |
`ISO-10646-UCS-2' or similar character encoding |
257 |
schemes and as much of the character repertoire of |
258 |
[ISO-10646] as is practical. |
259 |
|
260 |
* It behaves identically for documents whose parsed token |
261 |
sequences are identical. |
262 |
|
263 |
For example, comments and the whitespace in tags disappear |
264 |
during tokenization, and hence they do not influence the |
265 |
behavior of conforming user agents. |
266 |
|
267 |
* It allows the user to traverse (or at least attempt to |
268 |
traverse, resources permitting) all hyperlinks from <A> |
269 |
elements in an HTML document. |
270 |
|
271 |
An HTML user agent is a level 2 user agent if, additionally: |
272 |
|
273 |
* It allows the user to express all form field values |
274 |
specified in an HTML document and to (attempt to) submit the |
275 |
values as requests to information services. |
276 |
|
277 |
|
278 |
2. Terms |
279 |
|
280 |
absolute URI |
281 |
a URI in absolute form; for example, as per [URL] |
282 |
|
283 |
anchor |
284 |
one of two ends of a hyperlink; typically, a phrase |
285 |
marked as an <A> element. |
286 |
|
287 |
base URI |
288 |
an absolute URI used in combination with a relative URI |
289 |
to determine another absolute URI. |
290 |
|
291 |
character |
292 |
An atom of information, for example a letter or a digit. |
293 |
Graphic characters have associated glyphs, where as |
294 |
|
295 |
Berners-Lee, Connolly [Page 5] |
296 |
|
297 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
298 |
|
299 |
control characters have associated processing semantics. |
300 |
|
301 |
character encoding |
302 |
scheme |
303 |
A function whose domain is the set of sequences of |
304 |
octets, and whose range is the set of sequences of |
305 |
characters from a character repertoire; that is, a |
306 |
sequence of octets and a character encoding scheme |
307 |
determines a sequence of characters. |
308 |
|
309 |
character repertoire |
310 |
A finite set of characters; e.g. the range of a coded |
311 |
character set. |
312 |
|
313 |
code position |
314 |
An integer. A coded character set and a code position |
315 |
from its domain determine a character. |
316 |
|
317 |
coded character set |
318 |
A function whose domain is a subset of the integers and |
319 |
whose range is a character repertoire. That is, for some |
320 |
set of integers (usually of the form {0, 1, 2, ..., N} |
321 |
), a coded character set and an integer in that set |
322 |
determine a character. Conversely, a character and a |
323 |
coded character set determine the character's code |
324 |
position (or, in rare cases, a few code positions). |
325 |
|
326 |
conforming HTML user |
327 |
agent |
328 |
A user agent that conforms to this specification in its |
329 |
processing of the Internet Media Type `text/html'. |
330 |
|
331 |
data character |
332 |
Characters other than markup, which make up the content |
333 |
of elements. |
334 |
|
335 |
document character set |
336 |
a coded character set whose range includes all |
337 |
characters used in a document. Every SGML document has |
338 |
exactly one document character set. Numeric character |
339 |
references are resolved via the document character set. |
340 |
|
341 |
DTD |
342 |
document type definition. Rules that apply SGML to the |
343 |
markup of documents of a particular type, including a |
344 |
set of element and entity declarations. [SGML] |
345 |
|
346 |
element |
347 |
A component of the hierarchical structure defined by a |
348 |
document type definition; it is identified in a document |
349 |
instance by descriptive markup, usually a start-tag and |
350 |
end-tag. [SGML] |
351 |
|
352 |
end-tag |
353 |
|
354 |
Berners-Lee, Connolly [Page 6] |
355 |
|
356 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
357 |
|
358 |
Descriptive markup that identifies the end of an |
359 |
element. [SGML] |
360 |
|
361 |
entity |
362 |
data with an associated notation or interpretation; for |
363 |
example, a sequence of octets associated with an |
364 |
Internet Media Type. [SGML] |
365 |
|
366 |
fragment identifier |
367 |
the portion of an HREF attribute value following the `#' |
368 |
character which modifies the presentation of the |
369 |
destination of a hyperlink. |
370 |
|
371 |
form data set |
372 |
a sequence of name/value pairs; the names are given by |
373 |
an HTML document and the values are given by a user. |
374 |
|
375 |
HTML document |
376 |
An SGML document conforming to this document type |
377 |
definition. |
378 |
|
379 |
hyperlink |
380 |
a relationship between two anchors, called the tail and |
381 |
the head. |
382 |
|
383 |
markup |
384 |
Syntactically delimited characters added to the data of |
385 |
a document to represent its structure. There are four |
386 |
different kinds of markup: descriptive markup (tags), |
387 |
references, markup declarations, and processing |
388 |
instructions. [SGML] |
389 |
|
390 |
may |
391 |
A document or user interface is conforming whether this |
392 |
statement applies or not. |
393 |
|
394 |
media type |
395 |
an Internet Media Type, as per [IMEDIA]. |
396 |
|
397 |
message entity |
398 |
a head and body. The head is a collection of name/value |
399 |
fields, and the body is a sequence of octets. The head |
400 |
defines the content type and content transfer encoding |
401 |
of the body. [MIME] |
402 |
|
403 |
minimally conforming |
404 |
HTML user agent |
405 |
A user agent that conforms to this specification except |
406 |
for form processing. It may only process level 1 HTML |
407 |
documents. |
408 |
|
409 |
must |
410 |
Documents or user agents in conflict with this statement |
411 |
are not conforming. |
412 |
|
413 |
Berners-Lee, Connolly [Page 7] |
414 |
|
415 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
416 |
|
417 |
|
418 |
numeric character |
419 |
reference |
420 |
markup that refers to a character by its code position |
421 |
in the document character set. |
422 |
|
423 |
SGML document |
424 |
A sequence of characters organized physically as a set |
425 |
of entities and logically into a hierarchy of elements. |
426 |
An SGML document consists of data characters and markup; |
427 |
the markup describes the structure of the information |
428 |
and an instance of that structure. [SGML] |
429 |
|
430 |
shall |
431 |
If a document or user agent conflicts with this |
432 |
statement, it does not conform to this specification. |
433 |
|
434 |
should |
435 |
If a document or user agent conflicts with this |
436 |
statement, undesirable results may occur in practice |
437 |
even though it conforms to this specification. |
438 |
|
439 |
start-tag |
440 |
Descriptive markup that identifies the start of an |
441 |
element and specifies its generic identifier and |
442 |
attributes. [SGML] |
443 |
|
444 |
syntax-reference |
445 |
character set |
446 |
A coded character set whose range includes all |
447 |
characters used for markup; e.g. name characters and |
448 |
delimiter characters. |
449 |
|
450 |
tag |
451 |
Markup that delimits an element. A tag includes a name |
452 |
which refers to an element declaration in the DTD, and |
453 |
may include attributes. [SGML] |
454 |
|
455 |
text entity |
456 |
A finite sequence of characters. A text entity typically |
457 |
takes the form of a sequence of octets with some |
458 |
associated character encoding scheme, transmitted over |
459 |
the network or stored in a file. [SGML] |
460 |
|
461 |
typical |
462 |
Typical processing is described for many elements. This |
463 |
is not a mandatory part of the specification but is |
464 |
given as guidance for designers and to help explain the |
465 |
uses for which the elements were intended. |
466 |
|
467 |
URI |
468 |
A Uniform Resource Identifier is a formatted string that |
469 |
serves as an identifier for a resource, typically on the |
470 |
Internet. URIs are used in HTML to identify the anchors |
471 |
|
472 |
Berners-Lee, Connolly [Page 8] |
473 |
|
474 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
475 |
|
476 |
of hyperlinks. URIs in common practice include Uniform |
477 |
Resource Locators (URLs)[URL] and Relative URLs |
478 |
[RELURL]. |
479 |
|
480 |
user agent |
481 |
A component of a distributed system that presents an |
482 |
interface and processes requests on behalf of a user; |
483 |
for example, a www browser or a mail user agent. |
484 |
|
485 |
WWW |
486 |
The World-Wide Web is a hypertext-based, distributed |
487 |
information system created by researchers at CERN in |
488 |
Switzerland. <URL:http://www.w3.org/> |
489 |
|
490 |
|
491 |
3. HTML as an Application of SGML |
492 |
|
493 |
HTML is an application of ISO 8879:1986 -- Standard Generalized |
494 |
Markup Language (SGML). SGML is a system for defining structured |
495 |
document types and markup languages to represent instances of |
496 |
those document types[SGML]. The public text -- DTD and SGML |
497 |
declaration -- of the HTML document type definition are provided |
498 |
in 9, "HTML Public Text". |
499 |
|
500 |
The term _HTML_ refers to both the document type defined here |
501 |
and the markup language for representing instances of this |
502 |
document type. |
503 |
|
504 |
|
505 |
3.1. SGML Documents |
506 |
|
507 |
An HTML document is an SGML document; that is, a sequence of |
508 |
characters organized physically into a set of entities, and |
509 |
logically as a hierarchy of elements. |
510 |
|
511 |
In the SGML specification, the first production of the SGML |
512 |
syntax grammar separates an SGML document into three parts: an |
513 |
SGML declaration, a prologue, and an instance. For the purposes |
514 |
of this specification, the prologue is a DTD. This DTD describes |
515 |
another grammar: the start symbol is given in the doctype |
516 |
declaration, the terminals are data characters and tags, and the |
517 |
productions are determined by the element declarations. The |
518 |
instance must conform to the DTD, that is, it must be in the |
519 |
language defined by this grammar. |
520 |
|
521 |
The SGML declaration determines the lexicon of the grammar. It |
522 |
specifies the document character set, which determines a |
523 |
character repertoire that contains all characters that occur in |
524 |
all text entities in the document, and the code positions |
525 |
associated with those characters. |
526 |
|
527 |
The SGML declaration also specifies the syntax-reference |
528 |
character set of the document, and a few other parameters that |
529 |
bind the abstract syntax of SGML to a concrete syntax. This |
530 |
|
531 |
Berners-Lee, Connolly [Page 9] |
532 |
|
533 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
534 |
|
535 |
concrete syntax determines how the sequence of characters of the |
536 |
document is mapped to a sequence of terminals in the grammar of |
537 |
the prologue. |
538 |
|
539 |
For example, consider the following document: |
540 |
|
541 |
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN"> |
542 |
<title>Parsing Example</title> |
543 |
<p>Some text. <em>*wow*</em></p> |
544 |
|
545 |
An HTML user agent should use the SGML declaration that is given |
546 |
in 9.5, "SGML Declaration for HTML". According to its document |
547 |
character set, `*' refers to an asterisk character, `*'. |
548 |
|
549 |
The instance above is regarded as the following sequence of |
550 |
terminals: |
551 |
|
552 |
1. start-tag: TITLE |
553 |
|
554 |
2. data characters: ``Parsing Example'' |
555 |
|
556 |
3. end-tag: TITLE |
557 |
|
558 |
4. start-tag: P |
559 |
|
560 |
5. data characters ``Some text. '' |
561 |
|
562 |
6. start-tag: EM |
563 |
|
564 |
7. data characters: ``*wow*'' |
565 |
|
566 |
8. end-tag: EM |
567 |
|
568 |
9. end-tag: P |
569 |
|
570 |
The start symbol of the DTD grammar is HTML, and the productions |
571 |
are given in the public text identified by `-//IETF//DTD HTML |
572 |
2.0//EN' (9.1, "HTML DTD"). The terminals above parse as: |
573 |
|
574 |
HTML |
575 |
| |
576 |
\-HEAD |
577 |
| | |
578 |
| \-TITLE |
579 |
| | |
580 |
| \-<TITLE> |
581 |
| | |
582 |
| \-"Parsing Example" |
583 |
| | |
584 |
| \-</TITLE> |
585 |
| |
586 |
\-BODY |
587 |
| |
588 |
\-P |
589 |
|
590 |
Berners-Lee, Connolly [Page 10] |
591 |
|
592 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
593 |
|
594 |
| |
595 |
\-<P> |
596 |
| |
597 |
\-"Some text. " |
598 |
| |
599 |
\-EM |
600 |
| | |
601 |
| \-<EM> |
602 |
| | |
603 |
| \-"*wow*" |
604 |
| | |
605 |
| \-</EM> |
606 |
| |
607 |
\-</P> |
608 |
|
609 |
Some of the elements are delimited explicity by tags, while the |
610 |
boundaries of others are inferred. The <HTML> element contains a |
611 |
<HEAD> element and a <BODY> element. The <HEAD> contains |
612 |
<TITLE>, which is explicitly delimited by start- and end-tags. |
613 |
|
614 |
|
615 |
3.2. HTML Lexical Syntax |
616 |
|
617 |
SGML specifies an abstract syntax and a reference concrete |
618 |
syntax. Aside from certain quantities and capacities (e.g. the |
619 |
limit on the length of a name), all HTML documents use the |
620 |
reference concrete syntax. In particular, all markup characters |
621 |
are in the repertoire of [ISO-646]. Data characters are drawn |
622 |
from the document character set (see 6, "Characters, Words, and |
623 |
Paragraphs"). |
624 |
|
625 |
A complete discussion of SGML parsing, e.g. the mapping of a |
626 |
sequence of characters to a sequence of tags and data, is left |
627 |
to the SGML standard[SGML]. This section is only a summary. |
628 |
|
629 |
|
630 |
3.2.1. Data Characters |
631 |
|
632 |
Any sequence of characters that do not constitute markup (see |
633 |
9.6 ``Delimiter Recognition'' of [SGML]) are mapped directly to |
634 |
strings of data characters. Some markup also maps to data |
635 |
character strings. Numeric character references map to |
636 |
single-character strings, via the document character set. Each |
637 |
reference to one of the general entities defined in the HTML DTD |
638 |
maps to a single-character string. |
639 |
|
640 |
For example, |
641 |
|
642 |
abc<def => "abc","<","def" |
643 |
abc<def => "abc","<","def" |
644 |
|
645 |
The terminating semicolon on entity or numeric character |
646 |
references is only necessary when the character following the |
647 |
reference would otherwise be recognized as part of the name (see |
648 |
|
649 |
Berners-Lee, Connolly [Page 11] |
650 |
|
651 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
652 |
|
653 |
9.4.5 ``Reference End'' in [SGML]). |
654 |
|
655 |
abc < def => "abc ","<"," def" |
656 |
abc < def => "abc ","<"," def" |
657 |
|
658 |
An ampersand is only recognized as markup when it is followed by |
659 |
a letter or a `#' and a digit: |
660 |
|
661 |
abc & lt def => "abc & lt def" |
662 |
abc &# 60 def => "abc &# 60 def" |
663 |
|
664 |
A useful technique for translating plain text to HTML is to |
665 |
replace each '<', '&', and '>' by an entity reference or numeric |
666 |
character reference as follows: |
667 |
|
668 |
ENTITY NUMERIC |
669 |
CHARACTER REFERENCE CHAR REF CHARACTER DESCRIPTION |
670 |
--------- ---------- ----------- --------------------- |
671 |
& & & Ampersand |
672 |
< < < Less than |
673 |
> > > Greater than |
674 |
|
675 |
NOTE - There are SGML mechanisms, CDATA and RCDATA |
676 |
declared content, that allow most `<', `>', and `&' |
677 |
characters to be entered without the use of entity |
678 |
references. Because these mechanisms tend to be used and |
679 |
implemented inconsistently, and because they conflict |
680 |
with techniques for reducing HTML to 7 bit ASCII for |
681 |
transport, they are deprecated in this version of HTML. |
682 |
See 5.5.2.1, "Example and Listing: XMP, LISTING". |
683 |
|
684 |
|
685 |
3.2.2. Tags |
686 |
|
687 |
Tags delimit elements such as headings, paragraphs, lists, |
688 |
character highlighting, and links. Most HTML elements are |
689 |
identified in a document as a start-tag, which gives the element |
690 |
name and attributes, followed by the content, followed by the |
691 |
end tag. Start-tags are delimited by `<' and `>'; end tags are |
692 |
delimited by `</' and `>'. An example is: |
693 |
|
694 |
<H1>This is a Heading</H1> |
695 |
|
696 |
Some elements only have a start-tag without an end-tag. For |
697 |
example, to create a line break, you use the `<BR>' tag. |
698 |
Additionally, the end tags of some other elements, such as |
699 |
Paragraph (`</P>'), List Item (`</LI>'), Definition Term |
700 |
(`</DT>'), and Definition Description (`<DD>') elements, may be |
701 |
omitted. |
702 |
|
703 |
The content of an element is a sequence of data character |
704 |
strings and nested elements. Some elements, such as anchors, |
705 |
cannot be nested. Anchors and character highlighting may be put |
706 |
inside other constructs. See the HTML DTD, 9.1, "HTML DTD" for |
707 |
|
708 |
Berners-Lee, Connolly [Page 12] |
709 |
|
710 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
711 |
|
712 |
full details. |
713 |
|
714 |
NOTE - The SGML declaration for HTML specifies SHORTTAG |
715 |
YES, which means that there are other valid syntaxes for |
716 |
tags, such as NET tags, `<EM/.../'; empty start tags, |
717 |
`<>'; and empty end-tags, `</>'. Until support for these |
718 |
idioms is widely deployed, their use is strongly |
719 |
discouraged. |
720 |
|
721 |
|
722 |
3.2.3. Names |
723 |
|
724 |
A name consists of a letter followed by letters, digits, |
725 |
periods, or hyphens. The length of a name is limited to 72 |
726 |
characters by the `NAMELEN' parameter in the SGML delcaration |
727 |
for HTML, 9.5, "SGML Declaration for HTML". Element and |
728 |
attribute names are not case sensitive, but entity names are. |
729 |
For example, `<BLOCKQUOTE>', `<BlockQuote>', and `<blockquote>' |
730 |
are equivalent, whereas `&' is different from `&'. |
731 |
|
732 |
In a start-tag, the element name must immediately follow the tag |
733 |
open delimiter `<'. |
734 |
|
735 |
|
736 |
3.2.4. Attributes |
737 |
|
738 |
In a start-tag, white space and attributes are allowed between |
739 |
the element name and the closing delimiter. An attribute |
740 |
specification typically consists of an attribute name, an equal |
741 |
sign, and a value, though some attribute specifications may be |
742 |
just a name token. White space is allowed around the equal sign. |
743 |
|
744 |
The value of the attribute may be either: |
745 |
|
746 |
* A string literal, delimited by single quotes or double |
747 |
quotes and not containing any occurrences of the delimiting |
748 |
character. |
749 |
|
750 |
NOTE - Some historical implementations consider any |
751 |
occurrence of the `>' character to signal the end of |
752 |
a tag. For compatibility with such implementations, |
753 |
when `>' appears in an attribute value, it should be |
754 |
represented with a numeric character reference. For |
755 |
example, `<IMG SRC="eq1.jpg" alt="a>b">' should be |
756 |
written `<IMG SRC="eq1.jpg" alt="a>b">' or `<IMG |
757 |
SRC="eq1.jpg" alt="a>b">'. |
758 |
|
759 |
* A name token (a sequence of letters, digits, periods, or |
760 |
hyphens). Name tokens are not case sensitive. |
761 |
|
762 |
NOTE - Some historical implementations allow any |
763 |
character except space or `>' in a name token. |
764 |
|
765 |
In this example, <img> is the element name, src is the attribute |
766 |
|
767 |
Berners-Lee, Connolly [Page 13] |
768 |
|
769 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
770 |
|
771 |
name, and `http://host/dir/file.gif' is the attribute value: |
772 |
|
773 |
<img src='http://host/dir/file.gif'> |
774 |
|
775 |
A useful technique for computing an attribute value literal for |
776 |
a given string is to replace each quote and white space |
777 |
character by an entity reference or numeric character reference |
778 |
as follows: |
779 |
|
780 |
ENTITY NUMERIC |
781 |
CHARACTER REFERENCE CHAR REF CHARACTER DESCRIPTION |
782 |
--------- ---------- ----------- --------------------- |
783 |
HT 	 Tab |
784 |
LF Line Feed |
785 |
CR Carriage Return |
786 |
SP   Space |
787 |
" " " Quotation mark |
788 |
& & & Ampersand |
789 |
|
790 |
For example: |
791 |
|
792 |
<IMG SRC="image.jpg" alt="First "real" example"> |
793 |
|
794 |
The `NAMELEN' parameter in the SGML declaration (9.5, "SGML |
795 |
Declaration for HTML") limits the length of an attribute value |
796 |
to 1024 characters. |
797 |
|
798 |
Attributes such as ISMAP and COMPACT may be written using a |
799 |
minimized syntax (see 7.9.1.2 ``Omitted Attribute Name'' in |
800 |
[SGML]). The markup: |
801 |
|
802 |
<UL COMPACT="compact"> |
803 |
|
804 |
can be written using a minimized syntax: |
805 |
|
806 |
<UL COMPACT> |
807 |
|
808 |
NOTE - Some historical implementations only understand |
809 |
the minimized syntax. |
810 |
|
811 |
|
812 |
3.2.5. Comments |
813 |
|
814 |
To include comments in an HTML document, use a comment |
815 |
declaration. A comment declaration consists of `<!' followed by |
816 |
zero or more comments followed by `>'. Each comment starts with |
817 |
`--' and includes all text up to and including the next |
818 |
occurrence of `--'. In a comment declaration, white space is |
819 |
allowed after each comment, but not before the first comment. |
820 |
The entire comment declaration is ignored. |
821 |
|
822 |
NOTE - Some historical HTML implementations incorrectly |
823 |
consider any `>' character to be the termination of a |
824 |
comment. |
825 |
|
826 |
Berners-Lee, Connolly [Page 14] |
827 |
|
828 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
829 |
|
830 |
|
831 |
For example: |
832 |
|
833 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> |
834 |
<HEAD> |
835 |
<TITLE>HTML Comment Example</TITLE> |
836 |
<!-- Id: html-sgml.sgm,v 1.5 1995/05/26 21:29:50 connolly Exp --> |
837 |
<!-- another -- -- comment --> |
838 |
<!> |
839 |
</HEAD> |
840 |
<BODY> |
841 |
<p> <!- not a comment, just regular old data characters -> |
842 |
|
843 |
|
844 |
3.3. HTML Public Text Identifiers |
845 |
|
846 |
To identify information as an HTML document conforming to this |
847 |
specification, each document must start with one of the |
848 |
following document type declarations. |
849 |
|
850 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> |
851 |
|
852 |
This document type declaration refers to the HTML DTD in 9.1, |
853 |
"HTML DTD". |
854 |
|
855 |
NOTE - If the body of a `text/html' message entity does |
856 |
not begin with a document type declaration, an HTML user |
857 |
agent should infer the above document type declaration. |
858 |
|
859 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Level 2//EN"> |
860 |
|
861 |
This document type declaration also refers to the HTML DTD which |
862 |
appears in 9.1, "HTML DTD". |
863 |
|
864 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Level 1//EN"> |
865 |
|
866 |
This document type declaration refers to the level 1 HTML DTD in |
867 |
9.3, "Level 1 HTML DTD". Form elements must not occur in level 1 |
868 |
documents. |
869 |
|
870 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Strict//EN"> |
871 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Strict Level 1//EN"> |
872 |
|
873 |
These two document type declarations refer to the HTML DTD in |
874 |
9.2, "Strict HTML DTD" and 9.4, "Strict Level 1 HTML DTD". They |
875 |
refer to the more structurally rigid definition of HTML. |
876 |
|
877 |
HTML user agents may support other document types. In |
878 |
particular, they may support other formal public identifiers, or |
879 |
other document types altogether. They may support an internal |
880 |
declaration subset with supplemental entity, element, and other |
881 |
markup declarations. |
882 |
|
883 |
|
884 |
|
885 |
Berners-Lee, Connolly [Page 15] |
886 |
|
887 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
888 |
|
889 |
3.4. Example HTML Document |
890 |
|
891 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> |
892 |
<HTML> |
893 |
<!-- Here's a good place to put a comment. --> |
894 |
<HEAD> |
895 |
<TITLE>Structural Example</TITLE> |
896 |
</HEAD><BODY> |
897 |
<H1>First Header</H1> |
898 |
<P>This is a paragraph in the example HTML file. Keep in mind |
899 |
that the title does not appear in the document text, but that |
900 |
the header (defined by H1) does.</P> |
901 |
<OL> |
902 |
<LI>First item in an ordered list. |
903 |
<LI>Second item in an ordered list. |
904 |
<UL COMPACT> |
905 |
<LI> Note that lists can be nested; |
906 |
<LI> Whitespace may be used to assist in reading the |
907 |
HTML source. |
908 |
</UL> |
909 |
<LI>Third item in an ordered list. |
910 |
</OL> |
911 |
<P>This is an additional paragraph. Technically, end tags are |
912 |
not required for paragraphs, although they are allowed. You can |
913 |
include character highlighting in a paragraph. <EM>This sentence |
914 |
of the paragraph is emphasized.</EM> Note that the </P> |
915 |
end tag has been omitted. |
916 |
<P> |
917 |
<IMG SRC ="triangle.xbm" alt="Warning: "> |
918 |
Be sure to read these <b>bold instructions</b>. |
919 |
</BODY></HTML> |
920 |
|
921 |
|
922 |
4. HTML as an Internet Media Type |
923 |
|
924 |
An HTML user agent allows users to interact with resources which |
925 |
have HTML representations. At a minimum, it must allow users to |
926 |
examine and navigate the content of HTML level 1 documents. HTML |
927 |
user agents should be able to preserve all formatting |
928 |
distinctions represented in an HTML document, and be able to |
929 |
simultaneously present resources referred to by IMG elements |
930 |
(they may ignore some formatting distinctions or IMG resources |
931 |
at the request of the user). Level 2 HTML user agents should |
932 |
support form entry and submission. |
933 |
|
934 |
|
935 |
4.1. text/html media type |
936 |
|
937 |
This specification defines the Internet Media Type[IMEDIA] |
938 |
(formerly referred to as the Content Type[MIME]) called |
939 |
`text/html'. The following is to be registered with [IANA]. |
940 |
|
941 |
Media Type name |
942 |
text |
943 |
|
944 |
Berners-Lee, Connolly [Page 16] |
945 |
|
946 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
947 |
|
948 |
|
949 |
Media subtype name |
950 |
html |
951 |
|
952 |
Required parameters |
953 |
none |
954 |
|
955 |
Optional parameters |
956 |
level, charset |
957 |
|
958 |
Encoding considerations |
959 |
any encoding is allowed |
960 |
|
961 |
Security considerations |
962 |
see 10, "Security Considerations" |
963 |
|
964 |
The optional parameters are defined as follows: |
965 |
|
966 |
Level |
967 |
The level parameter specifies the feature set used in |
968 |
the document. The level is an integer number, implying |
969 |
that any features of same or lower level may be present |
970 |
in the document. Level 1 is all features defined in this |
971 |
specification except those that require the <FORM> |
972 |
element. Level 2 includes form processing. Level 2 is |
973 |
the default. |
974 |
|
975 |
Charset |
976 |
The charset parameter (as defined in section 7.1.1 of |
977 |
RFC 1521[MIME]) may be given to specify the character |
978 |
encoding scheme used to represent the HTML document as a |
979 |
sequence of octets. The default value is outside the |
980 |
scope of this specification; but for example, the |
981 |
default is `US-ASCII' in the context of MIME mail, and |
982 |
`ISO-8859-1' in the context of HTTP. |
983 |
|
984 |
|
985 |
4.2. HTML Document Representation |
986 |
|
987 |
A message entity with a content type of `text/html' represents |
988 |
an HTML document, consisting of a single text entity. The |
989 |
`charset' parameter (whether implicit or explicit) identifies a |
990 |
character encoding scheme. The text entity consists of the |
991 |
characters determined by this character encoding scheme and the |
992 |
octets of the body of the message entity. |
993 |
|
994 |
|
995 |
4.2.1. Undeclared Markup Error Handling |
996 |
|
997 |
To facilitate experimentation and interoperability between |
998 |
implementations of various versions of HTML, the installed base |
999 |
of HTML user agents supports a superset of the HTML 2.0 language |
1000 |
by reducing it to HTML 2.0: markup in the form of a start-tag or |
1001 |
end-tag, whose generic identifier is not declared is mapped to |
1002 |
|
1003 |
Berners-Lee, Connolly [Page 17] |
1004 |
|
1005 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1006 |
|
1007 |
nothing during tokenization. Undeclared attributes are treated |
1008 |
similarly. The entire attribute specification of an unknown |
1009 |
attribute (i.e., the unknown attribute and its value, if any) |
1010 |
should be ignored. On the other hand, references to undeclared |
1011 |
entities should be treated as data characters. |
1012 |
|
1013 |
For example: |
1014 |
|
1015 |
<div class=chapter><h1>foo</h1><p>...</div> |
1016 |
=> <H1>,"foo",</H1>,<P>,"..." |
1017 |
xxx <P ID=z23> yyy |
1018 |
=> "xxx ",<P>," yyy |
1019 |
Let α & β be finite sets. |
1020 |
=> "Let α & β be finite sets." |
1021 |
|
1022 |
Support for notifying the user of such errors is encouraged. |
1023 |
|
1024 |
Information providers are warned that this convention is not |
1025 |
binding: unspecified behavior may result, as such markup does |
1026 |
not conform to this specification. |
1027 |
|
1028 |
|
1029 |
4.2.2. Conventional Representation of Newlines |
1030 |
|
1031 |
SGML specifies that a text entity is a sequence of records, each |
1032 |
beginning with a record start character and ending with a record |
1033 |
end character (code positions 10 and 13 respectively) (section |
1034 |
7.6.1, ``Record Boundaries'' in [SGML]). |
1035 |
|
1036 |
[MIME] specifies that a body of type `text/*' is a sequence of |
1037 |
lines, each terminated by CRLF, that is, octets 13, 10. |
1038 |
|
1039 |
In practice, HTML documents are frequently represented and |
1040 |
transmitted using an end of line convention that depends on the |
1041 |
conventions of the source of the document; frequently, that |
1042 |
representation consists of CR only, LF only, or a CR LF |
1043 |
sequence. Hence the decoding of the octets will often result in |
1044 |
a text entity with some missing record start and record end |
1045 |
characters. |
1046 |
|
1047 |
Since there is no ambiguity, HTML user agents are encouraged to |
1048 |
infer the missing record start and end characters. |
1049 |
|
1050 |
An HTML user agent should treat end of line in any of its |
1051 |
variations as a word space in all contexts except preformatted |
1052 |
text. Within preformatted text, an HTML user agent should treat |
1053 |
any of the three common representations of end-of-line as |
1054 |
starting a new line. |
1055 |
|
1056 |
|
1057 |
5. Document Structure |
1058 |
|
1059 |
An HTML document is a tree of elements, including a head and |
1060 |
body, headings, paragraphs, lists, etc. Form elements are |
1061 |
|
1062 |
Berners-Lee, Connolly [Page 18] |
1063 |
|
1064 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1065 |
|
1066 |
discussed in 8, "Forms". |
1067 |
|
1068 |
|
1069 |
5.1. Document Element: HTML |
1070 |
|
1071 |
The HTML document element consists of a head and a body, much |
1072 |
like a memo or a mail message. The head contains the title and |
1073 |
optional elements. The body is a text flow consisting of |
1074 |
paragraphs, lists, and other elements. |
1075 |
|
1076 |
|
1077 |
5.2. Head: HEAD |
1078 |
|
1079 |
The head of an HTML document is an unordered collection of |
1080 |
information about the document. For example: |
1081 |
|
1082 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> |
1083 |
<HEAD> |
1084 |
<TITLE>Introduction to HTML</TITLE> |
1085 |
</HEAD> |
1086 |
... |
1087 |
|
1088 |
|
1089 |
5.2.1. Title: TITLE |
1090 |
|
1091 |
Every HTML document must contain a <TITLE> element. |
1092 |
|
1093 |
The title should identify the contents of the document in a |
1094 |
global context. A short title, such as ``Introduction'' may be |
1095 |
meaningless out of context. A title such as ``Introduction to |
1096 |
HTML Elements'' is more appropriate. |
1097 |
|
1098 |
NOTE - The length of a title is not limited; however, |
1099 |
long titles may be truncated in some applications. To |
1100 |
minimize this possibility, titles should be fewer than |
1101 |
64 characters. |
1102 |
|
1103 |
A user agent may display the title of a document in a history |
1104 |
list or as a label for the window displaying the document. This |
1105 |
differs from headings (5.4, "Headings: H1 ... H6"), which are |
1106 |
typically displayed within the body text flow. |
1107 |
|
1108 |
|
1109 |
5.2.2. Base Address: BASE |
1110 |
|
1111 |
The optional <BASE> element allows the address of a document to |
1112 |
be recorded in situations in which the document may be read out |
1113 |
of context. The required HREF attribute specifies the base URI |
1114 |
(see 7, "Hyperlinks") for navigating the document, overriding |
1115 |
any context otherwise known to the user agent. The value of the |
1116 |
HREF attribute must be an absolute URI. |
1117 |
|
1118 |
|
1119 |
|
1120 |
|
1121 |
Berners-Lee, Connolly [Page 19] |
1122 |
|
1123 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1124 |
|
1125 |
5.2.3. Keyword Index: ISINDEX |
1126 |
|
1127 |
The <ISINDEX> element indicates that the user agent should allow |
1128 |
the user to search an index by giving keywords. See 7.5, |
1129 |
"Queries and Indexes" for details. |
1130 |
|
1131 |
|
1132 |
5.2.4. Link: LINK |
1133 |
|
1134 |
The <LINK> element represents a hyperlink (see 7, "Hyperlinks"). |
1135 |
It has the same attributes as the <A> element (see 5.7.3, |
1136 |
"Anchor: A"). |
1137 |
|
1138 |
The <LINK> element is typically used to indicate authorship, |
1139 |
related indexes and glossaries, older or more recent versions, |
1140 |
style sheets, document hierarchy etc. |
1141 |
|
1142 |
|
1143 |
5.2.5. Associated Meta-information: META |
1144 |
|
1145 |
The <META> element is an extensible container for use in |
1146 |
identifying specialized document meta-information. |
1147 |
Meta-information has two main functions: |
1148 |
|
1149 |
* to provide a means to discover that the data set exists |
1150 |
and how it might be obtained or accessed; and |
1151 |
|
1152 |
* to document the content, quality, and features of a data |
1153 |
set, indicating its fitness for use. |
1154 |
|
1155 |
Each <META> element specifies a name/value pair. If multiple |
1156 |
META elements are provided with the same name, their combined |
1157 |
contents--concatenated as a comma-separated list--is the value |
1158 |
associated with that name. |
1159 |
|
1160 |
NOTE - The <META> element should not be used where a |
1161 |
specific element, such as <TITLE>, would be more |
1162 |
appropriate. |
1163 |
|
1164 |
HTTP servers may read the content of the document <HEAD> to |
1165 |
generate header fields corresponding to any elements defining a |
1166 |
value for the attribute HTTP-EQUIV. |
1167 |
|
1168 |
NOTE - The method by which the server extracts document |
1169 |
meta-information is unspecified and not mandatory. The |
1170 |
<META> element only provides an extensible mechanism for |
1171 |
identifying and embedding document meta-information -- |
1172 |
how it may be used is up to the individual server |
1173 |
implementation and the HTML user agent. |
1174 |
|
1175 |
Attributes of the META element: |
1176 |
|
1177 |
HTTP-EQUIV |
1178 |
binds the element to an HTTP header field. An HTTP |
1179 |
|
1180 |
Berners-Lee, Connolly [Page 20] |
1181 |
|
1182 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1183 |
|
1184 |
server may use this information to process the document. |
1185 |
In particular, it may include a header field in the |
1186 |
responses to requests for this document: the header name |
1187 |
is taken from the HTTP-EQUIV attribute value, and the |
1188 |
header value is taken from the value of the CONTENT |
1189 |
attribute. HTTP header names are not case sensitive. |
1190 |
|
1191 |
NAME |
1192 |
specifies the name of the name/value pair. If not |
1193 |
present, HTTP-EQUIV gives the name. |
1194 |
|
1195 |
CONTENT |
1196 |
specifies the value of the name/value pair. |
1197 |
|
1198 |
Examples |
1199 |
|
1200 |
If the document contains: |
1201 |
|
1202 |
<META HTTP-EQUIV="Expires" |
1203 |
CONTENT="Tue, 04 Dec 1993 21:29:02 GMT"> |
1204 |
<meta http-equiv="Keywords" CONTENT="Fred"> |
1205 |
<META HTTP-EQUIV="Reply-to" |
1206 |
content="fielding@ics.uci.edu (Roy Fielding)"> |
1207 |
<Meta Http-equiv="Keywords" CONTENT="Barney"> |
1208 |
|
1209 |
then the server may include the following header fields: |
1210 |
|
1211 |
Expires: Tue, 04 Dec 1993 21:29:02 GMT |
1212 |
Keywords: Fred, Barney |
1213 |
Reply-to: fielding@ics.uci.edu (Roy Fielding) |
1214 |
|
1215 |
as part of the HTTP response to a `GET' or `HEAD' request for |
1216 |
that document. |
1217 |
|
1218 |
An HTTP server must not use the <META> element to form an HTTP |
1219 |
response header unless the HTTP-EQUIV attribute is present. |
1220 |
|
1221 |
An HTTP server may disregard any <META> elements that specify |
1222 |
information controlled by the HTTP server, for example `Server', |
1223 |
`Date', and `Last-modified'. |
1224 |
|
1225 |
|
1226 |
5.2.6. Next Id: NEXTID |
1227 |
|
1228 |
The <NEXTID> element is included for historical reasons only. |
1229 |
HTML document should not contain <NEXTID> elements. |
1230 |
|
1231 |
The <NEXTID> element gives a hint for the name to use for a new |
1232 |
<A> element when editing an HTML document. It should be distinct |
1233 |
from all NAME attribute values on <A> elements. For example: |
1234 |
|
1235 |
<NEXTID N=Z27> |
1236 |
|
1237 |
|
1238 |
|
1239 |
Berners-Lee, Connolly [Page 21] |
1240 |
|
1241 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1242 |
|
1243 |
5.3. Body: BODY |
1244 |
|
1245 |
The <BODY> element contains the text flow of the document, |
1246 |
including headings, paragraphs, lists, etc. |
1247 |
|
1248 |
For example: |
1249 |
|
1250 |
<BODY> |
1251 |
<h1>Important Stuff</h1> |
1252 |
<p>Explanation about important stuff... |
1253 |
</BODY> |
1254 |
|
1255 |
|
1256 |
5.4. Headings: H1 ... H6 |
1257 |
|
1258 |
The six heading elements, <H1> through <H6>, denote section |
1259 |
headings. Although the order and occurrence of headings is not |
1260 |
constrained by the HTML DTD, documents should not skip levels |
1261 |
(for example, from H1 to H3), as converting such documents to |
1262 |
other representations is often problematic. |
1263 |
|
1264 |
Example of use: |
1265 |
|
1266 |
<H1>This is a heading</H1> |
1267 |
Here is some text |
1268 |
<H2>Second level heading</H2> |
1269 |
Here is some more text. |
1270 |
|
1271 |
Typical renderings are: |
1272 |
|
1273 |
H1 |
1274 |
Bold, very-large font, centered. One or two blank lines |
1275 |
above and below. |
1276 |
|
1277 |
H2 |
1278 |
Bold, large font, flush-left. One or two blank lines |
1279 |
above and below. |
1280 |
|
1281 |
H3 |
1282 |
Italic, large font, slightly indented from the left |
1283 |
margin. One or two blank lines above and below. |
1284 |
|
1285 |
H4 |
1286 |
Bold, normal font, indented more than H3. One blank line |
1287 |
above and below. |
1288 |
|
1289 |
H5 |
1290 |
Italic, normal font, indented as H4. One blank line |
1291 |
above. |
1292 |
|
1293 |
H6 |
1294 |
Bold, indented same as normal text, more than H5. One |
1295 |
blank line above. |
1296 |
|
1297 |
|
1298 |
Berners-Lee, Connolly [Page 22] |
1299 |
|
1300 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1301 |
|
1302 |
5.5. Block Structuring Elements |
1303 |
|
1304 |
Block structuring elements include paragraphs, lists, and block |
1305 |
quotes. They must not contain heading elements, but they may |
1306 |
contain phrase markup, and in some cases, they may be nested. |
1307 |
|
1308 |
|
1309 |
5.5.1. Paragraph: P |
1310 |
|
1311 |
The <P> element indicates a paragraph. The exact indentation, |
1312 |
leading space, etc. of a paragraph is not specified and may be a |
1313 |
function of other tags, style sheets, etc. |
1314 |
|
1315 |
Typically, paragraphs are surrounded by a vertical space of one |
1316 |
line or half a line. The first line in a paragraph is indented |
1317 |
in some cases. |
1318 |
|
1319 |
Example of use: |
1320 |
|
1321 |
<H1>This Heading Precedes the Paragraph</H1> |
1322 |
<P>This is the text of the first paragraph. |
1323 |
<P>This is the text of the second paragraph. Although you do not |
1324 |
need to start paragraphs on new lines, maintaining this |
1325 |
convention facilitates document maintenance.</P> |
1326 |
<P>This is the text of a third paragraph.</P> |
1327 |
|
1328 |
|
1329 |
5.5.2. Preformatted Text: PRE |
1330 |
|
1331 |
The <PRE> element represents a character cell block of text and |
1332 |
is suitable for text that has been formatted for a monospaced |
1333 |
font. |
1334 |
|
1335 |
The <PRE> tag may be used with the optional WIDTH attribute. The |
1336 |
WIDTH attribute specifies the maximum number of characters for a |
1337 |
line and allows the HTML user agent to select a suitable font |
1338 |
and indentation. |
1339 |
|
1340 |
Within preformatted text: |
1341 |
|
1342 |
* Line breaks within the text are rendered as a move to the |
1343 |
beginning of the next line. |
1344 |
|
1345 |
NOTE - References to the ``beginning of a new line'' |
1346 |
do not imply that the renderer is forbidden from |
1347 |
using a constant left indent for rendering |
1348 |
preformatted text. The left indent may be |
1349 |
constrained by the width required. |
1350 |
|
1351 |
* Anchor elements and phrase markup may be used. |
1352 |
|
1353 |
NOTE - Constraints on the processing of <PRE> |
1354 |
content may may limit or prevent the ability of the |
1355 |
HTML user agent to faithfully render phrase markup. |
1356 |
|
1357 |
Berners-Lee, Connolly [Page 23] |
1358 |
|
1359 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1360 |
|
1361 |
|
1362 |
* Elements that define paragraph formatting (headings, |
1363 |
address, etc.) must not be used. |
1364 |
|
1365 |
NOTE - Some historical documents contain <P> tags in |
1366 |
<PRE> elements. User agents are encouraged to treat |
1367 |
this as a line break. A <P> tag followed by a |
1368 |
newline character should produce only one line |
1369 |
break, not a line break plus a blank line. |
1370 |
|
1371 |
* The horizontal tab character (code position 9 in the HTML |
1372 |
document character set) must be interpreted as the smallest |
1373 |
positive nonzero number of spaces which will leave the |
1374 |
number of characters so far on the line as a multiple of 8. |
1375 |
Documents should not contain tab characters, as they are not |
1376 |
supported consistently. |
1377 |
|
1378 |
Example of use: |
1379 |
|
1380 |
<PRE> |
1381 |
Line 1. |
1382 |
Line 2 is to the right of line 1. <a href="abc">abc</a> |
1383 |
Line 3 aligns with line 2. <a href="def">def</a> |
1384 |
</PRE> |
1385 |
|
1386 |
|
1387 |
5.5.2.1. Example and Listing: XMP, LISTING |
1388 |
|
1389 |
The <XMP> and <LISTING> elements are similar to the <PRE> |
1390 |
element, but they have a different syntax. Their content is |
1391 |
declared as CDATA, which means that no markup except the end-tag |
1392 |
open delimiter-in-context is recognized (see 9.6 ``Delimiter |
1393 |
Recognition'' of [SGML]). |
1394 |
|
1395 |
NOTE - In a previous draft of the HTML specification, |
1396 |
the syntax of <XMP> and <LISTING> elements allowed |
1397 |
closing tags to be treated as data characters, as long |
1398 |
as the tag name was not <XMP> or <LISTING>, |
1399 |
respectively. |
1400 |
|
1401 |
Since CDATA declared content has a number of unfortunate |
1402 |
interactions with processing techniques and tends to be used and |
1403 |
implemented inconsistently, HTML documents should not contain |
1404 |
<XMP> nor <LISTING> elements -- the <PRE> tag is more expressive |
1405 |
and more consistently supported. |
1406 |
|
1407 |
The <LISTING> element should be rendered so that at least 132 |
1408 |
characters fit on a line. The <XMP> element should be rendered |
1409 |
so that at least 80 characters fit on a line but is otherwise |
1410 |
identical to the <LISTING> element. |
1411 |
|
1412 |
NOTE - In a previous draft, HTML included a <PLAINTEXT> |
1413 |
element that is similar to the <LISTING> element, except |
1414 |
that there is no closing tag: all characters after the |
1415 |
|
1416 |
Berners-Lee, Connolly [Page 24] |
1417 |
|
1418 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1419 |
|
1420 |
<PLAINTEXT> start-tag are data. |
1421 |
|
1422 |
|
1423 |
5.5.3. Address: ADDRESS |
1424 |
|
1425 |
The <ADDRESS> element contains such information as address, |
1426 |
signature and authorship, often at the beginning or end of the |
1427 |
body of a document. |
1428 |
|
1429 |
Typically, the <ADDRESS> element is rendered in an italic |
1430 |
typeface and may be indented. |
1431 |
|
1432 |
Example of use: |
1433 |
|
1434 |
<ADDRESS> |
1435 |
Newsletter editor<BR> |
1436 |
J.R. Brown<BR> |
1437 |
JimquickPost News, Jimquick, CT 01234<BR> |
1438 |
Tel (123) 456 7890 |
1439 |
</ADDRESS> |
1440 |
|
1441 |
|
1442 |
5.5.4. Block Quote: BLOCKQUOTE |
1443 |
|
1444 |
The <BLOCKQUOTE> element contains text quoted from another |
1445 |
source. |
1446 |
|
1447 |
A typical rendering might be a slight extra left and right |
1448 |
indent, and/or italic font. The <BLOCKQUOTE> typically provides |
1449 |
space above and below the quote. |
1450 |
|
1451 |
Single-font rendition may reflect the quotation style of |
1452 |
Internet mail by putting a vertical line of graphic characters, |
1453 |
such as the greater than symbol (>), in the left margin. |
1454 |
|
1455 |
Example of use: |
1456 |
|
1457 |
I think the poem ends |
1458 |
<BLOCKQUOTE> |
1459 |
<P>Soft you now, the fair Ophelia. Nymph, in thy orisons, be all |
1460 |
my sins remembered. |
1461 |
</BLOCKQUOTE> |
1462 |
but I am not sure. |
1463 |
|
1464 |
|
1465 |
5.6. List Elements |
1466 |
|
1467 |
HTML includes a number of list elements. They may be used in |
1468 |
combination; for example, a <OL> may be nested in an <LI> |
1469 |
element of a <UL>. |
1470 |
|
1471 |
The COMPACT attribute suggests that a compact rendering be used. |
1472 |
|
1473 |
|
1474 |
|
1475 |
Berners-Lee, Connolly [Page 25] |
1476 |
|
1477 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1478 |
|
1479 |
5.6.1. Unordered List: UL, LI |
1480 |
|
1481 |
The <UL> represents a list of items -- typically a bulleted |
1482 |
list. |
1483 |
|
1484 |
The content of a <UL> element is a sequence of <LI> elements. |
1485 |
For example: |
1486 |
|
1487 |
<UL> |
1488 |
<LI>First list item |
1489 |
<LI>Second list item |
1490 |
<p>second paragraph of second item |
1491 |
<LI>Third list item |
1492 |
</UL> |
1493 |
|
1494 |
|
1495 |
5.6.2. Ordered List: OL |
1496 |
|
1497 |
The <OL> element represents an ordered list of items, sorted by |
1498 |
sequence or order of importance. It is typically rendered as a |
1499 |
numbered list. |
1500 |
|
1501 |
The content of a <OL> element is a sequence of <LI> elements. |
1502 |
For example: |
1503 |
|
1504 |
<OL> |
1505 |
<LI>Click the Web button to open URI window. |
1506 |
<LI>Enter the URI number in the text field of the Open URI |
1507 |
window. The Web document you specified is displayed. |
1508 |
<ol> |
1509 |
<li>substep 1 |
1510 |
<li>substep 2 |
1511 |
</ol> |
1512 |
<LI>Click highlighted text to move from one link to another. |
1513 |
</OL> |
1514 |
|
1515 |
|
1516 |
5.6.3. Directory List: DIR |
1517 |
|
1518 |
The <DIR> element is similar to the <UL> element. It represents |
1519 |
a list of short items, typically up to 20 characters each. Items |
1520 |
in a directory list may be arranged in columns, typically 24 |
1521 |
characters wide. |
1522 |
|
1523 |
The content of a <DIR> element is a sequence of <LI> elements. |
1524 |
Nested block elements are not allowed in the content of <DIR> |
1525 |
elements. For example: |
1526 |
|
1527 |
<DIR> |
1528 |
<LI>A-H<LI>I-M |
1529 |
<LI>M-R<LI>S-Z |
1530 |
</DIR> |
1531 |
|
1532 |
|
1533 |
|
1534 |
Berners-Lee, Connolly [Page 26] |
1535 |
|
1536 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1537 |
|
1538 |
5.6.4. Menu List: MENU |
1539 |
|
1540 |
The <MENU> element is a list of items with typically one line |
1541 |
per item. The menu list style is typically more compact than the |
1542 |
style of an unordered list. |
1543 |
|
1544 |
The content of a <MENU> element is a sequence of <LI> elements. |
1545 |
Nested block elements are not allowed in the content of <MENU> |
1546 |
elements. For example: |
1547 |
|
1548 |
<MENU> |
1549 |
<LI>First item in the list. |
1550 |
<LI>Second item in the list. |
1551 |
<LI>Third item in the list. |
1552 |
</MENU> |
1553 |
|
1554 |
|
1555 |
5.6.5. Definition List: DL, DT, DD |
1556 |
|
1557 |
A definition list is a list of terms and corresponding |
1558 |
definitions. Definition lists are typically formatted with the |
1559 |
term flush-left and the definition, formatted paragraph style, |
1560 |
indented after the term. |
1561 |
|
1562 |
The content of a <DL> element is a sequence of <DT> elements |
1563 |
and/or <DD> elements, usually in pairs. Multiple <DT> may be |
1564 |
paired with a single <DD> element. Documents should not contain |
1565 |
multiple consecutive <DD> elements. |
1566 |
|
1567 |
Example of use: |
1568 |
|
1569 |
<DL> |
1570 |
<DT>Term<DD>This is the definition of the first term. |
1571 |
<DT>Term<DD>This is the definition of the second term. |
1572 |
</DL> |
1573 |
|
1574 |
If the DT term does not fit in the DT column (typically one |
1575 |
third of the display area), it may be extended across the page |
1576 |
with the DD section moved to the next line, or it may be wrapped |
1577 |
onto successive lines of the left hand column. |
1578 |
|
1579 |
The optional COMPACT attribute suggests that a compact rendering |
1580 |
be used, because the list items are small and/or the entire list |
1581 |
is large. |
1582 |
|
1583 |
Unless the COMPACT attribute is present, an HTML user agent may |
1584 |
leave white space between successive DT, DD pairs. The COMPACT |
1585 |
attribute may also reduce the width of the left-hand (DT) |
1586 |
column. |
1587 |
|
1588 |
<DL COMPACT> |
1589 |
<DT>Term<DD>This is the first definition in compact format. |
1590 |
<DT>Term<DD>This is the second definition in compact format. |
1591 |
</DL> |
1592 |
|
1593 |
Berners-Lee, Connolly [Page 27] |
1594 |
|
1595 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1596 |
|
1597 |
|
1598 |
|
1599 |
5.7. Phrase Markup |
1600 |
|
1601 |
Phrases may be marked up according to idiomatic usage, |
1602 |
typographic appearance, or for use as hyperlink anchors. |
1603 |
|
1604 |
User agents must render highlighted phrases distinctly from |
1605 |
plain text. Additionally, <EM> content must be rendered as |
1606 |
distinct from <STRONG> content, and <B> content must rendered as |
1607 |
distinct from <I> content. |
1608 |
|
1609 |
Phrase elements may be nested within the content of other phrase |
1610 |
elements; however, HTML user agents may render nested phrase |
1611 |
elements indistinctly from non-nested elements: |
1612 |
|
1613 |
plain <B>bold <I>italic</I></B> may be rendered |
1614 |
the same as plain <B>bold </B><I>italic</I> |
1615 |
|
1616 |
|
1617 |
5.7.1. Idiomatic Elements |
1618 |
|
1619 |
Phrases may be marked up to indicate certain idioms. |
1620 |
|
1621 |
NOTE - User agents may support the <DFN> element, not |
1622 |
included in this specification, as it has been deployed |
1623 |
to some extent. It is used to indicate the defining |
1624 |
instance of a term, and it is typically rendered in |
1625 |
italic or bold italic. |
1626 |
|
1627 |
|
1628 |
5.7.1.1. Citation: CITE |
1629 |
|
1630 |
The <CITE> element is used to indicate the title of a book or |
1631 |
other citation. It is typically rendered as italics. For |
1632 |
example: |
1633 |
|
1634 |
He just couldn't get enough of <cite>The Grapes of Wrath</cite>. |
1635 |
|
1636 |
|
1637 |
5.7.1.2. Code: CODE |
1638 |
|
1639 |
The <CODE> element indicates an example of code, typically |
1640 |
rendered in a mono-spaced font. The <CODE> element is intended |
1641 |
for short words or phrases of code; the <PRE> block structuring |
1642 |
element (5.5.2, "Preformatted Text: PRE") is more apropriate for |
1643 |
multiple-line listings. For example: |
1644 |
|
1645 |
The expression <code>x += 1</code> |
1646 |
is short for <code>x = x + 1</code>. |
1647 |
|
1648 |
|
1649 |
|
1650 |
|
1651 |
|
1652 |
Berners-Lee, Connolly [Page 28] |
1653 |
|
1654 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1655 |
|
1656 |
5.7.1.3. Emphasis: EM |
1657 |
|
1658 |
The <EM> element indicates an emphasized phrase, typically |
1659 |
rendered as italics. For example: |
1660 |
|
1661 |
A singular subject <em>always</em> takes a singular verb. |
1662 |
|
1663 |
|
1664 |
5.7.1.4. Keyboard: KBD |
1665 |
|
1666 |
The <KBD> element indicates text typed by a user, typically |
1667 |
rendered in a mono-spaced font. This is commonly used in |
1668 |
instruction manuals. For example: |
1669 |
|
1670 |
Enter <kbd>FIND IT</kbd> to search the database. |
1671 |
|
1672 |
|
1673 |
5.7.1.5. Sample: SAMP |
1674 |
|
1675 |
The <SAMP> element indicates a sequence of literal characters, |
1676 |
typically rendered in a mono-spaced font. For example: |
1677 |
|
1678 |
The only word containing the letters <samp>mt</samp> is dreamt. |
1679 |
|
1680 |
|
1681 |
5.7.1.6. Strong Emphasis: STRONG |
1682 |
|
1683 |
The <STRONG> element indicates strong emphasis, typically |
1684 |
rendered in bold. For example: |
1685 |
|
1686 |
<strong>STOP</strong>, or I'll say "<strong>STOP</strong>" again!. |
1687 |
|
1688 |
|
1689 |
5.7.1.7. Variable: VAR |
1690 |
|
1691 |
The <VAR> element indicates a placeholder variable, typically |
1692 |
rendered as italic. For example: |
1693 |
|
1694 |
Type <SAMP>html-check <VAR>file</VAR> | more</SAMP> |
1695 |
to check <VAR>file</VAR> for markup errors. |
1696 |
|
1697 |
|
1698 |
5.7.2. Typographic Elements |
1699 |
|
1700 |
Typographic elements are used to specify the format of marked |
1701 |
text. |
1702 |
|
1703 |
Typical renderings for idiomatic elements may vary between user |
1704 |
agents. If a specific rendering is necessary -- for example, |
1705 |
when referring to a specific text attribute as in ``The italic |
1706 |
parts are mandatory'' -- a typographic element can be used to |
1707 |
ensure that the intended typography is used where possible. |
1708 |
|
1709 |
NOTE - User agents may support some typographic elements |
1710 |
|
1711 |
Berners-Lee, Connolly [Page 29] |
1712 |
|
1713 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1714 |
|
1715 |
not included in this specification, as they have been |
1716 |
deployed to some extent. The <STRIKE> element indicates |
1717 |
horizontal line through the characters, and the <U> |
1718 |
element indicates an underline. |
1719 |
|
1720 |
|
1721 |
5.7.2.1. Bold: B |
1722 |
|
1723 |
The <B> element indicates bold text. Where bold typography is |
1724 |
unavailable, an alternative representation may be used. |
1725 |
|
1726 |
|
1727 |
5.7.2.2. Italic: I |
1728 |
|
1729 |
The <I> element indicates italic text. Where italic typography |
1730 |
is unavailable, an alternative representation may be used. |
1731 |
|
1732 |
|
1733 |
5.7.2.3. Teletype: TT |
1734 |
|
1735 |
The <TT> element indicates teletype (monospaced )text. Where a |
1736 |
teletype font is unavailable, an alternative representation may |
1737 |
be used. |
1738 |
|
1739 |
|
1740 |
5.7.3. Anchor: A |
1741 |
|
1742 |
The <A> element indicates a hyperlink anchor (see 7, |
1743 |
"Hyperlinks"). At least one of the NAME and HREF attributes |
1744 |
should be present. Attributes of the <A> element: |
1745 |
|
1746 |
HREF |
1747 |
gives the URI of the head anchor of a hyperlink. |
1748 |
|
1749 |
NAME |
1750 |
gives the name of the anchor, and makes it available as |
1751 |
a head of a hyperlink. |
1752 |
|
1753 |
TITLE |
1754 |
suggests a title for the destination resource -- |
1755 |
advisory only. The TITLE attribute may be used: |
1756 |
|
1757 |
* for display prior to accessing the destination |
1758 |
resource, for example, as a margin note or on a |
1759 |
small box while the mouse is over the anchor, or |
1760 |
while the document is being loaded; |
1761 |
|
1762 |
* for resources that do not include a title, such as |
1763 |
graphics, plain text and Gopher menus, for use as a |
1764 |
window title. |
1765 |
|
1766 |
REL |
1767 |
The REL attribute gives the relationship(s) described by |
1768 |
the hyperlink. The value is a whitespace separated list |
1769 |
|
1770 |
Berners-Lee, Connolly [Page 30] |
1771 |
|
1772 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1773 |
|
1774 |
of relationship names. |
1775 |
|
1776 |
REV |
1777 |
same as the REL attribute, but the semantics of the |
1778 |
relationship are in the reverse direction. A link from A |
1779 |
to B with REL=``X'' expresses the same relationship as a |
1780 |
link from B to A with REV=``X''. An anchor may have both |
1781 |
REL and REV attributes. |
1782 |
|
1783 |
URN |
1784 |
specifies a preferred, more persistent identifier for |
1785 |
the head anchor of the hyperlink. The syntax and |
1786 |
semantics of the URN attribute are not yet specified. |
1787 |
|
1788 |
METHODS |
1789 |
specifies methods to be used in accessing the |
1790 |
destination, as a whitespace-separated list of names. |
1791 |
The set of applicable names is a function of the scheme |
1792 |
of the URI in the HREF attribute. For similar reasons as |
1793 |
for the TITLE attribute, it may be useful to include the |
1794 |
information in advance in the link. For example, the |
1795 |
HTML user agent may chose a different rendering as a |
1796 |
function of the methods allowed; for example, something |
1797 |
that is searchable may get a different icon. |
1798 |
|
1799 |
|
1800 |
5.8. Line Break: BR |
1801 |
|
1802 |
The <BR> element specifies a line break between words (see 6, |
1803 |
"Characters, Words, and Paragraphs"). For example: |
1804 |
|
1805 |
<P> Pease porridge hot<BR> |
1806 |
Pease porridge cold<BR> |
1807 |
Pease porridge in the pot<BR> |
1808 |
Nine days old. |
1809 |
|
1810 |
|
1811 |
5.9. Horizontal Rule: HR |
1812 |
|
1813 |
The <HR> element is a divider between sections of text; |
1814 |
typically a full width horizontal rule or equivalent graphic. |
1815 |
For example: |
1816 |
|
1817 |
<HR> |
1818 |
<ADDRESS>February 8, 1995, CERN</ADDRESS> |
1819 |
</BODY> |
1820 |
|
1821 |
|
1822 |
5.10. Image: IMG |
1823 |
|
1824 |
The <IMG> element refers to an image or icon via a hyperlink |
1825 |
(see 7.3, "Simultaneous Presentation of Image Resources"). |
1826 |
|
1827 |
HTML user agents may process the value of the ALT attribute as |
1828 |
|
1829 |
Berners-Lee, Connolly [Page 31] |
1830 |
|
1831 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1832 |
|
1833 |
an alternative to processing the image resource indicated by the |
1834 |
SRC attribute. |
1835 |
|
1836 |
NOTE - Some HTML user agents can process graphics linked |
1837 |
via anchors, but not <IMG> graphics. If a graphic is |
1838 |
essential, it should be referenced from an <A> element |
1839 |
rather than an <IMG> element. If the graphic is not |
1840 |
essential, then the <IMG> element is appropriate. |
1841 |
|
1842 |
Attributes of the <IMG> element: |
1843 |
|
1844 |
ALIGN |
1845 |
alignment of the image with respect to the text |
1846 |
baseline. |
1847 |
|
1848 |
* `TOP' specifies that the top of the image aligns |
1849 |
with the tallest item on the line containing the |
1850 |
image. |
1851 |
|
1852 |
* `MIDDLE' specifies that the center of the image |
1853 |
aligns with the baseline of the line containing the |
1854 |
image. |
1855 |
|
1856 |
* `BOTTOM' specifies that the bottom of the image |
1857 |
aligns with the baseline of the line containing the |
1858 |
image. |
1859 |
|
1860 |
ALT |
1861 |
text to use in place of the referenced image resource, |
1862 |
for example due to processing constraints or user |
1863 |
preference. |
1864 |
|
1865 |
ISMAP |
1866 |
indicates an image map (see 7.6, "Image Maps"). |
1867 |
|
1868 |
SRC |
1869 |
specifies the URI of the image resource. |
1870 |
|
1871 |
NOTE - In practice, the media types of image |
1872 |
resources are limited to a few raster graphic |
1873 |
formats: typically `image/gif', `image/jpeg'. In |
1874 |
particular, `text/html' resources are not |
1875 |
intended to be used as image resources. |
1876 |
|
1877 |
Examples of use: |
1878 |
|
1879 |
<IMG SRC="triangle.xbm" ALT="Warning:"> Be sure |
1880 |
to read these instructions. |
1881 |
|
1882 |
<a href="http://machine/htbin/imagemap/sample"> |
1883 |
<IMG SRC="sample.xbm" ISMAP> |
1884 |
</a> |
1885 |
|
1886 |
|
1887 |
|
1888 |
Berners-Lee, Connolly [Page 32] |
1889 |
|
1890 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1891 |
|
1892 |
6. Characters, Words, and Paragraphs |
1893 |
|
1894 |
An HTML user agent should present the body of an HTML document |
1895 |
as a collection of typeset paragraphs and preformatted text. |
1896 |
Except for preformatted elements (<PRE>, <XMP>, <LISTING>, |
1897 |
<TEXTAREA>), each block structuring element is regarded as a |
1898 |
paragraph by taking the data characters in its content and the |
1899 |
content of its descendant elements, concatenating them, and |
1900 |
splitting the result into words, separated by space, tab, or |
1901 |
record end characters (and perhaps hyphen characters). The |
1902 |
sequence of words is typeset as a paragraph by breaking it into |
1903 |
lines. |
1904 |
|
1905 |
|
1906 |
6.1. The HTML Document Character Set |
1907 |
|
1908 |
The document character set specified in 9.5, "SGML Declaration |
1909 |
for HTML" must be supported by HTML user agents. It includes the |
1910 |
graphic characters of Latin Alphabet No. 1, or simply Latin-1. |
1911 |
Latin-1 comprises 191 graphic characters, including the |
1912 |
alphabets of most Western European languages. |
1913 |
|
1914 |
NOTE - Use the non-breaking space and soft hyphen |
1915 |
indicator characters is discouraged because support for |
1916 |
them is not widely deployed. |
1917 |
|
1918 |
NOTE - To support non-western writing systems, a larger |
1919 |
character repertoire will be specified in a future |
1920 |
version of HTML. The document character set will be |
1921 |
[ISO-10646], or some subset that agrees with |
1922 |
[ISO-10646]; in particular, all numeric character |
1923 |
references must use code positions assigned by |
1924 |
[ISO-10646]. |
1925 |
|
1926 |
In SGML applications, the use of control characters is limited |
1927 |
in order to maximize the chance of successful interchange over |
1928 |
heterogeneous networks and operating systems. In the HTML |
1929 |
document character set only three control characters are |
1930 |
allowed: Horizontal Tab, Carriage Return, and Line Feed (code |
1931 |
positions 9, 13, and 10). |
1932 |
|
1933 |
The HTML DTD references the Added Latin 1 entity set, to allow |
1934 |
mnemonic representation of selected Latin 1 characters using |
1935 |
only the widely supported ASCII character repertoire. For |
1936 |
example: |
1937 |
|
1938 |
Kurt Gödel was a famous logician and mathematician. |
1939 |
|
1940 |
See 9.7.2, "ISO Latin 1 Character Entity Set" for a table of the |
1941 |
``Added Latin 1'' entities, and 13, "The HTML Coded Character |
1942 |
Set" for a table of the code positions of [ISO 8859-1] and the |
1943 |
control characters in the HTML document character set. |
1944 |
|
1945 |
|
1946 |
|
1947 |
Berners-Lee, Connolly [Page 33] |
1948 |
|
1949 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
1950 |
|
1951 |
7. Hyperlinks |
1952 |
|
1953 |
In addition to general purpose elements such as paragraphs and |
1954 |
lists, HTML documents can express hyperlinks. An HTML user agent |
1955 |
allows the user to navigate these hyperlinks. |
1956 |
|
1957 |
A hyperlink is a relationship between two anchors, called the |
1958 |
head and the tail of the hyperlink[DEXTER]. Each anchor is |
1959 |
addressed, or uniquely identified, by an absolute Uniform |
1960 |
Resource Identifier (URI), optionally followed by a '#' and a |
1961 |
sequence of characters called a fragment identifier, as per |
1962 |
[RELURL]. For example: |
1963 |
|
1964 |
http://www.w3.org/hypertext/WWW/TheProject.html |
1965 |
http://www.w3.org/hypertext/WWW/TheProject.html#z31 |
1966 |
|
1967 |
In an anchor address, the URI refers to a resource; it may be |
1968 |
used in a variety of information retrieval protocols to obtain |
1969 |
an entity that represents the resource, such as an HTML |
1970 |
document. The fragment identifier, if present, refers to some |
1971 |
view on, or portion of the resource. |
1972 |
|
1973 |
An HTML user agent begins navigation with an absolute URI, |
1974 |
called the base URI, and an HTML document that is a |
1975 |
representation of the resource identified by the base URI. |
1976 |
|
1977 |
Each of the following markup constructs indicates the tail |
1978 |
anchor of a hyperlink or set of hyperlinks: |
1979 |
|
1980 |
* <A> elements with HREF present. |
1981 |
|
1982 |
* <LINK> elements. |
1983 |
|
1984 |
* <IMG> elements. |
1985 |
|
1986 |
* <INPUT> elements with the SRC attribute present. |
1987 |
|
1988 |
* <ISINDEX> elements. |
1989 |
|
1990 |
* <FORM> elements with `METHOD=GET'. |
1991 |
|
1992 |
These markup constructs refer to head anchors either directly by |
1993 |
means of an absolute URI, or indirectly by means of a relative |
1994 |
URI, which must be combined with the base URI as in [RELURL] to |
1995 |
determine the address of the head anchor. The markup may also |
1996 |
include fragment identifiers, separated from the URI by a '#' |
1997 |
character. |
1998 |
|
1999 |
|
2000 |
7.1. Accessing Resources |
2001 |
|
2002 |
Once the address of the head anchor is determined, the user |
2003 |
agent may obtain a representation of the resource, for example |
2004 |
as in [URL]. |
2005 |
|
2006 |
Berners-Lee, Connolly [Page 34] |
2007 |
|
2008 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2009 |
|
2010 |
|
2011 |
For example, if the base URI is `http://host/x/y.html' and the |
2012 |
document contains: |
2013 |
|
2014 |
<img src="../icons/abc.gif"> |
2015 |
|
2016 |
then the user agent uses the URI `http://host/icons/abc.gif' to |
2017 |
access the resource linked from the <IMG> element. |
2018 |
|
2019 |
If the URI in the address of the head anchor is the same as the |
2020 |
base URI, then the base document is sufficient as a |
2021 |
representation of the resource. A user agent must _not_, for |
2022 |
example, use any network information retrieval protocols to |
2023 |
obtain a new representation of the resourse. |
2024 |
|
2025 |
For example, if the base uri is |
2026 |
`http:'/www.w3.org/hypertext/WWW/TheProject.html/, then each of |
2027 |
the following markup constructs indicates a link whose head and |
2028 |
tail anchors have the same URI in their address: |
2029 |
|
2030 |
<a href="#xyz"> |
2031 |
<a href="../WWW/TheProject.html"> |
2032 |
<a href="./TheProject.html"> |
2033 |
<a href="TheProject.html"> |
2034 |
<a href="TheProject.html#z21"> |
2035 |
<a href="../../hypertext/WWW/TheProject.html"> |
2036 |
<a href="http://www.w3.org/hypertext/WWW/TheProject.html"> |
2037 |
|
2038 |
|
2039 |
7.2. Activation of Hyperlinks |
2040 |
|
2041 |
An HTML user agent allows the user to navigate the content of |
2042 |
the document and request activation of hyperlinks denoted by <A> |
2043 |
elements. HTML user agents should also allow activation of |
2044 |
<LINK> element hyperlinks. |
2045 |
|
2046 |
To activate a link, the user agent obtains a representation of |
2047 |
the resource identified in the address of the head anchor. If |
2048 |
the representation is another HTML document, navigation may |
2049 |
begin again with this new document. The base URI for navigation |
2050 |
is taken from the head anchor by default; however, any <BASE> |
2051 |
tag in the destination document overrides this default. The |
2052 |
process of obtaining the destination document may also override |
2053 |
the base URI, as in the case of an HTTP `URI:' header or |
2054 |
redirection transaction. |
2055 |
|
2056 |
|
2057 |
7.3. Simultaneous Presentation of Image Resources |
2058 |
|
2059 |
An HTML user agent may activate hyperlinks indicated by <IMG> |
2060 |
and <INPUT> elements concurrently with processing the document; |
2061 |
that is, image hyperlinks may be processed without explicit |
2062 |
request by the user. Image resources should be embedded in the |
2063 |
presentation at the point of the tail anchor, that is the <IMG> |
2064 |
|
2065 |
Berners-Lee, Connolly [Page 35] |
2066 |
|
2067 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2068 |
|
2069 |
or <INPUT> element. |
2070 |
|
2071 |
<LINK> hyperlinks may also be processed without explicit user |
2072 |
request; for example, style sheet resources may be processed |
2073 |
before or during the processing of the document. |
2074 |
|
2075 |
|
2076 |
7.4. Fragment Identifiers |
2077 |
|
2078 |
Any characters following a `#' character in a hypertext address |
2079 |
constitute a fragment identifier. In particular, an address of |
2080 |
the form `#fragment' refers to an anchor in the same document. |
2081 |
|
2082 |
The meaning of fragment identifiers depends on the media type of |
2083 |
the representation of the anchor's resource. For `text/html' |
2084 |
representations, it refers to the <A> element with a NAME |
2085 |
attribute whose value is the same as the fragment identifier. |
2086 |
The matching is case sensitive. The document should have exactly |
2087 |
one such element. The user agent should indicate the anchor |
2088 |
element, for example by scrolling to and/or highlighting the |
2089 |
phrase. |
2090 |
|
2091 |
For example, if the base URI is `http://host/x/y.html' and the |
2092 |
user activated the link denoted by the following markup: |
2093 |
|
2094 |
<p> See: <a href="app1.html#bananas">appendix 1</a> |
2095 |
for more detail on bananas. |
2096 |
|
2097 |
Then the user agent accesses the resource identified by |
2098 |
`http://host/x/app1.html'. Assuming the resource is represented |
2099 |
using the `text/html' media type, the user agent must locate the |
2100 |
<A> element whose NAME attribute is `bananas' and begin |
2101 |
navigation there. |
2102 |
|
2103 |
|
2104 |
7.5. Queries and Indexes |
2105 |
|
2106 |
The <ISINDEX> element represents a set of hyperlinks. The user |
2107 |
can choose from the set by providing keywords to the user agent. |
2108 |
The user agent computes the head URI by appending `?' and the |
2109 |
keywords to the base URI. The keywords are escaped according to |
2110 |
[URL] and joined by `+'. For example, if a document contains: |
2111 |
|
2112 |
<BASE HREF="http://host/index"> |
2113 |
<ISINDEX> |
2114 |
|
2115 |
and the user provides the keywords `apple' and `berry', then the |
2116 |
user agent must access the resource |
2117 |
`http://host/index?apple+berry'. |
2118 |
|
2119 |
<FORM> elements with `METHOD=GET' also represent sets of |
2120 |
hyperlinks. See 8.2.2, "Query Forms: METHOD=GET" for details. |
2121 |
|
2122 |
|
2123 |
|
2124 |
Berners-Lee, Connolly [Page 36] |
2125 |
|
2126 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2127 |
|
2128 |
7.6. Image Maps |
2129 |
|
2130 |
If the ISMAP attribute is present on an <IMG> element, the <IMG> |
2131 |
element must be contained in an <A> element with an HREF |
2132 |
present. This construct represents a set of hyperlinks. The user |
2133 |
can choose from the set by choosing a pixel of the image. The |
2134 |
user agent computes the head URI by appending `?' and the x and |
2135 |
y coordinates of the pixel to the URI given in the <A> element. |
2136 |
For example, if a document contains: |
2137 |
|
2138 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> |
2139 |
<head><title>ImageMap Example</title> |
2140 |
<BASE HREF="http://host/index"></head> |
2141 |
<body> |
2142 |
<p> Choose any of these icons:<br> |
2143 |
<a href="/cgi-bin/imagemap"><img ismap src="icons.gif"></a> |
2144 |
|
2145 |
and the user chooses the upper-leftmost pixel, the chosen |
2146 |
hyperlink is the one with the URI |
2147 |
`http://host/cgi-bin/imagemap?0,0'. |
2148 |
|
2149 |
|
2150 |
8. Forms |
2151 |
|
2152 |
A form is a template for a form data set and an associated |
2153 |
method and action URI. A form data set is a sequence of |
2154 |
name/value pair fields. The names are specified on the NAME |
2155 |
attributes of form input elements, and the values are given |
2156 |
initial values by various forms of markup and edited by the |
2157 |
user. The resulting form data set is used to access an |
2158 |
information service as a function of the action and method. |
2159 |
|
2160 |
Forms elements can be mixed in with document structuring |
2161 |
elements. For example, a <PRE> element may contain a <FORM> |
2162 |
element, or a <FORM> element may contain lists which contain |
2163 |
<INPUT> elements. This gives considerable flexibility in |
2164 |
designing the layout of forms. |
2165 |
|
2166 |
Form processing is a level 2 feature. |
2167 |
|
2168 |
|
2169 |
8.1. Form Elements |
2170 |
|
2171 |
|
2172 |
8.1.1. Form: FORM |
2173 |
|
2174 |
The <FORM> element contains a sequence of input elements, along |
2175 |
with document structuring elements. The attributes are: |
2176 |
|
2177 |
ACTION |
2178 |
specifies the action URI for the form. The action URI of |
2179 |
a form defaults to the base URI of the document (see 7, |
2180 |
"Hyperlinks"). |
2181 |
|
2182 |
|
2183 |
Berners-Lee, Connolly [Page 37] |
2184 |
|
2185 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2186 |
|
2187 |
METHOD |
2188 |
selects a method of accessing the action URI. The set of |
2189 |
applicable methods is a function of the scheme of the |
2190 |
action URI of the form. See 8.2.2, "Query Forms: |
2191 |
METHOD=GET" and 8.2.3, "Forms with Side-Effects: |
2192 |
METHOD=POST". |
2193 |
|
2194 |
ENCTYPE |
2195 |
specifies the media type used to encode the name/value |
2196 |
pairs for transport, in case the protocol does not |
2197 |
itself impose a format. See 8.2.1, "The form-urlencoded |
2198 |
Media Type". |
2199 |
|
2200 |
|
2201 |
8.1.2. Input Field: INPUT |
2202 |
|
2203 |
The <INPUT> element represents a field for user input. The TYPE |
2204 |
attribute discriminates between several variations of fields. |
2205 |
|
2206 |
The <INPUT> element has a number of attributes. The set of |
2207 |
applicable attributes depends on the value of the TYPE |
2208 |
attribute. |
2209 |
|
2210 |
|
2211 |
8.1.2.1. Text Field: INPUT TYPE=TEXT |
2212 |
|
2213 |
The default vaule of the TYPE attribute is `TEXT', indicating a |
2214 |
single line text entry fields. (Use the <TEXTAREA> element for |
2215 |
multi-line text fields.) |
2216 |
|
2217 |
Required attributes are: |
2218 |
|
2219 |
NAME |
2220 |
name for the form field corresponding to this element. |
2221 |
|
2222 |
The optional attriubtes are: |
2223 |
|
2224 |
MAXLENGTH |
2225 |
constrains the number of characters that can be entered |
2226 |
into a text input field. If the value of MAXLENGTH is |
2227 |
greater the the value of the SIZE attribute, the field |
2228 |
should scroll appropriately. The default number of |
2229 |
characters is unlimited. |
2230 |
|
2231 |
SIZE |
2232 |
specifies the amount of display space allocated to this |
2233 |
input field according to its type. The default depends |
2234 |
on the user agent. |
2235 |
|
2236 |
VALUE |
2237 |
The initial value of the field. |
2238 |
|
2239 |
For example: |
2240 |
|
2241 |
|
2242 |
Berners-Lee, Connolly [Page 38] |
2243 |
|
2244 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2245 |
|
2246 |
<p>Street Address: <input name=street><br> |
2247 |
Postal City code: <input name=city size=16 maxlength=16><br> |
2248 |
Zip Code: <input name=zip size=10 maxlength=10 value="99999-9999"><br> |
2249 |
|
2250 |
|
2251 |
8.1.2.2. Password Field: INPUT TYPE=PASSWORD |
2252 |
|
2253 |
An <INPUT> element with `TYPE=PASSWORD' is a text field as |
2254 |
above, except that the value is obscured as it is entered. (see |
2255 |
also: 10, "Security Considerations"). |
2256 |
|
2257 |
For example: |
2258 |
|
2259 |
<p>Name: <input name=login> Password: <input type=password name=passwd> |
2260 |
|
2261 |
|
2262 |
8.1.2.3. Check Box: INPUT TYPE=CHECKBOX |
2263 |
|
2264 |
An <INPUT> element with `TYPE=CHECKBOX' represents a boolean |
2265 |
choice. A set of such elements with the same name represents an |
2266 |
n-of-many choice field. Required attributes are: |
2267 |
|
2268 |
NAME |
2269 |
symbolic name for the form field corresponding to this |
2270 |
element or group of elements. |
2271 |
|
2272 |
VALUE |
2273 |
The portion of the value of the field contributed by |
2274 |
this element. |
2275 |
|
2276 |
Optional attributes are: |
2277 |
|
2278 |
CHECKED |
2279 |
indicates that the initial state is on. |
2280 |
|
2281 |
For example: |
2282 |
|
2283 |
<p>What flavors do you like? |
2284 |
<input type=checkbox name=flavor value=vanilla>Vanilla<br> |
2285 |
<input type=checkbox name=flavor value=strawberry>Strawberry<br> |
2286 |
<input type=checkbox name=flavor value=chocolate checked>Chocolate<br> |
2287 |
|
2288 |
|
2289 |
8.1.2.4. Radio Button: INPUT TYPE=RADIO |
2290 |
|
2291 |
An <INPUT> element with `TYPE=RADIO' represents a boolean |
2292 |
choice. A set of such elements with the same name represents a |
2293 |
1-of-many choice field. The NAME and VALUE attributes are |
2294 |
required as for check boxes. Optional attributes are: |
2295 |
|
2296 |
CHECKED |
2297 |
indicates that the initial state is on. |
2298 |
|
2299 |
At all times, exactly one of the radio buttons in a set is |
2300 |
|
2301 |
Berners-Lee, Connolly [Page 39] |
2302 |
|
2303 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2304 |
|
2305 |
checked. If none of the <INPUT> elements of a set of radio |
2306 |
buttons specifies `CHECKED', then the user agent must check the |
2307 |
first radio button of the set initially. |
2308 |
|
2309 |
For example: |
2310 |
|
2311 |
<p>Which is your favorite? |
2312 |
<input type=radio name=flavor value=vanilla>Vanilla<br> |
2313 |
<input type=radio name=flavor value=strawberry>Strawberry<br> |
2314 |
<input type=radio name=flavor value=chocolate>Chocolate<br> |
2315 |
|
2316 |
|
2317 |
8.1.2.5. Image Pixel: INPUT TYPE=IMAGE |
2318 |
|
2319 |
An <INPUT> element with `TYPE=IMAGE' specifies an image resource |
2320 |
to display, and allows input of two form fields: the x and y |
2321 |
coordinate of a pixel chosen from the image. The names of the |
2322 |
fields are the name of the field with `.x' and `.y' appended. |
2323 |
`TYPE=IMAGE' implies `TYPE=SUBMIT' processing; that is, when a |
2324 |
pixel is chosen, the form as a whole is submitted. |
2325 |
|
2326 |
The NAME attribute is required as for other input fields. The |
2327 |
SRC attribute is required and the ALIGN is optional as for the |
2328 |
<IMG> element (see 5.10, "Image: IMG"). |
2329 |
|
2330 |
For example: |
2331 |
|
2332 |
<p>Choose a point on the map: |
2333 |
<input type=image name=point src="map.gif"> |
2334 |
|
2335 |
|
2336 |
8.1.2.6. Hidden Field: INPUT TYPE=HIDDEN |
2337 |
|
2338 |
An <INPUT> element with `TYPE=HIDDEN' represents a hidden |
2339 |
field.The user does not interact with this field; instead, the |
2340 |
VALUE attribute specifies the value of the field. The NAME and |
2341 |
VALUE attributes are required. |
2342 |
|
2343 |
For example: |
2344 |
|
2345 |
<input type=hidden name=context value="l2k3j4l2k3j4l2k3j4lk23"> |
2346 |
|
2347 |
|
2348 |
8.1.2.7. Submit Button: INPUT TYPE=SUBMIT |
2349 |
|
2350 |
An <INPUT> element with `TYPE=SUBMIT' represents an input |
2351 |
option, typically a button, that instructs the user agent to |
2352 |
submit the form. Optional attributes are: |
2353 |
|
2354 |
NAME |
2355 |
indicates that this element contributes a form field |
2356 |
whose value is given by the VALUE attribute. If the NAME |
2357 |
attribute is not present, this element does not |
2358 |
contribute a form field. |
2359 |
|
2360 |
Berners-Lee, Connolly [Page 40] |
2361 |
|
2362 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2363 |
|
2364 |
|
2365 |
VALUE |
2366 |
indicates a label for the input (button). |
2367 |
|
2368 |
You may submit this request internally: |
2369 |
<input type=submit name=recipient value=internal><br> |
2370 |
or to the external world: |
2371 |
<input type=submit name=recipient value=world> |
2372 |
|
2373 |
|
2374 |
8.1.2.8. Reset Button: INPUT TYPE=RESET |
2375 |
|
2376 |
An <INPUT> element with `TYPE=RESET' represents an input option, |
2377 |
typically a button, that instructs the user agent to reset the |
2378 |
form's fields to their initial states. The VALUE attribute, if |
2379 |
present, indicates a label for the input (button). |
2380 |
|
2381 |
When you are finished, you may submit this request: |
2382 |
<input type=submit><br> |
2383 |
You may clear the form and start over at any time: <input type=reset> |
2384 |
|
2385 |
|
2386 |
8.1.3. Selection: SELECT |
2387 |
|
2388 |
The <SELECT> element constrains the form field to an enumerated |
2389 |
list of values. The values are given in <OPTION> elements. |
2390 |
Attributes are: |
2391 |
|
2392 |
MULTIPLE |
2393 |
indicates that more than one option may be included in |
2394 |
the value. |
2395 |
|
2396 |
NAME |
2397 |
specifies the name of the form field. |
2398 |
|
2399 |
SIZE |
2400 |
specifies the number of visible items. Select fields of |
2401 |
size one are typically pop-down menus, whereas select |
2402 |
fields with size greater than one are typically lists. |
2403 |
|
2404 |
For example: |
2405 |
|
2406 |
<SELECT NAME="flavor"> |
2407 |
<OPTION>Vanilla |
2408 |
<OPTION>Strawberry |
2409 |
<OPTION value="RumRasin">Rum and Raisin |
2410 |
<OPTION selected>Peach and Orange |
2411 |
</SELECT> |
2412 |
|
2413 |
The initial state has the first option selected, unless a |
2414 |
SELECTED attribute is present on any of the <OPTION> elements. |
2415 |
|
2416 |
|
2417 |
|
2418 |
|
2419 |
Berners-Lee, Connolly [Page 41] |
2420 |
|
2421 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2422 |
|
2423 |
8.1.3.1. Option: OPTION |
2424 |
|
2425 |
The Option element can only occur within a Select element. It |
2426 |
represents one choice, and has the following attributes: |
2427 |
|
2428 |
SELECTED |
2429 |
Indicates that this option is initially selected. |
2430 |
|
2431 |
VALUE |
2432 |
indicates the value to be returned if this option is |
2433 |
chosen. The field value defaults to the content of the |
2434 |
<OPTION> element. |
2435 |
|
2436 |
The content of the <OPTION> element is presented to the user to |
2437 |
represent the option. It is used as a returned value if the |
2438 |
VALUE attribute is not present. |
2439 |
|
2440 |
|
2441 |
8.1.4. Text Area: TEXTAREA |
2442 |
|
2443 |
The <TEXTAREA> element represents a multi-line text field. |
2444 |
Attributes are: |
2445 |
|
2446 |
COLS |
2447 |
the number of visible columns to display for the text |
2448 |
area, in characters. |
2449 |
|
2450 |
NAME |
2451 |
Specifies the name of the form field. |
2452 |
|
2453 |
ROWS |
2454 |
The number of visible rows to display for the text area, |
2455 |
in characters. |
2456 |
|
2457 |
For example: |
2458 |
|
2459 |
<TEXTAREA NAME="address" ROWS=6 COLS=64> |
2460 |
HaL Computer Systems |
2461 |
1315 Dell Avenue |
2462 |
Campbell, California 95008 |
2463 |
</TEXTAREA> |
2464 |
|
2465 |
The content of the <TEXTAREA> element is the field's initial |
2466 |
value. |
2467 |
|
2468 |
Typically, the ROWS and COLS attributes determine the visible |
2469 |
dimension of the field in characters. The field is typically |
2470 |
rendered in a fixed-width font. HTML user agents should allow |
2471 |
text to extend beyond these limits by scrolling as needed. |
2472 |
|
2473 |
|
2474 |
8.2. Form Submission |
2475 |
|
2476 |
An HTML user agent begins processing a form by presenting the |
2477 |
|
2478 |
Berners-Lee, Connolly [Page 42] |
2479 |
|
2480 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2481 |
|
2482 |
document with the fields in their initial state. The user is |
2483 |
allowed to modify the fields, constrained by the field type etc. |
2484 |
When the user indicates that the form should be submitted (using |
2485 |
a submit button or image input), the form data set is processed |
2486 |
according to its method, action URI and enctype. |
2487 |
|
2488 |
When there is only one single-line text input field in a form, |
2489 |
the user agent should accept Enter in that field as a request to |
2490 |
submit the form. |
2491 |
|
2492 |
|
2493 |
8.2.1. The form-urlencoded Media Type |
2494 |
|
2495 |
The default encoding for all forms is |
2496 |
`application/x-www-form-urlencoded'. A form data set is |
2497 |
represented in this media type as follows: |
2498 |
|
2499 |
1. The form field names and values are escaped: space |
2500 |
characters are replaced by `+', and then reserved characters |
2501 |
are escaped as per [URL]; that is, non-alphanumeric |
2502 |
characters are replaced by `%HH', a percent sign and two |
2503 |
hexadecimal digits representing the ASCII code of the |
2504 |
character. Line breaks, as in multi-line text field values, |
2505 |
are represented as CR LF pairs, i.e. `%0D%0A'. |
2506 |
|
2507 |
2. The fields are listed in the order they appear in the |
2508 |
document with the name separated from the value by `=' and |
2509 |
the pairs separated from each other by `&'. Fields with null |
2510 |
values may be omitted. In particular, unselected radio |
2511 |
buttons and checkboxes should not appear in the encoded |
2512 |
data, but hidden fields with VALUE attributes present |
2513 |
should. |
2514 |
|
2515 |
NOTE - The URI from a query form submission can be |
2516 |
used in a normal anchor style hyperlink. |
2517 |
Unfortunately, the use of the `&' character to |
2518 |
separate form fields interacts with its use in SGML |
2519 |
attribute values as an entity reference delimiter. |
2520 |
For example, the URI `http://host/?x=1&y=2' must be |
2521 |
written `<a href="http://host/?x=1&y=2"' or `<a |
2522 |
href="http://host/?x=1&y=2">'. |
2523 |
|
2524 |
HTTP server implementors, and in particular, CGI |
2525 |
implementors are encouraged to support the use of |
2526 |
`;' in place of `&' to save users the trouble of |
2527 |
escaping `&' characters this way. |
2528 |
|
2529 |
|
2530 |
8.2.2. Query Forms: METHOD=GET |
2531 |
|
2532 |
If the processing of a form is idempotent (i.e. it has no |
2533 |
lasting observable effect on the state of the world), then the |
2534 |
form method should be `GET'. Many database searches have no |
2535 |
visible side-effects and make ideal applications of query forms. |
2536 |
|
2537 |
Berners-Lee, Connolly [Page 43] |
2538 |
|
2539 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2540 |
|
2541 |
|
2542 |
To process a form whose action URL is an HTTP URL and whose |
2543 |
method is `GET', the user agent starts with the action URI and |
2544 |
appends a `?' and the form data set, in |
2545 |
`application/x-www-form-urlencoded' format as above. The user |
2546 |
agent then traverses the link to this URI just as if it were an |
2547 |
anchor (see 7.2, "Activation of Hyperlinks"). |
2548 |
|
2549 |
NOTE - The URL encoding may result in very long URIs, |
2550 |
which cause some historical HTTP server implementations |
2551 |
to exhibit defective behavior. As a result, some HTML |
2552 |
forms are written using `METHOD=POST' even though the |
2553 |
form submission has no side-effects. |
2554 |
|
2555 |
|
2556 |
8.2.3. Forms with Side-Effects: METHOD=POST |
2557 |
|
2558 |
If the service associated with the processing of a form has side |
2559 |
effects (for example, modification of a database or subscription |
2560 |
to a service), the method should be `POST'. |
2561 |
|
2562 |
To process a form whose action URL is an HTTP URL and whose |
2563 |
method is `POST', the user agent conducts an HTTP POST |
2564 |
transaction using the action URI, and a message body of type |
2565 |
`application/x-www-form-urlencoded' format as above. The user |
2566 |
agent should display the response from the HTTP POST interaction |
2567 |
just as it would display the response from an HTTP GET above. |
2568 |
|
2569 |
|
2570 |
8.2.4. Example Form Submission: Questionnaire Form |
2571 |
|
2572 |
Consider the following document: |
2573 |
|
2574 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> |
2575 |
<title>Sample of HTML Form Submission</title> |
2576 |
<H1>Sample Questionnaire</H1> |
2577 |
<P>Please fill out this questionnaire: |
2578 |
<FORM METHOD="POST" ACTION="http://www.w3.org/sample"> |
2579 |
<P>Your name: <INPUT NAME="name" size="48"> |
2580 |
<P>Male <INPUT NAME="gender" TYPE=RADIO VALUE="male"> |
2581 |
<P>Female <INPUT NAME="gender" TYPE=RADIO VALUE="female"> |
2582 |
<P>Number in family: <INPUT NAME="family" TYPE=text> |
2583 |
<P>Cities in which you maintain a residence: |
2584 |
<UL> |
2585 |
<LI>Kent <INPUT NAME="city" TYPE=checkbox VALUE="kent"> |
2586 |
<LI>Miami <INPUT NAME="city" TYPE=checkbox VALUE="miami"> |
2587 |
<LI>Other <TEXTAREA NAME="other" cols=48 rows=4></textarea> |
2588 |
</UL> |
2589 |
Nickname: <INPUT NAME="nickname" SIZE="42"> |
2590 |
<P>Thank you for responding to this questionnaire. |
2591 |
<P><INPUT TYPE=SUBMIT> <INPUT TYPE=RESET> |
2592 |
</FORM> |
2593 |
|
2594 |
The initial state of the form data set is: |
2595 |
|
2596 |
Berners-Lee, Connolly [Page 44] |
2597 |
|
2598 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2599 |
|
2600 |
|
2601 |
name |
2602 |
``'' |
2603 |
|
2604 |
gender |
2605 |
``male'' |
2606 |
|
2607 |
family |
2608 |
``'' |
2609 |
|
2610 |
other |
2611 |
``'' |
2612 |
|
2613 |
nickname |
2614 |
``'' |
2615 |
|
2616 |
Note that the radio input has an initial value, while the |
2617 |
checkbox has none. |
2618 |
|
2619 |
The user might edit the fields and request that the form be |
2620 |
submitted. At that point, suppose the values are: |
2621 |
|
2622 |
name |
2623 |
``John Doe'' |
2624 |
|
2625 |
gender |
2626 |
``male'' |
2627 |
|
2628 |
family |
2629 |
``5'' |
2630 |
|
2631 |
city |
2632 |
``kent'' |
2633 |
|
2634 |
city |
2635 |
``miami'' |
2636 |
|
2637 |
other |
2638 |
``abc\ndef'' |
2639 |
|
2640 |
nickname |
2641 |
``J&D'' |
2642 |
|
2643 |
The user agent then conducts an HTTP POST transaction using the |
2644 |
URI `http://www.w3.org/sample'. The message body would be |
2645 |
(ignore the line break): |
2646 |
|
2647 |
name=John+Doe&gender=male&family=5&city=kent&city=miami& |
2648 |
other=abc%0D%0Adef&nickname=J%26D |
2649 |
|
2650 |
|
2651 |
9. HTML Public Text |
2652 |
|
2653 |
|
2654 |
|
2655 |
Berners-Lee, Connolly [Page 45] |
2656 |
|
2657 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2658 |
|
2659 |
9.1. HTML DTD |
2660 |
|
2661 |
This is the Document Type Definition for the HyperText Markup |
2662 |
Language, level 2. |
2663 |
|
2664 |
<!-- html.dtd |
2665 |
|
2666 |
Document Type Definition for the HyperText Markup Language |
2667 |
(HTML DTD) |
2668 |
|
2669 |
$Id: html.dtd,v 1.29 1995/08/04 17:50:22 connolly Exp $ |
2670 |
|
2671 |
Author: Daniel W. Connolly <connolly@w3.org> |
2672 |
See Also: html.decl, html-1.dtd |
2673 |
http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html |
2674 |
- --> |
2675 |
|
2676 |
<!ENTITY % HTML.Version |
2677 |
"-//IETF//DTD HTML 2.0//EN" |
2678 |
|
2679 |
-- Typical usage: |
2680 |
|
2681 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> |
2682 |
<html> |
2683 |
... |
2684 |
</html> |
2685 |
-- |
2686 |
> |
2687 |
|
2688 |
|
2689 |
<!--============ Feature Test Entities ========================--> |
2690 |
|
2691 |
<!ENTITY % HTML.Recommended "IGNORE" |
2692 |
-- Certain features of the language are necessary for |
2693 |
compatibility with widespread usage, but they may |
2694 |
compromise the structural integrity of a document. |
2695 |
This feature test entity enables a more prescriptive |
2696 |
document type definition that eliminates |
2697 |
those features. |
2698 |
--> |
2699 |
|
2700 |
<![ %HTML.Recommended [ |
2701 |
<!ENTITY % HTML.Deprecated "IGNORE"> |
2702 |
]]> |
2703 |
|
2704 |
<!ENTITY % HTML.Deprecated "INCLUDE" |
2705 |
-- Certain features of the language are necessary for |
2706 |
compatibility with earlier versions of the specification, |
2707 |
but they tend to be used an implemented inconsistently, |
2708 |
and their use is deprecated. This feature test entity |
2709 |
enables a document type definition that eliminates |
2710 |
these features. |
2711 |
--> |
2712 |
|
2713 |
|
2714 |
Berners-Lee, Connolly [Page 46] |
2715 |
|
2716 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2717 |
|
2718 |
<!ENTITY % HTML.Highlighting "INCLUDE" |
2719 |
-- Use this feature test entity to validate that a |
2720 |
document uses no highlighting tags, which may be |
2721 |
ignored on minimal implementations. |
2722 |
--> |
2723 |
|
2724 |
<!ENTITY % HTML.Forms "INCLUDE" |
2725 |
-- Use this feature test entity to validate that a document |
2726 |
contains no forms, which may not be supported in minimal |
2727 |
implementations |
2728 |
--> |
2729 |
|
2730 |
<!--============== Imported Names ==============================--> |
2731 |
|
2732 |
<!ENTITY % Content-Type "CDATA" |
2733 |
-- meaning an internet media type |
2734 |
(aka MIME content type, as per RFC1521) |
2735 |
--> |
2736 |
|
2737 |
<!ENTITY % HTTP-Method "GET | POST" |
2738 |
-- as per HTTP specification, in progress |
2739 |
--> |
2740 |
|
2741 |
<!--========= DTD "Macros" =====================--> |
2742 |
|
2743 |
<!ENTITY % heading "H1|H2|H3|H4|H5|H6"> |
2744 |
|
2745 |
<!ENTITY % list " UL | OL | DIR | MENU " > |
2746 |
|
2747 |
|
2748 |
<!--======= Character mnemonic entities =================--> |
2749 |
|
2750 |
<!ENTITY % ISOlat1 PUBLIC |
2751 |
"ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML"> |
2752 |
%ISOlat1; |
2753 |
|
2754 |
<!ENTITY amp CDATA "&" -- ampersand --> |
2755 |
<!ENTITY gt CDATA ">" -- greater than --> |
2756 |
<!ENTITY lt CDATA "<" -- less than --> |
2757 |
<!ENTITY quot CDATA """ -- double quote --> |
2758 |
|
2759 |
|
2760 |
<!--========= SGML Document Access (SDA) Parameter Entities =====--> |
2761 |
|
2762 |
<!-- HTML 2.0 contains SGML Document Access (SDA) fixed attributes |
2763 |
in support of easy transformation to the International Committee |
2764 |
for Accessible Document Design (ICADD) DTD |
2765 |
"-//EC-USA-CDA/ICADD//DTD ICADD22//EN". |
2766 |
ICADD applications are designed to support usable access to |
2767 |
structured information by print-impaired individuals through |
2768 |
Braille, large print and voice synthesis. For more information on |
2769 |
SDA & ICADD: |
2770 |
- ISO 12083:1993, Annex A.8, Facilities for Braille, |
2771 |
large print and computer voice |
2772 |
|
2773 |
Berners-Lee, Connolly [Page 47] |
2774 |
|
2775 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2776 |
|
2777 |
- ICADD ListServ |
2778 |
<ICADD%ASUACAD.BITNET@ARIZVM1.ccit.arizona.edu> |
2779 |
- Usenet news group bit.listserv.easi |
2780 |
- Recording for the Blind, +1 800 221 4792 |
2781 |
- --> |
2782 |
|
2783 |
<!ENTITY % SDAFORM "SDAFORM CDATA #FIXED" |
2784 |
-- one to one mapping --> |
2785 |
<!ENTITY % SDARULE "SDARULE CDATA #FIXED" |
2786 |
-- context-sensitive mapping --> |
2787 |
<!ENTITY % SDAPREF "SDAPREF CDATA #FIXED" |
2788 |
-- generated text prefix --> |
2789 |
<!ENTITY % SDASUFF "SDASUFF CDATA #FIXED" |
2790 |
-- generated text suffix --> |
2791 |
<!ENTITY % SDASUSP "SDASUSP NAME #FIXED" |
2792 |
-- suspend transform process --> |
2793 |
|
2794 |
|
2795 |
<!--========== Text Markup =====================--> |
2796 |
|
2797 |
<![ %HTML.Highlighting [ |
2798 |
|
2799 |
<!ENTITY % font " TT | B | I "> |
2800 |
|
2801 |
<!ENTITY % phrase "EM | STRONG | CODE | SAMP | KBD | VAR | CITE "> |
2802 |
|
2803 |
<!ENTITY % text "#PCDATA | A | IMG | BR | %phrase | %font"> |
2804 |
|
2805 |
<!ELEMENT (%font;|%phrase) - - (%text)*> |
2806 |
<!ATTLIST ( TT | CODE | SAMP | KBD | VAR ) |
2807 |
%SDAFORM; "Lit" |
2808 |
> |
2809 |
<!ATTLIST ( B | STRONG ) |
2810 |
%SDAFORM; "B" |
2811 |
> |
2812 |
<!ATTLIST ( I | EM | CITE ) |
2813 |
%SDAFORM; "It" |
2814 |
> |
2815 |
|
2816 |
<!-- <TT> Typewriter text --> |
2817 |
<!-- <B> Bold text --> |
2818 |
<!-- <I> Italic text --> |
2819 |
|
2820 |
<!-- <EM> Emphasized phrase --> |
2821 |
<!-- <STRONG> Strong emphais --> |
2822 |
<!-- <CODE> Source code phrase --> |
2823 |
<!-- <SAMP> Sample text or characters --> |
2824 |
<!-- <KBD> Keyboard phrase, e.g. user input --> |
2825 |
<!-- <VAR> Variable phrase or substituable --> |
2826 |
<!-- <CITE> Name or title of cited work --> |
2827 |
|
2828 |
<!ENTITY % pre.content "#PCDATA | A | HR | BR | %font | %phrase"> |
2829 |
|
2830 |
]]> |
2831 |
|
2832 |
Berners-Lee, Connolly [Page 48] |
2833 |
|
2834 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2835 |
|
2836 |
|
2837 |
<!ENTITY % text "#PCDATA | A | IMG | BR"> |
2838 |
|
2839 |
<!ELEMENT BR - O EMPTY> |
2840 |
<!ATTLIST BR |
2841 |
%SDAPREF; "&#RE;" |
2842 |
> |
2843 |
|
2844 |
<!-- <BR> Line break --> |
2845 |
|
2846 |
|
2847 |
<!--========= Link Markup ======================--> |
2848 |
|
2849 |
<!ENTITY % linkType "NAMES"> |
2850 |
|
2851 |
<!ENTITY % linkExtraAttributes |
2852 |
"REL %linkType #IMPLIED |
2853 |
REV %linkType #IMPLIED |
2854 |
URN CDATA #IMPLIED |
2855 |
TITLE CDATA #IMPLIED |
2856 |
METHODS NAMES #IMPLIED |
2857 |
"> |
2858 |
|
2859 |
<![ %HTML.Recommended [ |
2860 |
<!ENTITY % A.content "(%text)*" |
2861 |
-- <H1><a name="xxx">Heading</a></H1> |
2862 |
is preferred to |
2863 |
<a name="xxx"><H1>Heading</H1></a> |
2864 |
--> |
2865 |
]]> |
2866 |
|
2867 |
<!ENTITY % A.content "(%heading|%text)*"> |
2868 |
|
2869 |
<!ELEMENT A - - %A.content -(A)> |
2870 |
<!ATTLIST A |
2871 |
HREF CDATA #IMPLIED |
2872 |
NAME CDATA #IMPLIED |
2873 |
%linkExtraAttributes; |
2874 |
%SDAPREF; "<Anchor: #AttList>" |
2875 |
> |
2876 |
<!-- <A> Anchor; source/destination of link --> |
2877 |
<!-- <A NAME="..."> Name of this anchor --> |
2878 |
<!-- <A HREF="..."> Address of link destination --> |
2879 |
<!-- <A URN="..."> Permanent address of destination --> |
2880 |
<!-- <A REL=...> Relationship to destination --> |
2881 |
<!-- <A REV=...> Relationship of destination to this --> |
2882 |
<!-- <A TITLE="..."> Title of destination (advisory) --> |
2883 |
<!-- <A METHODS="..."> Operations on destination (advisory) --> |
2884 |
|
2885 |
|
2886 |
<!--========== Images ==========================--> |
2887 |
|
2888 |
<!ELEMENT IMG - O EMPTY> |
2889 |
<!ATTLIST IMG |
2890 |
|
2891 |
Berners-Lee, Connolly [Page 49] |
2892 |
|
2893 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2894 |
|
2895 |
SRC CDATA #REQUIRED |
2896 |
ALT CDATA #IMPLIED |
2897 |
ALIGN (top|middle|bottom) #IMPLIED |
2898 |
ISMAP (ISMAP) #IMPLIED |
2899 |
%SDAPREF; "<Fig><?SDATrans Img: #AttList>#AttVal(Alt)</Fig>" |
2900 |
> |
2901 |
|
2902 |
<!-- <IMG> Image; icon, glyph or illustration --> |
2903 |
<!-- <IMG SRC="..."> Address of image object --> |
2904 |
<!-- <IMG ALT="..."> Textual alternative --> |
2905 |
<!-- <IMG ALIGN=...> Position relative to text --> |
2906 |
<!-- <IMG ISMAP> Each pixel can be a link --> |
2907 |
|
2908 |
<!--========== Paragraphs=======================--> |
2909 |
|
2910 |
<!ELEMENT P - O (%text)*> |
2911 |
<!ATTLIST P |
2912 |
%SDAFORM; "Para" |
2913 |
> |
2914 |
|
2915 |
<!-- <P> Paragraph --> |
2916 |
|
2917 |
|
2918 |
<!--========== Headings, Titles, Sections ===============--> |
2919 |
|
2920 |
<!ELEMENT HR - O EMPTY> |
2921 |
<!ATTLIST HR |
2922 |
%SDAPREF; "&#RE;&#RE;" |
2923 |
> |
2924 |
|
2925 |
<!-- <HR> Horizontal rule --> |
2926 |
|
2927 |
<!ELEMENT ( %heading ) - - (%text;)*> |
2928 |
<!ATTLIST H1 |
2929 |
%SDAFORM; "H1" |
2930 |
> |
2931 |
<!ATTLIST H2 |
2932 |
%SDAFORM; "H2" |
2933 |
> |
2934 |
<!ATTLIST H3 |
2935 |
%SDAFORM; "H3" |
2936 |
> |
2937 |
<!ATTLIST H4 |
2938 |
%SDAFORM; "H4" |
2939 |
> |
2940 |
<!ATTLIST H5 |
2941 |
%SDAFORM; "H5" |
2942 |
> |
2943 |
<!ATTLIST H6 |
2944 |
%SDAFORM; "H6" |
2945 |
> |
2946 |
|
2947 |
<!-- <H1> Heading, level 1 --> |
2948 |
<!-- <H2> Heading, level 2 --> |
2949 |
|
2950 |
Berners-Lee, Connolly [Page 50] |
2951 |
|
2952 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
2953 |
|
2954 |
<!-- <H3> Heading, level 3 --> |
2955 |
<!-- <H4> Heading, level 4 --> |
2956 |
<!-- <H5> Heading, level 5 --> |
2957 |
<!-- <H6> Heading, level 6 --> |
2958 |
|
2959 |
|
2960 |
<!--========== Text Flows ======================--> |
2961 |
|
2962 |
<![ %HTML.Forms [ |
2963 |
<!ENTITY % block.forms "BLOCKQUOTE | FORM | ISINDEX"> |
2964 |
]]> |
2965 |
|
2966 |
<!ENTITY % block.forms "BLOCKQUOTE"> |
2967 |
|
2968 |
<![ %HTML.Deprecated [ |
2969 |
<!ENTITY % preformatted "PRE | XMP | LISTING"> |
2970 |
]]> |
2971 |
|
2972 |
<!ENTITY % preformatted "PRE"> |
2973 |
|
2974 |
<!ENTITY % block "P | %list | DL |
2975 |
| %preformatted |
2976 |
| %block.forms"> |
2977 |
|
2978 |
<!ENTITY % flow "(%text|%block)*"> |
2979 |
|
2980 |
<!ENTITY % pre.content "#PCDATA | A | HR | BR"> |
2981 |
<!ELEMENT PRE - - (%pre.content)*> |
2982 |
<!ATTLIST PRE |
2983 |
WIDTH NUMBER #implied |
2984 |
%SDAFORM; "Lit" |
2985 |
> |
2986 |
|
2987 |
<!-- <PRE> Preformatted text --> |
2988 |
<!-- <PRE WIDTH=...> Maximum characters per line --> |
2989 |
|
2990 |
<![ %HTML.Deprecated [ |
2991 |
|
2992 |
<!ENTITY % literal "CDATA" |
2993 |
-- historical, non-conforming parsing mode where |
2994 |
the only markup signal is the end tag |
2995 |
in full |
2996 |
--> |
2997 |
|
2998 |
<!ELEMENT (XMP|LISTING) - - %literal> |
2999 |
<!ATTLIST XMP |
3000 |
%SDAFORM; "Lit" |
3001 |
%SDAPREF; "Example:&#RE;" |
3002 |
> |
3003 |
<!ATTLIST LISTING |
3004 |
%SDAFORM; "Lit" |
3005 |
%SDAPREF; "Listing:&#RE;" |
3006 |
> |
3007 |
|
3008 |
|
3009 |
Berners-Lee, Connolly [Page 51] |
3010 |
|
3011 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3012 |
|
3013 |
<!-- <XMP> Example section --> |
3014 |
<!-- <LISTING> Computer listing --> |
3015 |
|
3016 |
<!ELEMENT PLAINTEXT - O %literal> |
3017 |
<!-- <PLAINTEXT> Plain text passage --> |
3018 |
|
3019 |
<!ATTLIST PLAINTEXT |
3020 |
%SDAFORM; "Lit" |
3021 |
> |
3022 |
]]> |
3023 |
|
3024 |
|
3025 |
<!--========== Lists ==================--> |
3026 |
|
3027 |
<!ELEMENT DL - - (DT | DD)+> |
3028 |
<!ATTLIST DL |
3029 |
COMPACT (COMPACT) #IMPLIED |
3030 |
%SDAFORM; "List" |
3031 |
%SDAPREF; "Definition List:" |
3032 |
> |
3033 |
|
3034 |
<!ELEMENT DT - O (%text)*> |
3035 |
<!ATTLIST DT |
3036 |
%SDAFORM; "Term" |
3037 |
> |
3038 |
|
3039 |
<!ELEMENT DD - O %flow> |
3040 |
<!ATTLIST DD |
3041 |
%SDAFORM; "LItem" |
3042 |
> |
3043 |
|
3044 |
<!-- <DL> Definition list, or glossary --> |
3045 |
<!-- <DL COMPACT> Compact style list --> |
3046 |
<!-- <DT> Term in definition list --> |
3047 |
<!-- <DD> Definition of term --> |
3048 |
|
3049 |
<!ELEMENT (OL|UL) - - (LI)+> |
3050 |
<!ATTLIST OL |
3051 |
COMPACT (COMPACT) #IMPLIED |
3052 |
%SDAFORM; "List" |
3053 |
> |
3054 |
<!ATTLIST UL |
3055 |
COMPACT (COMPACT) #IMPLIED |
3056 |
%SDAFORM; "List" |
3057 |
> |
3058 |
<!-- <UL> Unordered list --> |
3059 |
<!-- <UL COMPACT> Compact list style --> |
3060 |
<!-- <OL> Ordered, or numbered list --> |
3061 |
<!-- <OL COMPACT> Compact list style --> |
3062 |
|
3063 |
|
3064 |
<!ELEMENT (DIR|MENU) - - (LI)+ -(%block)> |
3065 |
<!ATTLIST DIR |
3066 |
COMPACT (COMPACT) #IMPLIED |
3067 |
|
3068 |
Berners-Lee, Connolly [Page 52] |
3069 |
|
3070 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3071 |
|
3072 |
%SDAFORM; "List" |
3073 |
%SDAPREF; "<LHead>Directory</LHead>" |
3074 |
> |
3075 |
<!ATTLIST MENU |
3076 |
COMPACT (COMPACT) #IMPLIED |
3077 |
%SDAFORM; "List" |
3078 |
%SDAPREF; "<LHead>Menu</LHead>" |
3079 |
> |
3080 |
|
3081 |
<!-- <DIR> Directory list --> |
3082 |
<!-- <DIR COMPACT> Compact list style --> |
3083 |
<!-- <MENU> Menu list --> |
3084 |
<!-- <MENU COMPACT> Compact list style --> |
3085 |
|
3086 |
<!ELEMENT LI - O %flow> |
3087 |
<!ATTLIST LI |
3088 |
%SDAFORM; "LItem" |
3089 |
> |
3090 |
|
3091 |
<!-- <LI> List item --> |
3092 |
|
3093 |
<!--========== Document Body ===================--> |
3094 |
|
3095 |
<![ %HTML.Recommended [ |
3096 |
<!ENTITY % body.content "(%heading|%block|HR|ADDRESS|IMG)*" |
3097 |
-- <h1>Heading</h1> |
3098 |
<p>Text ... |
3099 |
is preferred to |
3100 |
<h1>Heading</h1> |
3101 |
Text ... |
3102 |
--> |
3103 |
]]> |
3104 |
|
3105 |
<!ENTITY % body.content "(%heading | %text | %block | |
3106 |
HR | ADDRESS)*"> |
3107 |
|
3108 |
<!ELEMENT BODY O O %body.content> |
3109 |
|
3110 |
<!-- <BODY> Document body --> |
3111 |
|
3112 |
<!ELEMENT BLOCKQUOTE - - %body.content> |
3113 |
<!ATTLIST BLOCKQUOTE |
3114 |
%SDAFORM; "BQ" |
3115 |
> |
3116 |
|
3117 |
<!-- <BLOCKQUOTE> Quoted passage --> |
3118 |
|
3119 |
<!ELEMENT ADDRESS - - (%text|P)*> |
3120 |
<!ATTLIST ADDRESS |
3121 |
%SDAFORM; "Lit" |
3122 |
%SDAPREF; "Address:&#RE;" |
3123 |
> |
3124 |
|
3125 |
<!-- <ADDRESS> Address, signature, or byline --> |
3126 |
|
3127 |
Berners-Lee, Connolly [Page 53] |
3128 |
|
3129 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3130 |
|
3131 |
|
3132 |
|
3133 |
<!--======= Forms ====================--> |
3134 |
|
3135 |
<![ %HTML.Forms [ |
3136 |
|
3137 |
<!ELEMENT FORM - - %body.content -(FORM) +(INPUT|SELECT|TEXTAREA)> |
3138 |
<!ATTLIST FORM |
3139 |
ACTION CDATA #IMPLIED |
3140 |
METHOD (%HTTP-Method) GET |
3141 |
ENCTYPE %Content-Type; "application/x-www-form-urlencoded" |
3142 |
%SDAPREF; "<Para>Form:</Para>" |
3143 |
%SDASUFF; "<Para>Form End.</Para>" |
3144 |
> |
3145 |
|
3146 |
<!-- <FORM> Fill-out or data-entry form --> |
3147 |
<!-- <FORM ACTION="..."> Address for completed form --> |
3148 |
<!-- <FORM METHOD=...> Method of submitting form --> |
3149 |
<!-- <FORM ENCTYPE="..."> Representation of form data --> |
3150 |
|
3151 |
<!ENTITY % InputType "(TEXT | PASSWORD | CHECKBOX | |
3152 |
RADIO | SUBMIT | RESET | |
3153 |
IMAGE | HIDDEN )"> |
3154 |
<!ELEMENT INPUT - O EMPTY> |
3155 |
<!ATTLIST INPUT |
3156 |
TYPE %InputType TEXT |
3157 |
NAME CDATA #IMPLIED |
3158 |
VALUE CDATA #IMPLIED |
3159 |
SRC CDATA #IMPLIED |
3160 |
CHECKED (CHECKED) #IMPLIED |
3161 |
SIZE CDATA #IMPLIED |
3162 |
MAXLENGTH NUMBER #IMPLIED |
3163 |
ALIGN (top|middle|bottom) #IMPLIED |
3164 |
%SDAPREF; "Input: " |
3165 |
> |
3166 |
|
3167 |
<!-- <INPUT> Form input datum --> |
3168 |
<!-- <INPUT TYPE=...> Type of input interaction --> |
3169 |
<!-- <INPUT NAME=...> Name of form datum --> |
3170 |
<!-- <INPUT VALUE="..."> Default/initial/selected value --> |
3171 |
<!-- <INPUT SRC="..."> Address of image --> |
3172 |
<!-- <INPUT CHECKED> Initial state is "on" --> |
3173 |
<!-- <INPUT SIZE=...> Field size hint --> |
3174 |
<!-- <INPUT MAXLENGTH=...> Data length maximum --> |
3175 |
<!-- <INPUT ALIGN=...> Image alignment --> |
3176 |
|
3177 |
<!ELEMENT SELECT - - (OPTION+) -(INPUT|SELECT|TEXTAREA)> |
3178 |
<!ATTLIST SELECT |
3179 |
NAME CDATA #REQUIRED |
3180 |
SIZE NUMBER #IMPLIED |
3181 |
MULTIPLE (MULTIPLE) #IMPLIED |
3182 |
%SDAFORM; "List" |
3183 |
%SDAPREF; |
3184 |
"<LHead>Select #AttVal(Multiple)</LHead>" |
3185 |
|
3186 |
Berners-Lee, Connolly [Page 54] |
3187 |
|
3188 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3189 |
|
3190 |
> |
3191 |
|
3192 |
<!-- <SELECT> Selection of option(s) --> |
3193 |
<!-- <SELECT NAME=...> Name of form datum --> |
3194 |
<!-- <SELECT SIZE=...> Options displayed at a time --> |
3195 |
<!-- <SELECT MULTIPLE> Multiple selections allowed --> |
3196 |
|
3197 |
<!ELEMENT OPTION - O (#PCDATA)*> |
3198 |
<!ATTLIST OPTION |
3199 |
SELECTED (SELECTED) #IMPLIED |
3200 |
VALUE CDATA #IMPLIED |
3201 |
%SDAFORM; "LItem" |
3202 |
%SDAPREF; |
3203 |
"Option: #AttVal(Value) #AttVal(Selected)" |
3204 |
> |
3205 |
|
3206 |
<!-- <OPTION> A selection option --> |
3207 |
<!-- <OPTION SELECTED> Initial state --> |
3208 |
<!-- <OPTION VALUE="..."> Form datum value for this option--> |
3209 |
|
3210 |
<!ELEMENT TEXTAREA - - (#PCDATA)* -(INPUT|SELECT|TEXTAREA)> |
3211 |
<!ATTLIST TEXTAREA |
3212 |
NAME CDATA #REQUIRED |
3213 |
ROWS NUMBER #REQUIRED |
3214 |
COLS NUMBER #REQUIRED |
3215 |
%SDAFORM; "Para" |
3216 |
%SDAPREF; "Input Text -- #AttVal(Name): " |
3217 |
> |
3218 |
|
3219 |
<!-- <TEXTAREA> An area for text input --> |
3220 |
<!-- <TEXTAREA NAME=...> Name of form datum --> |
3221 |
<!-- <TEXTAREA ROWS=...> Height of area --> |
3222 |
<!-- <TEXTAREA COLS=...> Width of area --> |
3223 |
|
3224 |
]]> |
3225 |
|
3226 |
|
3227 |
<!--======= Document Head ======================--> |
3228 |
|
3229 |
<![ %HTML.Recommended [ |
3230 |
<!ENTITY % head.extra ""> |
3231 |
]]> |
3232 |
<!ENTITY % head.extra "& NEXTID?"> |
3233 |
|
3234 |
<!ENTITY % head.content "TITLE & ISINDEX? & BASE? %head.extra"> |
3235 |
|
3236 |
<!ELEMENT HEAD O O (%head.content) +(META|LINK)> |
3237 |
|
3238 |
<!-- <HEAD> Document head --> |
3239 |
|
3240 |
<!ELEMENT TITLE - - (#PCDATA)*> |
3241 |
<!ATTLIST TITLE |
3242 |
%SDAFORM; "Ti" > |
3243 |
|
3244 |
|
3245 |
Berners-Lee, Connolly [Page 55] |
3246 |
|
3247 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3248 |
|
3249 |
<!-- <TITLE> Title of document --> |
3250 |
|
3251 |
<!ELEMENT LINK - O EMPTY> |
3252 |
<!ATTLIST LINK |
3253 |
HREF CDATA #REQUIRED |
3254 |
%linkExtraAttributes; |
3255 |
%SDAPREF; "Linked to : #AttVal (TITLE) (URN) (HREF)>" > |
3256 |
|
3257 |
<!-- <LINK> Link from this document --> |
3258 |
<!-- <LINK HREF="..."> Address of link destination --> |
3259 |
<!-- <LINK URN="..."> Lasting name of destination --> |
3260 |
<!-- <LINK REL=...> Relationship to destination --> |
3261 |
<!-- <LINK REV=...> Relationship of destination to this --> |
3262 |
<!-- <LINK TITLE="..."> Title of destination (advisory) --> |
3263 |
<!-- <LINK METHODS="..."> Operations allowed (advisory) --> |
3264 |
|
3265 |
<!ELEMENT ISINDEX - O EMPTY> |
3266 |
<!ATTLIST ISINDEX |
3267 |
%SDAPREF; |
3268 |
"<Para>[Document is indexed/searchable.]</Para>"> |
3269 |
|
3270 |
<!-- <ISINDEX> Document is a searchable index --> |
3271 |
|
3272 |
<!ELEMENT BASE - O EMPTY> |
3273 |
<!ATTLIST BASE |
3274 |
HREF CDATA #REQUIRED > |
3275 |
|
3276 |
<!-- <BASE> Base context document --> |
3277 |
<!-- <BASE HREF="..."> Address for this document --> |
3278 |
|
3279 |
<!ELEMENT NEXTID - O EMPTY> |
3280 |
<!ATTLIST NEXTID |
3281 |
N CDATA #REQUIRED > |
3282 |
|
3283 |
<!-- <NEXTID> Next ID to use for link name --> |
3284 |
<!-- <NEXTID N=...> Next ID to use for link name --> |
3285 |
|
3286 |
<!ELEMENT META - O EMPTY> |
3287 |
<!ATTLIST META |
3288 |
HTTP-EQUIV NAME #IMPLIED |
3289 |
NAME NAME #IMPLIED |
3290 |
CONTENT CDATA #REQUIRED > |
3291 |
|
3292 |
<!-- <META> Generic Metainformation --> |
3293 |
<!-- <META HTTP-EQUIV=...> HTTP response header name --> |
3294 |
<!-- <META NAME=...> Metainformation name --> |
3295 |
<!-- <META CONTENT="..."> Associated information --> |
3296 |
|
3297 |
<!--======= Document Structure =================--> |
3298 |
|
3299 |
<![ %HTML.Deprecated [ |
3300 |
<!ENTITY % html.content "HEAD, BODY, PLAINTEXT?"> |
3301 |
]]> |
3302 |
<!ENTITY % html.content "HEAD, BODY"> |
3303 |
|
3304 |
Berners-Lee, Connolly [Page 56] |
3305 |
|
3306 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3307 |
|
3308 |
|
3309 |
<!ELEMENT HTML O O (%html.content)> |
3310 |
<!ENTITY % version.attr "VERSION CDATA #FIXED '%HTML.Version;'"> |
3311 |
|
3312 |
<!ATTLIST HTML |
3313 |
%version.attr; |
3314 |
%SDAFORM; "Book" |
3315 |
> |
3316 |
|
3317 |
<!-- <HTML> HTML Document --> |
3318 |
|
3319 |
|
3320 |
9.2. Strict HTML DTD |
3321 |
|
3322 |
This document type declaration refers to the HTML DTD with the |
3323 |
`HTML.Recommended' entity defined as `INCLUDE' rather than |
3324 |
IGNORE; that is, it refers to the more structurally rigid |
3325 |
definition of HTML. |
3326 |
|
3327 |
<!-- html-s.dtd |
3328 |
|
3329 |
Document Type Definition for the HyperText Markup Language |
3330 |
with strict validation (HTML Strict DTD). |
3331 |
|
3332 |
$Id: html-s.dtd,v 1.3 1995/06/02 18:55:46 connolly Exp $ |
3333 |
|
3334 |
Author: Daniel W. Connolly <connolly@w3.org> |
3335 |
See Also: http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html |
3336 |
- --> |
3337 |
|
3338 |
<!ENTITY % HTML.Version |
3339 |
"-//IETF//DTD HTML 2.0 Strict//EN" |
3340 |
|
3341 |
-- Typical usage: |
3342 |
|
3343 |
<!DOCTYPE HTML PUBLIC |
3344 |
"-//IETF//DTD HTML Strict//EN"> |
3345 |
<html> |
3346 |
... |
3347 |
</html> |
3348 |
-- |
3349 |
> |
3350 |
|
3351 |
<!-- Feature Test Entities --> |
3352 |
<!ENTITY % HTML.Recommended "INCLUDE"> |
3353 |
|
3354 |
<!ENTITY % html PUBLIC "-//IETF//DTD HTML 2.0//EN"> |
3355 |
%html; |
3356 |
|
3357 |
|
3358 |
9.3. Level 1 HTML DTD |
3359 |
|
3360 |
This document type declaration refers to the HTML DTD with the |
3361 |
`HTML.Forms' entity defined as `IGNORE' rather than `INCLUDE'. |
3362 |
|
3363 |
Berners-Lee, Connolly [Page 57] |
3364 |
|
3365 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3366 |
|
3367 |
Documents which contain <FORM> elements do not conform to this |
3368 |
DTD, and must use the level 2 DTD. |
3369 |
|
3370 |
<!-- html-1.dtd |
3371 |
|
3372 |
Document Type Definition for the HyperText Markup Language |
3373 |
with Level 1 Extensions (HTML Level 1 DTD). |
3374 |
|
3375 |
$Id: html-1.dtd,v 1.2 1995/03/29 18:53:10 connolly Exp $ |
3376 |
|
3377 |
Author: Daniel W. Connolly <connolly@w3.org> |
3378 |
See Also: http://info.cern.ch/hypertext/WWW/MarkUp/MarkUp.html |
3379 |
- --> |
3380 |
|
3381 |
<!ENTITY % HTML.Version |
3382 |
"-//IETF//DTD HTML 2.0 Level 1//EN" |
3383 |
|
3384 |
-- Typical usage: |
3385 |
|
3386 |
<!DOCTYPE HTML PUBLIC |
3387 |
"-//IETF//DTD HTML Level 1//EN"> |
3388 |
<html> |
3389 |
... |
3390 |
</html> |
3391 |
-- |
3392 |
> |
3393 |
|
3394 |
<!-- Feature Test Entities --> |
3395 |
<!ENTITY % HTML.Forms "IGNORE"> |
3396 |
|
3397 |
<!ENTITY % html PUBLIC "-//IETF//DTD HTML 2.0//EN"> |
3398 |
%html; |
3399 |
|
3400 |
|
3401 |
9.4. Strict Level 1 HTML DTD |
3402 |
|
3403 |
This document type declaration refers to the level 1 HTML DTD |
3404 |
with the `HTML.Recommended' entity defined as `INCLUDE' rather |
3405 |
than IGNORE; that is, it refers to the more structurally rigid |
3406 |
definition of HTML. |
3407 |
|
3408 |
<!-- html-1s.dtd |
3409 |
|
3410 |
Document Type Definition for the HyperText Markup Language |
3411 |
Struct Level 1 |
3412 |
|
3413 |
$Id: html-1s.dtd,v 1.3 1995/06/02 18:55:43 connolly Exp $ |
3414 |
|
3415 |
Author: Daniel W. Connolly <connolly@w3.org> |
3416 |
See Also: http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html |
3417 |
- --> |
3418 |
|
3419 |
<!ENTITY % HTML.Version |
3420 |
"-//IETF//DTD HTML 2.0 Strict Level 1//EN" |
3421 |
|
3422 |
Berners-Lee, Connolly [Page 58] |
3423 |
|
3424 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3425 |
|
3426 |
|
3427 |
-- Typical usage: |
3428 |
|
3429 |
<!DOCTYPE HTML PUBLIC |
3430 |
"-//IETF//DTD HTML Strict Level 1//EN"> |
3431 |
<html> |
3432 |
... |
3433 |
</html> |
3434 |
-- |
3435 |
> |
3436 |
|
3437 |
<!-- Feature Test Entities --> |
3438 |
<!ENTITY % HTML.Recommended "INCLUDE"> |
3439 |
|
3440 |
<!ENTITY % html-1 PUBLIC "-//IETF//DTD HTML 2.0 Level 1//EN"> |
3441 |
%html-1; |
3442 |
|
3443 |
|
3444 |
9.5. SGML Declaration for HTML |
3445 |
|
3446 |
This is the SGML Declaration for HyperText Markup Language. |
3447 |
|
3448 |
<!SGML "ISO 8879:1986" |
3449 |
- -- |
3450 |
SGML Declaration for HyperText Markup Language (HTML). |
3451 |
|
3452 |
- -- |
3453 |
|
3454 |
CHARSET |
3455 |
BASESET "ISO 646:1983//CHARSET |
3456 |
International Reference Version |
3457 |
(IRV)//ESC 2/5 4/0" |
3458 |
DESCSET 0 9 UNUSED |
3459 |
9 2 9 |
3460 |
11 2 UNUSED |
3461 |
13 1 13 |
3462 |
14 18 UNUSED |
3463 |
32 95 32 |
3464 |
127 1 UNUSED |
3465 |
BASESET "ISO Registration Number 100//CHARSET |
3466 |
ECMA-94 Right Part of |
3467 |
Latin Alphabet Nr. 1//ESC 2/13 4/1" |
3468 |
|
3469 |
DESCSET 128 32 UNUSED |
3470 |
160 96 32 |
3471 |
|
3472 |
CAPACITY SGMLREF |
3473 |
TOTALCAP 150000 |
3474 |
GRPCAP 150000 |
3475 |
ENTCAP 150000 |
3476 |
|
3477 |
SCOPE DOCUMENT |
3478 |
SYNTAX |
3479 |
SHUNCHAR CONTROLS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
3480 |
|
3481 |
Berners-Lee, Connolly [Page 59] |
3482 |
|
3483 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3484 |
|
3485 |
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 127 |
3486 |
BASESET "ISO 646:1983//CHARSET |
3487 |
International Reference Version |
3488 |
(IRV)//ESC 2/5 4/0" |
3489 |
DESCSET 0 128 0 |
3490 |
FUNCTION |
3491 |
RE 13 |
3492 |
RS 10 |
3493 |
SPACE 32 |
3494 |
TAB SEPCHAR 9 |
3495 |
|
3496 |
|
3497 |
NAMING LCNMSTRT "" |
3498 |
UCNMSTRT "" |
3499 |
LCNMCHAR ".-" |
3500 |
UCNMCHAR ".-" |
3501 |
NAMECASE GENERAL YES |
3502 |
ENTITY NO |
3503 |
DELIM GENERAL SGMLREF |
3504 |
SHORTREF SGMLREF |
3505 |
NAMES SGMLREF |
3506 |
QUANTITY SGMLREF |
3507 |
ATTSPLEN 2100 |
3508 |
LITLEN 1024 |
3509 |
NAMELEN 72 -- somewhat arbitrary; taken from |
3510 |
internet line length conventions -- |
3511 |
PILEN 1024 |
3512 |
TAGLVL 100 |
3513 |
TAGLEN 2100 |
3514 |
GRPGTCNT 150 |
3515 |
GRPCNT 64 |
3516 |
|
3517 |
FEATURES |
3518 |
MINIMIZE |
3519 |
DATATAG NO |
3520 |
OMITTAG YES |
3521 |
RANK NO |
3522 |
SHORTTAG YES |
3523 |
LINK |
3524 |
SIMPLE NO |
3525 |
IMPLICIT NO |
3526 |
EXPLICIT NO |
3527 |
OTHER |
3528 |
CONCUR NO |
3529 |
SUBDOC NO |
3530 |
FORMAL YES |
3531 |
APPINFO "SDA" -- conforming SGML Document Access application |
3532 |
-- |
3533 |
> |
3534 |
<!-- |
3535 |
$Id: html.decl,v 1.17 1995/06/08 14:59:32 connolly Exp $ |
3536 |
|
3537 |
Author: Daniel W. Connolly <connolly@w3.org> |
3538 |
|
3539 |
|
3540 |
Berners-Lee, Connolly [Page 60] |
3541 |
|
3542 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3543 |
|
3544 |
See also: http://www.w3.org/hypertext/WWW/MarkUp/MarkUp.html |
3545 |
--> |
3546 |
|
3547 |
|
3548 |
9.6. Sample SGML Open Entity Catalog for HTML |
3549 |
|
3550 |
The SGML standard describes an ``entity manager'' as the portion |
3551 |
or component of an SGML system that maps SGML entities into the |
3552 |
actual storage model (e.g., the file system). The standard |
3553 |
itself does not define a particular mapping methodology or |
3554 |
notation. |
3555 |
|
3556 |
To assist the interoperability among various SGML tools and |
3557 |
systems, the SGML Open consortium has passed a technical |
3558 |
resolution that defines a format for an application- independent |
3559 |
entity catalog that maps external identifiers and/or entity |
3560 |
names to file names. |
3561 |
|
3562 |
Each entry in the catalog associates a storage object identifier |
3563 |
(such as a file name) with information about the external entity |
3564 |
that appears in the SGML document. In addition to entries that |
3565 |
associate public identifiers, a catalog entry can associate an |
3566 |
entity name with a storage object identifier. For example, the |
3567 |
following are possible catalog entries: |
3568 |
|
3569 |
-- catalog: SGML Open style entity catalog for HTML -- |
3570 |
-- $Id: catalog,v 1.2 1994/11/30 23:45:18 connolly Exp $ -- |
3571 |
|
3572 |
-- Ways to refer to Level 2: most general to most specific -- |
3573 |
PUBLIC "-//IETF//DTD HTML//EN" html.dtd |
3574 |
PUBLIC "-//IETF//DTD HTML 2.0//EN" html.dtd |
3575 |
PUBLIC "-//IETF//DTD HTML Level 2//EN" html.dtd |
3576 |
PUBLIC "-//IETF//DTD HTML 2.0 Level 2//EN" html.dtd |
3577 |
|
3578 |
-- Ways to refer to Level 1: most general to most specific -- |
3579 |
PUBLIC "-//IETF//DTD HTML Level 1//EN" html-1.dtd |
3580 |
PUBLIC "-//IETF//DTD HTML 2.0 Level 1//EN" html-1.dtd |
3581 |
|
3582 |
-- Ways to refer to Level 0: most general to most specific -- |
3583 |
PUBLIC "-//IETF//DTD HTML Level 0//EN" html-0.dtd |
3584 |
PUBLIC "-//IETF//DTD HTML 2.0 Level 0//EN" html-0.dtd |
3585 |
|
3586 |
|
3587 |
-- Ways to refer to Strict Level 2: most general to most specif\ |
3588 |
c -- |
3589 |
PUBLIC "-//IETF//DTD HTML Strict//EN" html-s.dtd |
3590 |
PUBLIC "-//IETF//DTD HTML 2.0 Strict//EN" html-s.dtd |
3591 |
PUBLIC "-//IETF//DTD HTML Strict Level 2//EN" html-s.dtd |
3592 |
PUBLIC "-//IETF//DTD HTML 2.0 Strict Level 2//EN" html-s.dtd |
3593 |
|
3594 |
-- Ways to refer to Strict Level 1: most general to most specif\ |
3595 |
c -- |
3596 |
PUBLIC "-//IETF//DTD HTML Strict Level 1//EN" html-1s.dtd |
3597 |
PUBLIC "-//IETF//DTD HTML 2.0 Strict Level 1//EN" html-1s.dtd |
3598 |
|
3599 |
Berners-Lee, Connolly [Page 61] |
3600 |
|
3601 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3602 |
|
3603 |
|
3604 |
-- Ways to refer to Strict Level 0: most general to most specif\ |
3605 |
c -- |
3606 |
PUBLIC "-//IETF//DTD HTML Strict Level 0//EN" html-0s.dtd |
3607 |
PUBLIC "-//IETF//DTD HTML 2.0 Strict Level 0//EN" html-0s.dtd |
3608 |
|
3609 |
-- ISO latin 1 entity set for HTML -- |
3610 |
PUBLIC "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML" ISOlat1\ |
3611 |
sgml |
3612 |
|
3613 |
|
3614 |
9.7. Character Entity Sets |
3615 |
|
3616 |
The HTML DTD defines the following entities. They represent |
3617 |
particular graphic characters which have special meanings in |
3618 |
places in the markup, or may not be part of the character set |
3619 |
available to the writer. |
3620 |
|
3621 |
|
3622 |
9.7.1. Numeric and Special Graphic Entity Set |
3623 |
|
3624 |
The following table lists each of the characters included from |
3625 |
the Numeric and Special Graphic entity set, along with its name, |
3626 |
syntax for use, and description. This list is derived from `ISO |
3627 |
Standard 8879:1986//ENTITIES Numeric and Special Graphic//EN'. |
3628 |
However, HTML does not include for the entire entity set -- only |
3629 |
the entities listed below are included. |
3630 |
|
3631 |
GLYPH NAME SYNTAX DESCRIPTION |
3632 |
< lt < Less than sign |
3633 |
> gt > Greater than sign |
3634 |
& amp & Ampersand |
3635 |
" quot " Double quote sign |
3636 |
|
3637 |
|
3638 |
9.7.2. ISO Latin 1 Character Entity Set |
3639 |
|
3640 |
The following public text lists each of the characters specified |
3641 |
in the Added Latin 1 entity set, along with its name, syntax for |
3642 |
use, and description. This list is derived from ISO Standard |
3643 |
8879:1986//ENTITIES Added Latin 1//EN. HTML includes the entire |
3644 |
entity set. |
3645 |
|
3646 |
<!-- (C) International Organization for Standardization 1986 |
3647 |
Permission to copy in any form is granted for use with |
3648 |
conforming SGML systems and applications as defined in |
3649 |
ISO 8879, provided this notice is included in all copies. |
3650 |
- --> |
3651 |
<!-- Character entity set. Typical invocation: |
3652 |
<!ENTITY % ISOlat1 PUBLIC |
3653 |
"ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML"> |
3654 |
%ISOlat1; |
3655 |
- --> |
3656 |
<!-- Modified for use in HTML |
3657 |
|
3658 |
Berners-Lee, Connolly [Page 62] |
3659 |
|
3660 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3661 |
|
3662 |
$Id: ISOlat1.sgml,v 1.2 1994/11/30 23:45:12 connolly Exp $ --> |
3663 |
<!ENTITY AElig CDATA "Æ" -- capital AE diphthong (ligature) --> |
3664 |
<!ENTITY Aacute CDATA "Á" -- capital A, acute accent --> |
3665 |
<!ENTITY Acirc CDATA "Â" -- capital A, circumflex accent --> |
3666 |
<!ENTITY Agrave CDATA "À" -- capital A, grave accent --> |
3667 |
<!ENTITY Aring CDATA "Å" -- capital A, ring --> |
3668 |
<!ENTITY Atilde CDATA "Ã" -- capital A, tilde --> |
3669 |
<!ENTITY Auml CDATA "Ä" -- capital A, dieresis or umlaut mark --> |
3670 |
<!ENTITY Ccedil CDATA "Ç" -- capital C, cedilla --> |
3671 |
<!ENTITY ETH CDATA "Ð" -- capital Eth, Icelandic --> |
3672 |
<!ENTITY Eacute CDATA "É" -- capital E, acute accent --> |
3673 |
<!ENTITY Ecirc CDATA "Ê" -- capital E, circumflex accent --> |
3674 |
<!ENTITY Egrave CDATA "È" -- capital E, grave accent --> |
3675 |
<!ENTITY Euml CDATA "Ë" -- capital E, dieresis or umlaut mark --> |
3676 |
<!ENTITY Iacute CDATA "Í" -- capital I, acute accent --> |
3677 |
<!ENTITY Icirc CDATA "Î" -- capital I, circumflex accent --> |
3678 |
<!ENTITY Igrave CDATA "Ì" -- capital I, grave accent --> |
3679 |
<!ENTITY Iuml CDATA "Ï" -- capital I, dieresis or umlaut mark --> |
3680 |
<!ENTITY Ntilde CDATA "Ñ" -- capital N, tilde --> |
3681 |
<!ENTITY Oacute CDATA "Ó" -- capital O, acute accent --> |
3682 |
<!ENTITY Ocirc CDATA "Ô" -- capital O, circumflex accent --> |
3683 |
<!ENTITY Ograve CDATA "Ò" -- capital O, grave accent --> |
3684 |
<!ENTITY Oslash CDATA "Ø" -- capital O, slash --> |
3685 |
<!ENTITY Otilde CDATA "Õ" -- capital O, tilde --> |
3686 |
<!ENTITY Ouml CDATA "Ö" -- capital O, dieresis or umlaut mark --> |
3687 |
<!ENTITY THORN CDATA "Þ" -- capital THORN, Icelandic --> |
3688 |
<!ENTITY Uacute CDATA "Ú" -- capital U, acute accent --> |
3689 |
<!ENTITY Ucirc CDATA "Û" -- capital U, circumflex accent --> |
3690 |
<!ENTITY Ugrave CDATA "Ù" -- capital U, grave accent --> |
3691 |
<!ENTITY Uuml CDATA "Ü" -- capital U, dieresis or umlaut mark --> |
3692 |
<!ENTITY Yacute CDATA "Ý" -- capital Y, acute accent --> |
3693 |
<!ENTITY aacute CDATA "á" -- small a, acute accent --> |
3694 |
<!ENTITY acirc CDATA "â" -- small a, circumflex accent --> |
3695 |
<!ENTITY aelig CDATA "æ" -- small ae diphthong (ligature) --> |
3696 |
<!ENTITY agrave CDATA "à" -- small a, grave accent --> |
3697 |
<!ENTITY aring CDATA "å" -- small a, ring --> |
3698 |
<!ENTITY atilde CDATA "ã" -- small a, tilde --> |
3699 |
<!ENTITY auml CDATA "ä" -- small a, dieresis or umlaut mark --> |
3700 |
<!ENTITY ccedil CDATA "ç" -- small c, cedilla --> |
3701 |
<!ENTITY eacute CDATA "é" -- small e, acute accent --> |
3702 |
<!ENTITY ecirc CDATA "ê" -- small e, circumflex accent --> |
3703 |
<!ENTITY egrave CDATA "è" -- small e, grave accent --> |
3704 |
<!ENTITY eth CDATA "ð" -- small eth, Icelandic --> |
3705 |
<!ENTITY euml CDATA "ë" -- small e, dieresis or umlaut mark --> |
3706 |
<!ENTITY iacute CDATA "í" -- small i, acute accent --> |
3707 |
<!ENTITY icirc CDATA "î" -- small i, circumflex accent --> |
3708 |
<!ENTITY igrave CDATA "ì" -- small i, grave accent --> |
3709 |
<!ENTITY iuml CDATA "ï" -- small i, dieresis or umlaut mark --> |
3710 |
<!ENTITY ntilde CDATA "ñ" -- small n, tilde --> |
3711 |
<!ENTITY oacute CDATA "ó" -- small o, acute accent --> |
3712 |
<!ENTITY ocirc CDATA "ô" -- small o, circumflex accent --> |
3713 |
<!ENTITY ograve CDATA "ò" -- small o, grave accent --> |
3714 |
<!ENTITY oslash CDATA "ø" -- small o, slash --> |
3715 |
<!ENTITY otilde CDATA "õ" -- small o, tilde --> |
3716 |
|
3717 |
Berners-Lee, Connolly [Page 63] |
3718 |
|
3719 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3720 |
|
3721 |
<!ENTITY ouml CDATA "ö" -- small o, dieresis or umlaut mark --> |
3722 |
<!ENTITY szlig CDATA "ß" -- small sharp s, German (sz ligature) -\ |
3723 |
> |
3724 |
<!ENTITY thorn CDATA "þ" -- small thorn, Icelandic --> |
3725 |
<!ENTITY uacute CDATA "ú" -- small u, acute accent --> |
3726 |
<!ENTITY ucirc CDATA "û" -- small u, circumflex accent --> |
3727 |
<!ENTITY ugrave CDATA "ù" -- small u, grave accent --> |
3728 |
<!ENTITY uuml CDATA "ü" -- small u, dieresis or umlaut mark --> |
3729 |
<!ENTITY yacute CDATA "ý" -- small y, acute accent --> |
3730 |
<!ENTITY yuml CDATA "ÿ" -- small y, dieresis or umlaut mark --> |
3731 |
|
3732 |
|
3733 |
10. Security Considerations |
3734 |
|
3735 |
Anchors, embedded images, and all other elements which contain |
3736 |
URIs as parameters may cause the URI to be dereferenced in |
3737 |
response to user input. In this case, the security |
3738 |
considerations of [URL] apply. |
3739 |
|
3740 |
The widely deployed methods for submitting forms requests -- |
3741 |
HTTP and SMTP -- provide little assurance of confidentiality. |
3742 |
Information providers who request sensitive information via |
3743 |
forms -- especially by way of the `PASSWORD' type input field |
3744 |
(see 8.1.2, "Input Field: INPUT") -- should be aware and make |
3745 |
their users aware of the lack of confidentiality. |
3746 |
|
3747 |
|
3748 |
11. References |
3749 |
|
3750 |
[URI] |
3751 |
T. Berners-Lee. ``Universal Resource Identifiers in WWW: |
3752 |
A Unifying Syntax for the Expression of Names and |
3753 |
Addresses of Objects on the Network as used in the |
3754 |
World- Wide Web.'' RFC 1630, CERN, June 1994. |
3755 |
<URL:ftp://ds.internic.net/rfc/rfc1630.txt> |
3756 |
|
3757 |
[URL] |
3758 |
T. Berners-Lee, L. Masinter, and M. McCahill. ``Uniform |
3759 |
Resource Locators (URL).'' RFC 1738, CERN, Xerox PARC, |
3760 |
University of Minnesota, October 1994. |
3761 |
<URL:ftp://ds.internic.net/rfc/rfc1738.txt> |
3762 |
|
3763 |
[HTTP] |
3764 |
T. Berners-Lee, R. T. Fielding, and H. Frystyk Nielsen. |
3765 |
``Hypertext Transfer Protocol - HTTP/1.0.'' Work in |
3766 |
Progress, MIT, UC Irvine, CERN, March 1995. |
3767 |
<URL:ftp://ds.internic.net/internet-drafts/draft-ietf-http-v10-spec-00.ps> |
3768 |
|
3769 |
[MIME] |
3770 |
N. Borenstein and N. Freed. ``MIME (Multipurpose |
3771 |
Internet Mail Extensions) Part One: Mechanisms for |
3772 |
Specifying and Describing the Format of Internet Message |
3773 |
Bodies.'' RFC 1521, Bellcore, Innosoft, September 1993. |
3774 |
<URL:ftp://ds.internic.net/rfc/rfc1521.txt> |
3775 |
|
3776 |
Berners-Lee, Connolly [Page 64] |
3777 |
|
3778 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3779 |
|
3780 |
|
3781 |
[RELURL] |
3782 |
R. Fielding. ``Relative Uniform Resource Locators.'' RFC |
3783 |
1808, June 1995 |
3784 |
<URL:ftp://ds.internic.net/rfc/rfc1808.txt> |
3785 |
|
3786 |
[GOLD90] |
3787 |
C. F. Goldfarb. ``The SGML Handbook.'' Y. Rubinsky, Ed., |
3788 |
Oxford University Press, 1990. <URL:> |
3789 |
|
3790 |
[DEXTER] |
3791 |
Frank Halasz and Mayer Schwartz, ``The Dexter Hypertext |
3792 |
Reference Model'', ``Communications of the ACM'', pp. |
3793 |
30-39, vol. 37 no. 2, Feb 1994, <URL:> |
3794 |
|
3795 |
[IMEDIA] |
3796 |
J. Postel. ``Media Type Registration Procedure.'', |
3797 |
USC/ISI, March 1994. |
3798 |
<URL:ftp://ds.internic.net/rfc/rfc1590.txt> |
3799 |
|
3800 |
[IANA] |
3801 |
J. Reynolds and J. Postel. ``Assigned Numbers.'' STD 2, |
3802 |
RFC 1700, USC/ISI, October 1994. |
3803 |
<URL:ftp://ds.internic.net/rfc/rfc1700.txt> |
3804 |
|
3805 |
[SQ91] |
3806 |
SoftQuad. ``The SGML Primer.'' 3rd ed., SoftQuad Inc., |
3807 |
1991. <URL:http://www.sq.com/> |
3808 |
|
3809 |
[ISO-646] |
3810 |
ISO/IEC 646:1991 Information technology -- ISO 7-bit |
3811 |
coded character set for information interchange |
3812 |
<URL:http://www.iso.ch/cate/d4777.html> |
3813 |
|
3814 |
[ISO-10646] |
3815 |
ISO/IEC 10646-1:1993 Information technology -- Universal |
3816 |
Multiple-Octet Coded Character Set (UCS) -- Part 1: |
3817 |
Architecture and Basic Multilingual Plane |
3818 |
<URL:http://www.iso.ch/cate/d18741.html> |
3819 |
|
3820 |
[ISO-8859-1] |
3821 |
ISO 8859. International Standard -- Information |
3822 |
Processing -- 8-bit Single-Byte Coded Graphic Character |
3823 |
Sets -- Part 1: Latin Alphabet No. 1, ISO 8859-1:1987. |
3824 |
<URL:http://www.iso.ch/cate/d16338.html> |
3825 |
|
3826 |
[SGML] |
3827 |
ISO 8879. Information Processing -- Text and Office |
3828 |
Systems - Standard Generalized Markup Language (SGML), |
3829 |
1986. <URL:http://www.iso.ch/cate/d16387.html> |
3830 |
|
3831 |
|
3832 |
|
3833 |
|
3834 |
|
3835 |
Berners-Lee, Connolly [Page 65] |
3836 |
|
3837 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3838 |
|
3839 |
12. Acknowledgments |
3840 |
|
3841 |
The HTML document type was designed by Tim Berners-Lee at CERN |
3842 |
as part of the 1990 World Wide Web project. In 1992, Dan |
3843 |
Connolly wrote the HTML Document Type Definition (DTD) and a |
3844 |
brief HTML specification. |
3845 |
|
3846 |
Since 1993, a wide variety of Internet participants have |
3847 |
contributed to the evolution of HTML, which has included the |
3848 |
addition of in-line images introduced by the NCSA Mosaic |
3849 |
software for WWW. Dave Raggett played an important role in |
3850 |
deriving the FORMS material from the HTML+ specification. |
3851 |
|
3852 |
Dan Connolly and Karen Olson Muldrow rewrote the HTML |
3853 |
Specification in 1994. The document was then edited by the HTML |
3854 |
working group as a whole, with updates being made by Eric |
3855 |
Schieler, Mike Knezovich, and Eric W. Sink at Spyglass, Inc. |
3856 |
Finally, Roy Fielding restructured the entire draft into its |
3857 |
current form. |
3858 |
|
3859 |
Special thanks to the many active participants in the HTML |
3860 |
working group, too numerous to list individually, without whom |
3861 |
there would be no standards process and no standard. That this |
3862 |
document approaches its objective of carefully converging a |
3863 |
description of current practice and formalization of HTML's |
3864 |
relationship to SGML is a tribute to their effort. |
3865 |
|
3866 |
|
3867 |
12.1. Authors' Addresses |
3868 |
|
3869 |
Tim Berners-Lee |
3870 |
|
3871 |
Director, W3 Consortium |
3872 |
MIT Laboratory for Computer Science |
3873 |
545 Technology Square |
3874 |
Cambridge, MA 02139, U.S.A. |
3875 |
Tel: +1 (617) 253 9670 |
3876 |
Fax: +1 (617) 258 8682 |
3877 |
Email: timbl@w3.org |
3878 |
|
3879 |
Daniel W. Connolly |
3880 |
|
3881 |
Research Technical Staff, W3 Consortium |
3882 |
MIT Laboratory for Computer Science |
3883 |
545 Technology Square |
3884 |
Cambridge, MA 02139, U.S.A. |
3885 |
Fax: +1 (617) 258 8682 |
3886 |
Email: connolly@w3.org |
3887 |
URI: http://www.w3.org/hypertext/WWW/People/Connolly/ |
3888 |
|
3889 |
|
3890 |
13. The HTML Coded Character Set |
3891 |
|
3892 |
This list details the code positions and characters of the HTML |
3893 |
|
3894 |
Berners-Lee, Connolly [Page 66] |
3895 |
|
3896 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3897 |
|
3898 |
document character set, specified in 9.5, "SGML Declaration for |
3899 |
HTML". This coded character set is based on [ISO-8859-1]. |
3900 |
|
3901 |
REFERENCE DESCRIPTION |
3902 |
-------------- ----------- |
3903 |
� -  Unused |
3904 |
	 Horizontal tab |
3905 |
Line feed |
3906 |
 -  Unused |
3907 |
Carriage Return |
3908 |
 -  Unused |
3909 |
  Space |
3910 |
! Exclamation mark |
3911 |
" Quotation mark |
3912 |
# Number sign |
3913 |
$ Dollar sign |
3914 |
% Percent sign |
3915 |
& Ampersand |
3916 |
' Apostrophe |
3917 |
( Left parenthesis |
3918 |
) Right parenthesis |
3919 |
* Asterisk |
3920 |
+ Plus sign |
3921 |
, Comma |
3922 |
- Hyphen |
3923 |
. Period (fullstop) |
3924 |
/ Solidus (slash) |
3925 |
0 - 9 Digits 0-9 |
3926 |
: Colon |
3927 |
; Semi-colon |
3928 |
< Less than |
3929 |
= Equals sign |
3930 |
> Greater than |
3931 |
? Question mark |
3932 |
@ Commercial at |
3933 |
A - Z Letters A-Z |
3934 |
[ Left square bracket |
3935 |
\ Reverse solidus (backslash) |
3936 |
] Right square bracket |
3937 |
^ Caret |
3938 |
_ Horizontal bar (underscore) |
3939 |
` Acute accent |
3940 |
a - z Letters a-z |
3941 |
{ Left curly brace |
3942 |
| Vertical bar |
3943 |
} Right curly brace |
3944 |
~ Tilde |
3945 |
 - Ÿ Unused |
3946 |
  Non-breaking Space |
3947 |
¡ Inverted exclamation |
3948 |
¢ Cent sign |
3949 |
£ Pound sterling |
3950 |
¤ General currency sign |
3951 |
¥ Yen sign |
3952 |
|
3953 |
Berners-Lee, Connolly [Page 67] |
3954 |
|
3955 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
3956 |
|
3957 |
¦ Broken vertical bar |
3958 |
§ Section sign |
3959 |
¨ Umlaut (dieresis) |
3960 |
© Copyright |
3961 |
ª Feminine ordinal |
3962 |
« Left angle quote, guillemotleft |
3963 |
¬ Not sign |
3964 |
­ Soft hyphen |
3965 |
® Registered trademark |
3966 |
¯ Macron accent |
3967 |
° Degree sign |
3968 |
± Plus or minus |
3969 |
² Superscript two |
3970 |
³ Superscript three |
3971 |
´ Acute accent |
3972 |
µ Micro sign |
3973 |
¶ Paragraph sign |
3974 |
· Middle dot |
3975 |
¸ Cedilla |
3976 |
¹ Superscript one |
3977 |
º Masculine ordinal |
3978 |
» Right angle quote, guillemotright |
3979 |
¼ Fraction one-fourth |
3980 |
½ Fraction one-half |
3981 |
¾ Fraction three-fourths |
3982 |
¿ Inverted question mark |
3983 |
À Capital A, grave accent |
3984 |
Á Capital A, acute accent |
3985 |
 Capital A, circumflex accent |
3986 |
à Capital A, tilde |
3987 |
Ä Capital A, dieresis or umlaut mark |
3988 |
Å Capital A, ring |
3989 |
Æ Capital AE dipthong (ligature) |
3990 |
Ç Capital C, cedilla |
3991 |
È Capital E, grave accent |
3992 |
É Capital E, acute accent |
3993 |
Ê Capital E, circumflex accent |
3994 |
Ë Capital E, dieresis or umlaut mark |
3995 |
Ì Capital I, grave accent |
3996 |
Í Capital I, acute accent |
3997 |
Î Capital I, circumflex accent |
3998 |
Ï Capital I, dieresis or umlaut mark |
3999 |
Ð Capital Eth, Icelandic |
4000 |
Ñ Capital N, tilde |
4001 |
Ò Capital O, grave accent |
4002 |
Ó Capital O, acute accent |
4003 |
Ô Capital O, circumflex accent |
4004 |
Õ Capital O, tilde |
4005 |
Ö Capital O, dieresis or umlaut mark |
4006 |
× Multiply sign |
4007 |
Ø Capital O, slash |
4008 |
Ù Capital U, grave accent |
4009 |
Ú Capital U, acute accent |
4010 |
Û Capital U, circumflex accent |
4011 |
|
4012 |
Berners-Lee, Connolly [Page 68] |
4013 |
|
4014 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
4015 |
|
4016 |
Ü Capital U, dieresis or umlaut mark |
4017 |
Ý Capital Y, acute accent |
4018 |
Þ Capital THORN, Icelandic |
4019 |
ß Small sharp s, German (sz ligature) |
4020 |
à Small a, grave accent |
4021 |
á Small a, acute accent |
4022 |
â Small a, circumflex accent |
4023 |
ã Small a, tilde |
4024 |
ä Small a, dieresis or umlaut mark |
4025 |
å Small a, ring |
4026 |
æ Small ae dipthong (ligature) |
4027 |
ç Small c, cedilla |
4028 |
è Small e, grave accent |
4029 |
é Small e, acute accent |
4030 |
ê Small e, circumflex accent |
4031 |
ë Small e, dieresis or umlaut mark |
4032 |
ì Small i, grave accent |
4033 |
í Small i, acute accent |
4034 |
î Small i, circumflex accent |
4035 |
ï Small i, dieresis or umlaut mark |
4036 |
ð Small eth, Icelandic |
4037 |
ñ Small n, tilde |
4038 |
ò Small o, grave accent |
4039 |
ó Small o, acute accent |
4040 |
ô Small o, circumflex accent |
4041 |
õ Small o, tilde |
4042 |
ö Small o, dieresis or umlaut mark |
4043 |
÷ Division sign |
4044 |
ø Small o, slash |
4045 |
ù Small u, grave accent |
4046 |
ú Small u, acute accent |
4047 |
û Small u, circumflex accent |
4048 |
ü Small u, dieresis or umlaut mark |
4049 |
ý Small y, acute accent |
4050 |
þ Small thorn, Icelandic |
4051 |
ÿ Small y, dieresis or umlaut mark |
4052 |
|
4053 |
|
4054 |
14. Proposed Entities |
4055 |
|
4056 |
The HTML DTD references the ``Added Latin 1'' entity set, which |
4057 |
only supplies named entities for a subset of the non-ASCII |
4058 |
characters in [ISO-8859-1], namely the accented characters. The |
4059 |
following entities should be supported so that all ISO 8859-1 |
4060 |
characters may only be referenced symbolically. The names for |
4061 |
these entities are taken from the appendixes of [SGML]. |
4062 |
|
4063 |
<!ENTITY nbsp CDATA " " -- no-break space --> |
4064 |
<!ENTITY iexcl CDATA "¡" -- inverted exclamation mark --> |
4065 |
<!ENTITY cent CDATA "¢" -- cent sign --> |
4066 |
<!ENTITY pound CDATA "£" -- pound sterling sign --> |
4067 |
<!ENTITY curren CDATA "¤" -- general currency sign --> |
4068 |
<!ENTITY yen CDATA "¥" -- yen sign --> |
4069 |
<!ENTITY brvbar CDATA "¦" -- broken (vertical) bar --> |
4070 |
|
4071 |
Berners-Lee, Connolly [Page 69] |
4072 |
|
4073 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
4074 |
|
4075 |
<!ENTITY sect CDATA "§" -- section sign --> |
4076 |
<!ENTITY uml CDATA "¨" -- umlaut (dieresis) --> |
4077 |
<!ENTITY copy CDATA "©" -- copyright sign --> |
4078 |
<!ENTITY ordf CDATA "ª" -- ordinal indicator, feminine --> |
4079 |
<!ENTITY laquo CDATA "«" -- angle quotation mark, left --> |
4080 |
<!ENTITY not CDATA "¬" -- not sign --> |
4081 |
<!ENTITY shy CDATA "­" -- soft hyphen --> |
4082 |
<!ENTITY reg CDATA "®" -- registered sign --> |
4083 |
<!ENTITY macr CDATA "¯" -- macron --> |
4084 |
<!ENTITY deg CDATA "°" -- degree sign --> |
4085 |
<!ENTITY plusmn CDATA "±" -- plus-or-minus sign --> |
4086 |
<!ENTITY sup2 CDATA "²" -- superscript two --> |
4087 |
<!ENTITY sup3 CDATA "³" -- superscript three --> |
4088 |
<!ENTITY acute CDATA "´" -- acute accent --> |
4089 |
<!ENTITY micro CDATA "µ" -- micro sign --> |
4090 |
<!ENTITY para CDATA "¶" -- pilcrow (paragraph sign) --> |
4091 |
<!ENTITY middot CDATA "·" -- middle dot --> |
4092 |
<!ENTITY cedil CDATA "¸" -- cedilla --> |
4093 |
<!ENTITY sup1 CDATA "¹" -- superscript one --> |
4094 |
<!ENTITY ordm CDATA "º" -- ordinal indicator, masculine --> |
4095 |
<!ENTITY raquo CDATA "»" -- angle quotation mark, right --> |
4096 |
<!ENTITY frac14 CDATA "¼" -- fraction one-quarter --> |
4097 |
<!ENTITY frac12 CDATA "½" -- fraction one-half --> |
4098 |
<!ENTITY frac34 CDATA "¾" -- fraction three-quarters --> |
4099 |
<!ENTITY iquest CDATA "¿" -- inverted question mark --> |
4100 |
<!ENTITY Agrave CDATA "À" -- capital A, grave accent --> |
4101 |
<!ENTITY Aacute CDATA "Á" -- capital A, acute accent --> |
4102 |
<!ENTITY Acirc CDATA "Â" -- capital A, circumflex accent --> |
4103 |
<!ENTITY Atilde CDATA "Ã" -- capital A, tilde --> |
4104 |
<!ENTITY Auml CDATA "Ä" -- capital A, dieresis or umlaut mark --> |
4105 |
<!ENTITY Aring CDATA "Å" -- capital A, ring --> |
4106 |
<!ENTITY AElig CDATA "Æ" -- capital AE diphthong (ligature) --> |
4107 |
<!ENTITY Ccedil CDATA "Ç" -- capital C, cedilla --> |
4108 |
<!ENTITY Egrave CDATA "È" -- capital E, grave accent --> |
4109 |
<!ENTITY Eacute CDATA "É" -- capital E, acute accent --> |
4110 |
<!ENTITY Ecirc CDATA "Ê" -- capital E, circumflex accent --> |
4111 |
<!ENTITY Euml CDATA "Ë" -- capital E, dieresis or umlaut mark --> |
4112 |
<!ENTITY Igrave CDATA "Ì" -- capital I, grave accent --> |
4113 |
<!ENTITY Iacute CDATA "Í" -- capital I, acute accent --> |
4114 |
<!ENTITY Icirc CDATA "Î" -- capital I, circumflex accent --> |
4115 |
<!ENTITY Iuml CDATA "Ï" -- capital I, dieresis or umlaut mark --> |
4116 |
<!ENTITY ETH CDATA "Ð" -- capital Eth, Icelandic --> |
4117 |
<!ENTITY Ntilde CDATA "Ñ" -- capital N, tilde --> |
4118 |
<!ENTITY Ograve CDATA "Ò" -- capital O, grave accent --> |
4119 |
<!ENTITY Oacute CDATA "Ó" -- capital O, acute accent --> |
4120 |
<!ENTITY Ocirc CDATA "Ô" -- capital O, circumflex accent --> |
4121 |
<!ENTITY Otilde CDATA "Õ" -- capital O, tilde --> |
4122 |
<!ENTITY Ouml CDATA "Ö" -- capital O, dieresis or umlaut mark --> |
4123 |
<!ENTITY times CDATA "×" -- multiply sign --> |
4124 |
<!ENTITY Oslash CDATA "Ø" -- capital O, slash --> |
4125 |
<!ENTITY Ugrave CDATA "Ù" -- capital U, grave accent --> |
4126 |
<!ENTITY Uacute CDATA "Ú" -- capital U, acute accent --> |
4127 |
<!ENTITY Ucirc CDATA "Û" -- capital U, circumflex accent --> |
4128 |
<!ENTITY Uuml CDATA "Ü" -- capital U, dieresis or umlaut mark --> |
4129 |
|
4130 |
Berners-Lee, Connolly [Page 70] |
4131 |
|
4132 |
INTERNET-DRAFT Hypertext Markup Language - 2.0 August 8, 1995 |
4133 |
|
4134 |
<!ENTITY Yacute CDATA "Ý" -- capital Y, acute accent --> |
4135 |
<!ENTITY THORN CDATA "Þ" -- capital THORN, Icelandic --> |
4136 |
<!ENTITY szlig CDATA "ß" -- small sharp s, German (sz ligature) --> |
4137 |
<!ENTITY agrave CDATA "à" -- small a, grave accent --> |
4138 |
<!ENTITY aacute CDATA "á" -- small a, acute accent --> |
4139 |
<!ENTITY acirc CDATA "â" -- small a, circumflex accent --> |
4140 |
<!ENTITY atilde CDATA "ã" -- small a, tilde --> |
4141 |
<!ENTITY auml CDATA "ä" -- small a, dieresis or umlaut mark --> |
4142 |
<!ENTITY aring CDATA "å" -- small a, ring --> |
4143 |
<!ENTITY aelig CDATA "æ" -- small ae diphthong (ligature) --> |
4144 |
<!ENTITY ccedil CDATA "ç" -- small c, cedilla --> |
4145 |
<!ENTITY egrave CDATA "è" -- small e, grave accent --> |
4146 |
<!ENTITY eacute CDATA "é" -- small e, acute accent --> |
4147 |
<!ENTITY ecirc CDATA "ê" -- small e, circumflex accent --> |
4148 |
<!ENTITY euml CDATA "ë" -- small e, dieresis or umlaut mark --> |
4149 |
<!ENTITY igrave CDATA "ì" -- small i, grave accent --> |
4150 |
<!ENTITY iacute CDATA "í" -- small i, acute accent --> |
4151 |
<!ENTITY icirc CDATA "î" -- small i, circumflex accent --> |
4152 |
<!ENTITY iuml CDATA "ï" -- small i, dieresis or umlaut mark --> |
4153 |
<!ENTITY eth CDATA "ð" -- small eth, Icelandic --> |
4154 |
<!ENTITY ntilde CDATA "ñ" -- small n, tilde --> |
4155 |
<!ENTITY ograve CDATA "ò" -- small o, grave accent --> |
4156 |
<!ENTITY oacute CDATA "ó" -- small o, acute accent --> |
4157 |
<!ENTITY ocirc CDATA "ô" -- small o, circumflex accent --> |
4158 |
<!ENTITY otilde CDATA "õ" -- small o, tilde --> |
4159 |
<!ENTITY ouml CDATA "ö" -- small o, dieresis or umlaut mark --> |
4160 |
<!ENTITY divide CDATA "÷" -- divide sign --> |
4161 |
<!ENTITY oslash CDATA "ø" -- small o, slash --> |
4162 |
<!ENTITY ugrave CDATA "ù" -- small u, grave accent --> |
4163 |
<!ENTITY uacute CDATA "ú" -- small u, acute accent --> |
4164 |
<!ENTITY ucirc CDATA "û" -- small u, circumflex accent --> |
4165 |
<!ENTITY uuml CDATA "ü" -- small u, dieresis or umlaut mark --> |
4166 |
<!ENTITY yacute CDATA "ý" -- small y, acute accent --> |
4167 |
<!ENTITY thorn CDATA "þ" -- small thorn, Icelandic --> |
4168 |
<!ENTITY yuml CDATA "ÿ" -- small y, dieresis or umlaut mark --> |
4169 |
|
4170 |
|
4171 |
|
4172 |
|
4173 |
|
4174 |
|
4175 |
|
4176 |
|
4177 |
|
4178 |
|
4179 |
|
4180 |
|
4181 |
|
4182 |
|
4183 |
|
4184 |
|
4185 |
|
4186 |
|
4187 |
|
4188 |
|
4189 |
Berners-Lee, Connolly [Page 71] |
4190 |
|
4191 |
|