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