Skip to content

Commit

Permalink
[e] (0) tweak the way that we describe <meta> to read better
Browse files Browse the repository at this point in the history 
git-svn-id: http://svn.whatwg.org/webapps@612 340c8d12-0b0e-0410-8428-c7bf67bfef74
  • Loading branch information
@Hixie
Hixie committed Feb 22, 2007
1 parent 359318a commit 00776f9
Show file tree
Hide file tree
Showing 2 changed files with 60 additions and 54 deletions.
60 changes: 30 additions & 30 deletions index
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7199,21 +7199,25 @@ class="main"> or <div class="content">. Why do we also need a body?
};</pre>
</dl>

<p>The <code><a href="#meta1">meta</a></code> element allows authors to
specify document metadata that cannot be expressed using the <code><a
<p>The <code><a href="#meta1">meta</a></code> element represents various
kinds of metadata that cannot be expressed using the <code><a
href="#title3">title</a></code>, <code><a href="#base0">base</a></code>,
<code><a href="#link0">link</a></code>, <code><a
href="#style0">style</a></code>, and <code><a
href="#script2">script</a></code> elements. The metadata is expressed in
terms of name/value pairs: the <dfn id=name
title=attr-meta-name><code>name</code></dfn> attribute on the <code><a
href="#meta1">meta</a></code> element gives the name, and the <dfn
id=content0 title=attr-meta-content><code>content</code></dfn> attribute
on the same element gives the value.

<p>If a <code><a href="#meta1">meta</a></code> element has no <code
title=attr-meta-name><a href="#name">name</a></code> attribute, it does
not set document metadata. If a <code><a href="#meta1">meta</a></code>
href="#script2">script</a></code> elements.

<p>The first kind of metadata expressible with <code><a
href="#meta1">meta</a></code> elements is document-level metadata. If a a
<code><a href="#meta1">meta</a></code> element has a <code
title=attr-meta-name><a href="#name">name</a></code> attribute, it sets
document metadata. Document metadata is expressed in terms of name/value
pairs, the <dfn id=name title=attr-meta-name><code>name</code></dfn>
attribute on the <code><a href="#meta1">meta</a></code> element giving the
name, and the <dfn id=content0
title=attr-meta-content><code>content</code></dfn> attribute on the same
element giving the value. The name specifies what aspect of metadata is
being set; valid names and the meaning of their values are described in
the following sections. If a <code><a href="#meta1">meta</a></code>
element has no <code title=attr-meta-content><a
href="#content0">content</a></code> attribute, then the value part of the
metadata name/value pair is the empty string.
Expand All @@ -7225,10 +7229,10 @@ class="main"> or <div class="content">. Why do we also need a body?
<p>The <code><a href="#meta1">meta</a></code> element also allows authors
to set pragma directives, using the <code title=attr-meta-http-equiv><a
href="#http-equiv">http-equiv</a></code> attribute, and to declare the
character encoding used (with the <code title=attr-meta-charset><a
href="#charset0">charset</a></code> attribute) when an HTML document is
serialised to string form (e.g. for transmission over the network or for
disk storage).
character encoding used when an HTML document is serialised to string form
(e.g. for transmission over the network or for disk storage), using the
<code title=attr-meta-charset><a href="#charset0">charset</a></code>
attribute.

<p>Exactly one of the <code title=attr-meta-name><a
href="#name">name</a></code>, <code title=attr-meta-http-equiv><a
Expand Down Expand Up @@ -7346,20 +7350,20 @@ class="main"> or <div class="content">. Why do we also need a body?
<h5 id=pragma><span class=secno>3.7.5.3. </span>Pragma directives</h5>

<p>The <dfn id=http-equiv
title=attr-meta-http-equiv><code>http-equiv</code></dfn> attribute is an
<a href="#enumerated">enumerated attribute</a>. The following table lists
the keywords defined for this attribute. The states given in the first
cell of the the rows with keywords give the states to which those keywords
map. Some of the keywords are non-conforming, as noted in the last column.
title=attr-meta-http-equiv><code>http-equiv</code></dfn> attribute, which
is used to set pragma directives, is an <a href="#enumerated">enumerated
attribute</a>. The following table lists the keywords defined for this
attribute. The states given in the first cell of the the rows with
keywords give the states to which those keywords
map.<!-- Some of the keywords are non-conforming, as noted in
the last column.-->

<table>
<thead>
<tr>
<th>State

<th>Keywords

<th>Notes
<th>Keywords <!-- <th>Notes-->

