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
(Registered Extensions: removed DCTERMS.* properties requiring a non-literal value. Added notes about optional non-literal <link> references.)
(Proposals That Don't Meet the Requirements For a Registration: Corrected syntax; and, minor, in two prior edits including my latest, added spaces.)
(42 intermediate revisions by 9 users not shown)
Line 1: Line 1:
This page lists the allowed extension values for the name="" attribute of the &lt;meta> element in HTML5.  
+
This page lists extension values for the name="" attribute of the HTML &lt;meta> element. You may add your own values to this list. We ask that you:
  
You may add your own values to this list, which makes them legal HTML5 metadata names.  
+
* '''Avoid redundancy''' - if someone has already defined a name that does roughly what you want, please reuse it.
 +
* '''Be sure to include ''all'' the items''' [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#other-metadata-names outlined in the spec] ''including a link to a specification'' that specifies the keyword ''as an HTML meta keyword''.  If a proposal lacks a specification and a version in a complete specification exists, the latter is to be preferred.
 +
* '''Alphabetize by keyword''', without regard for case, in any table. Sort nonalphanumerics by ASCII value.
 +
* '''Namespaces cannot be reserved.''' Instead, register individual names (known as enumerated values although you don't have to number them).
  
We ask that you:
+
Note that URL-valued properties must not be added to this page as meta names but should be registered as [http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions rel keywords] instead.  
* '''avoid redundancy''' - if someone has already defined a name that does roughly what you want, please reuse it.
 
* '''be sure to include ''all'' the items''' [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#other-metadata-names required by the spec] ''including a link to a specification'' that specifies the keyword ''as an HTML meta keyword''.  If a proposal lacks a specification and a version in a complete specification exists, the latter is to be preferred.  
 
  
Note that URL-valued properties must not be registered as meta names but should be registered as [http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions rel keywords] instead.
+
__TOC__
  
Also note that changes to this registry will not be reflected in validators in real time. But the validators will get automatically updated with the changes within one week or so.
+
== Meta Name Extensions ==
 
 
== Registered Extensions ==
 
  
 
{| class="wikitable sortable"
 
{| class="wikitable sortable"
Line 21: Line 20:
  
 
|-valign="top"  
 
|-valign="top"  
| AGLSTERMS.allow-search
+
| AGLSTERMS.accessibility
| A specific piece of legislation which requires or drives the creation or provision of the resource.
+
| A statement indicating the accessibility characteristics of the resource.
 
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
 
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
 
|  
 
|  
 
| Proposal
 
| Proposal
 
  
 
|-valign="top"  
 
|-valign="top"  
| AGLSTERMS.act
+
| AGLSTERMS.accessMode
| A specific piece of legislation which requires or drives the creation or provision of the resource.
+
| Perceptual mode for the resource.  
 
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
 
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
 
|  
 
|  
Line 36: Line 34:
  
 
|-valign="top"  
 
|-valign="top"  
| AGLSTERMS.accessibility
+
| AGLSTERMS.act
| A statement indicating the accessibility characteristics of the resource.
+
| A specific piece of legislation which requires or drives the creation or provision of the resource.
 
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
 
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
 
|  
 
|  
Line 43: Line 41:
  
 
|-valign="top"  
 
|-valign="top"  
| AGLSTERMS.accessMode
+
| AGLSTERMS.aggregationLevel
| Perceptual mode for the resource.  
+
| The level of aggregation of the described resource - an 'item' or a 'collection'.
 
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
 
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
 
|  
 
|  
Line 50: Line 48:
  
 
|-valign="top"  
 
|-valign="top"  
| AGLSTERMS.aggregationLevel
+
| AGLSTERMS.allow-search
| The level of aggregation of the described resource - an 'item' or a 'collection'.
+
| A specific piece of legislation which requires or drives the creation or provision of the resource.
 
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
 
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
 
|  
 
|  
Line 99: Line 97:
  
 
|-valign="top"  
 
|-valign="top"  
| AGLSTERMS.isBasisFor
+
| AGLSTERMS.isBasedOn
| A related resource that is a performance, production, derivation, translation or interpretation of the described resource.
+
| A related resource of which the described resource is a performance, production, derivation, translation or interpretation.
 
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
 
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
 
|  
 
|  
Line 106: Line 104:
  
 
|-valign="top"  
 
|-valign="top"  
| AGLSTERMS.isBasedOn
+
| AGLSTERMS.isBasisFor
| A related resource of which the described resource is a performance, production, derivation, translation or interpretation.
+
| A related resource that is a performance, production, derivation, translation or interpretation of the described resource.
 
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
 
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
 
|  
 
|  
Line 176: Line 174:
  
 
|-valign="top"  
 
|-valign="top"  
| apple-touch-fullscreen
+
| apple-mobile-web-app-title
| forces iPhone Fullscreen mode, if added to home screen. Not needed anymore.
+
| Sets the title of the application when added to the homescreen on iOS6+
| No specification yet
+
| [https://jokenetwork.de/faq/apple/title/ Unofficial Documentation of apple-mobile-web-app-title] - Read more about Apple's web-app's at [https://developer.apple.com/library/safari/documentation/appleapplications/reference/SafariHTMLRef/Articles/MetaTags.html Apple Safari HTML Reference]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| apple-mobile-web-app-title
+
| apple-touch-fullscreen
| Sets the title of the application when added to the homescreen on iOS6+
+
| forces iPhone Fullscreen mode, if added to home screen. Not needed anymore.
| [https://jokenetwork.de/faq/apple/title/ Unofficial Documentation of apple-mobile-web-app-title] - Read more about Apple's web-app's at [https://developer.apple.com/library/safari/documentation/appleapplications/reference/SafariHTMLRef/Articles/MetaTags.html Apple Safari HTML Reference]
+
| No specification yet
 
|  
 
|  
 
| Proposal
 
| Proposal
 +
 +
|-valign="top"
 +
| application-name
 +
| For Windows 7: "[D]efines the name of the Pinned site application instance. This is the name that appears in a tooltip when hovering over the Pinned site button on the Windows 7 taskbar. The application name is also appended to the window title of the Pinned site application instance." Although the documentation refers to an application, it gives an example of writing this metadata for HTML. Indeed, this name must not be used except in a Web application, according to HTML Living Standard and HTML 5.1.
 +
| [https://msdn.microsoft.com/en-us/library/gg491732%28v=vs.85%29.aspx Declaring Pinned Site Metadata (Microsoft Developer Network)]
 +
|
 +
| Proposed
  
 
|-valign="top"
 
|-valign="top"
Line 199: Line 204:
  
 
|-valign="top"  
 
|-valign="top"  
| baiduspider
+
| audience
| Synonym of <code>robots</code> for targeting Baidu only.
+
| Categorize the principal intended audience for the page, generally with a controlled vocabulary.<br /><br />Google uses this tag: [https://support.google.com/customsearch/answer/2595557?hl=en Custom Search Help], as accessed Jan. 8, 2016.
| [http://www.baidu.com/search/robots_english.html Baidu documentation]
+
| [http://brittlebit.org/specifications/html-meta-audience/specification-for-html-meta-element-with-name-value-audience.html BrittleBit.org spec]
 
|  
 
|  
 
| Proposal
 
| Proposal
Line 207: Line 212:
 
|-valign="top"  
 
|-valign="top"  
 
| bitcoin
 
| bitcoin
| a bitcoin-address
+
| A bitcoin-address
 
| Short documentation (unofficial): [https://jokenetwork.de/faq/bitcoin JokeNetwork's unofficial documentation for bitcoin-metatag], more informations about the Bitcoin-adress: [https://en.bitcoin.it/wiki/Address Bitcoin wiki]
 
| Short documentation (unofficial): [https://jokenetwork.de/faq/bitcoin JokeNetwork's unofficial documentation for bitcoin-metatag], more informations about the Bitcoin-adress: [https://en.bitcoin.it/wiki/Address Bitcoin wiki]
 
|  
 
|  
Line 213: Line 218:
  
 
|-valign="top"  
 
|-valign="top"  
| blazerr-support-identifier
+
| blazerr-secure
| Used to identify users for JokeNetwork's Blazerr Support-System along with a cookie. Not adapted to the cookie policy of the EU yet. The verification of a user without the use of cookies can be obtained with the meta tag [https://jokenetwork.de/faq/blazerr/ blazerr-support-id-noncookies].
+
| Decides whether connect via a secure connection or not to JokeNetwork's Blazerr-System. Synonym to blazerr-ssl, but only for old browsers such as Internet Explorer 7.<br>
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-support-identifier JokeNetwork's Blazerr Documentation]
+
Usage: <code><meta name="blazerr-secure" content="yes"></code>
 +
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-secure JokeNetwork's Blazerr Documentation]
 
|  
 
|  
| proposal
+
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| blazerr-support-id-noncookies
+
| blazerr-seo
| Used to identify users for JokeNetwork's Blazerr Support-System without a cookie.
+
| Checks whether Blazerr SEO has been used or not. It contains the user-id and the SEO Version.<br>
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-support-id-noncookies JokeNetwork's Blazerr Documentation]
+
Usage: <code><meta name="blazerr-seo" content="0001;v0.7"></code><br>0001 is an example for a user id, v0.7 identifies which version of SEO is used (In this case version Beta 7 / 0.7). If you're using Blazerr SEO, you have to include this meta-tag. Otherwise the tool will not work.
 +
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-seo JokeNetwork's Blazerr Documentation]
 
|  
 
|  
| proposal
+
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
Line 231: Line 238:
 
Usage: <code><meta name="blazerr-ssl" content="yes"></code>
 
Usage: <code><meta name="blazerr-ssl" content="yes"></code>
 
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-ssl JokeNetwork's Blazerr Documentation]
 
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-ssl JokeNetwork's Blazerr Documentation]
|  
+
| blazerr-secure is partial synonym (see that entry)
| proposal
+
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| blazerr-secure
+
| blazerr-support-id-noncookies
| Decides whether connect via a secure connection or not to JokeNetwork's Blazerr-System. Synonym to blazerr-ssl, but only for old browsers such as Internet Explorer 7.<br>
+
| Used to identify users for JokeNetwork's Blazerr Support-System without a cookie. Deprecated.
Usage: <code><meta name="blazerr-secure" content="yes"></code>
+
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-support-id-noncookies JokeNetwork's Blazerr Documentation]
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-secure JokeNetwork's Blazerr Documentation]
 
 
|  
 
|  
| proposal
+
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| blazerr-seo
+
| blazerr-support-identifier
| Checks whether Blazerr SEO has been used or not. It contains the user-id and the SEO Version.<br>
+
| Used to identify users for JokeNetwork's Blazerr Support-System along with a cookie. The verification of a user without the use of cookies can be obtained with the deprecated meta tag [https://jokenetwork.de/faq/blazerr/ blazerr-support-id-noncookies].
Usage: <code><meta name="blazerr-seo" content="0001;v0.7"></code><br>0001 is an example for a user id, v0.7 identifies which version of SEO is used (In this case version Beta 7 / 0.7). If you're using Blazerr SEO, you have to include this meta-tag. Otherwise the tool will not work.
+
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-support-identifier JokeNetwork's Blazerr Documentation]
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-seo JokeNetwork's Blazerr Documentation]
 
 
|  
 
|  
| proposal
+
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
Line 255: Line 260:
 
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]
 
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]
 
|  
 
|  
| proposal
+
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
Line 262: Line 267:
 
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]
 
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]
 
|  
 
|  
| proposal
+
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
Line 269: Line 274:
 
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]
 
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]
 
|  
 
|  
| proposal
+
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
Line 276: Line 281:
 
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]
 
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]
 
|  
 
|  
| proposal
+
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
Line 283: Line 288:
 
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]
 
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]
 
|  
 
|  
| proposal
+
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| theme-color
+
| cfia.gdr.activity
| Indicates a color associated with the web site's theme. Web browsers might use this color to theme their UI to be consistent with the web site's color scheme.<br>
+
| Canadian Food Inspection Agency Guidance Document Repository Page Activity
Usage: <code><meta name="theme-color" content="papayawhip"></code>
 
| [https://github.com/whatwg/meta-brand-color Documentation]
 
|
 
| proposal
 
 
 
|-valign="top"
 
| cfia.gdr.include
 
| Canadian Food Inspection Agency Guidance Document Repository Page
 
 
| Coming soon at [http://www.inspection.gc.ca CFIA website]
 
| Coming soon at [http://www.inspection.gc.ca CFIA website]
 
|  
 
|  
Line 301: Line 298:
  
 
|-valign="top"  
 
|-valign="top"  
| cfia.gdr.program
+
| cfia.gdr.commodity
| Canadian Food Inspection Agency Guidance Document Repository Page Program
+
| Canadian Food Inspection Agency Guidance Document Repository Page Commodity
 
| Coming soon at [http://www.inspection.gc.ca CFIA website]
 
| Coming soon at [http://www.inspection.gc.ca CFIA website]
 
|  
 
|  
Line 308: Line 305:
  
 
|-valign="top"  
 
|-valign="top"  
| cfia.gdr.commodity
+
| cfia.gdr.include
| Canadian Food Inspection Agency Guidance Document Repository Page Commodity
+
| Canadian Food Inspection Agency Guidance Document Repository Page
 
| Coming soon at [http://www.inspection.gc.ca CFIA website]
 
| Coming soon at [http://www.inspection.gc.ca CFIA website]
 
|  
 
|  
Line 315: Line 312:
  
 
|-valign="top"  
 
|-valign="top"  
| cfia.gdr.activity
+
| cfia.gdr.program
| Canadian Food Inspection Agency Guidance Document Repository Page Activity
+
| Canadian Food Inspection Agency Guidance Document Repository Page Program
 
| Coming soon at [http://www.inspection.gc.ca CFIA website]
 
| Coming soon at [http://www.inspection.gc.ca CFIA website]
 
|  
 
|  
Line 457: Line 454:
 
| citation_publisher
 
| citation_publisher
 
| The name of the publisher of an academic paper
 
| The name of the publisher of an academic paper
|  
+
| The [https://www.google.com/intl/en/scholar/inclusion.html#indexing spec] (as accessed 11-26-17) omits this meta name but refers to the meta name DC.publisher (see that on this page).
 
|  
 
|  
 
| Proposal
 
| Proposal
Line 515: Line 512:
 
| [http://arpita.github.io/ContactMetaExtensions/ Documentation]
 
| [http://arpita.github.io/ContactMetaExtensions/ Documentation]
 
|  
 
|  
| proposal
+
| Proposal
 +
 
 +
|-valign="top"
 +
| creator
 +
| Identify the creator of the page’s content, the content generally being the principal part of what info is rendered for website visitors.
 +
| [http://brittlebit.org/specifications/html-meta-creator/specification-for-html-meta-element-with-name-value-creator.html BrittleBit.org spec]
 +
|
 +
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
Line 672: Line 676:
  
 
|-valign="top"
 
|-valign="top"
| DC.contributor
+
| dc.created
| An entity responsible for making contributions to the resource.
+
| Date of creation of the resource.
It must be accompanied by a <code>&lt;link rel="schema.DC" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#elements-contributor DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-created DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| '''superseded by DCTERMS:contributor, especially for non-literal values.'''
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DC.coverage
+
| dc.creator
| The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.
+
| An entity primarily responsible for making the resource.
It must be accompanied by a <code>&lt;link rel="schema.DC" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#elements-coverage DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-creator DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| '''superseded by DCTERMS:coverage, especially for non-literal values.'''
+
|  
 +
| Proposal
 +
 
 +
|-valign="top"
 +
| dc.date.issued
 +
| Date of publication for Google News. The format of the content is YYYY-MM-DD or YYYY-MM-DDThh:mm:ssTZD.
 +
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element
 +
| [http://www.google.com/support/news_pub/bin/answer.py?answer=93994 Google News documentation]
 +
| <code>dcterms.issued</code> (former <code>&lt;time pubdate&gt;</code> no longer considered due to the abort of <code>@pubdate</code>)
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DC.creator
+
| dc.dateCopyrighted
| An entity primarily responsible for making the resource.
+
| Date of copyright.
It must be accompanied by a <code>&lt;link rel="schema.DC" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#elements-creator DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-dateCopyrighted DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| '''superseded by DCTERMS:creator, especially for non-literal values.'''
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DC.date
+
| dc.dateSubmitted
| A point or period of time associated with an event in the lifecycle of the resource.
+
| Date of submission of the resource.
It must be accompanied by a <code>&lt;link rel="schema.DC" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#elements-date DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-dateSubmitted DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| '''superseded by DCTERMS:date, especially for non-literal values.'''
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DC.description
+
| dc.description
 
| An account of the resource.
 
| An account of the resource.
It must be accompanied by a <code>&lt;link rel="schema.DC" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#elements-description DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-description DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| '''superseded by DCTERMS:description, especially for non-literal values.'''
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DC.format
+
| dc.language
| The file format, physical medium, or dimensions of the resource.
+
| A language of the resource. Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646].  
It must be accompanied by a <code>&lt;link rel="schema.DC" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#elements-format DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-language DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| '''superseded by DCTERMS:format, especially for non-literal values.'''
+
| Redundant with the <code>lang</code> attribute on the
 +
<code>html</code> element. (Browsers pay attention to the <code>lang</code> attribute but not <code>dc.language</code>)
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DC.identifier
+
| dc.license
| An unambiguous reference to the resource within a given context.
+
| A legal document giving official permission to do something with the resource.
It must be accompanied by a <code>&lt;link rel="schema.DC" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#elements-identifier DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-license DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| '''superseded by DCTERMS:identifier, especially for non-literal values.'''
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DC.language
+
| dc.mediator
| A language of the resource. Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646].  
+
| An entity that mediates access to the resource and for whom the resource is intended or useful.
It must be accompanied by a <code>&lt;link rel="schema.DC" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#elements-language DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-mediator DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| '''superseded by DCTERMS:language, especially for non-literal values.''' <br />
+
|  
Redundant with the <code>lang</code> attribute on the
 
<code>html</code> element. (Browsers pay attention to the <code>lang</code> attribute but not <code>DC.language</code>)
 
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DC.publisher
+
| dc.medium
| An entity responsible for making the resource available.
+
| The material or physical carrier of the resource.
It must be accompanied by a <code>&lt;link rel="schema.DC" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#elements-publisher DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-medium DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| '''superseded by DCTERMS:publisher, especially for non-literal values.'''
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DC.relation
+
| dc.modified
| A related resource.
+
| Date on which the resource was changed.
It must be accompanied by a <code>&lt;link rel="schema.DC" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#elements-relation DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-modified DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| '''superseded by DCTERMS:relation, especially for non-literal values.'''
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DC.rights
+
| dc.provenance
| Information about rights held in and over the resource.
+
| A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation.
It must be accompanied by a <code>&lt;link rel="schema.DC" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#elements-rights DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-provenance DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| '''superseded by DCTERMS:rights, especially for non-literal values.'''
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DC.source
+
| dc.publisher
| A related resource from which the described resource is derived.
+
| An entity responsible for making the resource available.
It must be accompanied by a <code>&lt;link rel="schema.DC" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#elements-source DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-publisher DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| '''superseded by DCTERMS:source, especially for non-literal values.'''
+
|  
 +
| Proposal
 +
 
 +
|-valign="top"
 +
| dc.references
 +
| A related resource that is referenced, cited, or otherwise pointed to by the described resource.
 +
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
 +
| [http://dublincore.org/documents/dcmi-terms/#terms-references DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 +
|
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DC.subject
+
| dc.temporal
| The topic of the resource.
+
| Temporal characteristics of the resource.
It must be accompanied by a <code>&lt;link rel="schema.DC" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#elements-subject DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-temporal DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| '''superseded by DCTERMS:subject, especially for non-literal values.'''
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DC.title
+
| dc.title
 
| A name given to the resource.
 
| A name given to the resource.
It must be accompanied by a <code>&lt;link rel="schema.DC" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#elements-title DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-title DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| '''superseded by DCTERMS:title, especially for non-literal values.'''
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DC.type
+
| dc.type
 
| The nature or genre of the resource. Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE].
 
| The nature or genre of the resource. Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE].
 
To describe the file format, physical medium, or dimensions of the resource, use the Format element.
 
To describe the file format, physical medium, or dimensions of the resource, use the Format element.
It must be accompanied by a <code>&lt;link rel="schema.DC" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#elements-type DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-type DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| '''superseded by DCTERMS:type, especially for non-literal values.'''
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.abstract
+
| dc.valid
 +
| Date (often a range) of validity of a resource.
 +
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.
 +
| [http://dublincore.org/documents/dcmi-terms/#terms-valid DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 +
|
 +
| Proposal
 +
 
 +
|-valign="top"
 +
| DCS.dcssta
 +
| '''Error page parameter'''
 +
This defines an error code web page so that Webtrends can identify it as a non-success page. Generally used to identify pages that contain 400 and 500 series return codes. As a result, Webtrends excludes these pages from its standard "Pages" report, to instead populate its standard "errors" report.
 +
Example:
 +
<meta name="DCS.dcssta" content="404">
 +
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters].
 +
|
 +
| Proposal
 +
 
 +
|-valign="top"
 +
| dcterms.abstract
 
| A summary of the resource.  
 
| A summary of the resource.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-abstract DCMI
 
| [http://dublincore.org/documents/dcmi-terms/#terms-abstract DCMI
 
Metadata Terms] mapped according to
 
Metadata Terms] mapped according to
Line 820: Line 859:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.accessRights
+
| dcterms.accessRights
 
| Information about who can access the resource or an indication of its security status.  
 
| Information about who can access the resource or an indication of its security status.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-accessRights DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-accessRights DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 829: Line 868:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.accrualMethod
+
| dcterms.accrualMethod
 
| The method by which items are added to a collection.  
 
| The method by which items are added to a collection.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-accrualMethod DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-accrualMethod DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 838: Line 877:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.accrualPeriodicity
+
| dcterms.accrualPeriodicity
 
| The frequency with which items are added to a collection.  
 
| The frequency with which items are added to a collection.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-accrualPeriodicity DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-accrualPeriodicity DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 847: Line 886:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.accrualPolicy
+
| dcterms.accrualPolicy
 
| The policy governing the addition of items to a collection.  
 
| The policy governing the addition of items to a collection.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-accrualPolicy DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-accrualPolicy DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 856: Line 895:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.alternative
+
| dcterms.alternative
 
| An alternative name for the resource.  
 
| An alternative name for the resource.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-alternative DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-alternative DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 865: Line 904:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.audience
+
| dcterms.audience
 
| A class of entity for whom the resource is intended or useful.  
 
| A class of entity for whom the resource is intended or useful.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-audience DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-audience DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 874: Line 913:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.available
+
| dcterms.available
 
| Date (often a range) that the resource became or will become available.  
 
| Date (often a range) that the resource became or will become available.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-available DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-available DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 883: Line 922:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.bibliographicCitation
+
| dcterms.bibliographicCitation
 
| A bibliographic reference for the resource.  
 
| A bibliographic reference for the resource.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-bibliographicCitation DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-bibliographicCitation DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 892: Line 931:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.conformsTo
+
| dcterms.collection
| An established standard to which the described resource conforms.  
+
| An aggregation of resources.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-conformsTo DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#dcmitype-Collection DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| If a non-literal value is preferable, it may be replaced by <code>&lt;link rel="DCTERMS.conformsTo" href="''reference URI'''" /></code>
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.contributor
+
| dcterms.conformsTo
 +
| An established standard to which the described resource conforms.
 +
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 +
| [http://dublincore.org/documents/dcmi-terms/#terms-conformsTo DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 +
|
 +
| Proposal
 +
 
 +
|-valign="top"
 +
| dcterms.contributor
 
| An entity responsible for making contributions to the content of the resource.  
 
| An entity responsible for making contributions to the content of the resource.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-contributor DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-contributor DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| If a non-literal value is preferable, it may be replaced by <code>&lt;link rel="DCTERMS.contributor" href="''reference URI'''" /></code>
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.coverage
+
| dcterms.coverage
 
| The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.  
 
| The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-coverage DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-coverage DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 919: Line 967:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.created
+
| dcterms.created
 
| Date of creation of the resource.  
 
| Date of creation of the resource.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-created DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-created DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 928: Line 976:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.creator
+
| dcterms.creator
 
| An entity primarily responsible for making the resource. Examples of a Creator include a person, an organization, or a service.  
 
| An entity primarily responsible for making the resource. Examples of a Creator include a person, an organization, or a service.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-creator DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-creator DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| If a non-literal value is preferable, it may be replaced by <code>&lt;link rel="DCTERMS.creator" href="''reference URI'''" /></code><br />
+
| In some cases redundant with the HTML built-in keyword <code>author</code>
In some cases redundant with the HTML built-in keyword <code>author</code>
 
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.date
+
| dcterms.date
 
| A point or period of time associated with an event in the lifecycle of the resource.  
 
| A point or period of time associated with an event in the lifecycle of the resource.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-date DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-date DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 947: Line 994:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.dateAccepted
+
| dcterms.dateAccepted
 
| Date of acceptance of the resource.  
 
| Date of acceptance of the resource.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-dateAccepted DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-dateAccepted DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 956: Line 1,003:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.dateCopyrighted
+
| dcterms.dateCopyrighted
 
| Date of copyright.  
 
| Date of copyright.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-dateCopyrighted DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-dateCopyrighted DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 965: Line 1,012:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.dateSubmitted
+
| dcterms.dateSubmitted
 
| Date of submission of the resource.  
 
| Date of submission of the resource.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-dateSubmitted DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-dateSubmitted DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 974: Line 1,021:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.description
+
| dcterms.description
 
| An account of the resource. Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.  
 
| An account of the resource. Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-description DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-description DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| If a non-literal value is preferable, it may be replaced by <code>&lt;link rel="DCTERMS.description" href="''reference URI'''" /></code><br />
+
| HTML built-in keyword <code>description</code>  
HTML built-in keyword <code>description</code>  
 
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.educationLevel
+
| dcterms.educationLevel
 
| A class of entity, defined in terms of progression through an educational or training context, for which the described resource is intended.  
 
| A class of entity, defined in terms of progression through an educational or training context, for which the described resource is intended.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-educationLevel DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-educationLevel DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 993: Line 1,039:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.extent
+
| dcterms.extent
 
| The size or duration of the resource.  
 
| The size or duration of the resource.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-extent DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-extent DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 1,002: Line 1,048:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.format
+
| dcterms.format
 
| The file format, physical medium, or dimensions of the resource.  
 
| The file format, physical medium, or dimensions of the resource.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-format DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-format DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| File format for the document is purely advisory, as is to be determined by server. Linked resources can be described by <code>type</code> attribute.
+
| To be limited to dimensions information. File format for the document is to be determined by server. Linked resources can be described by <code>type</code> attribute.
 +
| Proposal
 +
 
 +
|-valign="top"
 +
| dcterms.hasFormat
 +
| A related resource that is substantially the same as the pre-existing described resource, but in another format.
 +
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 +
| [http://dublincore.org/documents/dcmi-terms/#terms-hasFormat DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 +
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code>
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.identifier
+
| dcterms.hasPart
 +
| A related resource that is included either physically or logically in the described resource.
 +
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 +
| [http://dublincore.org/documents/dcmi-terms/#terms-hasPart DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 +
|
 +
| Proposal
 +
 +
|-valign="top"
 +
| dcterms.hasVersion
 +
| A related resource that is a version, edition, or adaptation of the described resource.
 +
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 +
| [http://dublincore.org/documents/dcmi-terms/#terms-hasVersion DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 +
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code>
 +
| Proposal
 +
 
 +
|-valign="top"
 +
| dcterms.identifier
 
| An unambiguous reference to the resource within a given context.  
 
| An unambiguous reference to the resource within a given context.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-identifier DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-identifier DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| If a non-literal value is preferable, it may be replaced by <code>&lt;link rel="DCTERMS.identifier" href="''reference URI'''" /></code>
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.instructionalMethod
+
| dcterms.instructionalMethod
 
| A process used to engender knowledge, attitudes and skills, that the described resource is designed to support.  
 
| A process used to engender knowledge, attitudes and skills, that the described resource is designed to support.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 
| [http://dublincore.org/documents/dcmi-terms/#terms-instructionalMethod DCMI Metadata Terms] mapped according to
 
| [http://dublincore.org/documents/dcmi-terms/#terms-instructionalMethod DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
Line 1,029: Line 1,102:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.issued
+
| dcterms.isFormatOf
| Date of formal issuance (e.g., publication) of the resource. (DC doesn't spec a date format but the established practice is YYYY-MM-DD.)
+
| A related resource that is substantially the same as the described resource, but in another format.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-issued DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-isFormatOf DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| (former <code>&lt;time pubdate&gt;</code> no longer considered due to the abort of <code>@pubdate</code>)
+
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code>
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.language
+
| dcterms.isPartOf
| A language of the resource. Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646].  
+
| A related resource in which the described resource is physically or logically included.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-language DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-isPartOf DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| Redundant with the <code>lang</code> attribute on the <code>html</code> element. (Browsers pay attention to the <code>lang</code> attribute but not <code>DCTERMS.language</code>)
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.license
+
| dcterms.isReferencedBy
| A legal document giving official permission to do something with the resource.  
+
| A related resource that references, cites, or otherwise points to the described resource.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-license DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-isReferencedBy DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| If a non-literal value is preferable, it may be replaced by <code>&lt;link rel="DCTERMS.license" href="''reference URI'''" /></code><br />
+
|  
The HTML <code>&lt;link&gt;</code> element with the keyword <code>"license"</code> as value of the <code>rel</code> attribute.
 
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.mediator
+
| dcterms.isReplacedBy
| An entity that mediates access to the resource and for whom the resource is intended or useful.  
+
| A related resource that supplants, displaces, or supersedes the described resource.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-mediator DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-isReplacedBy DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| If a non-literal value is preferable, it may be replaced by <code>&lt;link rel="DCTERMS.mediator" href="''reference URI'''" /></code>
+
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code>
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.medium
+
| dcterms.isRequiredBy
| The material or physical carrier of the resource.
+
| A related resource that requires the described resource to support its function, delivery, or coherence.
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-medium DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-isRequiredBy DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
|  
 
|  
Line 1,075: Line 1,147:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.modified
+
| dcterms.issued
| Date on which the resource was changed. (DC doesn't spec a date format but the established practice is YYYY-MM-DD.)  
+
| Date of formal issuance (e.g., publication) of the resource. (DC doesn't spec a date format but the established practice is YYYY-MM-DD.)  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-modified DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-issued DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
|
+
| (former <code>&lt;time pubdate&gt;</code> no longer considered due to the abort of <code>@pubdate</code>)
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.provenance
+
| dcterms.isVersionOf
| A statement for any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation.  
+
| A related resource of which the described resource is a version, edition, or adaptation.
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-provenance DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-isVersionOf DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
|  
+
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code>
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.publisher
+
| dcterms.language
| An entity responsible for making the resource available.  
+
| A language of the resource. Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646].  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-publisher DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-language DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| If a non-literal value is preferable, it may be replaced by <code>&lt;link rel="DCTERMS.publisher" href="''reference URI'''" /></code>
+
| Redundant with the <code>lang</code> attribute on the <code>html</code> element. (Browsers pay attention to the <code>lang</code> attribute but not <code>dcterms.language</code>)
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.rights
+
| dcterms.license
| Information about rights held in and over the resource.  
+
| A legal document giving official permission to do something with the resource.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-rights DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-license DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| The HTML <code>&lt;link&gt;</code> element with the keyword <code>"license"</code> as value of the <code>rel</code> attribute, if referring to a legal license format.
+
| The HTML <code>&lt;link&gt;</code> element with the keyword <code>"license"</code> as value of the <code>rel</code> attribute.
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.rightsHolder
+
| dcterms.mediator
| A person or organization owning or managing rights over the resource.  
+
| An entity that mediates access to the resource and for whom the resource is intended or useful.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-rightsHolder DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-mediator DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| If a non-literal value is preferable, it may be replaced by <code>&lt;link rel="DCTERMS.rightsHolder" href="''reference URI'''" /></code>
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.spatial
+
| dcterms.medium
| Spatial characteristics of the resource.  
+
| The material or physical carrier of the resource.
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-spatial DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-medium DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
|  
 
|  
Line 1,129: Line 1,201:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.tableOfContents
+
| dcterms.modified
| A list of subunits of the resource.  
+
| Date on which the resource was changed. (DC doesn't spec a date format but the established practice is YYYY-MM-DD.)
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-tableOfContents DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-modified DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| HTML built-in keywords <code>description</code> or <code>keywords</code>. Otherwise, a <code>details-summary</code> model which would provide user-readable information.
+
|
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.temporal
+
| dcterms.provenance
| Temporal characteristics of the resource.  
+
| A statement for any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-temporal DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-provenance DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
|  
 
|  
Line 1,147: Line 1,219:
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.title
+
| dcterms.publisher
| A name given to the resource.  
+
| An entity responsible for making the resource available.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-title DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-publisher DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| HTML built-in element <code>title</code> (not to be confused with <code>@title</code> attributes specific to each element)
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.type
+
| dcterms.references
| The nature or genre of the resource.
+
| A related resource that is referenced, cited, or otherwise pointed to by the described resource.
| [http://dublincore.org/documents/dcmi-terms/#terms-type DCMI Metadata Terms] mapped according to
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 +
| [http://dublincore.org/documents/dcmi-terms/#terms-references DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
|  
+
| <code>cite</code> attribute on specific quotes, if any.
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| DCTERMS.valid
+
| dcterms.relation
| Date (often a range) of validity of a resource.  
+
| A related resource.  
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>" /></code> element.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-valid DCMI Metadata Terms] mapped according to
+
| [http://dublincore.org/documents/dcmi-terms/#terms-relation DCMI Metadata Terms] mapped according to
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
|
+
| If the relation comes from an internal reference or quote, <code>dcterms.references</code> should be preferred.
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| detectify-verification
+
| dcterms.replaces
| Used by the Detectify web vulnerability scanner as a domain verification key. The Detectify service will only consider the domain authenticated if it contains the "detectify-verification" meta tag, with the content set according to a per-customer token.
+
| A related resource that is supplanted, displaced, or superseded by the described resource.
| [http://labs.detectify.com/post/85707633296/detectify-validation-specification Documentation]
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
|
+
| [http://dublincore.org/documents/dcmi-terms/#terms-replaces DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 +
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code>
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| designer
+
| dcterms.requires
| Credits the designer(s) responsible for the visual presentation of a website.
+
| A related resource that is required by the described resource to support its function, delivery, or coherence.
| [https://sites.google.com/site/metadesignerspec/ Documentation]
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
|
+
| [http://dublincore.org/documents/dcmi-terms/#terms-requires DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 +
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| entity
+
| dcterms.rights
| Allows for definitions of XML-style entities for substitution of references (defined as specially-named elements (e.g., use of data element and/or data-* attribute) or script tags) via inclusion of a JavaScript library. Library also supports inclusion of additional meta element entity definitions via iframe documents.
+
| Information about rights held in and over the resource.  
| [https://github.com/brettz9/js-css-entities Documentation]
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
|
+
| [http://dublincore.org/documents/dcmi-terms/#terms-rights DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 +
| The HTML <code>&lt;link&gt;</code> element with the keyword <code>"license"</code> as value of the <code>rel</code> attribute, if referring to a legal license format.
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| EssayDirectory
+
| dcterms.rightsHolder
| Defines a custom description of websites listed in EssayDirectory.<br>Example:
+
| A person or organization owning or managing rights over the resource.
<meta name="EssayDirectory" content="Helping students find legitimate essay services.">
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
| [http://essaydirectory.com/privacy-terms/#EssayDirectory_MetaExtension Documentation]
+
| [http://dublincore.org/documents/dcmi-terms/#terms-rightsHolder DCMI Metadata Terms] mapped according to
|
+
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 +
|  
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| fdse-description
+
| dcterms.source
| Tag used by FDSE search software, allows different description to be displayed in fdse results to that shown in description
+
| A related resource from which the described resource is derived.
| [http://www.xav.com/scripts/search/help/1013.html]
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
|  
+
| [http://dublincore.org/documents/dcmi-terms/#terms-source DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 +
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code> if documents are different versions. Otherwise, <code>cite</code> attribute.
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| fdse-index-as
+
| dcterms.spatial
| Tag used by FDSE search software, allows FDSE to index a page as url described here
+
| Spatial characteristics of the resource.
| [http://www.xav.com/scripts/search/help/1014.html]
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
|  
+
| [http://dublincore.org/documents/dcmi-terms/#terms-spatial DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 +
| geographic-coverage
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| fdse-keywords
+
| dcterms.subject
| Tag used by FDSE search software, allows different keywords to be used by FDSE to keywords tag
+
| The topic of the resource.
| [http://www.xav.com/scripts/search/help/1013.html]
+
| [http://dublincore.org/documents/dcmi-terms/#terms-subject DCMI Metadata Terms] mapped according to
|  
+
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 +
| HTML built-in keywords <code>description</code> or <code>keywords</code>
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| fdse-refresh
+
| dcterms.tableOfContents
| Tag used by FDSE search software, allows FDSE to ignore refresh meta tags
+
| A list of subunits of the resource.
| [http://www.xav.com/scripts/search/help/1013.html]
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
|  
+
| [http://dublincore.org/documents/dcmi-terms/#terms-tableOfContents DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 +
| HTML built-in keywords <code>description</code> or <code>keywords</code>. Otherwise, a <code>details-summary</code> model which would provide user-readable information.
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| fdse-robots
+
| dcterms.temporal
| Tag used by FDSE search software, allows different robots instructions to be sent to FDSE than that sent to other search engines eg: index no index pages for local search
+
| Temporal characteristics of the resource.
| [http://www.xav.com/scripts/search/help/1013.html]
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 +
| [http://dublincore.org/documents/dcmi-terms/#terms-temporal DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| gcterms.topicTaxonomy
+
| dcterms.title
| Organize resources specifically for taxonomy-based topical browse or search structures on websites (ie: breadcrumbs / website information architecture).
+
| A name given to the resource.
| [http://www.gcpedia.gc.ca/wiki/Metadata_Tools#Metadata_for_Web_Resource_Discovery] Government of Canada, Web Content Management System Metadata Application Profile.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
|  
+
| [http://dublincore.org/documents/dcmi-terms/#terms-title DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 +
| HTML built-in element <code>title</code> (not to be confused with <code>@title</code> attributes specific to each element)
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| google-play-app
+
| dcterms.type
| Promoting Apps with Smart App Banners
+
| The nature or genre of the resource.
| [http://jasny.github.io/jquery.smartbanner/] Smart banners for Google Apps
+
| [http://dublincore.org/documents/dcmi-terms/#terms-type DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
|icas.datetime.long
+
| dcterms.valid
|A point or period of time associated with an event in the lifecycle of the resource represented in terms of ICAS long date format such as "UCN 12012 M03 Blue ❀ day 333 ❀ IDC zone(UT) t969 tt189". example <meta name="icas.datetime.long" content="UCN 12012 M03 Blue ❀ day 333 ❀ IDC zone(UT) t969 tt189"/>
+
| Date (often a range) of validity of a resource.  
|a preliminary specification in the aaticas group on LinkedIn (http://www.linkedin.com/groups/aaticas-4034149). after a period of review, a specification for AAT ICAS meta keywords for HTML(5) will be referenced on an AAT ICAS area of the aatideas.org web site.
+
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.
 +
| [http://dublincore.org/documents/dcmi-terms/#terms-valid DCMI Metadata Terms] mapped according to
 +
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
 
|
 
|
|proposal
+
| Proposal
  
 
|-valign="top"
 
|-valign="top"
|icas.datetime.day
+
| detectify-verification
|A point or period of time associated with an event in the lifecycle of the resource represented in terms of ICAS day-of-year format such as "2012 day 333 t969".
+
| Used by the Detectify web vulnerability scanner as a domain verification key. The Detectify service will only consider the domain authenticated if it contains the "detectify-verification" meta tag, with the content set according to a per-customer token.
|a preliminary specification in the aaticas group on LinkedIn (http://www.linkedin.com/groups/aaticas-4034149). after a period of review, a specification for AAT ICAS meta keywords for HTML(5) will be referenced on an AAT ICAS area of the aatideas.org web site.
+
| [http://labs.detectify.com/post/85707633296/detectify-validation-specification Documentation]
 
|
 
|
|proposal
+
| Proposal
  
 
|-valign="top"
 
|-valign="top"
|icas.datetime.abbr
+
| designer
|A point or period of time associated with an event in the lifecycle of the resource represented in terms of an ICAS abbreviated format such as "d2M03 t969".
+
| Credits the designer(s) responsible for the visual presentation of a website.
|a preliminary specification in the aaticas group on LinkedIn (http://www.linkedin.com/groups/aaticas-4034149). after a period of review, a specification for AAT ICAS meta keywords for HTML(5) will be referenced on an AAT ICAS area of the aatideas.org web site.
+
| [https://sites.google.com/site/metadesignerspec/ Documentation]
 
|
 
|
|proposal
+
| Proposal
  
 
|-valign="top"
 
|-valign="top"
|icas.datetime
+
| entity
|A point or period of time associated with an event in the lifecycle of the resource represented in terms of an ICAS date and time format of unspecified information density (may include full, long, medium, short, or compressed forms).
+
| Allows for definitions of XML-style entities for substitution of references (defined as specially-named elements (e.g., use of data element and/or data-* attribute) or script tags) via inclusion of a JavaScript library. Library also supports inclusion of additional meta element entity definitions via iframe documents.
|a preliminary specification in the aaticas group on LinkedIn (http://www.linkedin.com/groups/aaticas-4034149). after a period of review, a specification for AAT ICAS meta keywords for HTML(5) will be referenced on an AAT ICAS area of the aatideas.org web site.
+
| [https://github.com/brettz9/js-css-entities Documentation]
 
|
 
|
|proposal
+
| Proposal
 +
 
 +
|-valign="top"
 +
| EssayDirectory
 +
| Defines a custom description of websites listed in EssayDirectory.<br>Example:
 +
<meta name="EssayDirectory" content="Helping students find legitimate essay services.">
 +
| [http://essaydirectory.com/privacy-terms/#EssayDirectory_MetaExtension Documentation]
 +
|
 +
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| format-detection
+
| fdse-description
| Enables or disables automatic detection of possible phone numbers in a webpage in Safari on iOS.
+
| Tag used by FDSE search software, allows different description to be displayed in fdse results to that shown in description
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/SafariHTMLRef/Articles/MetaTags.html Apple Safari HTML Reference]
+
| [http://www.xav.com/scripts/search/help/1013.html]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| fragment
+
| fdse-index-as
| Opts a webpage into the AJAX crawling scheme when it does not have a "#!" URL. The only valid content value is "!".
+
| Tag used by FDSE search software, allows FDSE to index a page as url described here
<meta name="fragment" content="!">
+
| [http://www.xav.com/scripts/search/help/1014.html]
| [https://developers.google.com/webmasters/ajax-crawling/docs/specification Google Crawable AJAX Specification]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| geo.position
+
| fdse-keywords
| Geographic position to which the page is related.
+
| Tag used by FDSE search software, allows different keywords to be used by FDSE to keywords tag
<meta name="geo.position" content="48.02682000000001;7.809769999999958">
+
| [http://www.xav.com/scripts/search/help/1013.html]
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]
 
| icbm (different value syntax)
 
| Proposal
 
 
 
|-valign="top"
 
| geo.country
 
| Case-insensitive ISO 3166-1 alpha-2 code of a country to which the page is related.
 
<meta name="geo.country" content="de">
 
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]<br>[http://en.wikipedia.org/wiki/ISO_3166-2 ISO-3166-2]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| geo.a1
+
| fdse-refresh
| National subdivision (state, canton, region, province, prefecture) of civil address to which the page is related. For resources within the US and Canada, corresponds to the common 2-character State/Province codes.
+
| Tag used by FDSE search software, allows FDSE to ignore refresh meta tags
<meta name="geo.a1" content="AB">
+
| [http://www.xav.com/scripts/search/help/1013.html]
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]<br>RFC 4776
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| geo.a2
+
| fdse-robots
| County, parish, gun (JP), district (IN) of civil address to which the page is related.
+
| Tag used by FDSE search software, allows different robots instructions to be sent to FDSE than that sent to other search engines eg: index no index pages for local search
<meta name="geo.a2" content="Warwickshire">
+
| [http://www.xav.com/scripts/search/help/1013.html]
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]<br>RFC 4776
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| geo.a3
+
| FLBlogAuthor
| City, township, shi (JP) of civil address to which the page is related.
+
| Depicts whether author of the blog is lawfirm or FL author
<meta name="geo.a3" content="Calgary">
+
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]<br>RFC 4776
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| geo.lmk
+
| format-detection
| A landmark or vanity address to which the page is related.
+
| Enables or disables automatic detection of possible phone numbers in a webpage in Safari on iOS.
<meta name="geo.lmk" content="Auwaldstraße 11, 79110 Freiburg im Breisgau, Deutschland">
+
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/SafariHTMLRef/Articles/MetaTags.html Apple Safari HTML Reference]
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| geo.region
+
| format-print
| Superseded by either geo.country alone or geo.country plus geo.a1. Name of geographic region to which the page is related. Content is specified by ISO-3166.
+
| Store print media requirements for a page so a user agent can alert a user to unusual needs, such as special paper, before printing is to begin.
<meta name="geo.region" content="DE-BW">
+
| [http://brittlebit.org/specifications/html-meta-format-print/specification-for-html-meta-element-with-name-value-format-print.html BrittleBit.org spec]
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]<br>[http://en.wikipedia.org/wiki/ISO_3166 ISO-3166]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| geo.placename
+
| fragment
| Superseded by geo.lmk. Name of geographic place to which the page is related.
+
| Opts a webpage into the AJAX crawling scheme when it does not have a "#!" URL. The only valid content value is "!".
  <meta name="geo.placename" content="London, Ontario">
+
  <meta name="fragment" content="!">
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]
+
| [https://developers.google.com/webmasters/ajax-crawling/docs/specification Google Crawable AJAX Specification]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.instruction
+
| FSDateCreation
| Globrix property information: Property to Buy or Rent
+
| Mentions the date when this web page was created
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.price
+
| FSDatePublish
| Globrix property information: Price for the property
+
| Mentions the date when this web page was created
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.postcode
+
| FSFLContent
| Globrix property information: Postcode of the property
+
| Informs the Publisher tool whether this page contains any content or not. Valid values yes or no
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.bedrooms
+
| FSLanguage
| Globrix property information: Number of bedrooms the property has
+
| Language of the content in the page. Example: US English or UK English, etc
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.bathrooms
+
| FSOnSitemap
| Globrix property information: Number of bathrooms the property has
+
| Whether the page is accessible via the Sitemap link in the firmsite
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.type
+
| FSPageDescription
| Globrix property information: Type of property e.g. 'semi-detatched house'
+
| Description of the content of page
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.condition
+
| FSPageName
| Globrix property information: Condition of the property e.g. 'renovated'
+
| Name of the page within a Findlaw firmsite
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.features
+
| FSSearchable
| Globrix property information: Features of the property e.g. 'double glazing'
+
| This tag mentions whether a certain page can be searched or not
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.outsidespace
+
| FSSection
| Globrix property information: External features of the property e.g. 'garden'
+
| Depicts whether a page is a Section Page or simple page. Section pages can have links to other pages
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.parking
+
| FSWritertoolPageType
| Globrix property information: Parking available for property e.g. 'parking for 2 cars'
+
| Page Type of a page in the firmsite. Page Type values help the Publisher toold in page creation
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.period
+
| gcterms.topicTaxonomy
| Globrix property information: Period of the property e.g. 'victorian terrace'
+
| Organize resources specifically for taxonomy-based topical browse or search structures on websites (ie: breadcrumbs / website information architecture).
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
| [http://www.gcpedia.gc.ca/wiki/Metadata_Tools#Metadata_for_Web_Resource_Discovery] Government of Canada, Web Content Management System Metadata Application Profile.
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.poa
+
| geo.a1
| Globrix property information: If the property price is only available on application
+
| National subdivision (state, canton, region, province, prefecture) of civil address to which the page is related. For resources within the US and Canada, corresponds to the common 2-character State/Province codes.
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
<meta name="geo.a1" content="AB">
 +
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]<br>RFC 4776
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.tenure
+
| geo.a2
| Globrix property information: The tenure of the property e.g. 'leasehold'
+
| County, parish, gun (JP), district (IN) of civil address to which the page is related.
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
<meta name="geo.a2" content="Warwickshire">
 +
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]<br>RFC 4776
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.underoffer
+
| geo.a3
| Globrix property information: Indicates if the property is under offer
+
| City, township, shi (JP) of civil address to which the page is related.
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
<meta name="geo.a3" content="Calgary">
 +
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]<br>RFC 4776
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.priceproximity
+
| geo.country
| Globrix property information: The region of the attached price e.g. 'guide price of'
+
| Case-insensitive ISO 3166-1 alpha-2 code of a country to which the page is related.
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
<meta name="geo.country" content="de">
 +
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]<br>[http://en.wikipedia.org/wiki/ISO_3166-2 ISO-3166-2]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.latitude
+
| geo.lmk
| Globrix property information: The latitude of the property
+
| A landmark or vanity address to which the page is related.
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
<meta name="geo.lmk" content="Auwaldstraße 11, 79110 Freiburg im Breisgau, Deutschland">
 +
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| globrix.longitude
+
| geo.placename
| Globrix property information: The longitude of the property
+
| Superseded by geo.lmk. Name of geographic place to which the page is related.
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
+
<meta name="geo.placename" content="London, Ontario">
 +
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| go-import
+
| geo.position
| Defines a remote source code location and version control scheme for the Go programming language's toolchain. Content format: <code>import-prefix vcs repo-root</code>.
+
| Geographic position to which the page is related.
| [http://golang.org/cmd/go/#hdr-Remote_import_path_syntax go tool documentation]
+
<meta name="geo.position" content="48.02682000000001;7.809769999999958">
|  
+
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]
 +
| icbm (different value syntax)
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| google
+
| geo.region
| Used to declare text that should not be translated by the Google Translate plugin <meta name="google" value="notranslate"> will declare the whole page should not be translated. <span class="notranslate"> is for text or paragraph areas you wish to not be translated.
+
| Superseded by either geo.country alone or geo.country plus geo.a1. Name of geographic region to which the page is related. Content is specified by ISO-3166.
| [http://googlewebmastercentral.blogspot.com/2007/12/answering-more-popular-picks-meta-tags.html Google blog post]
+
<meta name="geo.region" content="DE-BW">
 +
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]<br>[http://en.wikipedia.org/wiki/ISO_3166 ISO-3166]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| google-site-verification
+
| globrix.bathrooms
| Used to verify ownership for Webmaster Tools.
+
| Globrix property information: Number of bathrooms the property has
| [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=79812 Google documentation]
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| googlebot
+
| globrix.bedrooms
| Synonym of <code>robots</code> for targeting Googlebot only.
+
| Globrix property information: Number of bedrooms the property has
| [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=93710 Google documentation]
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
 
|  
 
|  
|Proposal
+
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| googlebot-mobile
+
| globrix.condition
| Synonym of <code>robots</code> for targeting Googlebot-Mobile
+
| Globrix property information: Condition of the property e.g. 'renovated'
| [https://developers.google.com/webmasters/smartphone-sites/googlebot-mobile]
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
|
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| gwt:property
+
| globrix.features
| Used to specify the locale client property
+
| Globrix property information: Features of the property e.g. 'double glazing'
| [https://developers.google.com/web-toolkit/doc/latest/DevGuideI18nLocale Locales in GWT]
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| handheldfriendly
+
| globrix.instruction
| Informs the BlackBerry browser that the content contained within the document is designed for small screens.
+
| Globrix property information: Property to Buy or Rent
| [http://docs.blackberry.com/en/developers/deliverables/6176/HTML_ref_meta_564143_11.jsp BlackBerry browser documentation]
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
|
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| icbm
+
| globrix.latitude
| Defines geographic position to which page is related to. The acronym stands for ICBM Intercontinental Ballistic Missile - an old, humorous allusion to the possible use of such coordinates.<br>Example:
+
| Globrix property information: The latitude of the property
<meta name="ICBM" content="47.0667, 15.4500" />
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
| [http://geourl.org/add.html GeoURL documentation]
+
|  
| geo.position (different value syntax)
 
| Proposal
 
 
 
|-valign="top"
 
| IE_RM_OFF
 
| If set to "true", disables Internet Explorer 11 Reading View button adjacent to address bar when the page is detected to have content suitable for Reading View. This is intended for pages that are not articles and are not intended to be read in IE 11 Reading View.
 
| [http://ie.microsoft.com/testdrive/browser/readingview/ Microsoft: Reading View Guidelines and Information] In the Code tab, at the bottom where Opt Out is read.
 
|
 
 
| Proposal
 
| Proposal
 
  
 
|-valign="top"  
 
|-valign="top"  
| itemsPerPage
+
| globrix.longitude
| Used to identify the number of search results returned per page.
+
| Globrix property information: The longitude of the property
| [http://www.opensearch.org/Specifications/OpenSearch/1.1#Response_metadata_in_HTML.2FXHTML OpenSearch Specification]
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| meta_date
+
| globrix.outsidespace
| The date used to indicate that the Metadata has been prepared and/or reviewed and approved by the Metadata Unit. Its purpose is administrative. (Used by "Autonomy".)
+
| Globrix property information: External features of the property e.g. 'garden'
| [http://www.hc-sc.gc.ca/home-accueil/alt_formats/pacrb-dgapcr/pdf/Metadata_Application_Profile_2009.pdf Health Canada Web Metadata Application Profile March 2009 ]
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
|
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| mobile-agent
+
| globrix.parking
| Specifies the mobile-compatible url of the web page.  Used by mobile browsers and search engines to redirect mobile phone visitors to the proper mobile page. <br>
+
| Globrix property information: Parking available for property e.g. 'parking for 2 cars'
The following properties can be used in the value of the content attribute:<br>url - The mobile-compatible url of the web page.<br>format - The format of the mobile page. An enum of "wml", "xhtml" and "html5".<br>Example:
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
<meta name="mobile-agent" content="format=html5; url=http://3g.sina.com.cn/">
 
| [http://open.shouji.baidu.com/?page=developer&action=pcandmo Baidu Mobile SEO]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| mobile-web-app-capable
+
| globrix.period
| Sets whether a web application can be added standalone to a home screen and launched in fullscreen mode. Also proposed as a vendor-neutral version of apple-mobile-web-app-capable.
+
| Globrix property information: Period of the property e.g. 'victorian terrace'
| [https://developers.google.com/chrome/mobile/docs/installtohomescreen Add to Homescreen - Google Chrome Mobile &mdash; Google Developers] (though a WHATWG or W3C spec would be preferred)
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
| apple-mobile-web-app-capable (vendor specific synonym)
+
|
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| mobileoptimized
+
| globrix.poa
| Controls layout behavior in older versions of Internet Explorer (e.g., 6.5).
+
| Globrix property information: If the property price is only available on application
| [http://msdn.microsoft.com/en-us/library/bb431690.aspx Microsoft Windows Mobile 6.5 documentation]
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
 
|  
 
|  
 
| Proposal
 
| Proposal
|-valign="top"
+
 
| msapplication-notification
+
|-valign="top"  
| '''"Pinned Sites" and "Live Tiles" in Windows 8.1'''
+
| globrix.postcode
Used to make pinned sites on the start screen into live tiles. Usage:
+
| Globrix property information: Postcode of the property
<META name="msapplication-notification" content="cycle=7;frequency=60;polling-uri=http://www.example.com/notifications.xml"  />
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
| [https://msdn.microsoft.com/en-us/library/ie/dn255024.aspx#msapplication-notification Pinned site metadata reference]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
|-valign="top"
+
 
| msapplication-starturl
+
|-valign="top"  
| '''"Jump List" or "Pinned Sites" in Windows 7'''
+
| globrix.price
The "msapplication-starturl" metadata contains the root URL of the application. The start URL can be fully qualified, or relative to the current document. Only HTTP and HTTPS protocols are allowed. If this element is missing, the address of the current page is used instead.
+
| Globrix property information: Price for the property
<meta name="msapplication-starturl" content="./" />
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
| [http://msdn.microsoft.com/en-us/library/gg491732(v=VS.85).aspx Declaring Pinned Site Metadata]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
|-valign="top"
+
 
| msapplication-task
+
|-valign="top"  
| '''"Jump List" or "Pinned Sites" in Windows 7'''
+
| globrix.priceproximity
Jump List items act as entry points into the website even when the browser is not running. A Jump List can contain commonly used destinations and tasks. Some items apply to the whole site, and some apply only to specific users.  
+
| Globrix property information: The region of the attached price e.g. 'guide price of'
For example, to add a single task called "Check Order Status" specify a meta element in the head of your webpage, as follows:
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
<META name="msapplication-task" content="name=Check Order Status;
 
      action-uri=./orderStatus.aspx?src=IE9;
 
      icon-uri=./favicon.ico"  />
 
| [http://msdn.microsoft.com/en-us/library/gg491725(v=vs.85).aspx Tasks in Jump List]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| msapplication-tooltip
+
| globrix.tenure
| '''"Jump List" or "Pinned Sites" in Windows 7'''
+
| Globrix property information: The tenure of the property e.g. 'leasehold'
The "msapplication-tooltip" metadata provides additional tooltip text that appears when you hover over the Pinned Site shortcut in the Windows Start menu or on the desktop.
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
<meta name="msapplication-tooltip" content="Channel 9 Podcasts" />
 
| [http://msdn.microsoft.com/en-us/library/gg491732(v=VS.85).aspx Declaring Pinned Site Metadata]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| msapplication-tap-highlight
+
| globrix.type
| '''Link highlighting in Internet Explorer'''
+
| Globrix property information: Type of property e.g. 'semi-detatched house'
The "msapplication-tap-highlight" meta tag can be used to disable automatic highlighting of tapped links in Internet Explorer. Applies to IE10 on Windows Phone 8 and IE11 on Windows 8.1.
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
<meta name="msapplication-tap-highlight" content="no" />
 
| [http://msdn.microsoft.com/en-us/library/ie/bg182645%28v=vs.85%29.aspx#tapHighlight Link highlighting]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| msapplication-navbutton-color
+
| globrix.underoffer
| '''"Jump List" or "Pinned Sites" in Windows 7'''
+
| Globrix property information: Indicates if the property is under offer
The "msapplication-navbutton-color" metadata define the custom color of the Back and Forward buttons in the Pinned Site browser window. Any named color, or hex color value is valid.
+
| [http://content.globrix.com/web-tools/8-technical-guide/74-what-are-globrix-meta-tags-and-how-can-i-use-them FAQ About the Globrix meta tags.]
<meta name="msapplication-navbutton-color" content="#FF3300" />
 
| [http://msdn.microsoft.com/en-us/library/gg491732(v=VS.85).aspx Declaring Pinned Site Metadata]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| msapplication-window
+
| go-import
| '''"Jump List" or "Pinned Sites" in Windows 7'''
+
| Defines a remote source code location and version control scheme for the Go programming language's toolchain. Content format: <code>import-prefix vcs repo-root</code>.
The "msapplication-window" metadata sets the initial size of the Pinned Site window when it is launched for the first time. However, if the user adjusts the size of the window, the Pinned Site retains the new dimensions when it is launched again.
+
| [http://golang.org/cmd/go/#hdr-Remote_import_path_syntax go tool documentation]
The following properties can be used in the value of the <code>content</code> attribute:
 
* width - The window width in pixels. The minimum value is 800.
 
* height - The window height in pixels. The minimum value is 600.
 
<meta name="msapplication-window" content="width=1024;height=768" />
 
| [http://msdn.microsoft.com/en-us/library/gg491732(v=VS.85).aspx Declaring Pinned Site Metadata]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| msapplication-config
+
| google
| '''"Pinned Sites" in Windows 8'''
+
| Multiple purposes:<br /><br />Used to declare text that should not be translated by the Google Translate plugin (&lt;meta name="google" value="notranslate"&gt; will declare the whole page should not be translated, while &lt;span class="notranslate"&gt; is for text or paragraph areas you wish to not be translated.<br /><br />Used "[t]o tell Google not to show a Sitelinks search box when your site appears in the search results" (implement with content="nositelinkssearchbox") (already in use).<br /><br />Presumably, multiple meta elements named "google" should all be parsed but this is may not have been explicitly specified anywhere.
The "msapplication-config" metadata defines the path to a browser configuration file, letting you set pinned sites customizations (such as tile background, badge updates and notifications) with this external XML file rather than metadata within the HTML markup of webpages.
+
| "notranslate": [http://googlewebmastercentral.blogspot.com/2007/12/answering-more-popular-picks-meta-tags.html Google blog post]<br /><br />"nositelinkssearchbox": [https://developers.google.com/structured-data/slsb-overview Google on Structured Data &gt; Sitelinks Search Box]
<meta name="msapplication-config" content="IEconfig.xml" />
 
'''Note'''
 
Without this metadata, IE11 looks for a default "browserconfig.xml" in the root directory of the server.
 
| [http://msdn.microsoft.com/en-us/library/ie/dn320426%28v=vs.85%29.aspx Browser configuration schema reference]
 
 
|  
 
|  
| Proposal
+
| Nontranslation: Proposal<br /><br />No Sitelinks search box: Proposed
  
|-valign="top"
+
|-valign="top"  
| msapplication-TileImage
+
| google-play-app
| The "msapplication-TileImage" metadata define the path to an image to be used as background for a tile in Pinned Sites in Windows 8. Tile images must be square PNGs 144px by 144px.
+
| Promoting Apps with Smart App Banners
<meta name="msapplication-TileImage" content="images/benthepcguy-144.png" />
+
| [http://jasny.github.io/jquery.smartbanner/] Smart banners for Google Apps
| [http://blogs.msdn.com/b/ie/archive/2012/06/08/high-quality-visuals-for-pinned-sites-in-windows-8.aspx High Quality Visuals for Pinned Sites in Windows 8]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| msapplication-TileColor
+
| google-site-verification
| The "msapplication-TileColor" metadata define the background color of a tile in Pinned Sites in Windows 8. The tile color can be specified as a hex RGB color using CSS’s #rrggbb notation, via CSS color names, or by the CSS rgb() function.
+
| Used to verify ownership for Webmaster Tools.
<meta name="msapplication-TileColor" content="#d83434"/>
+
| [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=79812 Google documentation]
| [http://blogs.msdn.com/b/ie/archive/2012/06/08/high-quality-visuals-for-pinned-sites-in-windows-8.aspx High Quality Visuals for Pinned Sites in Windows 8]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| msapplication-square70x70logo
+
| gwt:property
| '''msapplication-square70x70logo'''
+
| Used to specify the locale client property
Specifies the image to use as the small tile, which is 70x70 pixels at 100% scaling.
+
| [https://developers.google.com/web-toolkit/doc/latest/DevGuideI18nLocale Locales in GWT]
<meta name="msapplication-square70x70logo" content="images/tinylogo.png">
 
'''Note'''  The '''msapplication-square70x70logo''' value is supported as of IE11 Preview and applies to tiles pinned to the Windows Start screen.
 
| [http://msdn.microsoft.com/en-us/library/ie/dn255024%28v=vs.85%29.aspx Pinned site metadata reference]
 
 
|  
 
|  
 +
| Proposal
 +
 +
|-valign="top"
 +
| handheldfriendly
 +
| Informs the BlackBerry browser that the content contained within the document is designed for small screens.
 +
| [https://developer.blackberry.com/html5/documentation/v1_0/handheldfriendly.html BlackBerry (handheldfriendly "largely obsolete")]
 +
|
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| msapplication-square150x150logo
+
| icas.datetime
| '''msapplication-square150x150logo'''
+
| A point or period of time associated with an event in the lifecycle of the resource represented in terms of an ICAS date and time format of unspecified information density (may include full, long, medium, short, or compressed forms).
Specifies the image to use as the wide tile, which is 310x150 pixels at 100% scaling.
+
| a preliminary specification in the aaticas group on LinkedIn (http://www.linkedin.com/groups/aaticas-4034149). after a period of review, a specification for AAT ICAS meta keywords for HTML(5) will be referenced on an AAT ICAS area of the aatideas.org web site.
<meta name="msapplication-square150x150logo" content="images/logo.png">
+
|
'''Note'''  The '''msapplication-square150x150logo''' value is supported as of IE11 Preview and applies to tiles pinned to the Windows Start screen.
 
| [http://msdn.microsoft.com/en-us/library/ie/dn255024%28v=vs.85%29.aspx Pinned site metadata reference]
 
|  
 
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| msapplication-wide310x150logo
+
| icas.datetime.abbr
| '''msapplication-wide310x150logo'''
+
| A point or period of time associated with an event in the lifecycle of the resource represented in terms of an ICAS abbreviated format such as "d2M03 t969".
Specifies the image to use as the medium tile, which is 150x150 pixels at 100% scaling.
+
| a preliminary specification in the aaticas group on LinkedIn (http://www.linkedin.com/groups/aaticas-4034149). after a period of review, a specification for AAT ICAS meta keywords for HTML(5) will be referenced on an AAT ICAS area of the aatideas.org web site.
<meta name="msapplication-wide310x150logo" content="images/widelogo.png">
+
|
'''Note'''  The '''msapplication-wide310x150logo''' value is supported as of IE11 Preview and applies to tiles pinned to the Windows Start screen.
 
| [http://msdn.microsoft.com/en-us/library/ie/dn255024%28v=vs.85%29.aspx Pinned site metadata reference]
 
|  
 
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| msapplication-square310x310logo
+
| icas.datetime.day
| '''msapplication-square310x310logo'''
+
| A point or period of time associated with an event in the lifecycle of the resource represented in terms of ICAS day-of-year format such as "2012 day 333 t969".
Specifies the image to use as the large tile, which is 310x310 pixels at 100% scaling.
+
| a preliminary specification in the aaticas group on LinkedIn (http://www.linkedin.com/groups/aaticas-4034149). after a period of review, a specification for AAT ICAS meta keywords for HTML(5) will be referenced on an AAT ICAS area of the aatideas.org web site.
<meta name="msapplication-square310x310logo" content="images/largelogo.png">
+
|
'''Note'''  The '''msapplication-square310x310logo''' value is supported as of IE11 Preview and applies to tiles pinned to the Windows Start screen.
 
| [http://msdn.microsoft.com/en-us/library/ie/dn255024%28v=vs.85%29.aspx Pinned site metadata reference]
 
|  
 
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| msvalidate.01
+
| icas.datetime.long
| One of the verification elements used by Bing.
+
| A point or period of time associated with an event in the lifecycle of the resource represented in terms of ICAS long date format such as "UCN 12012 M03 Blue ❀ day 333 ❀ IDC zone(UT) t969 tt189". example <meta name="icas.datetime.long" content="UCN 12012 M03 Blue ❀ day 333 ❀ IDC zone(UT) t969 tt189"/>
| [http://onlinehelp.microsoft.com/en-us/bing/hh204490.aspx Bing Webmaster Tools]
+
| a preliminary specification in the aaticas group on LinkedIn (http://www.linkedin.com/groups/aaticas-4034149). after a period of review, a specification for AAT ICAS meta keywords for HTML(5) will be referenced on an AAT ICAS area of the aatideas.org web site.
|  
+
|
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| norton-safeweb-site-verification
+
| icbm
| Used to verify ownership of Website for Norton SafeWeb.
+
| Defines geographic position to which page is related to. The acronym stands for ICBM Intercontinental Ballistic Missile - an old, humorous allusion to the possible use of such coordinates.<br>Example:
| [http://safeweb.norton.com/help/site_owners#verification_tips Norton SafeWeb Help Documentation]
+
<meta name="ICBM" content="47.0667, 15.4500" />
 +
| [http://geourl.org/add.html GeoURL documentation]
 +
| geo.position (different value syntax)
 +
| Proposal
 +
 
 +
|-valign="top"
 +
| IE_RM_OFF
 +
| If set to "true", disables Internet Explorer 11 Reading View button adjacent to address bar when the page is detected to have content suitable for Reading View. This is intended for pages that are not articles and are not intended to be read in IE 11 Reading View.
 +
| [http://ie.microsoft.com/testdrive/browser/readingview/ Microsoft: Reading View Guidelines and Information] In the Code tab, at the bottom where Opt Out is read.
 +
|
 +
| Proposal
 +
 
 +
 
 +
|-valign="top"
 +
| itemsPerPage
 +
| Used to identify the number of search results returned per page.
 +
| [http://www.opensearch.org/Specifications/OpenSearch/1.1#Response_metadata_in_HTML.2FXHTML OpenSearch Specification]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| p:domain_verify
+
| keywords-not
| Used to register a site's domain with Pinterest as a "verified domain".
+
| Like keywords but instead keywords-not support Boolean NOT searches; useful for metaphors, satire/parody, and pages that say "this page is not about subject x" which therefore would be erroneously excluded by a NOT search against x.
Example:
+
| [http://brittlebit.org/specifications/html-meta-keywords-not/specification-for-html-meta-element-with-name-value-keywords-not.html BrittleBit.org spec]
  <code><meta name="p:domain_verify" content="5dd1c5f2db0ac0b521f08d56b4cd271b"></code>
 
| [https://help.pinterest.com/entries/22488487-Verify-with-HTML-meta-tags Pinterest Help Article]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| pingdom
+
| meta_date
| Used by Pingdom monitoring services as a heartbeat verification. The heartbeat service will only consider the request successful if it contains the "pingdom" meta tag, with the content set according to a per-customer key.
+
| The date used to indicate that the Metadata has been prepared and/or reviewed and approved by the Metadata Unit. Its purpose is administrative. (Used by "Autonomy".)
Example:
+
| [http://www.hc-sc.gc.ca/home-accueil/alt_formats/pacrb-dgapcr/pdf/Metadata_Application_Profile_2009.pdf Health Canada Web Metadata Application Profile March 2009 ]
<code><meta name="pingdom" content="6bh3nxnx"/></code>
 
 
|
 
|
|
 
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| pinterest
+
| microtip
| Used to block pinterest from linking to content on the URL.
+
| Specifies the cryptocurrency address (bitcoin, etc.) for sending tips to the people responsible for creating this page's content. This tag is used by various browser plugins that want to compensate the site's creators. Since it's microtipping instead of micropayments, there is no need to specify an amount.<br>
 
Example:
 
Example:
  <code><meta name="pinterest" content="nopin"/></code>
+
  <meta name="microtip" content="[bitcoin-address]">
| [https://support.pinterest.com/entries/21101932-what-if-i-don-t-want-images-from-my-site-to-be-pinned Pinterest Help Article]
+
Note: there can be multiple instances of this metatag on a page.
 +
| For full specification, see: http://autotip.io/docs/microtip-meta-tag
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| rating
+
| mobile-agent
| The Restricted to Adults label (RTA) provides a way for adult oriented websites to indicate that their content is off limits to children. RTA was introduced in 2006 and is currently used by a large number of adult web content providers. RTA is recognized by all major parental control filters.
+
| Specifies the mobile-compatible url of the web page.  Used by mobile browsers and search engines to redirect mobile phone visitors to the proper mobile page. <br>
Example:
+
The following properties can be used in the value of the content attribute:<br>url - The mobile-compatible url of the web page.<br>format - The format of the mobile page. An enum of "wml", "xhtml" and "html5".<br>Example:
  <meta name="RATING" content="RTA-5042-1996-1400-1577-RTA" />
+
  <meta name="mobile-agent" content="format=html5; url=http://3g.sina.com.cn/">
| [http://www.rtalabel.org/index.php?content=howto RTA documentation]
+
| [http://open.shouji.baidu.com/?page=developer&action=pcandmo Baidu Mobile SEO]
|
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| referrer
+
| mobile-web-app-capable
| Controls whether the user agent includes the Referer header in HTTP requests originating from this document
+
| Sets whether a web application can be added standalone to a home screen and launched in fullscreen mode. Also proposed as a vendor-neutral version of apple-mobile-web-app-capable.
| [http://wiki.whatwg.org/wiki/Meta_referrer Meta referrer]
+
| [https://developers.google.com/chrome/mobile/docs/installtohomescreen Add to Homescreen - Google Chrome Mobile &mdash; Google Developers] (though a WHATWG or W3C spec would be preferred)
|
+
| apple-mobile-web-app-capable (vendor specific synonym)
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| RepostUsAPIKey
+
| mobileoptimized
| Used to verify ownership of Website for Repost syndication service
+
| Controls layout behavior in older versions of Internet Explorer (e.g., 6.5).
| [http://www.repost.us/meta-headers-used-by-repost/ Meta Headers used by Repost]
+
| [http://msdn.microsoft.com/en-us/library/bb431690.aspx Microsoft Windows Mobile 6.5 documentation]
|
+
|  
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| ResourceLoaderDynamicStyles
+
| msapplication-config
| [[mw:|MediaWiki]]'s [[mw:ResourceLoader|ResourceLoader]] uses this name with <code>content</code> set to the empty string.  The purpose is to mark the DOM position before which dynamic styles should be added.
+
| '''"Pinned Sites" in Windows 8'''
| [[mw:ResourceLoader/ResourceLoaderDynamicStyles specification|ResourceLoaderDynamicStyles]]
+
The "msapplication-config" metadata defines the path to a browser configuration file, letting you set pinned sites customizations (such as tile background, badge updates and notifications) with this external XML file rather than metadata within the HTML markup of webpages.
|
+
<meta name="msapplication-config" content="IEconfig.xml" />
| Proposal
+
'''Note'''
|-valign="top"  
+
Without this metadata, IE11 looks for a default "browserconfig.xml" in the root directory of the server.
 
+
| [http://msdn.microsoft.com/en-us/library/ie/dn320426%28v=vs.85%29.aspx Browser configuration schema reference]
| review_date
+
|  
| The date a resource is scheduled for review by content creator in order to determine if it should be archived, updated or retained as is.
 
| [http://www.hc-sc.gc.ca/home-accueil/alt_formats/pacrb-dgapcr/pdf/Metadata_Application_Profile_2009.pdf Health Canada Web Metadata Application Profile March 2009 ]
 
[http://lists.w3.org/Archives/Public/www-archive/2014Feb/att-0020/dnd_ims-6001-1-2-eng.pdf IMS 6001-1-2, Metadata for Recordkeeping and Web Content]
 
|
 
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| revision
+
| msapplication-navbutton-color
| The revision of this page as reported by an underlying Version Control System. This is a free format string.
+
| '''"Jump List" or "Pinned Sites" in Windows 7'''
| [https://github.com/krallin/meta-revision Meta Revision Specification]
+
The "msapplication-navbutton-color" metadata define the custom color of the Back and Forward buttons in the Pinned Site browser window. Any named color, or hex color value is valid.
|
+
<meta name="msapplication-navbutton-color" content="#FF3300" />
 +
| [http://msdn.microsoft.com/en-us/library/gg491732(v=VS.85).aspx Declaring Pinned Site Metadata]
 +
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| revisit-after
+
| msapplication-notification
| revisit-after is used to tell search engines how often to recrawl the page. To our knowledge only one search engine has ever supported it, and that search engine was never widely used — at this point, it is nothing more than a good luck charm.
+
| '''"Pinned Sites" and "Live Tiles" in Windows 8.1'''
| [http://code.google.com/webstats/2005-12/metadata.html Google documentation]
+
Used to make pinned sites on the start screen into live tiles. Usage:
 +
<META name="msapplication-notification" content="cycle=7;frequency=60;polling-uri=http://www.example.com/notifications.xml"  />
 +
| [https://msdn.microsoft.com/en-us/library/ie/dn255024.aspx#msapplication-notification Pinned site metadata reference]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| rights-standard
+
| msapplication-square150x150logo
| The purpose is to enable search engines and other cataloging services to compile the types of rights allocated to the work. (Does any search engine actually implement this? [[User:Hsivonen|hsivonen]] 07:34, 14 July 2011 (UTC))
+
| '''msapplication-square150x150logo'''
 +
Specifies the image to use as the wide tile, which is 310x150 pixels at 100% scaling.
 +
<meta name="msapplication-square150x150logo" content="images/logo.png">
 +
'''Note'''  The '''msapplication-square150x150logo''' value is supported as of IE11 Preview and applies to tiles pinned to the Windows Start screen.
 +
| [http://msdn.microsoft.com/en-us/library/ie/dn255024%28v=vs.85%29.aspx Pinned site metadata reference]
 +
|
 +
| Proposal
  
'''This keyword does not provide, remove or alter any legal protections or designations.'''
+
|-valign="top"
 
+
| msapplication-square310x310logo
Format:
+
| '''msapplication-square310x310logo'''
<pre><meta name="rights-standard" content="element id;rights" /></pre>
+
Specifies the image to use as the large tile, which is 310x310 pixels at 100% scaling.
 
+
<meta name="msapplication-square310x310logo" content="images/largelogo.png">
* element id - the HTML Element ID of the item these rights apply to
+
'''Note''' The '''msapplication-square310x310logo''' value is supported as of IE11 Preview and applies to tiles pinned to the Windows Start screen.
* rights - what rights are assigned to the item
+
| [http://msdn.microsoft.com/en-us/library/ie/dn255024%28v=vs.85%29.aspx Pinned site metadata reference]
** "pd" - Public domain
 
** "cc by-sa" - Creative Commons Attribution
 
** "cc by-nd" - Creative Commons NoDerivs
 
** "cc by-nc" - Creative Commons Attribution-NonCommercial
 
** "cc by-nc-sa" - Creative Commons Attribution-NonCommercial-ShareAlike
 
** "cc by-nc-nd" - Creative Commons Attribution-NonCommercial-NoDerivs
 
 
 
| [http://sites.google.com/site/metarightsstandard/ Spec]
 
|Redundant with [http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#licensing-works Microdata vocabulary for licensing works].
 
|Proposal
 
 
 
|-valign="top"
 
| robots
 
| A comma-separated list of operators explaining how 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.<br />The content value "NOODP" has been offered elsewhere, so I'm proposing it here. It blocks robots from using [http://www.dmoz.org Open Directory Project] descriptions of a website instead of Web pages' own meta descriptions. It may have been introduced by Microsoft.<br />The content value "NOYDIR" has been offered by Yahoo, so I'm proposing it here. It blocks Yahoo's robot from using the Yahoo directory's descriptions of a website instead of Web pages' own meta descriptions. Whether any other robot supports this is unknown but possibly no other search engine uses Yahoo's directory anyway.
 
| [http://www.robotstxt.org/wc/exclusion.html#meta Robots exclusion protocol], NOODP value: [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=35264 Google], [http://help.yahoo.com/l/us/yahoo/search/indexing/indexing-11.html Yahoo], NOYDIR value: [http://ysearchblog.com/2007/02/28/yahoo-search-support-for-noydir-meta-tags-and-weather-update/ Yahoo], as accessed 4-28-09
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| rpuPlugin
+
| msapplication-square70x70logo
| Version of installed  Repost syndication service plugin
+
| '''msapplication-square70x70logo'''
| [http://www.repost.us/meta-headers-used-by-repost/ Meta Headers used by Repost]
+
Specifies the image to use as the small tile, which is 70x70 pixels at 100% scaling.
|
+
<meta name="msapplication-square70x70logo" content="images/tinylogo.png">
 +
'''Note'''  The '''msapplication-square70x70logo''' value is supported as of IE11 Preview and applies to tiles pinned to the Windows Start screen.
 +
| [http://msdn.microsoft.com/en-us/library/ie/dn255024%28v=vs.85%29.aspx Pinned site metadata reference]
 +
|  
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| rqid
+
| msapplication-starturl
| Request identifier of request that generated this page.
+
| '''"Jump List" or "Pinned Sites" in Windows 7'''
| [http://wiki.whatwg.org/wiki/RequestID RequestID]
+
The "msapplication-starturl" metadata contains the root URL of the application. The start URL can be fully qualified, or relative to the current document. Only HTTP and HTTPS protocols are allowed. If this element is missing, the address of the current page is used instead.
|
+
<meta name="msapplication-starturl" content="./" />
 +
| [http://msdn.microsoft.com/en-us/library/gg491732(v=VS.85).aspx Declaring Pinned Site Metadata]
 +
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| shareaholic:site_name
+
| msapplication-tap-highlight
| The name which should be displayed for the overall site for use with the Shareaholic Content Amplification system
+
| '''Link highlighting in Internet Explorer'''
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
+
The "msapplication-tap-highlight" meta tag can be used to disable automatic highlighting of tapped links in Internet Explorer. Applies to IE10 on Windows Phone 8 and IE11 on Windows 8.1.
|
+
<meta name="msapplication-tap-highlight" content="no" />
 +
| [http://msdn.microsoft.com/en-us/library/ie/bg182645%28v=vs.85%29.aspx#tapHighlight Link highlighting]
 +
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| shareaholic:site_id
+
| msapplication-task
| Shareaholic Site ID for the website for use with the Shareaholic Content Amplification system
+
| '''"Jump List" or "Pinned Sites" in Windows 7'''
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
+
Jump List items act as entry points into the website even when the browser is not running. A Jump List can contain commonly used destinations and tasks. Some items apply to the whole site, and some apply only to specific users.
|
+
For example, to add a single task called "Check Order Status" specify a meta element in the head of your webpage, as follows:
 +
<META name="msapplication-task" content="name=Check Order Status;
 +
      action-uri=./orderStatus.aspx?src=IE9;
 +
      icon-uri=./favicon.ico"  />
 +
| [http://msdn.microsoft.com/en-us/library/gg491725(v=vs.85).aspx Tasks in Jump List]
 +
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| shareaholic:keywords
+
| msapplication-TileColor
| Keywords associated with the content of a webpage for use with the Shareaholic Content Amplification system
+
| The "msapplication-TileColor" metadata define the background color of a tile in Pinned Sites in Windows 8. The tile color can be specified as a hex RGB color using CSS’s #rrggbb notation, via CSS color names, or by the CSS rgb() function.
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
+
<meta name="msapplication-TileColor" content="#d83434"/>
|
+
| [http://blogs.msdn.com/b/ie/archive/2012/06/08/high-quality-visuals-for-pinned-sites-in-windows-8.aspx High Quality Visuals for Pinned Sites in Windows 8]
 +
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| shareaholic:url
+
| msapplication-TileImage
| The canonical URL of your webpage that will be used as its permanent ID for use with the Shareaholic Content Amplification system
+
| The "msapplication-TileImage" metadata define the path to an image to be used as background for a tile in Pinned Sites in Windows 8. Tile images must be square PNGs 144px by 144px.
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
+
<meta name="msapplication-TileImage" content="images/benthepcguy-144.png" />
|
+
| [http://blogs.msdn.com/b/ie/archive/2012/06/08/high-quality-visuals-for-pinned-sites-in-windows-8.aspx High Quality Visuals for Pinned Sites in Windows 8]
 +
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| shareaholic:image
+
| msapplication-tooltip
| An image URL which represents your webpage for use with the Shareaholic Content Amplification system
+
| '''"Jump List" or "Pinned Sites" in Windows 7'''
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
+
The "msapplication-tooltip" metadata provides additional tooltip text that appears when you hover over the Pinned Site shortcut in the Windows Start menu or on the desktop.
|
+
<meta name="msapplication-tooltip" content="Channel 9 Podcasts" />
 +
| [http://msdn.microsoft.com/en-us/library/gg491732(v=VS.85).aspx Declaring Pinned Site Metadata]
 +
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| shareaholic:article_published_time
+
| msapplication-wide310x150logo
| When the article was first published for use with the Shareaholic Content Amplification system
+
| '''msapplication-wide310x150logo'''
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
+
Specifies the image to use as the medium tile, which is 150x150 pixels at 100% scaling.
|
+
<meta name="msapplication-wide310x150logo" content="images/widelogo.png">
 +
'''Note'''  The '''msapplication-wide310x150logo''' value is supported as of IE11 Preview and applies to tiles pinned to the Windows Start screen.
 +
| [http://msdn.microsoft.com/en-us/library/ie/dn255024%28v=vs.85%29.aspx Pinned site metadata reference]
 +
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| shareaholic:article_modified_time
+
| msapplication-window
| When the article was last modified for use with the Shareaholic Content Amplification system
+
| '''"Jump List" or "Pinned Sites" in Windows 7'''
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
+
The "msapplication-window" metadata sets the initial size of the Pinned Site window when it is launched for the first time. However, if the user adjusts the size of the window, the Pinned Site retains the new dimensions when it is launched again.
|
+
The following properties can be used in the value of the <code>content</code> attribute:
 +
* width - The window width in pixels. The minimum value is 800.
 +
* height - The window height in pixels. The minimum value is 600.
 +
<meta name="msapplication-window" content="width=1024;height=768" />
 +
| [http://msdn.microsoft.com/en-us/library/gg491732(v=VS.85).aspx Declaring Pinned Site Metadata]
 +
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| shareaholic:language
+
| MSSmartTagsPreventParsing
| Language of the content of the webpage for use with the Shareaholic Content Amplification system
+
| Prevent a Microsoft browser from adding a certain kind of content to a page because users could be confused into thinking the added content was part of the original page. (It's likely only relatively few copies of the browser, a beta release never finalized, are still in the installed Win base, but the base is so large that even relatively few would still be a significant absolute quantity.)<br /><br />This tag is used by Google: [https://support.google.com/customsearch/answer/2595557?hl=en Custom Search Help: Meta Tags], as accessed 1-8-16. And "<meta content='true' name='MSSmartTagsPreventParsing'/>" appeared (with internal quote marks as singles) in the source code for <[http://googleblog.blogspot.com/2009/04/listening-to-google-health-users.html]>, as accessed 4-27-09.
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
+
| [http://brittlebit.org/specifications/html-meta-mssmarttagspreventparsing/specification-for-html-meta-element-with-name-value-mssmarttagspreventparsing.html BrittleBit.org spec]
|
+
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| shareaholic:article_author_name
+
| msvalidate.01
| Contains the name of the author of the content of the webpage for use with the Shareaholic Content Amplification system
+
| One of the verification elements used by Bing.
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
+
| [http://onlinehelp.microsoft.com/en-us/bing/hh204490.aspx Bing Webmaster Tools]
|
+
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| shareaholic:article_author
+
| nonfiction
| An URL to the profile of the author of the content of the webpage for use with the Shareaholic Content Amplification system
+
| To reduce the "fake news" problem, this lets well-meaning page authors label satire and parody appropriately in metatags although unlabeled in content (not explicitly labeling being common in satire and parody). Characterize the principal content of the page as nonfiction, fiction, mixed, or other. This way, other websites and users needn't be fooled.
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
+
| [http://brittlebit.org/specifications/html-meta-nonfiction/specification-for-html-meta-element-with-name-value-nonfiction.html BrittleBit.org spec]
|
+
| fiction (antonym; see spec for usage)
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| shareaholic:article_visibility
+
| norton-safeweb-site-verification
| Specifies whether a webpage should be publicly recommendable for use with the Shareaholic Content Amplification system
+
| Used to verify ownership of Website for Norton SafeWeb.
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
+
| [http://safeweb.norton.com/help/site_owners#verification_tips Norton SafeWeb Help Documentation]
|
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| shareaholic:shareable_page
+
| origin
| Specifies whether a webpage should be publicly shareable for use with the Shareaholic Content Amplification system
+
| The ''origin'' meta tag is used to indicate the original source of a document.
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
+
| [https://doc.ohreally.nl/metatag-origin The ''origin'' meta tag]
 
|
 
|
 +
| Proposed
 +
 +
|-valign="top"
 +
| origin-trials
 +
| Used to enable experimental browser features for sites which are registered to participate in experimental trials.
 +
| [https://docs.google.com/document/d/1v5fi0EUV_QHckVHVF2K4P72iNywnrJtNhNZ6i2NPt0M/edit?usp=sharing Experimental Framework Trial Token Structure]
 +
|
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| shareaholic:analytics
+
| p:domain_verify
| Enables or disables Shareaholic Analytics for use with the Shareaholic Content Amplification system
+
| Used to register a site's domain with Pinterest as a "verified domain".
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
+
Example:
|
+
  <code><meta name="p:domain_verify" content="5dd1c5f2db0ac0b521f08d56b4cd271b"></code>
 +
| [https://help.pinterest.com/entries/22488487-Verify-with-HTML-meta-tags Pinterest Help Article]
 +
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| shareaholic:wp_version
+
| page-version
| Specifies Shareaholic for WordPress plugin version for use with the Shareaholic Content Amplification system
+
| When a page uploaded two or more times with the same last-modification date (per dc.modified, dcterms.modified, or article:modified_time metatag), distinguishing different uploads even on the same date can be done with the page-version metatag.
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
+
| [http://brittlebit.org/specifications/html-meta-page-version/specification-for-html-meta-element-with-name-value-page-version.html BrittleBit.org spec]
|
+
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| shareaholic:drupal_version
+
| pingdom
| Specifies Shareaholic for Drupal module version for use with the Shareaholic Content Amplification system
+
| Used by Pingdom monitoring services as a heartbeat verification. The heartbeat service will only consider the request successful if it contains the "pingdom" meta tag, with the content set according to a per-customer key.
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
+
Example:
 +
<code><meta name="pingdom" content="6bh3nxnx"/></code>
 
|
 
|
 +
|
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| signet:authors
+
| pinterest
| Authors of a page for use with javascript signet library
+
| Used to block pinterest from linking to content on the URL.
| [https://github.com/HubSpot/signet/blob/master/README.md Signet Revision Specification]
 
|
 
| Proposal
 
 
 
|-valign="top"
 
| signet:links
 
| links to related pages, for use with the javascript signet library
 
| [https://github.com/HubSpot/signet/blob/master/README.md Signet Revision Specification]
 
|
 
| Proposal
 
 
 
|-valign="top"
 
| skype_toolbar
 
| Prevents the Skype browser extension from automatically seeking through the page and replacing telephone numbers (or any number the program's algorithm thinks is a telephone number) with its own custom presentation that allows direct invocation of the Skype program to call the telephone number.
 
 
 
 
Example:
 
Example:
  <meta name="skype_toolbar" content="skype_toolbar_parser_compatible" />
+
  <code><meta name="pinterest" content="nopin"/></code>
| [http://skype.otherlinks.co.uk/page.asp?id=toolbar_number_formatting Skype Info]
+
| [https://support.pinterest.com/entries/21101932-what-if-i-don-t-want-images-from-my-site-to-be-pinned Pinterest Help Article]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| slurp
+
| prism:alternateTitle
| Synonym of <code>robots</code> for targeting Yahoo! only.
+
| An alternate title or alternate headline for a resource that may be used in a table of contents, a popup etc. and can vary with platform.
| [http://help.yahoo.com/l/au/yahoo7/search/indexing/indexing-11.html Yahoo! documentation]
+
| [http://www.prismstandard.org/specifications/3.0/PRISM_Basic_Metadata_3.0.htm PRISM Basic Metadata Specification V3.0]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| startIndex
+
| pro
| Used to identify the index of the first search result in the current set of search results.
+
| Signify expertise as judged by an authority. Counterpart to pro-auth (which see). Useful to search engines and Web directories.
| [http://www.opensearch.org/Specifications/OpenSearch/1.1#Response_metadata_in_HTML.2FXHTML OpenSearch Specification]
+
| [http://brittlebit.org/specifications/html-meta-pro/specification-for-html-meta-element-with-name-value-pro.html BrittleBit.org spec]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| startver
+
| pro-auth
| Used to verify WebApps for JokeNetwork's Start!-WebApp
+
| Signify an authority, subject to search engine's or directory's judgment of importance and credibility (the judgment could be by a human working for a search engine), so the authority's listing of experts can carry weight, making search results more useful.<br /><br />Counterpart to pro (which see). Supported also by pro-auth-field (which see) and pro-auth-fragment (which see).
| [https://jokenetwork.de/faq/start/verification/ JokeNetwork's Start Documentation]
+
| [http://brittlebit.org/specifications/html-meta-pro-auth/specification-for-html-meta-element-with-name-value-pro-auth.html BrittleBit.org spec]
|
 
| proposal
 
 
 
|-valign="top"
 
| teoma
 
| Synonym of <code>robots</code> for targeting Teoma and Ask.com only.
 
| [http://about.ask.com/en/docs/about/webmasters.shtml Ask.com documentation]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| totalResults
+
| pro-auth-field
| Used to identify the number of search results available for the current search.
+
| Signify an authority's claimed field of expertise, importance and validity to be judged by search engine or directory. Supports pro-auth (which see).
| [http://www.opensearch.org/Specifications/OpenSearch/1.1#Response_metadata_in_HTML.2FXHTML OpenSearch Specification]
+
| [http://brittlebit.org/specifications/html-meta-pro-auth-field/specification-for-html-meta-element-with-name-value-pro-auth-field.html BrittleBit.org spec]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| twitter:card
+
| pro-auth-fragment
| The card type, which will be one of "summary", "photo", "app", or "player".
+
| Signify which links from authority are links to experts, as distinct from other links. Supports pro-auth (which see).
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [http://brittlebit.org/specifications/html-meta-pro-auth-fragment/specification-for-html-meta-element-with-name-value-pro-auth-fragment.html BrittleBit.org spec]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:domain
+
| rating
| the domain of the website (added w/ API 1.1)
+
| The Restricted to Adults label (RTA) provides a way for adult oriented websites to indicate that their content is off limits to children. RTA was introduced in 2006 and is currently used by a large number of adult web content providers. RTA is recognized by all major parental control filters.
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
Example:
 +
<meta name="RATING" content="RTA-5042-1996-1400-1577-RTA" />
 +
| [http://www.rtalabel.org/index.php?content=howto RTA documentation]
 
|
 
|
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| twitter:url
+
| referrer
| Canonical URL of the card content.
+
| Controls whether the user agent includes the Referer header in HTTP requests originating from this document
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://www.w3.org/TR/referrer-policy/ Referrer Policy]
|  
+
| referer
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| twitter:title
+
| RepostUsAPIKey
| The title of the content as it should appear in the card.
+
| Used to verify ownership of Website for Repost syndication service
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [http://www.repost.us/meta-headers-used-by-repost/ Meta Headers used by Repost]
|  
+
|
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| twitter:description
+
| ResourceLoaderDynamicStyles
| A description of the content in a maximum of 200 characters.
+
| [[mw:|MediaWiki]]'s [[mw:ResourceLoader|ResourceLoader]] uses this name with <code>content</code> set to the empty string.  The purpose is to mark the DOM position before which dynamic styles should be added.
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [[mw:ResourceLoader/ResourceLoaderDynamicStyles specification|ResourceLoaderDynamicStyles]]
|  
+
|
 
| Proposal
 
| Proposal
 +
|-valign="top"
  
|-valign="top"
+
| review_date
| twitter:app:name:iphone
+
| The date a resource is scheduled for review by content creator in order to determine if it should be archived, updated or retained as is.
| Name of your iPhone app
+
| [http://www.hc-sc.gc.ca/home-accueil/alt_formats/pacrb-dgapcr/pdf/Metadata_Application_Profile_2009.pdf Health Canada Web Metadata Application Profile March 2009 ]
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
[http://lists.w3.org/Archives/Public/www-archive/2014Feb/att-0020/dnd_ims-6001-1-2-eng.pdf IMS 6001-1-2, Metadata for Recordkeeping and Web Content]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:app:name:ipad
+
| revision
| Name of your iPad optimized app
+
| The revision of this page as reported by an underlying Version Control System. This is a free format string.
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/krallin/meta-revision Meta Revision Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:app:name:googleplay
+
| revisit-after
| Name of your Android app
+
| revisit-after is used to tell search engines how often to recrawl the page. To our knowledge only one search engine has ever supported it, and that search engine was never widely used — at this point, it is nothing more than a good luck charm.
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [http://code.google.com/webstats/2005-12/metadata.html Google documentation]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| twitter:app:id:iphone
+
| rights
| String value, should be the numeric representation of your app ID in the App Store.
+
| Assert legal rights for the page in a machine-parsable format. Rights could include those in copyright, for trade secrets, and in other intellectual property.<br /><br/>[[Talk:MetaExtensions#rights:_why_reversion|Talk]]
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [http://brittlebit.org/specifications/html-meta-rights/specification-for-html-meta-element-with-name-value-rights.html BrittleBit.org spec]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:app:id:ipad
+
| rights-standard
| String value, should be the numeric representation of your app ID in the App Store.
+
| The purpose is to enable search engines and other cataloging services to compile the types of rights allocated to the work. (Does any search engine actually implement this? [[User:Hsivonen|hsivonen]] 07:34, 14 July 2011 (UTC))
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
 
|
 
| Proposal
 
  
|-valign="top"
+
'''This keyword does not provide, remove or alter any legal protections or designations.'''
| twitter:app:id:googleplay
 
| String value, and should be the numeric representation of your app ID in Google Play.
 
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
 
|
 
| Proposal
 
  
|-valign="top"  
+
Format:
| twitter:app:url:iphone
+
<pre><meta name="rights-standard" content="element id;rights" /></pre>
| Your app's custom URL scheme.
+
 
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
* element id - the HTML Element ID of the item these rights apply to
|  
+
* rights - what rights are assigned to the item
 +
** "pd" - Public domain
 +
** "cc by-sa" - Creative Commons Attribution
 +
** "cc by-nd" - Creative Commons  NoDerivs
 +
** "cc by-nc" - Creative Commons Attribution-NonCommercial
 +
** "cc by-nc-sa" - Creative Commons Attribution-NonCommercial-ShareAlike
 +
** "cc by-nc-nd" - Creative Commons Attribution-NonCommercial-NoDerivs
 +
 
 +
| [http://sites.google.com/site/metarightsstandard/ Spec]
 +
| Redundant with [http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#licensing-works Microdata vocabulary for licensing works].
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| twitter:app:url:ipad
+
| robots
| Your app's custom URL scheme.
+
| A comma-separated list of operators explaining how 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.<br />The content value "NOODP" has been offered elsewhere, so I'm proposing it here. It blocks robots from using [http://www.dmoz.org Open Directory Project] descriptions of a website instead of Web pages' own meta descriptions. It may have been introduced by Microsoft.<br />The content value "NOYDIR" has been offered by Yahoo, so I'm proposing it here. It blocks Yahoo's robot from using the Yahoo directory's descriptions of a website instead of Web pages' own meta descriptions. Whether any other robot supports this is unknown but possibly no other search engine uses Yahoo's directory anyway.
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [http://www.robotstxt.org/wc/exclusion.html#meta Robots exclusion protocol], NOODP value: [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=35264 Google], [http://help.yahoo.com/l/us/yahoo/search/indexing/indexing-11.html Yahoo], NOYDIR value: [http://ysearchblog.com/2007/02/28/yahoo-search-support-for-noydir-meta-tags-and-weather-update/ Yahoo], as accessed 4-28-09
|  
+
| baiduspider (for targeting Baidu or Baiduspider only)<br />googlebot (for targeting Googlebot only)<br />googlebot-mobile (for targeting Googlebot-Mobile)<br />ia_archive (for targeting Internet Archive (Wayback Machine) or Alexa only)<br />msnbot (for targeting Microsoft or Bing only)<br />slurp (for targeting Yahoo or slurp only)<br />teoma (for targeting TEOMA or Ask.com only)
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| twitter:app:url:googleplay
+
| rpuPlugin
| Your app's custom URL scheme.
+
| Version of installed  Repost syndication service plugin
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [http://www.repost.us/meta-headers-used-by-repost/ Meta Headers used by Repost]
|  
+
|
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| twitter:app:country
+
| rqid
| If your application is not available in the US App Store, you must set this value to the two-letter country code for the App Store that contains your application.
+
| Request identifier of request that generated this page.
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [http://wiki.whatwg.org/wiki/RequestID RequestID]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:image
+
| shareaholic:analytics
| A URL to the image representing the content.
+
| Enables or disables Shareaholic Analytics for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:image:height
+
| shareaholic:article_author
| The height of the image representing the content.
+
| A URL to the profile of the author of the content of the webpage for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:image:src
+
| shareaholic:article_author_name
| URL of image to use in the card. Image must be less than 1MB in size.
+
| Contains the name of the author of the content of the webpage for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:image:width
+
| shareaholic:article_modified_time
| The width of the image representing the content.
+
| When the article was last modified for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:image0
+
| shareaholic:article_published_time
| A URL to the image representing the first photo in your gallery.
+
| When the article was first published for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:image1
+
| shareaholic:article_visibility
| A URL to the image representing the second photo in your gallery.
+
| Specifies whether a webpage should be publicly recommendable for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:image2
+
| shareaholic:drupal_version
| A URL to the image representing the third photo in your gallery.
+
| Specifies Shareaholic for Drupal module version for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:image3
+
| shareaholic:image
| A URL to the image representing the fourth photo in your gallery.
+
| An image URL which represents your webpage for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:site
+
| shareaholic:keywords
| @username for the website used in the card footer.
+
| Keywords associated with the content of a webpage for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:site:id
+
| shareaholic:language
| Twitter ID for the website used in the card footer.
+
| Language of the content of the webpage for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:creator
+
| shareaholic:outstreamads
| @username for the content creator / author.
+
| Enables or disables Shareaholic Outstream Ads for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:creator:id
+
| shareaholic:shareable_page
| Twitter ID for the content creator / author.
+
| Specifies whether a webpage should be publicly shareable for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:data1
+
| shareaholic:site_id
| String value; value for labels such as price, items in stock, sizes, etc
+
| Shareaholic Site ID for the website for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:label1
+
| shareaholic:site_name
| String value; label such as price, items in stock, sizes, etc
+
| The name which should be displayed for the overall site for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:data2
+
| shareaholic:url
| String value; value for labels such as price, items in stock, sizes, etc
+
| The canonical URL of your webpage that will be used as its permanent ID for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:label2
+
| shareaholic:wp_version
| String value; label such as price, items in stock, sizes, etc
+
| Specifies Shareaholic for WordPress plugin version for use with the Shareaholic Content Amplification system
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|  
+
|
 
| Proposal
 
| Proposal
  
|-valign="top"  
+
|-valign="top"
| twitter:player
+
| signet:authors
| HTTPS URL to iframe player. This must be a HTTPS URL which does not generate active mixed content warnings in a web browser
+
| Authors of a page for use with javascript signet library
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://github.com/HubSpot/signet/blob/master/README.md Signet Revision Specification]
|  
+
|
 +
| Proposal
 +
 
 +
|-valign="top"
 +
| signet:links
 +
| links to related pages, for use with the javascript signet library
 +
| [https://github.com/HubSpot/signet/blob/master/README.md Signet Revision Specification]
 +
|
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| twitter:player:width
+
| skype_toolbar
| Width of IFRAME specified in twitter:player in pixels
+
| Prevents the Skype browser extension from automatically seeking through the page and replacing telephone numbers (or any number the program's algorithm thinks is a telephone number) with its own custom presentation that allows direct invocation of the Skype program to call the telephone number.
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
 
 +
Example:
 +
<meta name="skype_toolbar" content="skype_toolbar_parser_compatible" />
 +
| [http://skype.otherlinks.co.uk/page.asp?id=toolbar_number_formatting Skype Info]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| twitter:player:height
+
| startIndex
| Height of IFRAME specified in twitter:player in pixels
+
| Used to identify the index of the first search result in the current set of search results.
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [http://www.opensearch.org/Specifications/OpenSearch/1.1#Response_metadata_in_HTML.2FXHTML OpenSearch Specification]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| twitter:player:stream
+
| startver
| URL to raw stream that will be rendered in Twitter's mobile applications directly
+
| Used to verify WebApps for JokeNetwork's Start!-WebApp
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [https://jokenetwork.de/faq/start/verification/ JokeNetwork's Start Documentation]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| twitter:player:stream:content_type
+
| subject-datetime
| The MIME type/subtype combination that describes the content contained in twitter:player:stream
+
| Identify the principal datetime ranges of the subject of the page’s content, such as the dates of an historical event.
| [https://dev.twitter.com/docs/cards Twitter cards documentation]
+
| [http://brittlebit.org/specifications/html-meta-subject-datetime/specification-for-html-meta-element-with-name-value-subject-datetime.html BrittleBit.org spec]
 +
| page-datetime<br /><br />datetime-coverage<br />datetime-coverage-start<br />datetime-coverage-end<br />datetime-coverage-vague<br />
 +
| Proposal
 +
 
 +
|-valign="top"
 +
| subject-system
 +
| Where another metatag provides a subject for the page, that subject should be selected in accordance with a standard system for classifying subjects, such as one used for academic or public libraries of books. This metatag identifies the system in use for the current page, using a standard controlled vocabulary of system identifiiers.
 +
| [http://brittlebit.org/specifications/html-meta-subject-system/specification-for-html-meta-element-with-name-value-subject-system.html BrittleBit.org spec]
 +
| subj-.&nbsp;.&nbsp;. or subj-* (namespace not approved thus synonym would be "subj-" plus whatever is after hyphen in token)
 +
| Proposal
 +
 
 +
|-valign="top"
 +
| theme-color
 +
| Indicates a color associated with the web site's theme. Web browsers might use this color to theme their UI to be consistent with the web site's color scheme.<br>
 +
Usage: <code><meta name="theme-color" content="papayawhip"></code>
 +
| [https://github.com/whatwg/meta-brand-color Documentation]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| typemetal.formatprefs
+
| thumbnail
| Per-file HTML formatting preferences used by the TypeMetal HTML editor
+
| The full URL of a file that provides a thumbnail for the HTML page.<br /><br />(Note: This violates HTML5, section 4.2.5.2, which says this, because the value is a URL, must be a link element and not a meta element, but Google already recommends and parses this as a meta element.)
| [http://coherencelabs.com/typemetal/manual/typemetal-custom-metadata.html TypeMetal User Guide]
+
| [https://support.google.com/customsearch/answer/1626955?hl=en Google page], as accessed Jan. 2, 2016. Original date unknown.
 
|  
 
|  
| Proposal
+
| Proposed
  
 
|-valign="top"  
 
|-valign="top"  
| verify-v1
+
| topper
| Superseded by google-site-verification. Legacy verification for Google Sitemaps.
+
| Notify website visitors of later changes; easier for website authors to maintain than RSS or Atom.
| [http://sitemaps.blogspot.com/2006/05/more-about-meta-tag-verification.html Inside Google Sitemaps: More about meta tag verification]
+
| [http://brittlebit.org/specifications/html-meta-topper-topper-major-topper-minor/specification-for-html-meta-element-with-name-values-topper-topper-major-and-topper-minor.html BrittleBit.org spec]
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| version
+
| topper-major
| The version of a web application according to the [http://semver.org/ Semantic Versioning] specification<br>
+
| Limit use of topper to major changes.
Example:
+
| [http://brittlebit.org/specifications/html-meta-topper-topper-major-topper-minor/specification-for-html-meta-element-with-name-values-topper-topper-major-and-topper-minor.html BrittleBit.org spec]
<code><meta name="version" content="0.1.0+1"></code>
+
|  
| [https://github.com/dvorapa/meta-version Documentation]
 
| deprecated `page-version` due to backward compatibility
 
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| vfb-version
+
| topper-minor
| Specifies a Visual Form Builder plugin version for Wordpress.
+
| In use of topper, include minor changes.
| [http://wordpress.org/plugins/visual-form-builder/ Visual Form Builder Documentation and specs]
+
| [http://brittlebit.org/specifications/html-meta-topper-topper-major-topper-minor/specification-for-html-meta-element-with-name-values-topper-topper-major-and-topper-minor.html BrittleBit.org spec]
|
+
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| <span id="viewport">viewport</span>
+
| totalResults
| Provides a way for documents to specify (using markup rather than CSS) the size, zoom factor, and orientation of the viewport that is used as the base for the document's [http://www.w3.org/TR/CSS21/visudet.html#containing-block-details initial containing block]. The following properties can be used in the value of the <code>content</code> attribute:
+
| Used to identify the number of search results available for the current search.
* width
+
| [http://www.opensearch.org/Specifications/OpenSearch/1.1#Response_metadata_in_HTML.2FXHTML OpenSearch Specification]
* height
+
|  
* initial-scale
 
* minimum-scale
 
* maximum-scale
 
* user-scalable
 
Examples:
 
<meta name="viewport" content="initial-scale=1.0">
 
<meta name="viewport" content="width=480, initial-scale=2.0, user-scalable=1">
 
| [http://dev.w3.org/csswg/css-device-adapt/#viewport-meta CSS Device Adaptation]
 
|
 
 
| Proposal
 
| Proposal
  
 
|-valign="top"
 
|-valign="top"
| web_author
+
| translator
| Credits the developer(s) responsible for the technical design of a website.
+
| The ''translator'' meta tag is used to give credit to, and provide contact info for, the translator of a document.
| [http://www.metatags.info/meta_name_webauthor Documentation]
+
| [https://doc.ohreally.nl/metatag-translator The ''translator'' meta tag]
| [https://sites.google.com/site/metadesignerspec/ designer] - for visual presentation
+
|
 +
| Proposed
 +
 
 +
|-valign="top"
 +
| twitter:app:country
 +
| If your application is not available in the US App Store, you must set this value to the two-letter country code for the App Store that contains your application.
 +
|
 +
|
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| wot-verification
+
| twitter:app:id:googleplay
| Used to verify ownership of WOT (Web Of Trust)
+
| String value, and should be the numeric representation of your app ID in Google Play.
| [http://www.mywot.com/wiki/Verify_your_website WOT's verify your site wiki page]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| wt.cg_n
+
| twitter:app:id:ipad
| '''Name of the Content Group'''
+
| String value, should be the numeric representation of your app ID in the App Store.
Used to configure the appropriate Webtrends advanced feature. These are just some of the more popular ones. These appear in your META tags.  – showing you the web page, the source (meta tag), the log files entry and the subsequent WT report.
+
|  
Example:
 
<meta name="wt.cg_n" content="My content">
 
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| wt.cg_s
+
| twitter:app:id:iphone
| '''Name of Content Sub-Group'''
+
| String value, should be the numeric representation of your app ID in the App Store.
Used to configure the appropriate Webtrends advanced feature. These are just some of the more popular ones. These appear in your META tags.  – showing you the web page, the source (meta tag), the log files entry and the subsequent WT report.
+
|  
Example:
 
<meta name="wt.cg_s" content="My content">
 
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| WT.si_n
+
| twitter:app:name:googleplay
| '''Scenario analysis parameter - scenario name'''
+
| Name of your Android app
This defines a scenario name for the page or set of pages to be included in the scenario. This in turn produces a funnel type report in Webtrends.
+
|  
Example:
 
<meta name="WT.si_n" content="my_scenario_name">
 
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters].
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| WT.si_p
+
| twitter:app:name:ipad
| '''Scenario analysis parameter - scenario step name'''
+
| Name of your iPad optimized app
This defines a scenario step name for the page or set of pages to be included in the scenario. This in turn produces a funnel type report in Webtrends. It works when paired with metedata tag name WT.si_n.
+
|  
Example:
 
<meta name="WT.si_p" content="my_scenario_step_name">
 
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters].
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| WT.si_x
+
| twitter:app:name:iphone
| '''Scenario analysis parameter - scenario step number'''
+
| Name of your iPhone app
This defines a scenario step number for the page or set of pages to be included in the scenario. This in turn produces a funnel type report in Webtrends. It works when paired with metedata tag name WT.si_n, and as an alternative to Wt.si_p.
+
|  
Example:
 
<meta name="WT.si_x" content="my_scenario_step_number">
 
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters].
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| DCS.dcssta
+
| twitter:app:url:googleplay
| '''Error page parameter'''
+
| Your app's custom URL scheme.
This defines an error code web page so that Webtrends can identify it as a non-success page. Generally used to identify pages that contain 400 and 500 series return codes. As a result, Webtrends excludes these pages from its standard "Pages" report, to instead populate its standard "errors" report.
+
|  
Example:
 
<meta name="DCS.dcssta" content="404">
 
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters].
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| wt.ac
+
| twitter:app:url:ipad
| '''Advertising Click parameter'''
+
| Your app's custom URL scheme.
When a visitor to your site clicks on an ad, that action is referred to as an Ad Click. The following META tag tracks advertising clicks:
+
|
<META NAME="WT.ac" CONTENT="name">
+
|
Defines the name of the advertisement clicked to reach a particular web page. The Ad Click must contain an external redirect back to the client. The redirect needs to include the necessary code to generate a hit to the SDC server. You can designate multiple Advertising Clicks using semicolons.
+
| Proposal
Examples:
 
<a href="file111.html?WT.ac=CONTENT111">
 
<a href="file222.html?WT.ac=CONTENT222">
 
The name of the advertisement clicked to reach a particular web page. To capture this information with DCS, the Advertising Click must contain an external redirect back to the client. The redirect needs to
 
  
include the necessary code to generate a hit to the DCS. The maximum length for each name is 64 bytes.
+
|-valign="top"
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]
+
| twitter:app:url:iphone
 +
| Your app's custom URL scheme.
 +
|
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| wt.ad
+
| twitter:card
| '''Advertising View parameter'''
+
| The card type, which will be one of "summary", "photo", "app", or "player".
Visitors often view advertisements that they do not necessarily click on. You can use On-Site Advertising to determine the number of visitors to your web site who view particular ads. With this feature you can produce advertising reports for each of your clients.
+
|  
If you are selling advertising space on your web site, for example, you can collect traffic statistics to help determine pricing schedules.
 
The following META tag tracks advertising views:
 
<meta name="WT.ad" content="My content">
 
An Ad View occurs when a visitor views a page containing an ad. An ad is a link or graphic that contains an Ad Click parameter in the query portion of it's URL.
 
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| wt.mc_id
+
| twitter:creator
| '''Identifies the ID of the marketing campaign'''
+
| @username for the content creator / author.
To attract new students, a university launches a marketing campaign by sending recruitment email to all graduating high school seniors in a metropolitan area. The email links to a special landing page in the university’s web site, containing the following META tag to track marketing campaigns.
+
|  
Example:
 
<META NAME="WT.mc_id" CONTENT="1X2GG34">
 
You may use this parameter on the URL.
 
Example:
 
<a href="link?WT.mc_id=1X2GG34">
 
The Campaign ID 1X2GG34 represents recruits to be contacted by email
 
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| wt.sv
+
| twitter:creator:id
| '''Tracking Servers parameter'''
+
| Twitter ID for the content creator / author.
If your site is hosted on multiple servers, a server cluster, or a server farm, and you want to evaluate the performance of your load balancer, Webtrends can track page views for each server. To do so, populate the following META tag on all pages on each server:
+
|  
Example:
 
<meta name="WT.sv" content="My Server">
 
Defines the name of the machine that serves the web page. If you have two servers (Server1 and Server2), you would make two copies of the META tag and designate CONTENT=“Server1” for deployment to pages on the first server and CONTENT=“Server2” for deployment to the same pages on the second server.
 
For a server farm, you can extract the value of the built-in server name and dynamically assign it to the
 
META tag using server-side scripting.
 
Example:
 
<meta name="WT.sv" content="Server1">
 
<meta name="WT.sv" content="Server2">
 
An Ad View occurs when a visitor views a page containing an ad. An ad is a link or graphic that contains an Ad Click parameter in the query portion of it's URL.
 
| [https://tagbuilder.webtrends.com/Help/Miscellaneous/AdSearch.aspx?keepThis=true&TB_iframe=true&height=450&width=650 About WT.ad].
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|-valign="top"
+
|-valign="top"  
| wt.ti
+
| twitter:data1
| '''Tracking Page Titles'''
+
| String value; value for labels such as price, items in stock, sizes, etc
You may want to modify a page title before sending it to Webtrends in the following cases:
+
|  
* You are dealing with dynamic content pages identified by URL parameters, and the page title represents the title of the base URL page rather than the dynamic content page.
+
|  
Unless you modify the page titles, all pages have the same title in the reports.
 
* All pages have been assigned the same title, for reasons of style or company policy.
 
Even though URLs are displayed in addition to page title, the entire URL cannot be depended upon to distinguish one page from another.
 
Use server-side scripts to change the title to something that reflects the content of the pages so that you can identify them in reports. Next, pass the customized page titles to Webtrends, using the following META tag:
 
<META NAME="WT.ti" CONTENT="title">
 
Defines the name of the title for this page.
 
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]
 
|  
 
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| y_key
+
| twitter:data2
| Used to verify ownership for Yahoo! Site Explorer
+
| String value; value for labels such as price, items in stock, sizes, etc
| [http://help.yahoo.com/l/us/yahoo/search/siteexplorer/siteexplorer-06.html Yahoo! documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| yandex-verification
+
| twitter:description
| Used to verify ownership for Yandex Webmaster.
+
| A description of the content in a maximum of 200 characters.
| [http://help.yandex.ru/webmaster/?id=995300#995356 Yandex Webmaster ownership verification]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| ZOOMCATEGORY
+
| twitter:domain
| Category of page to be grouped in Wrensoft Zoom Search Engine.
+
| Short URL assigned by Twitter to a website.
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| ZOOMDESCRIPTION
+
| twitter:image
| Alternative page description for Wrensoft Zoom Search Engine.
+
| A URL to the image representing the content.
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| ZOOMIMAGE
+
| twitter:image0
| URL to image to be displayed alongside result in Wrensoft Zoom Search Engine.
+
| A URL to the image representing the first photo in your gallery.
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| ZOOMPAGEBOOST
+
| twitter:image1
| Page boost factor to increase or decrease the relevance of page in Wrensoft Zoom Search Engine.
+
| A URL to the image representing the second photo in your gallery.
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| ZOOMTITLE
+
| twitter:image2
| Alternative page title for Wrensoft Zoom Search Engine.
+
| A URL to the image representing the third photo in your gallery.
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| ZOOMWORDS
+
| twitter:image3
| Additional keywords to be indexed for Wrensoft Zoom Search Engine.
+
| A URL to the image representing the fourth photo in your gallery.
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| witget
+
| twitter:image:height
| Used to verify ownership for Witget.com.
+
| The height of the image representing the content.
Example <meta name="witget" content="XXXXXXXXXXXXXXXXXXXXXX">
+
|  
| [http://support.witget.com/topic/435278-prostaya-ustanovka-skripta/ Witget manual]
 
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| FSDateCreation
+
| twitter:image:src
| Mentions the date when this web page was created
+
| URL of image to use in the card. Image must be less than 1MB in size.
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| FSDatePublish
+
| twitter:image:width
| Mentions the date when this web page was created
+
| The width of the image representing the content.
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| FSFLContent
+
| twitter:label1
| Informs the Publisher tool whether this page contains any content or not. Valid values yes or no
+
| String value; label such as price, items in stock, sizes, etc
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| FSLanguage
+
| twitter:label2
| Language of the content in the page. Example: US English or UK English, etc
+
| String value; label such as price, items in stock, sizes, etc
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| FSOnSitemap
+
| twitter:player
| Whether the page is accessible via the Sitemap link in the firmsite
+
| HTTPS URL to iframe player. This must be a HTTPS URL which does not generate active mixed content warnings in a web browser
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| FSPageDescription
+
| twitter:player:height
| Description of the content of page
+
| Height of IFRAME specified in twitter:player in pixels
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| FSSearchable
+
| twitter:player:stream
| This tag mentions whether a certain page can be searched or not
+
| URL to raw stream that will be rendered in Twitter's mobile applications directly
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| FSWritertoolPageType
+
| twitter:player:stream:content_type
| Page Type of a page in the firmsite. Page Type values help the Publisher toold in page creation
+
| The MIME type/subtype combination that describes the content contained in twitter:player:stream
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| FSSection
+
| twitter:player:width
| Depicts whether a page is a Section Page or simple page. Section pages can have links to other pages
+
| Width of IFRAME specified in twitter:player in pixels
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| FSPageName
+
| twitter:site
| Name of the page within a Findlaw firmsite
+
| @username for the website used in the card footer.
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| FLBlogAuthor
+
| twitter:site:id
| Depicts whether author of the blog is lawfirm or FL author
+
| Twitter ID for the website used in the card footer.
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
+
|  
 
|  
 
|  
 
| Proposal
 
| Proposal
  
|}
+
|-valign="top"
 +
| twitter:title
 +
| The title of the content as it should appear in the card.
 +
|
 +
|
 +
| Proposal
  
== Proposals that don't meet the [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#other-metadata-names requirements] for a registration ==
+
|-valign="top"
 
+
| twitter:url
Note that these proposals can be moved back to the registry table if the problems listed in the rightmost column of this table are addressed.
+
| Canonical URL of the card content.
 
+
|
{| class="wikitable sortable"
+
|  
! Keyword
+
| Proposal
! Brief description
 
! Link to specification
 
! Synonyms
 
! Status
 
! Registration requirement failure
 
  
 
|-valign="top"  
 
|-valign="top"  
| gm-gpx-v
+
| typemetal.formatprefs
| Wordpress Plugin Google Maps GPX Viewer
+
| Per-file HTML formatting preferences used by the TypeMetal HTML editor
| [http://wordpress.org/extend/plugins/google-maps-gpx-viewer/ Google Maps GPX Viewer]
+
| [http://coherencelabs.com/typemetal/manual/typemetal-custom-metadata.html TypeMetal User Guide]
 
|  
 
|  
| Incomplete proposal
+
| Proposal
| Claimed spec link is not a link to a spec
 
  
 
|-valign="top"  
 
|-valign="top"  
| og:title
+
| verify-v1
| Open Graph Protocol by Facebook developers
+
| Superseded by google-site-verification. Legacy verification for Google Sitemaps.
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
+
| [http://sitemaps.blogspot.com/2006/05/more-about-meta-tag-verification.html Inside Google Sitemaps: More about meta tag verification]
 
|  
 
|  
| Incomplete proposal
+
| Proposal
| The spec specifies this to be a value of the property attribute--not a meta keyword
 
  
 
|-valign="top"  
 
|-valign="top"  
| og:type
+
| version
| Open Graph Protocol by Facebook developers
+
| The version of a web application according to the [http://semver.org/ Semantic Versioning] specification<br>
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
+
Example:
|  
+
<code><meta name="version" content="0.1.0+1"></code>
| Incomplete proposal
+
| [https://github.com/dvorapa/meta-version Documentation]
| The spec specifies this to be a value of the property attribute--not a meta keyword
+
| deprecated `page-version` due to backward compatibility
 +
| Proposal
  
|-valign="top"  
+
|-valign="top"
| og:url
+
| vfb-version
| Open Graph Protocol by Facebook developers
+
| Specifies a Visual Form Builder plugin version for Wordpress.
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
+
| [http://wordpress.org/plugins/visual-form-builder/ Visual Form Builder Documentation and specs]
|  
+
|
| Incomplete proposal
+
| Proposal
| The spec specifies this to be a value of the property attribute--not a meta keyword
 
  
 
|-valign="top"  
 
|-valign="top"  
| og:image
+
| <span id="viewport">viewport</span>
| Open Graph Protocol by Facebook developers
+
| Provides a way for documents to specify (using markup rather than CSS) the size, zoom factor, and orientation of the viewport that is used as the base for the document's [http://www.w3.org/TR/CSS21/visudet.html#containing-block-details initial containing block]. The following properties can be used in the value of the <code>content</code> attribute:
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
+
* width
|  
+
* height
| Incomplete proposal
+
* initial-scale
| The spec specifies this to be a value of the property attribute--not a meta keyword
+
* minimum-scale
 +
* maximum-scale
 +
* user-scalable
 +
Examples:
 +
<meta name="viewport" content="initial-scale=1.0">
 +
<meta name="viewport" content="width=480, initial-scale=2.0, user-scalable=1">
 +
| [http://dev.w3.org/csswg/css-device-adapt/#viewport-meta CSS Device Adaptation]
 +
|
 +
| Proposal
 +
 
 +
|-valign="top"
 +
| web_author
 +
| Credits the developer(s) responsible for the technical design of a website.
 +
| [http://www.metatags.info/meta_name_webauthor Documentation]
 +
| [https://sites.google.com/site/metadesignerspec/ designer] - for visual presentation
 +
| Proposal
  
 
|-valign="top"  
 
|-valign="top"  
| og:site_name
+
| witget
| Open Graph Protocol by Facebook developers
+
| Used to verify ownership for Witget.com.
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
+
Example <meta name="witget" content="XXXXXXXXXXXXXXXXXXXXXX">
 +
| [http://support.witget.com/topic/435278-prostaya-ustanovka-skripta/ Witget manual]
 
|  
 
|  
| Incomplete proposal
+
| Proposal
| The spec specifies this to be a value of the property attribute--not a meta keyword
 
  
 
|-valign="top"  
 
|-valign="top"  
| fb:admins
+
| wot-verification
| Open Graph Protocol by Facebook developers
+
| Used to verify ownership of WOT (Web Of Trust)
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
+
| [http://www.mywot.com/wiki/Verify_your_website WOT's verify your site wiki page]
 
|  
 
|  
| Incomplete proposal
+
| Proposal
| The spec specifies this to be a value of the property attribute--not a meta keyword
 
  
|-valign="top"  
+
|-valign="top"
| og:description
+
| wt.ac
| Open Graph Protocol by Facebook developers
+
| '''Advertising Click parameter'''
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
+
When a visitor to your site clicks on an ad, that action is referred to as an Ad Click. The following META tag tracks advertising clicks:
 +
<META NAME="WT.ac" CONTENT="name">
 +
Defines the name of the advertisement clicked to reach a particular web page. The Ad Click must contain an external redirect back to the client. The redirect needs to include the necessary code to generate a hit to the SDC server. You can designate multiple Advertising Clicks using semicolons.
 +
Examples:
 +
<a href="file111.html?WT.ac=CONTENT111">
 +
<a href="file222.html?WT.ac=CONTENT222">
 +
The name of the advertisement clicked to reach a particular web page. To capture this information with DCS, the Advertising Click must contain an external redirect back to the client. The redirect needs to
 +
 
 +
include the necessary code to generate a hit to the DCS. The maximum length for each name is 64 bytes.
 +
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]
 
|  
 
|  
| Incomplete proposal
+
| Proposal
| The spec specifies this to be a value of the property attribute--not a meta keyword
 
  
|-valign="top"  
+
|-valign="top"
| fb:page_id
+
| wt.ad
| Open Graph Protocol by Facebook developers
+
| '''Advertising View parameter'''
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
+
Visitors often view advertisements that they do not necessarily click on. You can use On-Site Advertising to determine the number of visitors to your web site who view particular ads. With this feature you can produce advertising reports for each of your clients.
 +
If you are selling advertising space on your web site, for example, you can collect traffic statistics to help determine pricing schedules.
 +
The following META tag tracks advertising views:
 +
<meta name="WT.ad" content="My content">
 +
An Ad View occurs when a visitor views a page containing an ad. An ad is a link or graphic that contains an Ad Click parameter in the query portion of it's URL.
 +
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]
 
|  
 
|  
| Incomplete proposal
+
| Proposal
| The spec specifies this to be a value of the property attribute--not a meta keyword
 
  
|-valign="top"  
+
|-valign="top"
| audience
+
| wt.cg_n
| To aid search engines in classifying and to aid directory compilers, an audience most appropriate for the page may be suggested. Subject matter may not be a good clue; for example, an analysis of children's literature may be directed to teachers.<br />A value is free-form case-insensitive text without a comma. Multiple values are to be comma-separated. Singular and plural forms have the same meaning.<br />Recognized values:<br />-- "all" and "everyone", which have the same meaning<br />-- "adult" and "mature" have the same meaning and are for content that only adults may access, but no one responsible for preventing a nonadult or the immature from accessing the page or its content should rely on either or both of these values to do so without other means (not the same as "grownup", which see)<br />-- "child" and "juvenile", which have the same meaning<br />-- "teen"<br />-- "grownup" is not identical to "adult" or "mature" in not implying a precise boundary but is approximately any person who may be able to understand and apply the content (e.g., car driving instruction that may be read by a minor not yet old enough to drive a car but who would likely benefit from somewhat early exposure to the instruction)<br />-- "parent" to include guardian and temporary caregiver<br />-- "teacher" to include professor and ad hoc instructor<br />-- "elementary school student" to include any student below high school<br />-- "high school student"<br />-- "elhi" to include any student in elementary school through high school<br />-- "college student" including graduate and professional school<br />-- "business" including management, finance, and prospective customers (this includes e-commerce and investor sites)<br />-- "health" including any health care provider including alternative and ad hoc<br />-- "patient" for any health care recipient<br />-- "lawyer" including judge, paralegal, and jailhouse lawyer<br />-- "law client" for any prospective recipient of a lawyer's service (not usually a social work client) with ''lawyer'' including paralegal and jailhouse lawyer but not necessarily judge<br />-- "craft" for any craftworker including laborer and artisan<br />-- "artist" including musician, actor, dancer, and sculptor and including creator and performer<br />-- "military" including paramilitary<br />-- "news" including any consumer of rapidly-developing news<br />-- "introductory" and "beginner", which have the same meaning<br />-- "intermediate" and "midlevel", which have the same meaning<br />-- "advanced" and "advance", which have the same meaning<br />-- "scholarly" and "scholar", which have the same meaning<br />-- "popular" generally referring to a writing style<br />-- "older" including retiree<br />-- "institution" including from corporation to conspiracy (such as for management advice)<br />-- "government" including agencies and prospective politicians<br />-- values using any integer or single-digit decimal in the form of "grade 8" or "grade 6.4" including to refer to a reading comprehension level (this generally will not exceed 12 and might be meaningless above 20 so higher values may be interpreted as the highest meaningful value)<br />-- "viewers" for when content (such as a movie) is intended almost entirely to be seen rather than read<br />-- "listeners" for when content (such as music) is intended almost entirely to be heard rather than read but not generally including text-to-speech support<br />-- "tts", "text-to-speech", or "text to speech", which three have the same meaning and which are for a page that has substantial support for TTS or that will be readily understood through TTS without need for such support (TTS is often aided by, e.g., pre-resolving pronunciation ambiguities in page coding)<br />-- values using any numbers in the form of "3-6 years old", whether a range or a single-number value<br />-- values using any decade in the form of "born in 1970s"<br />Unrecognized values such as "botanists", "Texans", and "writers who use red ink" may be used but at a risk that a search engine or directory editor will either fail to recognize it or will interpret it in unpredictable ways, or will in the future.<br />Spellings that are erroneous or slightly different from a recognized value may be interpreted by a search engine or directory editor as representing a recognized value.<br />The absence of the keyword defaults to a value of "all" but without overriding another indication arrived at by other means.
+
| '''Name of the Content Group'''
 +
Used to configure the appropriate Webtrends advanced feature. These are just some of the more popular ones. These appear in your META tags.  – showing you the web page, the source (meta tag), the log files entry and the subsequent WT report.
 +
Example:
 +
<meta name="wt.cg_n" content="My content">
 +
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]
 
|  
 
|  
|
+
| Proposal
| Incomplete proposal
 
| Lacks link to a spec
 
  
|-valign="top"  
+
|-valign="top"
| blogcatalog
+
| wt.cg_s
| Used to verify ownership of Blog Catalog.com
+
| '''Name of Content Sub-Group'''
| [http://www.blogcatalog.com/ Blog catalog site]
+
Used to configure the appropriate Webtrends advanced feature. These are just some of the more popular ones. These appear in your META tags.  – showing you the web page, the source (meta tag), the log files entry and the subsequent WT report.
 +
Example:
 +
<meta name="wt.cg_s" content="My content">
 +
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]
 
|  
 
|  
| Incomplete proposal
+
| Proposal
| Claimed spec link is not a link to a spec
 
  
|-valign="top"  
+
|-valign="top"
| bot-. . .
+
| wt.mc_id
| Robot owners, to allow page authors access to robotic capabilities, e.g., to deny them, should prefix "bot-" to the name of their robot, especially for proprietary bots.<br />Example: If a robot were to be named "dullbucklequiz", the name in the meta element would be "bot-dullbucklequiz".<br />The value "bot-" alone represents all bots so prefixed, like a wildcard.<br />Arguably, there's no need for a list here of any specific bots if http://user-agents.org or http://www.botsvsbrowsers.com/ (and perhaps other sites) is reliable.
+
| '''Identifies the ID of the marketing campaign'''
|
+
To attract new students, a university launches a marketing campaign by sending recruitment email to all graduating high school seniors in a metropolitan area. The email links to a special landing page in the university’s web site, containing the following META tag to track marketing campaigns.
|
+
Example:
| Incomplete proposal
+
<META NAME="WT.mc_id" CONTENT="1X2GG34">
| Lacks link to a spec, tries to register a space of names instead of enumerated names
+
You may use this parameter on the URL.
 
+
Example:
|-valign="top"  
+
<a href="link?WT.mc_id=1X2GG34">
| created
+
The Campaign ID 1X2GG34 represents recruits to be contacted by email
| The datetime at which the document was created. The value is an ISO8601 date. The date MUST follow the [http://www.w3.org/TR/NOTE-datetime W3C Profile of ISO 8601] with a granularity of "Complete date:" or finer. The [http://www.bbc.co.uk/guidelines/futuremedia/desed/previousversions/searchmetadata_vs_1_0.shtml#metadata BBC] use this name.
+
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]
 
|  
 
|  
|
+
| Proposal
| Incomplete proposal
 
| Lacks link to a spec
 
  
|-valign="top"  
+
|-valign="top"
| creator
+
| WT.si_n
| The creator is an off-Web or pre-Web creator of a work for which an author authored a Web page, so that the creator and the author may be different people.<br />Searching for one content creator's work requires a standard robot-parsable format for the information. A personal name, institutional name, or other text entry is permissible.<br />One element represents only one creator. Multiple creators are to be represented with multiple tags.<br />Search engines may index by any component of a name, so a content creator need only enter a name once in one first-last or family-given order (e.g., Pat Thunderbird or Thunderbird, Pat, but not requiring both).
+
| '''Scenario analysis parameter - scenario name'''
| [[Talk:MetaExtensions#Re:_Proposed_'creator'_MetaExtension|Talk]]
+
This defines a scenario name for the page or set of pages to be included in the scenario. This in turn produces a funnel type report in Webtrends.
|
+
Example:
| Incomplete proposal
+
<meta name="WT.si_n" content="my_scenario_name">
| Lacks link to a spec
+
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters].
 
 
 
 
|-valign="top"  
 
| msnbot
 
| Synonym of <code>robots</code> for targeting Bing only.
 
 
|  
 
|  
|  
+
| Proposal
| Incomplete proposal
 
| Lacks link to a spec
 
  
|-valign="top"  
+
|-valign="top"
| ia_archive
+
| WT.si_p
| Synonym of <code>robots</code> for targeting Internet Archive and Alexa only.
+
| '''Scenario analysis parameter - scenario step name'''
 +
This defines a scenario step name for the page or set of pages to be included in the scenario. This in turn produces a funnel type report in Webtrends. It works when paired with metedata tag name WT.si_n.
 +
Example:
 +
<meta name="WT.si_p" content="my_scenario_step_name">
 +
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters].
 
|  
 
|  
|  
+
| Proposal
| Incomplete proposal
 
| Lacks link to a spec
 
  
|-valign="top"  
+
|-valign="top"
| datetime-coverage
+
| WT.si_x
| The author may be the best expert on which time frame is most relevant to the content. Leaving that to search engine analysis may be too chancy without search engine optimization, which analysis is difficult to apply by algorithm to, e.g., historical papers that may focus on the 1800s but mention 1731 and 1912 perhaps unimportantly.<br />The value for this keyword is a date or time -- not a range and not vague, for which other keywords are proposed -- in a format in accordance with http://www.w3.org/TR/NOTE-datetime (albeit a note that's at W3C only for discussion). Any of the six levels of granularity in that note are acceptable, such as expressing only a year.<br />Should this keyword appear more than  once, all the values so appearing are determinative. Multiple values are to be expressed with separate meta elements lest the note be revised in the future in a way incompatible with comma-separating a list.
+
| '''Scenario analysis parameter - scenario step number'''
 +
This defines a scenario step number for the page or set of pages to be included in the scenario. This in turn produces a funnel type report in Webtrends. It works when paired with metedata tag name WT.si_n, and as an alternative to Wt.si_p.
 +
Example:
 +
<meta name="WT.si_x" content="my_scenario_step_number">
 +
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters].
 
|  
 
|  
|
+
| Proposal
| Incomplete proposal
 
| Lacks link to a spec
 
  
|-valign="top"  
+
|-valign="top"
| property="og:*"
+
| wt.sv
| Metadata used by the Open Graph protocol (used by Facebook). Note: currently these are defined as: <meta property="og.*" content="x"/>
+
| '''Tracking Servers parameter'''
| [http://developers.facebook.com/docs/opengraph/ FAQ About the Open Graph protocol from Facebook.]
+
If your site is hosted on multiple servers, a server cluster, or a server farm, and you want to evaluate the performance of your load balancer, Webtrends can track page views for each server. To do so, populate the following META tag on all pages on each server:
|  
+
Example:
| Doesn't belong in this registry
+
<meta name="WT.sv" content="My Server">
| Not a value to be used in the <code>name</code> attribute
+
Defines the name of the machine that serves the web page. If you have two servers (Server1 and Server2), you would make two copies of the META tag and designate CONTENT=“Server1” for deployment to pages on the first server and CONTENT=“Server2” for deployment to the same pages on the second server.
 +
For a server farm, you can extract the value of the built-in server name and dynamically assign it to the
 +
META tag using server-side scripting.
 +
Example:
 +
<meta name="WT.sv" content="Server1">
 +
<meta name="WT.sv" content="Server2">
 +
An Ad View occurs when a visitor views a page containing an ad. An ad is a link or graphic that contains an Ad Click parameter in the query portion of it's URL.
 +
| [https://tagbuilder.webtrends.com/Help/Miscellaneous/AdSearch.aspx?keepThis=true&TB_iframe=true&height=450&width=650 About WT.ad].
 +
|  
 +
| Proposal
  
|-valign="top"  
+
|-valign="top"
| datetime-coverage-end
+
| wt.ti
| This is identical to the keyword datetime-coverage except that it represents only the end. If this keyword is used without datetime-coverage-start (also proposed), its value is interpreted as ending a range without a start.<br />Should this keyword appear more than once, all the values so appearing are determinative, in which case each represents the end of a different range assumed to be nonnesting. Example: If four elements happen to be in the order of datetime-coverage-end=1865, datetime-coverage-start=1914, datetime-coverage-end=1918, and datetime-coverage-start=1862, assuming proper formatting, the ranges should be interpreted as 1862-1865 and 1914-1918.
+
| '''Tracking Page Titles'''
 +
You may want to modify a page title before sending it to Webtrends in the following cases:
 +
* You are dealing with dynamic content pages identified by URL parameters, and the page title represents the title of the base URL page rather than the dynamic content page.
 +
Unless you modify the page titles, all pages have the same title in the reports.
 +
* All pages have been assigned the same title, for reasons of style or company policy.
 +
Even though URLs are displayed in addition to page title, the entire URL cannot be depended upon to distinguish one page from another.
 +
Use server-side scripts to change the title to something that reflects the content of the pages so that you can identify them in reports. Next, pass the customized page titles to Webtrends, using the following META tag:
 +
<META NAME="WT.ti" CONTENT="title">
 +
Defines the name of the title for this page.
 +
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]
 
|  
 
|  
|
+
| Proposal
| Incomplete proposal
 
| Lacks link to a spec
 
  
 
|-valign="top"  
 
|-valign="top"  
| datetime-coverage-start
+
| y_key
| This is identical to the keyword datetime-coverage except that it represents only the start. If this keyword is used without datetime-coverage-end (also proposed), its value is interpreted as starting a range without an end.<br />Should this keyword appear more than once, all the values so appearing are determinative, in which case each represents the start of a different range assumed to be nonnesting. Example: If four elements happen to be in the order of datetime-coverage-start=1862, datetime-coverage-start=1914, datetime-coverage-end=1865, and datetime-coverage-end=1918, assuming proper formatting, the ranges should be interpreted as 1862-1865 and 1914-1918.
+
| Used to verify ownership for Yahoo! Site Explorer
 +
| [http://help.yahoo.com/l/us/yahoo/search/siteexplorer/siteexplorer-06.html Yahoo! documentation]
 
|  
 
|  
|
+
| Proposal
| Incomplete proposal
 
| Lacks link to a spec
 
  
 
|-valign="top"  
 
|-valign="top"  
| datetime-coverage-vague
+
| yandex-verification
| This is identical to the keyword datetime-coverage except that its value is not necessarily crisp. This keyword should be used only when datetime-coverage, datetime-coverage-start, and datetime-coverage-end are inappropriate, but there's no ban on using all four. Any text without a comma can be the value (e.g., Pleistocene, 1820s, Tuesdays, or before we were born); multiple values are comma-separated.<br />If this keyword is used with datetime-coverage, datetime-coverage-start, or datetime-coverage-end, the vague value should be exploited along with the value/s for the other keyword/s.<br />Should this keyword appear more than once, all are determinative.
+
| Used to verify ownership for Yandex Webmaster.
 +
| [http://help.yandex.ru/webmaster/?id=995300#995356 Yandex Webmaster ownership verification]
 
|  
 
|  
|
+
| Proposal
| Incomplete proposal
 
| Lacks link to a spec
 
  
 
|-valign="top"  
 
|-valign="top"  
| DC.
+
| ZOOMCATEGORY
| Dublin Core, maintained by Dublin Core MetaData Initiative (DCMI), is an extensive system with some overlap with non-DC names.<br />This reserves all strings that begin with DC and a dot. ''Not true; DC-HTML doesn't use hardwired prefixes, but defines the prefixes using link/@rel="scheme.prefix"''
+
| Category of page to be grouped in Wrensoft Zoom Search Engine.
| [http://www.DublinCore.org DCMI]
+
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
 
|  
 
|  
| Incomplete proposal
+
| Proposal
| Tries to register a space of names instead of enumerated names
 
  
 
|-valign="top"  
 
|-valign="top"  
| dir-content-pointer
+
| ZOOMDESCRIPTION
| When several pages in a directory include main content, a table of contents, an index, and the like, a search engine may be able to organize results more usefully by identifying which is which with a standard vocabulary, helpful when different publishers use different conventions when displaying or printing content.<br />A value is free-form case-insensitive text without a comma and optionally with a trailing number. Multiple values are to be comma-separated (multiple values are appropriate when one document serves multiple purposes). Singular and plural forms have the same meaning.<br />Recognized values, which are pointer types to which numbers may be suffixed, are limited to "start" meaning 'the first page that should be seen by a user' (this may be anywhere in the directory and anywhere within content), "toc" meaning 'table of contents', "intro" including introductions, forewords, prefaces, and tables of figures, "abstract", "main", "bibliography" and "biblio", which have the same meaning, "index" which may mean 'sitemap' or not, "afterword" and "update" which have the same meaning and need not actually update, "credit" meaning 'credits and acknowledgments', and "author bio" meaning 'author's biography', including any information about the author including credentials and contact information. The number suffix may be spaceless or not.<br />When numbers are suffixed, a search engine or directory should arrange like items in numerical order in the results, with unnumbered items following like items that are numbered, e.g., intro 1, intro 2, main 1, main 2, main, main, and so on.<br />Each directory and each subdirectory has its own sequence.
+
| Alternative page description for Wrensoft Zoom Search Engine.
 +
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
 
|  
 
|  
|
+
| Proposal
| Incomplete proposal
 
| Lacks link to a spec
 
  
|-valign="top"
+
|-valign="top"  
|expires
+
| ZOOMIMAGE
|<code>meta name='expires'</code> defines the expiration date of the page. This can be used for web pages in preparation for an upcoming event, e.g. a registration form for an exposition or competition, or other cases with a pre-set date when the document will no longer be valid, e.g. a product offer in a special sale or a support page for a product known not to be supported anymore from a given time onward.
+
| URL to image to be displayed alongside result in Wrensoft Zoom Search Engine.
 +
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
 +
|
 +
| Proposal
  
Search engines should respond to this meta tag in a reasonable way, i.e. by removing the page from their main search results after the expiration date (possibly still returning the result in a special search for expired pages as long as the page exists and is not explicitly excluded via <code>robots.txt</code> or <code>meta name='robots'</code> etc.) or simply by indicating to the user that this result is out-of-date.
+
|-valign="top"  
 
+
| ZOOMPAGEBOOST
The content attribute should define the expiration date in accordance with http://www.w3.org/TR/NOTE-datetime . The meta tag should not be used for pages without expiration date. However, for historical reasons, search engines should also interpret other date formats where possible and should be prepared to find values such as "", "0", "no" and "never". Such non-date values are to be interpreted as no expiration date.
+
| Page boost factor to increase or decrease the relevance of page in Wrensoft Zoom Search Engine.
 
+
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
Correctly formatted example:
 
<code><pre><meta name='expires' content='2012-12-31T23:59Z'></pre></code>
 
 
 
This tag is not to be confused with and has a different meaning than <code>meta http-equiv='expires'.</code>
 
|
 
|
 
| Incomplete proposal
 
| Lacks link to a spec
 
 
 
|-valign="top"  
 
| format-print
 
| This is to allow a user agent to inform an operating system or a printer driver of the preferred print medium, such as the paper size.<br />A value is free-form case-insensitive text without a comma. Multiple values are to be comma-separated (multiple values might be appropriate because standard paper sizes vary around the world). Singular and plural forms have the same meaning.<br />Recognized values are limited to "letter", "A4", "legal", "A5", "B5", "monarch", "envelope 10" meaning size #10, "envelope 6-3-4" meaning size #6 3/4, values with integers and decimals in the form of "8.5 x 11" or "8.5x11" in which spacing of the "x" does not affect meaning, "paper", which means 'paper of the default color (usually white) and weight (usually 20-lb. stock)', "white", "yellow", "pink", "blue", "green", "violet", or "multicolor", which means a medium of the given color or mixed, "letterhead", "p2 letterhead" meaning 'letterhead intended for any page except the first', "watermark" meaning a 'special watermark such as an organization's own', and "plain" meaning 'not preprinted and not letterhead (it may have a paper manufacturer's watermark not related to letterhead)'.<br />Omitting "paper" when another recognized value is given defaults to an implied meaning of 'paper' with the other value; e.g., "letter" means 'letter paper'; the same principle applies to a medium's color (the default being white for paper and colorless for transparency) and plainness or lack thereof (the default being plain).<br />Other values should be proposed before being recognized here. Label sizes should be proposed here for labels that are not on backing sheets that fit one of the recognized values, e.g., labels on narrow rolls. Blueprint paper sizes should be proposed here. Media other than standard paper, such as onion skin, heavier paper, card, and clear or color transparency, should be proposed here.<br />The user agent may, with the user's or user sysadmin's permission (as by a menu-driven default), interpret a value to offer an alternative the user might accept and software and firmware other than the UA may interpret a value to the same end with or without permission, so this keyword is only suggestive; e.g., "letter" may be interpreted as "A4".<br />The absence of the keyword defaults to a value determined by other than the page, e.g., by the printer driver or the user agent.
 
| [[Talk:MetaExtensions#Re:_Proposed_'format-print'_MetaExtension|Talk]]
 
 
|  
 
|  
| Incomplete proposal
+
| Proposal
| Lacks link to a spec
 
  
 
|-valign="top"  
 
|-valign="top"  
| geographic-coverage
+
| ZOOMTITLE
| The author may be the best expert on the geographic relevance of the content. Leaving that to search engine analysis may be too chancy without search engine optimization, which analysis is difficult to apply by algorithm to, e.g., historical papers and epidemiological studies which may mention locales only once.<br />Absence of the keyword defaults to a value of world (not universe), unless the search engine chooses to interpret the page or larger unit for some other value, probably based on other than just contact information given in the website.<br />The value for this keyword is a semicolon-separated list of one or more place-values, the order of which do not matter. One place-value will use commas to separate, in order, an optional standard natural language symbol applicable to the place-value (when omitted the language applicable to the page will control), a place-class, one or more place-subclasses if any, and one or more place name parts (where, e.g., in "Cape Town, South Africa", "Cape Town" is a place name part but "Town" is not). Spaces after semicolons and commas are optional; spaces within place-values are present when required for each place-value (e.g., "Quezon City", not an invented "QuezonCity").<br />To distinguish names that might otherwise be too similar, place-classes, all lower-case and hyphenatably spaceless, include ''outer-space'', ''region'' (on Earth and crossing or larger than a nation, e.g., southern hemisphere, polar region, temperate zone, or Asia), ''intntl-water'' (an 'international water body'), ''intntl-agcy'' ('international agency' or 'international collection', e.g., all U.N. member nations), ''nation'', ''within-nation'' (limited to only one political level down from nation, e.g., state, province, territory, possession, city not included within other political units of a nation, or any comparable unit), ''city'' (including town, village, hamlet, and any comparable political unit below the level of ''within-nation''), ''addr'' (including address, full-length street, building, institution, and neighborhood without political boundaries), ''pol-unit'' (''pol'' abbreviating 'political') (e.g., a place of disputed nationhood), ''hist-pol-unit'' (''hist'' abbreviating 'historical') (e.g., the Roman Empire), ''feature'' (e.g., river), ''num'' (e.g., latitude and longitude or outer-space equivalent in numbers), and ''ethereal'' (including thealogical/theological, fictional including from modern popular entertainment, and ancient secular mythical, but not including that which is asserted to be a state of mind or existence but not a place, such as nirvana). (Example for one hypothetical page: name="geographic-coverage" content="region, sub-Saharan Africa; nation, Panama; city, Panama, Panama; within-nation, Sao Paulo, Brazil; city, Sao Paulo, Sao Paulo, Brazil; within-nation, Mississippi, United States of America; region, Middle East; region, Midwest, United States of America; hist-pol-unit, Northwest Territory, United States of America; feature, river, Indus; outer-space, Indus; ethereal, ultima Thule; ethereal, Heaven; ethereal, Flatland; ethereal, Valhalla; en-US, addr, Hotel Valhalla, Fredrikstad, Norway; es, nation, Espana" (Indus is both a river and a constellation, illustrating the need for place-classes)).<br />Ambiguity of place-values should be avoided despite convenience in coding because search engines may each interpret them as they see fit, e.g., it would be hard for an engine to distinguish New York from New York.<br />For consistency of spelling, several authority lists should be settled upon, with legal, well-known, and disputed names and common abbreviations all being acceptable; but I'm not proposing one here now (relying on IANA's ccTLD list might be too complex to implement and still assure coding consistency, e.g., occasionally ccTLDs can be phased out and off of IANA's list) (a standard vocabulary possibly usable here is the [http://www.getty.edu/research/conducting_research/vocabularies/tgn/index.html Getty Thesaurus of Geographic Names Online], subject to licensing and charset choice); and promulgating authority lists may best be done publicly by search engine managements, who may disagree with each other.<br />Allowing Unicode for non-Roman alphabet-using locales is desirable, but at present that may raise technical problems, including computer security issues, that are not yet readily soluble.
+
| Alternative page title for Wrensoft Zoom Search Engine.
 +
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
 
|  
 
|  
|
+
| Proposal
| Incomplete proposal
 
| Lacks link to a spec
 
  
 
|-valign="top"  
 
|-valign="top"  
| google-translate-customization
+
| ZOOMWORDS
| Used to verify ownership for Website Translator. <meta name="google-translate-customization" content="Your Website Code Goes Here. Generated When Adding The Google Translate Plugin To Your Site" />
+
| Additional keywords to be indexed for Wrensoft Zoom Search Engine.
 +
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
 
|  
 
|  
|
+
| Proposal
| Incomplete proposal
+
 
| Lacks link to a spec
+
|}
 +
 
 +
== Proposals That Don't Meet the [http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html#other-metadata-names Requirements] For a Registration ==
 +
 
 +
Note that these proposals can be moved back to the registry table if the problems listed in the rightmost column of this table are addressed.
 +
 
 +
{| class="wikitable sortable"
 +
! Keyword
 +
! Brief description
 +
! Link to specification
 +
! Synonyms
 +
! Status
 +
! Registration requirement failure
  
 
|-valign="top"  
 
|-valign="top"  
| keywords-not
+
| blogcatalog
| A comma-separated list of negative keywords that distinguish a closely-related theme from this page's true theme, to support Boolean NOT searches often more realistically than visible text can, especially when both themes share the same lexicon.<br />If keywords is no longer a supported name for a meta element, keywords-not is superfluous; however, debate has been revived on whether keywords should be supported or not; see the keywords entry in this Wiki.
+
| Used to verify ownership of Blog Catalog.com
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=6609 W3C Bug 6609]
+
| [http://www.blogcatalog.com/ Blog catalog site]
|
+
|  
 
| Incomplete proposal
 
| Incomplete proposal
| Lacks link to a spec
+
| Claimed spec link is not a link to a spec
  
 
|-valign="top"  
 
|-valign="top"  
| nextgen
+
| bot-. . .
| Used for nextgen gallery plugin in wordpress
+
| Robot owners, to allow page authors access to robotic capabilities, e.g., to deny them, should prefix "bot-" to the name of their robot, especially for proprietary bots.<br />Example: If a robot were to be named "dullbucklequiz", the name in the meta element would be "bot-dullbucklequiz".<br />The value "bot-" alone represents all bots so prefixed, like a wildcard.<br />Arguably, there's no need for a list here of any specific bots if http://user-agents.org or http://www.botsvsbrowsers.com/ (or perhaps another site) is reliable.
| [http://www.alexa.com/faqs/?p=188 Alexa FAQ About this meta attribute Reference]
 
 
|  
 
|  
 +
|
 
| Incomplete proposal
 
| Incomplete proposal
| Unrelated spec link
+
| Lacks link to a spec, tries to register a space of names instead of enumerated names
  
 
|-valign="top"  
 
|-valign="top"  
| page-datetime
+
| created
| Better ranking in search engine results for recency or relevance to an event date would be aided by a standard format robots can parse. Users would save search time by not having to load many pages to find which ones are new or date-relevant.<br />To supply a consistent and known format, the value for this keyword is a date-time expression formed in accordance with http://www.w3.org/TR/NOTE-datetime (albeit a note that's at W3C only for discussion). Any of the six levels of granularity in that note are acceptable, such as expressing only a year.<br />Should this keyword appear more than once, only the first one so appearing is determinative.
+
| The datetime at which the document was created. The value is an ISO8601 date. The date MUST follow the [http://www.w3.org/TR/NOTE-datetime W3C Profile of ISO 8601] with a granularity of "Complete date:" or finer. The [http://www.bbc.co.uk/guidelines/futuremedia/desed/previousversions/searchmetadata_vs_1_0.shtml#metadata BBC] use this name.
|
 
 
|  
 
|  
 +
|
 
| Incomplete proposal
 
| Incomplete proposal
 
| Lacks link to a spec
 
| Lacks link to a spec
  
 
|-valign="top"  
 
|-valign="top"  
| page-version
+
| dir-content-pointer
| Pages may be revised several times daily. While date-time given to a granularity of a fraction of a second would often suffice, when a page has to be approved more than once before posting, any or no such time may be correct (without this keyword, a comment could be necessary but probably not parsable by an engine). In addition, versions regardless of date may show consecutiveness and can replace a date that must be vague. In that case, a version number may be more useful for searches and so a robot-parsable format is needed.<br />The keyword's value is stated in ASCII digits, is any nonnegative base-10 rational number expressed as an integer or a decimal, with any number of decimal places allowed, and may be padded with any number of leading zeros to support extraction for ASCII sorting.<br />Should this keyword appear more than once, only the first one so appearing is determinative.<br />The versions 0 and 0.''n'', with ''n'' being to any number of places, signify beta versions, i.e., drafts, in the tradition of beta software, while versions 1 and higher ordinarily signify final-release versions. After a final-release version is released, a draft of a later version is not given a version number of 0 or 0.''n'', but is numbered higher than the last final-release version. It is suggested to page authors that draft status, if applicable, be shown in the visibly displayed text of the page, rather than that this meta tag be relied upon as the sole notice of draft status, as it may be inadequate notice if alone.<br />To assign a low page-version such as 0.''n'' or 1, the page's URL, if static, may be used as the relevant premise. Thus, if a page is copied or moved to a new URL, the author may choose to restart page-version numbering from 0.''n'' or 1. If a page's URL is dynamic, e.g., if created on the fly from a script, the page author may prefer to use as the relevant premise for assigning a low page-version such as 0.''n'' or 1 the URL of the script or other technology that generates the dynamic-URL page, placing this meta element containing this attribute within the script or other technology, not within the generating page's head element (the generating page's head element may have its own meta element with this attribute describing the generating page). If one page containing the script or other technology that generates another page has more than one means for generating dynamic-URL pages, each means should contain its own meta element with this attribute. Page-version is thus largely independent of the page's date, although both would likely advance roughly in parallel.
+
| '''This is no longer useful. The function is better performed with HTML markup, some of which may be newer than this meta name.'''<br />When several pages in a directory include main content, a table of contents, an index, and the like, a search engine may be able to organize results more usefully by identifying which is which with a standard vocabulary, helpful when different publishers use different conventions when displaying or printing content.<br />A value is free-form case-insensitive text without a comma and optionally with a trailing number. Multiple values are to be comma-separated (multiple values are appropriate when one document serves multiple purposes). Singular and plural forms have the same meaning.<br />Recognized values, which are pointer types to which numbers may be suffixed, are limited to "start" meaning 'the first page that should be seen by a user' (this may be anywhere in the directory and anywhere within content), "toc" meaning 'table of contents', "intro" including introductions, forewords, prefaces, and tables of figures, "abstract", "main", "bibliography" and "biblio", which have the same meaning, "index" which may mean 'sitemap' or not, "afterword" and "update" which have the same meaning and need not actually update, "credit" meaning 'credits and acknowledgments', and "author bio" meaning 'author's biography', including any information about the author including credentials and contact information. The number suffix may be spaceless or not.<br />When numbers are suffixed, a search engine or directory should arrange like items in numerical order in the results, with unnumbered items following like items that are numbered, e.g., intro 1, intro 2, main 1, main 2, main, main, and so on.<br />Each directory and each subdirectory has its own sequence.
|
 
 
|  
 
|  
 +
|
 
| Incomplete proposal
 
| Incomplete proposal
 
| Lacks link to a spec
 
| Lacks link to a spec
  
|-valign="top"  
+
|-valign="top"
| resolutions
+
| expires
| Authoring web sites to use resolution independent images that display beautifully on high-resolution displays should be made as easy as possible for developers and should not require JavaScript to accomplish.
+
| <code>meta name='expires'</code> defines the expiration date of the page. This can be used for web pages in preparation for an upcoming event, e.g. a registration form for an exposition or competition, or other cases with a pre-set date when the document will no longer be valid, e.g. a product offer in a special sale or a support page for a product known not to be supported anymore from a given time onward.
 +
 
 +
Search engines should respond to this meta tag in a reasonable way, i.e. by removing the page from their main search results after the expiration date (possibly still returning the result in a special search for expired pages as long as the page exists and is not explicitly excluded via <code>robots.txt</code> or <code>meta name='robots'</code> etc.) or simply by indicating to the user that this result is out-of-date.
 +
 
 +
The content attribute should define the expiration date in accordance with http://www.w3.org/TR/NOTE-datetime . The meta tag should not be used for pages without expiration date. However, for historical reasons, search engines should also interpret other date formats where possible and should be prepared to find values such as "", "0", "no" and "never". Such non-date values are to be interpreted as no expiration date.
 +
 
 +
Correctly formatted example:
 +
<code><pre><meta name='expires' content='2012-12-31T23:59Z'></pre></code>
 +
 
 +
This tag is not to be confused with and has a different meaning than <code>meta http-equiv='expires'.</code>
 +
|
 +
|
 +
| Incomplete proposal
 +
| Lacks link to a spec
 +
 
 +
|-valign="top"
 +
| fb:admins
 +
| Open Graph Protocol by Facebook developers
 +
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
 +
|
 +
| Incomplete proposal
 +
| The spec specifies this to be a value of the property attribute--not a meta keyword
 +
 
 +
|-valign="top"
 +
| fb:page_id
 +
| Open Graph Protocol by Facebook developers
 +
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
 +
|
 +
| Incomplete proposal
 +
| The spec specifies this to be a value of the property attribute--not a meta keyword
 +
 
 +
|-valign="top"
 +
| gm-gpx-v
 +
| Wordpress Plugin Google Maps GPX Viewer
 +
| [http://wordpress.org/extend/plugins/google-maps-gpx-viewer/ Google Maps GPX Viewer]
 +
|
 +
| Incomplete proposal
 +
| Claimed spec link is not a link to a spec
 +
 
 +
|-valign="top"
 +
| google-translate-customization
 +
| Used to verify ownership for Website Translator. <meta name="google-translate-customization" content="Your Website Code Goes Here. Generated When Adding The Google Translate Plugin To Your Site" />
 +
|
 +
|
 +
| Incomplete proposal
 +
| Lacks link to a spec
 +
 
 +
|-valign="top"
 +
| nextgen
 +
| Used for nextgen gallery plugin in wordpress
 +
| [http://www.alexa.com/faqs/?p=188 Alexa FAQ About this meta attribute Reference]
 +
|
 +
| Incomplete proposal
 +
| Unrelated spec link
 +
 
 +
|-valign="top"
 +
| nibbler-site-verification
 +
| Used to verify ownership of Nibbler site
 +
| [http://nibbler.silktide.com/ Nibbler site]
 +
|
 +
| Incomplete proposal
 +
| Claimed spec link does not link to a spec
 +
 
 +
|-valign="top"
 +
| og:description
 +
| Open Graph Protocol by Facebook developers
 +
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
 +
|
 +
| Incomplete proposal
 +
| The spec specifies this to be a value of the property attribute--not a meta keyword
 +
 
 +
|-valign="top"
 +
| og:image
 +
| Open Graph Protocol by Facebook developers
 +
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
 +
|
 +
| Incomplete proposal
 +
| The spec specifies this to be a value of the property attribute--not a meta keyword
 +
 
 +
|-valign="top"
 +
| og:site_name
 +
| Open Graph Protocol by Facebook developers
 +
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
 +
|
 +
| Incomplete proposal
 +
| The spec specifies this to be a value of the property attribute--not a meta keyword
 +
 
 +
|-valign="top"
 +
| og:title
 +
| Open Graph Protocol by Facebook developers
 +
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
 +
|
 +
| Incomplete proposal
 +
| The spec specifies this to be a value of the property attribute--not a meta keyword
 +
 
 +
|-valign="top"
 +
| og:type
 +
| Open Graph Protocol by Facebook developers
 +
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
 +
|
 +
| Incomplete proposal
 +
| The spec specifies this to be a value of the property attribute--not a meta keyword
 +
 
 +
|-valign="top"
 +
| og:url
 +
| Open Graph Protocol by Facebook developers
 +
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]
 +
|
 +
| Incomplete proposal
 +
| The spec specifies this to be a value of the property attribute--not a meta keyword
 +
 
 +
|-valign="top"
 +
| property="og:*"
 +
| Metadata used by the Open Graph protocol (used by Facebook). Note: currently these are defined as: <meta property="og.*" content="x"/>
 +
| [http://developers.facebook.com/docs/opengraph/ FAQ About the Open Graph protocol from Facebook.]
 +
|
 +
| Doesn't belong in this registry
 +
| Not a value to be used in the <code>name</code> attribute
 +
 
 +
|-valign="top"  
 +
| resolutions
 +
| Authoring web sites to use resolution independent images that display beautifully on high-resolution displays should be made as easy as possible for developers and should not require JavaScript to accomplish.
 +
 
 +
To accomplish this, I propose a new HTML Meta Tag, <code>resolutions</code>, that can be used to specify that high-resolution versions of images linked to from the page are available and that the browser should use them in place of the lower-resolution default images if it detects that a user is using a high-resolution screen. The resolutions meta tag lists the device-pixel ratios supported by images in the page.
 +
 
 +
So, for example…
 +
 
 +
<code><pre><meta name="resolutions" content="2x"></pre></code>
 +
 
 +
… means that the developer is telling the browser that she has created 2x resolution images for the images linked to from the current page and named them with a @2x suffix.
 +
 
 +
To illustrate, if her image tag is as follows…
 +
 
 +
<code><pre><img src="/images/flower.jpg" alt="A flower"></pre></code>
 +
 
 +
… then she has two image files under /images: the low-resolution default (flower.jpg), and a higher-resolution (200%) version named flower@2x.jpg.
 +
 
 +
(This is the same naming convention already used by Apple in its Cocoa Touch framework for automatically loading in higher-resolution versions of images.)
 +
 
 +
Based on the meta tag, if the browser detects that the user is running at a <code>min-device-pixel-ratio</code> of 2.0, it will automatically ask for the 2x version of the image (flower@2x.jpg) instead of the default image as specified in the image tag.
 +
 
 +
Finally, so as not to flood external sites with high-resolution image requests, this functionality would only work for local images specified via relative links.
 +
 
 +
<b>Multiple resolutions</b>
 +
 
 +
The resolutions tag can also contain a list of supported device-pixel ratios so as to support even higher-resolution displays when and if they become available in the future.
 +
 
 +
For example:
 +
 
 +
<code><pre><meta name="resolutions" content="2x, 4x, 8x"></pre></code>
 +
 
 +
In this case, the developer would provide 2x, 4x, and 8x versions of all images. So, in the running example, she would make flower.jpg, flower@2x.jpg, flower@4x.jpg, and flower@8x.jpg.
 +
 
 +
<b>Advantages</b>
 +
 
 +
The advantages of this approach are several:
 +
 
 +
<ol>
 +
    <li>Makes it very simple for developers to support high-resolution displays like the iPhone 4's Retina screen</li>
 +
    <li>Does not require JavaScript</li>
 +
    <li>Does not change the default way that things work (if the meta tag is not specified, the browser simply behaves as it always has).</li>
 +
</ol>
 +
 
 +
| [http://aralbalkan.com/3355 Proposal for native browser support of high-resolution image substitution]
 +
[http://aralbalkan.com/3331 How to make your web content look stunning on the iPhone 4’s new Retina display]
 +
|
 +
| Incomplete proposal
 +
| Lacks link to a spec
 +
 
 +
|}
  
To accomplish this, I propose a new HTML Meta Tag, <code>resolutions</code>, that can be used to specify that high-resolution versions of images linked to from the page are available and that the browser should use them in place of the lower-resolution default images if it detects that a user is using a high-resolution screen. The resolutions meta tag lists the device-pixel ratios supported by images in the page.
+
== Failed Proposals ==
  
So, for example…
+
{| class="wikitable sortable"
 +
! Keyword
 +
! Brief description
 +
! Link to more details
 +
! Synonyms
 +
! Status
  
<code><pre><meta name="resolutions" content="2x"></pre></code>
+
|-valign="top"  
 
+
| cache
… means that the developer is telling the browser that she has created 2x resolution images for the images linked to from the current page and named them with a @2x suffix.  
+
| This doesn't actually work; use HTTP headers instead.<br />Value must be "public", "private", or "no-cache". Intended 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.
 
+
| none
To illustrate, if her image tag is as follows…
+
|  
 
+
| Unendorsed
<code><pre><img src="/images/flower.jpg" alt="A flower"></pre></code>
 
 
 
… then she has two image files under /images: the low-resolution default (flower.jpg), and a higher-resolution (200%) version named flower@2x.jpg.
 
 
 
(This is the same naming convention already used by Apple in its Cocoa Touch framework for automatically loading in higher-resolution versions of images.)
 
 
 
Based on the meta tag, if the browser detects that the user is running at a <code>min-device-pixel-ratio</code> of 2.0, it will automatically ask for the 2x version of the image (flower@2x.jpg) instead of the default image as specified in the image tag.
 
 
 
Finally, so as not to flood external sites with high-resolution image requests, this functionality would only work for local images specified via relative links.
 
 
 
<b>Multiple resolutions</b>
 
 
 
The resolutions tag can also contain a list of supported device-pixel ratios so as to support even higher-resolution displays when and if they become available in the future.
 
 
 
For example:
 
 
 
<code><pre><meta name="resolutions" content="2x, 4x, 8x"></pre></code>
 
 
 
In this case, the developer would provide 2x, 4x, and 8x versions of all images. So, in the running example, she would make flower.jpg, flower@2x.jpg, flower@4x.jpg, and flower@8x.jpg.
 
 
 
<b>Advantages</b>
 
 
 
The advantages of this approach are several:
 
 
 
<ol>
 
    <li>Makes it very simple for developers to support high-resolution displays like the iPhone 4's Retina screen</li>
 
    <li>Does not require JavaScript</li>
 
    <li>Does not change the default way that things work (if the meta tag is not specified, the browser simply behaves as it always has).</li>
 
</ol>
 
 
 
| [http://aralbalkan.com/3355 Proposal for native browser support of high-resolution image substitution]
 
[http://aralbalkan.com/3331 How to make your web content look stunning on the iPhone 4’s new Retina display]
 
|
 
| Incomplete proposal
 
| Lacks link to a spec
 
  
 
|-valign="top"  
 
|-valign="top"  
| rights
+
| DC.
| As a page effectively appears in at least two forms, usually one as interpreted and displayed on a device and the other as source code, arguably intellectual property rights that must be asserted must be asserted in ways understandable in both contexts. For example, &amp;copy; is a raw representation that may legally fail as part of copyright notice to someone seeing source code and not the display, important when someone wants to copy source code for use elsewhere and may rely on a defense of innocent infringement (at least in U.S.). While such assertions can be made in a comment element, it may be helpful to have a tag that search engines can parse and index verbatim.<br />The value may include standard and nonstandard notices, invocations of licenses such as GFDL and ASCAP, and any other information. Content is defined as free-form, leaving the page author discretion for the entry.<br />Statements in one tag may discuss several portions of the page differently, e.g., with different licenses.<br />More than one license may be offered, along with the page's relationship to all.<br />Not all statements need be license grants. A statement may state whom to ask for reprint permission or may reserve all rights, for example.<br />Only one meta tag with this keyword may be present. Page authors must not use more than one. A UA finding multiple such tags on one page must ignore all of them.<br />The copyright symbol that would be generated by its character entity is not recommended for legal notice in source code when the word 'Copyright' may be used instead, because the entity may be read in raw form, but use is up to the page author. The same concept applies to any intellectual property rights symbol for which a suitable alternative is available, such as for trademark or service mark.<br />ASCII text would not suffice when a name or notice legally may have to be in a non-Roman alphabet, but no alternative may yet exist in HTML5.<br />Search engine storage may impose a length limit, but, because of legal consequences, if the value's length exceeds a given limit the search index should retain or interpret none of it but only refer to it.<br />The content string may only be copied verbatim in its full length, referred to, or ignored. It may not be, for example, paraphrased, truncated, interpreted, or classified except in addition to being copied verbatim in its full length.<br />Ignoring shall not void, nullify, or alter any rights stated in such tag.<br />For the synonymy, ''IP'', ''IP-rights'', and ''IP-right'' are not reserved; while the abbreviation ''IP'' 'intellectual property' is common among attorneys in the U.S., page authors will more likely be computerate, and the abbreviation may be wanted for 'Internet Protocol'.
+
| Dublin Core, maintained by Dublin Core MetaData Initiative (DCMI), is an extensive system with some overlap with non-DC names.<br />This reserves all strings that begin with DC and a dot. ''Not true; DC-HTML doesn't use hardwired prefixes, but defines the prefixes using link/@rel="scheme.prefix"''
| [[Talk:MetaExtensions#rights:_why_reversion|Talk]]
+
| [http://www.DublinCore.org DCMI]
|
 
| Incomplete proposal
 
| Lacks link to a spec
 
 
 
|-valign="top"
 
| subj-. . .
 
| To classify by subject a page's content, a standard subject taxonomy that will be recognized by a search engine or directory will help. Because many such high-quality taxonomies exist, only a prefix is proposed. Over time, particular taxonomies, in print or online, may be recognized here and keywords assigned for each.<br />The keyword will be constructed case-insensitively with subkeywords in the form subj-[nationAbbrev]-[taxonomy]-[edition][-optionalSubedition], e.g., subj-US-MeSH-2009online (perhaps). After "subj-", the second subkeyword will identify the nation where the taxonomy is published or offered as an aid in identifying the taxonomy and does not limit the subject coverage; e.g., a taxonomy published in Japan may be ideal for classifying Canadian botany or Peruvian economy.<br />As subject values may vary between editions of one taxonomy, an edition and optionally a subedition is to be identified in the third and optionally the fourth subkeywords. The subedition, if any, is any update or revision occurring between editions, such that a value drawn from that edition and subedition is stable. The means of identifying edition and subedition should be included in the registration of a keyword.<br />Examples of taxonomies from the U.S. include MeSH (medical) and the Library of Congress Subject Headings.<br />The value identifying a subject for a Web page will be drawn from the cited taxonomy's edition and subedition.<br />If the value should have a style to prevent ambiguity in interpretation, that style is to be registered here for that keyword. Multiple values are expressed with multiple meta elements, one value for each, since comma-separation is probably not compatible with all taxonomies.<br />If a value requires case-sensitivity to prevent confusion, the entry here registering the keyword must accommodate that need with the needs of HTML 5 with an appropriate rule. To that end, a proposal to allow case-sensitivity in meta tags under some circumstances has been offered in the W3C bug reporting system.
 
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=6854 W3C Bug 6854]
 
| subject-. . .
 
| Incomplete proposal
 
| Lacks link to a spec, tries to register a space of names instead of enumerated names
 
 
 
 
 
|-valign="top"
 
| nibbler-site-verification
 
| Used to verify ownership of Nibbler site
 
| [http://nibbler.silktide.com/ Nibbler site]
 
|
 
| Incomplete proposal
 
| Claimed spec link does not link to a spec
 
 
 
|-valign="top"
 
| MSSmartTagsPreventParsing
 
| Microsoft introduced into Internet Explorer 6 Beta a feature that some website designers wished to preclude from applying in order to prevent public misunderstanding of their websites. The feature allowed a browser to add information but at a risk that users wouldn't know that it wasn't supplied by the website. This keyword was provided by Microsoft for those of us who wanted it.<br />Its value was "TRUE". Microsoft spelled the keyword with some capitals and the value in all capitals but whether capitalization was required for either is unknown; some opinions vary. Since it need be understood by only one browser, and that one a beta version, full standards compliance should not be assumed, and original case may be required. (This tag is used by Google: "<meta content='true' name='MSSmartTagsPreventParsing'/>" appeared (with internal quote marks as singles) in the source code for <http://googleblog.blogspot.com/2009/04/listening-to-google-health-users.html>, as accessed 4-27-09.)<br />Microsoft has apparently removed this instruction from its website on the ground that the beta version is no longer available and is not supported, but that doesn't assure that some users aren't still using the beta browser, perhaps inadvertently. Therefore, designers may wish to continue using the keyword and value and they are preserved here.
 
| e.g., [http://www.theregister.co.uk/2001/06/25/web_sites_banish_those_winxp/ The Register (U.K.)], [http://cc.uoregon.edu/cnews/summer2001/summer2001.pdf Univ. Oregon (U.S.) (PDF p. 18)], & [http://trillian.mit.edu/~jc/demo/SmartTagsOff.html John Chambers (U.S.) (job résumé near root)], all as accessed 4-19-09
 
|
 
| Incomplete proposal
 
| Lacks spec, potentially never minted by MS as a meta name (as opposed to a http-equiv value), even if minted by Microsoft, abandoned before shipping in any final release of IE
 
 
 
|}
 
 
 
== Failed Proposals ==
 
 
 
{| class="wikitable sortable"
 
! Keyword
 
! Brief description
 
! Link to more details
 
! Synonyms
 
! Status
 
 
 
|-valign="top"
 
| cache
 
| This doesn't actually work; use HTTP headers instead.<br />Value must be "public", "private", or "no-cache". Intended 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.
 
| none
 
 
|  
 
|  
 
| Unendorsed
 
| Unendorsed
Line 2,980: Line 3,158:
 
|}
 
|}
  
== Process ==
 
 
The process for this page is being discussed on the whatwg@whatwg.org mailing list as we speak. Contribute to the discussion!
 
 
http://lists.w3.org/Archives/Public/public-whatwg-archive/2014Jan/0097.html
 
 
[[Category:Registries]]
 
[[Category:Registries]]

Revision as of 07:26, 3 December 2017

This page lists extension values for the name="" attribute of the HTML <meta> element. You may add your own values to this list. We ask that you:

  • Avoid redundancy - if someone has already defined a name that does roughly what you want, please reuse it.
  • Be sure to include all the items outlined in the spec including a link to a specification that specifies the keyword as an HTML meta keyword. If a proposal lacks a specification and a version in a complete specification exists, the latter is to be preferred.
  • Alphabetize by keyword, without regard for case, in any table. Sort nonalphanumerics by ASCII value.
  • Namespaces cannot be reserved. Instead, register individual names (known as enumerated values although you don't have to number them).

Note that URL-valued properties must not be added to this page as meta names but should be registered as rel keywords instead.

Meta Name Extensions

Keyword Brief description Link to specification Synonyms Status
AGLSTERMS.accessibility A statement indicating the accessibility characteristics of the resource. AGLS Metadata Usage Guide Proposal
AGLSTERMS.accessMode Perceptual mode for the resource. AGLS Metadata Usage Guide Proposal
AGLSTERMS.act A specific piece of legislation which requires or drives the creation or provision of the resource. AGLS Metadata Usage Guide Proposal
AGLSTERMS.aggregationLevel The level of aggregation of the described resource - an 'item' or a 'collection'. AGLS Metadata Usage Guide Proposal
AGLSTERMS.allow-search A specific piece of legislation which requires or drives the creation or provision of the resource. AGLS Metadata Usage Guide Proposal
AGLSTERMS.availability How the resource can be obtained or accessed, or contact information. Primarily used for offline resources to provide information on how to obtain physical access to the resource. AGLS Metadata Usage Guide Proposal
AGLSTERMS.case A specific piece of case law which requires or drives the creation or provision of the resource. AGLS Metadata Usage Guide Proposal
AGLSTERMS.category The generic type of the resource being described - a 'service', 'document' or 'agency'. AGLS Metadata Usage Guide Proposal
AGLSTERMS.dateLicensed Date a license was applied or became effective. AGLS Metadata Usage Guide Proposal
AGLSTERMS.documentType The form of the described resource where the value of category is‘document’. Document is used in its widest sense and includes resources such as text, images, sound files and software. AGLS Metadata Usage Guide Proposal
AGLSTERMS.function The business function to which the resource relates. Functions are the major units of activity which organisations pursue in order to meet the mission and goals of the organisation. AGLS Metadata Usage Guide Proposal
AGLSTERMS.isBasedOn A related resource of which the described resource is a performance, production, derivation, translation or interpretation. AGLS Metadata Usage Guide Proposal
AGLSTERMS.isBasisFor A related resource that is a performance, production, derivation, translation or interpretation of the described resource. AGLS Metadata Usage Guide Proposal
AGLSTERMS.jurisdiction The name of the political/administrative entity covered by the described resource. AGLS Metadata Usage Guide Proposal
AGLSTERMS.mandate A specific legal instrument which requires or drives the creation or provision of the resource. AGLS Metadata Usage Guide Proposal
AGLSTERMS.protectiveMarking A protective marking applied to the described resource. AGLS Metadata Usage Guide Proposal
AGLSTERMS.regulation A specific regulation which requires or drives the creation or provision of the resource. AGLS Metadata Usage Guide Proposal
AGLSTERMS.serviceType The form of the described resource where the value of category is ‘service'. AGLS Metadata Usage Guide Proposal
alexaverifyid Used to verify ownership of Alexa Search Alexa FAQ About this meta attribute Reference Proposal
apple-itunes-app Promoting Apps with Smart App Banners Safari Web Content Guide Proposal
apple-mobile-web-app-capable Sets whether a web application runs in full-screen mode. Apple Safari HTML Reference mobile-web-app-capable (also could maybe be assumed when application-name is set?) Proposal
apple-mobile-web-app-status-bar-style Sets the style of the status bar for a web application. Apple Safari HTML Reference Proposal
apple-mobile-web-app-title Sets the title of the application when added to the homescreen on iOS6+ Unofficial Documentation of apple-mobile-web-app-title - Read more about Apple's web-app's at Apple Safari HTML Reference Proposal
apple-touch-fullscreen forces iPhone Fullscreen mode, if added to home screen. Not needed anymore. No specification yet Proposal
application-name For Windows 7: "[D]efines the name of the Pinned site application instance. This is the name that appears in a tooltip when hovering over the Pinned site button on the Windows 7 taskbar. The application name is also appended to the window title of the Pinned site application instance." Although the documentation refers to an application, it gives an example of writing this metadata for HTML. Indeed, this name must not be used except in a Web application, according to HTML Living Standard and HTML 5.1. Declaring Pinned Site Metadata (Microsoft Developer Network) Proposed
application-url Start URL of web apps in Google Chrome

The "application-url" meta tag can be used to specify the start URL of pinned web apps in Google Chrome.

<meta name="application-url" content="https://gmail.com/">
Google Chrome Webmaster FAQ Chromium issue response Proposal
audience Categorize the principal intended audience for the page, generally with a controlled vocabulary.

Google uses this tag: Custom Search Help, as accessed Jan. 8, 2016.
BrittleBit.org spec Proposal
bitcoin A bitcoin-address Short documentation (unofficial): JokeNetwork's unofficial documentation for bitcoin-metatag, more informations about the Bitcoin-adress: Bitcoin wiki Proposal
blazerr-secure Decides whether connect via a secure connection or not to JokeNetwork's Blazerr-System. Synonym to blazerr-ssl, but only for old browsers such as Internet Explorer 7.

Usage: <meta name="blazerr-secure" content="yes">

JokeNetwork's Blazerr Documentation Proposal
blazerr-seo Checks whether Blazerr SEO has been used or not. It contains the user-id and the SEO Version.

Usage: <meta name="blazerr-seo" content="0001;v0.7">
0001 is an example for a user id, v0.7 identifies which version of SEO is used (In this case version Beta 7 / 0.7). If you're using Blazerr SEO, you have to include this meta-tag. Otherwise the tool will not work.

JokeNetwork's Blazerr Documentation Proposal
blazerr-ssl Decides whether connect via a secure connection or not to JokeNetwork's Blazerr-System. Similar to blazerr-secure.

Usage: <meta name="blazerr-ssl" content="yes">

JokeNetwork's Blazerr Documentation blazerr-secure is partial synonym (see that entry) Proposal
blazerr-support-id-noncookies Used to identify users for JokeNetwork's Blazerr Support-System without a cookie. Deprecated. JokeNetwork's Blazerr Documentation Proposal
blazerr-support-identifier Used to identify users for JokeNetwork's Blazerr Support-System along with a cookie. The verification of a user without the use of cookies can be obtained with the deprecated meta tag blazerr-support-id-noncookies. JokeNetwork's Blazerr Documentation Proposal
bug.blocked Bugzilla dependency tree to which the https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js bug-creation script will add a link. Embedded documentation Proposal
bug.comment Bugzilla comment used by the https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js bug-creation script. Embedded documentation Proposal
bug.component Bugzilla component against which the https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js bug-creation script will create a new bug. Embedded documentation Proposal
bug.product Bugzilla product against which the https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js bug-creation script will create a new bug. Embedded documentation Proposal
bug.short_desc Bugzilla short description used by the https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js bug-creation script. Embedded documentation Proposal
cfia.gdr.activity Canadian Food Inspection Agency Guidance Document Repository Page Activity Coming soon at CFIA website Proposal
cfia.gdr.commodity Canadian Food Inspection Agency Guidance Document Repository Page Commodity Coming soon at CFIA website Proposal
cfia.gdr.include Canadian Food Inspection Agency Guidance Document Repository Page Coming soon at CFIA website Proposal
cfia.gdr.program Canadian Food Inspection Agency Guidance Document Repository Page Program Coming soon at CFIA website Proposal
citation_author The name of an author of an academic paper Google Scholar indexing documentation Proposal
citation_author_email The email address of the preceding author (identified using citation_author) of an academic paper Proposal
citation_author_institution The name of an institution to which the preceding author (identified using citation_author) of an academic paper is affiliated Proposal
citation_conference_title The title of the conference at which an academic paper is published Google Scholar indexing documentation Proposal
citation_date The publication date of an academic paper Proposal
citation_dissertation_institution The name of the institution which published an academic dissertation Google Scholar indexing documentation Proposal
citation_doi The Digital Object Identifier of an academic paper Proposal
citation_firstpage The first page of the journal in which an academic paper is published Google Scholar indexing documentation Proposal
citation_fulltext_html_url The URL of the full text HTML version of an academic paper Proposal
citation_isbn The ISBN of the book in which an academic paper is published Google Scholar indexing documentation Proposal
citation_issn The ISSN of the journal in which an academic paper is published Google Scholar indexing documentation Proposal
citation_issue The issue of the journal in which an academic paper is published Google Scholar indexing documentation Proposal
citation_journal_abbrev The abbreviated title of the journal in which an academic paper is published Proposal
citation_journal_title The title of the journal in which an academic paper is published Google Scholar indexing documentation Proposal
citation_keywords A semicolon-separated list of keywords associated with an academic paper Proposal
citation_language The language in which an academic paper is written, as an ISO 639-1 two-letter code Proposal
citation_lastpage The last page of the journal in which an academic paper is published Google Scholar indexing documentation Proposal
citation_pdf_url The URL of a PDF version of an academic paper Google Scholar indexing documentation Proposal
citation_publication_date The publication date of an academic paper Google Scholar indexing documentation Proposal
citation_publisher The name of the publisher of an academic paper The spec (as accessed 11-26-17) omits this meta name but refers to the meta name DC.publisher (see that on this page). Proposal
citation_technical_report_institution The name of the institution which published an academic technical report or preprint Google Scholar indexing documentation Proposal
citation_technical_report_number The identification number of an academic technical report or preprint Google Scholar indexing documentation Proposal
citation_title The title of an academic paper Google Scholar indexing documentation Proposal
citation_volume The volume of the journal in which an academic paper is published Google Scholar indexing documentation Proposal
citeseerxbot Synonym of robots for targeting CiteSeerX only. CiteSeerX Submit Documents 'If you do not want your documents crawled by CiteSeerX, please use a robots.txt to disallow our crawler named "citeseerxbot"', CiteSeerX Crawler Proposal
collection To replace the obsolete dc:collection. A collection is described as a group, an aggregation of topics Used to describe the top-level content of XHTML documents. These appear in your META tags showing a group of subject. Website Taxonomy improve classification for search engine analysis and semantic communication with a description language content.

<meta name="collection" content="MetaExtensions" /> <meta name="subject" content="topics, thesaurus, Meta Tag, header, semantic" />

[1] Proposal
contact Defines the vendor's contact information by way of a phone-number (such as the customer support number), an e-mail ID (such as the customer support mail ID) or a physical address (such as the office address or billing address).

Usage: <meta name="contact" content="+1-555-555-5555 abc@xyz.com '5844 South Oak Street, Chicago, Illinois'">
or in case of multiple entries:
<meta name="contact" content="Chicago: +1-555-555-5555 abc@xyz.com '5844 South Oak Street, Chicago, Illinois'; Brookfield: +1-444-444-4444 def@xyz.com '2341 Cherry Lane, Brookfield, Illinois'">
The content attribute is a space separated string containing the phone-number followed by the e-mail ID and then the address (specified within quotes).
For specifying multiple entries a semi-colon separated list of name: value pairs can be defined. The name can be any descriptive tag identifying the given location.
Valid phone numbers and mail IDs should be provided by the vendor. The address can either be a string specified within quotes or the latitude and longtitude coordinates.

Documentation Proposal
creator Identify the creator of the page’s content, the content generally being the principal part of what info is rendered for website visitors. BrittleBit.org spec Proposal
csrf-param Cross-site request forgery protection parameter for Ruby on Rails Rails API Proposal
csrf-token Cross-site request forgery protection token for Ruby on Rails Rails API Proposal
da_anonymiseIP Defines anonymiseIP parameter for Decibel Insight Documentation Proposal
da_contactCompany Defines the contactCompany of the page for Decibel Insight Documentation Proposal
da_contactEmail Defines the contactEmail of the page for Decibel Insight Documentation Proposal
da_contactFirstName Defines the contactFirstName of the page for Decibel Insight Documentation Proposal
da_contactLastName Defines the contactLastName of the page for Decibel Insight Documentation Proposal
da_contactName Defines the contactName of the page for Decibel Insight Documentation Proposal
da_contactTelephone Defines the contactTelephone of the page for Decibel Insight Documentation Proposal
da_conversionCurrency Defines the conversionCurrency of the page for Decibel Insight Documentation Proposal
da_conversionId Defines the conversionId of the page for Decibel Insight Documentation Proposal
da_conversionValue Defines the conversionValue of the page for Decibel Insight Documentation Proposal
da_goalCurrency Defines the goalCurrency of the page for Decibel Insight Documentation Proposal
da_goalId Defines the goalId of the page for Decibel Insight Documentation Proposal
da_goalValue Defines the goalValue of the page for Decibel Insight Documentation Proposal
da_interactionSelector Defines the interactionSelector parameter for Decibel Insight Documentation Proposal
da_pageRole Defines the role of the page for Decibel Insight Documentation Proposal
da_pageTaxonomy Defines the taxonomy of the page for Decibel Insight Documentation Proposal
da_pageTitle Defines the pageTitle of the page for Decibel Insight Documentation Proposal
da_pageVersion Defines the pageVersion of the page for Decibel Insight Documentation Proposal
da_sessionId Defines the sessionId parameter for Decibel Insight Documentation Proposal
da_userId Defines the userId parameter for Decibel Insight Documentation Proposal
dc.created Date of creation of the resource.

It must be accompanied by a <link rel="schema.dc" href="http://purl.org/dc/elements/1.1/"> element.

DCMI Metadata Terms mapped according to

Expressing Dublin Core metadata using HTML/XHTML meta and link elements

Proposal
dc.creator An entity primarily responsible for making the resource.

It must be accompanied by a <link rel="schema.dc" href="http://purl.org/dc/elements/1.1/"> element.

DCMI Metadata Terms mapped according to

Expressing Dublin Core metadata using HTML/XHTML meta and link elements

Proposal
dc.date.issued Date of publication for Google News. The format of the content is YYYY-MM-DD or YYYY-MM-DDThh:mm:ssTZD.

It must be accompanied by a <link rel="schema.dc" href="http://purl.org/dc/elements/1.1/"> element

Google News documentation dcterms.issued (former <time pubdate> no longer considered due to the abort of @pubdate) Proposal
dc.dateCopyrighted Date of copyright.

It must be accompanied by a <link rel="schema.dc" href="http://purl.org/dc/elements/1.1/"> element.

DCMI Metadata Terms mapped according to

Expressing Dublin Core metadata using HTML/XHTML meta and link elements

Proposal
dc.dateSubmitted Date of submission of the resource.

It must be accompanied by a <link rel="schema.dc" href="http://purl.org/dc/elements/1.1/"> element.

DCMI Metadata Terms mapped according to

Expressing Dublin Core metadata using HTML/XHTML meta and link elements

Proposal
dc.description An account of the resource.

It must be accompanied by a <link rel="schema.dc" href="http://purl.org/dc/elements/1.1/"> element.

DCMI Metadata Terms mapped according to

Expressing Dublin Core metadata using HTML/XHTML meta and link elements

Proposal
dc.language A language of the resource. Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646].

It must be accompanied by a <link rel="schema.dc" href="http://purl.org/dc/elements/1.1/"> element.

DCMI Metadata Terms mapped according to