WHATWG Wiki - User contributions [en]

MetaExtensions

2021-02-27T19:23:29Z

GPHemsley: allow link

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

For assistance in preparing a specification, see the [[:Category:Specification editing|specification editing]] category and the [https://github.com/tabatkins/bikeshed/ Bikeshed] documentation.

If the specification is ready, 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''' [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.
* '''Not reserve namespaces.''' Instead, register individual names (known as enumerated values although you don't have to number them).

URL-valued attributes 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.

__TOC__

== Meta Name Extensions ==

{| class="wikitable sortable"
! Keyword
! Brief description
! Link to specification
! Synonyms
! Status

|-valign="top"
| AGLSTERMS.accessibility
| 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]
|
| Proposal

|-valign="top"
| AGLSTERMS.accessMode
| Perceptual mode for the resource.
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
|
| Proposal

|-valign="top"
| AGLSTERMS.act
| 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]
|
| Proposal

|-valign="top"
| AGLSTERMS.aggregationLevel
| 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]
|
| Proposal

|-valign="top"
| AGLSTERMS.allow-search
| 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]
|
| Proposal

|-valign="top"
| 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.
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
|
| Proposal

|-valign="top"
| AGLSTERMS.case
| A specific piece of case law 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]
|
| Proposal

|-valign="top"
| AGLSTERMS.category
| The generic type of the resource being described - a 'service', 'document' or 'agency'.
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
|
| Proposal

|-valign="top"
| AGLSTERMS.dateLicensed
| Date a license was applied or became effective.
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
|
| Proposal

|-valign="top"
| 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.
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
|
| Proposal

|-valign="top"
| 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.
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
|
| Proposal

|-valign="top"
| AGLSTERMS.isBasedOn
| 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]
|
| Proposal

|-valign="top"
| AGLSTERMS.isBasisFor
| 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]
|
| Proposal

|-valign="top"
| AGLSTERMS.jurisdiction
| The name of the political/administrative entity covered by the described resource.
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
|
| Proposal

|-valign="top"
| AGLSTERMS.mandate
| A specific legal instrument 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]
|
| Proposal

|-valign="top"
| AGLSTERMS.protectiveMarking
| A protective marking applied to the described resource.
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
|
| Proposal

|-valign="top"
| AGLSTERMS.regulation
| A specific regulation 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]
|
| Proposal

|-valign="top"
| AGLSTERMS.serviceType
| The form of the described resource where the value of category is ‘service'.
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]
|
| Proposal

|-valign="top"
| alexaverifyid
| Used to verify ownership of Alexa Search
| [http://www.alexa.com/faqs/?p=188 Alexa FAQ About this meta attribute Reference]
|
| Proposal

|-valign="top"
| apple-itunes-app
| Promoting Apps with Smart App Banners
| [http://developer.apple.com/library/ios/#documentation/AppleApplications/Reference/SafariWebContent/PromotingAppswithAppBanners/PromotingAppswithAppBanners.html Safari Web Content Guide]
|
| Proposal

|-valign="top"
| apple-mobile-web-app-capable
| Sets whether a web application runs in full-screen mode.
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/SafariHTMLRef/Articles/MetaTags.html Apple Safari HTML Reference]
| mobile-web-app-capable (also could maybe be assumed when <code>application-name</code> is set?)
| Proposal

|-valign="top"
| apple-mobile-web-app-status-bar-style
| Sets the style of the status bar for a web application.
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/SafariHTMLRef/Articles/MetaTags.html Apple Safari HTML Reference]
|
| Proposal

|-valign="top"
| apple-mobile-web-app-title
| Sets the title of the application when added to the homescreen on iOS6+
| [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

|-valign="top"
| apple-touch-fullscreen
| forces iPhone Fullscreen mode, if added to home screen. Not needed anymore.
| No specification yet
|
| 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"
| 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/">
| [http://www.google.com/chrome/intl/en/webmasters-faq.html#customshortcuts Google Chrome Webmaster FAQ] [http://code.google.com/p/chromium/issues/detail?id=40010#c1 Chromium issue response]
|
| Proposal

|-valign="top"
| appstore:bundle_id
| Application bundle identifier or package identifier, used to identify applications on platforms and within some app stores. Usage: <code><meta name="appstore:bundle_id" content="com.example.myapp"></code>
| IAB Tech Lab app-ads.txt documentation: <nowiki>https://iabtechlab.com/ads-txt/</nowiki>
|
| Proposal

|-valign="top"
| appstore:developer_url
| The consumer-visible URL published as developer contact details within an app store listing for an app. Usage: <code><meta name="appstore:developer_url" content="<nowiki>https://www.path.to/page</nowiki>"></code>
| IAB Tech Lab app-ads.txt documentation: <nowiki>https://iabtechlab.com/ads-txt/</nowiki>
|
| Proposal

|-valign="top"
| appstore:store_id
| An app store specific identifier representing the stock keeping unit (SKU) or another identifier used to locate the app within the store. Usage: <code><meta name="appstore:store_id" content="SKU12345"></code>
| IAB Tech Lab app-ads.txt documentation: <nowiki>https://iabtechlab.com/ads-txt/</nowiki>
|
| Proposal

|-valign="top"
| audience
| 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://brittlebit.org/specifications/html-meta-audience/specification-for-html-meta-element-with-name-value-audience.html BrittleBit.org spec]
|
| Proposal

|-valign="top"
| bitcoin
| 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]
|
| Proposal

|-valign="top"
| 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.<br>
Usage: <code><meta name="blazerr-secure" content="yes"></code>
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-secure JokeNetwork's Blazerr Documentation]
|
| Proposal

|-valign="top"
| blazerr-seo
| Checks whether Blazerr SEO has been used or not. It contains the user-id and the SEO Version.<br>
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

|-valign="top"
| blazerr-ssl
| Decides whether connect via a secure connection or not to JokeNetwork's Blazerr-System. Similar to blazerr-secure.<br>
Usage: <code><meta name="blazerr-ssl" content="yes"></code>
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-ssl JokeNetwork's Blazerr Documentation]
| blazerr-secure is partial synonym (see that entry)
| Proposal

|-valign="top"
| blazerr-support-id-noncookies
| Used to identify users for JokeNetwork's Blazerr Support-System without a cookie. Deprecated.
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-support-id-noncookies JokeNetwork's Blazerr Documentation]
|
| Proposal

|-valign="top"
| 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 [https://jokenetwork.de/faq/blazerr/ blazerr-support-id-noncookies].
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-support-identifier JokeNetwork's Blazerr Documentation]
|
| Proposal

|-valign="top"
| 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.
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]
|
| Proposal

|-valign="top"
| bug.comment
| Bugzilla comment used by the https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js bug-creation script.
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]
|
| Proposal

|-valign="top"
| 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.
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]
|
| Proposal

|-valign="top"
| 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.
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]
|
| Proposal

|-valign="top"
| 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.
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]
|
| Proposal

|-valign="top"
| cfia.gdr.activity
| Canadian Food Inspection Agency Guidance Document Repository Page Activity
| Coming soon at [http://www.inspection.gc.ca CFIA website]
|
| Proposal

|-valign="top"
| cfia.gdr.commodity
| Canadian Food Inspection Agency Guidance Document Repository Page Commodity
| Coming soon at [http://www.inspection.gc.ca CFIA website]
|
| Proposal

|-valign="top"
| cfia.gdr.include
| Canadian Food Inspection Agency Guidance Document Repository Page
| Coming soon at [http://www.inspection.gc.ca CFIA website]
|
| Proposal

|-valign="top"
| cfia.gdr.program
| Canadian Food Inspection Agency Guidance Document Repository Page Program
| Coming soon at [http://www.inspection.gc.ca CFIA website]
|
| Proposal

|-valign="top"
| citation_author
| The name of an author of an academic paper
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]
|
| Proposal

|-valign="top"
| citation_author_email
| The email address of the preceding author (identified using citation_author) of an academic paper
|
|
| Proposal

|-valign="top"
| citation_author_institution
| The name of an institution to which the preceding author (identified using citation_author) of an academic paper is affiliated
|
|
| Proposal

|-valign="top"
| citation_conference_title
| The title of the conference at which an academic paper is published
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]
|
| Proposal

|-valign="top"
| citation_date
| The publication date of an academic paper
|
|
| Proposal

|-valign="top"
| citation_dissertation_institution
| The name of the institution which published an academic dissertation
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]
|
| Proposal

|-valign="top"
| citation_doi
| The Digital Object Identifier of an academic paper
|
|
| Proposal

|-valign="top"
| citation_firstpage
| The first page of the journal in which an academic paper is published
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]
|
| Proposal

|-valign="top"
| citation_fulltext_html_url
| The URL of the full text HTML version of an academic paper
|
|
| Proposal

|-valign="top"
| citation_isbn
| The ISBN of the book in which an academic paper is published
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]
|
| Proposal

|-valign="top"
| citation_issn
| The ISSN of the journal in which an academic paper is published
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]
|
| Proposal

|-valign="top"
| citation_issue
| The issue of the journal in which an academic paper is published
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]
|
| Proposal

|-valign="top"
| citation_journal_abbrev
| The abbreviated title of the journal in which an academic paper is published
|
|
| Proposal

|-valign="top"
| citation_journal_title
| The title of the journal in which an academic paper is published
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]
|
| Proposal

|-valign="top"
| citation_keywords
| A semicolon-separated list of keywords associated with an academic paper
|
|
| Proposal

|-valign="top"
| citation_language
| The language in which an academic paper is written, as an ISO 639-1 two-letter code
|
|
| Proposal

|-valign="top"
| citation_lastpage
| The last page of the journal in which an academic paper is published
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]
|
| Proposal

|-valign="top"
| citation_pdf_url
| The URL of a PDF version of an academic paper
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]
|
| Proposal

|-valign="top"
| citation_publication_date
| The publication date of an academic paper
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]
|
| Proposal

|-valign="top"
| citation_publisher
| 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

|-valign="top"
| citation_technical_report_institution
| The name of the institution which published an academic technical report or preprint
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]
|
| Proposal

|-valign="top"
| citation_technical_report_number
| The identification number of an academic technical report or preprint
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]
|
| Proposal

|-valign="top"
| citation_title
| The title of an academic paper
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]
|
| Proposal

|-valign="top"
| citation_volume
| The volume of the journal in which an academic paper is published
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]
|
| Proposal

|-valign="top"
| 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" />
| [http://www.trucsweb.com/tw/]
|
| Proposal

|-valign="top"
| 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).<br>
Usage: <code><meta name="contact" content="+1-555-555-5555 abc@xyz.com '5844 South Oak Street, Chicago, Illinois'"></code><br>or in case of multiple entries:<br>
<code><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'"></code><br>
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).<br>
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.<br>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.
| [http://arpita.github.io/ContactMetaExtensions/ Documentation]
|
| 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"
| csrf-param
| Cross-site request forgery protection parameter for Ruby on Rails
| [http://apidock.com/rails/ActionView/Helpers/CsrfHelper/csrf_meta_tag Rails API]
|
| Proposal

|-valign="top"
| csrf-token
| Cross-site request forgery protection token for Ruby on Rails
| [http://apidock.com/rails/ActionView/Helpers/CsrfHelper/csrf_meta_tag Rails API]
|
| Proposal

|-valign="top"
| da_anonymiseIP
| Defines anonymiseIP parameter for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_contactCompany
| Defines the contactCompany of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_contactEmail
| Defines the contactEmail of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_contactFirstName
| Defines the contactFirstName of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_contactLastName
| Defines the contactLastName of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_contactName
| Defines the contactName of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_contactTelephone
| Defines the contactTelephone of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_conversionCurrency
| Defines the conversionCurrency of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_conversionId
| Defines the conversionId of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_conversionValue
| Defines the conversionValue of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_goalCurrency
| Defines the goalCurrency of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_goalId
| Defines the goalId of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_goalValue
| Defines the goalValue of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_interactionSelector
| Defines the interactionSelector parameter for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_pageRole
| Defines the role of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_pageTaxonomy
| Defines the taxonomy of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_pageTitle
| Defines the pageTitle of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_pageVersion
| Defines the pageVersion of the page for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_sessionId
| Defines the sessionId parameter for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| da_userId
| Defines the userId parameter for Decibel Insight
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]
|
| Proposal

|-valign="top"
| dc.created
| Date of creation of the resource.
It must be accompanied by a <code><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dc.creator
| An entity primarily responsible for making the resource.
It must be accompanied by a <code><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></code> element.
| [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]
|
| 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><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></code> element
| [http://www.google.com/support/news_pub/bin/answer.py?answer=93994 Google News documentation]
| <code>dcterms.issued</code> (former <code><time pubdate></code> no longer considered due to the abort of <code>@pubdate</code>)
| Proposal

|-valign="top"
| dc.dateCopyrighted
| Date of copyright.
It must be accompanied by a <code><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dc.dateSubmitted
| Date of submission of the resource.
It must be accompanied by a <code><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dc.description
| An account of the resource.
It must be accompanied by a <code><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| 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 <code><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></code> element.
| [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]
| 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

|-valign="top"
| dc.license
| A legal document giving official permission to do something with the resource.
It must be accompanied by a <code><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dc.mediator
| An entity that mediates access to the resource and for whom the resource is intended or useful.
It must be accompanied by a <code><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dc.medium
| The material or physical carrier of the resource.
It must be accompanied by a <code><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dc.modified
| Date on which the resource was changed.
It must be accompanied by a <code><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dc.provenance
| 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><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dc.publisher
| An entity responsible for making the resource available.
It must be accompanied by a <code><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></code> element.
| [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]
|
| 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><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></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

|-valign="top"
| dc.temporal
| Temporal characteristics of the resource.
It must be accompanied by a <code><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></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

|-valign="top"
| dc.title
| A name given to the resource.
It must be accompanied by a <code><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></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]
|
| Proposal

|-valign="top"
| 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].
To describe the file format, physical medium, or dimensions of the resource, use the Format element.
It must be accompanied by a <code><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></code> element.
| [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

|-valign="top"
| dc.valid
| Date (often a range) of validity of a resource.
It must be accompanied by a <code><link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"></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.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [http://dublincore.org/documents/dcmi-terms/#terms-abstract DCMI
Metadata Terms] mapped according to
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]
| <code><meta name="description"></code>
| Proposal

|-valign="top"
| dcterms.accessRights
| Information about who can access the resource or an indication of its security status.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.accrualMethod
| The method by which items are added to a collection.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.accrualPeriodicity
| The frequency with which items are added to a collection.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.accrualPolicy
| The policy governing the addition of items to a collection.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.alternative
| An alternative name for the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.audience
| A class of entity for whom the resource is intended or useful.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.available
| Date (often a range) that the resource became or will become available.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.bibliographicCitation
| A bibliographic reference for the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
| The HTML attribute <code>cite</code>
| Proposal

|-valign="top"
| dcterms.collection
| An aggregation of resources.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.conformsTo
| An established standard to which the described resource conforms.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></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.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| 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.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.created
| Date of creation of the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.creator
| 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><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
| In some cases redundant with the HTML built-in keyword <code>author</code>
| Proposal

|-valign="top"
| dcterms.date
| A point or period of time associated with an event in the lifecycle of the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.dateAccepted
| Date of acceptance of the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.dateCopyrighted
| Date of copyright.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.dateSubmitted
| Date of submission of the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| 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.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
| HTML built-in keyword <code>description</code>
| Proposal

|-valign="top"
| dcterms.educationLevel
| 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><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.extent
| The size or duration of the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.format
| The file format, physical medium, or dimensions of the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
| 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><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></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

|-valign="top"
| dcterms.hasPart
| A related resource that is included either physically or logically in the described resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></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><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></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.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.instructionalMethod
| A process used to engender knowledge, attitudes and skills, that the described resource is designed to support.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.isFormatOf
| A related resource that is substantially the same as the described resource, but in another format.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code>
| Proposal

|-valign="top"
| dcterms.isPartOf
| A related resource in which the described resource is physically or logically included.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.isReferencedBy
| A related resource that references, cites, or otherwise points to the described resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.isReplacedBy
| A related resource that supplants, displaces, or supersedes the described resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code>
| Proposal

|-valign="top"
| dcterms.isRequiredBy
| A related resource that requires the described resource to support its function, delivery, or coherence.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.issued
| 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><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
| (former <code><time pubdate></code> no longer considered due to the abort of <code>@pubdate</code>)
| Proposal

|-valign="top"
| dcterms.isVersionOf
| A related resource of which the described resource is a version, edition, or adaptation.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code>
| Proposal

|-valign="top"
| dcterms.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 <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
| 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

|-valign="top"
| dcterms.license
| A legal document giving official permission to do something with the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
| The HTML <code><link></code> element with the keyword <code>"license"</code> as value of the <code>rel</code> attribute.
| Proposal

|-valign="top"
| dcterms.mediator
| An entity that mediates access to the resource and for whom the resource is intended or useful.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.medium
| The material or physical carrier of the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.modified
| 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><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.provenance
| 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><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
|
| Proposal

|-valign="top"
| dcterms.publisher
| An entity responsible for making the resource available.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
| publisher
| Proposal

|-valign="top"
| dcterms.references
| A related resource that is referenced, cited, or otherwise pointed to by the described resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></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]
| <code>cite</code> attribute on specific quotes, if any.
| Proposal

|-valign="top"
| dcterms.relation
| A related resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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]
| If the relation comes from an internal reference or quote, <code>dcterms.references</code> should be preferred.
| Proposal

|-valign="top"
| dcterms.replaces
| A related resource that is supplanted, displaced, or superseded by the described resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></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

|-valign="top"
| dcterms.requires
| A related resource that is required by the described resource to support its function, delivery, or coherence.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></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

|-valign="top"
| dcterms.rights
| Information about rights held in and over the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></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><link></code> element with the keyword <code>"license"</code> as value of the <code>rel</code> attribute, if referring to a legal license format.
| Proposal

|-valign="top"
| dcterms.rightsHolder
| A person or organization owning or managing rights over the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></code> element.
| [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

|-valign="top"
| dcterms.source
| A related resource from which the described resource is derived.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></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

|-valign="top"
| dcterms.spatial
| Spatial characteristics of the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></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

|-valign="top"
| dcterms.subject
| The topic of the resource.
| [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

|-valign="top"
| dcterms.tableOfContents
| A list of subunits of the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></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

|-valign="top"
| dcterms.temporal
| Temporal characteristics of the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></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

|-valign="top"
| dcterms.title
| A name given to the resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></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

|-valign="top"
| dcterms.type
| The nature or genre of the resource.
| [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

|-valign="top"
| dcterms.valid
| Date (often a range) of validity of a resource.
It must be accompanied by a <code><link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"></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"
| detectify-verification
| 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.
| [http://labs.detectify.com/post/85707633296/detectify-validation-specification Documentation]
|
| Proposal

|-valign="top"
| designer
| Credits the designer(s) responsible for the visual presentation of a website.
| [https://sites.google.com/site/metadesignerspec/ Documentation]
|
| Proposal

|-valign="top"
| entity
| 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.
| [https://github.com/brettz9/js-css-entities Documentation]
|
| 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"
| fdse-description
| Tag used by FDSE search software, allows different description to be displayed in fdse results to that shown in description
| [http://www.xav.com/scripts/search/help/1013.html]
|
| Proposal

|-valign="top"
| fdse-index-as
| Tag used by FDSE search software, allows FDSE to index a page as url described here
| [http://www.xav.com/scripts/search/help/1014.html]
|
| Proposal

|-valign="top"
| fdse-keywords
| Tag used by FDSE search software, allows different keywords to be used by FDSE to keywords tag
| [http://www.xav.com/scripts/search/help/1013.html]
|
| Proposal

|-valign="top"
| fdse-refresh
| Tag used by FDSE search software, allows FDSE to ignore refresh meta tags
| [http://www.xav.com/scripts/search/help/1013.html]
|
| Proposal

|-valign="top"
| fdse-robots
| 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
| [http://www.xav.com/scripts/search/help/1013.html]
|
| Proposal

|-valign="top"
| FLBlogAuthor
| Depicts whether author of the blog is lawfirm or FL author
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
|
| Proposal

|-valign="top"
| format-detection
| Enables or disables automatic detection of possible phone numbers in a webpage in Safari on iOS.
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/SafariHTMLRef/Articles/MetaTags.html Apple Safari HTML Reference]
|
| Proposal

|-valign="top"
| format-print
| 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.
| [http://brittlebit.org/specifications/html-meta-format-print/specification-for-html-meta-element-with-name-value-format-print.html BrittleBit.org spec]
|
| Proposal

|-valign="top"
| fragment
| Opts a webpage into the AJAX crawling scheme when it does not have a "#!" URL. The only valid content value is "!".
<meta name="fragment" content="!">
| [https://developers.google.com/webmasters/ajax-crawling/docs/specification Google Crawable AJAX Specification]
|
| Proposal

|-valign="top"
| FSDateCreation
| Mentions the date when this web page was created
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
|
| Proposal

|-valign="top"
| FSDatePublish
| Mentions the date when this web page was created
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
|
| Proposal

|-valign="top"
| FSFLContent
| Informs the Publisher tool whether this page contains any content or not. Valid values yes or no
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
|
| Proposal

|-valign="top"
| FSLanguage
| Language of the content in the page. Example: US English or UK English, etc
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
|
| Proposal

|-valign="top"
| FSOnSitemap
| Whether the page is accessible via the Sitemap link in the firmsite
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
|
| Proposal

|-valign="top"
| FSPageDescription
| Description of the content of page
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
|
| Proposal

|-valign="top"
| FSPageName
| Name of the page within a Findlaw firmsite
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
|
| Proposal

|-valign="top"
| FSSearchable
| This tag mentions whether a certain page can be searched or not
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
|
| Proposal

|-valign="top"
| FSSection
| Depicts whether a page is a Section Page or simple page. Section pages can have links to other pages
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
|
| Proposal

|-valign="top"
| FSWritertoolPageType
| Page Type of a page in the firmsite. Page Type values help the Publisher toold in page creation
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]
|
| Proposal

|-valign="top"
| gcterms.topicTaxonomy
| Organize resources specifically for taxonomy-based topical browse or search structures on websites (ie: breadcrumbs / website information architecture).
| [http://www.gcpedia.gc.ca/wiki/Metadata_Tools#Metadata_for_Web_Resource_Discovery] Government of Canada, Web Content Management System Metadata Application Profile.
|
| Proposal

|-valign="top"
| geo.a1
| 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.
<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

|-valign="top"
| geo.a2
| County, parish, gun (JP), district (IN) of civil address to which the page is related.
<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

|-valign="top"
| geo.a3
| City, township, shi (JP) of civil address to which the page is related.
<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

|-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

|-valign="top"
| geo.lmk
| A landmark or vanity address to which the page is related.
<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

|-valign="top"
| geo.placename
| Superseded by geo.lmk. Name of geographic place to which the page is related.
<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

|-valign="top"
| geo.position
| Geographic position to which the page is related.
<meta name="geo.position" content="48.02682000000001;7.809769999999958"><br />Like icbm except for value syntax.
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft (expired)]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]
|
| Proposal

|-valign="top"
| geo.region
| 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.
<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

|-valign="top"
| globrix.bathrooms
| Globrix property information: Number of bathrooms the property has
| [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

|-valign="top"
| globrix.bedrooms
| Globrix property information: Number of bedrooms the property has
| [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

|-valign="top"
| globrix.condition
| Globrix property information: Condition of the property e.g. 'renovated'
| [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

|-valign="top"
| globrix.features
| Globrix property information: Features of the property e.g. 'double glazing'
| [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

|-valign="top"
| globrix.instruction
| Globrix property information: Property to Buy or Rent
| [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

|-valign="top"
| globrix.latitude
| Globrix property information: The latitude of the property
| [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

|-valign="top"
| globrix.longitude
| Globrix property information: The longitude of the property
| [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

|-valign="top"
| globrix.outsidespace
| Globrix property information: External features of the property e.g. 'garden'
| [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

|-valign="top"
| globrix.parking
| Globrix property information: Parking available for property e.g. 'parking for 2 cars'
| [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

|-valign="top"
| globrix.period
| Globrix property information: Period of the property e.g. 'victorian terrace'
| [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

|-valign="top"
| globrix.poa
| Globrix property information: If the property price is only available on application
| [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

|-valign="top"
| globrix.postcode
| Globrix property information: Postcode of the property
| [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

|-valign="top"
| globrix.price
| Globrix property information: Price for the property
| [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

|-valign="top"
| globrix.priceproximity
| Globrix property information: The region of the attached price e.g. 'guide price of'
| [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

|-valign="top"
| globrix.tenure
| Globrix property information: The tenure of the property e.g. 'leasehold'
| [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

|-valign="top"
| globrix.type
| Globrix property information: Type of property e.g. 'semi-detatched house'
| [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

|-valign="top"
| globrix.underoffer
| Globrix property information: Indicates if the property is under offer
| [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

|-valign="top"
| go-import
| 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>.
| [http://golang.org/cmd/go/#hdr-Remote_import_path_syntax go tool documentation]
|
| Proposal

|-valign="top"
| google
| Multiple purposes:<br /><br />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, while <span class="notranslate"> 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.
| "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 > Sitelinks Search Box]
|
| Nontranslation: Proposal<br /><br />No Sitelinks search box: Proposed

|-valign="top"
| google-play-app
| Promoting Apps with Smart App Banners
| [http://jasny.github.io/jquery.smartbanner/] Smart banners for Google Apps
|
| Proposal

|-valign="top"
| google-site-verification
| Used to verify ownership for Webmaster Tools.
| [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=79812 Google documentation]
|
| Proposal

|-valign="top"
| gwt:property
| Used to specify the locale client property
| [https://developers.google.com/web-toolkit/doc/latest/DevGuideI18nLocale Locales in GWT]
|
| 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

|-valign="top"
| icas.datetime
| 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).
| 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

|-valign="top"
| icas.datetime.abbr
| 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".
| 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

|-valign="top"
| icas.datetime.day
| 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".
| 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

|-valign="top"
| icas.datetime.long
| 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"/>
| 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

|-valign="top"
| icbm
| 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:
<meta name="ICBM" content="47.0667, 15.4500" /><br />Like geo.position except for value syntax.
| [http://geourl.org/add.html GeoURL documentation]
|
| 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

|-valign="top"
| keywords-not
| 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.
| [http://brittlebit.org/specifications/html-meta-keywords-not/specification-for-html-meta-element-with-name-value-keywords-not.html BrittleBit.org spec]
|
| Proposal

|-valign="top"
| meta_date
| 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".)
| [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 ]
|
| Proposal

|-valign="top"
| microtip
| 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:
<meta name="microtip" content="[bitcoin-address]">
Note: there can be multiple instances of this metatag on a page.
| For full specification, see: http://autotip.io/docs/microtip-meta-tag
|
| Proposal

|-valign="top"
| mobile-agent
| 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>
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="mobile-agent" content="format=html5; url=http://3g.sina.com.cn/">
| [http://open.shouji.baidu.com/?page=developer&action=pcandmo Baidu Mobile SEO]
|
| Proposal

|-valign="top"
| mobile-web-app-capable
| 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.
| [https://developers.google.com/chrome/mobile/docs/installtohomescreen Add to Homescreen - Google Chrome Mobile — Google Developers] (though a WHATWG or W3C spec would be preferred)
| apple-mobile-web-app-capable (vendor specific synonym)
| Proposal

|-valign="top"
| mobileoptimized
| Controls layout behavior in older versions of Internet Explorer (e.g., 6.5).
| [http://msdn.microsoft.com/en-us/library/bb431690.aspx Microsoft Windows Mobile 6.5 documentation]
|
| Proposal

|-valign="top"
| msapplication-config
| '''"Pinned Sites" in Windows 8'''
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" />
'''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

|-valign="top"
| msapplication-navbutton-color
| '''"Jump List" or "Pinned Sites" in Windows 7'''
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

|-valign="top"
| msapplication-notification
| '''"Pinned Sites" and "Live Tiles" in Windows 8.1'''
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

|-valign="top"
| msapplication-square150x150logo
| '''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

|-valign="top"
| msapplication-square310x310logo
| '''msapplication-square310x310logo'''
Specifies the image to use as the large tile, which is 310x310 pixels at 100% scaling.
<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

|-valign="top"
| msapplication-square70x70logo
| '''msapplication-square70x70logo'''
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

|-valign="top"
| msapplication-starturl
| '''"Jump List" or "Pinned Sites" in Windows 7'''
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

|-valign="top"
| msapplication-tap-highlight
| '''Link highlighting in Internet Explorer'''
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

|-valign="top"
| msapplication-task
| '''"Jump List" or "Pinned Sites" in Windows 7'''
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

|-valign="top"
| msapplication-TileColor
| 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.
<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

|-valign="top"
| msapplication-TileImage
| 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.
<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

|-valign="top"
| msapplication-tooltip
| '''"Jump List" or "Pinned Sites" in Windows 7'''
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

|-valign="top"
| msapplication-wide310x150logo
| '''msapplication-wide310x150logo'''
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

|-valign="top"
| msapplication-window
| '''"Jump List" or "Pinned Sites" in Windows 7'''
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

|-valign="top"
| MSSmartTagsPreventParsing
| 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.
| [http://brittlebit.org/specifications/html-meta-mssmarttagspreventparsing/specification-for-html-meta-element-with-name-value-mssmarttagspreventparsing.html BrittleBit.org spec]
|
| Proposal

|-valign="top"
| msvalidate.01
| One of the verification elements used by Bing.
| [http://onlinehelp.microsoft.com/en-us/bing/hh204490.aspx Bing Webmaster Tools]
|
| Proposal

|-valign="top"
| nonfiction
| 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.
| [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

|-valign="top"
| norton-safeweb-site-verification
| Used to verify ownership of Website for Norton SafeWeb.
| [http://safeweb.norton.com/help/site_owners#verification_tips Norton SafeWeb Help Documentation]
|
| Proposal

|-valign="top"
| origin
| The ''origin'' meta tag is used to indicate the original source of a document.
| [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

|-valign="top"
| p:domain_verify
| Used to register a site's domain with Pinterest as a "verified domain".
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

|-valign="top"
| page-version
| 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.
| [http://brittlebit.org/specifications/html-meta-page-version/specification-for-html-meta-element-with-name-value-page-version.html BrittleBit.org spec]
|
| Proposal

|-valign="top"
| pingdom
| 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.
Example:
<code><meta name="pingdom" content="6bh3nxnx"/></code>
|
|
| Proposal

|-valign="top"
| pinterest
| Used to block pinterest from linking to content on the URL.
Example:
<code><meta name="pinterest" content="nopin"/></code>
| [https://support.pinterest.com/entries/21101932-what-if-i-don-t-want-images-from-my-site-to-be-pinned Pinterest Help Article]
|
| Proposal

|-valign="top"
| prism:alternateTitle
| 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://www.prismstandard.org/specifications/3.0/PRISM_Basic_Metadata_3.0.htm PRISM Basic Metadata Specification V3.0]
|
| Proposal

|-valign="top"
| pro
| Signify expertise as judged by an authority. Counterpart to pro-auth (which see). Useful to search engines and Web directories.
| [http://brittlebit.org/specifications/html-meta-pro/specification-for-html-meta-element-with-name-value-pro.html BrittleBit.org spec]
|
| Proposal

|-valign="top"
| pro-auth
| 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).
| [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"
| pro-auth-field
| 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://brittlebit.org/specifications/html-meta-pro-auth-field/specification-for-html-meta-element-with-name-value-pro-auth-field.html BrittleBit.org spec]
|
| Proposal

|-valign="top"
| pro-auth-fragment
| Signify which links from authority are links to experts, as distinct from other links. Supports pro-auth (which see).
| [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

|-valign="top"
| rating
| 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.
Example:
<meta name="RATING" content="RTA-5042-1996-1400-1577-RTA" />
| [http://www.rtalabel.org/index.php?content=howto RTA documentation]
|
| Proposal

|-valign="top"
| referrer
| Controls whether the user agent includes the Referer header in HTTP requests originating from this document
| [https://www.w3.org/TR/referrer-policy/ Referrer Policy]
| referer
| Proposal

|-valign="top"
| RepostUsAPIKey
| Used to verify ownership of Website for Repost syndication service
| [http://www.repost.us/meta-headers-used-by-repost/ Meta Headers used by Repost]
|
| Proposal

|-valign="top"
| ResourceLoaderDynamicStyles
| [[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.
| [[mw:ResourceLoader/ResourceLoaderDynamicStyles specification|ResourceLoaderDynamicStyles]]
|
| Proposal
|-valign="top"

| 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

|-valign="top"
| revision
| The revision of this page as reported by an underlying Version Control System. This is a free format string.
| [https://github.com/krallin/meta-revision Meta Revision Specification]
|
| Proposal

|-valign="top"
| revisit-after
| 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.
| [http://code.google.com/webstats/2005-12/metadata.html Google documentation]
|
| Proposal

|-valign="top"
| rights
| 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]]
| [http://brittlebit.org/specifications/html-meta-rights/specification-for-html-meta-element-with-name-value-rights.html BrittleBit.org spec]
|
| Proposal

|-valign="top"
| rights-standard
| 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))

'''This keyword does not provide, remove or alter any legal protections or designations.'''

Format:
<pre><meta name="rights-standard" content="element id;rights" /></pre>

* 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

|-valign="top"
| robots
| A comma-separated list of operators explaining how search engine crawlers should treat the content. This meta name is already supported by every popular search engine.<br />Possible values are "noarchive" to prevent cached versions, "noindex" to prevent indexing, and "nofollow" works as the link rel value with the same name.<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/meta.html About the Robots <META> tag]; 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 />citeseerxbot (for targeting CiteSeerX 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

|-valign="top"
| rpuPlugin
| Version of installed Repost syndication service plugin
| [http://www.repost.us/meta-headers-used-by-repost/ Meta Headers used by Repost]
|
| Proposal

|-valign="top"
| rqid
| Request identifier of request that generated this page.
| [http://wiki.whatwg.org/wiki/RequestID RequestID]
|
| Proposal

|-valign="top"
| shareaholic:analytics
| Enables or disables Shareaholic Analytics for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:article_author
| A URL to the profile of the author of the content of the webpage for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:article_author_name
| Contains the name of the author of the content of the webpage for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:article_modified_time
| When the article was last modified for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:article_published_time
| When the article was first published for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:article_visibility
| Specifies whether a webpage should be publicly recommendable for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:drupal_version
| Specifies Shareaholic for Drupal module version for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:image
| An image URL which represents your webpage for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:keywords
| Keywords associated with the content of a webpage for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:language
| Language of the content of the webpage for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:outstreamads
| Enables or disables Shareaholic Outstream Ads for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:shareable_page
| Specifies whether a webpage should be publicly shareable for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:site_id
| Shareaholic Site ID for the website for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:site_name
| The name which should be displayed for the overall site for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:title
| Title associated with the content of a webpage for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:url
| The canonical URL of your webpage that will be used as its permanent ID for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| shareaholic:wp_version
| Specifies Shareaholic for WordPress plugin version for use with the Shareaholic Content Amplification system
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]
|
| Proposal

|-valign="top"
| signet:authors
| Authors of a page for use with javascript signet library
| [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:
<meta name="skype_toolbar" content="skype_toolbar_parser_compatible" />
| [http://skype.otherlinks.co.uk/page.asp?id=toolbar_number_formatting Skype Info]
|
| Proposal

|-valign="top"
| startIndex
| Used to identify the index of the first search result in the current set of search results.
| [http://www.opensearch.org/Specifications/OpenSearch/1.1#Response_metadata_in_HTML.2FXHTML OpenSearch Specification]
|
| Proposal

|-valign="top"
| startver
| Used to verify WebApps for JokeNetwork's Start!-WebApp
| [https://jokenetwork.de/faq/start/verification/ JokeNetwork's Start Documentation]
|
| Proposal

|-valign="top"
| subject-datetime
| Identify the principal datetime ranges of the subject of the page’s content, such as the dates of an historical event.
| [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-. . . or subj-* (namespace not approved thus synonym would be "subj-" plus whatever is after hyphen in token)
| Proposal

|-valign="top"
| supported-media
| Indicates the range of media for which the page's viewing is supported. Not intended for use by browsers, but rather by referrers that make use of crawl data.
| https://github.com/google/webpackager/blob/master/docs/supported_media.md
|
| 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

|-valign="top"
| thumbnail
| 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.)
| [https://support.google.com/customsearch/answer/1626955?hl=en Google page], as accessed Jan. 2, 2016. Original date unknown.
|
| Proposed

|-valign="top"
| topper
| Notify website visitors of later changes; easier for website authors to maintain than RSS or Atom.
| [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

|-valign="top"
| topper-major
| Limit use of topper to major changes.
| [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

|-valign="top"
| topper-minor
| In use of topper, include minor changes.
| [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

|-valign="top"
| totalResults
| Used to identify the number of search results available for the current search.
| [http://www.opensearch.org/Specifications/OpenSearch/1.1#Response_metadata_in_HTML.2FXHTML OpenSearch Specification]
|
| Proposal

|-valign="top"
| translator
| The ''translator'' meta tag is used to give credit to, and provide contact info for, the translator of a document.
| [https://doc.ohreally.nl/metatag-translator The ''translator'' meta tag]
|
| 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

|-valign="top"
| twitter:app:id:googleplay
| String value, and should be the numeric representation of your app ID in Google Play.
|
|
| Proposal

|-valign="top"
| twitter:app:id:ipad
| String value, should be the numeric representation of your app ID in the App Store.
|
|
| Proposal

|-valign="top"
| twitter:app:id:iphone
| String value, should be the numeric representation of your app ID in the App Store.
|
|
| Proposal

|-valign="top"
| twitter:app:name:googleplay
| Name of your Android app
|
|
| Proposal

|-valign="top"
| twitter:app:name:ipad
| Name of your iPad optimized app
|
|
| Proposal

|-valign="top"
| twitter:app:name:iphone
| Name of your iPhone app
|
|
| Proposal

|-valign="top"
| twitter:app:url:googleplay
| Your app's custom URL scheme.
|
|
| Proposal

|-valign="top"
| twitter:app:url:ipad
| Your app's custom URL scheme.
|
|
| Proposal

|-valign="top"
| twitter:app:url:iphone
| Your app's custom URL scheme.
|
|
| Proposal

|-valign="top"
| twitter:card
| The card type, which will be one of "summary", "photo", "app", or "player".
|
|
| Proposal

|-valign="top"
| twitter:creator
| @username for the content creator / author.
|
|
| Proposal

|-valign="top"
| twitter:creator:id
| Twitter ID for the content creator / author.
|
|
| Proposal

|-valign="top"
| twitter:data1
| String value; value for labels such as price, items in stock, sizes, etc
|
|
| Proposal

|-valign="top"
| twitter:data2
| String value; value for labels such as price, items in stock, sizes, etc
|
|
| Proposal

|-valign="top"
| twitter:description
| A description of the content in a maximum of 200 characters.
|
|
| Proposal

|-valign="top"
| twitter:domain
| Short URL assigned by Twitter to a website.
|
|
| Proposal

|-valign="top"
| twitter:image
| A URL to the image representing the content.
|
|
| Proposal

|-valign="top"
| twitter:image0
| A URL to the image representing the first photo in your gallery.
|
|
| Proposal

|-valign="top"
| twitter:image1
| A URL to the image representing the second photo in your gallery.
|
|
| Proposal

|-valign="top"
| twitter:image2
| A URL to the image representing the third photo in your gallery.
|
|
| Proposal

|-valign="top"
| twitter:image3
| A URL to the image representing the fourth photo in your gallery.
|
|
| Proposal

|-valign="top"
| twitter:image:height
| The height of the image representing the content.
|
|
| Proposal

|-valign="top"
| twitter:image:src
| URL of image to use in the card. Image must be less than 1MB in size.
|
|
| Proposal

|-valign="top"
| twitter:image:width
| The width of the image representing the content.
|
|
| Proposal

|-valign="top"
| twitter:label1
| String value; label such as price, items in stock, sizes, etc
|
|
| Proposal

|-valign="top"
| twitter:label2
| String value; label such as price, items in stock, sizes, etc
|
|
| Proposal

|-valign="top"
| twitter:player
| HTTPS URL to iframe player. This must be a HTTPS URL which does not generate active mixed content warnings in a web browser
|
|
| Proposal

|-valign="top"
| twitter:player:height
| Height of IFRAME specified in twitter:player in pixels
|
|
| Proposal

|-valign="top"
| twitter:player:stream
| URL to raw stream that will be rendered in Twitter's mobile applications directly
|
|
| Proposal

|-valign="top"
| twitter:player:stream:content_type
| The MIME type/subtype combination that describes the content contained in twitter:player:stream
|
|
| Proposal

|-valign="top"
| twitter:player:width
| Width of IFRAME specified in twitter:player in pixels
|
|
| Proposal

|-valign="top"
| twitter:site
| @username for the website used in the card footer.
|
|
| Proposal

|-valign="top"
| twitter:site:id
| Twitter ID for the website used in the card footer.
|
|
| Proposal

|-valign="top"
| twitter:title
| The title of the content as it should appear in the card.
|
|
| Proposal

|-valign="top"
| twitter:url
| Canonical URL of the card content.
|
|
| Proposal

|-valign="top"
| typemetal.formatprefs
| Per-file HTML formatting preferences used by the TypeMetal HTML editor
| [http://coherencelabs.com/typemetal/manual/typemetal-custom-metadata.html TypeMetal User Guide]
|
| Proposal

|-valign="top"
| verify-v1
| Superseded by google-site-verification. Legacy verification for Google Sitemaps.
| [http://sitemaps.blogspot.com/2006/05/more-about-meta-tag-verification.html Inside Google Sitemaps: More about meta tag verification]
|
| Proposal

|-valign="top"
| version
| The version of a web application according to the [http://semver.org/ Semantic Versioning] specification<br>
Example:
<code><meta name="version" content="0.1.0+1"></code>
| [https://github.com/dvorapa/meta-version Documentation]
|
| Proposal

|-valign="top"
| vfb-version
| Specifies a Visual Form Builder plugin version for Wordpress.
| [http://wordpress.org/plugins/visual-form-builder/ Visual Form Builder Documentation and specs]
|
| Proposal

|-valign="top"
| <span id="viewport">viewport</span>
| 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:
* width
* 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

|-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"
| witget
| Used to verify ownership for Witget.com.
Example <meta name="witget" content="XXXXXXXXXXXXXXXXXXXXXX">
| [http://support.witget.com/topic/435278-prostaya-ustanovka-skripta/ Witget manual]
|
| Proposal

|-valign="top"
| wot-verification
| Used to verify ownership of WOT (Web Of Trust)
| [http://www.mywot.com/wiki/Verify_your_website WOT's verify your site wiki page]
|
| Proposal

|-valign="top"
| wt.ac
| '''Advertising Click parameter'''
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]
|
| Proposal

|-valign="top"
| wt.ad
| '''Advertising View parameter'''
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

|-valign="top"
| wt.cg_n
| '''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

|-valign="top"
| wt.cg_s
| '''Name of Content Sub-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_s" content="My content">
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]
|
| Proposal

|-valign="top"
| wt.mc_id
| '''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:
<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

|-valign="top"
| WT.si_n
| '''Scenario analysis parameter - scenario name'''
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

|-valign="top"
| WT.si_p
| '''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

|-valign="top"
| WT.si_x
| '''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

|-valign="top"
| wt.sv
| '''Tracking Servers parameter'''
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

|-valign="top"
| wt.ti
| '''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

|-valign="top"
| y_key
| Used to verify ownership for Yahoo! Site Explorer
| [http://help.yahoo.com/l/us/yahoo/search/siteexplorer/siteexplorer-06.html Yahoo! documentation]
|
| Proposal

|-valign="top"
| yandex-verification
| Used to verify ownership for Yandex Webmaster.
| [http://help.yandex.ru/webmaster/?id=995300#995356 Yandex Webmaster ownership verification]
|
| Proposal

|-valign="top"
| ZOOMCATEGORY
| Category of page to be grouped in Wrensoft Zoom Search Engine.
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
|
| Proposal

|-valign="top"
| ZOOMDESCRIPTION
| Alternative page description for Wrensoft Zoom Search Engine.
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
|
| Proposal

|-valign="top"
| ZOOMIMAGE
| 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

|-valign="top"
| ZOOMPAGEBOOST
| 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]
|
| Proposal

|-valign="top"
| ZOOMTITLE
| Alternative page title for Wrensoft Zoom Search Engine.
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
|
| Proposal

|-valign="top"
| ZOOMWORDS
| Additional keywords to be indexed for Wrensoft Zoom Search Engine.
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]
|
| 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 ==

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"
| blogcatalog
| Used to verify ownership of Blog Catalog.com
| [http://www.blogcatalog.com/ Blog catalog site]
|
| Incomplete proposal
| Claimed spec link is not a link to a spec

|-valign="top"
| created
| 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
| Lacks link to a spec

|-valign="top"
| expires
| <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

|}

== Failed Proposals ==

{| class="wikitable sortable"
! Keyword
! Brief description
! Link to more details
! Synonyms
! Status

|-valign="top"
| bot-. . .
|
| [https://wiki.whatwg.org/index.php?title=MetaExtensions&diff=3727&oldid=3705 Old MetaExtensions revision diff] & [https://wiki.whatwg.org/index.php?title=MetaExtensions&diff=4088&oldid=3824 edit]
|
| Unendorsed

|-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

|-valign="top"
| DC.
| 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"''
| [http://www.DublinCore.org DCMI]
|
| Unendorsed

|-valign="top"
| dir-content-pointer
| No longer useful. The function is better performed with HTML markup.
| [https://wiki.whatwg.org/index.php?title=MetaExtensions&diff=3727&oldid=3705 Old MetaExtensions revision diff] & [https://wiki.whatwg.org/index.php?title=MetaExtensions&diff=10213&oldid=10212 edit]
|
| Unendorsed

|-valign="top"
| no-email-collection
| HTML5 prohibits URL-valued meta names. They should be rel keywords instead.<br />Intended to reference legal policy of web site indicating that harvesting of e-mail addresses on the site is not permitted and in violation of applicable laws such as the CAN-SPAM Act of 2003.
| [https://www.ProjectHoneyPot.org/how_to_avoid_spambots_5.php Project Honey Pot]
|
| Unendorsed

|}

[[Category:Registries]]

MediaWiki:Gadgets-definition

2020-01-01T19:33:09Z

GPHemsley: Turn on ResourceLoader for gadgets that need it; turn off ReferenceTooltips by default.

== browsing ==

* modrollback[ResourceLoader]|modrollback.js
* WatchlistChangesBold[ResourceLoader|default]|WatchlistChangesBold.css
* exlinks[ResourceLoader|dependencies=mediawiki.util|default]|exlinks.js
* revisionjumper[ResourceLoader]|revisionjumper.js
* ReferenceTooltips[ResourceLoader]|ReferenceTooltips.js|ReferenceTooltips.css

== editing ==

* HotCat[ResourceLoader]|HotCat.js
* charinsert[ResourceLoader|default]|charinsert.js|charinsert.css

== appearance ==

* edittop[ResourceLoader|default]|edittop.js
* UTCLiveClock[ResourceLoader]|UTCLiveClock.js
* PrettyLog[ResourceLoader|default]|PrettyLog.js
* widensearch[ResourceLoader|default]|widensearch.css

== compatibility ==

* DejaVu_Sans||DejaVu_Sans.css

MediaWiki:Gadgets-definition

2020-01-01T19:26:59Z

GPHemsley: https://github.com/whatwg/misc-server/issues/119

== browsing ==

* modrollback|modrollback.js
* WatchlistChangesBold[ResourceLoader|default]|WatchlistChangesBold.css
* exlinks[ResourceLoader|dependencies=mediawiki.util|default]|exlinks.js
* revisionjumper|revisionjumper.js
* ReferenceTooltips[default]|ReferenceTooltips.js|ReferenceTooltips.css

== editing ==

* HotCat[ResourceLoader]|HotCat.js
* charinsert[ResourceLoader|default]|charinsert.js|charinsert.css

== appearance ==

* edittop[default]|edittop.js
* UTCLiveClock[ResourceLoader]|UTCLiveClock.js
* PrettyLog[default]|PrettyLog.js
* widensearch[ResourceLoader|default]|widensearch.css

== compatibility ==

* DejaVu_Sans||DejaVu_Sans.css

MediaWiki:Sidebar

2017-12-03T01:31:47Z

GPHemsley: Special:PopularPages has been removed from MediaWiki

GIF

2017-11-20T20:04:35Z

GPHemsley: /* Specifications */ Add MathType; enumerate fractint application authentication codes

Animated GIFs need a spec that, in particular, specifies how to handle timings (not all browsers honor all values, so we should specify what needs to be honored exactly)

== Implementations ==

=== Gecko ===

* http://mxr.mozilla.org/mozilla-central/source/image/decoders/nsGIFDecoder2.h
* http://mxr.mozilla.org/mozilla-central/source/image/decoders/GIF2.h
* http://mxr.mozilla.org/mozilla-central/source/image/decoders/nsGIFDecoder2.cpp

=== WebKit ===

* http://trac.webkit.org/browser/trunk/Source/WebCore/platform/image-decoders/gif/GIFImageDecoder.h
* http://trac.webkit.org/browser/trunk/Source/WebCore/platform/image-decoders/gif/GIFImageReader.h
* http://trac.webkit.org/browser/trunk/Source/WebCore/platform/image-decoders/gif/GIFImageDecoder.cpp
* http://trac.webkit.org/browser/trunk/Source/WebCore/platform/image-decoders/gif/GIFImageReader.cpp
* http://trac.webkit.org/browser/trunk/Source/WebCore/platform/image-decoders/ImageDecoder.cpp

=== Blink ===

* https://chromium.googlesource.com/chromium/blink/+/master/Source/core/platform/image-decoders/gif/GIFImageDecoder.h
* https://chromium.googlesource.com/chromium/blink/+/master/Source/core/platform/image-decoders/gif/GIFImageReader.h
* https://chromium.googlesource.com/chromium/blink/+/master/Source/core/platform/image-decoders/gif/GIFImageDecoder.cpp
* https://chromium.googlesource.com/chromium/blink/+/master/Source/core/platform/image-decoders/gif/GIFImageReader.cpp
* https://chromium.googlesource.com/chromium/blink/+/master/Source/core/platform/image-decoders/ImageDecoder.cpp

=== Other ===

* http://sourceforge.net/p/giflib/code/ci/master/tree/ (giflib)
* https://github.com/jnordberg/gif.js (gif.js)
* https://github.com/deanm/omggif (omggif)
* https://github.com/avik-das/giferly (giferly)
* http://code.google.com/p/gifdotnet/source/browse/ (gifdotnet)

== References ==

=== Specifications ===

* GIF87a: [http://web.archive.org/web/20100929230301/http://www.etsimo.uniovi.es/gifanim/gif87a.txt Text] (Stanford) / [http://www.w3.org/Graphics/GIF/spec-gif87.txt Text] (W3C)
* GIF89a: [http://www.w3.org/Graphics/GIF/spec-gif89a.txt Text] / [https://web.archive.org/web/20070715193723/http://odur.let.rug.nl/~kleiweg/gif/GIF89a.html HTML]
* GIF Application Extensions:
** <code>NETSCAPE</code> <code>2.0</code>
*** [https://web.archive.org/web/20140830100320/http://odur.let.rug.nl/~kleiweg/gif/netscape.html GIF Application Extension: NETSCAPE2.0]
*** [http://www.vurdalakov.net/misc/gif/netscape-looping-application-extension Netscape Looping Application Extension]
*** [http://www.vurdalakov.net/misc/gif/netscape-buffering-application-extension Netscape Buffering Application Extension]
** <code>ANIMEXTS</code> <code>1.0</code>
*** [http://www.vurdalakov.net/misc/gif/animexts-looping-application-extension AnimExts Looping Application Extension]
** <code>ICCRGBG1</code> <code>012</code>
*** [http://www.color.org/icc1V42.pdf Specification ICC.1:2004-10 (Profile version 4.2.0.0) – Image technology colour management: Architecture, profile format, and data structure] (section B.6)
** <code>XMP Data</code> <code>XMP</code>
*** [http://wwwimages.adobe.com/www.adobe.com/content/dam/acom/en/devnet/xmp/pdfs/XMP%20SDK%20Release%20cc-2014-12/XMPSpecificationPart3.pdf XMP Specification, Part 3: Storage in Files] (section 1.1.2)
** <code>fractint</code> <code>001</code> / <code>fractint</code> <code>002</code> / <code>fractint</code> <code>003</code> / <code>fractint</code> <code>004</code> / <code>fractint</code> <code>005</code> / <code>fractint</code> <code>006</code> / <code>fractint</code> <code>007</code>
*** [http://fractint.net/fractsvn/trunk/fractint/common/encoder.c fractint encoder source code]
*** [http://fractint.net/fractsvn/trunk/fractint/common/loadfile.c fractint decoder source code], with notes and backwards compatibility for older versions of the fractint extension blocks. All of their extension blocks have names of the form <code>fractint<var>nnn</var></code>, where <code><var>nnn</var></code> is a 3 digit block number.
** <code>MathType</code> <code>001</code> / <code>MathType</code> <code>002</code> / <code>MathType</code> <code>003</code>
*** [http://www.inr.ac.ru/~blackbox/MathType/SDK/docs/baseline_gif.htm MathType baseline information]
*** [http://www.dessci.com/en/support/mathtype/tsn/tsn147.htm MathType: GIFs do not retain their DPI properties] - descriptions and sample images could be used to reverse engineer format

=== Further details ===

* [[Wikipedia:GIF]]
* [http://fileformats.archiveteam.org/wiki/GIF GIF File Format]
* [http://www.matthewflickinger.com/lab/whatsinagif/ What's in a GIF]
* [http://commandlinefanatic.com/cgi-bin/showarticle.cgi?article=art011 Command Line Fanatic: Inside the GIF file format]
* [http://www.theimage.com/animation/toc/toc.html Gifology: Understanding GIF Files & GIF Animation]
* [http://web.archive.org/web/20100929231133/http://www.etsimo.uniovi.es/gifanim/gifabout.htm All About GIF89a]

=== Test images ===

* ImageTestSuite
** [https://github.com/Wormnest/imagetestsuite/blob/wiki/GIFTestSuite.md Documentation]
** [https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/imagetestsuite/imagetestsuite-gif-1.00.tar.gz Images (Archive)]
** [https://github.com/Wormnest/imagetestsuite/tree/master/gif Images (git)]

[[Category:Spec coordination]]

GIF

2017-11-20T19:44:36Z

GPHemsley: /* References */ Fix dead links

Animated GIFs need a spec that, in particular, specifies how to handle timings (not all browsers honor all values, so we should specify what needs to be honored exactly)

== Implementations ==

=== Gecko ===

* http://mxr.mozilla.org/mozilla-central/source/image/decoders/nsGIFDecoder2.h
* http://mxr.mozilla.org/mozilla-central/source/image/decoders/GIF2.h
* http://mxr.mozilla.org/mozilla-central/source/image/decoders/nsGIFDecoder2.cpp

=== WebKit ===

* http://trac.webkit.org/browser/trunk/Source/WebCore/platform/image-decoders/gif/GIFImageDecoder.h
* http://trac.webkit.org/browser/trunk/Source/WebCore/platform/image-decoders/gif/GIFImageReader.h
* http://trac.webkit.org/browser/trunk/Source/WebCore/platform/image-decoders/gif/GIFImageDecoder.cpp
* http://trac.webkit.org/browser/trunk/Source/WebCore/platform/image-decoders/gif/GIFImageReader.cpp
* http://trac.webkit.org/browser/trunk/Source/WebCore/platform/image-decoders/ImageDecoder.cpp

=== Blink ===

* https://chromium.googlesource.com/chromium/blink/+/master/Source/core/platform/image-decoders/gif/GIFImageDecoder.h
* https://chromium.googlesource.com/chromium/blink/+/master/Source/core/platform/image-decoders/gif/GIFImageReader.h
* https://chromium.googlesource.com/chromium/blink/+/master/Source/core/platform/image-decoders/gif/GIFImageDecoder.cpp
* https://chromium.googlesource.com/chromium/blink/+/master/Source/core/platform/image-decoders/gif/GIFImageReader.cpp
* https://chromium.googlesource.com/chromium/blink/+/master/Source/core/platform/image-decoders/ImageDecoder.cpp

=== Other ===

* http://sourceforge.net/p/giflib/code/ci/master/tree/ (giflib)
* https://github.com/jnordberg/gif.js (gif.js)
* https://github.com/deanm/omggif (omggif)
* https://github.com/avik-das/giferly (giferly)
* http://code.google.com/p/gifdotnet/source/browse/ (gifdotnet)

== References ==

=== Specifications ===

* GIF87a: [http://web.archive.org/web/20100929230301/http://www.etsimo.uniovi.es/gifanim/gif87a.txt Text] (Stanford) / [http://www.w3.org/Graphics/GIF/spec-gif87.txt Text] (W3C)
* GIF89a: [http://www.w3.org/Graphics/GIF/spec-gif89a.txt Text] / [https://web.archive.org/web/20070715193723/http://odur.let.rug.nl/~kleiweg/gif/GIF89a.html HTML]
* GIF Application Extensions:
** <code>NETSCAPE</code> <code>2.0</code>
*** [https://web.archive.org/web/20140830100320/http://odur.let.rug.nl/~kleiweg/gif/netscape.html GIF Application Extension: NETSCAPE2.0]
*** [http://www.vurdalakov.net/misc/gif/netscape-looping-application-extension Netscape Looping Application Extension]
*** [http://www.vurdalakov.net/misc/gif/netscape-buffering-application-extension Netscape Buffering Application Extension]
** <code>ANIMEXTS</code> <code>1.0</code>
*** [http://www.vurdalakov.net/misc/gif/animexts-looping-application-extension AnimExts Looping Application Extension]
** <code>ICCRGBG1</code> <code>012</code>
*** [http://www.color.org/icc1V42.pdf Specification ICC.1:2004-10 (Profile version 4.2.0.0) – Image technology colour management: Architecture, profile format, and data structure] (section B.6)
** <code>XMP Data</code> <code>XMP</code>
*** [http://wwwimages.adobe.com/www.adobe.com/content/dam/acom/en/devnet/xmp/pdfs/XMP%20SDK%20Release%20cc-2014-12/XMPSpecificationPart3.pdf XMP Specification, Part 3: Storage in Files] (section 1.1.2)
** <code>fractint</code>
*** [http://fractint.net/fractsvn/trunk/fractint/common/encoder.c fractint encoder source code]
*** [http://fractint.net/fractsvn/trunk/fractint/common/loadfile.c fractint decoder source code], with notes and backwards compatibility for older versions of the fractint extension blocks. All of their extension blocks have names of the form <code>fractint<var>nnn</var></code>, where <code><var>nnn</var></code> is a 3 digit block number.

=== Further details ===

* [[Wikipedia:GIF]]
* [http://fileformats.archiveteam.org/wiki/GIF GIF File Format]
* [http://www.matthewflickinger.com/lab/whatsinagif/ What's in a GIF]
* [http://commandlinefanatic.com/cgi-bin/showarticle.cgi?article=art011 Command Line Fanatic: Inside the GIF file format]
* [http://www.theimage.com/animation/toc/toc.html Gifology: Understanding GIF Files & GIF Animation]
* [http://web.archive.org/web/20100929231133/http://www.etsimo.uniovi.es/gifanim/gifabout.htm All About GIF89a]

=== Test images ===

* ImageTestSuite
** [https://github.com/Wormnest/imagetestsuite/blob/wiki/GIFTestSuite.md Documentation]
** [https://storage.googleapis.com/google-code-archive-downloads/v2/code.google.com/imagetestsuite/imagetestsuite-gif-1.00.tar.gz Images (Archive)]
** [https://github.com/Wormnest/imagetestsuite/tree/master/gif Images (git)]

[[Category:Spec coordination]]

Contexts

2015-04-01T12:30:17Z

GPHemsley: Add link to Fetch section

== How to use a context ==

# Identify context.
# Determine whether to fetch resource based on CSP directives and type hint, if any.
# Fetch resource.
# Set no-sniff flag on resource (based on URL), if necessary.
# Handle resource.
# Sniff resource.
# Process and display resource or prompt to download resource, as appropriate.

== Context types ==

{| class="wikitable" style="text-align: center;" |
! Context
! Definition
! Used in HTML?
! Used in CSS?
! Scriptable?
! CSP Directive
! Type Hint
! [[MIME Sniffing|Sniffing]] Algorithm
|-
| browsing (navigate)
| [http://www.whatwg.org/specs/web-apps/current-work/multipage/#browsing-context HTML]
| Yes
| No?
| Yes
|
| —
| rowspan="2" | [http://mimesniff.spec.whatwg.org/#mime-type-sniffing-algorithm MIME type sniffing algorithm]
|-
| nested browsing (navigate)
| [http://www.whatwg.org/specs/web-apps/current-work/multipage/#nested-browsing-context HTML]
| Yes
| No?
| Yes
| [https://w3c.github.io/webappsec/specs/content-security-policy/#frame-src <code>frame-src</code>]
|
|-
| connection
|
| Yes
| No?
| Yes?
| [https://w3c.github.io/webappsec/specs/content-security-policy/#connect-src <code>connect-src</code>]
|
|
|-
| image
|
| Yes
| Yes
| No
| [https://w3c.github.io/webappsec/specs/content-security-policy/#img-src <code>img-src</code>]
|
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-images-specifically rules for sniffing images specifically]
|-
| audio/video
|
| Yes
| No?
| No
| [https://w3c.github.io/webappsec/specs/content-security-policy/#media-src <code>media-src</code>]
|
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-audio-and-video-specifically rules for sniffing audio and video specifically]
|-
| plugin
|
| Yes
| No?
| Yes
| [https://w3c.github.io/webappsec/specs/content-security-policy/#object-src <code>object-src</code>]
|
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-in-a-plugin-context rules for sniffing in a plugin context]
|-
| style
|
| Yes
| Yes?
| No
| [https://w3c.github.io/webappsec/specs/content-security-policy/#style-src <code>style-src</code>]
| @<code>type</code> or "<code>text/css</code>"
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-in-a-style-context rules for sniffing in a style context]
|-
| script
|
| Yes
| No?
| Yes?
| [https://w3c.github.io/webappsec/specs/content-security-policy/#script-src <code>script-src</code>]
| @<code>type</code> or "<code>text/javascript</code>"
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-in-a-script-context rules for sniffing in a script context]
|-
| font
|
| No
| Yes
| No
| [https://w3c.github.io/webappsec/specs/content-security-policy/#font-src <code>font-src</code>]
| <code>format()</code>
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-fonts-specifically rules for sniffing fonts specifically]
|-
| text track
|
| Yes
| No
| No
|
| "<code>text/vtt</code>"
|
|-
| cache manifest
|
| Yes
| No
| No
|
| "<code>text/cache-manifest</code>"
|
|}

== Context triggers ==

{| class="wikitable" |
! Context
! HTML Triggers
! CSS Triggers
! Other Triggers
|-
! browsing
|
|
|
|-
! nested browsing
| <code><iframe></code>, <code><object></code> (sometimes), <code><frame></code>
|
|
|-
! connection
|
|
| EventSource, WebSocket, XMLHttpRequest
|-
! image
| <code><img></code>, <code><link rel=icon></code>, <code><input type=image></code>, <code><object></code> (sometimes)
| <code>background-image</code>
|
|-
! audio/video
| <code><audio></code>, <code><video></code>
|
|
|-
! plugin
| <code><embed></code>, <code><object></code> (sometimes)
|
|
|-
! style
| <code><link rel=stylesheet></code>
| <code>@import</code>?
|
|-
! script
| <code><script src></code>
|
|
|-
! font
| —
| <code>@font-face</code>
| FontFace#load(), FontFaceSet#load()
|-
! text track
| <code><track></code>
| —
|
|-
! cache manifest
| <code><html manifest></code>
| —
|
|}

== Issues ==

* What about SVG?
* What about XSLT?
* document.load()? (Seems similar enough to connect-src.)
* What about CSS masks?
* What about CSS shapes?

== See also ==

* [https://fetch.spec.whatwg.org/#concept-request-context Fetch Standard: request context]

[[Category:Spec coordination]]

Specs/style

2015-02-25T01:36:32Z

GPHemsley: /* Terminology */ Equality

To be effective, specs must be written clearly and consistently, using precise and succinct language.

To facilitate those goals, it is suggested that spec editors adhere to the style guidelines set forth in this document.

== Spelling ==

; Use standard American English spelling, unless otherwise stated below.
: Continue the history of the Web and use 'en-US' spelling for your specs and the technologies they document. Consult [[wikipedia:Wikipedia:Manual of Style/Spelling|Wikipedia's Manual of Style for spelling]] for assistance.
; Use "acknowledgements" instead of "acknowledgments".
: Whenever 'dg' represents the "soft" /d͡ʒ/ sound, it should be followed by an 'e' or an 'i', to ensure it is not confused with the "hard" /dɡ/ sounds.
; Use "cannot" when something is impossible or prohibited.
: "Can not" implies a choice; "cannot" prevents one.

== Punctuation ==

; Use the Oxford comma.
: When conjoining three or more items, place a comma between the second-to-last item and the conjunction.
; Use double quotation marks for outer quotes and single quotation marks for inner quotes.
: This is slowly becoming the worldwide standard anyway, but just in case you need to be reminded.
; Where applicable, use double quotation marks for quoted terms or scare quotes and single quotation marks for literal sequences of characters.
: You ''could'' use double quotation marks for the latter, but single ones are less bulky. Besides, it's better to use semantic markup and/or styling to get the message across anyway.
; Only include between quotation marks what is actually being quoted.
: It's OK to have punctuation on the outside of a quotation mark. It's even OK to have punctuation on both sides of a quotation mark, if that's how things turn out.
; Avoid parenthesizing an entire sentence within another sentence.
: It's OK to let a parenthetical sentence stand on its own.
; Include trailing punctuation within parentheses.
: You should be able to remove a parenthetical without breaking anything around it; if you have trailing punctuation outside parentheses, removing the parenthetical will leave the punctuation orphaned.

== Terminology ==

=== Bags of bits ===

; Be careful with your use of the terms "file" and "resource".
: Make sure your definitions refer only to bags of bits, and not also to stuff in the Real World™ (like baskets of apples).

=== Collections of values ===

{| class="wikitable" style="min-width: 50em;"
|+ For a keyless collection of values, use the provided term when … and …
|-
!
! uniqueness doesn't matter
! uniqueness matters
|-
! order doesn't matter
| style="text-align: center;" | "unordered list"
| style="text-align: center;" | "set"
|-
! order matters
| style="text-align: center;" | "list"
| style="text-align: center;" | "ordered set"
|}

{| class="wikitable" style="min-width: 50em;"
|+ For a keyed collection of values, use the provided term when there can be … and …
|-
!
! only one key per value
! more than one key per value
|-
! only one value per key
| style="text-align: center;" | "bidirectional map"
| style="text-align: center;" | "map"
|-
! more than one value per key
| style="text-align: center;" | "inverse map"
| style="text-align: center;" | "multimap"
|}

; Use "object" for a map whose values can be functions.
: This helps to distinguish cases where values might not be static data types.
; Do not use "dictionary" for any collection of values.
: There is potential for confusion between a map (which, as mentioned above, can have only one value per key) and a Real World™ dictionary (which can have more than one definition per headword).

=== Willful violations of other specs ===

; When willfully and deliberately violating standards set out in other documents, use the term "willful violation" instead of simply "violation".
: "Violation" makes you sound naughty; "willful violation" makes you sound knowledgeable.
; When willfully and deliberately violating standards set out in other documents, carefully document the differences from the standards in question, as well as the rationale for each decision to differ.
: If you don't explain your decision making, there will be no incentive to follow your standard over the existing one.

=== Equality ===

; Use the form "<var>X</var> is <var>Y</var>" when defining a term.
: A definition asserts that the relationship between <var>X</var> and <var>Y</var> exists and is one of absolute equality.
: "A '''baz''' is a foo that bars."
: <code><var>X</var> === <var>Y</var></code>
; Use the form "<var>X</var> is <var>Y</var>" or "<var>X</var> is equal to <var>Y</var>" when comparing for equality.
: A conditional questions whether the relationship between <var>X</var> and <var>Y</var> is one of equality.
: "If ''baz'' is equal to ''foo'', then bar."
: <code><var>X</var> == <var>Y</var></code>
; Use the form "set <var>X</var> to <var>Y</var>" when assigning a value.
: Make all assignments explicit and unambiguous.
: "Set <var>foo</var> to 'bar'."
: <code><var>X</var> = <var>Y</var></code>

[[Category:Spec coordination|*]]

CustomElements

2015-02-02T00:31:46Z

GPHemsley: GPHemsley moved page CustomElements to Custom Elements: Space

#REDIRECT [[Custom Elements]]

Custom Elements

2015-02-02T00:31:45Z

GPHemsley: GPHemsley moved page CustomElements to Custom Elements: Space

This page documents some of the discussion about [https://w3c.github.io/webcomponents/spec/custom/ Custom Elements] in [https://lists.w3.org/Archives/Public/public-webapps/2015JanMar/ public-webapps@w3.org from January to March 2015].

== Rough consensus ==

There appears to be rough consensus for:

* ES6-style classes (Spec/Chrome: mutating prototype)
* Subclassing of HTMLElement and SVGElement
* registerElement() API to tie a class to a local name
* Lifecycle callbacks for: insertion into a document, removal from a document, mutation of an attribute

== Additional lifecycle callbacks ==

There's a proposal in various bugs to offer these lifecycle callbacks as well:

* Adopting so when moving nodes across documents adjustments can be made (e.g. an <code><img></code> has its animation restarted). This callback needs to be passed the old and new document.
* Cloning so <code>cloneNode()</code> can have similar semantics for custom elements as it does for e.g. <code><input></code>. For cloning we want the browser to create a clone (via the constructor) and copy all content attributes. Then the callback is passed the clone, a document, and the clone children flag (note that these are only needed for children not part of a tree, for elements such as <code><template></code>, children part of the tree are handled by the browser).

== Use symbols to identify lifecycle callbacks ==

It has been suggested that we should use symbols rather than names ending in <code>Callback</code> to avoid collisions with libraries.

== Upgrading ==

Upgrading is the concept of going from a piece of markup, such as <code><my-div data-teehee="💩"></my-div></code>, to an object in a tree.

{| class="wikitable"
|-
! Tactic
! Explanation
! Drawbacks
|-
! Spec/Chrome
| A basic element is created by the parser and then its prototype is mutated at a later stage followed by a callback.
|
* Does not use ES6-style classes
* Does not have identity at all (at best it looks alike due to the mutated prototype)
|-
! Brain transplant ([https://lists.w3.org/Archives/Public/public-webapps/2015JanMar/0230.html "Dmitry"])
| A basic element is created by the parser and a callback registered by the developer is invoked at a later point to turn that basic element into a custom element.
|
* Not having identity at creation-time is currently a mismatch with the rest of the platform. (Domenic suggests we could maybe change the rest of the platform.)
|-
! Dummy replacement
| A dummy element is created by the parser and replaced at a later point by an actual instance of the custom element created by invoking the constructor registered by the developer.
|
* What about attributes on the dummy element?
* What about event listeners on the dummy element?
* What if the dummy element was removed from the tree (or moved around)?
* Causes mutation observer "spam"
|-
! Synchronous constructor
| The constructor registered by the developer is invoked by the parser at the point the custom element is created and inserted into the tree.
|
* Requires synchronization for document.write() for each custom element.
* Nested event loop.
* Does not work with asynchronously loaded assets.
|-
! Almost-synchronous constructor ([https://lists.w3.org/Archives/Public/public-webapps/2014JanMar/0098.html "Jonas"])
| The parser does bookkeeping of where custom elements need to be inserted and does it at a later synchronization point.
|
* Potential performance issues.
* Complicated?
|}

(Written under the assumption that mutating the prototype of the basic element is no longer considered viable.)

== Subclassing existing elements ==

Subclassing existing elements is hard as implementation-wise identity is both object-based and name / namespace based. Therefore subclassing an existing element (currently) requires that the name / namespace does not change.

A hack was invented to make this work: <code><button is="my-button"></code>. That hack is not well liked leaving us two options:

* We leave this for now and work on this in parallel while stabilizing a smaller subset of custom elements.
* We block on this and delay even more.

However, without this hack accessibility for trivial components is harder as more things have to be done by hand.

(Assuming that not all implementers are suddenly going to be okay with this hack.)

== ARIA integration ==

https://lists.w3.org/Archives/Public/public-webapps/2014JulSep/0355.html

[[Category:Spec coordination]]

User talk:Kenrussell

2015-02-02T00:28:41Z

GPHemsley: Created page with "== Unnecessary edits == Please don't edit pages just to create links to new pages. You can create new pages by searching for a name that doesn't exist, visiting the name dire..."

== Unnecessary edits ==

Please don't edit pages just to create links to new pages. You can create new pages by searching for a name that doesn't exist, visiting the name directly via the URL, or using preview to create a link without saving the page. Thanks. —[[User:GPHemsley|GPHemsley]] ([[User talk:GPHemsley|talk]]) 00:28, 2 February 2015 (UTC)

Sanitization rules

2015-01-27T16:07:10Z

GPHemsley: +{{obsolete}}

{{obsolete}}
This page was initially seeded with the sanitization lists and rules implemented by the [http://code.google.com/p/html5lib/ html5lib] sanitizer, which in turn was based on [http://golem.ph.utexas.edu/instiki/show/HomePage Jacques Distler's branch of Instiki], which in turn was based on the sanitization logic in the [http://www.feedparser.org/ Universal Feed Parser].

It is hoped that others will add, update, and extend this list based on their experiences in their own products, and furthermore that some will update their products based on these lists. One such product is [http://htmlpurifier.org/ HTMLPurifier] ([http://intertwingly.net/stories/2007/08/11/diffs diffs]). Another product is [http://www.bloglines.com/help/css-support bloglines].

As a suggestion but not as a requirement: people who do update their products to reflect information from this list are encouraged to add a link to this page as a comment in the hopes that it will encourage subsequent maintainers to keep this page up to date.

As a convenience, [http://intertwingly.net/stories/2007/08/13/sanitize_lists.cgi this script] ([http://intertwingly.net/stories/2007/08/13/sanitize_lists.rb source]) converts these lists into a syntax shared by a number of common programming languages.

=== Acceptable Elements ===

* a
* abbr
* acronym
* address
* area
* b
* bdo
* big
* blockquote
* br
* button
* caption
* center
* cite
* code
* col
* colgroup
* dd
* del
* dfn
* dir
* div
* dl
* dt
* em
* fieldset
* font
* form
* h1
* h2
* h3
* h4
* h5
* h6
* hr
* i
* img
* input
* ins
* kbd
* label
* legend
* li
* map
* menu
* ol
* optgroup
* option
* p
* pre
* q
* s
* samp
* select
* small
* span
* strike
* strong
* sub
* sup
* table
* tbody
* td
* textarea
* tfoot
* th
* thead
* tr
* tt
* u
* ul
* var
* wbr

==== mathml Elements ====

* maction
* math
* merror
* mfrac
* mi
* mmultiscripts
* mn
* mo
* mover
* mpadded
* mphantom
* mprescripts
* mroot
* mrow
* mspace
* msqrt
* mstyle
* msub
* msubsup
* msup
* mtable
* mtd
* mtext
* mtr
* munder
* munderover
* none

==== svg Elements ====

* a
* animate
* animateColor
* animateMotion
* animateTransform
* circle
* defs
* desc
* ellipse
* font-face
* font-face-name
* font-face-src
* g
* glyph
* hkern
* image
* linearGradient
* line
* marker
* metadata
* missing-glyph
* mpath
* path
* polygon
* polyline
* radialGradient
* rect
* set
* stop
* svg
* switch
* text
* title
* tspan
* use

=== Acceptable Attributes ===

* abbr
* accept
* accept-charset
* accesskey
* action
* align
* alt
* axis
* border
* cellpadding
* cellspacing
* char
* charoff
* charset
* checked
* cite
* class
* clear
* cols
* colspan
* color
* compact
* coords
* datetime
* dir
* disabled
* enctype
* for
* frame
* headers
* height
* href
* hreflang
* hspace
* id
* ismap
* label
* lang
* longdesc
* maxlength
* media
* method
* multiple
* name
* nohref
* noshade
* nowrap
* prompt
* readonly
* rel
* rev
* rows
* rowspan
* rules
* scope
* selected
* shape
* size
* span
* src
* start
* style
* summary
* tabindex
* target
* title
* type
* usemap
* valign
* value
* vspace
* width
* xml:lang

==== mathml Attributes ====

* actiontype
* align
* columnalign
* columnalign
* columnalign
* columnlines
* columnspacing
* columnspan
* depth
* display
* displaystyle
* equalcolumns
* equalrows
* fence
* fontstyle
* fontweight
* frame
* height
* linethickness
* lspace
* mathbackground
* mathcolor
* mathvariant
* mathvariant
* maxsize
* minsize
* other
* rowalign
* rowalign
* rowalign
* rowlines
* rowspacing
* rowspan
* rspace
* scriptlevel
* selection
* separator
* stretchy
* width
* width
* xlink:href
* xlink:show
* xlink:type
* xmlns
* xmlns:xlink

==== svg Attributes ====

* accent-height
* accumulate
* additive
* alphabetic
* arabic-form
* ascent
* attributeName
* attributeType
* baseProfile
* bbox
* begin
* by
* calcMode
* cap-height
* class
* color
* color-rendering
* content
* cx
* cy
* d
* dx
* dy
* descent
* display
* dur
* end
* fill
* fill-rule
* font-family
* font-size
* font-stretch
* font-style
* font-variant
* font-weight
* from
* fx
* fy
* g1
* g2
* glyph-name
* gradientUnits
* hanging
* height
* horiz-adv-x
* horiz-origin-x
* id
* ideographic
* k
* keyPoints
* keySplines
* keyTimes
* lang
* marker-end
* marker-mid
* marker-start
* markerHeight
* markerUnits
* markerWidth
* mathematical
* max
* min
* name
* offset
* opacity
* orient
* origin
* overline-position
* overline-thickness
* panose-1
* path
* pathLength
* points
* preserveAspectRatio
* r
* refX
* refY
* repeatCount
* repeatDur
* requiredExtensions
* requiredFeatures
* restart
* rotate
* rx
* ry
* slope
* stemh
* stemv
* stop-color
* stop-opacity
* strikethrough-position
* strikethrough-thickness
* stroke
* stroke-dasharray
* stroke-dashoffset
* stroke-linecap
* stroke-linejoin
* stroke-miterlimit
* stroke-opacity
* stroke-width
* systemLanguage
* target
* text-anchor
* to
* transform
* type
* u1
* u2
* underline-position
* underline-thickness
* unicode
* unicode-range
* units-per-em
* values
* version
* viewBox
* visibility
* width
* widths
* x
* x-height
* x1
* x2
* xlink:actuate
* xlink:arcrole
* xlink:href
* xlink:role
* xlink:show
* xlink:title
* xlink:type
* xml:base
* xml:lang
* xml:space
* xmlns
* xmlns:xlink
* y
* y1
* y2
* zoomAndPan

=== CSS Rules ===

First <code>urls</code> matching the following regular expression are removed:
<pre>url\s*$\s*[^\s)]+?\s*$\s*</pre>

The style strings that don't match the following are deemed obfuscated, and ignored entirely:
<pre>^([:,;#%.\sa-zA-Z0-9!]|\w-\w|'[\s\w]+'|"[\s\w]+"|$[\d,\s]+$)*$</pre>
<pre>^(\s*[-\w]+\s*:\s*[^:;]*(;|$))*$</pre>

==== style Properties ====

* azimuth
* background, background-*
* border, border-*
* clear
* color
* cursor
* direction
* display
* elevation
* float
* font
* font-family
* font-size
* font-style
* font-variant
* font-weight
* height
* letter-spacing
* line-height
* margin, margin-*
* overflow
* padding, padding-*
* pause
* pause-after
* pause-before
* pitch
* pitch-range
* richness
* speak
* speak-header
* speak-numeral
* speak-punctuation
* speech-rate
* stress
* text-align
* text-decoration
* text-indent
* unicode-bidi
* vertical-align
* voice-family
* volume
* white-space
* width

==== style Property Values ====

* auto
* aqua
* black
* block
* blue
* bold
* both
* bottom
* brown
* center
* collapse
* dashed
* dotted
* fuchsia
* gray
* green
* !important
* italic
* left
* lime
* maroon
* medium
* none
* navy
* normal
* nowrap
* olive
* pointer
* purple
* red
* right
* solid
* silver
* teal
* top
* transparent
* underline
* white
* yellow

In addition, values that match the following regular expression are valid:

<code>^(#[0-9a-f]+|rgb$\d+%?,\d*%?,?\d*%?$?|\d{0,2}\.?\d{0,2}(cm|em|ex|in|mm|pc|pt|px|%|,|\))?)$</code>

==== svg style Properties ====

* fill
* fill-opacity
* fill-rule
* stroke
* stroke-width
* stroke-linecap
* stroke-linejoin
* stroke-opacity

=== URIs ===
==== Attributes whose value is a URI ====

* href
* src
* cite
* action
* longdesc
* xlink:href
* xml:base

==== URI schemes ====

* afs
* aim
* callto
* data (see [[#Safe data URL content types]])
* ed2k
* feed
* ftp
* gopher
* http
* https
* irc
* mailto
* news
* nntp
* rsync
* rtsp
* sftp
* ssh
* tag
* tel
* telnet
* urn
* webcal
* wtai
* xmpp

==== Safe data URL content types ====
Note: This section is being [http://wiki.whatwg.org/wiki/Talk:Sanitization_rules discussed].
* text/plain
* image/gif
* image/jpeg
* image/png

Why not conneg

2014-10-10T10:44:26Z

GPHemsley: Reverted edits by Annevk (talk) to last revision by Hsivonen

The purpose of this page is to explain what's wrong with HTTP content negotiation and why you should not suggest HTTP content negotiation as a solution to a problem.

HTTP content negotiation has four axes: negotiation by format (<code>Accept</code>), negotiation by character encoding <code>Accept-Charset</code>, negotiation by natural language (<code>Accept-Language</code>) and negotiation by compression (<code>Accept-Encoding</code>). These axes need to be discussed separately. The only one of these that shouldn't be classified as a failure is negotiation by compression, but even it shouldn't be taken as a role model considering its verbosity for basically negotiating one bit of information.

This page explains what’s wrong with each of the existing negotiation axes and then uses the HTML <code>video</code> element as an example for illustrating why HTTP-based negotiation in general is worse than letting the browser choose from alternative URLs by showing how an HTTP-based codec negotiation solution would be worse than the actual browser-side codec negotiation solution that <code>video</code> element uses.

==Negotiation by compression==

In practice, in the years HTTP has existed, a wide variety of compression methods has not cropped up. For practical purposes, there are two compression modes: uncompressed and gzipped. Google experimented with Shared Dictionary Compression over HTTP, but in practice it went nowhere on the wider Web. Even the Google-designed HTTP replacement SPDY uses gzip.

These days, all major browsers support gzipped responses. In that sense, the feature is a success. However, it is terribly wasteful that each request ends up containing 23 bytes of boilerplate. It would have been much more efficient if HTTP 1.1 had made the ability to accept gzipped responses a mandatory feature so that servers would have known that they are eligible to send a gzipped response if the request says HTTP/1.1 (or higher) rather than HTTP/1.0.

One might argue that it was important for getting from the HTTP/1.0 world to the world we have now by allowing new features to be opted into one by one and that format and protocol versions are an anti-pattern on the Web. In any case, it’s sad for the 1 bit of information to take 23 bytes—especially if HTTP is to have version number anyway and some features tied to the version number (like support for chunked responses).

==Negotiation by character encoding==

UTF-8 was introduced in 1993. By the time <code>Accept-Charset</code> was introduced, it was already obsolete in the sense that any server capable of converting to multiple encoding could have used its conversion capabilities to just convert to UTF-8. (Granted, UTF-8 support in browsers didn’t appear right away, but supporting UTF-8 sooner would have been more worthwhile than sending <code>Accept-Charset</code>.) Fortunately, we have been able to get rid of this one. Of the major browsers, only Chrome sends <code>Accept-Charset</code> anymore.

==Negotiation by natural language==

Negotiation by natural language is a failure for multiple reasons.

First, Web sites that provide content (as opposed to application user interface) in multiple languages so that the different language versions are so equally good that one language version could be selected without human judgment is actually very, very rare. When sites do have multiple language versions, the versions often are not equal. Typically, one language is the primary language for the site and the other language versions are incomplete, out of date or otherwise of low quality. Therefore, if the user can read more than one of the languages offered by the site, the user is most often best off choosing the language version to read manually by making a judgment about which language version that the user is able to read is most likely to be of highest quality. The negotiation algorithm tries to make this automatic, but in practice the algorithm is no substitute for the users human judgment.

It is slightly more common for Web applications to provide their UI strings in multiple languages. In that case, automatic choice might have a chance of working, but the user has a larger time commitment to a particular application anyway, so it is more okay for an application to provide an explicit language is UI than for a content site to require the user choose a language (which, per the previous paragraph, multilanguage content sites need to do anyway) making automatic negotiation less necessary for an application. Even though the initial value for the language preference for a Web application UI could be taken from what the browser suggests, the user starts using a new Web application so rarely relative to all HTTP requests that the user's browser makes that it is terribly wasteful for each HTTP request to broadcast the user's preferred language in case the request happens to be one whose headers and up seeding the preferences for a Web application. (And Web applications these days use JavaScript anyway and, therefore, could request the data from the browser instead of the browser broadcasting it with every HTTP request.)

Also, it's a problem that negotiation by natural language is about negotiating by a characteristic of the human user as opposed to a characteristic of software. That is, the browser doesn't really know the characteristics of the human user without the human user configuring the browser. Since negotiation by natural language is so rarely useful, it doesn't really make sense for the browser to advertise the configuration option a lot or insist that the user makes the configuration before browsing the Web. As a result, the browser doesn't really know about the user's language skills beyond guessing that the user might be able to read the UI language of the browser. And that's a pretty bad guess. It doesn't give any information about the other languages the user is able to read and the user might not even be able to actually read meaningful prose in the language of the browser UI. (You can get pretty far with the browser UI simply by knowing that you can type addresses into the location bar and that the arrow to the left takes you back to the previous page.)

Finally, there is an actual disincentive for configuring the browser: Even if everyone configured with their language preferences in their browser, the combination of languages that the person can read would partition the population of the world into rather small buckets in some cases making the language combination the way to identify a particular user or a smallish group of users. Since people so rarely configure their language preference, when someone does configure it, chances are that the configuration becomes uniquely or almost uniquely identifying. This can be seen as a privacy problem.

==Negotiating by format==

Negotiating by format is a failure because:

* It is actually rather rare that format alternatives can be chosen without knowing the user's intent. You might be able to choose automatically between different ways of compressing bitmaps, but choosing among e.g. a PDF and a Microsoft Word file might depend on the user's intent to print without reflowing lines due to different fonts on the system (PDF) or editing (Word) even if the user has software for reading both PDF and Microsoft Word files. Therefore, it makes sense to provide links to both the PDF and the Microsoft Word file and let the user choose which link to follow.

* You can’t rely on format negotiation as Web author, because there are always clients that accept something they don’t declare.

* Due to the previous point, if you are a browser vendor and another vendor has shipped a browser that doesn’t declare that it support something it supports, it doesn't make sense for you to waste bytes declaring it, either, because Web authors can’t rely (solely) on the declaration anyway.

* Negotiated responses are so rare relative to all HTTP responses that the request bloat resulting from advertising the supported formats is almost always waste.

* Past experience from the GIF to PNG transition suggests that authors are more likely to deploy one format—either the old one (with worse capabilities) or the new one (forgoing support for old browsers)—than actually bother using negotiation (as a generalization on the Web scale; there may be individual counterexamples that round to practical nothingness).

* It never pays to advertise a format once all current browsers support it but there are still old browsers that don't. (E.g. SVG as of 2013.) Since there are browsers that support the format that don't advertise it, the earlier point about not being able to rely on the declaration applies. However, since non-support is a past phenomenon, it is safe to UA sniff for the legacy browsers. If all current browsers support the format, there probably cannot be successful future browsers that don't support the format so the usual problem with you a sniffing where you assume that the current defect stays present in the future versions of a given browser does not apply.

==Server-side choice is worse for intermediate caches than browser-side choice==

Aside from script-driven HTTP requests (XHR), the HTTP requests made by browsers fall into two main categories: requests that arise from navigation
(HTML most of the time) and requests that arise from resource
inclusions (images, videos, audio, style sheets, fonts and scripts).

For resource inclusions, the server has always already sent
(unless the site uses SPDY push) an HTML document to the browser and
then the browser makes the requests in response to what it sees in
that document. That is, the server has had an opportunity to say something
to the browser already.

It is more friendly for intermediate caches for the resource (typically HTML document) that the server has alread sent to the browser to list alternative URLs for a resource inclusion request with information that allows the browser to choose which one of the URLs to fetch than to give the browser one URL and have the server vary what gets served from that URL.

Consider the actual design of the video element versus a hypothetical HTTP-based negotiation design
like this: There are no <code>source</code> elements. There is just the <code>src</code>
attribute on the <code>video</code> element. When making the request for the URL
given in the <code>src</code> attribute, the browser sends an <code>Accept-Codecs</code> HTTP
header that declares the supported container and codec combinations.
The server decides which video file to respond with depending on the
request header. The server sets the <code>Vary: Accept-Codecs</code> header on the response.

Now, intermediate caches have to use the value of the <code>Accept-Codecs</code>
header as part of the cache key.

Suppose the origin server has
two alternative video files MP4/H.264/AAC and WebM/VP8/Vorbis.
Ideally, this should result in at most two distinct cache entries and two cache keys in
an intermede cache. However, in this scenario, the worst case number for
the cache keys in the intermediary is the number of distinct
<code>Accept-Codec</code> values sent by the browsers out there.

Suppose first a browser that declares support for WebM/VP8/Vorbis request the video URL. The intermediate cache has no data for that URL yet, so it forwards the request to the origin server and caches the result with the URL and the value of the <code>Accept-Codecs</code> header as the cache key. Then another browser that declares support for MP4/H.264/AAC fetches the same URL from the same intermediate cache. The value of the <code>Accept-Codecs</code> header does not match the value in the existing cache key, so the intermediary cannot just go and serve the existing cache entry. Instead, it forwards the request to the origin server, gets a different response and makes new cache entry for that response with the URL and the different <code>Accept-Codecs</code> header value as the cache key. So now the intermediary has in its cache all the distinct video files that the origin server has for this URL. If the solution was properly cache-friendly, all subsequent requests could be served straight from the cache without consulting with the origin server until the entries' time to live expires.

But server-side negotiation isn't cache-friendly in that way. Suppose that now a browser that declares support for WebM/VP8/Vorbis ''and'' WebM/VP8/Opus makes a request for the same URL. The value of the <code>Accept-Codecs</code> header matches neither of the cache keys, so the intermediary needs to consult with the origin server even though it has cached all the possible variants already and one of them would be acceptable to this browser.

With the actual design of the video element, this problem does not occur. Each alternative video
file has a distinct URL, there is no need for the origin server to set
the Vary header and the result is as cache-friendly as possible. That
is, the worst case number of distinct cache keys is the number of
distinct videos on the origin server, so after the intermediary has cached them all, there is no need to consult with the origin server until the cache entries expire due to their age.

This example illustrates that solving the problem of choosing
between alternative resources on the HTTP level ends up being
less cache-friendly than letting the browser choose from
distinct URLs offered in the referring document.

[[Category:Justifications]]

MediaWiki:Common.css

2014-10-10T10:32:18Z

GPHemsley: Make size of anonnotice text dependent on screen size.

/* CSS placed here will be applied to all skins */

#anonNotice {
font-size: 0.75vw;
}

/* Disable the anonnotice on certain high-traffic pages. */
.page-FAQ #anonNotice {
display: none;
}

/* Limit width of legacy images on text track pages. */
.page-Use_cases_for_timed_tracks_rendered_over_video_by_the_UA img,
.page-Use_cases_for_API-level_access_to_timed_tracks img {
max-width: 400px;
}

MediaWiki:Anonnotice

2014-10-10T10:26:28Z

GPHemsley: Remove note about where to write specifications.

Contexts

2014-07-27T22:42:01Z

GPHemsley: /* Context triggers */ +Triggers

== How to use a context ==

# Identify context.
# Determine whether to fetch resource based on CSP directives and type hint, if any.
# Fetch resource.
# Set no-sniff flag on resource (based on URL), if necessary.
# Handle resource.
# Sniff resource.
# Process and display resource or prompt to download resource, as appropriate.

== Context types ==

{| class="wikitable" style="text-align: center;" |
! Context
! Definition
! Used in HTML?
! Used in CSS?
! Scriptable?
! CSP Directive
! Type Hint
! [[MIME Sniffing|Sniffing]] Algorithm
|-
| browsing (navigate)
| [http://www.whatwg.org/specs/web-apps/current-work/multipage/#browsing-context HTML]
| Yes
| No?
| Yes
|
| —
| rowspan="2" | [http://mimesniff.spec.whatwg.org/#mime-type-sniffing-algorithm MIME type sniffing algorithm]
|-
| nested browsing (navigate)
| [http://www.whatwg.org/specs/web-apps/current-work/multipage/#nested-browsing-context HTML]
| Yes
| No?
| Yes
| [https://w3c.github.io/webappsec/specs/content-security-policy/#frame-src <code>frame-src</code>]
|
|-
| connection
|
| Yes
| No?
| Yes?
| [https://w3c.github.io/webappsec/specs/content-security-policy/#connect-src <code>connect-src</code>]
|
|
|-
| image
|
| Yes
| Yes
| No
| [https://w3c.github.io/webappsec/specs/content-security-policy/#img-src <code>img-src</code>]
|
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-images-specifically rules for sniffing images specifically]
|-
| audio/video
|
| Yes
| No?
| No
| [https://w3c.github.io/webappsec/specs/content-security-policy/#media-src <code>media-src</code>]
|
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-audio-and-video-specifically rules for sniffing audio and video specifically]
|-
| plugin
|
| Yes
| No?
| Yes?
| [https://w3c.github.io/webappsec/specs/content-security-policy/#object-src <code>object-src</code>]
|
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-in-a-plugin-context rules for sniffing in a plugin context]
|-
| style
|
| Yes
| Yes?
| No
| [https://w3c.github.io/webappsec/specs/content-security-policy/#style-src <code>style-src</code>]
| @<code>type</code> or "<code>text/css</code>"
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-in-a-style-context rules for sniffing in a style context]
|-
| script
|
| Yes
| No?
| Yes?
| [https://w3c.github.io/webappsec/specs/content-security-policy/#script-src <code>script-src</code>]
| @<code>type</code> or "<code>text/javascript</code>"
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-in-a-script-context rules for sniffing in a script context]
|-
| font
|
| No
| Yes
| No
| [https://w3c.github.io/webappsec/specs/content-security-policy/#font-src <code>font-src</code>]
| <code>format()</code>
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-fonts-specifically rules for sniffing fonts specifically]
|-
| text track
|
| Yes
| No
| No
|
| "<code>text/vtt</code>"
|
|-
| cache manifest
|
| Yes
| No
| No
|
| "<code>text/cache-manifest</code>"
|
|}

== Context triggers ==

{| class="wikitable" |
! Context
! HTML Triggers
! CSS Triggers
! Other Triggers
|-
! browsing
|
|
|
|-
! nested browsing
| <code><iframe></code>, <code><object></code> (sometimes), <code><frame></code>
|
|
|-
! connection
|
|
| EventSource, WebSocket, XMLHttpRequest
|-
! image
| <code><img></code>, <code><link rel=icon></code>, <code><input type=image></code>, <code><object></code> (sometimes)
| <code>background-image</code>
|
|-
! audio/video
| <code><audio></code>, <code><video></code>
|
|
|-
! plugin
| <code><embed></code>, <code><object></code> (sometimes)
|
|
|-
! style
| <code><link rel=stylesheet></code>
| <code>@import</code>?
|
|-
! script
| <code><script src></code>
|
|
|-
! font
| —
| <code>@font-face</code>
|
|-
! text track
| <code><track></code>
| —
|
|-
! cache manifest
| <code><html manifest></code>
| —
|
|}

== Issues ==

* What about SVG?
* What about XSLT?
* document.load()? (Seems similar enough to connect-src.)
* What about CSS masks?
* What about CSS shapes?

[[Category:Spec coordination]]

Contexts

2014-07-27T22:41:39Z

GPHemsley: /* Context types */ Update CSP links.

== How to use a context ==

# Identify context.
# Determine whether to fetch resource based on CSP directives and type hint, if any.
# Fetch resource.
# Set no-sniff flag on resource (based on URL), if necessary.
# Handle resource.
# Sniff resource.
# Process and display resource or prompt to download resource, as appropriate.

== Context types ==

{| class="wikitable" style="text-align: center;" |
! Context
! Definition
! Used in HTML?
! Used in CSS?
! Scriptable?
! CSP Directive
! Type Hint
! [[MIME Sniffing|Sniffing]] Algorithm
|-
| browsing (navigate)
| [http://www.whatwg.org/specs/web-apps/current-work/multipage/#browsing-context HTML]
| Yes
| No?
| Yes
|
| —
| rowspan="2" | [http://mimesniff.spec.whatwg.org/#mime-type-sniffing-algorithm MIME type sniffing algorithm]
|-
| nested browsing (navigate)
| [http://www.whatwg.org/specs/web-apps/current-work/multipage/#nested-browsing-context HTML]
| Yes
| No?
| Yes
| [https://w3c.github.io/webappsec/specs/content-security-policy/#frame-src <code>frame-src</code>]
|
|-
| connection
|
| Yes
| No?
| Yes?
| [https://w3c.github.io/webappsec/specs/content-security-policy/#connect-src <code>connect-src</code>]
|
|
|-
| image
|
| Yes
| Yes
| No
| [https://w3c.github.io/webappsec/specs/content-security-policy/#img-src <code>img-src</code>]
|
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-images-specifically rules for sniffing images specifically]
|-
| audio/video
|
| Yes
| No?
| No
| [https://w3c.github.io/webappsec/specs/content-security-policy/#media-src <code>media-src</code>]
|
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-audio-and-video-specifically rules for sniffing audio and video specifically]
|-
| plugin
|
| Yes
| No?
| Yes?
| [https://w3c.github.io/webappsec/specs/content-security-policy/#object-src <code>object-src</code>]
|
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-in-a-plugin-context rules for sniffing in a plugin context]
|-
| style
|
| Yes
| Yes?
| No
| [https://w3c.github.io/webappsec/specs/content-security-policy/#style-src <code>style-src</code>]
| @<code>type</code> or "<code>text/css</code>"
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-in-a-style-context rules for sniffing in a style context]
|-
| script
|
| Yes
| No?
| Yes?
| [https://w3c.github.io/webappsec/specs/content-security-policy/#script-src <code>script-src</code>]
| @<code>type</code> or "<code>text/javascript</code>"
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-in-a-script-context rules for sniffing in a script context]
|-
| font
|
| No
| Yes
| No
| [https://w3c.github.io/webappsec/specs/content-security-policy/#font-src <code>font-src</code>]
| <code>format()</code>
| [http://mimesniff.spec.whatwg.org/#rules-for-sniffing-fonts-specifically rules for sniffing fonts specifically]
|-
| text track
|
| Yes
| No
| No
|
| "<code>text/vtt</code>"
|
|-
| cache manifest
|
| Yes
| No
| No
|
| "<code>text/cache-manifest</code>"
|
|}

== Context triggers ==

{| class="wikitable" |
! Context
! HTML Triggers
! CSS Triggers
! Other
|-
! browsing
|
|
|
|-
! nested browsing
| <code><iframe></code>, <code><object></code> (sometimes), <code><frame></code>
|
|
|-
! connection
|
|
| EventSource, WebSocket, XMLHttpRequest
|-
! image
| <code><img></code>, <code><link rel=icon></code>, <code><input type=image></code>, <code><object></code> (sometimes)
| <code>background-image</code>
|
|-
! audio/video
| <code><audio></code>, <code><video></code>
|
|
|-
! plugin
| <code><embed></code>, <code><object></code> (sometimes)
|
|
|-
! style
| <code><link rel=stylesheet></code>
| <code>@import</code>?
|
|-
! script
| <code><script src></code>
|
|
|-
! font
| —
| <code>@font-face</code>
|
|-
! text track
| <code><track></code>
| —
|
|-
! cache manifest
| <code><html manifest></code>
| —
|
|}

== Issues ==

* What about SVG?
* What about XSLT?
* document.load()? (Seems similar enough to connect-src.)
* What about CSS masks?
* What about CSS shapes?

[[Category:Spec coordination]]

HTTP

2014-06-26T19:44:44Z

GPHemsley: /* Content-Type parsing */ link to mimesniff algorithm

This page is an attempt to document some discrepancies between browsers and RFC 2068 (and its successor, RFC 2616) because the HTTP WG seems unwilling to resolve those issues. Hopefully one day someone writes HTTP5 and takes this into account.

== Content-Encoding ==

Under certain conditions this header needs to be stripped: http://hg.mozilla.org/mozilla-central/file/366b5c0c02d3/netwerk/protocol/http/nsHttpChannel.cpp#l4042

Not raised. Monkey patched in Fetch.

== Content-Type parsing ==

Pretty sure I (Anne) raised this at some point. A trailing ";" after a MIME type is considered invalid, but works fine in all implementations.

mnot: relevant spec - http://httpwg.github.io/specs/rfc7231.html#media.type I don't remember this being raised; we can either record it as errata or work it into the next revision.

http://mimesniff.spec.whatwg.org/#parsing-a-mime-type

== Redirects ==

For 301 and 302 redirects browsers uniformly ignore HTTP and use GET for the subsequent request if the initial request uses an unsafe method. (And the user is not prompted.)

'''Raised:''' http://lists.w3.org/Archives/Public/ietf-http-wg/2007JanMar/thread.html#msg225

mnot: See http://httpwg.github.io/specs/rfc7231.html#status.3xx

== Location header ==

Browsers handle relative URIs and URIs with invalid characters in interoperable fashion.

'''Raised:''' http://lists.w3.org/Archives/Public/ietf-http-wg/2009JanMar/thread.html#msg276

mnot: see note in: http://httpwg.github.io/specs/rfc7231.html#header.location

If there's an updated URL spec that's able to be referenced when 7231 is revised, we can point at that.

== Content-Location header ==

Browsers cannot support this header.

'''Raised:''' http://lists.w3.org/Archives/Public/ietf-http-wg/2006OctDec/thread.html#msg190

This has apparently been fixed by making Content-Location have no UA conformance criteria. (It's not clear what it's good for at this point.)

== Accept header ==

Accept header should preferably be done without spaces.

(not raised, odinho: I came across a site that didn't like the spaces, the developer said he'd gotten it off php.net or stackoverflow. He fixed the site. This could be disputed.)

== Requiring two interoperable browser implementations ==

To prove that RFC 2616 can be implemented there should be two compatible implementations in browsers.

'''Raised:''' http://lists.w3.org/Archives/Public/ietf-http-wg/2007JanMar/0222.html

mnot: That'll happen when RFC723x go to full Standard.

== Assume Vary: User-Agent ==

UAs and intermediary caches should act as if all responses had Vary: User-Agent specified since many pages on the Web serve different content depending on the User-Agent header but do not bother specifying Vary: User-Agent.

'''Raised:''' http://lists.w3.org/Archives/Public/ietf-http-wg/2012OctDec/0114.html

:You may as well not have a cache if you do this. It's hard to find two users with the same User-Agent string if you try. It varies based on minor browser version, major OS version, and in old IE doesn't it vary based on installed plugins? Yes, some pages will break if you run a transparent caching proxy and don't vary based on UA, but it will be a small minority and somewhat random, and generally they'll fix themselves if you force-refresh. (Browsers send Cache-Control: no-cache when you force-refresh, which will skip a normally-configured cache.) Even if you vary based on UA, caching proxies will break some pages, because some sites serve incorrect caching headers and a caching proxy will make you hit these more often even in the single-user case. (E.g., hitting refresh will skip browser cache for the current page but not proxy cache, right?)<p>So basically, this is a performance vs. correctness tradeoff, and the correct answer for the vast majority of users is not to have a caching proxy at all. Some will want a caching proxy that serves them some incorrect pages. No one wants a caching proxy that varies based on UA, because then the cache will be useless. The only case I could think of where this might make sense is in an office with a homogeneous browser environment, which wants caching for its standard browsers (which all have the same UA string), but still wants to be relatively correct for people using Wi-Fi on their laptops with different browsers. But it's not something that makes any sense to require across the board. [[User:Aryeh Gregor|Aryeh Gregor]] 08:45, 17 October 2012 (UTC)

mnot: Yeah, that's a really bad idea.

[[Category:Spec_coordination]]

MediaWiki:Anonnotice

2014-03-17T12:39:05Z

GPHemsley: Fix link to autoconfirmed members (h/t mithro)

<div id="anonNotice">
<div style="margin: 0.5em auto; border: 1px solid #333333; background-color: #EEEEEE; padding: 0.5em; font-size: larger; text-align: center;">
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 <span class="plainlinks">[{{fullurl:Special:ListUsers|group=autoconfirmed}} these permanent autoconfirmed members]</span>) or send an e-mail to [mailto:admin@wiki.whatwg.org admin@wiki.whatwg.org] with your desired username and an explanation of the first edit you'd like to make. (Do not use this e-mail address for any other inquiries, as they will be ignored or politely declined.)
</div>

<div style="margin: 0.5em auto; border: 1px solid #CC0000; background-color: #FFEEEE; padding: 0.5em; color: #CC0000; font-size: larger; text-align: center;">
'''Note:''' This wiki is used to supplement, not replace, specification discussions. If you would like to request changes to existing specifications, please use [[IRC]] or a [http://www.whatwg.org/mailing-list mailing list] first.
</div>
</div>

WHATWG Wiki:How to create a user account

2014-01-02T00:39:13Z

GPHemsley: The part of the password being sent by e-mail is now shown in the change UI instead of the log message, so it's OK to include trailing punctuation in the Reason field now.

If you are an autoconfirmed user, you can fulfill requests to register a new account.

The method of doing this is not necessarily intuitive, so here are the necessary steps:

# Go to [[Special:UserLogin]] and click on "Create another account". (Or go directly to the <span class="plainlinks">[{{fullurl:Special:UserLogin|type=signup}} Create account]</span> page.)
# Remove any of your info automatically filled in by your browser (username, password, e-mail address, etc.).
# Enter the requested username in the "Username" field.
# Check (tick) the box for "Use a temporary random password and send it to the specified email address".
# Enter the requested e-mail address in the "Email address" field.
# Enter the requested real name in the "Real name (optional)" field, if desired.
# Enter the request method (e-mail, IRC, etc.) in the "Reason" field.
# Submit the form by clicking the "Create another account" button.

This process will send an e-mail containing an automatically-generated password to the e-mail address provided. The user can then log in and change their password (and confirm their e-mail address) from the information in that e-mail.

WHATWG Wiki:How to create a user account

2013-12-18T20:16:54Z

GPHemsley: Update instructions for MediaWiki 1.22.

If you are an autoconfirmed user, you can fulfill requests to register a new account.

The method of doing this is not necessarily intuitive, so here are the necessary steps:

# Go to [[Special:UserLogin]] and click on "Create another account". (Or go directly to the <span class="plainlinks">[{{fullurl:Special:UserLogin|type=signup}} Create account]</span> page.)
# Remove any of your info automatically filled in by your browser (username, password, e-mail address, etc.).
# Enter the requested username in the "Username" field.
# Check (tick) the box for "Use a temporary random password and send it to the specified email address".
# Enter the requested e-mail address in the "Email address" field.
# Enter the requested real name in the "Real name (optional)" field, if desired.
# Enter the request method (e-mail, IRC, etc.) in the "Reason" field. (Leave off any trailing punctuation; it will be followed by a comma in the full log message.)
# Submit the form by clicking the "Create another account" button.

This process will send an e-mail containing an automatically-generated password to the e-mail address provided. The user can then log in and change their password (and confirm their e-mail address) from the information in that e-mail.

MediaWiki:Common.css

2013-12-18T19:39:07Z

GPHemsley: Copy over some old styles from MediaWiki:Monobook.css.

/* CSS placed here will be applied to all skins */

/* Disable the anonnotice on certain high-traffic pages. */
.page-FAQ #anonNotice {
display: none;
}

/* Limit width of legacy images on text track pages. */
.page-Use_cases_for_timed_tracks_rendered_over_video_by_the_UA img,
.page-Use_cases_for_API-level_access_to_timed_tracks img {
max-width: 400px;
}

Timed tracks

2013-12-18T19:34:44Z

GPHemsley: /* Markup */ Work around parsing issue caused by <source>.

This page contains notes for the development of the first version of timed track features in HTML.

See also [[use cases for timed tracks rendered over video by the UA]], [[use cases for API-level access to timed tracks]].

== Requirements ==

=== Subtitle/Caption/Karaoke File Format ===

* per-cue in/out times
** relative timings would be useful while editing, but may not be necessary in the published format
* inline time cues for karaoke
* bidi, newlines, ruby, italics, bold [there's been no evidence provided that there's any need for more fine-grained control at a per-cue level]
* voice selection (so that e.g. sfx descriptions and each character can be a different colour)
* per cue vertical position: % of vertical video height (default 100%)
* per cue horizontal position: % of horizontal video width (default 50%)
* per cue direction: horizontal/vertical (default horizontal)
* per cue width/height: % (default is remaining space on line given alignment)
* per cue text alignment: start/middle/end (default middle for subtitles, start for captions)
* multiple cues placed in adjacent places (e.g. from different voices or with slightly different times) would need to automatically stack so they don't overlap
** but should support multiple cues from multiple voices on the same "line", e.g. when two people both utter something at the same time (need an example of this).

(Percentage positions would work like background-position in CSS.)

==== Track-wide formatting ====
* color of background/text/outline is needed for readability on different types of video, unless UA default has clear contrasting outlines or an opaque background.
* webfonts is needed to provide high quality subtitles in some non-Latin languages (e.g. Chinese where a suitable font is unlikely to be available even on Chinese computer systems).
* providing a pseudo-element to style each voice would likely be sufficient for authors who want overall formatting control (this would also allow user overrides conveniently)

=== HTML ===

* an API and UI for exposing what timed tracks exist and selectively enabling/disabling them

* format for external subtitles/captions
* format for external audio descriptions
* some mechanism for text in the page to be used instead of external files, for subtitles/captions or audio description
* an API to allow a segment to be dynamically inserted into the rendering on the fly

* an API for exposing what the currently relevant segments of each timed track are
* a way to hook into this mechanism to advance slides

* native rendering of subtitles
* native rendering of audio descriptions
* native rendering of multiple audio or video tracks, to allow pre-recorded audio descriptions to be mixed in and sign language video to be overlaid
* a way to hook into this to manually render timed tracks

== Architecture ==

<img src="http://docs.google.com/drawings/pub?id=1GR6Pzq0GY2n1sx_ZjDfuICM2LnXxLVxzvyl4kuQy-48&w=640&h=480">

The caption format should be reasonable for either a web engine or a media engine to render, since implementation strategies may differ.

=== Declaring timed tracks ===

Each timed track is either:

*enabled, in which case it is downloaded, triggers events, and if appropriate is rendered by the user agent; or
*disabled, in which case it does nothing

The enabled/disabled state is by default based on user preferences and the kind of timed track as described below, but can be overridden on a per-track basis.

Each timed track has a kind which is one of:
* for visual display (subtitles, captions, translations), enabled based on user preferences, shows in video playback area
* for audio playback (text audio descriptions), enabled based on user preferences, renders as audio
* for navigation (chapter titles), enabled by default, shows in UA UI
* for off-video display (lyrics), disabled by default in this version, not shown by UA
* for metadata (slide timings, annotation data for app-rendered annotations), enabled by default, not shown by UA

Tracks that are for visual display or audio playback have additionally a user-facing label and a language.

Tracks that are for visual display have an additional boolean indicating if they include sound effects and speaker identification (intended for the deaf, hard of hearing, or people with sound muted) or not (i.e. translations intended for people with audio enabled but who cannot understand the language, or karaoke lyrics).

Each timed track associated with a media resource, like the media resource itself, can have multiple sources.

Each source for a timed track has:
* URL
* type (if there are multiple sources)
* media

The media resource can also imply certain timed tracks based on data in the media resource.

The script can also add "virtual" timed tracks dynamically.

==== Markup ====

<pre>
<track src="" enabled="true" kind="" label="" lang=""></track>

<track enabled="true" kind="" label="" lang="">
<source src="" type="" media="">
...
</track>
</pre>

enabled="" is true or false.

Values for kind="":

* subtitles (includes karaoke) - default
* captions
* description (text audio descriptions)
* chapters
* lyrics
* metadata

Questions:

* Should we use lang="", hreflang="", srclang=""?

* Is there a better solution to enabled=false for disabling tracks by default? Do we ever need to disable a track that might be enabled by default?

=== Visual titles ===

==== File format ====

Based on studying a broad range of [[Timed track formats]], there does not appear to be a format that is easy to read and write, supports automatic positioning to avoid overlapping titles while still supporting some level of positioning control, supports temporally-overlapping titles, uses video-independent positioning instead of pixel-based (for visual) or frame-based (for temporal) positioning, and supports some inline structure for ruby, italics, bold, and karaoke.

The two formats that are the cleanest in terms of existing syntax, that are a subset of the above feature set, and that can be extended relatively cleanly in a backwards-compatible way are the FAB subtitler format and the SRT format. The former, however, lacks much documentation. The latter appears to be more well-known.

Proposal: http://damowmow.com/temp/srtspec

==== CSS extensions ====

Cues are rendered as block boxes with inline boxes. Cues have a voice (identified by a keyword or a number). Cues can have a part that is before the current time and a part after the current time.

The block box is matched by the pseudo-element ::cue on the media element (<video>).
Only visible cues are matched (those on tracks enabled and shown by the UA whose start/end time range contains the current time).
The ::cue pseudo takes an optional argument that is the voice of cues that it is to match. The keyword "*", matching all voices, is assumed if the argument is absent.

video::cue { color: white; background: rgba(0,0,0,0.5); font: 900 sans-serif; text-transform: uppercase; }
video::cue(narrator) { color: white; font-style: italics; }
video::cue(1) { color: yellow; }
video::cue(2) { color: lime; }

The ::cue pseudo when given _two_ arguments matches all innermost inline boxes in the cue of the element that match its second argument. Its first argument is a voice; the keyword "*" matches all voices. Its second argument is one of "i", "b", "ruby", "rt" (matches inline boxes immediately inside one of those annotations), "before", "after" (fragments before/after the current time).

video::cue(*, i) { font-style: italic; }
video::cue(narrator, i) { font-style: bold; }
video::cue(*, b) { font-size: larger; }

[This isn't great. Any better ideas?]

=== DOM API ===

HTMLMediaElement
attribute MediaTrack[] tracks;
MutableMediaTrack addTrack(label, kind, language);

MediaTrack
readonly attribute DOMString label;
readonly attribute DOMString kind; // subtitles, captions, descriptions, chapters, lyrics, metadata
readonly attribute DOMString language;
readonly attribute unsigned short mode;
const unsigned short TRACK_OFF = 0; // not firing events, may not even be downloaded yet
const unsigned short TRACK_HIDDEN = 1; // firing events but otherwise ignored by UA - intended for scripts
const unsigned short TRACK_SHOWING = 2; // browser is handling it
readonly attribute MediaCue[] cues; // sorted in startTime order
readonly attribute MediaCue[] activeCues; // sorted in endTime order?
readonly attribute Function onentercue; // fires CueEvent
readonly attribute Function onexitcue; // fires CueEvent

MutableMediaTrack: MediaTrack
void addCue(cue); // throws if cue.track != null
void removeCue(cue); // throws if cue isn't in this track

MediaCue
readonly attribute MediaTrack track; // null if newly created and not yet added to a track
readonly attribute DOMString id; // empty string if not applicable
readonly attribute float startTime;
readonly attribute float endTime;
readonly attribute boolean snapToLines;
readonly attribute long linePosition;
readonly attribute long textPosition;
readonly attribute long size;
readonly attribute DOMString direction; // horizontal, vertical
readonly attribute DOMString alignment; // start, middle, end
readonly attribute DOMString voice; // for styling purposes
DOMString getCueAsSource(); // returns the cue as it was expressed in the file (for XML formats, this reserializes, expressing all namespaces appropriately)
DocumentFragment getCueAsHTML(); // returns a copy of the cue as HTML, with the current position in the case of karaoke lyrics annotated using a ProcessingInstruction or some such; throws if the format doesn't define a conversion to HTML

Constructor for MediaCue: new MediaCue(id, startTime, endTime, settings, text); // settings and text get parsed like the cues in the main format, whatever that ends up being

CueEvent
readonly attribute MediaCue cue;

HTMLTrackElement
readonly attribute MediaTrack track;

=== Other minor things ===

We need to make sure that media playback is paused until all enabled timed tracks are locally available.

We need to block cross-origin tracks (eventually blocking only those that aren't CORS-enabled).

== Open issues ==

=== Synchronised media ===

For now, sign-language and alternate or additive audio tracks (e.g. audio description tracks) have to be in-band, because UA vendors are refusing to implement synchronisation of external media tracks for now.

However, we should bear it in mind. Adding that kind of thing to the API is going to be non-trivial. The simplest way is probably to just to require that the authors use multiple <video>/<audio> elements and we link them somehow; with one designated as the "sync clock" with them all syncing to it, rather than having each <video> element expose multiple "buffered" "seekable" etc.

=== Streaming ===

Do we need to handle live transcription and streaming titles in external files? If so, how?

For now, it's not clear if there are any use case for streaming external timed track resources.

Web based radio might benefit from serving a live audio stream with song title and other details like a artist URL, but it's not clear that this needs to be a timed track (it could be a WebSocket or EventSource feed).

== Specification approach ==

# Add <track> element
# Add concept of a media element's timed tracks list
# Add algorithms to update the timed tracks list (based on <track> elements and based on the media resource)
# Add a sectioning defining WebSRT (backronymed to Web Subtitle Resource Tracks?); acknowledge SubRip in a history section - contact zuggy
#* file format — authoring requirements
#* internal data model
#* file format — downloading requirements, CORS, etc
#* file format — parsing requirements
#* processing model — rendering rules
#:See also [[SRT research]] about compatibility with existing parsers.
# Define processing model for active timed tracks — events, display, etc
# Add requirements to pause playback while active tracks load
# Add DOM API
# Add CSS extensions — propose them to CSSWG

[[Category:Proposals]]

MediaWiki:Common.css

2013-12-04T00:37:40Z

GPHemsley: Disable anonnotice on the FAQ page.

/* CSS placed here will be applied to all skins */

/* Disable the anonnotice on certain high-traffic pages. */
.page-FAQ #anonNotice {
display: none;
}

MediaWiki:Anonnotice

2013-12-04T00:34:36Z

GPHemsley: Add id="anonNotice".

<div id="anonNotice">
<div style="margin: 0.5em auto; border: 1px solid #333333; background-color: #EEEEEE; padding: 0.5em; font-size: larger; text-align: center;">
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 [[Special:ListUsers&group=autoconfirmed|these permanent autoconfirmed members]]) or send an e-mail to [mailto:admin@wiki.whatwg.org admin@wiki.whatwg.org] with your desired username and an explanation of the first edit you'd like to make. (Do not use this e-mail address for any other inquiries, as they will be ignored or politely declined.)
</div>

<div style="margin: 0.5em auto; border: 1px solid #CC0000; background-color: #FFEEEE; padding: 0.5em; color: #CC0000; font-size: larger; text-align: center;">
'''Note:''' This wiki is used to supplement, not replace, specification discussions. If you would like to request changes to existing specifications, please use [[IRC]] or a [http://www.whatwg.org/mailing-list mailing list] first.
</div>
</div>

Specs/todo

2013-12-01T19:45:13Z

GPHemsley: /* Platform */ Modern robots.txt behavior should be recorded and standardized.

There are many specifications that need editors. This page lists some of the more important ones. If you want to volunteer to edit one of these specs, contact ian@hixie.ch, post on the WHATWG mailing list or say something on [[IRC]].

== Platform ==

* A specification that defines how XML maps to DOM Core. (I think this should be in DOM Parsing and Serialization. Well really in XML.)
* X-Frames-Options (seems this is going into CSP)
* multipart/form-data
* HTTP (error handling in particular)
* APNG (other image formats too maybe?)
* HTML editing: the spec is quite mature, but needs more work
* [[Wikipedia:Robots.txt|robots.txt]]

== APIs ==

* User Interaction Events (onclick, onkeypress, etc).
** e.g. need to define somewhere that if you cancel mousedown, an element can't get focus
** setCapture / releaseCapture [http://lists.w3.org/Archives/Public/public-webapps/2008OctDec/0308.html]
** [http://krijnhoetmer.nl/irc-logs/whatwg/20121128#l-1719 selectstart] (WebKit/IE)
* An API for cryptography, to generate keys and the like
* The console.* API. [http://www.w3.org/Bugs/Public/show_bug.cgi?id=10694] [http://www.w3.org/mid/d7be01cb7077$4dd45010$e97cf030$@gmail.com] [http://sideshowbarker.github.com/console-spec/]
* Undomanager: http://rniwa.com/editing/undomanager.html and http://rniwa.com/editing/undomanager-usecases.html
* [[DOM XPath]]

== CSS ==

There are [http://www.w3.org/Style/CSS/current-work many specifications for extending CSS] that are in need of editors. The most important ones are:
* Table Layout
** http://dbaron.org/css/intrinsic/
** http://dev.w3.org/csswg/css3-tables-algorithms/Overview.src.htm
* Replaced Content
** http://dev.w3.org/csswg/css3-content/ (Do we still want this or is the component model sufficient?)
* an imperative model of box-tree construction
* hit testing per http://lists.w3.org/Archives/Public/www-style/2010Aug/0407.html

== Registries ==

Currently, the state of registries on the Web (and indeed for the Internet in general) is a disaster. At a minimum, the following registries need dramatically updating:

* MIME types
* Schemes

It's possible that the right solution is to change approach altogether (e.g. moving more to a wiki model of registries).

See also: [[Registries]]

== Miscellaneous ==
* an API to do syntax highlighting on <textarea>, <pre>, and contenteditable sections would be highly popular with Web developers (ack Ryan Johnson). (This would probably best be done as some sort of output filter at the CSS level, rather than anything HTML-specific.)
* Animated [[GIF]]s need a spec that, in particular, specifies how to handle timings (not all browsers honor all values, so we should specify what needs to be honored exactly)
* Client-side HTTP implementation requirements specification ("option 3" in http://www.w3.org/mid/20101101063413.bf1d8102.eric@bisonsystems.net)
* innerText and outerText, if browsers don't remove them entirely

== Other stuff ==

http://lists.w3.org/Archives/Public/public-html/2008Oct/0127.html has a description of some sections that needed editing in 2008 and how much work they would be.

Some notes from the HTML5 spec about things that need doing:

* a way to show icons for file types e.g. http://www.gadgetopia.com/2004/05/04/FileIconTag.html (this should probably be a function for the 'content', 'background-image' and 'list-style-image' properties in CSS)
** Maybe something like moz-icon://? http://lists.w3.org/Archives/Public/public-webapps/2010JanMar/0255.html, http://draft-icon-uri-scheme.googlecode.com/hg/draft-lafayette-icon-uri-scheme-00.html

[[Category:Spec coordination|*]]
[[Category:Specification editing]]

Specs/style

2013-11-06T22:53:11Z

GPHemsley: /* Bags of bits */ "of" -> "with"

Specs/style

2013-11-06T22:52:15Z

GPHemsley: Improve preamble.

To be effective, specs must be written clearly and consistently, using precise and succinct language.

To facilitate those goals, it is suggested that spec editors adhere to the style guidelines set forth in this document.

== Spelling ==

; Use standard American English spelling, unless otherwise stated below.
: Continue the history of the Web and use 'en-US' spelling for your specs and the technologies they document. Consult [[wikipedia:Wikipedia:Manual of Style/Spelling|Wikipedia's Manual of Style for spelling]] for assistance.
; Use "acknowledgements" instead of "acknowledgments".
: Whenever 'dg' represents the "soft" /d͡ʒ/ sound, it should be followed by an 'e' or an 'i', to ensure it is not confused with the "hard" /dɡ/ sounds.
; Use "cannot" when something is impossible or prohibited.
: "Can not" implies a choice; "cannot" prevents one.

== Punctuation ==

; Use the Oxford comma.
: When conjoining three or more items, place a comma between the second-to-last item and the conjunction.
; Use double quotation marks for outer quotes and single quotation marks for inner quotes.
: This is slowly becoming the worldwide standard anyway, but just in case you need to be reminded.
; Where applicable, use double quotation marks for quoted terms or scare quotes and single quotation marks for literal sequences of characters.
: You ''could'' use double quotation marks for the latter, but single ones are less bulky. Besides, it's better to use semantic markup and/or styling to get the message across anyway.
; Only include between quotation marks what is actually being quoted.
: It's OK to have punctuation on the outside of a quotation mark. It's even OK to have punctuation on both sides of a quotation mark, if that's how things turn out.
; Avoid parenthesizing an entire sentence within another sentence.
: It's OK to let a parenthetical sentence stand on its own.
; Include trailing punctuation within parentheses.
: You should be able to remove a parenthetical without breaking anything around it; if you have trailing punctuation outside parentheses, removing the parenthetical will leave the punctuation orphaned.

== Terminology ==

=== Bags of bits ===

; Be careful of your use of the terms "file" and "resource".
: Make sure your definitions refer only to bags of bits, and not also to stuff in the Real World™ (like baskets of apples).

=== Collections of values ===

{| class="wikitable" style="min-width: 50em;"
|+ For a keyless collection of values, use the provided term when … and …
|-
!
! uniqueness doesn't matter
! uniqueness matters
|-
! order doesn't matter
| style="text-align: center;" | "unordered list"
| style="text-align: center;" | "set"
|-
! order matters
| style="text-align: center;" | "list"
| style="text-align: center;" | "ordered set"
|}

{| class="wikitable" style="min-width: 50em;"
|+ For a keyed collection of values, use the provided term when there can be … and …
|-
!
! only one key per value
! more than one key per value
|-
! only one value per key
| style="text-align: center;" | "bidirectional map"
| style="text-align: center;" | "map"
|-
! more than one value per key
| style="text-align: center;" | "inverse map"
| style="text-align: center;" | "multimap"
|}

; Use "object" for a map whose values can be functions.
: This helps to distinguish cases where values might not be static data types.
; Do not use "dictionary" for any collection of values.
: There is potential for confusion between a map (which, as mentioned above, can have only one value per key) and a Real World™ dictionary (which can have more than one definition per headword).

=== Willful violations of other specs ===

; When willfully and deliberately violating standards set out in other documents, use the term "willful violation" instead of simply "violation".
: "Violation" makes you sound naughty; "willful violation" makes you sound knowledgeable.
; When willfully and deliberately violating standards set out in other documents, carefully document the differences from the standards in question, as well as the rationale for each decision to differ.
: If you don't explain your decision making, there will be no incentive to follow your standard over the existing one.

[[Category:Spec coordination|*]]

Specs/style

2013-11-06T22:44:23Z

GPHemsley: /* Willful violations of other specs */ +s

When writing a spec, it is suggested that you adhere to the following guidelines.

== Spelling ==

; Use standard American English spelling, unless otherwise stated below.
: Continue the history of the Web and use 'en-US' spelling for your specs and the technologies they document. Consult [[wikipedia:Wikipedia:Manual of Style/Spelling|Wikipedia's Manual of Style for spelling]] for assistance.
; Use "acknowledgements" instead of "acknowledgments".
: Whenever 'dg' represents the "soft" /d͡ʒ/ sound, it should be followed by an 'e' or an 'i', to ensure it is not confused with the "hard" /dɡ/ sounds.
; Use "cannot" when something is impossible or prohibited.
: "Can not" implies a choice; "cannot" prevents one.

== Punctuation ==

; Use the Oxford comma.
: When conjoining three or more items, place a comma between the second-to-last item and the conjunction.
; Use double quotation marks for outer quotes and single quotation marks for inner quotes.
: This is slowly becoming the worldwide standard anyway, but just in case you need to be reminded.
; Where applicable, use double quotation marks for quoted terms or scare quotes and single quotation marks for literal sequences of characters.
: You ''could'' use double quotation marks for the latter, but single ones are less bulky. Besides, it's better to use semantic markup and/or styling to get the message across anyway.
; Only include between quotation marks what is actually being quoted.
: It's OK to have punctuation on the outside of a quotation mark. It's even OK to have punctuation on both sides of a quotation mark, if that's how things turn out.
; Avoid parenthesizing an entire sentence within another sentence.
: It's OK to let a parenthetical sentence stand on its own.
; Include trailing punctuation within parentheses.
: You should be able to remove a parenthetical without breaking anything around it; if you have trailing punctuation outside parentheses, removing the parenthetical will leave the punctuation orphaned.

== Terminology ==

=== Bags of bits ===

; Be careful of your use of the terms "file" and "resource".
: Make sure your definitions refer only to bags of bits, and not also to stuff in the Real World™ (like baskets of apples).

=== Collections of values ===

{| class="wikitable" style="min-width: 50em;"
|+ For a keyless collection of values, use the provided term when … and …
|-
!
! uniqueness doesn't matter
! uniqueness matters
|-
! order doesn't matter
| style="text-align: center;" | "unordered list"
| style="text-align: center;" | "set"
|-
! order matters
| style="text-align: center;" | "list"
| style="text-align: center;" | "ordered set"
|}

{| class="wikitable" style="min-width: 50em;"
|+ For a keyed collection of values, use the provided term when there can be … and …
|-
!
! only one key per value
! more than one key per value
|-
! only one value per key
| style="text-align: center;" | "bidirectional map"
| style="text-align: center;" | "map"
|-
! more than one value per key
| style="text-align: center;" | "inverse map"
| style="text-align: center;" | "multimap"
|}

; Use "object" for a map whose values can be functions.
: This helps to distinguish cases where values might not be static data types.
; Do not use "dictionary" for any collection of values.
: There is potential for confusion between a map (which, as mentioned above, can have only one value per key) and a Real World™ dictionary (which can have more than one definition per headword).

=== Willful violations of other specs ===

; When willfully and deliberately violating standards set out in other documents, use the term "willful violation" instead of simply "violation".
: "Violation" makes you sound naughty; "willful violation" makes you sound knowledgeable.
; When willfully and deliberately violating standards set out in other documents, carefully document the differences from the standards in question, as well as the rationale for each decision to differ.
: If you don't explain your decision making, there will be no incentive to follow your standard over the existing one.

[[Category:Spec coordination|*]]

Specs/style

2013-11-06T22:43:50Z

GPHemsley: /* Willful violations of other specs */ Add guideline about explicitly documenting willful violations.

When writing a spec, it is suggested that you adhere to the following guidelines.

== Spelling ==

; Use standard American English spelling, unless otherwise stated below.
: Continue the history of the Web and use 'en-US' spelling for your specs and the technologies they document. Consult [[wikipedia:Wikipedia:Manual of Style/Spelling|Wikipedia's Manual of Style for spelling]] for assistance.
; Use "acknowledgements" instead of "acknowledgments".
: Whenever 'dg' represents the "soft" /d͡ʒ/ sound, it should be followed by an 'e' or an 'i', to ensure it is not confused with the "hard" /dɡ/ sounds.
; Use "cannot" when something is impossible or prohibited.
: "Can not" implies a choice; "cannot" prevents one.

== Punctuation ==

; Use the Oxford comma.
: When conjoining three or more items, place a comma between the second-to-last item and the conjunction.
; Use double quotation marks for outer quotes and single quotation marks for inner quotes.
: This is slowly becoming the worldwide standard anyway, but just in case you need to be reminded.
; Where applicable, use double quotation marks for quoted terms or scare quotes and single quotation marks for literal sequences of characters.
: You ''could'' use double quotation marks for the latter, but single ones are less bulky. Besides, it's better to use semantic markup and/or styling to get the message across anyway.
; Only include between quotation marks what is actually being quoted.
: It's OK to have punctuation on the outside of a quotation mark. It's even OK to have punctuation on both sides of a quotation mark, if that's how things turn out.
; Avoid parenthesizing an entire sentence within another sentence.
: It's OK to let a parenthetical sentence stand on its own.
; Include trailing punctuation within parentheses.
: You should be able to remove a parenthetical without breaking anything around it; if you have trailing punctuation outside parentheses, removing the parenthetical will leave the punctuation orphaned.

== Terminology ==

=== Bags of bits ===

; Be careful of your use of the terms "file" and "resource".
: Make sure your definitions refer only to bags of bits, and not also to stuff in the Real World™ (like baskets of apples).

=== Collections of values ===

{| class="wikitable" style="min-width: 50em;"
|+ For a keyless collection of values, use the provided term when … and …
|-
!
! uniqueness doesn't matter
! uniqueness matters
|-
! order doesn't matter
| style="text-align: center;" | "unordered list"
| style="text-align: center;" | "set"
|-
! order matters
| style="text-align: center;" | "list"
| style="text-align: center;" | "ordered set"
|}

{| class="wikitable" style="min-width: 50em;"
|+ For a keyed collection of values, use the provided term when there can be … and …
|-
!
! only one key per value
! more than one key per value
|-
! only one value per key
| style="text-align: center;" | "bidirectional map"
| style="text-align: center;" | "map"
|-
! more than one value per key
| style="text-align: center;" | "inverse map"
| style="text-align: center;" | "multimap"
|}

; Use "object" for a map whose values can be functions.
: This helps to distinguish cases where values might not be static data types.
; Do not use "dictionary" for any collection of values.
: There is potential for confusion between a map (which, as mentioned above, can have only one value per key) and a Real World™ dictionary (which can have more than one definition per headword).

=== Willful violations of other specs ===

; When willfully and deliberately violating standards set out in other documents, use the term "willful violation" instead of simply "violation".
: "Violation" makes you sound naughty; "willful violation" makes you sound knowledgeable.
; When willfully and deliberately violating standards set out in other documents, carefully document the differences from the standard in question, as well as the rationale for each decision to differ.
: If you don't explain your decision making, there will be no incentive to follow your standard over the existing one.

[[Category:Spec coordination|*]]

Specs/style

2013-11-06T22:35:03Z

GPHemsley: /* Punctuation */ Add the Oxford comma.

Specs/style

2013-11-06T21:10:15Z

GPHemsley: /* Collections of values */ Try to reduce confusion around the "and".

When writing a spec, it is suggested that you adhere to the following guidelines.

== Spelling ==

; Use standard American English spelling, unless otherwise stated below.
: Continue the history of the Web and use 'en-US' spelling for your specs and the technologies they document. Consult [[wikipedia:Wikipedia:Manual of Style/Spelling|Wikipedia's Manual of Style for spelling]] for assistance.
; Use "acknowledgements" instead of "acknowledgments".
: Whenever 'dg' represents the "soft" /d͡ʒ/ sound, it should be followed by an 'e' or an 'i', to ensure it is not confused with the "hard" /dɡ/ sounds.
; Use "cannot" when something is impossible or prohibited.
: "Can not" implies a choice; "cannot" prevents one.

== Punctuation ==

; Use double quotation marks for outer quotes and single quotation marks for inner quotes.
: This is slowly becoming the worldwide standard anyway, but just in case you need to be reminded.
; Where applicable, use double quotation marks for quoted terms or scare quotes and single quotation marks for literal sequences of characters.
: You ''could'' use double quotation marks for the latter, but single ones are less bulky. Besides, it's better to use semantic markup and/or styling to get the message across anyway.
; Only include between quotation marks what is actually being quoted.
: It's OK to have punctuation on the outside of a quotation mark. It's even OK to have punctuation on both sides of a quotation mark, if that's how things turn out.
; Avoid parenthesizing an entire sentence within another sentence.
: It's OK to let a parenthetical sentence stand on its own.
; Include trailing punctuation within parentheses.
: You should be able to remove a parenthetical without breaking anything around it; if you have trailing punctuation outside parentheses, removing the parenthetical will leave the punctuation orphaned.

== Terminology ==

=== Bags of bits ===

; Be careful of your use of the terms "file" and "resource".
: Make sure your definitions refer only to bags of bits, and not also to stuff in the Real World™ (like baskets of apples).

=== Collections of values ===

{| class="wikitable" style="min-width: 50em;"
|+ For a keyless collection of values, use the provided term when … and …
|-
!
! uniqueness doesn't matter
! uniqueness matters
|-
! order doesn't matter
| style="text-align: center;" | "unordered list"
| style="text-align: center;" | "set"
|-
! order matters
| style="text-align: center;" | "list"
| style="text-align: center;" | "ordered set"
|}

{| class="wikitable" style="min-width: 50em;"
|+ For a keyed collection of values, use the provided term when there can be … and …
|-
!
! only one key per value
! more than one key per value
|-
! only one value per key
| style="text-align: center;" | "bidirectional map"
| style="text-align: center;" | "map"
|-
! more than one value per key
| style="text-align: center;" | "inverse map"
| style="text-align: center;" | "multimap"
|}

; Use "object" for a map whose values can be functions.
: This helps to distinguish cases where values might not be static data types.
; Do not use "dictionary" for any collection of values.
: There is potential for confusion between a map (which, as mentioned above, can have only one value per key) and a Real World™ dictionary (which can have more than one definition per headword).

=== Willful violations of other specs ===

; When willfully and deliberately violating standards set out in other documents, use the term "willful violation" instead of simply "violation".
: "Violation" makes you sound naughty; "willful violation" makes you sound knowledgeable.

[[Category:Spec coordination|*]]

Specs/style

2013-11-06T21:07:06Z

GPHemsley: /* Spelling */ Remove the "-log(ue)" rule because it's causing too much confusion and raising too many exceptions.

When writing a spec, it is suggested that you adhere to the following guidelines.

== Spelling ==

; Use standard American English spelling, unless otherwise stated below.
: Continue the history of the Web and use 'en-US' spelling for your specs and the technologies they document. Consult [[wikipedia:Wikipedia:Manual of Style/Spelling|Wikipedia's Manual of Style for spelling]] for assistance.
; Use "acknowledgements" instead of "acknowledgments".
: Whenever 'dg' represents the "soft" /d͡ʒ/ sound, it should be followed by an 'e' or an 'i', to ensure it is not confused with the "hard" /dɡ/ sounds.
; Use "cannot" when something is impossible or prohibited.
: "Can not" implies a choice; "cannot" prevents one.

== Punctuation ==

; Use double quotation marks for outer quotes and single quotation marks for inner quotes.
: This is slowly becoming the worldwide standard anyway, but just in case you need to be reminded.
; Where applicable, use double quotation marks for quoted terms or scare quotes and single quotation marks for literal sequences of characters.
: You ''could'' use double quotation marks for the latter, but single ones are less bulky. Besides, it's better to use semantic markup and/or styling to get the message across anyway.
; Only include between quotation marks what is actually being quoted.
: It's OK to have punctuation on the outside of a quotation mark. It's even OK to have punctuation on both sides of a quotation mark, if that's how things turn out.
; Avoid parenthesizing an entire sentence within another sentence.
: It's OK to let a parenthetical sentence stand on its own.
; Include trailing punctuation within parentheses.
: You should be able to remove a parenthetical without breaking anything around it; if you have trailing punctuation outside parentheses, removing the parenthetical will leave the punctuation orphaned.

== Terminology ==

=== Bags of bits ===

; Be careful of your use of the terms "file" and "resource".
: Make sure your definitions refer only to bags of bits, and not also to stuff in the Real World™ (like baskets of apples).

=== Collections of values ===

{| class="wikitable" style="min-width: 40em;"
|+ For a keyless collection of values, use the following term when…
|-
! and
! uniqueness doesn't matter
! uniqueness matters
|-
! order doesn't matter
| style="text-align: center;" | "unordered list"
| style="text-align: center;" | "set"
|-
! order matters
| style="text-align: center;" | "list"
| style="text-align: center;" | "ordered set"
|}

{| class="wikitable" style="min-width: 40em;"
|+ For a keyed collection of values, use the following term when there can be…
|-
! and
! only one key per value
! more than one key per value
|-
! only one value per key
| style="text-align: center;" | "bidirectional map"
| style="text-align: center;" | "map"
|-
! more than one value per key
| style="text-align: center;" | "inverse map"
| style="text-align: center;" | "multimap"
|}

; Use "object" for a map whose values can be functions.
: This helps to distinguish cases where values might not be static data types.
; Do not use "dictionary" for any collection of values.
: There is potential for confusion between a map (which, as mentioned above, can have only one value per key) and a Real World™ dictionary (which can have more than one definition per headword).

=== Willful violations of other specs ===

; When willfully and deliberately violating standards set out in other documents, use the term "willful violation" instead of simply "violation".
: "Violation" makes you sound naughty; "willful violation" makes you sound knowledgeable.

[[Category:Spec coordination|*]]

Specs/style

2013-11-06T21:00:45Z

GPHemsley: /* Spelling */ Try to clarify the distinction between "dialogue" and "dialog" for the purposes of the guideline.

When writing a spec, it is suggested that you adhere to the following guidelines.

== Spelling ==

; Use standard American English spelling, unless otherwise stated below.
: Continue the history of the Web and use 'en-US' spelling for your specs and the technologies they document. Consult [[wikipedia:Wikipedia:Manual of Style/Spelling|Wikipedia's Manual of Style for spelling]] for assistance.
; Use "acknowledgements" instead of "acknowledgments".
: Whenever 'dg' represents the "soft" /d͡ʒ/ sound, it should be followed by an 'e' or an 'i', to ensure it is not confused with the "hard" /dɡ/ sounds.
; Use "dialogue" for the definitive noun (the conversation) and "dialog" for the adjectival noun (the box on the screen) and all other parts of speech.
: Whenever a word has a '-log(ue)' dichotomy, only keep '-ue' for the definitive noun: "monologue", "dialog box", "catalogging", "homologous".
; Use "cannot" when something is impossible or prohibited.
: "Can not" implies a choice; "cannot" prevents one.

== Punctuation ==

; Use double quotation marks for outer quotes and single quotation marks for inner quotes.
: This is slowly becoming the worldwide standard anyway, but just in case you need to be reminded.
; Where applicable, use double quotation marks for quoted terms or scare quotes and single quotation marks for literal sequences of characters.
: You ''could'' use double quotation marks for the latter, but single ones are less bulky. Besides, it's better to use semantic markup and/or styling to get the message across anyway.
; Only include between quotation marks what is actually being quoted.
: It's OK to have punctuation on the outside of a quotation mark. It's even OK to have punctuation on both sides of a quotation mark, if that's how things turn out.
; Avoid parenthesizing an entire sentence within another sentence.
: It's OK to let a parenthetical sentence stand on its own.
; Include trailing punctuation within parentheses.
: You should be able to remove a parenthetical without breaking anything around it; if you have trailing punctuation outside parentheses, removing the parenthetical will leave the punctuation orphaned.

== Terminology ==

=== Bags of bits ===

; Be careful of your use of the terms "file" and "resource".
: Make sure your definitions refer only to bags of bits, and not also to stuff in the Real World™ (like baskets of apples).

=== Collections of values ===

{| class="wikitable" style="min-width: 40em;"
|+ For a keyless collection of values, use the following term when…
|-
! and
! uniqueness doesn't matter
! uniqueness matters
|-
! order doesn't matter
| style="text-align: center;" | "unordered list"
| style="text-align: center;" | "set"
|-
! order matters
| style="text-align: center;" | "list"
| style="text-align: center;" | "ordered set"
|}

{| class="wikitable" style="min-width: 40em;"
|+ For a keyed collection of values, use the following term when there can be…
|-
! and
! only one key per value
! more than one key per value
|-
! only one value per key
| style="text-align: center;" | "bidirectional map"
| style="text-align: center;" | "map"
|-
! more than one value per key
| style="text-align: center;" | "inverse map"
| style="text-align: center;" | "multimap"
|}

; Use "object" for a map whose values can be functions.
: This helps to distinguish cases where values might not be static data types.
; Do not use "dictionary" for any collection of values.
: There is potential for confusion between a map (which, as mentioned above, can have only one value per key) and a Real World™ dictionary (which can have more than one definition per headword).

=== Willful violations of other specs ===

; When willfully and deliberately violating standards set out in other documents, use the term "willful violation" instead of simply "violation".
: "Violation" makes you sound naughty; "willful violation" makes you sound knowledgeable.

[[Category:Spec coordination|*]]

Specs/style

2013-11-06T20:31:20Z

GPHemsley: /* Collections of values */ Do not use "dictionary" for any collection of values.

When writing a spec, it is suggested that you adhere to the following guidelines.

== Spelling ==

; Use standard American English spelling, unless otherwise stated below.
: Continue the history of the Web and use 'en-US' spelling for your specs and the technologies they document. Consult [[wikipedia:Wikipedia:Manual of Style/Spelling|Wikipedia's Manual of Style for spelling]] for assistance.
; Use "acknowledgements" instead of "acknowledgments".
: Whenever 'dg' represents the "soft" /d͡ʒ/ sound, it should be followed by an 'e' or an 'i', to ensure it is not confused with the "hard" /dɡ/ sounds.
; Use "dialogue" for the noun and "dialog" for all other parts of speech.
: Whenever a word has a '-log(ue)' dichotomy, only keep '-ue' for the definitive noun: "monologue", "dialog box", "catalogging", "homologous".
; Use "cannot" when something is impossible or prohibited.
: "Can not" implies a choice; "cannot" prevents one.

== Punctuation ==

; Use double quotation marks for outer quotes and single quotation marks for inner quotes.
: This is slowly becoming the worldwide standard anyway, but just in case you need to be reminded.
; Where applicable, use double quotation marks for quoted terms or scare quotes and single quotation marks for literal sequences of characters.
: You ''could'' use double quotation marks for the latter, but single ones are less bulky. Besides, it's better to use semantic markup and/or styling to get the message across anyway.
; Only include between quotation marks what is actually being quoted.
: It's OK to have punctuation on the outside of a quotation mark. It's even OK to have punctuation on both sides of a quotation mark, if that's how things turn out.
; Avoid parenthesizing an entire sentence within another sentence.
: It's OK to let a parenthetical sentence stand on its own.
; Include trailing punctuation within parentheses.
: You should be able to remove a parenthetical without breaking anything around it; if you have trailing punctuation outside parentheses, removing the parenthetical will leave the punctuation orphaned.

== Terminology ==

=== Bags of bits ===

; Be careful of your use of the terms "file" and "resource".
: Make sure your definitions refer only to bags of bits, and not also to stuff in the Real World™ (like baskets of apples).

=== Collections of values ===

{| class="wikitable" style="min-width: 40em;"
|+ For a keyless collection of values, use the following term when…
|-
! and
! uniqueness doesn't matter
! uniqueness matters
|-
! order doesn't matter
| style="text-align: center;" | "unordered list"
| style="text-align: center;" | "set"
|-
! order matters
| style="text-align: center;" | "list"
| style="text-align: center;" | "ordered set"
|}

{| class="wikitable" style="min-width: 40em;"
|+ For a keyed collection of values, use the following term when there can be…
|-
! and
! only one key per value
! more than one key per value
|-
! only one value per key
| style="text-align: center;" | "bidirectional map"
| style="text-align: center;" | "map"
|-
! more than one value per key
| style="text-align: center;" | "inverse map"
| style="text-align: center;" | "multimap"
|}

; Use "object" for a map whose values can be functions.
: This helps to distinguish cases where values might not be static data types.
; Do not use "dictionary" for any collection of values.
: There is potential for confusion between a map (which, as mentioned above, can have only one value per key) and a Real World™ dictionary (which can have more than one definition per headword).

=== Willful violations of other specs ===

; When willfully and deliberately violating standards set out in other documents, use the term "willful violation" instead of simply "violation".
: "Violation" makes you sound naughty; "willful violation" makes you sound knowledgeable.

[[Category:Spec coordination|*]]

Specs/style

2013-11-06T20:22:43Z

GPHemsley: /* Bags of bits */ to

When writing a spec, it is suggested that you adhere to the following guidelines.

== Spelling ==

; Use standard American English spelling, unless otherwise stated below.
: Continue the history of the Web and use 'en-US' spelling for your specs and the technologies they document. Consult [[wikipedia:Wikipedia:Manual of Style/Spelling|Wikipedia's Manual of Style for spelling]] for assistance.
; Use "acknowledgements" instead of "acknowledgments".
: Whenever 'dg' represents the "soft" /d͡ʒ/ sound, it should be followed by an 'e' or an 'i', to ensure it is not confused with the "hard" /dɡ/ sounds.
; Use "dialogue" for the noun and "dialog" for all other parts of speech.
: Whenever a word has a '-log(ue)' dichotomy, only keep '-ue' for the definitive noun: "monologue", "dialog box", "catalogging", "homologous".
; Use "cannot" when something is impossible or prohibited.
: "Can not" implies a choice; "cannot" prevents one.

== Punctuation ==

; Use double quotation marks for outer quotes and single quotation marks for inner quotes.
: This is slowly becoming the worldwide standard anyway, but just in case you need to be reminded.
; Where applicable, use double quotation marks for quoted terms or scare quotes and single quotation marks for literal sequences of characters.
: You ''could'' use double quotation marks for the latter, but single ones are less bulky. Besides, it's better to use semantic markup and/or styling to get the message across anyway.
; Only include between quotation marks what is actually being quoted.
: It's OK to have punctuation on the outside of a quotation mark. It's even OK to have punctuation on both sides of a quotation mark, if that's how things turn out.
; Avoid parenthesizing an entire sentence within another sentence.
: It's OK to let a parenthetical sentence stand on its own.
; Include trailing punctuation within parentheses.
: You should be able to remove a parenthetical without breaking anything around it; if you have trailing punctuation outside parentheses, removing the parenthetical will leave the punctuation orphaned.

== Terminology ==

=== Bags of bits ===

; Be careful of your use of the terms "file" and "resource".
: Make sure your definitions refer only to bags of bits, and not also to stuff in the Real World™ (like baskets of apples).

=== Collections of values ===

{| class="wikitable" style="min-width: 40em;"
|+ For a keyless collection of values, use the following term when…
|-
! and
! uniqueness doesn't matter
! uniqueness matters
|-
! order doesn't matter
| style="text-align: center;" | "unordered list"
| style="text-align: center;" | "set"
|-
! order matters
| style="text-align: center;" | "list"
| style="text-align: center;" | "ordered set"
|}

{| class="wikitable" style="min-width: 40em;"
|+ For a keyed collection of values, use the following term when there can be…
|-
! and
! only one key per value
! more than one key per value
|-
! only one value per key
| style="text-align: center;" | "bidirectional map"
| style="text-align: center;" | "map"
|-
! more than one value per key
| style="text-align: center;" | "inverse map"
| style="text-align: center;" | "multimap"
|}

; Use "object" for a map whose values can be functions.
: This helps to distinguish cases where values might not be static data types.

=== Willful violations of other specs ===

; When willfully and deliberately violating standards set out in other documents, use the term "willful violation" instead of simply "violation".
: "Violation" makes you sound naughty; "willful violation" makes you sound knowledgeable.

[[Category:Spec coordination|*]]

Specs/style

2013-11-06T20:21:48Z

GPHemsley: /* Punctuation */ Add some more notes about quotation marks.

When writing a spec, it is suggested that you adhere to the following guidelines.

== Spelling ==

; Use standard American English spelling, unless otherwise stated below.
: Continue the history of the Web and use 'en-US' spelling for your specs and the technologies they document. Consult [[wikipedia:Wikipedia:Manual of Style/Spelling|Wikipedia's Manual of Style for spelling]] for assistance.
; Use "acknowledgements" instead of "acknowledgments".
: Whenever 'dg' represents the "soft" /d͡ʒ/ sound, it should be followed by an 'e' or an 'i', to ensure it is not confused with the "hard" /dɡ/ sounds.
; Use "dialogue" for the noun and "dialog" for all other parts of speech.
: Whenever a word has a '-log(ue)' dichotomy, only keep '-ue' for the definitive noun: "monologue", "dialog box", "catalogging", "homologous".
; Use "cannot" when something is impossible or prohibited.
: "Can not" implies a choice; "cannot" prevents one.

== Punctuation ==

; Use double quotation marks for outer quotes and single quotation marks for inner quotes.
: This is slowly becoming the worldwide standard anyway, but just in case you need to be reminded.
; Where applicable, use double quotation marks for quoted terms or scare quotes and single quotation marks for literal sequences of characters.
: You ''could'' use double quotation marks for the latter, but single ones are less bulky. Besides, it's better to use semantic markup and/or styling to get the message across anyway.
; Only include between quotation marks what is actually being quoted.
: It's OK to have punctuation on the outside of a quotation mark. It's even OK to have punctuation on both sides of a quotation mark, if that's how things turn out.
; Avoid parenthesizing an entire sentence within another sentence.
: It's OK to let a parenthetical sentence stand on its own.
; Include trailing punctuation within parentheses.
: You should be able to remove a parenthetical without breaking anything around it; if you have trailing punctuation outside parentheses, removing the parenthetical will leave the punctuation orphaned.

== Terminology ==

=== Bags of bits ===

; Be careful of your use of the terms "file" and "resource".
: Make sure your definitions refer only to bags of bits, and not also stuff in the Real World™ (like baskets of apples).

=== Collections of values ===

{| class="wikitable" style="min-width: 40em;"
|+ For a keyless collection of values, use the following term when…
|-
! and
! uniqueness doesn't matter
! uniqueness matters
|-
! order doesn't matter
| style="text-align: center;" | "unordered list"
| style="text-align: center;" | "set"
|-
! order matters
| style="text-align: center;" | "list"
| style="text-align: center;" | "ordered set"
|}

{| class="wikitable" style="min-width: 40em;"
|+ For a keyed collection of values, use the following term when there can be…
|-
! and
! only one key per value
! more than one key per value
|-
! only one value per key
| style="text-align: center;" | "bidirectional map"
| style="text-align: center;" | "map"
|-
! more than one value per key
| style="text-align: center;" | "inverse map"
| style="text-align: center;" | "multimap"
|}

; Use "object" for a map whose values can be functions.
: This helps to distinguish cases where values might not be static data types.

=== Willful violations of other specs ===

; When willfully and deliberately violating standards set out in other documents, use the term "willful violation" instead of simply "violation".
: "Violation" makes you sound naughty; "willful violation" makes you sound knowledgeable.

[[Category:Spec coordination|*]]

Specs/style

2013-11-06T20:11:56Z

GPHemsley: Add section on punctuation.

When writing a spec, it is suggested that you adhere to the following guidelines.

== Spelling ==

; Use standard American English spelling, unless otherwise stated below.
: Continue the history of the Web and use 'en-US' spelling for your specs and the technologies they document. Consult [[wikipedia:Wikipedia:Manual of Style/Spelling|Wikipedia's Manual of Style for spelling]] for assistance.
; Use "acknowledgements" instead of "acknowledgments".
: Whenever 'dg' represents the "soft" /d͡ʒ/ sound, it should be followed by an 'e' or an 'i', to ensure it is not confused with the "hard" /dɡ/ sounds.
; Use "dialogue" for the noun and "dialog" for all other parts of speech.
: Whenever a word has a '-log(ue)' dichotomy, only keep '-ue' for the definitive noun: "monologue", "dialog box", "catalogging", "homologous".
; Use "cannot" when something is impossible or prohibited.
: "Can not" implies a choice; "cannot" prevents one.

== Punctuation ==

; Only include between quotation marks what is actually being quoted.
: It's OK to have punctuation on the outside of a quotation mark. It's even OK to have punctuation on both sides of a quotation mark, if that's how things turn out.
; Avoid parenthesizing an entire sentence within another sentence.
: It's OK to have a parenthetical sentence stand on its own.
; Include trailing punctuation within parentheses.
: You should be able to remove a parenthetical without breaking anything around it; if you have trailing punctuation outside parentheses, removing the parenthetical will leave the punctuation orphaned.

== Terminology ==

=== Bags of bits ===

; Be careful of your use of the terms "file" and "resource".
: Make sure your definitions refer only to bags of bits, and not also stuff in the Real World™ (like baskets of apples).

=== Collections of values ===

{| class="wikitable" style="min-width: 40em;"
|+ For a keyless collection of values, use the following term when…
|-
! and
! uniqueness doesn't matter
! uniqueness matters
|-
! order doesn't matter
| style="text-align: center;" | "unordered list"
| style="text-align: center;" | "set"
|-
! order matters
| style="text-align: center;" | "list"
| style="text-align: center;" | "ordered set"
|}

{| class="wikitable" style="min-width: 40em;"
|+ For a keyed collection of values, use the following term when there can be…
|-
! and
! only one key per value
! more than one key per value
|-
! only one value per key
| style="text-align: center;" | "bidirectional map"
| style="text-align: center;" | "map"
|-
! more than one value per key
| style="text-align: center;" | "inverse map"
| style="text-align: center;" | "multimap"
|}

; Use "object" for a map whose values can be functions.
: This helps to distinguish cases where values might not be static data types.

=== Willful violations of other specs ===

; When willfully and deliberately violating standards set out in other documents, use the term "willful violation" instead of simply "violation".
: "Violation" makes you sound naughty; "willful violation" makes you sound knowledgeable.

[[Category:Spec coordination|*]]

Specs/style

2013-11-06T18:46:24Z

GPHemsley: /* Collections of values */ "dictionary" -> "multimap"

Specs/style

2013-11-06T18:38:31Z

GPHemsley: /* Collections of values */ "strict dictionary" -> "inverse map"

Specs/style

2013-11-06T18:25:00Z

GPHemsley: /* Terminology */ Add guidelines for terms for collections of values.

Specs/style

2013-11-06T16:15:53Z

GPHemsley: /* Spelling */ see -> consult

Specs/style

2013-11-06T16:14:27Z

GPHemsley: /* Spelling */ Move "unless otherwise stated" to the end, so spelling guidelines all start with "use".

Specs/style

2013-11-06T16:12:43Z

GPHemsley: /* Spelling */ Use "cannot".

When writing a spec, it is suggested that you adhere to the following guidelines.

== Spelling ==

; Unless otherwise stated, use standard American English spelling.
: Continue the history of the Web and use 'en-US' spelling for your specs and the technologies they document. See [[wikipedia:Wikipedia:Manual of Style/Spelling|Wikipedia's Manual of Style for spelling]] for assistance.
; Use "acknowledgements" instead of "acknowledgments".
: Whenever 'dg' represents the "soft" /d͡ʒ/ sound, it should be followed by an 'e' or an 'i', to ensure it is not confused with the "hard" /dɡ/ sounds.
; Use "dialogue" for the noun and "dialog" for all other parts of speech.
: Whenever a word has a '-log(ue)' dichotomy, only keep '-ue' for the definitive noun: "monologue", "dialog box", "catalogging", "homologous".
; Use "cannot" when something is impossible or prohibited.
: "Can not" implies a choice; "cannot" prevents one.

== Terminology ==

=== Bags of bits ===

; Be careful of your use of the terms "file" and "resource".
: Make sure your definitions refer only to bags of bits, and not also stuff in the Real World™ (like baskets of apples).

=== Willful violations of other specs ===

; When willfully and deliberately violating standards set out in other documents, use the term "willful violation" instead of simply "violation".
: "Violation" makes you sound naughty; "willful violation" makes you sound knowledgeable.

[[Category:Spec coordination|*]]

Specs/style

2013-11-06T16:08:55Z

GPHemsley: /* Spelling */ the

When writing a spec, it is suggested that you adhere to the following guidelines.

== Spelling ==

; Unless otherwise stated, use standard American English spelling.
: Continue the history of the Web and use 'en-US' spelling for your specs and the technologies they document. See [[wikipedia:Wikipedia:Manual of Style/Spelling|Wikipedia's Manual of Style for spelling]] for assistance.
; Use "acknowledgements" instead of "acknowledgments".
: Whenever 'dg' represents the "soft" /d͡ʒ/ sound, it should be followed by an 'e' or an 'i', to ensure it is not confused with the "hard" /dɡ/ sounds.
; Use "dialogue" for the noun and "dialog" for all other parts of speech.
: Whenever a word has a '-log(ue)' dichotomy, only keep '-ue' for the definitive noun: "monologue", "dialog box", "catalogging", "homologous".

== Terminology ==

=== Bags of bits ===

; Be careful of your use of the terms "file" and "resource".
: Make sure your definitions refer only to bags of bits, and not also stuff in the Real World™ (like baskets of apples).

=== Willful violations of other specs ===

; When willfully and deliberately violating standards set out in other documents, use the term "willful violation" instead of simply "violation".
: "Violation" makes you sound naughty; "willful violation" makes you sound knowledgeable.

[[Category:Spec coordination|*]]

Specs/style

2013-11-06T16:06:51Z

GPHemsley: Use 'en-US-x-ghemsley' spelling.

When writing a spec, it is suggested that you adhere to the following guidelines.

== Spelling ==

; Unless otherwise stated, use standard American English spelling.
: Continue the history of the Web and use 'en-US' spelling for your specs and the technologies they document. See [[wikipedia:Wikipedia:Manual of Style/Spelling|Wikipedia's Manual of Style for spelling]] for assistance.
; Use "acknowledgements" instead of "acknowledgments".
: Whenever 'dg' represents the "soft" /d͡ʒ/ sound, it should be followed by an 'e' or an 'i', to ensure it is not confused with "hard" /dɡ/ sounds.
; Use "dialogue" for the noun and "dialog" for all other parts of speech.
: Whenever a word has a '-log(ue)' dichotomy, only keep '-ue' for the definitive noun: "monologue", "dialog box", "catalogging", "homologous".

== Terminology ==

=== Bags of bits ===

; Be careful of your use of the terms "file" and "resource".
: Make sure your definitions refer only to bags of bits, and not also stuff in the Real World™ (like baskets of apples).

=== Willful violations of other specs ===

; When willfully and deliberately violating standards set out in other documents, use the term "willful violation" instead of simply "violation".
: "Violation" makes you sound naughty; "willful violation" makes you sound knowledgeable.

[[Category:Spec coordination|*]]

Specs

2013-11-06T15:16:47Z

GPHemsley: /* Categories */ Add Proposals.

The WHATWG writes specs.

== Helpful documents ==
* [[Specs/advice|Hixie's advice for people writing specs]]
* [[Specs/howto|How-to guide for writing specs]]
* [[Specs/style|Style guide for writing specs]]
* [[Specs/todo|To-do list for writing specs]]

=== Categories ===
* [[:Category:Spec coordination|Pages used to coordinate specs]]
* [[:Category:Specification editing|Instructional pages for writing and editing specs]]
* [[:Category:Proposals|Proposals for additions to specs]]

== External links ==
* [http://spec.whatwg.org/ List of WHATWG specs]
* [http://platform.html5.org/ The Web Platform: Browser technologies]

[[Category:Spec coordination| ]]

Specs

2013-11-06T15:10:07Z

GPHemsley: Add another category and improve document structure.

The WHATWG writes specs.

== Helpful documents ==
* [[Specs/advice|Hixie's advice for people writing specs]]
* [[Specs/howto|How-to guide for writing specs]]
* [[Specs/style|Style guide for writing specs]]
* [[Specs/todo|To-do list for writing specs]]

=== Categories ===
* [[:Category:Spec coordination|Pages used to coordinate specs]]
* [[:Category:Specification editing|Instructional pages for writing and editing specs]]

== External links ==
* [http://spec.whatwg.org/ List of WHATWG specs]
* [http://platform.html5.org/ The Web Platform: Browser technologies]

[[Category:Spec coordination| ]]

Specs/todo

2013-11-06T15:04:51Z

GPHemsley: Streamlining for Specs.

There are many specifications that need editors. This page lists some of the more important ones. If you want to volunteer to edit one of these specs, contact ian@hixie.ch, post on the WHATWG mailing list or say something on [[IRC]].

== Platform ==

* A specification that defines how XML maps to DOM Core. (I think this should be in DOM Parsing and Serialization. Well really in XML.)
* X-Frames-Options (seems this is going into CSP)
* multipart/form-data
* HTTP (error handling in particular)
* APNG (other image formats too maybe?)
* HTML editing: the spec is quite mature, but needs more work

== APIs ==

* User Interaction Events (onclick, onkeypress, etc).
** e.g. need to define somewhere that if you cancel mousedown, an element can't get focus
** setCapture / releaseCapture [http://lists.w3.org/Archives/Public/public-webapps/2008OctDec/0308.html]
** [http://krijnhoetmer.nl/irc-logs/whatwg/20121128#l-1719 selectstart] (WebKit/IE)
* An API for cryptography, to generate keys and the like
* The console.* API. [http://www.w3.org/Bugs/Public/show_bug.cgi?id=10694] [http://www.w3.org/mid/d7be01cb7077$4dd45010$e97cf030$@gmail.com] [http://sideshowbarker.github.com/console-spec/]
* Undomanager: http://rniwa.com/editing/undomanager.html and http://rniwa.com/editing/undomanager-usecases.html
* [[DOM XPath]]

== CSS ==

There are [http://www.w3.org/Style/CSS/current-work many specifications for extending CSS] that are in need of editors. The most important ones are:
* Table Layout
** http://dbaron.org/css/intrinsic/
** http://dev.w3.org/csswg/css3-tables-algorithms/Overview.src.htm
* Replaced Content
** http://dev.w3.org/csswg/css3-content/ (Do we still want this or is the component model sufficient?)
* an imperative model of box-tree construction
* hit testing per http://lists.w3.org/Archives/Public/www-style/2010Aug/0407.html

== Registries ==

Currently, the state of registries on the Web (and indeed for the Internet in general) is a disaster. At a minimum, the following registries need dramatically updating:

* MIME types
* Schemes

It's possible that the right solution is to change approach altogether (e.g. moving more to a wiki model of registries).

See also: [[Registries]]

== Miscellaneous ==
* an API to do syntax highlighting on <textarea>, <pre>, and contenteditable sections would be highly popular with Web developers (ack Ryan Johnson). (This would probably best be done as some sort of output filter at the CSS level, rather than anything HTML-specific.)
* Animated [[GIF]]s need a spec that, in particular, specifies how to handle timings (not all browsers honor all values, so we should specify what needs to be honored exactly)
* Client-side HTTP implementation requirements specification ("option 3" in http://www.w3.org/mid/20101101063413.bf1d8102.eric@bisonsystems.net)
* innerText and outerText, if browsers don't remove them entirely

== Other stuff ==

http://lists.w3.org/Archives/Public/public-html/2008Oct/0127.html has a description of some sections that needed editing in 2008 and how much work they would be.

Some notes from the HTML5 spec about things that need doing:

* a way to show icons for file types e.g. http://www.gadgetopia.com/2004/05/04/FileIconTag.html (this should probably be a function for the 'content', 'background-image' and 'list-style-image' properties in CSS)
** Maybe something like moz-icon://? http://lists.w3.org/Archives/Public/public-webapps/2010JanMar/0255.html, http://draft-icon-uri-scheme.googlecode.com/hg/draft-lafayette-icon-uri-scheme-00.html

[[Category:Spec coordination|*]]
[[Category:Specification editing]]

Specs/style

2013-11-06T15:01:05Z

GPHemsley: Start style guide.

When writing a spec, it is suggested that you adhere to the following guidelines.

== Terminology ==

=== Bags of bits ===

; Be careful of your use of the terms "file" and "resource".
: Make sure your definitions refer only to bags of bits, and not also stuff in the Real World™ (like apple baskets).

=== Willful violations of other specs ===

; When willfully and deliberately violating standards set out in other documents, use the term "willful violation" instead of simply "violation".
: "Violation" makes you sound naughty; "willful violation" makes you sound knowledgeable.

[[Category:Spec coordination|*]]