<tbody><!-- things that are neither conforming nor do anything are commented out
<tr>
Expand All @@ -7383,17 +7387,13 @@ class="main"> or <div class="content">. Why do we also need a body?
<tr>
<td><a href="#refresh" title=attr-meta-http-equiv-refresh>Refresh</a>

<td><code title="">refresh</code>

<td>
<td><code title="">refresh</code> <!-- <td>-->

<tr>
<td><a href="#default" title=attr-meta-http-equiv-default-style>Default
Style</a>

<td><code title="">default-style</code>

<td>
<td><code title="">default-style</code> <!-- <td>-->
</table>

<p>When a <code><a href="#meta1">meta</a></code> element is inserted into
Expand Down
54 changes: 30 additions & 24 deletions source
View file
Original file line number Diff line number Diff line change
Expand Up @@ -5932,32 +5932,36 @@ class="main"> or <div class="content">. Why do we also need a body?
</dd>
</dl>

<p>The <code>meta</code> element allows authors to specify document
<p>The <code>meta</code> element represents various kinds of
metadata that cannot be expressed using the <code>title</code>,
<code>base</code>, <code>link</code>, <code>style</code>, and
<code>script</code> elements. The metadata is expressed in terms of
name/value pairs: the <dfn
<code>script</code> elements.</p>

<p>The first kind of metadata expressible with <code>meta</code>
elements is document-level metadata. If a a <code>meta</code>
element has a <code title="attr-meta-name">name</code> attribute, it
sets document metadata. Document metadata is expressed in terms of
name/value pairs, the <dfn
title="attr-meta-name"><code>name</code></dfn> attribute on the
<code>meta</code> element gives the name, and the <dfn
<code>meta</code> element giving the name, and the <dfn
title="attr-meta-content"><code>content</code></dfn> attribute on
the same element gives the value.</p>

<p>If a <code>meta</code> element has no <code
title="attr-meta-name">name</code> attribute, it does not set
document metadata. If a <code>meta</code> element has no <code
title="attr-meta-content">content</code> attribute, then the value
part of the metadata name/value pair is the empty string.</p>
the same element giving the value. The name specifies what aspect of
metadata is being set; valid names and the meaning of their values
are described in the following sections. If a <code>meta</code>
element has no <code title="attr-meta-content">content</code>
attribute, then the value part of the metadata name/value pair is
the empty string.</p>

<p>The value must not be a URI. Links must be represented using the
<code>link</code> element, not the <code>meta</code> element.</p>

<p>The <code>meta</code> element also allows authors to set pragma
directives, using the <code
title="attr-meta-http-equiv">http-equiv</code> attribute, and to
declare the character encoding used (with the <code
title="attr-meta-charset">charset</code> attribute) when an HTML
document is serialised to string form (e.g. for transmission over
the network or for disk storage).</p>
declare the character encoding used when an HTML document is
serialised to string form (e.g. for transmission over the network or
for disk storage), using the <code
title="attr-meta-charset">charset</code> attribute.</p>

<p>Exactly one of the <code title="attr-meta-name">name</code>,
<code title="attr-meta-http-equiv">http-equiv</code>, and <code
Expand Down Expand Up @@ -6089,19 +6093,21 @@ class="main"> or <div class="content">. Why do we also need a body?

<h5>Pragma directives</h5>

<p>The <dfn title="attr-meta-http-equiv"><code>http-equiv</code></dfn>
attribute is an <span>enumerated attribute</span>. The following
table lists the keywords defined for this attribute. The states
given in the first cell of the the rows with keywords give the
states to which those keywords map. Some of the keywords are
non-conforming, as noted in the last column.</p>
<p>The <dfn
title="attr-meta-http-equiv"><code>http-equiv</code></dfn>
attribute, which is used to set pragma directives, is an
<span>enumerated attribute</span>. The following table lists the
keywords defined for this attribute. The states given in the first
cell of the the rows with keywords give the states to which those
keywords map.<!-- Some of the keywords are non-conforming, as noted in
the last column.--></p>

<table>
<thead>
<tr>
<th>State
<th>Keywords
<th>Notes
<!-- <th>Notes-->
<tbody>
<!-- things that are neither conforming nor do anything are commented out
<tr>
Expand All @@ -6124,11 +6130,11 @@ class="main"> or <div class="content">. Why do we also need a body?
<tr>
<td><span title="attr-meta-http-equiv-refresh">Refresh</span>
<td><code title="">refresh</code>
<td>
<!-- <td>-->
<tr>
<td><span title="attr-meta-http-equiv-default-style">Default Style</span>
<td><code title="">default-style</code>
<td>
<!-- <td>-->
</table>

<p>When a <code>meta</code> element is inserted into the document,
Expand Down

0 comments on commit 00776f9

Please sign in to comment.