1 |
|
2 |
HTML Working Group T. Berners-Lee |
3 |
INTERNET-DRAFT MIT/W3C |
4 |
<draft-ietf-html-spec-02.txt> D. Connolly |
5 |
Expires: In six months May 6, 1995 |
6 |
|
7 |
|
8 |
Hypertext Markup Language - 2.0 |
9 |
|
10 |
|
11 |
CONTENTS |
12 |
|
13 |
|
14 |
1. Introduction |
15 |
2. HTML as an Application of SGML |
16 |
3. HTML as an Internet Media Type |
17 |
4. Document Structure Elements |
18 |
5. Character Content |
19 |
6. Data Elements |
20 |
7. Character Format Elements |
21 |
8. Hyperlink Elements |
22 |
9. Block Structuring Elements |
23 |
10. Form-based Input Elements |
24 |
11. HTML Public Text |
25 |
12. Glossary |
26 |
13. Bibliography |
27 |
14. Appendices |
28 |
15. Acknowledgments |
29 |
|
30 |
|
31 |
|
32 |
Status of this Memo |
33 |
|
34 |
This document is an Internet-Draft. Internet-Drafts are working |
35 |
documents of the Internet Engineering Task Force (IETF), its areas, |
36 |
and its working groups. Note that other groups may also distribute |
37 |
working documents as Internet-Drafts. |
38 |
|
39 |
Internet-Drafts are draft documents valid for a maximum of six months |
40 |
and may be updated, replaced, or obsoleted by other documents at any |
41 |
time. It is inappropriate to use Internet-Drafts as reference material |
42 |
or to cite them other than as ``work in progress.'' |
43 |
|
44 |
To learn the current status of any Internet-Draft, please check the |
45 |
1id-abstracts.txt listing contained in the Internet-Drafts Shadow |
46 |
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), |
47 |
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or |
48 |
ftp.isi.edu (US West Coast). |
49 |
|
50 |
Distribution of this document is unlimited. Please send comments to |
51 |
the HTML working group (HTML-WG) of the Internet Engineering Task |
52 |
Force (IETF) at <html-wg@oclc.org>. Discussions of the group are |
53 |
archived at <URL:http://www.acl.lanl.gov/HTML_WG/archives.html>. |
54 |
|
55 |
|
56 |
ABSTRACT |
57 |
|
58 |
The Hypertext Markup Language (HTML) is a simple markup |
59 |
language used to create hypertext documents that are |
60 |
platform independent. HTML documents are SGML documents with |
61 |
generic semantics that are appropriate for representing |
62 |
information from a wide range of domains. HTML markup can |
63 |
represent hypertext news, mail, documentation, and |
64 |
hypermedia; menus of options; database query results; simple |
65 |
structured documents with in-lined graphics; and hypertext |
66 |
views of existing bodies of information. |
67 |
|
68 |
HTML has been in use by the World Wide Web (WWW) global |
69 |
information initiative since 1990. This specification |
70 |
roughly corresponds to the capabilities of HTML in common |
71 |
use prior to June 1994. HTML is an application of ISO |
72 |
Standard 8879:1986 Information Processing Text and Office |
73 |
Systems; Standard Generalized Markup Language (SGML). |
74 |
|
75 |
The `"text/html; version=2.0"' Internet Media Type (RFC |
76 |
1590) and MIME Content Type (RFC 1521) is defined by this |
77 |
specification. |
78 |
|
79 |
|
80 |
1. Introduction |
81 |
|
82 |
The HyperText Markup Language (HTML) is a simple data format |
83 |
used to create hypertext documents that are portable from |
84 |
one platform to another. HTML documents are SGML documents |
85 |
with generic semantics that are appropriate for representing |
86 |
information from a wide range of domains. |
87 |
|
88 |
|
89 |
1.1. Scope |
90 |
|
91 |
HTML has been in use by the World-Wide Web (WWW) global |
92 |
information initiative since 1990. This specification |
93 |
corresponds to the capabilities of HTML in common use prior |
94 |
to June 1994 and referred to as ``HTML 2.0''. |
95 |
|
96 |
HTML is an application of ISO Standard 8879:1986 |
97 |
_Information Processing Text and Office Systems; Standard |
98 |
Generalized Markup Language_ (SGML). The HTML Document Type |
99 |
Definition (DTD) is a formal definition of the HTML syntax |
100 |
in terms of SGML. |
101 |
|
102 |
This specification also defines HTML as an Internet Media |
103 |
Type[IMEDIA] and MIME Content Type[MIME] called `text/html', |
104 |
or `text/html; version=2.0'. As such, it defines the |
105 |
semantics of the HTML syntax and how that syntax should be |
106 |
interpreted by user agents. |
107 |
|
108 |
|
109 |
1.2. Conformance |
110 |
|
111 |
This specification governs the syntax of HTML documents and |
112 |
the behaviour of HTML user agents. |
113 |
|
114 |
|
115 |
1.2.1. Documents |
116 |
|
117 |
A document is a conforming HTML document only if: |
118 |
|
119 |
* It is a conforming SGML document, and it conforms to |
120 |
the HTML DTD (see 11.1, "HTML DTD") |
121 |
* It conforms to the application conventions in this |
122 |
specification. For example, the value of the `HREF' |
123 |
attribute of the <A> element must conform to the URI |
124 |
syntax. |
125 |
* Its document character set includes ISO-8859-1 and |
126 |
agrees with ISO10646; that is, each code position |
127 |
listed in 14.1, "The ISO-8859-1 Coded Character Set" is |
128 |
included, and each code position in the document |
129 |
character set is mapped to the same character as |
130 |
ISO10646 designates for that code position. |
131 |
NOTE - The document character set is somewhat |
132 |
independent of the character encoding scheme used to |
133 |
represent a document. For example, the ISO-2022-JP |
134 |
character encoding scheme can be used for HTML |
135 |
documents, since its repertoire is a subset of the |
136 |
ISO10646 repertoire. The crititcal distinction is that |
137 |
numeric character references agree with ISO10646 |
138 |
regardless of how the document is encoded. |
139 |
|
140 |
NOTE - There are a number of syntactic idioms that are |
141 |
not supported or are supported inconsistently in some |
142 |
historical user agent implementations. These idioms are |
143 |
called out in notes like this throughout this |
144 |
specification. |
145 |
|
146 |
HTML documents should not contain these idioms, at |
147 |
least until such time as support for them is widely |
148 |
deployed. |
149 |
|
150 |
The HTML DTD defines a standard HTML document type and |
151 |
several variations, based on feature test entities: |
152 |
|
153 |
|
154 |
HTML.Recommended |
155 |
Certain features of the language are necessary for |
156 |
compatibility with widespread usage, but they may |
157 |
compromise the structural integrity of a document. |
158 |
This feature test entity enables a more |
159 |
prescriptive document type definition that |
160 |
eliminates those features. |
161 |
|
162 |
For example, in order to preserve the structure of |
163 |
a document, an editing user agent may translate |
164 |
HTML documents to the recommended subset, or it |
165 |
may require that the documents be in the |
166 |
recommended subset for import. |
167 |
|
168 |
HTML.Deprecated |
169 |
Certain features of the language are necessary for |
170 |
compatibility with earlier versions of the |
171 |
specification, but they tend to be used an |
172 |
implemented inconsistently, and their use is |
173 |
deprecated. This feature test entity enables a |
174 |
document type definition that eliminates these |
175 |
features. |
176 |
|
177 |
Documents generated by tranlation software or |
178 |
editing software should not contain these idioms. |
179 |
|
180 |
|
181 |
1.2.2. User Agents |
182 |
|
183 |
An HTML user agent conforms to this specification if: |
184 |
|
185 |
* It parses the characters of an HTML document into |
186 |
data characters and markup as per [SGML]. |
187 |
* It supports the ISO-8859-1 character encoding scheme, |
188 |
and processes each character in the ISO Latin Alphabet |
189 |
Nr. 1 as specified in 5.1, "The ISO Latin 1 Character |
190 |
Repertoire". |
191 |
NOTE - To support non-western writing systems, HTML |
192 |
user agents should support the Unicode-1-1-UTF-8 and |
193 |
Unicode-1-1-UCS-2 encodings and as much of the |
194 |
character repertoire of ISO10646 as is possible as |
195 |
well. |
196 |
* It behaves identically for documents whose parsed |
197 |
token sequences are identical. |
198 |
For example, comments and the whitespace in tags |
199 |
disappear during tokenization, and hence they do not |
200 |
influence the behaviour of conforming user agents. |
201 |
* It allows the user to traverse (or at least attempt |
202 |
to traverse, resources permitting) all hyperlinks in an |
203 |
HTML document. |
204 |
* It allows the user to express all form field values |
205 |
specified in an HTML document and to (attempt to) |
206 |
submit the values as requests to information services. |
207 |
|
208 |
NOTE - In the interest of robustness and extensibility, |
209 |
there are a number of widely deployed conventions for |
210 |
handling non-conforming documents. See 3.2.1, |
211 |
"Undeclared Markup Error Handling" for details. |
212 |
|
213 |
|
214 |
2. HTML as an Application of SGML |
215 |
|
216 |
HTML is an application of ISO Standard 8879:1986 - Standard |
217 |
Generalized Markup Language (SGML). SGML is a system for |
218 |
defining structured document types and markup languages to |
219 |
represent instances of those document types[SGML]. The |
220 |
public text -- DTD and SGML declaration -- of the HTML |
221 |
document type definition are provided in 11, "HTML Public |
222 |
Text". |
223 |
|
224 |
The term _HTML_ refers to both the document type defined |
225 |
here and the markup language for representing instances of |
226 |
this document type. |
227 |
|
228 |
|
229 |
2.1. SGML Documents |
230 |
|
231 |
An HTML document is an SGML document; that is, a sequence of |
232 |
characters organized physically into a set of entities, and |
233 |
logically as a hierarchy of elements. |
234 |
|
235 |
The first production of the SGML grammar separates an SGML |
236 |
document into three parts: an SGML declaration, a prologue, |
237 |
and an instance. For the purposes of this specification, the |
238 |
prologue is a DTD. This DTD describes another grammar: the |
239 |
start symbol is given in the doctype declaration; the |
240 |
terminals are data characters and tags, and the productions |
241 |
are determined by the element declarations. The instance |
242 |
must conform to the DTD, that is, it must be in the language |
243 |
defined by this grammar. |
244 |
|
245 |
The SGML declaration determines the lexicon of the grammar. |
246 |
It specifies the document character set, which determines a |
247 |
character repertoire that contains all characters that occur |
248 |
in all text entities in the document, and the code positions |
249 |
associated with those characters. |
250 |
|
251 |
The SGML declaration also specifies the syntax-reference |
252 |
character set of the document, and a few other parameters |
253 |
that bind the abstract syntax of SGML to a concrete syntax. |
254 |
This concrete syntax determines how the sequence of |
255 |
characters of the document is mapped to a sequence of |
256 |
terminals in the grammar of the prologue. |
257 |
|
258 |
For example, consider the following document: |
259 |
|
260 |
<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 2.0//EN"> |
261 |
<title>Parsing Example</title> |
262 |
<p>Some text. <em>*wow*</em></p> |
263 |
|
264 |
An HTML user agent should use the SGML declaration is given |
265 |
in 11.2, "SGML Declaration for HTML". According to the |
266 |
document character set there,`*' refers to an asterisk |
267 |
character. |
268 |
|
269 |
The instance above is regarded as the following sequence of |
270 |
terminals: |
271 |
|
272 |
1. TITLE start-tag |
273 |
2. data characters: ``Parsing Example'' |
274 |
3. TITLE end-tag |
275 |
4. P start-tag |
276 |
5. data characters ``Some text. '' |
277 |
6. EM start-tag |
278 |
7. ``*wow*'' |
279 |
8. EM end-tag |
280 |
|
281 |
The start symbol of the DTD grammar is HTML, and the |
282 |
productions are given in the public text identified by |
283 |
`-//IETF//DTD HTML 2.0//EN' (11.1, "HTML DTD"). Hence the |
284 |
terminals above parse as: |
285 |
|
286 |
HTML |
287 |
| |
288 |
\-HEAD |
289 |
| | |
290 |
| \-TITLE |
291 |
| | |
292 |
| \-<TITLE> |
293 |
| | |
294 |
| \-"Parsing Example" |
295 |
| | |
296 |
| \-</TITLE> |
297 |
| |
298 |
\-BODY |
299 |
| |
300 |
\-P |
301 |
| |
302 |
\-<P> |
303 |
| |
304 |
\-"Some text. " |
305 |
| |
306 |
\-EM |
307 |
| | |
308 |
| \-<EM> |
309 |
| | |
310 |
| \-"*wow*" |
311 |
| | |
312 |
| \-</EM> |
313 |
| |
314 |
\-</P> |
315 |
|
316 |
|
317 |
2.2. HTML Lexical Syntax |
318 |
|
319 |
SGML specifies an abstract syntax and a reference concrete |
320 |
syntax. Aside from certain quantities and capacities (e.g. |
321 |
the limit on the length of a name), all HTML documents use |
322 |
the reference concrete syntax. In particular, all markup |
323 |
characters are in the ISO-646-IRV character repertoire. Data |
324 |
characters are drawn from the document character set (see 5, |
325 |
"Character Content"). |
326 |
|
327 |
A complete discussion of SGML parsing, e.g. the mapping of a |
328 |
sequence of characters to a sequence of tags and data is |
329 |
left to the SGML standard[SGML]. This section is only a |
330 |
summary. |
331 |
|
332 |
|
333 |
2.2.1. Data Characters |
334 |
|
335 |
Any sequence of characters that do not constitute markup |
336 |
(see 9.6 ``Delimiter Recognition'' of [SGML]) are mapped |
337 |
directly to strings of data characters. Some markup also |
338 |
maps to data character strings. Numeric character references |
339 |
also map to single-character strings, via the document |
340 |
character set. Each reference to one of the general entities |
341 |
defined in the HTML DTD also maps to a single-character |
342 |
string. |
343 |
|
344 |
For example, |
345 |
|
346 |
abc<def => "abc","<","def" |
347 |
abc<def => "abc","<","def" |
348 |
|
349 |
Note that the terminating semicolon is only necessary when |
350 |
the character following the reference would otherwise be |
351 |
recognized as markup: |
352 |
|
353 |
abc < def => "abc ","<"," def" |
354 |
abc < def => "abc ","<"," def" |
355 |
|
356 |
And note that an ampersand is only recognized as markup when |
357 |
it is followed by a letter or digit: |
358 |
|
359 |
abc & lt def => "abc & lt def" |
360 |
abc & 60 def => "abc & 60 def" |
361 |
|
362 |
A useful technique for translating plain text to HTML is to |
363 |
replace each '<', '&', and '>' by an entity reference or |
364 |
numeric character reference as follows: |
365 |
|
366 |
ENTITY NUMERIC |
367 |
CHARACTER REFERENCE CHAR REF CHARACTER DESCRIPTION |
368 |
& & & Ampersand |
369 |
< < < Less than |
370 |
> > > Greater than |
371 |
|
372 |
NOTE - There are SGML mechanisms, CDATA and RCDATA, to |
373 |
allow most `<', `>', and `&' characters to be entered |
374 |
without the use of entity references. Because these |
375 |
features tend to be used and implemented |
376 |
inconsistently, and because they conflict with |
377 |
techinques for reducing HTML to 7 bit ASCII for |
378 |
transport, they are not used in this version of the |
379 |
HTML DTD. |
380 |
|
381 |
|
382 |
2.2.2. Tags |
383 |
|
384 |
Tags delimit elements such as headings, paragraphs, lists, |
385 |
character highlighting and links. Most HTML elements are |
386 |
identified in a document as a start-tag, which gives the |
387 |
element name and attributes, followed by the content, |
388 |
followed by the end tag. Start-tags are delimited by `<' and |
389 |
`>'; end tags are delimited by `</' and `>'. An example is: |
390 |
|
391 |
<H1>This is a Heading</H1> |
392 |
|
393 |
Some elements only have a start-tag without an end-tag. For |
394 |
example, to create a line break, you use the `<BR>' tag. |
395 |
Additionally, the end tags of some other elements, such as |
396 |
Paragraph (`</P>'), List Item (`</LI>'), Definition Term |
397 |
(`</DT>'), and Definition Description (`<DD>') elements, may |
398 |
be omitted. |
399 |
|
400 |
The content of an element is a sequence of data character |
401 |
strings and nested elements. Some elements, such as anchors, |
402 |
cannot be nested. Anchors and character highlighting may be |
403 |
put inside other constructs. See the HTML DTD, 11.1, "HTML |
404 |
DTD" for full details. |
405 |
|
406 |
NOTE - The SGML declaration for HTML specifies SHORTTAG |
407 |
YES, which means that there are other valid syntaxes |
408 |
for tags, such as NET tags, `<EM/.../'; empty start |
409 |
tags, `<>'; and empty end-tags, `</>'. Until support |
410 |
for these idioms is widely deployed, their use is |
411 |
strongly discouraged. |
412 |
|
413 |
|
414 |
2.2.3. Names |
415 |
|
416 |
A name consists of a letter followed by up to 71 letters, |
417 |
digits, periods, or hyphens. Element names are not case |
418 |
sensitive, but entity names are. For example, |
419 |
`<BLOCKQUOTE>', `<BlockQuote>', and `<blockquote>' are |
420 |
equivalent, whereas `&' is different from `&'. |
421 |
|
422 |
In a start-tag, the element name must immediately follow the |
423 |
tag open delimiter `<'. |
424 |
|
425 |
|
426 |
2.2.4. Attributes |
427 |
|
428 |
In a start-tag, white space and attributes are allowed |
429 |
between the element name and the closing delimiter. An |
430 |
attribute typically consists of an attribute name, an equal |
431 |
sign, and a value, though some attributes may be just a |
432 |
value. White space is allowed around the equal sign. |
433 |
|
434 |
The value of the attribute may be either: |
435 |
|
436 |
* A string literal, delimited by single quotes or |
437 |
double quotes and not containing any occurrences of the |
438 |
delimiting character. |
439 |
* A name token (a sequence of letters, digits, periods, |
440 |
or hyphens) |
441 |
|
442 |
In this example, img is the element name, `src' is the |
443 |
attribute name, and `http://host/dir/file.gif' is the |
444 |
attribute value: |
445 |
|
446 |
<img src="http://host/dir/file.gif"> |
447 |
|
448 |
NOTE - Some historical implementations consider any |
449 |
occurrence of the `>' character to signal the end of a |
450 |
tag. For ompatibility with such implementations, when |
451 |
`>' appears in an attribute value, it should be |
452 |
represented with a numeric character reference, such as |
453 |
in: `<IMG SRC="eq1.jpg" alt="a>b">'. |
454 |
|
455 |
A useful technique for computing an attribute value literal |
456 |
for a given string is to replace each quote and space |
457 |
character by an entity reference or numeric character |
458 |
reference as follows: |
459 |
|
460 |
ENTITY NUMERIC |
461 |
CHARACTER REFERENCE CHAR REF CHARACTER DESCRIPTION |
462 |
TAB 	 Tab |
463 |
LF Line Feed |
464 |
CR Carriage Return |
465 |
  Space |
466 |
" " " Quotation mark |
467 |
& & & Ampersand |
468 |
|
469 |
For example: |
470 |
|
471 |
<IMG SRC="image.jpg" alt="First "real" example"> |
472 |
|
473 |
NOTE - Some historical implementations allow any |
474 |
character except space or `>' in a name token. |
475 |
Attributes values must be quoted only if they don't |
476 |
satisfy the syntax for a name token. |
477 |
|
478 |
Note that the SGML declaration in section 13.3 limits the |
479 |
length of an attribute value to 1024 characters. |
480 |
|
481 |
Attributes such as ISMAP and COMPACT, may be written using a |
482 |
minimized syntax. The markup: |
483 |
|
484 |
<UL COMPACT="compact"> |
485 |
|
486 |
can be written using a minimized syntax: |
487 |
|
488 |
<UL COMPACT> |
489 |
|
490 |
NOTE - Some historical implementations only understand |
491 |
the minimized syntax. |
492 |
|
493 |
|
494 |
2.2.5. Comments |
495 |
|
496 |
To include comments in an HTML document that will be |
497 |
eliminated in the mapping to terminals, surround them with |
498 |
`<!--' and `-->'. After the comment delimiter, all text up |
499 |
to the next occurrence of `-->' is ignored. Hence comments |
500 |
cannot be nested. White space is allowed between the closing |
501 |
`--' and `>', but not between the opening `<!' and `--'. |
502 |
|
503 |
For example: |
504 |
|
505 |
<HEAD> |
506 |
<TITLE>HTML Guide: Recommended Usage</TITLE> |
507 |
<!-- $Id: html-sgml.sgm,v 1.4 1995/05/06 01:44:46 connolly Exp $ --> |
508 |
</HEAD> |
509 |
|
510 |
NOTE - Some historical HTML implementations incorrectly |
511 |
consider any `>' character to be the termination of a |
512 |
comment. |
513 |
|
514 |
|
515 |
2.2.6. Example HTML Document |
516 |
|
517 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> |
518 |
<HTML> |
519 |
<!-- Here's a good place to put a comment. --> |
520 |
<HEAD> |
521 |
<TITLE>Structural Example</TITLE> |
522 |
</HEAD><BODY> |
523 |
<H1>First Header</H1> |
524 |
<P>This is a paragraph in the example HTML file. Keep in mind |
525 |
that the title does not appear in the document text, but that |
526 |
the header (defined by H1) does.</P> |
527 |
<OL> |
528 |
<LI>First item in an ordered list. |
529 |
<LI>Second item in an ordered list. |
530 |
<UL COMPACT> |
531 |
<LI> Note that lists can be nested; |
532 |
<LI> Whitespace may be used to assist in reading the |
533 |
HTML source. |
534 |
</UL> |
535 |
<LI>Third item in an ordered list. |
536 |
</OL> |
537 |
<P>This is an additional paragraph. Technically, end tags are |
538 |
not required for paragraphs, although they are allowed. You can |
539 |
include character highlighting in a paragraph. <EM>This sentence |
540 |
of the paragraph is emphasized.</EM> Note that the </P> |
541 |
end tag has been omitted. |
542 |
<P> |
543 |
<IMG SRC ="triangle.xbm" alt="Warning: "> |
544 |
Be sure to read these <b>bold instructions</b>. |
545 |
</BODY></HTML> |
546 |
|
547 |
|
548 |
3. HTML as an Internet Media Type |
549 |
|
550 |
An HTML user agent allows users to interact with resources |
551 |
which have HTML representations. At a minimum, it must allow |
552 |
users to examine and navigate the content of HTML documents. |
553 |
HTML user agents should be able to preserve all formatting |
554 |
distinctions represented in an HTML document, and be able to |
555 |
simultaneously present resources referred to by IMG |
556 |
elements. (they may ignore some formatting distinctions or |
557 |
IMG resources at the request of the user). Conforming HTML |
558 |
user agents should support form entry and submission. |
559 |
|
560 |
|
561 |
3.1. text/html media type |
562 |
|
563 |
This specification defines the Internet Media Type[IMEDIA] |
564 |
(formerly referred to as the Content Type[MIME]) called |
565 |
`text/html'. The following is to be registered with [IANA]. |
566 |
|
567 |
Media Type name |
568 |
text |
569 |
|
570 |
Media subtype |
571 |
name |
572 |
html |
573 |
|
574 |
Required |
575 |
parameters |
576 |
none |
577 |
|
578 |
Optional |
579 |
parameters |
580 |
version, charset |
581 |
|
582 |
Encoding |
583 |
considerations |
584 |
any encoding is allowed |
585 |
|
586 |
Security |
587 |
considerations |
588 |
see 3.3, "Security Considerations" |
589 |
|
590 |
The optional parameters are defined as follows: |
591 |
|
592 |
Version |
593 |
To help avoid future compatibility problems, the |
594 |
version parameter may be used to give the version |
595 |
number of the specification to which the document |
596 |
conforms. The version number appears at the front |
597 |
of this document and within the public identifier |
598 |
of the HTML DTD. This specification defines |
599 |
version 2.0. There is no default. |
600 |
|
601 |
Charset |
602 |
The charset parameter (as defined in section 7.1.1 |
603 |
of RFC 1521[MIME]) may be given to specify the |
604 |
character encoding scheme used to represent the |
605 |
HTML document as a sequence of octets. The default |
606 |
value is outside the scope of this specification; |
607 |
but for example, the default is US-ASCII in the |
608 |
context of MIME mail, and ISO-8859-1 in the |
609 |
context of HTTP. |
610 |
|
611 |
|
612 |
3.2. HTML Document Representation |
613 |
|
614 |
A message entity with a content type of `text/html' |
615 |
represents an HTML document, consisting of a single text |
616 |
entity. The `charset' parameter (whether implicit or |
617 |
explicit) identifies a character encoding scheme. The text |
618 |
entity consists of the characters determined by this |
619 |
character encoding scheme and the octets of the body of the |
620 |
message entity. |
621 |
|
622 |
|
623 |
3.2.1. Undeclared Markup Error Handling |
624 |
|
625 |
To facilitate experimentation and interoperability between |
626 |
implementations of various versions of HTML, the installed |
627 |
base of HTML user agents supports a superset of the HTML 2.0 |
628 |
language by reducing it to HTML 2.0: markup in the form of a |
629 |
start-tag or end-tag whose generic identifier is not |
630 |
declared is mapped to nothing during tokenization. |
631 |
Undeclared attributes are treated similarly. The entire |
632 |
attribute specification of an unknown attribute (i.e., the |
633 |
unknown attribute and its value, if any) should be ignored. |
634 |
On the other hand, references to undeclared entities should |
635 |
be treated as data characters. |
636 |
|
637 |
For example: |
638 |
|
639 |
<div class=chapter><h1>foo</h1><p>...</div> |
640 |
=> <H1>,"foo",</H1>,<P>,"..." |
641 |
xxx <P ID=z23> yyy |
642 |
=> "xxx ",<P>," yyy |
643 |
Let α and β be finite sets. |
644 |
=> "Let α and β be finite sets." |
645 |
|
646 |
Support for notifying the user of such errors is encouraged. |
647 |
|
648 |
Information providers are warned that this convention is not |
649 |
binding: unspecified behavior may result, as such markup is |
650 |
not conforming to this specification. |
651 |
|
652 |
|
653 |
3.2.2. Conventional Representation of Newlines |
654 |
|
655 |
SGML specifies that a text entity is a sequence of records, |
656 |
each beginning with a record start character and ending with |
657 |
a record end character (code positions 10 and 13 |
658 |
respectively). (section 7.6.1, ``Record Boundaries'' in |
659 |
[SGML]) |
660 |
|
661 |
[MIME] specifies that a body of type `text/*' is a sequence |
662 |
of lines, each terminated by CRLF, that is octets 10, 13. |
663 |
|
664 |
In practice, HTML documents are frequently represented and |
665 |
transmitted using an end of line convention that depends on |
666 |
the conventions of the source of the document; frequently, |
667 |
that representation consists of CR only, LF only, or CR LF |
668 |
combination. Hence the decoding of the octets will often |
669 |
result in a text entity with some missing record start and |
670 |
record end characters. |
671 |
|
672 |
Since there is no ambiguity, HTML user agents are encouraged |
673 |
to infer the missing record start and end characters. |
674 |
|
675 |
An HTML user agent should treat end of line in any of its |
676 |
variations as a word space in all contexts except |
677 |
preformatted text. Within preformatted text, an HTML user |
678 |
agent should expect to treat any of the three common |
679 |
representations of end-of-line as starting a new line. |
680 |
|
681 |
|
682 |
3.3. Security Considerations |
683 |
|
684 |
Anchors, embedded images, and all other elements which |
685 |
contain URIs as parameters may cause the URI to be |
686 |
dereferenced in response to user input. In this case, the |
687 |
security considerations of the URI specification apply. |
688 |
|
689 |
The widely deployed methods for submitting forms requests -- |
690 |
HTTP and SMTP -- provide little assurance of |
691 |
confidentiality. Information providers who request sensitive |
692 |
information via forms -- especially by way of the `PASSWORD' |
693 |
type input field -- should be aware and make their users |
694 |
aware of the lack of confidentiality. |
695 |
|
696 |
> |
697 |
|
698 |
|
699 |
4. Document Structure Elements |
700 |
|
701 |
To identify information as an HTML document conforming to |
702 |
this specification, each document should start with the |
703 |
prologue: |
704 |
|
705 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> |
706 |
|
707 |
NOTE - If the body of a text/html body part does not |
708 |
begin with a document type declaration, an HTML user |
709 |
agent should infer the above document type declaration. |
710 |
|
711 |
HTML user agents are required to support the above document |
712 |
type declaration, the following document type declarations, |
713 |
and no others. |
714 |
|
715 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0 Strict//EN"> |
716 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML Strict//EN"> |
717 |
|
718 |
In particular, they may support other formal public |
719 |
identifiers, or document types altogether. They may support |
720 |
an internal declaration subset with supplemental entity, |
721 |
element, and other markup declarations, or they may not. |
722 |
|
723 |
|
724 |
4.1. HTML Document Element |
725 |
|
726 |
<HTML> ... </HTML> Level 0 |
727 |
|
728 |
The HTML document element is organized as a head and a body, |
729 |
much like a memo or a mail message. Within the head, you can |
730 |
specify the title and other information about the document. |
731 |
Within the body, you can structure text into paragraphs and |
732 |
lists, as well as highlight phrases and create links, using |
733 |
HTML elements. |
734 |
|
735 |
NOTE - The start and end tags for HTML, Head, and Body |
736 |
elements are omissible; however, this is not |
737 |
recommended since the head/body structure allows an |
738 |
implementation to determine certain properties of a |
739 |
document, such as the title, without parsing the entire |
740 |
document. |
741 |
|
742 |
< |
743 |
|
744 |
|
745 |
4.2. Head |
746 |
|
747 |
<HEAD> ... </HEAD> Level 0 |
748 |
|
749 |
The head of an HTML document is an unordered collection of |
750 |
information about the document. The Title element is |
751 |
required. |
752 |
|
753 |
<HEAD> |
754 |
<TITLE>Introduction to HTML</TITLE> |
755 |
</HEAD> |
756 |
|
757 |
|
758 |
4.3. Body |
759 |
|
760 |
<BODY> ... </BODY> Level 0 |
761 |
|
762 |
The Body element identifies the body component of an HTML |
763 |
document. Specifically, the body of a document may contain |
764 |
links, text, and formatting information within <BODY> and |
765 |
</BODY> tags. |
766 |
|
767 |
|
768 |
4.4. Title |
769 |
|
770 |
<TITLE> ... </TITLE> Level 0 |
771 |
|
772 |
Every HTML document must contain a Title element. The title |
773 |
should identify the contents of the document in a global |
774 |
context, and may be used in history lists and as a label for |
775 |
the window displaying the document. Unlike headings, titles |
776 |
are not rendered in the text of a document itself. |
777 |
|
778 |
The Title element must occur within the head of the |
779 |
document, and must not contain anchors, paragraph tags, or |
780 |
highlighting. Only one title is allowed in a document. |
781 |
|
782 |
NOTE - The length of a title is not limited; however, |
783 |
long titles may be truncated in some applications. To |
784 |
minimize this possibility, titles should be fewer than |
785 |
64 characters. Also keep in mind that a short title, |
786 |
such as Introduction, may be meaningless out of |
787 |
context. An example of a meaningful title might be |
788 |
``Introduction to HTML Elements.'' |
789 |
|
790 |
|
791 |
4.5. Base |
792 |
|
793 |
<BASE> Level 0 |
794 |
|
795 |
The Base element allows the URI of the document itself to be |
796 |
recorded in situations in which the document may be read out |
797 |
of context. URIs within the document may be in a ``partial'' |
798 |
form relative to this base address[RELURL]. |
799 |
|
800 |
The Base element has one attribute, HREF, which identifies |
801 |
the absolute base URI. |
802 |
|
803 |
|
804 |
4.6. Isindex |
805 |
|
806 |
<ISINDEX> Level 0 |
807 |
|
808 |
The Isindex element tells the interpreter that the document |
809 |
is an index. This means that the reader may request a |
810 |
keyword search on the resource by adding a question mark to |
811 |
the end of the document address, followed by a list of |
812 |
keywords separated by plus signs. |
813 |
|
814 |
The Isindex element is usually generated by the network |
815 |
server from which the document was obtained via a URI. The |
816 |
server must have a search engine that supports this feature |
817 |
for the resource. If the document URI is unknown to the |
818 |
interpreter, <isindex> must be ignored. |
819 |
|
820 |
|
821 |
4.7. Link |
822 |
|
823 |
<LINK> Level 0 |
824 |
|
825 |
The Link element indicates a relationship between the |
826 |
document and some other object. A document may have any |
827 |
number of Link elements. |
828 |
|
829 |
The Link element is empty (does not have a closing tag), but |
830 |
takes the same attributes as the Anchor element. |
831 |
|
832 |
Typical uses are to indicate authorship, related indexes and |
833 |
glossaries, older or more recent versions, etc. Links can |
834 |
indicate a static tree structure in which the document was |
835 |
authored by pointing to a ``parent'' and ``next'' and |
836 |
``previous'' document, for example. |
837 |
|
838 |
Servers may also allow links to be added by those who do not |
839 |
have the right to alter the body of a document. |
840 |
|
841 |
|
842 |
4.8. Meta |
843 |
|
844 |
<META> Level 0 |
845 |
|
846 |
The META element is used within the HEAD element to embed |
847 |
document metainformation not defined by other HTML elements. |
848 |
META elements can be extracted by servers and/or clients for |
849 |
use in identifying, indexing, and cataloging specialized |
850 |
document metainformation. |
851 |
|
852 |
Although it is generally preferable to use named elements |
853 |
which have well-defined semantics for each type of |
854 |
metainformation (e.g. TITLE), the META element is provided |
855 |
for situations where strict SGML parsing is necessary and |
856 |
the local DTD is not extensible. HTML interpreters may use |
857 |
the META element's content if they recognize and understand |
858 |
the semantics identified by the NAME or HTTP-EQUIV |
859 |
attributes, and may treat the content as metainformation |
860 |
(and not render it) even when they do not recognize the |
861 |
name. |
862 |
|
863 |
In addition, HTTP servers may wish to read the content of |
864 |
the document HEAD to generate header fields corresponding to |
865 |
any elements defining a value for the attribute HTTP-EQUIV. |
866 |
Note, however, that the method by which the server extracts |
867 |
document metainformation is not part of this specification, |
868 |
nor can it be assumed by authors that any given server will |
869 |
be capable of extracting it. The META element only provides |
870 |
an extensible mechanism for identifying and embedding |
871 |
document metainformation - how it may be used is up to the |
872 |
individual server implementation and the HTML interpreter. |
873 |
|
874 |
Attributes of the META element: |
875 |
|
876 |
HTTP-EQUIV |
877 |
This attribute binds the element to an HTTP header |
878 |
field. It means that if you know the semantics of |
879 |
the HTTP header field named by this attribute, |
880 |
then you can process the contents based on a |
881 |
well-defined syntactic mapping, whether or not |
882 |
your DTD tells you anything about it. HTTP header |
883 |
field names are not case sensitive. If not |
884 |
present, the attribute NAME should be used to |
885 |
identify this metainformation and the content |
886 |
should not be used within an HTTP response header. |
887 |
|
888 |
NAME |
889 |
Metainformation name. If the NAME attribute is not |
890 |
present, the name can be assumed to be equal to |
891 |
the value of HTTP-EQUIV. |
892 |
|
893 |
CONTENT |
894 |
The metainformation content to be associated with |
895 |
the given name. If multiple META elements are |
896 |
provided with the same name, their combined |
897 |
contents-concatenated as a comma-separated list-is |
898 |
the value associated with that name. |
899 |
|
900 |
Examples |
901 |
|
902 |
If the document contains: |
903 |
|
904 |
<META HTTP-EQUIV="Expires" |
905 |
CONTENT="Tue, 04 Dec 1993 21:29:02 GMT"> |
906 |
<meta http-equiv="Keywords" CONTENT="Fred, Barney"> |
907 |
<META HTTP-EQUIV="Reply-to" |
908 |
content="fielding@ics.uci.edu (Roy Fielding)"> |
909 |
|
910 |
then the server (if so configured) may include the following |
911 |
headers: |
912 |
|
913 |
Expires: Tue, 04 Dec 1993 21:29:02 GMT |
914 |
Keywords: Fred, Barney |
915 |
Reply-to: fielding@ics.uci.edu (Roy Fielding) |
916 |
|
917 |
as part of the HTTP response to a GET or HEAD request for |
918 |
that document. |
919 |
|
920 |
When the HTTP-EQUIV attribute is not present, the server |
921 |
should not generate an HTTP response header for the |
922 |
metainformation; e.g., |
923 |
|
924 |
<META NAME="IndexType" CONTENT="Service"> |
925 |
|
926 |
would never generate an HTTP response header, but would |
927 |
still allow HTML interpreters to identify and make use of |
928 |
that metainformation. |
929 |
|
930 |
The Meta element should never be used to define information |
931 |
that should be associated with an existing HTML element. An |
932 |
example of an inappropriate use of the Meta element is: |
933 |
|
934 |
<META NAME="Title" CONTENT="The Etymology of |
935 |
Dunsel"> |
936 |
|
937 |
Do not name an HTTP-EQUIV equal to a response header that |
938 |
should normally only be generated by the HTTP server. |
939 |
Example names that are inappropriate include ``Server'', |
940 |
``Date'', and ``Last-modified'' - the exact list of |
941 |
inappropriate names is dependent on the particular server |
942 |
implementation. We recommend that servers ignore any META |
943 |
elements which specify HTTP-equivalents which are equal |
944 |
(case-insensitively) to their own reserved response headers. |
945 |
|
946 |
|
947 |
4.9. Nextid |
948 |
|
949 |
<NEXTID> Level 0 |
950 |
|
951 |
The Nextid element is a parameter read and generated by text |
952 |
editing software to create unique identifiers. This tag |
953 |
takes a single attribute which is the next document-wide |
954 |
alpha- numeric identifier to be allocated of the form z123: |
955 |
|
956 |
<NEXTID N=Z27> |
957 |
|
958 |
When modifying a document, existing anchor identifiers |
959 |
should not be reused, as these identifiers may be referenced |
960 |
by other documents. Human writers of HTML usually use |
961 |
mnemonic alphabetical identifiers. |
962 |
|
963 |
HTML interpreters may ignore the Nextid element. Support for |
964 |
the Nextid element does not impact HTML interpreters in any |
965 |
way. |
966 |
|
967 |
|
968 |
5. Character Content |
969 |
|
970 |
An HTML user agent should present the body of an HTML |
971 |
document as a collection of typeset paragraphs and |
972 |
preformatted text. Except for the <PRE> element, each block |
973 |
structuring element is regarded as a paragraph by taking the |
974 |
data characters in its content and the content of its |
975 |
descendant elements, concatenating them, and splitting the |
976 |
result into words, separated by space, tab, or record end |
977 |
characters (and perhaps hyphen characters). The sequence of |
978 |
words is typeset as a paragraph by breaking it into lines. |
979 |
|
980 |
|
981 |
5.1. The ISO Latin 1 Character Repertoire |
982 |
|
983 |
The minimum character repertoire supported by all conforming |
984 |
HTML user agents is Latin Alphabet Nr. 1, or simply Latin-1. |
985 |
Latin-1 includes characters from most Western European |
986 |
languages, as well as a number of control characters. |
987 |
Latin-1 also includes a non-breaking space, a soft hyphen |
988 |
indicator, 93 graphical characters, 8 unassigned characters, |
989 |
and 25 control characters. |
990 |
|
991 |
NOTE - Use the non-breaking space and soft hyphen |
992 |
indicator characters is discouraged because support for |
993 |
them is not widely deployed. |
994 |
|
995 |
In SGML applications, the use of control characters is |
996 |
limited in order to maximize the chance of successful |
997 |
interchange over heterogeneous networks and operating |
998 |
systems. In HTML, only three control characters are allowed: |
999 |
Horizontal Tab (HT, encoded as 9 decimal in US-ASCII and |
1000 |
ISO-8859-1), Carriage Return, and Line Feed. |
1001 |
|
1002 |
The HTML DTD references the Added Latin 1 entity set, to |
1003 |
allow mnemonic representation of Latin 1 characters using |
1004 |
only the widely supported ASCII character repertoire. For |
1005 |
example: |
1006 |
|
1007 |
Kurt Gödel was a famous logician and mathematician. |
1008 |
|
1009 |
See 11.4.2, "ISO Latin 1 Character Entity Set" for a table |
1010 |
of the ``Added Latin 1'' entities, and 14.1, "The ISO-8859-1 |
1011 |
Coded Character Set" for a table of the code positions of |
1012 |
ISO-8859-1. |
1013 |
|
1014 |
|
1015 |
6. Data Elements |
1016 |
|
1017 |
|
1018 |
6.1. Line Break |
1019 |
|
1020 |
<BR> Level 0 |
1021 |
|
1022 |
The Line Break element specifies that a new line must be |
1023 |
started at the given point. A new line indents the same as |
1024 |
that of line-wrapped text. |
1025 |
|
1026 |
Example of use: |
1027 |
|
1028 |
<P> Pease porridge hot<BR> |
1029 |
Pease porridge cold<BR> |
1030 |
Pease porridge in the pot<BR> |
1031 |
Nine days old. |
1032 |
|
1033 |
|
1034 |
6.2. Horizontal Rule |
1035 |
|
1036 |
<HR> Level 0 |
1037 |
|
1038 |
A Horizontal Rule element is a divider between sections of |
1039 |
text such as a full width horizontal rule or equivalent |
1040 |
graphic. |
1041 |
|
1042 |
Example of use: |
1043 |
|
1044 |
<HR> |
1045 |
<ADDRESS>February 8, 1995, CERN</ADDRESS> |
1046 |
</BODY> |
1047 |
|
1048 |
|
1049 |
6.3. Image |
1050 |
|
1051 |
<IMG> Level 0 |
1052 |
|
1053 |
The Image element is used to incorporate in-line graphics |
1054 |
(typically icons or small graphics) into an HTML document. |
1055 |
This element cannot be used for embedding other HTML text. |
1056 |
|
1057 |
HTML interpreters that cannot render in-line images ignore |
1058 |
the Image element unless it contains the ALT attribute. Note |
1059 |
that some HTML interpreters can render linked graphics but |
1060 |
not in-line graphics. If a graphic is essential, you may |
1061 |
want to create a link to it rather than to put it in-line. |
1062 |
If the graphic is not essential, then the Image element is |
1063 |
appropriate. |
1064 |
|
1065 |
The Image element, which is empty (no closing tag), has |
1066 |
these attributes: |
1067 |
|
1068 |
ALIGN |
1069 |
The ALIGN attribute accepts the values TOP or |
1070 |
MIDDLE or BOTTOM, which specifies if the following |
1071 |
line of text is aligned with the top, middle, or |
1072 |
bottom of the graphic. |
1073 |
|
1074 |
ALT |
1075 |
Optional text as an alternative to the graphic for |
1076 |
rendering in non-graphical environments. Alternate |
1077 |
text should be provided whenever the graphic is |
1078 |
not rendered. Alternate text is mandatory for |
1079 |
Level 0 documents. Example of use: |
1080 |
|
1081 |
<IMG SRC="triangle.xbm" ALT="Warning:"> Be sure |
1082 |
to read these instructions. |
1083 |
|
1084 |
ISMAP |
1085 |
The ISMAP (is map) attribute identifies an image |
1086 |
as an image map. Image maps are graphics in which |
1087 |
certain regions are mapped to URIs. By clicking on |
1088 |
different regions, different resources can be |
1089 |
accessed from the same graphic. Example of use: |
1090 |
|
1091 |
<A HREF="http://machine/htbin/imagemap/sample"> |
1092 |
<IMG SRC="sample.xbm" ISMAP> |
1093 |
</A> |
1094 |
|
1095 |
SRC |
1096 |
The value of the SRC attribute is the URI of the |
1097 |
document to be embedded; only images can be |
1098 |
embedded, not HTML text. Its syntax is the same as |
1099 |
that of the HREF attribute of the `<A>' tag. SRC |
1100 |
is mandatory. Image elements are allowed within |
1101 |
anchors. |
1102 |
|
1103 |
Example of use: |
1104 |
|
1105 |
<IMG SRC="triangle.xbm">Be sure to read these |
1106 |
instructions. |
1107 |
|
1108 |
|
1109 |
7. Character Format Elements |
1110 |
|
1111 |
Character format elements are used to specify either the |
1112 |
logical meaning or the physical appearance of marked text |
1113 |
without causing a paragraph break. Like most other elements, |
1114 |
character format elements include both opening and closing |
1115 |
tags. Only the characters between the tags are affected: |
1116 |
|
1117 |
This is <EM>emphasized</EM> text. |
1118 |
|
1119 |
Character format tags may be ignored by minimal HTML |
1120 |
applications. |
1121 |
|
1122 |
Character format tags are interpreted from left to right as |
1123 |
they appear in the flow of text. Level 1 interpreters must |
1124 |
render highlighted text distinctly from plain text. |
1125 |
Additionally, EM content must be rendered as distinct from |
1126 |
STRONG content, and B content must rendered as distinct from |
1127 |
I content. |
1128 |
|
1129 |
Character format elements may be nested within the content |
1130 |
of other character format elements; however, HTML |
1131 |
interpreters are not required to render nested character |
1132 |
format elements distinctly from non-nested elements: |
1133 |
|
1134 |
plain <B>bold <I>italic</I></B> may the rendered |
1135 |
the same as plain <B>bold </B><I>italic</I> |
1136 |
|
1137 |
|
1138 |
7.1. Semantic Format Elements |
1139 |
|
1140 |
Note that typical renderings for semantic format elements |
1141 |
vary between applications. If a specific rendering is |
1142 |
necessary - for example, when referring to a specific text |
1143 |
attribute as in ``The italic parts are mandatory'' - a |
1144 |
physical formating element can be used to ensure that the |
1145 |
intended rendered is used where possible. |
1146 |
|
1147 |
Note that different sematic elements may be rendered in the |
1148 |
same way. |
1149 |
|
1150 |
|
1151 |
7.1.1. Citation |
1152 |
|
1153 |
<CITE>...</CITE> Level 1 |
1154 |
|
1155 |
The Citation element specifies a citation, typically |
1156 |
rendered as italics. |
1157 |
|
1158 |
|
1159 |
7.1.2. Code |
1160 |
|
1161 |
<CODE> ... </CODE> Level 1 |
1162 |
|
1163 |
The Code element indicates an example of code, typically |
1164 |
rendered in a monospaced font. This should not be confused |
1165 |
with the Preformatted Text element. |
1166 |
|
1167 |
|
1168 |
7.1.3. Emphasis |
1169 |
|
1170 |
<EM> ... </EM> Level 1 |
1171 |
|
1172 |
The Emphasis element indicates typographic emphasis, |
1173 |
typically rendered as italics. |
1174 |
|
1175 |
|
1176 |
7.1.4. Keyboard |
1177 |
|
1178 |
<KBD> ... </KBD> Level 1 |
1179 |
|
1180 |
The Keyboard element indicates text typed by a user, |
1181 |
typically rendered in a monospaced font. This is commonly |
1182 |
used in instruction manuals. |
1183 |
|
1184 |
|
1185 |
7.1.5. Sample |
1186 |
|
1187 |
<SAMP> ... </SAMP> Level 1 |
1188 |
|
1189 |
The Sample element indicates a sequence of literal |
1190 |
characters, typically rendered in a monospaced font. |
1191 |
|
1192 |
|
1193 |
7.1.6. Strong |
1194 |
|
1195 |
<STRONG> ... </STRONG> Level 1 |
1196 |
|
1197 |
The Strong element indicates strong typographic emphasis, |
1198 |
typically rendered in bold. |
1199 |
|
1200 |
|
1201 |
7.1.7. Variable |
1202 |
|
1203 |
<VAR> ... </VAR> Level 1 |
1204 |
|
1205 |
The Variable element indicates a variable name, typically |
1206 |
rendered as italic. |
1207 |
|
1208 |
|
1209 |
7.2. Physical Format Elements |
1210 |
|
1211 |
Physical format elements are used to specify the format of |
1212 |
marked text. |
1213 |
|
1214 |
|
1215 |
7.2.1. Bold |
1216 |
|
1217 |
<B> ... </B> Level 1 |
1218 |
|
1219 |
The Bold element specifies that the text should be rendered |
1220 |
in boldface, where available. Otherwise, an alternative |
1221 |
mapping is allowed. |
1222 |
|
1223 |
|
1224 |
7.2.2. Italic |
1225 |
|
1226 |
<I> ... </I> Level 1 |
1227 |
|
1228 |
The Italic element specifies that the text should be |
1229 |
rendered in an italic font, where available. Otherwise, an |
1230 |
alternative mapping is allowed. |
1231 |
|
1232 |
|
1233 |
7.2.3. Teletype |
1234 |
|
1235 |
<TT> ... </TT> Level 1 |
1236 |
|
1237 |
The Teletype element specifies that the text should be |
1238 |
rendered in a fixed-width typewriter font. |
1239 |
|
1240 |
|
1241 |
8. Hyperlink Elements |
1242 |
|
1243 |
|
1244 |
8.1. Anchor |
1245 |
|
1246 |
<A> ... </A> Level 0 |
1247 |
|
1248 |
An anchor is a marked section of text that is the start |
1249 |
and/or destination of a hypertext link. Anchor elements are |
1250 |
defined by the `<A>' tag. The `<A>' tag accepts several |
1251 |
attributes; at least one of the NAME and HREF attributes is |
1252 |
required. |
1253 |
|
1254 |
Attributes of the `<A>' tag: |
1255 |
|
1256 |
|
1257 |
8.1.1. HREF |
1258 |
|
1259 |
If the HREF attribute is present, the text between the |
1260 |
opening and closing anchor tags becomes hypertext. If this |
1261 |
hypertext is selected by readers, they are moved to another |
1262 |
document, or to a different location in the current |
1263 |
document, whose network address is defined by the value of |
1264 |
the HREF attribute. |
1265 |
|
1266 |
Example: |
1267 |
|
1268 |
See <A HREF="http://www.hal.com/">HaL</A>'s |
1269 |
information for more details. |
1270 |
|
1271 |
In this example, selecting ``HaL'' takes the reader to a |
1272 |
document at http://www.hal.com. The format of the network |
1273 |
address is specified in the URI specification for print |
1274 |
readers. |
1275 |
|
1276 |
With the HREF attribute, the form HREF=``#identifier'' can |
1277 |
refer to another anchor in the same document. |
1278 |
|
1279 |
Example: |
1280 |
|
1281 |
The <A HREF="#glossary">glossary</A> defines |
1282 |
terms used in this document. |
1283 |
|
1284 |
In this example, selecting ``glossary'' takes the reader to |
1285 |
another anchor (i.e., <A NAME=``glossary''>Glossary</A>) in |
1286 |
the same document. The NAME attribute is described below. If |
1287 |
the anchor is in another document, the HREF attribute may be |
1288 |
relative to the document's address or the specified base |
1289 |
address (see 4.5, "Base"). |
1290 |
|
1291 |
|
1292 |
8.1.2. NAME |
1293 |
|
1294 |
If present, the NAME attribute allows the anchor to be the |
1295 |
target of a link. The value of the NAME attribute is an |
1296 |
identifier for the anchor. Identifiers are arbitrary strings |
1297 |
but must be unique within the HTML document. |
1298 |
|
1299 |
Example of use: |
1300 |
|
1301 |
<A NAME="coffee">Coffee</A> is an example of ... |
1302 |
... An example of this is <A HREF="#coffee">coffee</A>. |
1303 |
|
1304 |
Another document can then make a reference explicitly to |
1305 |
this anchor by putting the identifier after the address, |
1306 |
separated by a hash sign: |
1307 |
|
1308 |
<A HREF="drinks.html#coffee"> |
1309 |
|
1310 |
|
1311 |
8.1.3. TITLE |
1312 |
|
1313 |
The TITLE attribute is informational only. If present, the |
1314 |
TITLE attribute should provide the title of the document |
1315 |
whose address is given by the HREF attribute. The TITLE |
1316 |
attribute is useful for at least two reasons. The HTML |
1317 |
interpreter may display the title of the document prior to |
1318 |
retrieving it, for example, as a margin note or on a small |
1319 |
box while the mouse is over the anchor, or while the |
1320 |
document is being loaded. Another reason is that documents |
1321 |
that are not marked up text, such as graphics, plain text |
1322 |
and Gopher menus, do not have titles. The TITLE attribute |
1323 |
can be used to provide a title to such documents. When using |
1324 |
the TITLE attribute, the title should be valid and unique |
1325 |
for the destination document. |
1326 |
|
1327 |
|
1328 |
8.1.4. REL |
1329 |
|
1330 |
The REL attribute gives the relationship(s) described by the |
1331 |
hypertext link from the anchor to the target. The value is a |
1332 |
whitespace-separated list of relationship names. |
1333 |
Relationship names and their semantics will be registered by |
1334 |
the W3 Consortium. The default relationship is void. The REL |
1335 |
attribute is only used when the HREF attribute is present. |
1336 |
|
1337 |
|
1338 |
8.1.5. REV |
1339 |
|
1340 |
The REV attribute is the same as the REL attribute, but the |
1341 |
semantics of the link type are in the reverse direction. A |
1342 |
link from A to B with REL=``X'' expresses the same |
1343 |
relationship as a link from B to A with REV=``X''. An anchor |
1344 |
may have both REL and REV attributes. |
1345 |
|
1346 |
|
1347 |
8.1.6. URN |
1348 |
|
1349 |
If present, the URN attribute specifies a uniform resource |
1350 |
name (URN) for a target document. The format of URNs is |
1351 |
under discussion (1995) by various working groups of the |
1352 |
Internet Engineering Task Force. |
1353 |
|
1354 |
|
1355 |
8.1.7. METHODS |
1356 |
|
1357 |
The METHODS attributes of anchors and links provide |
1358 |
information about the functions that the user may perform on |
1359 |
an object. These are more accurately given by the HTTP |
1360 |
protocol when it is used, but it may, for similar reasons as |
1361 |
for the TITLE attribute, be useful to include the |
1362 |
information in advance in the link. For example, the HTML |
1363 |
interpreter may chose a different rendering as a function of |
1364 |
the methods allowed; for example, something that is |
1365 |
searchable may get a different icon. |
1366 |
|
1367 |
The value of the METHODS attribute is a whitespace-separated |
1368 |
list of HTTP methods supported by the object for public use. |
1369 |
|
1370 |
|
1371 |
9. Block Structuring Elements |
1372 |
|
1373 |
The following elements may be included in the body of an |
1374 |
HTML document: |
1375 |
|
1376 |
|
1377 |
9.1. Paragraph |
1378 |
|
1379 |
<P> ... </P> Level 0 |
1380 |
|
1381 |
The Paragraph element indicates a paragraph. The exact |
1382 |
indentation, leading space, etc. of a paragraph is not |
1383 |
defined and may be a function of other tags, style sheets, |
1384 |
etc. |
1385 |
|
1386 |
Typically, paragraphs are surrounded by a vertical space of |
1387 |
one line or half a line. This is typically not the case |
1388 |
within the Address element and is never the case within the |
1389 |
Preformatted Text element. With some HTML interpreters, the |
1390 |
first line in a paragraph is indented. |
1391 |
|
1392 |
Example of use: |
1393 |
|
1394 |
<H1>This Heading Precedes the Paragraph</H1> |
1395 |
<P>This is the text of the first paragraph. |
1396 |
<P>This is the text of the second paragraph. Although you do not |
1397 |
need to start paragraphs on new lines, maintaining this |
1398 |
convention facilitates document maintenance.</P> |
1399 |
<P>This is the text of a third paragraph.</P> |
1400 |
|
1401 |
|
1402 |
9.2. Preformatted Text |
1403 |
|
1404 |
<PRE> ... </PRE> Level 0 |
1405 |
|
1406 |
The Preformatted Text element presents blocks of text in |
1407 |
fixed-width font, and so is suitable for text that has been |
1408 |
formatted on screen. |
1409 |
|
1410 |
The <PRE> tag may be used with the optional WIDTH attribute. |
1411 |
The WIDTH attribute specifies the maximum number of |
1412 |
characters for a line and allows the HTML interpreter to |
1413 |
select a suitable font and indentation. If the WIDTH |
1414 |
attribute is not present, a width of 80 characters is |
1415 |
assumed. Where the WIDTH attribute is supported, widths of |
1416 |
40, 80 and 132 characters should be presented optimally, |
1417 |
with other widths being rounded up. |
1418 |
|
1419 |
Within preformatted text: |
1420 |
|
1421 |
* Line breaks within the text are rendered as a move to |
1422 |
the beginning of the next line. |
1423 |
* Anchor elements and character highlighting elements |
1424 |
may be used. |
1425 |
* Elements that define paragraph formatting (headings, |
1426 |
address, etc.) must not be used. |
1427 |
* The horizontal tab character (encoded in US-ASCII and |
1428 |
ISO-8859-1 as decimal 9) must be interpreted as the |
1429 |
smallest positive nonzero number of spaces which will |
1430 |
leave the number of characters so far on the line as a |
1431 |
multiple of 8. Its use is not recommended however. |
1432 |
|
1433 |
NOTE - Som historical documents contain <P> tags in |
1434 |
<PRE> elements. User agents are engcouraged to treat |
1435 |
this a a line break. A <P> tag followed by a newline |
1436 |
character should produce only one line break, not a |
1437 |
line break plus a blank line. |
1438 |
|
1439 |
NOTE - References to the ``beginning of a new line'' do |
1440 |
not imply that the renderer is forbidden from using a |
1441 |
constant left indent for rendering preformatted text. |
1442 |
The left indent may be constrained by the width |
1443 |
required. |
1444 |
|
1445 |
Example of use: |
1446 |
|
1447 |
<PRE WIDTH="80"> |
1448 |
This is an example line. |
1449 |
</PRE> |
1450 |
|
1451 |
NOTE - Within a Preformatted Text element, the |
1452 |
constraint that the rendering must be on a fixed |
1453 |
horizontal character pitch may limit or prevent the |
1454 |
ability of the HTML interpreter to faithfully render |
1455 |
character formatting elements. |
1456 |
|
1457 |
|
1458 |
9.3. Address |
1459 |
|
1460 |
<ADDRESS> ... </ADDRESS> Level 0 |
1461 |
|
1462 |
The Address element specifies such information as address, |
1463 |
signature and authorship, often at the top or bottom of a |
1464 |
document. |
1465 |
|
1466 |
Typically, an Address is rendered in an italic typeface and |
1467 |
may be indented. The Address element implies a paragraph |
1468 |
break before and after. |
1469 |
|
1470 |
Example of use: |
1471 |
|
1472 |
<ADDRESS> |
1473 |
Newsletter editor<BR> |
1474 |
J.R. Brown<BR> |
1475 |
JimquickPost News, Jumquick, CT 01234<BR> |
1476 |
Tel (123) 456 7890 |
1477 |
</ADDRESS> |
1478 |
|
1479 |
|
1480 |
9.4. Blockquote |
1481 |
|
1482 |
<BLOCKQUOTE> ... </BLOCKQUOTE> Level 0 |
1483 |
|
1484 |
The Blockquote element is used to contain text quoted from |
1485 |
another source. |
1486 |
|
1487 |
A typical rendering might be a slight extra left and right |
1488 |
indent, and/or italic font. The Blockquote element causes a |
1489 |
paragraph break, and typically provides space above and |
1490 |
below the quote. |
1491 |
|
1492 |
Single-font rendition may reflect the quotation style of |
1493 |
Internet mail by putting a vertical line of graphic |
1494 |
characters, such as the greater than symbol (>), in the left |
1495 |
margin. |
1496 |
|
1497 |
Example of use: |
1498 |
|
1499 |
I think the poem ends |
1500 |
<BLOCKQUOTE> |
1501 |
<P>Soft you now, the fair Ophelia. Nymph, in thy orisons, be all |
1502 |
my sins remembered. |
1503 |
</BLOCKQUOTE> |
1504 |
but I am not sure. |
1505 |
|
1506 |
|
1507 |
9.5. Headings |
1508 |
|
1509 |
<H1> ... </H1> through <H6> ... </H6> Level 0 |
1510 |
|
1511 |
HTML defines six levels of heading. A Heading element |
1512 |
implies all the font changes, paragraph breaks before and |
1513 |
after, and white space necessary to render the heading. |
1514 |
|
1515 |
The highest level of headings is H1, followed by H2 ... H6. |
1516 |
|
1517 |
Example of use: |
1518 |
|
1519 |
<H1>This is a heading</H1> |
1520 |
Here is some text |
1521 |
<H2>Second level heading</H2> |
1522 |
Here is some more text. |
1523 |
|
1524 |
The rendering of headings is determined by the HTML |
1525 |
interpreter, but typical renderings are: |
1526 |
|
1527 |
<H1> ... </H1> |
1528 |
Bold, very-large font, centered. One or two blank |
1529 |
lines above and below. |
1530 |
|
1531 |
<H2> ... </H2> |
1532 |
Bold, large font, flush-left. One or two blank |
1533 |
lines above and below. |
1534 |
|
1535 |
<H3> ... </H3> |
1536 |
Italic, large font, slightly indented from the |
1537 |
left margin. One or two blank lines above and |
1538 |
below. |
1539 |
|
1540 |
<H4> ... </H4> |
1541 |
Bold, normal font, indented more than H3. One |
1542 |
blank line above and below. |
1543 |
|
1544 |
<H5> ... </H5> |
1545 |
Italic, normal font, indented as H4. One blank |
1546 |
line above. |
1547 |
|
1548 |
<H6> ... </H6> |
1549 |
Bold, indented same as normal text, more than H5. |
1550 |
One blank line above. |
1551 |
|
1552 |
Although heading levels can be skipped (for example, from H1 |
1553 |
to H3), this practice is discouraged as skipping heading |
1554 |
levels may produce unpredictable results when generating |
1555 |
other representations from HTML. |
1556 |
|
1557 |
|
1558 |
9.6. List Elements |
1559 |
|
1560 |
HTML supports several types of lists, all of which may be |
1561 |
nested. |
1562 |
|
1563 |
|
1564 |
9.6.1. Definition List |
1565 |
|
1566 |
<DL> ... </DL> Level 0 |
1567 |
|
1568 |
A definition list is a list of terms and corresponding |
1569 |
definitions. Definition lists are typically formatted with |
1570 |
the term flush-left and the definition, formatted paragraph |
1571 |
style, indented after the term. |
1572 |
|
1573 |
Example of use: |
1574 |
|
1575 |
<DL> |
1576 |
<DT>Term<DD>This is the definition of the first term. |
1577 |
<DT>Term<DD>This is the definition of the second term. |
1578 |
</DL> |
1579 |
|
1580 |
If the DT term does not fit in the DT column (one third of |
1581 |
the display area), it may be extended across the page with |
1582 |
the DD section moved to the next line, or it may be wrapped |
1583 |
onto successive lines of the left hand column. |
1584 |
|
1585 |
Single occurrences of a <DT> tag without a subsequent <DD> |
1586 |
tag are allowed, and have the same significance as if the |
1587 |
<DD> tag had been present with no text. |
1588 |
|
1589 |
The opening list tag must be <DL> and must be immediately |
1590 |
followed by the first term (<DT>). |
1591 |
|
1592 |
The definition list type can take the COMPACT attribute, |
1593 |
which suggests that a compact rendering be used, because the |
1594 |
list items are small and/or the entire list is large. |
1595 |
|
1596 |
Unless you provide the COMPACT attribute, the HTML |
1597 |
interpreter may leave white space between successive DT, DD |
1598 |
pairs. The COMPACT attribute may also reduce the width of |
1599 |
the left-hand (DT) column. |
1600 |
|
1601 |
If using the COMPACT attribute, the opening list tag must be |
1602 |
<DL COMPACT>, which must be immediately followed by the |
1603 |
first <DT> tag: |
1604 |
|
1605 |
<DL COMPACT> |
1606 |
<DT>Term<DD>This is the first definition in compact format. |
1607 |
<DT>Term<DD>This is the second definition in compact format. |
1608 |
</DL> |
1609 |
|
1610 |
|
1611 |
9.6.2. Directory List |
1612 |
|
1613 |
<DIR> ... </DIR> Level 0 |
1614 |
|
1615 |
A Directory List element is used to present a list of items |
1616 |
containing up to 20 characters each. Items in a directory |
1617 |
list may be arranged in columns, typically 24 characters |
1618 |
wide. If the HTML interpreter can optimize the column width |
1619 |
as function of the widths of individual elements, so much |
1620 |
the better. |
1621 |
|
1622 |
A directory list must begin with the <DIR> tag which is |
1623 |
immediately followed by a <LI> (list item) tag: |
1624 |
|
1625 |
<DIR> |
1626 |
<LI>A-H<LI>I-M |
1627 |
<LI>M-R<LI>S-Z |
1628 |
</DIR> |
1629 |
|
1630 |
|
1631 |
9.6.3. Menu List |
1632 |
|
1633 |
<MENU> ... </MENU> Level 0 |
1634 |
|
1635 |
A menu list is a list of items with typically one line per |
1636 |
item. The menu list style is more compact than the style of |
1637 |
an unordered list. |
1638 |
|
1639 |
A menu list must begin with a <MENU> tag which is |
1640 |
immediately followed by a <LI> (list item) tag: |
1641 |
|
1642 |
<MENU> |
1643 |
<LI>First item in the list. |
1644 |
<LI>Second item in the list. |
1645 |
<LI>Third item in the list. |
1646 |
</MENU> |
1647 |
|
1648 |
|
1649 |
9.6.4. Ordered List |
1650 |
|
1651 |
<OL> ... </OL> Level 0 |
1652 |
|
1653 |
The Ordered List element is used to present a numbered list |
1654 |
of items, sorted by sequence or order of importance. |
1655 |
|
1656 |
An ordered list must begin with the <OL> tag which is |
1657 |
immediately followed by a <LI> (list item) tag: |
1658 |
|
1659 |
<OL> |
1660 |
<LI>Click the Web button to open the Open the URI window. |
1661 |
<LI>Enter the URI number in the text field of the Open URI |
1662 |
window. The Web document you specified is displayed. |
1663 |
<LI>Click highlighted text to move from one link to another. |
1664 |
</OL> |
1665 |
|
1666 |
The Ordered List element can take the COMPACT attribute, |
1667 |
which suggests that a compact rendering be used. |
1668 |
|
1669 |
|
1670 |
9.6.5. Unordered List |
1671 |
|
1672 |
<UL> ... </UL> Level 0 |
1673 |
|
1674 |
The Unordered List element is used to present a list of |
1675 |
items which is typically separated by white space and/or |
1676 |
marked by bullets. |
1677 |
|
1678 |
An unordered list must begin with the <UL> tag which is |
1679 |
immediately followed by a <LI> (list item) tag: |
1680 |
|
1681 |
<UL> |
1682 |
<LI>First list item |
1683 |
<LI>Second list item |
1684 |
<LI>Third list item |
1685 |
</UL> |
1686 |
|
1687 |
|
1688 |
10. Form-based Input Elements |
1689 |
|
1690 |
Forms are created by placing input fields within paragraphs, |
1691 |
preformatted/literal text, and lists. This gives |
1692 |
considerable flexibility in designing the layout of forms. |
1693 |
|
1694 |
The following elements are used to create forms: |
1695 |
|
1696 |
FORM |
1697 |
A form within a document. |
1698 |
|
1699 |
INPUT |
1700 |
One input field. |
1701 |
|
1702 |
OPTION |
1703 |
One option within a Select element. |
1704 |
|
1705 |
SELECT |
1706 |
A selection from a finite set of options. |
1707 |
|
1708 |
TEXTAREA |
1709 |
A multi-line input field. |
1710 |
|
1711 |
Each variable field is defined by an Input, Textarea, or |
1712 |
Option element and must have an NAME attribute to identify |
1713 |
its value in the data returned when the form is submitted. |
1714 |
|
1715 |
Example of use (a questionnaire form): |
1716 |
|
1717 |
<H1>Sample Questionnaire</H1> |
1718 |
<P>Please fill out this questionnaire: |
1719 |
<FORM METHOD="POST" ACTION="http://www.w3.org/sample"> |
1720 |
<P>Your name: <INPUT NAME="name" size="48"> |
1721 |
<P>Male <INPUT NAME="gender" TYPE=RADIO VALUE="male"> |
1722 |
<P>Female <INPUT NAME="gender" TYPE=RADIO VALUE="female"> |
1723 |
<P>Number in family: <INPUT NAME="family" TYPE=text> |
1724 |
<P>Cities in which you maintain a residence: |
1725 |
<UL> |
1726 |
<LI>Kent <INPUT NAME="city" TYPE=checkbox VALUE="kent"> |
1727 |
<LI>Miami <INPUT NAME="city" TYPE=checkbox VALUE="miami"> |
1728 |
<LI>Other <TEXTAREA NAME="other" cols=48 rows=4></textarea> |
1729 |
</UL> |
1730 |
Nickname: <INPUT NAME="nickname" SIZE="42"> |
1731 |
<P>Thank you for responding to this questionnaire. |
1732 |
<P><INPUT TYPE=SUBMIT> <INPUT TYPE=RESET> |
1733 |
</FORM> |
1734 |
|
1735 |
In the example above, the <P> and <UL> tags have been used |
1736 |
to lay out the text and input fields. The HTML interpreter |
1737 |
is responsible for handling which field will currently get |
1738 |
keyboard input. |
1739 |
|
1740 |
Many platforms have existing conventions for forms, for |
1741 |
example, using Tab and Shift keys to move the keyboard focus |
1742 |
forwards and backwards between fields, and using the Enter |
1743 |
key to submit the form. In the example, the SUBMIT and RESET |
1744 |
buttons are specified explicitly with special purpose |
1745 |
fields. The SUBMIT button is used to e-mail the form or send |
1746 |
its contents to the server as specified by the ACTION |
1747 |
attribute, while RESET resets the fields to their initial |
1748 |
values. When the form consists of a single text field, it |
1749 |
may be appropriate to leave such buttons out and rely on the |
1750 |
Enter key. |
1751 |
|
1752 |
The Input element is used for a large variety of types of |
1753 |
input fields. |
1754 |
|
1755 |
To let users enter more than one line of text, use the |
1756 |
Textarea element. |
1757 |
|
1758 |
The radio button and checkbox types of input field can be |
1759 |
used to specify multiple choice forms in which every |
1760 |
alternative is visible as part of the form. An alternative |
1761 |
is to use the Select element which is typically rendered in |
1762 |
a more compact fashion as a pull down combo list. |
1763 |
|
1764 |
|
1765 |
10.1. Form |
1766 |
|
1767 |
<FORM> ... </FORM> Level 2 |
1768 |
|
1769 |
The Form element is used to delimit a data input form. There |
1770 |
can be several forms in a single document, but the Form |
1771 |
element can't be nested. |
1772 |
|
1773 |
The ACTION attribute is a URI specifying the location to |
1774 |
which the contents of the form is submitted to elicit a |
1775 |
response. If the ACTION attribute is missing, the URI of the |
1776 |
document itself is assumed. The way data is submitted varies |
1777 |
with the access protocol of the URI, and with the values of |
1778 |
the METHOD and ENCTYPE attributes. |
1779 |
|
1780 |
In general: |
1781 |
|
1782 |
* the METHOD attribute selects variations in the |
1783 |
protocol. |
1784 |
* the ENCTYPE attribute specifies the format of the |
1785 |
submitted data in case the protocol does not impose a |
1786 |
format itself. |
1787 |
|
1788 |
When the ACTION attribute is set to an HTTP URL, the METHOD |
1789 |
attribute must be set to an HTTP method [HTTP]. The default |
1790 |
method is GET, although for many applications the POST |
1791 |
method is preferred. With the POST method, the ENCTYPE |
1792 |
attribute is a media type specifying the format of the |
1793 |
posted data; the default is |
1794 |
``application/x-www-form-urlencoded''. |
1795 |
|
1796 |
The submitted contents of the form logically consist of |
1797 |
name/value pairs. The names are usually equal to the NAME |
1798 |
attributes of the various interactive elements in the form. |
1799 |
|
1800 |
NOTE - The names are not guaranteed to be unique keys, |
1801 |
nor are the names of form elements required to be |
1802 |
distinct. The values encode the user's input to the |
1803 |
corresponding interactive elements. Fields with null |
1804 |
values may be omitted from the returned list of |
1805 |
name/value pairs, whereas those with non-null values |
1806 |
should be included (even if the value was not altered |
1807 |
by the user). In particular, unselected radio buttons |
1808 |
and checkboxes should be excluded from the contents |
1809 |
list. |
1810 |
|
1811 |
|
1812 |
10.2. Input |
1813 |
|
1814 |
<INPUT> Level 2 |
1815 |
|
1816 |
The Input element represents a field whose contents may be |
1817 |
edited by the user. |
1818 |
|
1819 |
Attributes of the Input element: |
1820 |
|
1821 |
ALIGN |
1822 |
Vertical alignment of the image. For use only with |
1823 |
TYPE=IMAGE. The possible values are exactly the |
1824 |
same as for the ALIGN attribute of the image |
1825 |
element. |
1826 |
|
1827 |
CHECKED |
1828 |
Indicates that a checkbox or radio button is |
1829 |
selected. Unselected checkboxes and radio buttons |
1830 |
do not return name/value pairs when the form is |
1831 |
submitted. |
1832 |
|
1833 |
MAXLENGTH |
1834 |
Indicates the maximum number of characters that |
1835 |
can be entered into a text field. This can be |
1836 |
greater than specified by the SIZE attribute, in |
1837 |
which case the field will scroll appropriately. |
1838 |
The default number of characters is unlimited. |
1839 |
|
1840 |
NAME |
1841 |
Symbolic name used when transferring the form's |
1842 |
contents. The NAME attribute is required for most |
1843 |
input types and is normally used to provide a |
1844 |
unique identifier for a field, or for a logically |
1845 |
related group of fields. |
1846 |
|
1847 |
SIZE |
1848 |
Specifies the size or precision of the field |
1849 |
according to its type. For example, to specify a |
1850 |
field with a visible width of 24 characters: |
1851 |
|
1852 |
INPUT TYPE=text SIZE="24" |
1853 |
|
1854 |
SRC |
1855 |
A URI specifying an image. For use only with |
1856 |
TYPE=IMAGE. |
1857 |
|
1858 |
TYPE |
1859 |
Defines the type of data the field accepts. |
1860 |
Defaults to free text. Several types of fields can |
1861 |
be defined with the type attribute: |
1862 |
|
1863 |
CHECKBOX |
1864 |
Used for simple Boolean attributes, or for |
1865 |
attributes that can take multiple values at the |
1866 |
same time. The latter is represented by a number |
1867 |
of checkbox fields each of which has the same |
1868 |
name. Each selected checkbox generates a separate |
1869 |
name/value pair in the submitted data, even if |
1870 |
this results in duplicate names. The default value |
1871 |
for checkboxes is ``on''. |
1872 |
|
1873 |
HIDDEN |
1874 |
No field is presented to the user, but the content |
1875 |
of the field is sent with the submitted form. This |
1876 |
value may be used to transmit state information |
1877 |
about client/server interaction. |
1878 |
|
1879 |
IMAGE |
1880 |
An image field upon which you can click with a |
1881 |
pointing device, causing the form to be |
1882 |
immediately submitted. The coordinates of the |
1883 |
selected point are measured in pixel units from |
1884 |
the upper-left corner of the image, and are |
1885 |
returned (along with the other contents of the |
1886 |
form) in two name/value pairs. The x-coordinate is |
1887 |
submitted under the name of the field with ``.x'' |
1888 |
appended, and the y-coordinate is submitted under |
1889 |
the name of the field with ``.y'' appended. Any |
1890 |
VALUE attribute is ignored. The image itself is |
1891 |
specified by the SRC attribute, exactly as for the |
1892 |
Image element. |
1893 |
|
1894 |
NOTE - In a future version of the HTML specification, |
1895 |
the IMAGE functionality may be folded into an enhanced |
1896 |
SUBMIT field. |
1897 |
|
1898 |
PASSWORD |
1899 |
The same as the TEXT attribute, except that text |
1900 |
is not displayed as it is entered. |
1901 |
|
1902 |
RADIO |
1903 |
Used for attributes that accept a single value |
1904 |
from a set of alternatives. Each radio button |
1905 |
field in the group should be given the same name. |
1906 |
Only the selected radio button in the group |
1907 |
generates a name/value pair in the submitted data. |
1908 |
Radio buttons require an explicit VALUE attribute. |
1909 |
|
1910 |
RESET |
1911 |
A button that when pressed resets the form's |
1912 |
fields to their specified initial values. The |
1913 |
label to be displayed on the button may be |
1914 |
specified just as for the SUBMIT button. |
1915 |
|
1916 |
SUBMIT |
1917 |
A button that when pressed submits the form. You |
1918 |
can use the VALUE attribute to provide a |
1919 |
non-editable label to be displayed on the button. |
1920 |
The default label is application-specific. If a |
1921 |
SUBMIT button is pressed in order to submit the |
1922 |
form, and that button has a NAME attribute |
1923 |
specified, then that button contributes a |
1924 |
name/value pair to the submitted data. Otherwise, |
1925 |
a SUBMIT button makes no contribution to the |
1926 |
submitted data. |
1927 |
|
1928 |
TEXT |
1929 |
Used for a single line text entry fields. Use in |
1930 |
conjunction with the SIZE and MAXLENGTH |
1931 |
attributes. Use the Textarea element for text |
1932 |
fields which can accept multiple lines. |
1933 |
|
1934 |
VALUE |
1935 |
The initial displayed value of the field, if it |
1936 |
displays a textual or numerical value; or the |
1937 |
value to be returned when the field is selected, |
1938 |
if it displays a Boolean value. This attribute is |
1939 |
required for radio buttons. |
1940 |
|
1941 |
|
1942 |
10.3. Option |
1943 |
|
1944 |
<OPTION> Level 2 |
1945 |
|
1946 |
The Option element can only occur within a Select element. |
1947 |
It represents one choice, and can take these attributes: |
1948 |
|
1949 |
SELECTED |
1950 |
Indicates that this option is initially selected. |
1951 |
|
1952 |
VALUE |
1953 |
When present indicates the value to be returned if |
1954 |
this option is chosen. The returned value defaults |
1955 |
to the contents of the Option element. |
1956 |
|
1957 |
The contents of the Option element is presented to the user |
1958 |
to represent the option. It is used as a returned value if |
1959 |
the VALUE attribute is not present. |
1960 |
|
1961 |
|
1962 |
10.4. Select |
1963 |
|
1964 |
<SELECT NAME=... > ... </SELECT> Level 2 |
1965 |
|
1966 |
The Select element allows the user to chose one of a set of |
1967 |
alternatives described by textual labels. Every alternative |
1968 |
is represented by the Option element. Attributes are: |
1969 |
|
1970 |
MULTIPLE |
1971 |
The MULTIPLE attribute is needed when users are |
1972 |
allowed to make several selections, e.g. <SELECT |
1973 |
MULTIPLE>. |
1974 |
|
1975 |
NAME |
1976 |
Specifies the name that will submitted as a |
1977 |
name/value pair. |
1978 |
|
1979 |
SIZE |
1980 |
Specifies the number of visible items. If this is |
1981 |
greater than one, then the resulting form control |
1982 |
will be a list. |
1983 |
|
1984 |
The Select element is typically rendered as a pull down or |
1985 |
pop-up list. For example: |
1986 |
|
1987 |
<SELECT NAME="flavor"> |
1988 |
<OPTION>Vanilla |
1989 |
<OPTION>Strawberry |
1990 |
<OPTION>Rum and Raisin |
1991 |
<OPTION>Peach and Orange |
1992 |
</SELECT> |
1993 |
|
1994 |
If no option is initially marked as selected, then the first |
1995 |
item listed is selected. |
1996 |
|
1997 |
|
1998 |
10.5. Text Area |
1999 |
|
2000 |
<TEXTAREA> ... </TEXTAREA> Level 2 |
2001 |
|
2002 |
The Textarea element lets users enter more than one line of |
2003 |
text. For example: |
2004 |
|
2005 |
<TEXTAREA NAME="address" ROWS=64 COLS=6> |
2006 |
HaL Computer Systems |
2007 |
1315 Dell Avenue |
2008 |
Campbell, California 95008 |
2009 |
</TEXTAREA> |
2010 |
|
2011 |
The text up to the end tag (</TEXTAREA>) is used to |
2012 |
initialize the field's value. This end tag is always |
2013 |
required even if the field is initially blank. When |
2014 |
submitting a form, lines in a TEXTAREA should be terminated |
2015 |
using CRLF. |
2016 |
|
2017 |
In a typical rendering, the ROWS and COLS attributes |
2018 |
determine the visible dimension of the field in characters. |
2019 |
The field is rendered in a fixed-width font. HTML |
2020 |
interpreters should allow text to extend beyond these limits |
2021 |
by scrolling as needed. |
2022 |
|
2023 |
NOTE - In the initial design for forms, multi-line text |
2024 |
fields were supported by the Input element with |
2025 |
TYPE=TEXT. Unfortunately, this causes problems for |
2026 |
fields with long text values. SGML's default (Reference |
2027 |
Quantity Set) limits the length of attribute literals |
2028 |
to only 240 characters. The HTML 2.0 SGML declaration |
2029 |
increases the limit to 1024 characters. |
2030 |
|
2031 |
|
2032 |
11. HTML Public Text |
2033 |
|
2034 |
|
2035 |
11.1. HTML DTD |
2036 |
|
2037 |
This is the Document Type Definition for the HyperText |
2038 |
Markup Language. |
2039 |
|
2040 |
<!-- html.dtd |
2041 |
|
2042 |
Document Type Definition for the HyperText Markup Language |
2043 |
(HTML DTD) |
2044 |
5 |
2045 |
$Id: html.dtd,v 1.25 1995/03/29 18:53:13 connolly Exp $ |
2046 |
|
2047 |
Author: Daniel W. Connolly <connolly@w3.org> |
2048 |
See Also: html.decl, html-0.dtd, html-1.dtd |
2049 |
10 http://info.cern.ch/hypertext/WWW/MarkUp/MarkUp.html |
2050 |
--> |
2051 |
|
2052 |
<!ENTITY % HTML.Version |
2053 |
"-//IETF//DTD HTML 2.0//EN" |
2054 |
15 |
2055 |
-- Typical usage: |
2056 |
|
2057 |
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN"> |
2058 |
<html> |
2059 |
20 ... |
2060 |
</html> |
2061 |
-- |
2062 |
> |
2063 |
|
2064 |
25 |
2065 |
<!--============ Feature Test Entities ========================--> |
2066 |
|
2067 |
<!ENTITY % HTML.Recommended "IGNORE" |
2068 |
-- Certain features of the language are necessary for |
2069 |
30 compatibility with widespread usage, but they may |
2070 |
compromise the structural integrity of a document. |
2071 |
This feature test entity enables a more prescriptive |
2072 |
document type definition that eliminates |
2073 |
those features. |
2074 |
35 --> |
2075 |
|
2076 |
<![ %HTML.Recommended [ |
2077 |
<!ENTITY % HTML.Deprecated "IGNORE"> |
2078 |
]]> |
2079 |
40 |
2080 |
<!ENTITY % HTML.Deprecated "INCLUDE" |
2081 |
-- Certain features of the language are necessary for |
2082 |
compatibility with earlier versions of the specification, |
2083 |
but they tend to be used an implemented inconsistently, |
2084 |
45 and their use is deprecated. This feature test entity |
2085 |
enables a document type definition that eliminates |
2086 |
these features. |
2087 |
--> |
2088 |
|
2089 |
50 <!ENTITY % HTML.Highlighting "INCLUDE" |
2090 |
-- Use this feature test entity to validate that a |
2091 |
document uses no highlighting tags, which may be |
2092 |
ignored on minimal implementations. |
2093 |
--> |
2094 |
55 |
2095 |
<!ENTITY % HTML.Forms "INCLUDE" |
2096 |
-- Use this feature test entity to validate that a document |
2097 |
contains no forms, which may not be supported in minimal |
2098 |
implementations |
2099 |
60 --> |
2100 |
|
2101 |
<!--============== Imported Names ==============================--> |
2102 |
|
2103 |
<!ENTITY % Content-Type "CDATA" |
2104 |
65 -- meaning an internet media type |
2105 |
(aka MIME content type, as per RFC1521) |
2106 |
--> |
2107 |
|
2108 |
<!ENTITY % HTTP-Method "GET | POST" |
2109 |
70 -- as per HTTP specification, in progress |
2110 |
--> |
2111 |
|
2112 |
<!ENTITY % URI "CDATA" |
2113 |
-- The term URI means a CDATA attribute |
2114 |
75 whose value is a Uniform Resource Identifier, |
2115 |
as defined by |
2116 |
"Universal Resource Identifiers" by Tim Berners-Lee |
2117 |
aka RFC 1630 |
2118 |
|
2119 |
80 Note that CDATA attributes are limited by the LITLEN |
2120 |
capacity (1024 in the current version of html.decl), |
2121 |
so that URIs in HTML have a bounded length. |
2122 |
|
2123 |
--> |
2124 |
85 |
2125 |
|
2126 |
<!--========= DTD "Macros" =====================--> |
2127 |
|
2128 |
<!ENTITY % heading "H1|H2|H3|H4|H5|H6"> |
2129 |
90 |
2130 |
<!ENTITY % list " UL | OL | DIR | MENU " > |
2131 |
|
2132 |
|
2133 |
<!--======= Character mnemonic entities =================--> |
2134 |
95 |
2135 |
<!ENTITY % ISOlat1 PUBLIC |
2136 |
"ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML"> |
2137 |
%ISOlat1; |
2138 |
|
2139 |
100 <!ENTITY amp CDATA "&" -- ampersand --> |
2140 |
<!ENTITY gt CDATA ">" -- greater than --> |
2141 |
<!ENTITY lt CDATA "<" -- less than --> |
2142 |
<!ENTITY quot CDATA """ -- double quote --> |
2143 |
|
2144 |
105 |
2145 |
<!--========= SGML Document Access (SDA) Parameter Entities =====--> |
2146 |
|
2147 |
<!-- HTML 2.0 contains SGML Document Access (SDA) fixed attributes |
2148 |
in support of easy transformation to the International Committee |
2149 |
110 for Accessible Document Design (ICADD) DTD |
2150 |
"-//EC-USA-CDA/ICADD//DTD ICADD22//EN". |
2151 |
ICADD applications are designed to support usable access to |
2152 |
structured information by print-impaired individuals through |
2153 |
Braille, large print and voice synthesis. For more information on |
2154 |
115 SDA & ICADD: |
2155 |
- ISO 12083:1993, Annex A.8, Facilities for Braille, |
2156 |
large print and computer voice |
2157 |
- ICADD ListServ |
2158 |
<ICADD%ASUACAD.BITNET@ARIZVM1.ccit.arizona.edu> |
2159 |
120 - Usenet news group bit.listserv.easi |
2160 |
- Recording for the Blind, +1 800 221 4792 |
2161 |
--> |
2162 |
|
2163 |
<!ENTITY % SDAFORM "SDAFORM CDATA #FIXED" |
2164 |
125 -- one to one mapping --> |
2165 |
<!ENTITY % SDARULE "SDARULE CDATA #FIXED" |
2166 |
-- context-sensitive mapping --> |
2167 |
<!ENTITY % SDAPREF "SDAPREF CDATA #FIXED" |
2168 |
-- generated text prefix --> |
2169 |
130 <!ENTITY % SDASUFF "SDASUFF CDATA #FIXED" |
2170 |
-- generated text suffix --> |
2171 |
<!ENTITY % SDASUSP "SDASUSP NAME #FIXED" |
2172 |
-- suspend transform process --> |
2173 |
|
2174 |
135 |
2175 |
<!--========== Text Markup =====================--> |
2176 |
|
2177 |
<![ %HTML.Highlighting [ |
2178 |
|
2179 |
140 <!ENTITY % font " TT | B | I "> |
2180 |
|
2181 |
<!ENTITY % phrase "EM | STRONG | CODE | SAMP | KBD | VAR | CITE "> |
2182 |
|
2183 |
<!ENTITY % text "#PCDATA | A | IMG | BR | %phrase | %font"> |
2184 |
145 |
2185 |
<!ELEMENT (%font;|%phrase) - - (%text)*> |
2186 |
<!ATTLIST ( TT | CODE | SAMP | KBD | VAR ) |
2187 |
%SDAFORM; "Lit" |
2188 |
> |
2189 |
150 <!ATTLIST ( B | STRONG ) |
2190 |
%SDAFORM; "B" |
2191 |
> |
2192 |
<!ATTLIST ( I | EM | CITE ) |
2193 |
%SDAFORM; "It" |
2194 |
155 > |
2195 |
|
2196 |
<!-- <TT> Typewriter text --> |
2197 |
<!-- <B> Bold text --> |
2198 |
<!-- <I> Italic text --> |
2199 |
160 |
2200 |
<!-- <EM> Emphasized phrase --> |
2201 |
<!-- <STRONG> Strong emphais --> |
2202 |
<!-- <CODE> Source code phrase --> |
2203 |
<!-- <SAMP> Sample text or characters --> |
2204 |
165 <!-- <KBD> Keyboard phrase, e.g. user input --> |
2205 |
<!-- <VAR> Variable phrase or substituable --> |
2206 |
<!-- <CITE> Name or title of cited work --> |
2207 |
|
2208 |
<!ENTITY % pre.content "#PCDATA | A | HR | BR | %font | %phrase"> |
2209 |
170 |
2210 |
]]> |
2211 |
|
2212 |
<!ENTITY % text "#PCDATA | A | IMG | BR"> |
2213 |
|
2214 |
175 <!ELEMENT BR - O EMPTY> |
2215 |
<!ATTLIST BR |
2216 |
%SDAPREF; "&#RE;" |
2217 |
> |
2218 |
|
2219 |
180 <!-- <BR> Line break --> |
2220 |
|
2221 |
|
2222 |
<!--========= Link Markup ======================--> |
2223 |
|
2224 |
185 <![ %HTML.Recommended [ |
2225 |
<!ENTITY % linkName "ID"> |
2226 |
]]> |
2227 |
|
2228 |
<!ENTITY % linkName "CDATA"> |
2229 |
190 |
2230 |
<!ENTITY % linkType "NAME" |
2231 |
-- a list of these will be specified at a later date --> |
2232 |
|
2233 |
<!ENTITY % linkExtraAttributes |
2234 |
195 "REL %linkType #IMPLIED |
2235 |
REV %linkType #IMPLIED |
2236 |
URN CDATA #IMPLIED |
2237 |
TITLE CDATA #IMPLIED |
2238 |
METHODS NAMES #IMPLIED |
2239 |
200 "> |
2240 |
|
2241 |
<![ %HTML.Recommended [ |
2242 |
<!ENTITY % A.content "(%text)*" |
2243 |
-- <H1><a name="xxx">Heading</a></H1> |
2244 |
205 is preferred to |
2245 |
<a name="xxx"><H1>Heading</H1></a> |
2246 |
--> |
2247 |
]]> |
2248 |
|
2249 |
210 <!ENTITY % A.content "(%heading|%text)*"> |
2250 |
|
2251 |
<!ELEMENT A - - %A.content -(A)> |
2252 |
<!ATTLIST A |
2253 |
HREF %URI #IMPLIED |
2254 |
215 NAME %linkName #IMPLIED |
2255 |
%linkExtraAttributes; |
2256 |
%SDAPREF; "<Anchor: #AttList>" |
2257 |
> |
2258 |
<!-- <A> Anchor; source/destination of link --> |
2259 |
220 <!-- <A NAME="..."> Name of this anchor --> |
2260 |
<!-- <A HREF="..."> Address of link destination --> |
2261 |
<!-- <A URN="..."> Permanent address of destination --> |
2262 |
<!-- <A REL=...> Relationship to destination --> |
2263 |
<!-- <A REV=...> Relationship of destination to this --> |
2264 |
225 <!-- <A TITLE="..."> Title of destination (advisory) --> |
2265 |
<!-- <A METHODS="..."> Operations on destination (advisory) --> |
2266 |
|
2267 |
|
2268 |
<!--========== Images ==========================--> |
2269 |
230 |
2270 |
<!ELEMENT IMG - O EMPTY> |
2271 |
<!ATTLIST IMG |
2272 |
SRC %URI; #REQUIRED |
2273 |
ALT CDATA #IMPLIED |
2274 |
235 ALIGN (top|middle|bottom) #IMPLIED |
2275 |
ISMAP (ISMAP) #IMPLIED |
2276 |
%SDAPREF; "<Fig><?SDATrans Img: #AttList>#AttVal(Alt)</Fig>" |
2277 |
> |
2278 |
|
2279 |
240 <!-- <IMG> Image; icon, glyph or illustration --> |
2280 |
<!-- <IMG SRC="..."> Address of image object --> |
2281 |
<!-- <IMG ALT="..."> Textual alternative --> |
2282 |
<!-- <IMG ALIGN=...> Position relative to text --> |
2283 |
<!-- <IMG ISMAP> Each pixel can be a link --> |
2284 |
245 |
2285 |
<!--========== Paragraphs=======================--> |
2286 |
|
2287 |
<!ELEMENT P - O (%text)*> |
2288 |
<!ATTLIST P |
2289 |
250 %SDAFORM; "Para" |
2290 |
> |
2291 |
|
2292 |
<!-- <P> Paragraph --> |
2293 |
|
2294 |
255 |
2295 |
<!--========== Headings, Titles, Sections ===============--> |
2296 |
|
2297 |
<!ELEMENT HR - O EMPTY> |
2298 |
<!ATTLIST HR |
2299 |
260 %SDAPREF; "&#RE;&#RE;" |
2300 |
> |
2301 |
|
2302 |
<!-- <HR> Horizontal rule --> |
2303 |
|
2304 |
265 <!ELEMENT ( %heading ) - - (%text;)*> |
2305 |
<!ATTLIST H1 |
2306 |
%SDAFORM; "H1" |
2307 |
> |
2308 |
<!ATTLIST H2 |
2309 |
270 %SDAFORM; "H2" |
2310 |
> |
2311 |
<!ATTLIST H3 |
2312 |
%SDAFORM; "H3" |
2313 |
> |
2314 |
275 <!ATTLIST H4 |
2315 |
%SDAFORM; "H4" |
2316 |
> |
2317 |
<!ATTLIST H5 |
2318 |
%SDAFORM; "H5" |
2319 |
280 > |
2320 |
<!ATTLIST H6 |
2321 |
%SDAFORM; "H6" |
2322 |
> |
2323 |
|
2324 |
285 <!-- <H1> Heading, level 1 --> |
2325 |
<!-- <H2> Heading, level 2 --> |
2326 |
<!-- <H3> Heading, level 3 --> |
2327 |
<!-- <H4> Heading, level 4 --> |
2328 |
<!-- <H5> Heading, level 5 --> |
2329 |
290 <!-- <H6> Heading, level 6 --> |
2330 |
|
2331 |
|
2332 |
<!--========== Text Flows ======================--> |
2333 |
|
2334 |
295 <![ %HTML.Forms [ |
2335 |
<!ENTITY % block.forms "BLOCKQUOTE | FORM | ISINDEX"> |
2336 |
]]> |
2337 |
|
2338 |
<!ENTITY % block.forms "BLOCKQUOTE"> |
2339 |
300 |
2340 |
<![ %HTML.Deprecated [ |
2341 |
<!ENTITY % preformatted "PRE | XMP | LISTING"> |
2342 |
]]> |
2343 |
|
2344 |
305 <!ENTITY % preformatted "PRE"> |
2345 |
|
2346 |
<!ENTITY % block "P | %list | DL |
2347 |
| %preformatted |
2348 |
| %block.forms"> |
2349 |
310 |
2350 |
<!ENTITY % flow "(%text|%block)*"> |
2351 |
|
2352 |
<!ENTITY % pre.content "#PCDATA | A | HR | BR"> |
2353 |
<!ELEMENT PRE - - (%pre.content)*> |
2354 |
315 <!ATTLIST PRE |
2355 |
WIDTH NUMBER #implied |
2356 |
%SDAFORM; "Lit" |
2357 |
> |
2358 |
|
2359 |
320 <!-- <PRE> Preformatted text --> |
2360 |
<!-- <PRE WIDTH=...> Maximum characters per line --> |
2361 |
|
2362 |
<![ %HTML.Deprecated [ |
2363 |
|
2364 |
325 <!ENTITY % literal "CDATA" |
2365 |
-- historical, non-conforming parsing mode where |
2366 |
the only markup signal is the end tag |
2367 |
in full |
2368 |
--> |
2369 |
330 |
2370 |
<!ELEMENT (XMP|LISTING) - - %literal> |
2371 |
<!ATTLIST XMP |
2372 |
%SDAFORM; "Lit" |
2373 |
%SDAPREF; "Example:&#RE;" |
2374 |
335 > |
2375 |
<!ATTLIST LISTING |
2376 |
%SDAFORM; "Lit" |
2377 |
%SDAPREF; "Listing:&#RE;" |
2378 |
> |
2379 |
340 |
2380 |
<!-- <XMP> Example section --> |
2381 |
<!-- <LISTING> Computer listing --> |
2382 |
|
2383 |
<!ELEMENT PLAINTEXT - O %literal> |
2384 |
345 <!-- <PLAINTEXT> Plain text passage --> |
2385 |
|
2386 |
<!ATTLIST PLAINTEXT |
2387 |
%SDAFORM; "Lit" |
2388 |
> |
2389 |
350 ]]> |
2390 |
|
2391 |
|
2392 |
<!--========== Lists ==================--> |
2393 |
|
2394 |
355 <!ELEMENT DL - - (DT | DD)+> |
2395 |
<!ATTLIST DL |
2396 |
COMPACT (COMPACT) #IMPLIED |
2397 |
%SDAFORM; "List" |
2398 |
%SDAPREF; "Definition List:" |
2399 |
360 > |
2400 |
|
2401 |
<!ELEMENT DT - O (%text)*> |
2402 |
<!ATTLIST DT |
2403 |
%SDAFORM; "Term" |
2404 |
365 > |
2405 |
|
2406 |
<!ELEMENT DD - O %flow> |
2407 |
<!ATTLIST DD |
2408 |
%SDAFORM; "LItem" |
2409 |
370 > |
2410 |
|
2411 |
<!-- <DL> Definition list, or glossary --> |
2412 |
<!-- <DL COMPACT> Compact style list --> |
2413 |
<!-- <DT> Term in definition list --> |
2414 |
375 <!-- <DD> Definition of term --> |
2415 |
|
2416 |
<!ELEMENT (OL|UL) - - (LI)+> |
2417 |
<!ATTLIST OL |
2418 |
COMPACT (COMPACT) #IMPLIED |
2419 |
380 %SDAFORM; "List" |
2420 |
> |
2421 |
<!ATTLIST UL |
2422 |
COMPACT (COMPACT) #IMPLIED |
2423 |
%SDAFORM; "List" |
2424 |
385 > |
2425 |
<!-- <UL> Unordered list --> |
2426 |
<!-- <UL COMPACT> Compact list style --> |
2427 |
<!-- <OL> Ordered, or numbered list --> |
2428 |
<!-- <OL COMPACT> Compact list style --> |
2429 |
390 |
2430 |
|
2431 |
<!ELEMENT (DIR|MENU) - - (LI)+ -(%block)> |
2432 |
<!ATTLIST DIR |
2433 |
COMPACT (COMPACT) #IMPLIED |
2434 |
395 %SDAFORM; "List" |
2435 |
%SDAPREF; "<LHead>Directory</LHead>" |
2436 |
> |
2437 |
<!ATTLIST MENU |
2438 |
COMPACT (COMPACT) #IMPLIED |
2439 |
400 %SDAFORM; "List" |
2440 |
%SDAPREF; "<LHead>Menu</LHead>" |
2441 |
> |
2442 |
|
2443 |
<!-- <DIR> Directory list --> |
2444 |
405 <!-- <DIR COMPACT> Compact list style --> |
2445 |
<!-- <MENU> Menu list --> |
2446 |
<!-- <MENU COMPACT> Compact list style --> |
2447 |
|
2448 |
<!ELEMENT LI - O %flow> |
2449 |
410 <!ATTLIST LI |
2450 |
%SDAFORM; "LItem" |
2451 |
> |
2452 |
|
2453 |
<!-- <LI> List item --> |
2454 |
415 |
2455 |
<!--========== Document Body ===================--> |
2456 |
|
2457 |
<![ %HTML.Recommended [ |
2458 |
<!ENTITY % body.content "(%heading|%block|HR|ADDRESS|IMG)*" |
2459 |
420 -- <h1>Heading</h1> |
2460 |
<p>Text ... |
2461 |
is preferred to |
2462 |
<h1>Heading</h1> |
2463 |
Text ... |
2464 |
425 --> |
2465 |
]]> |
2466 |
|
2467 |
<!ENTITY % body.content "(%heading | %text | %block | |
2468 |
HR | ADDRESS)*"> |
2469 |
430 |
2470 |
<!ELEMENT BODY O O %body.content> |
2471 |
|
2472 |
<!-- <BODY> Document body --> |
2473 |
|
2474 |
435 <!ELEMENT BLOCKQUOTE - - %body.content> |
2475 |
<!ATTLIST BLOCKQUOTE |
2476 |
%SDAFORM; "BQ" |
2477 |
> |
2478 |
|
2479 |
440 <!-- <BLOCKQUOTE> Quoted passage --> |
2480 |
|
2481 |
<!ELEMENT ADDRESS - - (%text|P)*> |
2482 |
<!ATTLIST ADDRESS |
2483 |
%SDAFORM; "Lit" |
2484 |
445 %SDAPREF; "Address:&#RE;" |
2485 |
> |
2486 |
|
2487 |
<!-- <ADDRESS> Address, signature, or byline --> |
2488 |
|
2489 |
450 |
2490 |
<!--======= Forms ====================--> |
2491 |
|
2492 |
<![ %HTML.Forms [ |
2493 |
|
2494 |
455 <!ELEMENT FORM - - %body.content -(FORM) +(INPUT|SELECT|TEXTAREA)> |
2495 |
<!ATTLIST FORM |
2496 |
ACTION %URI #IMPLIED |
2497 |
METHOD (%HTTP-Method) GET |
2498 |
ENCTYPE %Content-Type; "application/x-www-form-urlencoded" |
2499 |
460 %SDAPREF; "<Para>Form:</Para>" |
2500 |
%SDASUFF; "<Para>Form End.</Para>" |
2501 |
> |
2502 |
|
2503 |
<!-- <FORM> Fill-out or data-entry form --> |
2504 |
465 <!-- <FORM ACTION="..."> Address for completed form --> |
2505 |
<!-- <FORM METHOD=...> Method of submitting form --> |
2506 |
<!-- <FORM ENCTYPE="..."> Representation of form data --> |
2507 |
|
2508 |
<!ENTITY % InputType "(TEXT | PASSWORD | CHECKBOX | |
2509 |
470 RADIO | SUBMIT | RESET | |
2510 |
IMAGE | HIDDEN )"> |
2511 |
<!ELEMENT INPUT - O EMPTY> |
2512 |
<!ATTLIST INPUT |
2513 |
TYPE %InputType TEXT |
2514 |
475 NAME CDATA #IMPLIED |
2515 |
VALUE CDATA #IMPLIED |
2516 |
SRC %URI #IMPLIED |
2517 |
CHECKED (CHECKED) #IMPLIED |
2518 |
SIZE CDATA #IMPLIED |
2519 |
480 MAXLENGTH NUMBER #IMPLIED |
2520 |
ALIGN (top|middle|bottom) #IMPLIED |
2521 |
%SDAPREF; "Input: " |
2522 |
> |
2523 |
|
2524 |
485 <!-- <INPUT> Form input datum --> |
2525 |
<!-- <INPUT TYPE=...> Type of input interaction --> |
2526 |
<!-- <INPUT NAME=...> Name of form datum --> |
2527 |
<!-- <INPUT VALUE="..."> Default/initial/selected value --> |
2528 |
<!-- <INPUT SRC="..."> Address of image --> |
2529 |
490 <!-- <INPUT CHECKED> Initial state is "on" --> |
2530 |
<!-- <INPUT SIZE=...> Field size hint --> |
2531 |
<!-- <INPUT MAXLENGTH=...> Data length maximum --> |
2532 |
<!-- <INPUT ALIGN=...> Image alignment --> |
2533 |
|
2534 |
495 <!ELEMENT SELECT - - (OPTION+) -(INPUT|SELECT|TEXTAREA)> |
2535 |
<!ATTLIST SELECT |
2536 |
NAME CDATA #REQUIRED |
2537 |
SIZE NUMBER #IMPLIED |
2538 |
MULTIPLE (MULTIPLE) #IMPLIED |
2539 |
500 %SDAFORM; "List" |
2540 |
%SDAPREF; |
2541 |
"<LHead>Select #AttVal(Multiple)</LHead>" |
2542 |
> |
2543 |
|
2544 |
505 <!-- <SELECT> Selection of option(s) --> |
2545 |
<!-- <SELECT NAME=...> Name of form datum --> |
2546 |
<!-- <SELECT SIZE=...> Options displayed at a time --> |
2547 |
<!-- <SELECT MULTIPLE> Multiple selections allowed --> |
2548 |
|
2549 |
510 <!ELEMENT OPTION - O (#PCDATA)*> |
2550 |
<!ATTLIST OPTION |
2551 |
SELECTED (SELECTED) #IMPLIED |
2552 |
VALUE CDATA #IMPLIED |
2553 |
%SDAFORM; "LItem" |
2554 |
515 %SDAPREF; |
2555 |
"Option: #AttVal(Value) #AttVal(Selected)" |
2556 |
> |
2557 |
|
2558 |
<!-- <OPTION> A selection option --> |
2559 |
520 <!-- <OPTION SELECTED> Initial state --> |
2560 |
<!-- <OPTION VALUE="..."> Form datum value for this option--> |
2561 |
|
2562 |
<!ELEMENT TEXTAREA - - (#PCDATA)* -(INPUT|SELECT|TEXTAREA)> |
2563 |
<!ATTLIST TEXTAREA |
2564 |
525 NAME CDATA #REQUIRED |
2565 |
ROWS NUMBER #REQUIRED |
2566 |
COLS NUMBER #REQUIRED |
2567 |
%SDAFORM; "Para" |
2568 |
%SDAPREF; "Input Text -- #AttVal(Name): " |
2569 |
530 > |
2570 |
|
2571 |
<!-- <TEXTAREA> An area for text input --> |
2572 |
<!-- <TEXTAREA NAME=...> Name of form datum --> |
2573 |
<!-- <TEXTAREA ROWS=...> Height of area --> |
2574 |
535 <!-- <TEXTAREA COLS=...> Width of area --> |
2575 |
|
2576 |
]]> |
2577 |
|
2578 |
|
2579 |
540 <!--======= Document Head ======================--> |
2580 |
|
2581 |
<![ %HTML.Recommended [ |
2582 |
<!ENTITY % head.extra "META* & LINK*"> |
2583 |
]]> |
2584 |
545 |
2585 |
<!ENTITY % head.extra "NEXTID? & META* & LINK*"> |
2586 |
|
2587 |
<!ENTITY % head.content "TITLE & ISINDEX? & BASE? & |
2588 |
(%head.extra)"> |
2589 |
550 |
2590 |
<!ELEMENT HEAD O O (%head.content)> |
2591 |
|
2592 |
<!-- <HEAD> Document head --> |
2593 |
|
2594 |
555 <!ELEMENT TITLE - - (#PCDATA)*> |
2595 |
<!ATTLIST TITLE |
2596 |
%SDAFORM; "Ti" > |
2597 |
|
2598 |
<!-- <TITLE> Title of document --> |
2599 |
560 |
2600 |
<!ELEMENT LINK - O EMPTY> |
2601 |
<!ATTLIST LINK |
2602 |
HREF %URI #REQUIRED |
2603 |
%linkExtraAttributes; |
2604 |
565 %SDAPREF; "Linked to : #AttVal (TITLE) (URN) (HREF)>" > |
2605 |
|
2606 |
<!-- <LINK> Link from this document --> |
2607 |
<!-- <LINK HREF="..."> Address of link destination --> |
2608 |
<!-- <LINK URN="..."> Lasting name of destination --> |
2609 |
570 <!-- <LINK REL=...> Relationship to destination --> |
2610 |
<!-- <LINK REV=...> Relationship of destination to this --> |
2611 |
<!-- <LINK TITLE="..."> Title of destination (advisory) --> |
2612 |
<!-- <LINK METHODS="..."> Operations allowed (advisory) --> |
2613 |
|
2614 |
575 <!ELEMENT ISINDEX - O EMPTY> |
2615 |
<!ATTLIST ISINDEX |
2616 |
%SDAPREF; |
2617 |
"<Para>[Document is indexed/searchable.]</Para>"> |
2618 |
|
2619 |
580 <!-- <ISINDEX> Document is a searchable index --> |
2620 |
|
2621 |
<!ELEMENT BASE - O EMPTY> |
2622 |
<!ATTLIST BASE |
2623 |
HREF %URI; #REQUIRED > |
2624 |
585 |
2625 |
<!-- <BASE> Base context document --> |
2626 |
<!-- <BASE HREF="..."> Address for this document --> |
2627 |
|
2628 |
<!ELEMENT NEXTID - O EMPTY> |
2629 |
590 <!ATTLIST NEXTID |
2630 |
N %linkName #REQUIRED > |
2631 |
|
2632 |
<!-- <NEXTID> Next ID to use for link name --> |
2633 |
<!-- <NEXTID N=...> Next ID to use for link name --> |
2634 |
595 |
2635 |
<!ELEMENT META - O EMPTY> |
2636 |
<!ATTLIST META |
2637 |
HTTP-EQUIV NAME #IMPLIED |
2638 |
NAME NAME #IMPLIED |
2639 |
600 CONTENT CDATA #REQUIRED > |
2640 |
|
2641 |
<!-- <META> Generic Metainformation --> |
2642 |
<!-- <META HTTP-EQUIV=...> HTTP response header name --> |
2643 |
<!-- <META NAME=...> Metainformation name --> |
2644 |
605 <!-- <META CONTENT="..."> Associated information --> |
2645 |
|
2646 |
<!--======= Document Structure =================--> |
2647 |
|
2648 |
<![ %HTML.Deprecated [ |
2649 |
610 <!ENTITY % html.content "HEAD, BODY, PLAINTEXT?"> |
2650 |
]]> |
2651 |
<!ENTITY % html.content "HEAD, BODY"> |
2652 |
|
2653 |
<!ELEMENT HTML O O (%html.content)> |
2654 |
615 <!ENTITY % version.attr "VERSION CDATA #FIXED '%HTML.Version;'"> |
2655 |
|
2656 |
<!ATTLIST HTML |
2657 |
%version.attr; |
2658 |
%SDAFORM; "Book" |
2659 |
620 > |
2660 |
|
2661 |
<!-- <HTML> HTML Document --> |
2662 |
|
2663 |
|
2664 |
11.2. SGML Declaration for HTML |
2665 |
|
2666 |
This is the SGML Declaration for HyperText Markup Language |
2667 |
(HTML) as used by the World Wide Web (WWW) application: |
2668 |
|
2669 |
<!SGML "ISO 8879:1986" |
2670 |
-- |
2671 |
SGML Declaration for HyperText Markup Language (HTML). |
2672 |
|
2673 |
5 -- |
2674 |
|
2675 |
CHARSET |
2676 |
BASESET "ISO 646:1983//CHARSET |
2677 |
International Reference Version |
2678 |
10 (IRV)//ESC 2/5 4/0" |
2679 |
DESCSET 0 9 UNUSED |
2680 |
9 2 9 |
2681 |
11 2 UNUSED |
2682 |
13 1 13 |
2683 |
15 14 18 UNUSED |
2684 |
32 95 32 |
2685 |
127 1 UNUSED |
2686 |
BASESET "ISO Registration Number 100//CHARSET |
2687 |
ECMA-94 Right Part of |
2688 |
20 Latin Alphabet Nr. 1//ESC 2/13 4/1" |
2689 |
|
2690 |
DESCSET 128 32 UNUSED |
2691 |
160 96 32 |
2692 |
|
2693 |
25 CAPACITY SGMLREF |
2694 |
TOTALCAP 150000 |
2695 |
GRPCAP 150000 |
2696 |
ENTCAP 150000 |
2697 |
|
2698 |
30 SCOPE DOCUMENT |
2699 |
SYNTAX |
2700 |
SHUNCHAR CONTROLS 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
2701 |
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 127 |
2702 |
BASESET "ISO 646:1983//CHARSET |
2703 |
35 International Reference Version |
2704 |
(IRV)//ESC 2/5 4/0" |
2705 |
DESCSET 0 128 0 |
2706 |
FUNCTION |
2707 |
RE 13 |
2708 |
40 RS 10 |
2709 |
SPACE 32 |
2710 |
TAB SEPCHAR 9 |
2711 |
|
2712 |
|
2713 |
45 NAMING LCNMSTRT "" |
2714 |
UCNMSTRT "" |
2715 |
LCNMCHAR ".-" |
2716 |
UCNMCHAR ".-" |
2717 |
NAMECASE GENERAL YES |
2718 |
50 ENTITY NO |
2719 |
DELIM GENERAL SGMLREF |
2720 |
SHORTREF SGMLREF |
2721 |
NAMES SGMLREF |
2722 |
QUANTITY SGMLREF |
2723 |
55 ATTSPLEN 2100 |
2724 |
LITLEN 1024 |
2725 |
NAMELEN 72 -- somewhat arbitrary; taken from |
2726 |
internet line length conventions -- |
2727 |
PILEN 1024 |
2728 |
60 TAGLEN 2100 |
2729 |
GRPGTCNT 150 |
2730 |
GRPCNT 64 |
2731 |
|
2732 |
FEATURES |
2733 |
65 MINIMIZE |
2734 |
DATATAG NO |
2735 |
OMITTAG YES |
2736 |
RANK NO |
2737 |
SHORTTAG YES |
2738 |
70 LINK |
2739 |
SIMPLE NO |
2740 |
IMPLICIT NO |
2741 |
EXPLICIT NO |
2742 |
OTHER |
2743 |
75 CONCUR NO |
2744 |
SUBDOC NO |
2745 |
FORMAL YES |
2746 |
APPINFO "SDA" -- conforming SGML Document Access application |
2747 |
-- |
2748 |
80 > |
2749 |
<!-- |
2750 |
$Id: html.decl,v 1.15 1995/05/06 01:44:47 connolly Exp $ |
2751 |
|
2752 |
Author: Daniel W. Connolly <connolly@hal.com> |
2753 |
85 |
2754 |
See also: http://www.hal.com/%7Econnolly/html-spec |
2755 |
http://info.cern.ch/hypertext/WWW/MarkUp/MarkUp.html |
2756 |
--> |
2757 |
|
2758 |
|
2759 |
11.3. Sample SGML Open Entity Catalog for HTML |
2760 |
|
2761 |
The SGML standard describes an ``entity manager'' as the |
2762 |
portion or component of an SGML system that maps SGML |
2763 |
entities into the actual storage model (e.g., the file |
2764 |
system). The standard itself does not define a particular |
2765 |
mapping methodology or notation. |
2766 |
|
2767 |
To assist the interoperability among various SGML tools and |
2768 |
systems, the SGML Open consortium has passed a technical |
2769 |
resolution that defines a format for an application- |
2770 |
independent entity catalog that maps external identifiers |
2771 |
and/or entity names to file names. |
2772 |
|
2773 |
Each entry in the catalog associates a storage object |
2774 |
identifier (such as a file name) with information about the |
2775 |
external entity that appears in the SGML document. In |
2776 |
addition to entries that associate public identifiers, a |
2777 |
catalog entry can associate an entity name with a storage |
2778 |
object indentifier. For example, the following are possible |
2779 |
catalog entries: |
2780 |
|
2781 |
-- catalog: SGML Open style entity catalog for HTML -- |
2782 |
-- $Id: catalog,v 1.2 1994/11/30 23:45:18 connolly Exp $ -- |
2783 |
|
2784 |
-- Ways to refer to Level 2: most general to most specific -- |
2785 |
5 PUBLIC "-//IETF//DTD HTML//EN" html.dtd |
2786 |
PUBLIC "-//IETF//DTD HTML 2.0//EN" html.dtd |
2787 |
PUBLIC "-//IETF//DTD HTML Level 2//EN" html.dtd |
2788 |
PUBLIC "-//IETF//DTD HTML 2.0 Level 2//EN" html.dtd |
2789 |
|
2790 |
10 -- Ways to refer to Level 1: most general to most specific -- |
2791 |
PUBLIC "-//IETF//DTD HTML Level 1//EN" html-1.dtd |
2792 |
PUBLIC "-//IETF//DTD HTML 2.0 Level 1//EN" html-1.dtd |
2793 |
|
2794 |
-- Ways to refer to Level 0: most general to most specific -- |
2795 |
15 PUBLIC "-//IETF//DTD HTML Level 0//EN" html-0.dtd |
2796 |
PUBLIC "-//IETF//DTD HTML 2.0 Level 0//EN" html-0.dtd |
2797 |
|
2798 |
|
2799 |
-- Ways to refer to Strict Level 2: most general to most specific \ |
2800 |
& -- |
2801 |
20 PUBLIC "-//IETF//DTD HTML Strict//EN" html-s.dtd |
2802 |
PUBLIC "-//IETF//DTD HTML 2.0 Strict//EN" html-s.dtd |
2803 |
PUBLIC "-//IETF//DTD HTML Strict Level 2//EN" html-s.dtd |
2804 |
PUBLIC "-//IETF//DTD HTML 2.0 Strict Level 2//EN" html-s.dtd |
2805 |
|
2806 |
25 -- Ways to refer to Strict Level 1: most general to most specific \ |
2807 |
& -- |
2808 |
PUBLIC "-//IETF//DTD HTML Strict Level 1//EN" html-1s.dtd |
2809 |
PUBLIC "-//IETF//DTD HTML 2.0 Strict Level 1//EN" html-1s.dtd |
2810 |
|
2811 |
-- Ways to refer to Strict Level 0: most general to most specific \ |
2812 |
& -- |
2813 |
30 PUBLIC "-//IETF//DTD HTML Strict Level 0//EN" html-0s.dtd |
2814 |
PUBLIC "-//IETF//DTD HTML 2.0 Strict Level 0//EN" html-0s.dtd |
2815 |
|
2816 |
-- ISO latin 1 entity set for HTML -- |
2817 |
PUBLIC "ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML" ISOlat1.sg\ |
2818 |
& ml |
2819 |
|
2820 |
|
2821 |
11.4. Character Entity Sets |
2822 |
|
2823 |
The HTML DTD defines the following entities. They represent |
2824 |
particular graphic characters which have special meanings in |
2825 |
places in the markup, or may not be part of the character |
2826 |
set available to the writer. |
2827 |
|
2828 |
|
2829 |
11.4.1. Numeric and Special Graphic Entity Set |
2830 |
|
2831 |
The following table lists each of the characters included |
2832 |
from the Numeric and Special Graphic entity set, along with |
2833 |
its name, syntax for use, and description. This list is |
2834 |
derived from `ISO Standard 8879:1986//ENTITIES Numeric and |
2835 |
Special Graphic//EN'. However, HTML does not include for the |
2836 |
entire entity set -- only the entities listed below are |
2837 |
included. |
2838 |
|
2839 |
GLYPH NAME SYNTAX DESCRIPTION |
2840 |
< lt < Less than sign |
2841 |
> gt > Greater than sign |
2842 |
& amp & Ampersand |
2843 |
" quot " Double quote sign |
2844 |
|
2845 |
|
2846 |
11.4.2. ISO Latin 1 Character Entity Set |
2847 |
|
2848 |
The following public text lists each of the characters |
2849 |
specified in the Added Latin 1 entity set, along with its |
2850 |
name, syntax for use, and description. This list is derived |
2851 |
from ISO Standard 8879:1986//ENTITIES Added Latin 1//EN. |
2852 |
HTML includes the entire entity set. |
2853 |
|
2854 |
<!-- (C) International Organization for Standardization 1986 |
2855 |
Permission to copy in any form is granted for use with |
2856 |
conforming SGML systems and applications as defined in |
2857 |
ISO 8879, provided this notice is included in all copies. |
2858 |
5 --> |
2859 |
<!-- Character entity set. Typical invocation: |
2860 |
<!ENTITY % ISOlat1 PUBLIC |
2861 |
"ISO 8879-1986//ENTITIES Added Latin 1//EN//HTML"> |
2862 |
%ISOlat1; |
2863 |
10 --> |
2864 |
<!-- Modified for use in HTML |
2865 |
$Id: ISOlat1.sgml,v 1.2 1994/11/30 23:45:12 connolly Exp $ --> |
2866 |
<!ENTITY AElig CDATA "Æ" -- capital AE diphthong (ligature) --> |
2867 |
<!ENTITY Aacute CDATA "Á" -- capital A, acute accent --> |
2868 |
15 <!ENTITY Acirc CDATA "Â" -- capital A, circumflex accent --> |
2869 |
<!ENTITY Agrave CDATA "À" -- capital A, grave accent --> |
2870 |
<!ENTITY Aring CDATA "Å" -- capital A, ring --> |
2871 |
<!ENTITY Atilde CDATA "Ã" -- capital A, tilde --> |
2872 |
<!ENTITY Auml CDATA "Ä" -- capital A, dieresis or umlaut mark --> |
2873 |
20 <!ENTITY Ccedil CDATA "Ç" -- capital C, cedilla --> |
2874 |
<!ENTITY ETH CDATA "Ð" -- capital Eth, Icelandic --> |
2875 |
<!ENTITY Eacute CDATA "É" -- capital E, acute accent --> |
2876 |
<!ENTITY Ecirc CDATA "Ê" -- capital E, circumflex accent --> |
2877 |
<!ENTITY Egrave CDATA "È" -- capital E, grave accent --> |
2878 |
25 <!ENTITY Euml CDATA "Ë" -- capital E, dieresis or umlaut mark --> |
2879 |
<!ENTITY Iacute CDATA "Í" -- capital I, acute accent --> |
2880 |
<!ENTITY Icirc CDATA "Î" -- capital I, circumflex accent --> |
2881 |
<!ENTITY Igrave CDATA "Ì" -- capital I, grave accent --> |
2882 |
<!ENTITY Iuml CDATA "Ï" -- capital I, dieresis or umlaut mark --> |
2883 |
30 <!ENTITY Ntilde CDATA "Ñ" -- capital N, tilde --> |
2884 |
<!ENTITY Oacute CDATA "Ó" -- capital O, acute accent --> |
2885 |
<!ENTITY Ocirc CDATA "Ô" -- capital O, circumflex accent --> |
2886 |
<!ENTITY Ograve CDATA "Ò" -- capital O, grave accent --> |
2887 |
<!ENTITY Oslash CDATA "Ø" -- capital O, slash --> |
2888 |
35 <!ENTITY Otilde CDATA "Õ" -- capital O, tilde --> |
2889 |
<!ENTITY Ouml CDATA "Ö" -- capital O, dieresis or umlaut mark --> |
2890 |
<!ENTITY THORN CDATA "Þ" -- capital THORN, Icelandic --> |
2891 |
<!ENTITY Uacute CDATA "Ú" -- capital U, acute accent --> |
2892 |
<!ENTITY Ucirc CDATA "Û" -- capital U, circumflex accent --> |
2893 |
40 <!ENTITY Ugrave CDATA "Ù" -- capital U, grave accent --> |
2894 |
<!ENTITY Uuml CDATA "Ü" -- capital U, dieresis or umlaut mark --> |
2895 |
<!ENTITY Yacute CDATA "Ý" -- capital Y, acute accent --> |
2896 |
<!ENTITY aacute CDATA "á" -- small a, acute accent --> |
2897 |
<!ENTITY acirc CDATA "â" -- small a, circumflex accent --> |
2898 |
45 <!ENTITY aelig CDATA "æ" -- small ae diphthong (ligature) --> |
2899 |
<!ENTITY agrave CDATA "à" -- small a, grave accent --> |
2900 |
<!ENTITY aring CDATA "å" -- small a, ring --> |
2901 |
<!ENTITY atilde CDATA "ã" -- small a, tilde --> |
2902 |
<!ENTITY auml CDATA "ä" -- small a, dieresis or umlaut mark --> |
2903 |
50 <!ENTITY ccedil CDATA "ç" -- small c, cedilla --> |
2904 |
<!ENTITY eacute CDATA "é" -- small e, acute accent --> |
2905 |
<!ENTITY ecirc CDATA "ê" -- small e, circumflex accent --> |
2906 |
<!ENTITY egrave CDATA "è" -- small e, grave accent --> |
2907 |
<!ENTITY eth CDATA "ð" -- small eth, Icelandic --> |
2908 |
55 <!ENTITY euml CDATA "ë" -- small e, dieresis or umlaut mark --> |
2909 |
<!ENTITY iacute CDATA "í" -- small i, acute accent --> |
2910 |
<!ENTITY icirc CDATA "î" -- small i, circumflex accent --> |
2911 |
<!ENTITY igrave CDATA "ì" -- small i, grave accent --> |
2912 |
<!ENTITY iuml CDATA "ï" -- small i, dieresis or umlaut mark --> |
2913 |
60 <!ENTITY ntilde CDATA "ñ" -- small n, tilde --> |
2914 |
<!ENTITY oacute CDATA "ó" -- small o, acute accent --> |
2915 |
<!ENTITY ocirc CDATA "ô" -- small o, circumflex accent --> |
2916 |
<!ENTITY ograve CDATA "ò" -- small o, grave accent --> |
2917 |
<!ENTITY oslash CDATA "ø" -- small o, slash --> |
2918 |
65 <!ENTITY otilde CDATA "õ" -- small o, tilde --> |
2919 |
<!ENTITY ouml CDATA "ö" -- small o, dieresis or umlaut mark --> |
2920 |
<!ENTITY szlig CDATA "ß" -- small sharp s, German (sz ligature) --> |
2921 |
<!ENTITY thorn CDATA "þ" -- small thorn, Icelandic --> |
2922 |
<!ENTITY uacute CDATA "ú" -- small u, acute accent --> |
2923 |
70 <!ENTITY ucirc CDATA "û" -- small u, circumflex accent --> |
2924 |
<!ENTITY ugrave CDATA "ù" -- small u, grave accent --> |
2925 |
<!ENTITY uuml CDATA "ü" -- small u, dieresis or umlaut mark --> |
2926 |
<!ENTITY yacute CDATA "ý" -- small y, acute accent --> |
2927 |
<!ENTITY yuml CDATA "ÿ" -- small y, dieresis or umlaut mark --> |
2928 |
|
2929 |
|
2930 |
12. Glossary |
2931 |
|
2932 |
character |
2933 |
An atom of information, for example a letter or a |
2934 |
digit. Graphic characters have associated glyphs, |
2935 |
where as control characters have associated |
2936 |
processing semantics. |
2937 |
|
2938 |
character |
2939 |
encoding scheme |
2940 |
A function whose domain is the set of sequences of |
2941 |
octets, and whose range is the set of sequences of |
2942 |
characters from a character repertoire; that is, a |
2943 |
sequence of octets and a character encoding scheme |
2944 |
determines a sequence of characters. |
2945 |
|
2946 |
character |
2947 |
repertoire |
2948 |
A finite set of characters; e.g. the range of a |
2949 |
coded character set. |
2950 |
|
2951 |
code position |
2952 |
An integer. A coded character set and a code |
2953 |
position from its domain determine a character. |
2954 |
|
2955 |
coded character |
2956 |
set |
2957 |
A function whose domain is a subset of the |
2958 |
integers and whose range is a character |
2959 |
repertoire. That is, for some set of integers |
2960 |
(usually of the form {0, 1, 2, ..., N} ), a coded |
2961 |
character set and an integer in that set determine |
2962 |
a character. Conversely, a character and a coded |
2963 |
character set determine the character's code |
2964 |
position (or, in rare cases, a few code |
2965 |
positions). |
2966 |
|
2967 |
conforming HTML |
2968 |
user agent |
2969 |
A user agent that conforms to this specification |
2970 |
in its processing of the Internet Media Type |
2971 |
`text/html; version=2.0'. |
2972 |
|
2973 |
data character |
2974 |
Characters other than markup, which make up the |
2975 |
content of elements. |
2976 |
|
2977 |
document |
2978 |
character set |
2979 |
a coded character set whose range includes all |
2980 |
characters used in a document. Every SGML document |
2981 |
has exactly one document character set. Numeric |
2982 |
character references are resolved via the document |
2983 |
character set. |
2984 |
|
2985 |
DTD |
2986 |
document type definition. Rules that apply SGML to |
2987 |
the markup of documents of a particular type, |
2988 |
including a set of element and entity |
2989 |
declarations. [SGML] |
2990 |
|
2991 |
element |
2992 |
A component of the hierarchical structure defined |
2993 |
by a document type definition; it is identified in |
2994 |
a document instance by descriptive markup, sually |
2995 |
a start-tag and end-tag. [SGML] |
2996 |
|
2997 |
end-tag |
2998 |
Descriptive markup that identifies the end of an |
2999 |
element. [SGML] |
3000 |
|
3001 |
entity |
3002 |
data with an associated notation or |
3003 |
interpretation; for example, a sequence of octets |
3004 |
associated with an Internet Media Type.[SGML] |
3005 |
|
3006 |
HTML document |
3007 |
An SGML document conforming to this document type |
3008 |
definition. |
3009 |
|
3010 |
markup |
3011 |
Syntactically delimited characters added to the |
3012 |
data of a document to represent its structure. |
3013 |
There are four different kinds of markup: |
3014 |
descriptive markup (tags), references, markup |
3015 |
declarations, and processing instructions.[SGML] |
3016 |
|
3017 |
may |
3018 |
A document or user interface is conforming whether |
3019 |
this statement applies or not. |
3020 |
|
3021 |
message entity |
3022 |
a head and body. The head is a collection of |
3023 |
name/value fields, and the body is a sequence of |
3024 |
octets. The head defines the content type and |
3025 |
content transfer encoding of the body. [MIME] |
3026 |
|
3027 |
must |
3028 |
Documents or user agents in conflict with this |
3029 |
statement are not conforming. |
3030 |
|
3031 |
SGML document |
3032 |
A sequence of characters organized physically as a |
3033 |
set of entities and logically into a hierarchy of |
3034 |
elements. An SGML document consists of data |
3035 |
characters and markup; the markup describes the |
3036 |
structure of the information and an instance of |
3037 |
that structure.[SGML] |
3038 |
|
3039 |
shall |
3040 |
If a document or user agent conflicts with this |
3041 |
statement, it does not conform to this |
3042 |
specification. |
3043 |
|
3044 |
should |
3045 |
If a document or user agent conflicts with this |
3046 |
statement, undesirable results may occur in |
3047 |
practice even though it conforms to this |
3048 |
specification. |
3049 |
|
3050 |
start-tag |
3051 |
Descriptive markup that identifies the start of an |
3052 |
element and specifies its generic identifier and |
3053 |
attributes. [SGML] |
3054 |
|
3055 |
|
3056 |
syntax-reference |
3057 |
character set |
3058 |
A coded character set whose range includes all |
3059 |
characters used for markup; e.g. name characters |
3060 |
and delimiter characters. |
3061 |
|
3062 |
tag |
3063 |
Markup that delimits an element. A tag includes a |
3064 |
name which refers to an element declaration in the |
3065 |
DTD, and may include attributes.[SGML] |
3066 |
|
3067 |
text entity |
3068 |
A finite sequence of characters. A text entity |
3069 |
typically takes the form of a sequence of octets |
3070 |
with some associated character encoding scheme, |
3071 |
transmitted over the network or stored in a |
3072 |
file.[SGML] |
3073 |
|
3074 |
typical |
3075 |
Typical processing is described for many elements. |
3076 |
This is not a mandatory part of the specification |
3077 |
but is given as guidance for designers and to help |
3078 |
explain the uses for which the elements were |
3079 |
intended. |
3080 |
|
3081 |
URI |
3082 |
A Universal Resource Identifier is a formatted |
3083 |
string that serves as an identifier for a |
3084 |
resource, typcally on the Internet. URIs are used |
3085 |
in HTML to identify the destination of hypertext |
3086 |
links, the source of in-line images, and the |
3087 |
object of form actions. URIs in common use include |
3088 |
Uniform Resource Locators (URLs)[URL] and Relative |
3089 |
URLs[RELURL]. |
3090 |
|
3091 |
user agent |
3092 |
A component of a distributed system that presents |
3093 |
an interface and processes requests on behalf of a |
3094 |
user; for example, a www browser or a mail user |
3095 |
agent. |
3096 |
|
3097 |
WWW |
3098 |
The World-Wide Web is a hypertext-based, |
3099 |
distributed information system created by |
3100 |
researchers at CERN in Switzerland. Users may |
3101 |
create, edit or browse hypertext documents. |
3102 |
`http://www.w3.org/' |
3103 |
|
3104 |
|
3105 |
13. Bibliography |
3106 |
|
3107 |
[URI] |
3108 |
T. Berners-Lee. ``Universal Resource Identifiers |
3109 |
in WWW: A Unifying Syntax for the Expression of |
3110 |
Names and Addresses of Objects on the Network as |
3111 |
used in the World- Wide Web.'' RFC 1630, CERN, |
3112 |
June 1994. |
3113 |
|
3114 |
[URL] |
3115 |
T. Berners-Lee, L. Masinter, and M. McCahill. |
3116 |
``Uniform Resource Locators (URL).'' RFC 1738, |
3117 |
CERN, Xerox PARC, University of Minnesota, October |
3118 |
1994. |
3119 |
|
3120 |
[HTTP] |
3121 |
T. Berners-Lee, R. T. Fielding, and H. Frystyk |
3122 |
Nielsen. ``Hypertext Transfer Protocol - |
3123 |
HTTP/1.0.'' Work in Progress |
3124 |
(draft-ietf-http-v10-spec-00.ps), MIT, UC Irvine, |
3125 |
CERN, March 1995. |
3126 |
|
3127 |
[MIME] |
3128 |
N. Borenstein and N. Freed. ``MIME (Multipurpose |
3129 |
Internet Mail Extensions) Part One: Mechanisms for |
3130 |
Specifying and Describing the Format of Internet |
3131 |
Message Bodies.'' RFC 1521, Bellcore, Innosoft, |
3132 |
September 1993. |
3133 |
|
3134 |
[RELURL] |
3135 |
R. T. Fielding. ``Relative Uniform Resource |
3136 |
Locators.'' Work in Progress (draft-ietf-uri- |
3137 |
relative-url-06.txt), UC Irvine, March 1995. |
3138 |
|
3139 |
[GOLD90] |
3140 |
C. F. Goldfarb. ``The SGML Handbook.'' Y. |
3141 |
Rubinsky, Ed., Oxford University Press, 1990. |
3142 |
|
3143 |
[IMEDIA] |
3144 |
J. Postel. ``Media Type Registration Procedure.'' |
3145 |
RFC 1590, USC/ISI, March 1994. |
3146 |
|
3147 |
[IANA] |
3148 |
J. Reynolds and J. Postel. ``Assigned Numbers.'' |
3149 |
STD 2, RFC 1700, USC/ISI, October 1994. |
3150 |
|
3151 |
[SQ91] |
3152 |
SoftQuad. ``The SGML Primer.'' 3rd ed., SoftQuad |
3153 |
Inc., 1991. |
3154 |
|
3155 |
[US-ASCII] |
3156 |
US-ASCII. Coded Character Set - 7-Bit American |
3157 |
Standard Code for Information Interchange. |
3158 |
Standard ANSI X3.4-1986, ANSI, 1986. |
3159 |
|
3160 |
[ISO-8859-1] |
3161 |
ISO 8859. International Standard -- Information |
3162 |
Processing -- 8-bit Single-Byte Coded Graphic |
3163 |
Character Sets -- Part 1: Latin Alphabet No. 1, |
3164 |
ISO 8859-1:1987. Part 2: Latin alphabet No. 2, ISO |
3165 |
8859-2, 1987. Part 3: Latin alphabet No. 3, ISO |
3166 |
8859-3, 1988. Part 4: Latin alphabet No. 4, ISO |
3167 |
8859-4, 1988. Part 5: Latin/Cyrillic alphabet, ISO |
3168 |
8859-5, 1988. Part 6: Latin/Arabic alphabet, ISO |
3169 |
8859-6, 1987. Part 7: Latin/Greek alphabet, ISO |
3170 |
8859-7, 1987. Part 8: Latin/Hebrew alphabet, ISO |
3171 |
8859-8, 1988. Part 9: Latin alphabet No. 5, ISO |
3172 |
8859-9, 1990. |
3173 |
|
3174 |
[SGML] |
3175 |
ISO 8879. Information Processing - Text and Office |
3176 |
Systems - Standard Generalized Markup Language |
3177 |
(SGML), 1986. |
3178 |
|
3179 |
|
3180 |
14. Appendices |
3181 |
|
3182 |
These appendices are provided for informational reasons only |
3183 |
- they do not form a part of the HTML specification. |
3184 |
|
3185 |
|
3186 |
14.1. The ISO-8859-1 Coded Character Set |
3187 |
|
3188 |
This list, sorted numerically, is derived from ISO-8859-1 |
3189 |
8-bit single-byte coded graphic character set: |
3190 |
|
3191 |
REFERENCE DESCRIPTION |
3192 |
� -  Unused |
3193 |
	 Horizontal tab |
3194 |
Line feed |
3195 |
 -  Unused |
3196 |
  Space |
3197 |
! Exclamation mark |
3198 |
" Quotation mark |
3199 |
# Number sign |
3200 |
$ Dollar sign |
3201 |
% Percent sign |
3202 |
& Ampersand |
3203 |
' Apostrophe |
3204 |
( Left parenthesis |
3205 |
) Right parenthesis |
3206 |
* Asterisk |
3207 |
+ Plus sign |
3208 |
, Comma |
3209 |
- Hyphen |
3210 |
. Period (fullstop) |
3211 |
/ Solidus (slash) |
3212 |
0 - 9 Digits 0-9 |
3213 |
: Colon |
3214 |
; Semi-colon |
3215 |
< Less than |
3216 |
= Equals sign |
3217 |
> Greater than |
3218 |
? Question mark |
3219 |
@ Commercial at |
3220 |
A - Z Letters A-Z |
3221 |
[ Left square bracket |
3222 |
\ Reverse solidus (backslash) |
3223 |
] Right square bracket |
3224 |
^ Caret |
3225 |
_ Horizontal bar (underscore) |
3226 |
` Acute accent |
3227 |
a - z Letters a-z |
3228 |
{ Left curly brace |
3229 |
| Vertical bar |
3230 |
} Right curly brace |
3231 |
~ Tilde |
3232 |
 -   Unused |
3233 |
¡ Inverted exclamation |
3234 |
¢ Cent sign |
3235 |
£ Pound sterling |
3236 |
¤ General currency sign |
3237 |
¥ Yen sign |
3238 |
¦ Broken vertical bar |
3239 |
§ Section sign |
3240 |
¨ Umlaut (dieresis) |
3241 |
© Copyright |
3242 |
ª Feminine ordinal |
3243 |
« Left angle quote, guillemotleft |
3244 |
¬ Not sign |
3245 |
­ Soft hyphen |
3246 |
® Registered trademark |
3247 |
¯ Macron accent |
3248 |
° Degree sign |
3249 |
± Plus or minus |
3250 |
² Superscript two |
3251 |
³ Superscript three |
3252 |
´ Acute accent |
3253 |
µ Micro sign |
3254 |
¶ Paragraph sign |
3255 |
· Middle dot |
3256 |
¸ Cedilla |
3257 |
¹ Superscript one |
3258 |
º Masculine ordinal |
3259 |
» Right angle quote, guillemotright |
3260 |
¼ Fraction one-fourth |
3261 |
½ Fraction one-half |
3262 |
¾ Fraction three-fourths |
3263 |
¿ Inverted question mark |
3264 |
À Capital A, grave accent |
3265 |
Á Capital A, acute accent |
3266 |
 Capital A, circumflex accent |
3267 |
à Capital A, tilde |
3268 |
Ä Capital A, dieresis or umlaut mark |
3269 |
Å Capital A, ring |
3270 |
Æ Capital AE dipthong (ligature) |
3271 |
Ç Capital C, cedilla |
3272 |
È Capital E, grave accent |
3273 |
É Capital E, acute accent |
3274 |
Ê Capital E, circumflex accent |
3275 |
Ë Capital E, dieresis or umlaut mark |
3276 |
Ì Capital I, grave accent |
3277 |
Í Capital I, acute accent |
3278 |
Î Capital I, circumflex accent |
3279 |
Ï Capital I, dieresis or umlaut mark |
3280 |
Ð Capital Eth, Icelandic |
3281 |
Ñ Capital N, tilde |
3282 |
Ò Capital O, grave accent |
3283 |
Ó Capital O, acute accent |
3284 |
Ô Capital O, circumflex accent |
3285 |
Õ Capital O, tilde |
3286 |
Ö Capital O, dieresis or umlaut mark |
3287 |
× Multiply sign |
3288 |
Ø Capital O, slash |
3289 |
Ù Capital U, grave accent |
3290 |
Ú Capital U, acute accent |
3291 |
Û Capital U, circumflex accent |
3292 |
Ü Capital U, dieresis or umlaut mark |
3293 |
Ý Capital Y, acute accent |
3294 |
Þ Capital THORN, Icelandic |
3295 |
ß Small sharp s, German (sz ligature) |
3296 |
à Small a, grave accent |
3297 |
á Small a, acute accent |
3298 |
â Small a, circumflex accent |
3299 |
ã Small a, tilde |
3300 |
ä Small a, dieresis or umlaut mark |
3301 |
å Small a, ring |
3302 |
æ Small ae dipthong (ligature) |
3303 |
ç Small c, cedilla |
3304 |
è Small e, grave accent |
3305 |
é Small e, acute accent |
3306 |
ê Small e, circumflex accent |
3307 |
ë Small e, dieresis or umlaut mark |
3308 |
ì Small i, grave accent |
3309 |
í Small i, acute accent |
3310 |
î Small i, circumflex accent |
3311 |
ï Small i, dieresis or umlaut mark |
3312 |
ð Small eth, Icelandic |
3313 |
ñ Small n, tilde |
3314 |
ò Small o, grave accent |
3315 |
ó Small o, acute accent |
3316 |
ô Small o, circumflex accent |
3317 |
õ Small o, tilde |
3318 |
ö Small o, dieresis or umlaut mark |
3319 |
÷ Division sign |
3320 |
ø Small o, slash |
3321 |
ù Small u, grave accent |
3322 |
ú Small u, acute accent |
3323 |
û Small u, circumflex accent |
3324 |
ü Small u, dieresis or umlaut mark |
3325 |
ý Small y, acute accent |
3326 |
þ Small thorn, Icelandic |
3327 |
ÿ Small y, dieresis or umlaut mark |
3328 |
|
3329 |
|
3330 |
14.2. Obsolete Features |
3331 |
|
3332 |
This section describes elements that are no longer part of |
3333 |
HTML. Client implementors should implement these obsolete |
3334 |
elements for compatibility with previous versions of the |
3335 |
HTML specification. |
3336 |
|
3337 |
|
3338 |
14.2.1. Comment Element |
3339 |
|
3340 |
The Comment element is used to delimit unneeded text and |
3341 |
comments. The Comment element has been introduced in some |
3342 |
HTML applications but should be replaced by the SGML comment |
3343 |
feature in new HTML interpreters (see Section 2.2.5). |
3344 |
|
3345 |
|
3346 |
14.2.2. Highlighted Phrase Element |
3347 |
|
3348 |
<HP> |
3349 |
|
3350 |
The Highlighted Phrase element should be ignored if not |
3351 |
implemented. This element has been replaced by more |
3352 |
meaningful elements (see Section 8). |
3353 |
|
3354 |
Example of use: |
3355 |
|
3356 |
<HP1>first highlighted phrase</HP1>non- |
3357 |
highlighted text<HP2>second highlighted phrase</HP2> etc. |
3358 |
|
3359 |
|
3360 |
14.2.3. Plain Text Element |
3361 |
|
3362 |
<PLAINTEXT> |
3363 |
|
3364 |
The Plain Text element is used to terminates the HTML entity |
3365 |
and to indicate that what follows is not SGML which does not |
3366 |
require parsing. Instead, an old HTTP convention specified |
3367 |
that what followed was an ASCII (MIME ``text/plain'') body. |
3368 |
Its presence is an optimization. There is no closing tag. |
3369 |
|
3370 |
Example of use: |
3371 |
|
3372 |
<PLAINTEXT> |
3373 |
0001 This is line one of a long listing |
3374 |
0002 file from <ANY@HOST.INC.COM> which is sent |
3375 |
|
3376 |
|
3377 |
14.2.4. Example and Listing Elements |
3378 |
|
3379 |
<XMP> ... </XMP> and <LISTING> ... </LISTING> |
3380 |
|
3381 |
The Example and Listing elements have been replaced by the |
3382 |
Preformatted Text element (Section 10.2). |
3383 |
|
3384 |
These styles allow text of fixed-width characters to be |
3385 |
embedded absolutely as is into the document. The syntax is: |
3386 |
|
3387 |
<LISTING> ... </LISTING> |
3388 |
|
3389 |
or |
3390 |
|
3391 |
<XMP> ... </XMP> |
3392 |
|
3393 |
The text between these tags is typically rendered in a |
3394 |
monospaced font so that any formatting done by character |
3395 |
spacing on successive lines will be maintained. |
3396 |
|
3397 |
Between the opening and closing tags: |
3398 |
|
3399 |
* The text may contain any ISO Latin-1 printable |
3400 |
characters, except for the end-tag opener. The Example |
3401 |
and Listing elements have historically used |
3402 |
specifications which do not conform to SGML. |
3403 |
Specifically, the text may contain ISO Latin printable |
3404 |
characters, including the tag opener, as long it they |
3405 |
does not contain the closing tag in full. |
3406 |
* SGML does not support this form. HTML interpreters |
3407 |
may vary on how they interpret other tags within |
3408 |
Example and Listing elements. |
3409 |
* Line boundaries within the text are rendered as a |
3410 |
move to the beginning of the next line, except for one |
3411 |
immediately following a start-tag or immediately |
3412 |
preceding an end-tag. |
3413 |
* The horizontal tab character must be interpreted as |
3414 |
the smallest positive nonzero number of spaces which |
3415 |
will leave the number of characters so far on the line |
3416 |
as a multiple of 8. Its use is not recommended. |
3417 |
|
3418 |
The Listing element is rendered so that at least 132 |
3419 |
characters fit on a line. The Example element is rendered to |
3420 |
that at least 80 characters fit on a line but is otherwise |
3421 |
identical to the Listing element. |
3422 |
|
3423 |
|
3424 |
14.3. Proposed Features |
3425 |
|
3426 |
This section describes proposed HTML elements and entities |
3427 |
that are not currently supported under HTML Levels 0, 1, or |
3428 |
2@@, but may be supported in the future. |
3429 |
|
3430 |
|
3431 |
14.3.1. Additional Character Entities |
3432 |
|
3433 |
To indicate special characters, HTML uses entity or numeric |
3434 |
representations. Additional character presentations are |
3435 |
proposed: |
3436 |
|
3437 |
CHARACTER REPRESENTATION |
3438 |
Non-breaking space |
3439 |
Soft-hyphen ­ |
3440 |
Registered ® |
3441 |
Copyright © |
3442 |
|
3443 |
|
3444 |
14.3.2. Defining Instance Element |
3445 |
|
3446 |
<DFN> ... </DFN> |
3447 |
|
3448 |
The Defining Instance element indicates the defining |
3449 |
instance of a term. The typical rendering is bold or bold |
3450 |
italic. This element is not widely supported. |
3451 |
|
3452 |
|
3453 |
14.3.3. Strike Element |
3454 |
|
3455 |
<STRIKE> ... </STRIKE> |
3456 |
|
3457 |
The Strike element is proposed to indicate strikethrough, a |
3458 |
font style in which a horizontal line appears through |
3459 |
characters. This element is not widely supported. |
3460 |
|
3461 |
|
3462 |
14.3.4. Underline Element |
3463 |
|
3464 |
<U> ... </U> |
3465 |
|
3466 |
The Underline element is proposed to indicate that the text |
3467 |
should be rendered as underlined. This proposed tag is not |
3468 |
supported by all HTML interpreters. |
3469 |
|
3470 |
Example of use: |
3471 |
|
3472 |
The text <U>shown here</U> is rendered in the |
3473 |
document as underlined. |
3474 |
|
3475 |
|
3476 |
15. Acknowledgments |
3477 |
|
3478 |
The HTML document type was designed by Tim Berners-Lee at |
3479 |
CERN as part of the 1990 World Wide Web project. In 1992, |
3480 |
Dan Connolly wrote the HTML Document Type Definition (DTD) |
3481 |
and a brief HTML specification. |
3482 |
|
3483 |
Since 1993, a wide variety of Internet participants have |
3484 |
contributed to the evolution of HTML, which has included the |
3485 |
addition of in-line images introduced by the NCSA Mosaic |
3486 |
software for WWW. Dave Raggett played an important role in |
3487 |
deriving the FORMS material from the HTML+ specification. |
3488 |
|
3489 |
Dan Connolly and Karen Olson Muldrow rewrote the HTML |
3490 |
Specification in 1994. The document was then edited by the |
3491 |
HTML working group as a whole, with updates being made by |
3492 |
Eric Schieler, Mike Knezovich, and Eric W. Sink at Spyglass, |
3493 |
Inc. Finally, Roy Fielding restructured the entire draft |
3494 |
into its current form. |
3495 |
|
3496 |
Special thanks to the many people who have contributed to |
3497 |
this specification: |
3498 |
|
3499 |
Terry Allen Marc Andreessen |
3500 |
|
3501 |
Tim Berners-Lee Paul Burchard |
3502 |
|
3503 |
James Clark Daniel W. Connolly |
3504 |
|
3505 |
Roy T. Fielding Peter Flynn |
3506 |
|
3507 |
Jay Glicksman Paul Grosso |
3508 |
|
3509 |
Eduardo Gutentag Bill Hefley |
3510 |
|
3511 |
Chung-Jen Ho Mike Knezovich |
3512 |
|
3513 |
Tom Magliery Murray Maloney |
3514 |
|
3515 |
Larry Masinter Karen Olson Muldrow |
3516 |
|
3517 |
Bill Perry Dave Raggett |
3518 |
|
3519 |
E. Corprew Reed Yuri Rubinsky |
3520 |
|
3521 |
Eric Schieler James L. Seidman |
3522 |
|
3523 |
Eric W. Sink Stuart Weibel |
3524 |
|
3525 |
Chris Wilson Francois Yergeau |
3526 |
|
3527 |
|
3528 |
15.1. Authors' Addresses |
3529 |
|
3530 |
Tim Berners-Lee |
3531 |
|
3532 |
Director, W3 Consortium |
3533 |
MIT Laboratory for Computer Science |
3534 |
545 Technology Square |
3535 |
Cambridge, MA 02139, U.S.A. |
3536 |
Tel: +1 (617) 253 9670 |
3537 |
Fax: +1 (617) 258 8682 |
3538 |
Email: timbl@w3.org |
3539 |
|
3540 |
Daniel W. |
3541 |
Connolly |
3542 |
|
3543 |
Research Technical Staff, W3 Consortium |
3544 |
MIT Laboratory for Computer Science |
3545 |
545 Technology Square |
3546 |
Cambridge, MA 02139, U.S.A. |
3547 |
Fax: +1 (617) 258 8682 |
3548 |
Email: connolly@w3.org |
3549 |
URI: http://www.w3.org/hypertext/WWW/People/Connolly/ |
3550 |
|