File: meta.html

package info (click to toggle)
perlsgml 1996Oct09-6
  • links: PTS
  • area: main
  • in suites: hamm
  • size: 2,452 kB
  • ctags: 792
  • sloc: perl: 4,639; makefile: 167
file content (121 lines) | stat: -rw-r--r-- 3,329 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
<HTML>
<HEAD>
<TITLE>HTML 2.0 DTD: META element</TITLE>
</HEAD>
<BODY>
<H1>META</H1>
<p>
The &lt;META&gt; element is an extensible container for use in identifying
specialized document meta-information.  Meta-information has two main
functions:
</p>
<ul>
<li>to provide a means to discover that the data set exists
and how it might be obtained or accessed; and</li>
<li>to document the content, quality, and features of a data
set, indicating its fitness for use.</li>
</ul>
<p>
Each &lt;META&gt; element specifies a name/value pair. If multiple META
elements are provided with the same name, their combined contents--
concatenated as a comma-separated list--is the value associated with
that name.
</p>
<dl>
<dt>NOTE</dt>
<dd>The &lt;META&gt; element should not be used where a
specific element, such as
<a href="title.html">&lt;TITLE&gt;</a>, would be more
appropriate. Rather than a &lt;META&gt; element with a URI as
the value of the CONTENT attribute, use a
<a href="link.html">&lt;LINK&gt;</a>
element.
</dd>
</dl>
<p>
HTTP servers may read the content of the document
<a href="head.html">&lt;HEAD&gt;</a> to generate
header fields corresponding to any elements defining a value for the
attribute HTTP-EQUIV.
</p>
<dl>
<dt>NOTE</dt>
<dd>
The method by which the server extracts document
meta-information is unspecified and not mandatory. The
&lt;META&gt; element only provides an extensible mechanism for
identifying and embedding document meta-information --
how it may be used is up to the individual server
implementation and the HTML user agent.
</dd>
</dl>
<p><strong>Examples</strong></p>
<p>
If the document contains:
</p>
<pre>
    &lt;META HTTP-EQUIV="Expires"
          CONTENT="Tue, 04 Dec 1993 21:29:02 GMT"&gt;
    &lt;meta http-equiv="Keywords" CONTENT="Fred"&gt;
    &lt;META HTTP-EQUIV="Reply-to"
          content="fielding@ics.uci.edu (Roy Fielding)"&gt;
    &lt;Meta Http-equiv="Keywords" CONTENT="Barney"&gt;
</pre>
<p>
then the server may include the following header fields:
</p>
<pre>
    Expires: Tue, 04 Dec 1993 21:29:02 GMT
    Keywords: Fred, Barney
    Reply-to: fielding@ics.uci.edu (Roy Fielding)
</pre>
<p>
as part of the HTTP response to a `GET' or `HEAD' request for
that document.
</p>
<p>
An HTTP server must not use the &lt;META&gt; element to form an HTTP
response header unless the HTTP-EQUIV attribute is present.
</p>
<p>
An HTTP server may disregard any &lt;META&gt; elements that specify
information controlled by the HTTP server, for example `Server',
`Date', and `Last-modified'.
</p>
<HR>
<H2>Content</H2>
<UL>
<LI>EMPTY</LI>
</UL>
<HR>
<P>
<A HREF="meta.attr.html"><STRONG>ATTRIBUTES</STRONG></A><BR>
<STRONG>Empty</STRONG> CONTENT DECLARATION
</P>
<DL>
<DT><STRONG>Tag Minimization</STRONG><DD>
Open Tag: <EM>REQUIRED</EM><BR>
Close Tag: <EM>OPTIONAL</EM><BR>
</DL>
<HR>
<H2>Parent Elements</H2>
<UL COMPACT>
<LI><A HREF="head.html"><STRONG>head</STRONG></A> -- Document head
</LI>
</UL>
<HR>
<P>
<A HREF="TOP-ELEM.html"><STRONG>Top Elements</STRONG></A>
<BR>
<A HREF="ALL-ELEM.html"><STRONG>All Elements</STRONG></A>
<BR>
<A HREF="ENTS.html"><STRONG>General Entities</STRONG></A><BR>
<A HREF="DTD-TREE.html#meta"><STRONG>Tree</STRONG></A>
</P>
<HR>
<ADDRESS>
<A HREF="DTD-HOME.html">HTML 2.0 DTD</A>
</ADDRESS>
</BODY>
</HTML>