A user account is required in order to edit this wiki, but we've had to disable public user registrations due to spam.

To request an account, ask an autoconfirmed user on IRC (such as one of these permanent autoconfirmed members).

Difference between revisions of "MetaExtensions"

From WHATWG Wiki
Jump to: navigation, search
m (Reverted edits by CosZxz (Talk); changed back to last version by Aleksandersen)
m (wiki markup)
Line 1: Line 1:
 
This page lists the allowed extension values for the name="" attribute of the <meta> element in HTML5. You may add your own values to this list, which makes them legal HTML5 metadata names. We ask that you try to avoid redundancy; if someone has already defined a name that does roughly what you want, please reuse it.
 
This page lists the allowed extension values for the name="" attribute of the <meta> element in HTML5. You may add your own values to this list, which makes them legal HTML5 metadata names. We ask that you try to avoid redundancy; if someone has already defined a name that does roughly what you want, please reuse it.
  
<table>
+
{| 
  <tr>
+
! Keyword
  <th>Keyword
+
! Brief description
  <th>Brief description
+
! Link to more details
  <th>Link to more details
+
! Synonyms
  <th>Synonyms
+
! Status
  <th>Status
+
|-
  </tr>
+
| cache
  <tr>
+
| Value must be "public", "private", or "no-cache",. Inteded as a simple way to tell user agents whether to store a copy of the document or not. An alternate for HTTP/1.1's cache-control; for publishers without access to modifying cache-control.<br/>'''This doesn't actually work, use HTTP headers instead'''
  <td>cache
+
| none
  <td>Value must be "public", "private", or "no-cache",. Inteded as a simple way to tell user agents whether to store a copy of the document or not. An alternate for HTTP/1.1's cache-control; for publishers without access to modifying cache-control.  
+
|
 
+
| Unendorsed
'''This doesn't actually work, use HTTP headers instead'''
+
|-
  <td>none
+
| description
  <td>
+
| A short paragraph of text explaining what the page is about.
  <td>Unendorsed
+
| none
  </tr>
+
|
  <tr>
+
| Proposal
  <td>description
+
|-
  <td>A short paragraph of text explaining what the page is about.
+
| keywords
  <td>none
+
| A comma separated list of keywords that describe this page. Not necessary these days; search engines use much more sophisticated means to determine the page's contents.
  <td>
+
| none
  <td>Proposal
+
|
  </tr>
+
| Unendorsed
  <tr>
+
|-
  <td>keywords
+
| robots
  <td>A comma separated list of keywords that describe this page. Not necessary these days; search engines use much more sophisticated means to determine the page's contents.
+
| A comma separated list of operators explaining hos search engine crawlers should treat the content. Possible values are "noarchive" to prevent cached versions, "noindex" to prevent indexing, and "nofollow" works as the link rel value with the same name. This meta name is already supported by every popular search engine.
  <td>none
+
| [http://www.robotstxt.org/wc/exclusion.html#meta Robots exclusion protocol], [http://www.google.com/support/webmasters/bin/answer.py?answer=61050 Googlebot], [http://help.yahoo.com/help/us/ysearch/slurp/index.html Yahoo&#33; Slurp], and [http://about.ask.com/en/docs/about/webmasters.shtml Ask.com Teoma]
  <td>
+
|
  <td>Unendorsed
+
| Proposal
  </tr>
+
|}
  <tr>
 
  <td>robots
 
  <td>A comma separated list of operators explaining hos search engine crawlers should treat the content. Possible values are "noarchive" to prevent cached versions, "noindex" to prevent indexing, and "nofollow" works as the link rel value with the same name. This meta name is already supported by every popular search engine.
 
  <td>[http://www.robotstxt.org/wc/exclusion.html#meta Robots exclusion protocol], [http://www.google.com/support/webmasters/bin/answer.py?answer=61050 Googlebot], [http://help.yahoo.com/help/us/ysearch/slurp/index.html Yahoo! Slurp], and [http://about.ask.com/en/docs/about/webmasters.shtml Ask.com Teoma]
 
  <td>
 
  <td>Proposal
 
  </tr>
 
</table>
 
  
 
For the "Status" section to be changed to "Accepted", the proposed keyword must have been through the [http://microformats.org/wiki/process Microformats process], and been approved by the Microformats community. If it fails to go through this process, it is "Unendorsed".
 
For the "Status" section to be changed to "Accepted", the proposed keyword must have been through the [http://microformats.org/wiki/process Microformats process], and been approved by the Microformats community. If it fails to go through this process, it is "Unendorsed".
  
 
For more details, see [http://whatwg.org/specs/web-apps/current-work/#meta the HTML5 specification].
 
For more details, see [http://whatwg.org/specs/web-apps/current-work/#meta the HTML5 specification].

Revision as of 10:28, 4 September 2007

This page lists the allowed extension values for the name="" attribute of the <meta> element in HTML5. You may add your own values to this list, which makes them legal HTML5 metadata names. We ask that you try to avoid redundancy; if someone has already defined a name that does roughly what you want, please reuse it.

Keyword Brief description Link to more details Synonyms Status
cache Value must be "public", "private", or "no-cache",. Inteded as a simple way to tell user agents whether to store a copy of the document or not. An alternate for HTTP/1.1's cache-control; for publishers without access to modifying cache-control.
This doesn't actually work, use HTTP headers instead
none Unendorsed
description A short paragraph of text explaining what the page is about. none Proposal
keywords A comma separated list of keywords that describe this page. Not necessary these days; search engines use much more sophisticated means to determine the page's contents. none Unendorsed
robots A comma separated list of operators explaining hos search engine crawlers should treat the content. Possible values are "noarchive" to prevent cached versions, "noindex" to prevent indexing, and "nofollow" works as the link rel value with the same name. This meta name is already supported by every popular search engine. Robots exclusion protocol, Googlebot, Yahoo! Slurp, and Ask.com Teoma Proposal

For the "Status" section to be changed to "Accepted", the proposed keyword must have been through the Microformats process, and been approved by the Microformats community. If it fails to go through this process, it is "Unendorsed".

For more details, see the HTML5 specification.