https://wiki.whatwg.org/api.php?action=feedcontributions&user=TheresaOConnor&feedformat=atomWHATWG Wiki - User contributions [en]2024-03-29T08:30:13ZUser contributionsMediaWiki 1.39.3https://wiki.whatwg.org/index.php?title=MetaExtensions&diff=10338MetaExtensions2021-04-21T17:18:49Z<p>TheresaOConnor: <meta name=theme-color> is standardized in HTML</p>
<hr />
<div>This page lists extension values for the name="" attribute of the HTML &lt;meta> element. You may add your own values to this list.<br />
<br />
For assistance in preparing a specification, see the [[:Category:Specification editing|specification editing]] category and the [https://github.com/tabatkins/bikeshed/ Bikeshed] documentation.<br />
<br />
If the specification is ready, we ask that you:<br />
<br />
* '''Avoid redundancy.''' If someone has already defined a name that does roughly what you want, please reuse it. <br />
* '''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. <br />
* '''Alphabetize by keyword''', without regard for case, in any table. Sort nonalphanumerics by ASCII value.<br />
* '''Not reserve namespaces.''' Instead, register individual names (known as enumerated values although you don't have to number them).<br />
<br />
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. <br />
<br />
__TOC__<br />
<br />
== Meta Name Extensions ==<br />
<br />
{| class="wikitable sortable"<br />
! Keyword<br />
! Brief description<br />
! Link to specification<br />
! Synonyms<br />
! Status<br />
<br />
|-valign="top" <br />
| AGLSTERMS.accessibility<br />
| A statement indicating the accessibility characteristics of the resource.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.accessMode<br />
| Perceptual mode for the resource. <br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.act<br />
| A specific piece of legislation which requires or drives the creation or provision of the resource.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.aggregationLevel<br />
| The level of aggregation of the described resource - an 'item' or a 'collection'.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.allow-search<br />
| A specific piece of legislation which requires or drives the creation or provision of the resource.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.availability<br />
| 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.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.case<br />
| A specific piece of case law which requires or drives the creation or provision of the resource.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.category<br />
| The generic type of the resource being described - a 'service', 'document' or 'agency'.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.dateLicensed<br />
| Date a license was applied or became effective.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.documentType<br />
| 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.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.function<br />
| 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.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.isBasedOn<br />
| A related resource of which the described resource is a performance, production, derivation, translation or interpretation.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.isBasisFor<br />
| A related resource that is a performance, production, derivation, translation or interpretation of the described resource.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.jurisdiction<br />
| The name of the political/administrative entity covered by the described resource.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.mandate<br />
| A specific legal instrument which requires or drives the creation or provision of the resource.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.protectiveMarking<br />
| A protective marking applied to the described resource.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.regulation<br />
| A specific regulation which requires or drives the creation or provision of the resource.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| AGLSTERMS.serviceType<br />
| The form of the described resource where the value of category is ‘service'.<br />
| [http://www.agls.gov.au/pdf/AGLS%20Metadata%20Standard%20Part%202%20Usage%20Guide.PDF AGLS Metadata Usage Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| alexaverifyid<br />
| Used to verify ownership of Alexa Search<br />
| [http://www.alexa.com/faqs/?p=188 Alexa FAQ About this meta attribute Reference]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| apple-itunes-app<br />
| Promoting Apps with Smart App Banners<br />
| [http://developer.apple.com/library/ios/#documentation/AppleApplications/Reference/SafariWebContent/PromotingAppswithAppBanners/PromotingAppswithAppBanners.html Safari Web Content Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| apple-mobile-web-app-capable<br />
| Sets whether a web application runs in full-screen mode.<br />
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/SafariHTMLRef/Articles/MetaTags.html Apple Safari HTML Reference]<br />
| mobile-web-app-capable (also could maybe be assumed when <code>application-name</code> is set?)<br />
| Proposal<br />
<br />
|-valign="top" <br />
| apple-mobile-web-app-status-bar-style<br />
| Sets the style of the status bar for a web application.<br />
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/SafariHTMLRef/Articles/MetaTags.html Apple Safari HTML Reference]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| apple-mobile-web-app-title<br />
| Sets the title of the application when added to the homescreen on iOS6+<br />
| [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]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| apple-touch-fullscreen<br />
| forces iPhone Fullscreen mode, if added to home screen. Not needed anymore.<br />
| No specification yet<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| application-name<br />
| 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.<br />
| [https://msdn.microsoft.com/en-us/library/gg491732%28v=vs.85%29.aspx Declaring Pinned Site Metadata (Microsoft Developer Network)]<br />
|<br />
| Proposed<br />
<br />
|-valign="top"<br />
| application-url<br />
| '''Start URL of web apps in Google Chrome'''<br />
The "application-url" meta tag can be used to specify the start URL of pinned web apps in Google Chrome.<br />
<meta name="application-url" content="https://gmail.com/"><br />
| [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]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| appstore:bundle_id<br />
| 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><br />
| IAB Tech Lab app-ads.txt documentation: <nowiki>https://iabtechlab.com/ads-txt/</nowiki><br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| appstore:developer_url<br />
| 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><br />
| IAB Tech Lab app-ads.txt documentation: <nowiki>https://iabtechlab.com/ads-txt/</nowiki><br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| appstore:store_id<br />
| 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><br />
| IAB Tech Lab app-ads.txt documentation: <nowiki>https://iabtechlab.com/ads-txt/</nowiki><br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| audience<br />
| 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.<br />
| [http://brittlebit.org/specifications/html-meta-audience/specification-for-html-meta-element-with-name-value-audience.html BrittleBit.org spec]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| bitcoin<br />
| A bitcoin-address<br />
| 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]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| blazerr-secure<br />
| 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><br />
Usage: <code><meta name="blazerr-secure" content="yes"></code><br />
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-secure JokeNetwork's Blazerr Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| blazerr-seo<br />
| Checks whether Blazerr SEO has been used or not. It contains the user-id and the SEO Version.<br><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.<br />
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-seo JokeNetwork's Blazerr Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| blazerr-ssl<br />
| Decides whether connect via a secure connection or not to JokeNetwork's Blazerr-System. Similar to blazerr-secure.<br><br />
Usage: <code><meta name="blazerr-ssl" content="yes"></code><br />
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-ssl JokeNetwork's Blazerr Documentation]<br />
| blazerr-secure is partial synonym (see that entry)<br />
| Proposal<br />
<br />
|-valign="top" <br />
| blazerr-support-id-noncookies<br />
| Used to identify users for JokeNetwork's Blazerr Support-System without a cookie. Deprecated.<br />
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-support-id-noncookies JokeNetwork's Blazerr Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| blazerr-support-identifier<br />
| Used to identify users for JokeNetwork's Blazerr Support-System along with a cookie. The verification of a user without the use of cookies can be obtained with the deprecated meta tag [https://jokenetwork.de/faq/blazerr/ blazerr-support-id-noncookies].<br />
| [https://jokenetwork.de/faq/blazerr/metatags/#blazerr-support-identifier JokeNetwork's Blazerr Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| bug.blocked<br />
| 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.<br />
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| bug.comment<br />
| Bugzilla comment used by the https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js bug-creation script.<br />
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| bug.component<br />
| 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.<br />
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| bug.product<br />
| 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.<br />
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| bug.short_desc<br />
| Bugzilla short description used by the https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js bug-creation script.<br />
| [https://dvcs.w3.org/hg/webcomponents/raw-file/default/assets/scripts/bug-assist.js Embedded documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| cfia.gdr.activity<br />
| Canadian Food Inspection Agency Guidance Document Repository Page Activity<br />
| Coming soon at [http://www.inspection.gc.ca CFIA website]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| cfia.gdr.commodity<br />
| Canadian Food Inspection Agency Guidance Document Repository Page Commodity<br />
| Coming soon at [http://www.inspection.gc.ca CFIA website]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| cfia.gdr.include<br />
| Canadian Food Inspection Agency Guidance Document Repository Page<br />
| Coming soon at [http://www.inspection.gc.ca CFIA website]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| cfia.gdr.program<br />
| Canadian Food Inspection Agency Guidance Document Repository Page Program<br />
| Coming soon at [http://www.inspection.gc.ca CFIA website]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_author<br />
| The name of an author of an academic paper<br />
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_author_email<br />
| The email address of the preceding author (identified using citation_author) of an academic paper<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_author_institution<br />
| The name of an institution to which the preceding author (identified using citation_author) of an academic paper is affiliated<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_conference_title<br />
| The title of the conference at which an academic paper is published<br />
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_date<br />
| The publication date of an academic paper<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_dissertation_institution<br />
| The name of the institution which published an academic dissertation<br />
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_doi<br />
| The Digital Object Identifier of an academic paper<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_firstpage<br />
| The first page of the journal in which an academic paper is published<br />
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_fulltext_html_url<br />
| The URL of the full text HTML version of an academic paper<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_isbn<br />
| The ISBN of the book in which an academic paper is published<br />
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_issn<br />
| The ISSN of the journal in which an academic paper is published<br />
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_issue<br />
| The issue of the journal in which an academic paper is published<br />
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_journal_abbrev<br />
| The abbreviated title of the journal in which an academic paper is published<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_journal_title<br />
| The title of the journal in which an academic paper is published<br />
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_keywords<br />
| A semicolon-separated list of keywords associated with an academic paper<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_language<br />
| The language in which an academic paper is written, as an ISO 639-1 two-letter code<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_lastpage<br />
| The last page of the journal in which an academic paper is published<br />
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_pdf_url<br />
| The URL of a PDF version of an academic paper<br />
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_publication_date<br />
| The publication date of an academic paper<br />
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_publisher<br />
| The name of the publisher of an academic paper<br />
| 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).<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_technical_report_institution<br />
| The name of the institution which published an academic technical report or preprint<br />
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_technical_report_number<br />
| The identification number of an academic technical report or preprint<br />
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_title<br />
| The title of an academic paper<br />
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| citation_volume<br />
| The volume of the journal in which an academic paper is published<br />
| [https://www.google.com/intl/en/scholar/inclusion.html#indexing Google Scholar indexing documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| collection<br />
| 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.<br />
<br />
<meta name="collection" content="MetaExtensions" /><br />
<meta name="subject" content="topics, thesaurus, Meta Tag, header, semantic" /><br />
| [http://www.trucsweb.com/tw/]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| contact<br />
| 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><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><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><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><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.<br />
| [http://arpita.github.io/ContactMetaExtensions/ Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| creator<br />
| Identify the creator of the page’s content, the content generally being the principal part of what info is rendered for website visitors.<br />
| [http://brittlebit.org/specifications/html-meta-creator/specification-for-html-meta-element-with-name-value-creator.html BrittleBit.org spec]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| csrf-param<br />
| Cross-site request forgery protection parameter for Ruby on Rails<br />
| [http://apidock.com/rails/ActionView/Helpers/CsrfHelper/csrf_meta_tag Rails API]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| csrf-token<br />
| Cross-site request forgery protection token for Ruby on Rails<br />
| [http://apidock.com/rails/ActionView/Helpers/CsrfHelper/csrf_meta_tag Rails API]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_anonymiseIP<br />
| Defines anonymiseIP parameter for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_contactCompany<br />
| Defines the contactCompany of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_contactEmail<br />
| Defines the contactEmail of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_contactFirstName<br />
| Defines the contactFirstName of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_contactLastName<br />
| Defines the contactLastName of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_contactName<br />
| Defines the contactName of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_contactTelephone<br />
| Defines the contactTelephone of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_conversionCurrency<br />
| Defines the conversionCurrency of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_conversionId<br />
| Defines the conversionId of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_conversionValue<br />
| Defines the conversionValue of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_goalCurrency<br />
| Defines the goalCurrency of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_goalId<br />
| Defines the goalId of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_goalValue<br />
| Defines the goalValue of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_interactionSelector<br />
| Defines the interactionSelector parameter for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_pageRole<br />
| Defines the role of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_pageTaxonomy<br />
| Defines the taxonomy of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_pageTitle<br />
| Defines the pageTitle of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_pageVersion<br />
| Defines the pageVersion of the page for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_sessionId<br />
| Defines the sessionId parameter for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| da_userId<br />
| Defines the userId parameter for Decibel Insight<br />
| [https://www.decibelinsight.com/assets/Documents/DecibelInsightImplementationGuide.pdf Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.created<br />
| Date of creation of the resource.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-created DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.creator<br />
| An entity primarily responsible for making the resource.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-creator DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| dc.date.issued<br />
| Date of publication for Google News. The format of the content is YYYY-MM-DD or YYYY-MM-DDThh:mm:ssTZD.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element<br />
| [http://www.google.com/support/news_pub/bin/answer.py?answer=93994 Google News documentation]<br />
| <code>dcterms.issued</code> (former <code>&lt;time pubdate&gt;</code> no longer considered due to the abort of <code>@pubdate</code>)<br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.dateCopyrighted<br />
| Date of copyright.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-dateCopyrighted DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.dateSubmitted<br />
| Date of submission of the resource.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-dateSubmitted DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.description<br />
| An account of the resource.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-description DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.language<br />
| A language of the resource. Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646]. <br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-language DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| Redundant with the <code>lang</code> attribute on the<br />
<code>html</code> element. (Browsers pay attention to the <code>lang</code> attribute but not <code>dc.language</code>)<br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.license<br />
| A legal document giving official permission to do something with the resource.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-license DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.mediator<br />
| An entity that mediates access to the resource and for whom the resource is intended or useful.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-mediator DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.medium<br />
| The material or physical carrier of the resource.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-medium DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.modified<br />
| Date on which the resource was changed.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-modified DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.provenance<br />
| A statement of any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-provenance DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.publisher<br />
| An entity responsible for making the resource available.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-publisher DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.references<br />
| A related resource that is referenced, cited, or otherwise pointed to by the described resource.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-references DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.temporal<br />
| Temporal characteristics of the resource.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-temporal DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.title<br />
| A name given to the resource.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-title DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.type<br />
| The nature or genre of the resource. Recommended best practice is to use a controlled vocabulary such as the DCMI Type Vocabulary [DCMITYPE].<br />
To describe the file format, physical medium, or dimensions of the resource, use the Format element.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-type DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dc.valid<br />
| Date (often a range) of validity of a resource.<br />
It must be accompanied by a <code>&lt;link rel="schema.dc" href="<nowiki>http://purl.org/dc/elements/1.1/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-valid DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| DCS.dcssta<br />
| '''Error page parameter'''<br />
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.<br />
Example:<br />
<meta name="DCS.dcssta" content="404"><br />
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters].<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.abstract<br />
| A summary of the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-abstract DCMI<br />
Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <code>&lt;meta name="description"&gt;</code><br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.accessRights<br />
| Information about who can access the resource or an indication of its security status. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-accessRights DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.accrualMethod<br />
| The method by which items are added to a collection. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-accrualMethod DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.accrualPeriodicity<br />
| The frequency with which items are added to a collection. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-accrualPeriodicity DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.accrualPolicy<br />
| The policy governing the addition of items to a collection. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-accrualPolicy DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.alternative<br />
| An alternative name for the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-alternative DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.audience<br />
| A class of entity for whom the resource is intended or useful. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-audience DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.available<br />
| Date (often a range) that the resource became or will become available. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-available DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.bibliographicCitation<br />
| A bibliographic reference for the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-bibliographicCitation DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| The HTML attribute <code>cite</code><br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.collection<br />
| An aggregation of resources. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#dcmitype-Collection DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.conformsTo<br />
| An established standard to which the described resource conforms. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-conformsTo DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.contributor<br />
| An entity responsible for making contributions to the content of the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-contributor DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.coverage<br />
| The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-coverage DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.created<br />
| Date of creation of the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-created DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.creator<br />
| An entity primarily responsible for making the resource. Examples of a Creator include a person, an organization, or a service. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-creator DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| In some cases redundant with the HTML built-in keyword <code>author</code><br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.date<br />
| A point or period of time associated with an event in the lifecycle of the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-date DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.dateAccepted<br />
| Date of acceptance of the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-dateAccepted DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.dateCopyrighted<br />
| Date of copyright. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-dateCopyrighted DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.dateSubmitted<br />
| Date of submission of the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-dateSubmitted DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.description<br />
| 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. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-description DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| HTML built-in keyword <code>description</code> <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.educationLevel<br />
| A class of entity, defined in terms of progression through an educational or training context, for which the described resource is intended. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-educationLevel DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.extent<br />
| The size or duration of the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-extent DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.format<br />
| The file format, physical medium, or dimensions of the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-format DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| 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.<br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.hasFormat<br />
| A related resource that is substantially the same as the pre-existing described resource, but in another format. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-hasFormat DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code><br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.hasPart<br />
| A related resource that is included either physically or logically in the described resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-hasPart DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.hasVersion<br />
| A related resource that is a version, edition, or adaptation of the described resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-hasVersion DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code><br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.identifier<br />
| An unambiguous reference to the resource within a given context. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-identifier DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.instructionalMethod<br />
| A process used to engender knowledge, attitudes and skills, that the described resource is designed to support. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-instructionalMethod DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.isFormatOf<br />
| A related resource that is substantially the same as the described resource, but in another format. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-isFormatOf DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code><br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.isPartOf<br />
| A related resource in which the described resource is physically or logically included. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-isPartOf DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.isReferencedBy<br />
| A related resource that references, cites, or otherwise points to the described resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-isReferencedBy DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.isReplacedBy<br />
| A related resource that supplants, displaces, or supersedes the described resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-isReplacedBy DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code><br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.isRequiredBy<br />
| A related resource that requires the described resource to support its function, delivery, or coherence.<br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-isRequiredBy DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.issued<br />
| 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.) <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-issued DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| (former <code>&lt;time pubdate&gt;</code> no longer considered due to the abort of <code>@pubdate</code>)<br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.isVersionOf<br />
| A related resource of which the described resource is a version, edition, or adaptation.<br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-isVersionOf DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code><br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.language<br />
| A language of the resource. Recommended best practice is to use a controlled vocabulary such as RFC 4646 [RFC4646]. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-language DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| Redundant with the <code>lang</code> attribute on the <code>html</code> element. (Browsers pay attention to the <code>lang</code> attribute but not <code>dcterms.language</code>)<br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.license<br />
| A legal document giving official permission to do something with the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-license DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| The HTML <code>&lt;link&gt;</code> element with the keyword <code>"license"</code> as value of the <code>rel</code> attribute.<br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.mediator<br />
| An entity that mediates access to the resource and for whom the resource is intended or useful. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-mediator DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.medium<br />
| The material or physical carrier of the resource.<br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-medium DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.modified<br />
| Date on which the resource was changed. (DC doesn't spec a date format but the established practice is YYYY-MM-DD.) <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-modified DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.provenance<br />
| A statement for any changes in ownership and custody of the resource since its creation that are significant for its authenticity, integrity, and interpretation. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-provenance DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.publisher<br />
| An entity responsible for making the resource available. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-publisher DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| publisher<br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.references<br />
| A related resource that is referenced, cited, or otherwise pointed to by the described resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-references DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <code>cite</code> attribute on specific quotes, if any.<br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.relation<br />
| A related resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-relation DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| If the relation comes from an internal reference or quote, <code>dcterms.references</code> should be preferred.<br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.replaces<br />
| A related resource that is supplanted, displaced, or superseded by the described resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-replaces DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| The HTML link type keyword "alternate" used with "link" element:<code>rel="alternate" href="URI of related resource"</code><br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.requires<br />
| A related resource that is required by the described resource to support its function, delivery, or coherence. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-requires DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.rights<br />
| Information about rights held in and over the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-rights DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| The HTML <code>&lt;link&gt;</code> element with the keyword <code>"license"</code> as value of the <code>rel</code> attribute, if referring to a legal license format.<br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.rightsHolder<br />
| A person or organization owning or managing rights over the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-rightsHolder DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.source<br />
| A related resource from which the described resource is derived. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-source DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| 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.<br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.spatial<br />
| Spatial characteristics of the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-spatial DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| geographic-coverage<br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.subject<br />
| The topic of the resource.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-subject DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| HTML built-in keywords <code>description</code> or <code>keywords</code><br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.tableOfContents<br />
| A list of subunits of the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-tableOfContents DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| HTML built-in keywords <code>description</code> or <code>keywords</code>. Otherwise, a <code>details-summary</code> model which would provide user-readable information.<br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.temporal<br />
| Temporal characteristics of the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-temporal DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.title<br />
| A name given to the resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-title DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| HTML built-in element <code>title</code> (not to be confused with <code>@title</code> attributes specific to each element)<br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.type<br />
| The nature or genre of the resource.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-type DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| dcterms.valid<br />
| Date (often a range) of validity of a resource. <br />
It must be accompanied by a <code>&lt;link rel="schema.dcterms" href="<nowiki>http://purl.org/dc/terms/</nowiki>"&gt;</code> element.<br />
| [http://dublincore.org/documents/dcmi-terms/#terms-valid DCMI Metadata Terms] mapped according to<br />
[http://dublincore.org/documents/dc-html/ Expressing Dublin Core metadata using HTML/XHTML meta and link elements]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| detectify-verification<br />
| 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.<br />
| [http://labs.detectify.com/post/85707633296/detectify-validation-specification Documentation]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| designer<br />
| Credits the designer(s) responsible for the visual presentation of a website.<br />
| [https://sites.google.com/site/metadesignerspec/ Documentation]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| entity<br />
| 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.<br />
| [https://github.com/brettz9/js-css-entities Documentation]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| EssayDirectory<br />
| Defines a custom description of websites listed in EssayDirectory.<br>Example:<br />
<meta name="EssayDirectory" content="Helping students find legitimate essay services."><br />
| [http://essaydirectory.com/privacy-terms/#EssayDirectory_MetaExtension Documentation]<br />
|<br />
| Proposal<br />
<br />
|-valign="top" <br />
| fdse-description<br />
| Tag used by FDSE search software, allows different description to be displayed in fdse results to that shown in description<br />
| [http://www.xav.com/scripts/search/help/1013.html]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| fdse-index-as<br />
| Tag used by FDSE search software, allows FDSE to index a page as url described here<br />
| [http://www.xav.com/scripts/search/help/1014.html]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| fdse-keywords<br />
| Tag used by FDSE search software, allows different keywords to be used by FDSE to keywords tag<br />
| [http://www.xav.com/scripts/search/help/1013.html]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| fdse-refresh<br />
| Tag used by FDSE search software, allows FDSE to ignore refresh meta tags<br />
| [http://www.xav.com/scripts/search/help/1013.html]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| fdse-robots<br />
| 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<br />
| [http://www.xav.com/scripts/search/help/1013.html]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| FLBlogAuthor<br />
| Depicts whether author of the blog is lawfirm or FL author<br />
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| format-detection<br />
| Enables or disables automatic detection of possible phone numbers in a webpage in Safari on iOS.<br />
| [http://developer.apple.com/library/safari/#documentation/appleapplications/reference/SafariHTMLRef/Articles/MetaTags.html Apple Safari HTML Reference]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| format-print<br />
| 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.<br />
| [http://brittlebit.org/specifications/html-meta-format-print/specification-for-html-meta-element-with-name-value-format-print.html BrittleBit.org spec]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| fragment<br />
| Opts a webpage into the AJAX crawling scheme when it does not have a "#!" URL. The only valid content value is "!".<br />
<meta name="fragment" content="!"><br />
| [https://developers.google.com/webmasters/ajax-crawling/docs/specification Google Crawable AJAX Specification]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| FSDateCreation<br />
| Mentions the date when this web page was created<br />
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| FSDatePublish <br />
| Mentions the date when this web page was created<br />
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| FSFLContent <br />
| Informs the Publisher tool whether this page contains any content or not. Valid values yes or no<br />
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| FSLanguage <br />
| Language of the content in the page. Example: US English or UK English, etc<br />
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| FSOnSitemap <br />
| Whether the page is accessible via the Sitemap link in the firmsite<br />
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| FSPageDescription<br />
| Description of the content of page<br />
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| FSPageName <br />
| Name of the page within a Findlaw firmsite<br />
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| FSSearchable<br />
| This tag mentions whether a certain page can be searched or not<br />
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| FSSection<br />
| Depicts whether a page is a Section Page or simple page. Section pages can have links to other pages<br />
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| FSWritertoolPageType<br />
| Page Type of a page in the firmsite. Page Type values help the Publisher toold in page creation<br />
| [http://images.findlaw.com/firmsites/flfs_meta_tags.html FL Meta Names documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| gcterms.topicTaxonomy<br />
| Organize resources specifically for taxonomy-based topical browse or search structures on websites (ie: breadcrumbs / website information architecture).<br />
| [http://www.gcpedia.gc.ca/wiki/Metadata_Tools#Metadata_for_Web_Resource_Discovery] Government of Canada, Web Content Management System Metadata Application Profile.<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| geo.a1<br />
| 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.<br />
<meta name="geo.a1" content="AB"><br />
| [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<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| geo.a2<br />
| County, parish, gun (JP), district (IN) of civil address to which the page is related.<br />
<meta name="geo.a2" content="Warwickshire"><br />
| [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<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| geo.a3<br />
| City, township, shi (JP) of civil address to which the page is related.<br />
<meta name="geo.a3" content="Calgary"><br />
| [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<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| geo.country<br />
| Case-insensitive ISO 3166-1 alpha-2 code of a country to which the page is related.<br />
<meta name="geo.country" content="de"><br />
| [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]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| geo.lmk<br />
| A landmark or vanity address to which the page is related.<br />
<meta name="geo.lmk" content="Auwaldstraße 11, 79110 Freiburg im Breisgau, Deutschland"><br />
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| geo.placename<br />
| Superseded by geo.lmk. Name of geographic place to which the page is related.<br />
<meta name="geo.placename" content="London, Ontario"><br />
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| geo.position<br />
| Geographic position to which the page is related.<br />
<meta name="geo.position" content="48.02682000000001;7.809769999999958"><br />Like icbm except for value syntax.<br />
| [http://tools.ietf.org/html/draft-daviel-html-geo-tag-08 IETF Draft (expired)]<br>[http://geotags.com/geo/geotags2.html GeoTags.com]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| geo.region<br />
| 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.<br />
<meta name="geo.region" content="DE-BW"><br />
| [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]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.bathrooms<br />
| Globrix property information: Number of bathrooms the property has<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.bedrooms<br />
| Globrix property information: Number of bedrooms the property has<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.condition<br />
| Globrix property information: Condition of the property e.g. 'renovated'<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.features<br />
| Globrix property information: Features of the property e.g. 'double glazing'<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.instruction<br />
| Globrix property information: Property to Buy or Rent<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.latitude<br />
| Globrix property information: The latitude of the property<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.longitude<br />
| Globrix property information: The longitude of the property<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.outsidespace<br />
| Globrix property information: External features of the property e.g. 'garden'<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.parking<br />
| Globrix property information: Parking available for property e.g. 'parking for 2 cars'<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.period<br />
| Globrix property information: Period of the property e.g. 'victorian terrace'<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.poa<br />
| Globrix property information: If the property price is only available on application<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.postcode<br />
| Globrix property information: Postcode of the property<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.price<br />
| Globrix property information: Price for the property<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.priceproximity<br />
| Globrix property information: The region of the attached price e.g. 'guide price of'<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.tenure<br />
| Globrix property information: The tenure of the property e.g. 'leasehold'<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.type<br />
| Globrix property information: Type of property e.g. 'semi-detatched house'<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| globrix.underoffer<br />
| Globrix property information: Indicates if the property is under offer<br />
| [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.]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| go-import<br />
| 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>.<br />
| [http://golang.org/cmd/go/#hdr-Remote_import_path_syntax go tool documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| google<br />
| Multiple purposes:<br /><br />Used to declare text that should not be translated by the Google Translate plugin (&lt;meta name="google" value="notranslate"&gt; will declare the whole page should not be translated, while &lt;span class="notranslate"&gt; is for text or paragraph areas you wish to not be translated.<br /><br />Used "[t]o tell Google not to show a Sitelinks search box when your site appears in the search results" (implement with content="nositelinkssearchbox") (already in use).<br /><br />Presumably, multiple meta elements named "google" should all be parsed but this is may not have been explicitly specified anywhere.<br />
| "notranslate": [http://googlewebmastercentral.blogspot.com/2007/12/answering-more-popular-picks-meta-tags.html Google blog post]<br /><br />"nositelinkssearchbox": [https://developers.google.com/structured-data/slsb-overview Google on Structured Data &gt; Sitelinks Search Box]<br />
| <br />
| Nontranslation: Proposal<br /><br />No Sitelinks search box: Proposed<br />
<br />
|-valign="top" <br />
| google-play-app<br />
| Promoting Apps with Smart App Banners<br />
| [http://jasny.github.io/jquery.smartbanner/] Smart banners for Google Apps <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| google-site-verification<br />
| Used to verify ownership for Webmaster Tools.<br />
| [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=79812 Google documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| gwt:property<br />
| Used to specify the locale client property<br />
| [https://developers.google.com/web-toolkit/doc/latest/DevGuideI18nLocale Locales in GWT]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| handheldfriendly<br />
| Informs the BlackBerry browser that the content contained within the document is designed for small screens.<br />
| [https://developer.blackberry.com/html5/documentation/v1_0/handheldfriendly.html BlackBerry (handheldfriendly "largely obsolete")]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| icas.datetime<br />
| 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).<br />
| 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.<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| icas.datetime.abbr<br />
| 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".<br />
| 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.<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| icas.datetime.day<br />
| 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".<br />
| 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.<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| icas.datetime.long<br />
| 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"/><br />
| 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.<br />
|<br />
| Proposal<br />
<br />
|-valign="top" <br />
| icbm<br />
| 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:<br />
<meta name="ICBM" content="47.0667, 15.4500" /><br />Like geo.position except for value syntax.<br />
| [http://geourl.org/add.html GeoURL documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| IE_RM_OFF<br />
| 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.<br />
| [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.<br />
|<br />
| Proposal<br />
<br />
<br />
|-valign="top" <br />
| itemsPerPage<br />
| Used to identify the number of search results returned per page.<br />
| [http://www.opensearch.org/Specifications/OpenSearch/1.1#Response_metadata_in_HTML.2FXHTML OpenSearch Specification]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| keywords-not<br />
| 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.<br />
| [http://brittlebit.org/specifications/html-meta-keywords-not/specification-for-html-meta-element-with-name-value-keywords-not.html BrittleBit.org spec]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| meta_date<br />
| 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".)<br />
| [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 ]<br />
|<br />
| Proposal<br />
<br />
|-valign="top" <br />
| microtip<br />
| 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><br />
Example:<br />
<meta name="microtip" content="[bitcoin-address]"><br />
Note: there can be multiple instances of this metatag on a page.<br />
| For full specification, see: http://autotip.io/docs/microtip-meta-tag<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| mobile-agent<br />
| 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><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:<br />
<meta name="mobile-agent" content="format=html5; url=http://3g.sina.com.cn/"><br />
| [http://open.shouji.baidu.com/?page=developer&action=pcandmo Baidu Mobile SEO]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| mobile-web-app-capable<br />
| 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.<br />
| [https://developers.google.com/chrome/mobile/docs/installtohomescreen Add to Homescreen - Google Chrome Mobile &mdash; Google Developers] (though a WHATWG or W3C spec would be preferred)<br />
| apple-mobile-web-app-capable (vendor specific synonym)<br />
| Proposal<br />
<br />
|-valign="top" <br />
| mobileoptimized<br />
| Controls layout behavior in older versions of Internet Explorer (e.g., 6.5). <br />
| [http://msdn.microsoft.com/en-us/library/bb431690.aspx Microsoft Windows Mobile 6.5 documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| msapplication-config<br />
| '''"Pinned Sites" in Windows 8'''<br />
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.<br />
<meta name="msapplication-config" content="IEconfig.xml" /><br />
'''Note'''<br />
Without this metadata, IE11 looks for a default "browserconfig.xml" in the root directory of the server.<br />
| [http://msdn.microsoft.com/en-us/library/ie/dn320426%28v=vs.85%29.aspx Browser configuration schema reference]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| msapplication-navbutton-color<br />
| '''"Jump List" or "Pinned Sites" in Windows 7'''<br />
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.<br />
<meta name="msapplication-navbutton-color" content="#FF3300" /><br />
| [http://msdn.microsoft.com/en-us/library/gg491732(v=VS.85).aspx Declaring Pinned Site Metadata]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| msapplication-notification<br />
| '''"Pinned Sites" and "Live Tiles" in Windows 8.1'''<br />
Used to make pinned sites on the start screen into live tiles. Usage:<br />
<META name="msapplication-notification" content="cycle=7;frequency=60;polling-uri=http://www.example.com/notifications.xml" /><br />
| [https://msdn.microsoft.com/en-us/library/ie/dn255024.aspx#msapplication-notification Pinned site metadata reference]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| msapplication-square150x150logo<br />
| '''msapplication-square150x150logo'''<br />
Specifies the image to use as the wide tile, which is 310x150 pixels at 100% scaling.<br />
<meta name="msapplication-square150x150logo" content="images/logo.png"><br />
'''Note''' The '''msapplication-square150x150logo''' value is supported as of IE11 Preview and applies to tiles pinned to the Windows Start screen.<br />
| [http://msdn.microsoft.com/en-us/library/ie/dn255024%28v=vs.85%29.aspx Pinned site metadata reference]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| msapplication-square310x310logo<br />
| '''msapplication-square310x310logo'''<br />
Specifies the image to use as the large tile, which is 310x310 pixels at 100% scaling.<br />
<meta name="msapplication-square310x310logo" content="images/largelogo.png"><br />
'''Note''' The '''msapplication-square310x310logo''' value is supported as of IE11 Preview and applies to tiles pinned to the Windows Start screen.<br />
| [http://msdn.microsoft.com/en-us/library/ie/dn255024%28v=vs.85%29.aspx Pinned site metadata reference]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| msapplication-square70x70logo<br />
| '''msapplication-square70x70logo'''<br />
Specifies the image to use as the small tile, which is 70x70 pixels at 100% scaling.<br />
<meta name="msapplication-square70x70logo" content="images/tinylogo.png"><br />
'''Note''' The '''msapplication-square70x70logo''' value is supported as of IE11 Preview and applies to tiles pinned to the Windows Start screen.<br />
| [http://msdn.microsoft.com/en-us/library/ie/dn255024%28v=vs.85%29.aspx Pinned site metadata reference]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| msapplication-starturl<br />
| '''"Jump List" or "Pinned Sites" in Windows 7'''<br />
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.<br />
<meta name="msapplication-starturl" content="./" /><br />
| [http://msdn.microsoft.com/en-us/library/gg491732(v=VS.85).aspx Declaring Pinned Site Metadata]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| msapplication-tap-highlight<br />
| '''Link highlighting in Internet Explorer'''<br />
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.<br />
<meta name="msapplication-tap-highlight" content="no" /><br />
| [http://msdn.microsoft.com/en-us/library/ie/bg182645%28v=vs.85%29.aspx#tapHighlight Link highlighting]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| msapplication-task<br />
| '''"Jump List" or "Pinned Sites" in Windows 7'''<br />
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. <br />
For example, to add a single task called "Check Order Status" specify a meta element in the head of your webpage, as follows:<br />
<META name="msapplication-task" content="name=Check Order Status;<br />
action-uri=./orderStatus.aspx?src=IE9;<br />
icon-uri=./favicon.ico" /><br />
| [http://msdn.microsoft.com/en-us/library/gg491725(v=vs.85).aspx Tasks in Jump List]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| msapplication-TileColor<br />
| 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.<br />
<meta name="msapplication-TileColor" content="#d83434"/><br />
| [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]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| msapplication-TileImage<br />
| 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.<br />
<meta name="msapplication-TileImage" content="images/benthepcguy-144.png" /><br />
| [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]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| msapplication-tooltip<br />
| '''"Jump List" or "Pinned Sites" in Windows 7'''<br />
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.<br />
<meta name="msapplication-tooltip" content="Channel 9 Podcasts" /><br />
| [http://msdn.microsoft.com/en-us/library/gg491732(v=VS.85).aspx Declaring Pinned Site Metadata]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| msapplication-wide310x150logo<br />
| '''msapplication-wide310x150logo'''<br />
Specifies the image to use as the medium tile, which is 150x150 pixels at 100% scaling.<br />
<meta name="msapplication-wide310x150logo" content="images/widelogo.png"><br />
'''Note''' The '''msapplication-wide310x150logo''' value is supported as of IE11 Preview and applies to tiles pinned to the Windows Start screen.<br />
| [http://msdn.microsoft.com/en-us/library/ie/dn255024%28v=vs.85%29.aspx Pinned site metadata reference]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| msapplication-window<br />
| '''"Jump List" or "Pinned Sites" in Windows 7'''<br />
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.<br />
The following properties can be used in the value of the <code>content</code> attribute:<br />
* width - The window width in pixels. The minimum value is 800.<br />
* height - The window height in pixels. The minimum value is 600.<br />
<meta name="msapplication-window" content="width=1024;height=768" /><br />
| [http://msdn.microsoft.com/en-us/library/gg491732(v=VS.85).aspx Declaring Pinned Site Metadata]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| MSSmartTagsPreventParsing<br />
| 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.<br />
| [http://brittlebit.org/specifications/html-meta-mssmarttagspreventparsing/specification-for-html-meta-element-with-name-value-mssmarttagspreventparsing.html BrittleBit.org spec]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| msvalidate.01<br />
| One of the verification elements used by Bing.<br />
| [http://onlinehelp.microsoft.com/en-us/bing/hh204490.aspx Bing Webmaster Tools]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| nonfiction<br />
| 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.<br />
| [http://brittlebit.org/specifications/html-meta-nonfiction/specification-for-html-meta-element-with-name-value-nonfiction.html BrittleBit.org spec]<br />
| fiction (antonym; see spec for usage)<br />
| Proposal<br />
<br />
|-valign="top" <br />
| norton-safeweb-site-verification<br />
| Used to verify ownership of Website for Norton SafeWeb.<br />
| [http://safeweb.norton.com/help/site_owners#verification_tips Norton SafeWeb Help Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| origin<br />
| The ''origin'' meta tag is used to indicate the original source of a document.<br />
| [https://doc.ohreally.nl/metatag-origin The ''origin'' meta tag]<br />
|<br />
| Proposed<br />
<br />
|-valign="top" <br />
| origin-trials<br />
| Used to enable experimental browser features for sites which are registered to participate in experimental trials.<br />
| [https://docs.google.com/document/d/1v5fi0EUV_QHckVHVF2K4P72iNywnrJtNhNZ6i2NPt0M/edit?usp=sharing Experimental Framework Trial Token Structure]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| p:domain_verify<br />
| Used to register a site's domain with Pinterest as a "verified domain".<br />
Example:<br />
<code><meta name="p:domain_verify" content="5dd1c5f2db0ac0b521f08d56b4cd271b"></code><br />
| [https://help.pinterest.com/entries/22488487-Verify-with-HTML-meta-tags Pinterest Help Article]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| page-version<br />
| 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.<br />
| [http://brittlebit.org/specifications/html-meta-page-version/specification-for-html-meta-element-with-name-value-page-version.html BrittleBit.org spec]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| pingdom<br />
| 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.<br />
Example:<br />
<code><meta name="pingdom" content="6bh3nxnx"/></code><br />
|<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| pinterest<br />
| Used to block pinterest from linking to content on the URL.<br />
Example:<br />
<code><meta name="pinterest" content="nopin"/></code><br />
| [https://support.pinterest.com/entries/21101932-what-if-i-don-t-want-images-from-my-site-to-be-pinned Pinterest Help Article]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| prism:alternateTitle<br />
| 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.<br />
| [http://www.prismstandard.org/specifications/3.0/PRISM_Basic_Metadata_3.0.htm PRISM Basic Metadata Specification V3.0]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| pro<br />
| Signify expertise as judged by an authority. Counterpart to pro-auth (which see). Useful to search engines and Web directories.<br />
| [http://brittlebit.org/specifications/html-meta-pro/specification-for-html-meta-element-with-name-value-pro.html BrittleBit.org spec]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| pro-auth<br />
| 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).<br />
| [http://brittlebit.org/specifications/html-meta-pro-auth/specification-for-html-meta-element-with-name-value-pro-auth.html BrittleBit.org spec]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| pro-auth-field<br />
| Signify an authority's claimed field of expertise, importance and validity to be judged by search engine or directory. Supports pro-auth (which see).<br />
| [http://brittlebit.org/specifications/html-meta-pro-auth-field/specification-for-html-meta-element-with-name-value-pro-auth-field.html BrittleBit.org spec]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| pro-auth-fragment<br />
| Signify which links from authority are links to experts, as distinct from other links. Supports pro-auth (which see).<br />
| [http://brittlebit.org/specifications/html-meta-pro-auth-fragment/specification-for-html-meta-element-with-name-value-pro-auth-fragment.html BrittleBit.org spec]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| rating <br />
| 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.<br />
Example:<br />
<meta name="RATING" content="RTA-5042-1996-1400-1577-RTA" /><br />
| [http://www.rtalabel.org/index.php?content=howto RTA documentation]<br />
|<br />
| Proposal<br />
<br />
|-valign="top" <br />
| referrer<br />
| Controls whether the user agent includes the Referer header in HTTP requests originating from this document<br />
| [https://www.w3.org/TR/referrer-policy/ Referrer Policy]<br />
| referer<br />
| Proposal<br />
<br />
|-valign="top" <br />
| RepostUsAPIKey<br />
| Used to verify ownership of Website for Repost syndication service<br />
| [http://www.repost.us/meta-headers-used-by-repost/ Meta Headers used by Repost]<br />
|<br />
| Proposal<br />
<br />
|-valign="top" <br />
| ResourceLoaderDynamicStyles<br />
| [[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.<br />
| [[mw:ResourceLoader/ResourceLoaderDynamicStyles specification|ResourceLoaderDynamicStyles]]<br />
|<br />
| Proposal<br />
|-valign="top" <br />
<br />
| review_date<br />
| 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.<br />
| [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 ]<br />
[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]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| revision<br />
| The revision of this page as reported by an underlying Version Control System. This is a free format string.<br />
| [https://github.com/krallin/meta-revision Meta Revision Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| revisit-after<br />
| 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.<br />
| [http://code.google.com/webstats/2005-12/metadata.html Google documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| rights<br />
| 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]]<br />
| [http://brittlebit.org/specifications/html-meta-rights/specification-for-html-meta-element-with-name-value-rights.html BrittleBit.org spec]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| rights-standard<br />
| 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))<br />
<br />
'''This keyword does not provide, remove or alter any legal protections or designations.'''<br />
<br />
Format: <br />
<pre><meta name="rights-standard" content="element id;rights" /></pre><br />
<br />
* element id - the HTML Element ID of the item these rights apply to<br />
* rights - what rights are assigned to the item<br />
** "pd" - Public domain<br />
** "cc by-sa" - Creative Commons Attribution<br />
** "cc by-nd" - Creative Commons NoDerivs <br />
** "cc by-nc" - Creative Commons Attribution-NonCommercial<br />
** "cc by-nc-sa" - Creative Commons Attribution-NonCommercial-ShareAlike<br />
** "cc by-nc-nd" - Creative Commons Attribution-NonCommercial-NoDerivs<br />
<br />
| [http://sites.google.com/site/metarightsstandard/ Spec]<br />
| Redundant with [http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#licensing-works Microdata vocabulary for licensing works].<br />
| Proposal<br />
<br />
|-valign="top" <br />
| robots<br />
| 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.<br />
| [http://www.robotstxt.org/meta.html About the Robots &lt;META&gt; 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<br />
| 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)<br />
| Proposal<br />
<br />
|-valign="top" <br />
| rpuPlugin<br />
| Version of installed Repost syndication service plugin<br />
| [http://www.repost.us/meta-headers-used-by-repost/ Meta Headers used by Repost]<br />
|<br />
| Proposal<br />
<br />
|-valign="top" <br />
| rqid<br />
| Request identifier of request that generated this page.<br />
| [http://wiki.whatwg.org/wiki/RequestID RequestID]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:analytics<br />
| Enables or disables Shareaholic Analytics for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:article_author<br />
| A URL to the profile of the author of the content of the webpage for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:article_author_name<br />
| Contains the name of the author of the content of the webpage for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:article_modified_time<br />
| When the article was last modified for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:article_published_time<br />
| When the article was first published for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:article_visibility<br />
| Specifies whether a webpage should be publicly recommendable for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:drupal_version<br />
| Specifies Shareaholic for Drupal module version for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:image<br />
| An image URL which represents your webpage for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:keywords<br />
| Keywords associated with the content of a webpage for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:language<br />
| Language of the content of the webpage for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:outstreamads<br />
| Enables or disables Shareaholic Outstream Ads for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:shareable_page<br />
| Specifies whether a webpage should be publicly shareable for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:site_id<br />
| Shareaholic Site ID for the website for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:site_name<br />
| The name which should be displayed for the overall site for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:title<br />
| Title associated with the content of a webpage for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:url<br />
| The canonical URL of your webpage that will be used as its permanent ID for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| shareaholic:wp_version<br />
| Specifies Shareaholic for WordPress plugin version for use with the Shareaholic Content Amplification system<br />
| [https://github.com/shareaholic/shareaholic-api-docs/blob/master/shareaholic_meta_tags.md Shareaholic CAS Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| signet:authors<br />
| Authors of a page for use with javascript signet library<br />
| [https://github.com/HubSpot/signet/blob/master/README.md Signet Revision Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| signet:links<br />
| links to related pages, for use with the javascript signet library<br />
| [https://github.com/HubSpot/signet/blob/master/README.md Signet Revision Specification]<br />
|<br />
| Proposal<br />
<br />
|-valign="top" <br />
| skype_toolbar<br />
| 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.<br />
<br />
Example:<br />
<meta name="skype_toolbar" content="skype_toolbar_parser_compatible" /><br />
| [http://skype.otherlinks.co.uk/page.asp?id=toolbar_number_formatting Skype Info]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| startIndex<br />
| Used to identify the index of the first search result in the current set of search results.<br />
| [http://www.opensearch.org/Specifications/OpenSearch/1.1#Response_metadata_in_HTML.2FXHTML OpenSearch Specification]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| startver<br />
| Used to verify WebApps for JokeNetwork's Start!-WebApp<br />
| [https://jokenetwork.de/faq/start/verification/ JokeNetwork's Start Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| subject-datetime<br />
| Identify the principal datetime ranges of the subject of the page’s content, such as the dates of an historical event.<br />
| [http://brittlebit.org/specifications/html-meta-subject-datetime/specification-for-html-meta-element-with-name-value-subject-datetime.html BrittleBit.org spec]<br />
| page-datetime<br /><br />datetime-coverage<br />datetime-coverage-start<br />datetime-coverage-end<br />datetime-coverage-vague<br /><br />
| Proposal<br />
<br />
|-valign="top" <br />
| subject-system<br />
| 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.<br />
| [http://brittlebit.org/specifications/html-meta-subject-system/specification-for-html-meta-element-with-name-value-subject-system.html BrittleBit.org spec]<br />
| subj-.&nbsp;.&nbsp;. or subj-* (namespace not approved thus synonym would be "subj-" plus whatever is after hyphen in token)<br />
| Proposal<br />
<br />
|-valign="top"<br />
| supported-media<br />
| 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.<br />
| [https://github.com/google/webpackager/blob/master/docs/supported_media.md supported-media spec]<br />
|<br />
| Proposal<br />
<br />
|-valign="top" <br />
| theme-color<br />
| 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><br />
Usage: <code><meta name="theme-color" content="papayawhip"></code><br />
| [https://html.spec.whatwg.org/multipage/semantics.html#meta-theme-color Defined in HTML]<br />
| <br />
| Standard<br />
<br />
|-valign="top" <br />
| thumbnail<br />
| 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.)<br />
| [https://support.google.com/customsearch/answer/1626955?hl=en Google page], as accessed Jan. 2, 2016. Original date unknown.<br />
| <br />
| Proposed<br />
<br />
|-valign="top" <br />
| topper<br />
| Notify website visitors of later changes; easier for website authors to maintain than RSS or Atom.<br />
| [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]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| topper-major<br />
| Limit use of topper to major changes.<br />
| [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]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| topper-minor<br />
| In use of topper, include minor changes.<br />
| [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]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| totalResults<br />
| Used to identify the number of search results available for the current search.<br />
| [http://www.opensearch.org/Specifications/OpenSearch/1.1#Response_metadata_in_HTML.2FXHTML OpenSearch Specification]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| translator<br />
| The ''translator'' meta tag is used to give credit to, and provide contact info for, the translator of a document.<br />
| [https://doc.ohreally.nl/metatag-translator The ''translator'' meta tag]<br />
|<br />
| Proposed<br />
<br />
|-valign="top" <br />
| twitter:app:country<br />
| 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.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:app:id:googleplay<br />
| String value, and should be the numeric representation of your app ID in Google Play.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:app:id:ipad<br />
| String value, should be the numeric representation of your app ID in the App Store.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:app:id:iphone<br />
| String value, should be the numeric representation of your app ID in the App Store.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:app:name:googleplay<br />
| Name of your Android app<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:app:name:ipad<br />
| Name of your iPad optimized app<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:app:name:iphone<br />
| Name of your iPhone app<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:app:url:googleplay<br />
| Your app's custom URL scheme.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:app:url:ipad<br />
| Your app's custom URL scheme.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:app:url:iphone<br />
| Your app's custom URL scheme.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:card<br />
| The card type, which will be one of "summary", "photo", "app", or "player".<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:creator<br />
| @username for the content creator / author.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:creator:id<br />
| Twitter ID for the content creator / author.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:data1<br />
| String value; value for labels such as price, items in stock, sizes, etc<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:data2<br />
| String value; value for labels such as price, items in stock, sizes, etc<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:description<br />
| A description of the content in a maximum of 200 characters.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:domain<br />
| Short URL assigned by Twitter to a website.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:image<br />
| A URL to the image representing the content.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:image0<br />
| A URL to the image representing the first photo in your gallery.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:image1<br />
| A URL to the image representing the second photo in your gallery.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:image2<br />
| A URL to the image representing the third photo in your gallery.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:image3<br />
| A URL to the image representing the fourth photo in your gallery.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:image:height<br />
| The height of the image representing the content.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:image:src<br />
| URL of image to use in the card. Image must be less than 1MB in size.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:image:width<br />
| The width of the image representing the content.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:label1<br />
| String value; label such as price, items in stock, sizes, etc<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:label2<br />
| String value; label such as price, items in stock, sizes, etc<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:player<br />
| HTTPS URL to iframe player. This must be a HTTPS URL which does not generate active mixed content warnings in a web browser<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:player:height<br />
| Height of IFRAME specified in twitter:player in pixels<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:player:stream<br />
| URL to raw stream that will be rendered in Twitter's mobile applications directly<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:player:stream:content_type<br />
| The MIME type/subtype combination that describes the content contained in twitter:player:stream<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:player:width<br />
| Width of IFRAME specified in twitter:player in pixels<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:site<br />
| @username for the website used in the card footer.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:site:id<br />
| Twitter ID for the website used in the card footer.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:title<br />
| The title of the content as it should appear in the card.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| twitter:url<br />
| Canonical URL of the card content.<br />
| <br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| typemetal.formatprefs<br />
| Per-file HTML formatting preferences used by the TypeMetal HTML editor<br />
| [http://coherencelabs.com/typemetal/manual/typemetal-custom-metadata.html TypeMetal User Guide]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| verify-v1<br />
| Superseded by google-site-verification. Legacy verification for Google Sitemaps.<br />
| [http://sitemaps.blogspot.com/2006/05/more-about-meta-tag-verification.html Inside Google Sitemaps: More about meta tag verification]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| version<br />
| The version of a web application according to the [http://semver.org/ Semantic Versioning] specification<br><br />
Example:<br />
<code><meta name="version" content="0.1.0+1"></code><br />
| [https://github.com/dvorapa/meta-version Documentation]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| vfb-version<br />
| Specifies a Visual Form Builder plugin version for Wordpress.<br />
| [http://wordpress.org/plugins/visual-form-builder/ Visual Form Builder Documentation and specs]<br />
|<br />
| Proposal<br />
<br />
|-valign="top" <br />
| <span id="viewport">viewport</span><br />
| 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:<br />
* width<br />
* height<br />
* initial-scale<br />
* minimum-scale<br />
* maximum-scale<br />
* user-scalable<br />
Examples:<br />
<meta name="viewport" content="initial-scale=1.0"><br />
<meta name="viewport" content="width=480, initial-scale=2.0, user-scalable=1"><br />
| [http://dev.w3.org/csswg/css-device-adapt/#viewport-meta CSS Device Adaptation]<br />
|<br />
| Proposal<br />
<br />
|-valign="top"<br />
| web_author<br />
| Credits the developer(s) responsible for the technical design of a website.<br />
| [http://www.metatags.info/meta_name_webauthor Documentation]<br />
| [https://sites.google.com/site/metadesignerspec/ designer] - for visual presentation<br />
| Proposal<br />
<br />
|-valign="top" <br />
| witget<br />
| Used to verify ownership for Witget.com.<br />
Example <meta name="witget" content="XXXXXXXXXXXXXXXXXXXXXX"><br />
| [http://support.witget.com/topic/435278-prostaya-ustanovka-skripta/ Witget manual]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| wot-verification<br />
| Used to verify ownership of WOT (Web Of Trust)<br />
| [http://www.mywot.com/wiki/Verify_your_website WOT's verify your site wiki page]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| wt.ac<br />
| '''Advertising Click parameter'''<br />
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:<br />
<META NAME="WT.ac" CONTENT="name"><br />
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.<br />
Examples:<br />
<a href="file111.html?WT.ac=CONTENT111"><br />
<a href="file222.html?WT.ac=CONTENT222"><br />
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 <br />
<br />
include the necessary code to generate a hit to the DCS. The maximum length for each name is 64 bytes.<br />
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| wt.ad<br />
| '''Advertising View parameter'''<br />
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.<br />
If you are selling advertising space on your web site, for example, you can collect traffic statistics to help determine pricing schedules.<br />
The following META tag tracks advertising views:<br />
<meta name="WT.ad" content="My content"><br />
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.<br />
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| wt.cg_n<br />
| '''Name of the Content Group'''<br />
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.<br />
Example:<br />
<meta name="wt.cg_n" content="My content"><br />
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| wt.cg_s<br />
| '''Name of Content Sub-Group'''<br />
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.<br />
Example:<br />
<meta name="wt.cg_s" content="My content"><br />
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| wt.mc_id<br />
| '''Identifies the ID of the marketing campaign'''<br />
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.<br />
Example:<br />
<META NAME="WT.mc_id" CONTENT="1X2GG34"><br />
You may use this parameter on the URL.<br />
Example:<br />
<a href="link?WT.mc_id=1X2GG34"><br />
The Campaign ID 1X2GG34 represents recruits to be contacted by email<br />
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| WT.si_n<br />
| '''Scenario analysis parameter - scenario name'''<br />
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.<br />
Example:<br />
<meta name="WT.si_n" content="my_scenario_name"><br />
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters].<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| WT.si_p<br />
| '''Scenario analysis parameter - scenario step name'''<br />
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.<br />
Example:<br />
<meta name="WT.si_p" content="my_scenario_step_name"><br />
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters].<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| WT.si_x<br />
| '''Scenario analysis parameter - scenario step number'''<br />
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.<br />
Example:<br />
<meta name="WT.si_x" content="my_scenario_step_number"><br />
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters].<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| wt.sv<br />
| '''Tracking Servers parameter'''<br />
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:<br />
Example:<br />
<meta name="WT.sv" content="My Server"><br />
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.<br />
For a server farm, you can extract the value of the built-in server name and dynamically assign it to the<br />
META tag using server-side scripting.<br />
Example:<br />
<meta name="WT.sv" content="Server1"><br />
<meta name="WT.sv" content="Server2"><br />
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.<br />
| [https://tagbuilder.webtrends.com/Help/Miscellaneous/AdSearch.aspx?keepThis=true&TB_iframe=true&height=450&width=650 About WT.ad].<br />
| <br />
| Proposal<br />
<br />
|-valign="top"<br />
| wt.ti<br />
| '''Tracking Page Titles'''<br />
You may want to modify a page title before sending it to Webtrends in the following cases:<br />
* 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.<br />
Unless you modify the page titles, all pages have the same title in the reports.<br />
* All pages have been assigned the same title, for reasons of style or company policy.<br />
Even though URLs are displayed in addition to page title, the entire URL cannot be depended upon to distinguish one page from another.<br />
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:<br />
<META NAME="WT.ti" CONTENT="title"><br />
Defines the name of the title for this page.<br />
| [http://product.webtrends.com/WRC/OnDemand/ResourceCenter/rc/Library/PDF/IGOD/WebTrendsAnalyticsOnDemandImplementationGuide.pdf Webtrends Parameters]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| y_key<br />
| Used to verify ownership for Yahoo! Site Explorer<br />
| [http://help.yahoo.com/l/us/yahoo/search/siteexplorer/siteexplorer-06.html Yahoo! documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| yandex-verification<br />
| Used to verify ownership for Yandex Webmaster.<br />
| [http://help.yandex.ru/webmaster/?id=995300#995356 Yandex Webmaster ownership verification]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| ZOOMCATEGORY<br />
| Category of page to be grouped in Wrensoft Zoom Search Engine.<br />
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| ZOOMDESCRIPTION<br />
| Alternative page description for Wrensoft Zoom Search Engine.<br />
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| ZOOMIMAGE<br />
| URL to image to be displayed alongside result in Wrensoft Zoom Search Engine.<br />
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| ZOOMPAGEBOOST<br />
| Page boost factor to increase or decrease the relevance of page in Wrensoft Zoom Search Engine.<br />
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| ZOOMTITLE<br />
| Alternative page title for Wrensoft Zoom Search Engine.<br />
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]<br />
| <br />
| Proposal<br />
<br />
|-valign="top" <br />
| ZOOMWORDS<br />
| Additional keywords to be indexed for Wrensoft Zoom Search Engine.<br />
| [http://www.wrensoft.com/zoom/zoommeta.html Wrensoft Zoom Meta Documentation]<br />
| <br />
| Proposal<br />
<br />
|}<br />
<br />
== 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 ==<br />
<br />
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.<br />
<br />
{| class="wikitable sortable"<br />
! Keyword<br />
! Brief description<br />
! Link to specification<br />
! Synonyms<br />
! Status<br />
! Registration requirement failure<br />
<br />
|-valign="top" <br />
| blogcatalog<br />
| Used to verify ownership of Blog Catalog.com<br />
| [http://www.blogcatalog.com/ Blog catalog site]<br />
| <br />
| Incomplete proposal<br />
| Claimed spec link is not a link to a spec<br />
<br />
|-valign="top" <br />
| created<br />
| 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.<br />
| <br />
|<br />
| Incomplete proposal<br />
| Lacks link to a spec<br />
<br />
|-valign="top"<br />
| expires<br />
| <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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
Correctly formatted example:<br />
<code><pre><meta name='expires' content='2012-12-31T23:59Z'></pre></code><br />
<br />
This tag is not to be confused with and has a different meaning than <code>meta http-equiv='expires'.</code><br />
|<br />
|<br />
| Incomplete proposal<br />
| Lacks link to a spec<br />
<br />
|-valign="top" <br />
| fb:admins<br />
| Open Graph Protocol by Facebook developers<br />
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]<br />
| <br />
| Incomplete proposal<br />
| The spec specifies this to be a value of the property attribute--not a meta keyword<br />
<br />
|-valign="top" <br />
| fb:page_id<br />
| Open Graph Protocol by Facebook developers<br />
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]<br />
| <br />
| Incomplete proposal<br />
| The spec specifies this to be a value of the property attribute--not a meta keyword<br />
<br />
|-valign="top" <br />
| gm-gpx-v<br />
| Wordpress Plugin Google Maps GPX Viewer<br />
| [http://wordpress.org/extend/plugins/google-maps-gpx-viewer/ Google Maps GPX Viewer]<br />
| <br />
| Incomplete proposal<br />
| Claimed spec link is not a link to a spec<br />
<br />
|-valign="top" <br />
| google-translate-customization<br />
| 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" /><br />
| <br />
|<br />
| Incomplete proposal<br />
| Lacks link to a spec<br />
<br />
|-valign="top" <br />
| nextgen<br />
| Used for nextgen gallery plugin in wordpress<br />
| [http://www.alexa.com/faqs/?p=188 Alexa FAQ About this meta attribute Reference]<br />
| <br />
| Incomplete proposal<br />
| Unrelated spec link<br />
<br />
|-valign="top" <br />
| nibbler-site-verification<br />
| Used to verify ownership of Nibbler site<br />
| [http://nibbler.silktide.com/ Nibbler site]<br />
| <br />
| Incomplete proposal<br />
| Claimed spec link does not link to a spec<br />
<br />
|-valign="top" <br />
| og:description<br />
| Open Graph Protocol by Facebook developers<br />
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]<br />
| <br />
| Incomplete proposal<br />
| The spec specifies this to be a value of the property attribute--not a meta keyword<br />
<br />
|-valign="top" <br />
| og:image<br />
| Open Graph Protocol by Facebook developers<br />
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]<br />
| <br />
| Incomplete proposal<br />
| The spec specifies this to be a value of the property attribute--not a meta keyword<br />
<br />
|-valign="top" <br />
| og:site_name<br />
| Open Graph Protocol by Facebook developers<br />
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]<br />
| <br />
| Incomplete proposal<br />
| The spec specifies this to be a value of the property attribute--not a meta keyword<br />
<br />
|-valign="top" <br />
| og:title<br />
| Open Graph Protocol by Facebook developers<br />
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]<br />
| <br />
| Incomplete proposal<br />
| The spec specifies this to be a value of the property attribute--not a meta keyword<br />
<br />
|-valign="top" <br />
| og:type<br />
| Open Graph Protocol by Facebook developers<br />
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]<br />
| <br />
| Incomplete proposal<br />
| The spec specifies this to be a value of the property attribute--not a meta keyword<br />
<br />
|-valign="top" <br />
| og:url<br />
| Open Graph Protocol by Facebook developers<br />
| [http://developers.facebook.com/docs/opengraph/ Facebook developers]<br />
| <br />
| Incomplete proposal<br />
| The spec specifies this to be a value of the property attribute--not a meta keyword<br />
<br />
|-valign="top" <br />
| property="og:*"<br />
| Metadata used by the Open Graph protocol (used by Facebook). Note: currently these are defined as: <meta property="og.*" content="x"/><br />
| [http://developers.facebook.com/docs/opengraph/ FAQ About the Open Graph protocol from Facebook.]<br />
| <br />
| Doesn't belong in this registry<br />
| Not a value to be used in the <code>name</code> attribute<br />
<br />
|-valign="top" <br />
| resolutions<br />
| 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.<br />
<br />
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. <br />
<br />
So, for example…<br />
<br />
<code><pre><meta name="resolutions" content="2x"></pre></code><br />
<br />
… 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. <br />
<br />
To illustrate, if her image tag is as follows…<br />
<br />
<code><pre><img src="/images/flower.jpg" alt="A flower"></pre></code><br />
<br />
… then she has two image files under /images: the low-resolution default (flower.jpg), and a higher-resolution (200%) version named flower@2x.jpg. <br />
<br />
(This is the same naming convention already used by Apple in its Cocoa Touch framework for automatically loading in higher-resolution versions of images.)<br />
<br />
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. <br />
<br />
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.<br />
<br />
<b>Multiple resolutions</b><br />
<br />
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. <br />
<br />
For example:<br />
<br />
<code><pre><meta name="resolutions" content="2x, 4x, 8x"></pre></code><br />
<br />
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.<br />
<br />
<b>Advantages</b><br />
<br />
The advantages of this approach are several:<br />
<br />
<ol><br />
<li>Makes it very simple for developers to support high-resolution displays like the iPhone 4's Retina screen</li><br />
<li>Does not require JavaScript</li><br />
<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><br />
</ol><br />
<br />
| [http://aralbalkan.com/3355 Proposal for native browser support of high-resolution image substitution]<br />
[http://aralbalkan.com/3331 How to make your web content look stunning on the iPhone 4’s new Retina display]<br />
|<br />
| Incomplete proposal<br />
| Lacks link to a spec<br />
<br />
|}<br />
<br />
== Failed Proposals ==<br />
<br />
{| class="wikitable sortable"<br />
! Keyword<br />
! Brief description<br />
! Link to more details<br />
! Synonyms<br />
! Status<br />
<br />
|-valign="top" <br />
| bot-.&nbsp;.&nbsp;.<br />
| <br />
| [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]<br />
| <br />
| Unendorsed<br />
<br />
|-valign="top" <br />
| cache<br />
| 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.<br />
| none<br />
| <br />
| Unendorsed<br />
<br />
|-valign="top" <br />
| DC.<br />
| 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"''<br />
| [http://www.DublinCore.org DCMI]<br />
| <br />
| Unendorsed<br />
<br />
|-valign="top" <br />
| dir-content-pointer<br />
| No longer useful. The function is better performed with HTML markup.<br />
| [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]<br />
| <br />
| Unendorsed<br />
<br />
|-valign="top" <br />
| no-email-collection<br />
| 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.<br />
| [https://www.ProjectHoneyPot.org/how_to_avoid_spambots_5.php Project Honey Pot]<br />
| <br />
| Unendorsed<br />
<br />
|}<br />
<br />
[[Category:Registries]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Conneg&diff=9300Conneg2013-09-10T11:44:33Z<p>TheresaOConnor: redirect to Why not conneg</p>
<hr />
<div>#REDIRECT [[Why not conneg]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=New_Features_Awaiting_Implementation_Interest&diff=9294New Features Awaiting Implementation Interest2013-09-06T23:42:57Z<p>TheresaOConnor: </p>
<hr />
<div>There are features that have been requested, but for which we are lacking implementor interest. Without two or more vendors interested in implementing the feature, they are unlikely to get added to the specs.<br />
<br />
<table class="wikitable"><br />
<tr><th rowspan=2>Feature <th colspan=6>Interest indicated by... <th rowspan=2>Comments<br />
<tr><th>Mozilla (Firefox) <th>Opera <th>Microsoft (IE) <th>Apple (Safari) <th>Google (Chrome) <th>Others<br />
<tr><br />
<td>[https://www.w3.org/Bugs/Public/show_bug.cgi?id=22682 Some way to add files to <input type=file>]<br />
<td>[http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Dec/0153.html Jonas Sicking]<br />
<td><br />
<td><br />
<td><br />
<td> Nico Weber<br />
<td><br />
<td> On track for spec<br />
<tr><br />
<td>[[AllowSeamless|Cross-origin seamless iframes]]<br />
<td>[http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Apr/0149.html Boris Zbarsky]<br />
<td><br />
<td><br />
<td><br />
<td> Adam Barth<br />
<td><br />
<td>[http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Dec/0006.html Pending input on this thread]<br />
<tr><br />
<td>[https://www.w3.org/Bugs/Public/show_bug.cgi?id=22698 HTMLCanvasElement.printCallback API]<br />
<td>Julian Viereck<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<tr><br />
<td>[http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Dec/0107.html Metadata API for media elements]<br />
<td>Ralph Giles<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td>Also needs a spec for the metadata schema<br />
<tr><br />
<td>[https://www.w3.org/Bugs/Public/show_bug.cgi?id=22696 Adding defer/async to inline scripts]<br />
<td>[http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Aug/0290.html Jonas Sicking]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<tr><br />
<td>[https://www.w3.org/Bugs/Public/show_bug.cgi?id=22675 &lt;meta name="referrer">]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td> Adam Barth<br />
<td><br />
<td><br />
<tr><br />
<td>[https://www.w3.org/Bugs/Public/show_bug.cgi?id=22699 Location.ancestorOrigins]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td> Already implemented<br />
<td><br />
<td> [http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Nov/0259.html Negative feedback from Tobie Langel]<br />
<tr><br />
<td>[https://www.w3.org/Bugs/Public/show_bug.cgi?id=22701 A method to trigger autofill]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td> [http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Oct/0231.html Elliott Sprehn], [http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Nov/0289.html Peter Kasting]<br />
<td><br />
<td><br />
<tr><br />
<td>[https://www.w3.org/Bugs/Public/show_bug.cgi?id=22676 Prerendering APIs]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td> [http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-November/037833.html Gavin Peters]<br />
<td><br />
<td> Needs detailed specification work to describe what happens with scripts running in the prerender context (since normally scripts can't run in non-active documents, and normally there's only one active document per session history).<br />
<tr><br />
<td> [https://www.w3.org/Bugs/Public/show_bug.cgi?id=22697 APIs for 'palpable' content] (at the bottom)<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td> [http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Sep/0082.html Ojan Vofai]<br />
<td><br />
<td><br />
<tr><br />
<td>Appcache: [http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Nov/0345.html More detail in error events]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td> [http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-November/038185.html Michael Nordman]<br />
<td><br />
<td><br />
<tr><br />
<td>[http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Dec/0088.html Making drawImage() have a mode to clamp at source rectangle]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td> Justin Novosad<br />
<td><br />
<td> There is a workaround using ImageBitmaps to extract a subregions of the source image. The workaround does not solve cases where sub-region extraction needs to be synchronous either because the source image content changes over time (e.g a canvas or video), or because the subrectangle coordinates cannot be determined in advance.<br />
<tr><br />
<td>Appcache: [https://www.w3.org/Bugs/Public/show_bug.cgi?id=20083 Interceptor Worker]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td> Needs use cases as well<br />
<tr><br />
<td>[https://www.w3.org/Bugs/Public/show_bug.cgi?id=22680 FormData]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<tr><br />
<td>[https://www.w3.org/Bugs/Public/show_bug.cgi?id=22674 Canvas: Stroke alignment]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<tr><br />
<td>[http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Jan/0073.html Canvas: Page flipping for the 2D context]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td>[http://lists.w3.org/Archives/Public/public-whatwg-archive/2013Jan/0098.html James Robinson]<br />
<td><br />
<td><br />
<tr><br />
<td>[http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-November/038079.html Canvas: control over when shadows paint]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<tr><br />
<td>[http://lists.w3.org/Archives/Public/public-whatwg-archive/2012May/0138.html &lt;img srcset>: a mechanism to enable adaptive images]<br />
<td><br />
<td><br />
<td><br />
<td>[https://bugs.webkit.org/show_bug.cgi?id=110252 Implemented]<br />
<td><br />
<td><br />
<td><br />
<tr><br />
<td>[https://www.w3.org/Bugs/Public/show_bug.cgi?id=17859 locale=""]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<tr><br />
<td>[http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Dec/0238.html <video> currentTime and seek using rational numbers]<br />
<td><br />
<td><br />
<td><br />
<td>[http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Dec/0232.html Jer Noble]<br />
<td><br />
<td><br />
<td> Would expose the video's timebase, too, assuming it's constant. See also next line.<br />
<tr><br />
<td>[https://www.w3.org/Bugs/Public/show_bug.cgi?id=22678 video source material metrics] (e.g. frame rate for fixed-frame-rate video data)<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<tr><br />
<td>[http://lists.w3.org/Archives/Public/public-webapps/2012OctDec/0617.html Cross-origin workers]<br />
<td><br />
<td><br />
<td>[http://lists.w3.org/Archives/Public/public-webapps/2012OctDec/0647.html Travis Leithead?]<br />
<td><br />
<td>[http://lists.w3.org/Archives/Public/public-webapps/2012OctDec/0618.html Ojan Vafai]<br />
<td><br />
<td><br />
<tr><br />
<td>[https://www.w3.org/Bugs/Public/show_bug.cgi?id=17842 Deferring &lt;img> loads until the image is needed]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<tr><br />
<td>[http://lists.w3.org/Archives/Public/public-whatwg-archive/2012Dec/0272.html API to request Web Worker latency guarantees (in exchange for guaranteeing low CPU usage)]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<td><br />
<tr><br />
<td>[http://lists.w3.org/Archives/Public/public-whatwg-archive/2010Oct/0024.html SearchBox API]<br />
<td><br />
<td><br />
<td><br />
<td><br />
<td> Tony Gentilcore<br />
<td><br />
<td> No longer being tracked.<br />
</table><br />
<br />
See also: [[Who to ask about stuff]]<br />
<br />
[[Category:Implementations]]<br />
[[Category:Spec coordination]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Data&diff=8888Data2012-12-19T20:11:34Z<p>TheresaOConnor: add dotbot</p>
<hr />
<div>This lists sources for data that can be used to research what is used on the web (to some extent).<br />
<br />
* http://html5accessibility.com/HTML5data/html.zip (Please only download if you are going to make use of the data)<br />
* [http://dotnetdotcom.org Dotbot]<br />
* ...?<br />
<br />
See also: http://www.w3.org/community/data-driven-standards/<br />
<br />
[[Category:Spec coordination]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Band_names&diff=8710Band names2012-10-30T16:36:58Z<p>TheresaOConnor: + AbA</p>
<hr />
<div>These are band names collected from #whatwg.<br />
<br />
* Bogus DOM<br />
* The Unpaired Surrogates (also Lone Surrogates)<br />
* The Designated Experts<br />
* Spidermonkey and the GC Jitters<br />
* Polyglot Heartbeat<br />
* Extant Web Corpus<br />
* Ambushed by Ambiguity</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Band_names&diff=8709Band names2012-10-30T16:07:58Z<p>TheresaOConnor: add extant web corpus</p>
<hr />
<div>These are band names collected from #whatwg.<br />
<br />
* Bogus DOM<br />
* The Unpaired Surrogates (also Lone Surrogates)<br />
* The Designated Experts<br />
* Spidermonkey and the GC Jitters<br />
* Polyglot Heartbeat<br />
* Extant Web Corpus</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=HTML_derivatives&diff=8590HTML derivatives2012-10-22T22:15:36Z<p>TheresaOConnor: add Microdata to the "republications" list</p>
<hr />
<div>This page documents specifications which have some past or present relationship to [http://www.whatwg.org/specs/web-apps/current-work/multipage/ the WHATWG HTML Standard].<br />
<br />
== Spin-offs ==<br />
<br />
Work that once took place within the WHATWG HTML Standard but that now continues elsewhere.<br />
<br />
{|border=1 cellpadding=4 cellspacing=0<br />
|-<br />
! Former section(s)<br />
! Revision<br />
! Date<br />
! Current specification<br />
! Notes<br />
|-<br />
| <!-- WD-html5-20090423:2.7 -->Determining the type of a resource<br />
| [http://html5.org/tools/web-apps-tracker?from=3233&to=3234 r3234]<br />
| 2009-06-12<br />
| [http://mimesniff.spec.whatwg.org/ MIME Sniffing] (WHATWG)<br />
| Formerly known as "Content-Type Processing Model".<br />
|-<br />
| rowspan="2" | <!-- WD-html5-20090423:2.5.2,2.5.3 -->Parsing URLs, Resolving URLs<br />
| rowspan="2" | [http://html5.org/tools/web-apps-tracker?from=3244&to=3245 r3245]<br />
| rowspan="2" | 2009-06-14<br />
| [http://url.spec.whatwg.org/ URL] (WHATWG)<br />
| <br />
|-<br />
| [http://tools.ietf.org/html/draft-ietf-iri-3987bis Internationalized Resource Identifiers (IRIs)] (IETF)<br />
|<br />
|-<br />
| <!-- WD-html5-20110525:3.5.5,3.5.6,3.5.7 --><code>innerHTML</code>, <code>outerHTML</code>, <code>insertAdjacentHTML()</code><br />
| [http://html5.org/tools/web-apps-tracker?from=6531&to=6532 r6532]<br />
| 2011-09-04<br />
| [http://domparsing.spec.whatwg.org/ DOM Parsing and Serialization] (WHATWG)<br />
| <br />
|-<br />
| rowspan="2" | Editing APIs<br />
| rowspan="2" | <br />
| rowspan="2" | <br />
| [http://dvcs.w3.org/hg/editing/raw-file/tip/editing.html HTML Editing APIs] (W3C)<br />
| <br />
|-<br />
| [http://dvcs.w3.org/hg/undomanager/raw-file/tip/undomanager.html UndoManager and DOM Transaction] (W3C)<br />
| <br />
|-<br />
| Origin<br />
| <br />
| <br />
| [http://tools.ietf.org/html/rfc6454 The Web Origin Concept] (IETF)<br />
| RFC 6454<br />
|-<br />
| rowspan="2" | Selectors API<br />
| rowspan="2" | <br />
| rowspan="2" | <br />
| [http://www.w3.org/TR/selectors-api/ Selectors API Level 1] (W3C)<br />
| <br />
|-<br />
| [http://www.w3.org/TR/selectors-api2/ Selectors API Level 2] (W3C)<br />
| <br />
|-<br />
| Web Database<br />
| <br />
| <br />
| [http://dev.w3.org/html5/webdatabase/ Web SQL Database] (W3C)<br />
| Abandoned in late 2010.<br />
|-<br />
| WebRTC<br />
| <br />
| <br />
| [http://dev.w3.org/2011/webrtc/editor/webrtc.html WebRTC] (W3C)<br />
| <br />
|-<br />
| Web Sockets<br />
| <br />
| <br />
| [http://tools.ietf.org/html/rfc6455 The WebSocket Protocol] (IETF)<br />
| RFC 6455<br />
|-<br />
| Web Subtitle Resource Tracks<br />
| <br />
| <br />
| [http://dev.w3.org/html5/webvtt/ WebVTT] (W3C)<br />
| <br />
|-<br />
| rowspan="2" | XMLHttpRequest<br />
| rowspan="2" | <br />
| rowspan="2" | <br />
| [http://xhr.spec.whatwg.org/ XMLHttpRequest] (WHATWG)<br />
| <br />
|-<br />
| [http://dvcs.w3.org/hg/xhr/raw-file/tip/Overview.html XMLHttpRequest] (W3C)<br />
|<br />
|}<br />
<br />
== Republications ==<br />
<br />
Work that is being done in the WHATWG HTML Standard and then republished separately elsewhere.<br />
<br />
{|border=1 cellpadding=4 cellspacing=0<br />
|-<br />
! Current section(s)<br />
! Derivative specification<br />
! Notes<br />
|-<br />
| <!-- 9 -->[http://www.whatwg.org/specs/web-apps/current-work/multipage/workers.html#workers Web workers]<br />
| [http://dev.w3.org/html5/workers/ Web Workers] (W3C)<br />
| <br />
|-<br />
| <!-- 10.2 -->[http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html#server-sent-events Server-sent events]<br />
| [http://dev.w3.org/html5/eventsource/ Server-Sent Events] (W3C)<br />
|<br />
|-<br />
| <!-- 10.3 -->[http://www.whatwg.org/specs/web-apps/current-work/multipage/network.html#network Web sockets]<br />
| [http://dev.w3.org/html5/websockets/ The WebSocket API] (W3C)<br />
|<br />
|-<br />
| <!-- 11 -->[http://www.whatwg.org/specs/web-apps/current-work/multipage/webstorage.html#webstorage Web storage]<br />
| [http://dev.w3.org/html5/webstorage/ Web Storage] (W3C)<br />
| <br />
|-<br />
| [http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html Microdata]<br />
| [http://dev.w3.org/html5/md/ HTML Microdata] (W3C)<br />
| <br />
|}<br />
<br />
== Forks ==<br />
<br />
Work that has forked from the WHATWG HTML Standard and may differ significantly from that document.<br />
<br />
{|border=1 cellpadding=4 cellspacing=0<br />
|-<br />
! Derivative specification<br />
! Standards body<br />
! Notes<br />
|-<br />
| [http://dev.w3.org/html5/spec/Overview.html HTML5]<br />
| W3C<br />
| Regularly takes patches from the WHATWG spec, but is not up to date and doesn't take all changes. See [http://www.whatwg.org/specs/web-apps/current-work/multipage/introduction.html#how-do-the-whatwg-and-w3c-specifications-differ? this document] for an incomplete list of differences.<br />
|}<br />
<br />
[[Category:Spec_coordination]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=User_talk:TheresaOConnor&diff=7995User talk:TheresaOConnor2012-03-14T17:51:11Z<p>TheresaOConnor: formatting test</p>
<hr />
<div> &lt;pre role=image aria-describedby=foo> )\._.,--....,'``. fL<br />
/, _.. \ _\ ;`._ ,.<br />
`._.-(,_..'--(,_..'`-.;.'&lt;/pre><br />
&lt;p id=foo hidden>An ASCII art rendition of a cat in prone position.&lt;/p></div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=User_talk:TheresaOConnor&diff=7994User talk:TheresaOConnor2012-03-14T17:50:32Z<p>TheresaOConnor: formatting test</p>
<hr />
<div> <pre role=image aria-describedby=foo> )\._.,--....,'``. fL<br />
/, _.. \ _\ ;`._ ,.<br />
`._.-(,_..'--(,_..'`-.;.'</pre><br />
<p id=foo hidden>An ASCII art rendition of a cat in prone position.</p></div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Sanitization_rules&diff=7596Sanitization rules2011-11-07T22:44:29Z<p>TheresaOConnor: Reverted edits by FrShorts7 (talk) to last revision by Ocolon</p>
<hr />
<div>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].<br />
<br />
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].<br />
<br />
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.<br />
<br />
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.<br />
<br />
=== Acceptable Elements ===<br />
<br />
* a<br />
* abbr<br />
* acronym<br />
* address<br />
* area<br />
* b<br />
* bdo<br />
* big<br />
* blockquote<br />
* br<br />
* button<br />
* caption<br />
* center<br />
* cite<br />
* code<br />
* col<br />
* colgroup<br />
* dd<br />
* del<br />
* dfn<br />
* dir<br />
* div<br />
* dl<br />
* dt<br />
* em<br />
* fieldset<br />
* font<br />
* form<br />
* h1<br />
* h2<br />
* h3<br />
* h4<br />
* h5<br />
* h6<br />
* hr<br />
* i<br />
* img<br />
* input<br />
* ins<br />
* kbd<br />
* label<br />
* legend<br />
* li<br />
* map<br />
* menu<br />
* ol<br />
* optgroup<br />
* option<br />
* p<br />
* pre<br />
* q<br />
* s<br />
* samp<br />
* select<br />
* small<br />
* span<br />
* strike<br />
* strong<br />
* sub<br />
* sup<br />
* table<br />
* tbody<br />
* td<br />
* textarea<br />
* tfoot<br />
* th<br />
* thead<br />
* tr<br />
* tt<br />
* u<br />
* ul<br />
* var<br />
* wbr<br />
<br />
==== mathml Elements ====<br />
<br />
* maction<br />
* math<br />
* merror<br />
* mfrac<br />
* mi<br />
* mmultiscripts<br />
* mn<br />
* mo<br />
* mover<br />
* mpadded<br />
* mphantom<br />
* mprescripts<br />
* mroot<br />
* mrow<br />
* mspace<br />
* msqrt<br />
* mstyle<br />
* msub<br />
* msubsup<br />
* msup<br />
* mtable<br />
* mtd<br />
* mtext<br />
* mtr<br />
* munder<br />
* munderover<br />
* none<br />
<br />
==== svg Elements ====<br />
<br />
* a<br />
* animate<br />
* animateColor<br />
* animateMotion<br />
* animateTransform<br />
* circle<br />
* defs<br />
* desc<br />
* ellipse<br />
* font-face<br />
* font-face-name<br />
* font-face-src<br />
* g<br />
* glyph<br />
* hkern<br />
* image<br />
* linearGradient<br />
* line<br />
* marker<br />
* metadata<br />
* missing-glyph<br />
* mpath<br />
* path<br />
* polygon<br />
* polyline<br />
* radialGradient<br />
* rect<br />
* set<br />
* stop<br />
* svg<br />
* switch<br />
* text<br />
* title<br />
* tspan<br />
* use<br />
<br />
=== Acceptable Attributes ===<br />
<br />
* abbr<br />
* accept<br />
* accept-charset<br />
* accesskey<br />
* action<br />
* align<br />
* alt<br />
* axis<br />
* border<br />
* cellpadding<br />
* cellspacing<br />
* char<br />
* charoff<br />
* charset<br />
* checked<br />
* cite<br />
* class<br />
* clear<br />
* cols<br />
* colspan<br />
* color<br />
* compact<br />
* coords<br />
* datetime<br />
* dir<br />
* disabled<br />
* enctype<br />
* for<br />
* frame<br />
* headers<br />
* height<br />
* href<br />
* hreflang<br />
* hspace<br />
* id<br />
* ismap<br />
* label<br />
* lang<br />
* longdesc<br />
* maxlength<br />
* media<br />
* method<br />
* multiple<br />
* name<br />
* nohref<br />
* noshade<br />
* nowrap<br />
* prompt<br />
* readonly<br />
* rel<br />
* rev<br />
* rows<br />
* rowspan<br />
* rules<br />
* scope<br />
* selected<br />
* shape<br />
* size<br />
* span<br />
* src<br />
* start<br />
* style<br />
* summary<br />
* tabindex<br />
* target<br />
* title<br />
* type<br />
* usemap<br />
* valign<br />
* value<br />
* vspace<br />
* width<br />
* xml:lang<br />
<br />
==== mathml Attributes ====<br />
<br />
* actiontype<br />
* align<br />
* columnalign<br />
* columnalign<br />
* columnalign<br />
* columnlines<br />
* columnspacing<br />
* columnspan<br />
* depth<br />
* display<br />
* displaystyle<br />
* equalcolumns<br />
* equalrows<br />
* fence<br />
* fontstyle<br />
* fontweight<br />
* frame<br />
* height<br />
* linethickness<br />
* lspace<br />
* mathbackground<br />
* mathcolor<br />
* mathvariant<br />
* mathvariant<br />
* maxsize<br />
* minsize<br />
* other<br />
* rowalign<br />
* rowalign<br />
* rowalign<br />
* rowlines<br />
* rowspacing<br />
* rowspan<br />
* rspace<br />
* scriptlevel<br />
* selection<br />
* separator<br />
* stretchy<br />
* width<br />
* width<br />
* xlink:href<br />
* xlink:show<br />
* xlink:type<br />
* xmlns<br />
* xmlns:xlink<br />
<br />
==== svg Attributes ====<br />
<br />
* accent-height<br />
* accumulate<br />
* additive<br />
* alphabetic<br />
* arabic-form<br />
* ascent<br />
* attributeName<br />
* attributeType<br />
* baseProfile<br />
* bbox<br />
* begin<br />
* by<br />
* calcMode<br />
* cap-height<br />
* class<br />
* color<br />
* color-rendering<br />
* content<br />
* cx<br />
* cy<br />
* d<br />
* dx<br />
* dy<br />
* descent<br />
* display<br />
* dur<br />
* end<br />
* fill<br />
* fill-rule<br />
* font-family<br />
* font-size<br />
* font-stretch<br />
* font-style<br />
* font-variant<br />
* font-weight<br />
* from<br />
* fx<br />
* fy<br />
* g1<br />
* g2<br />
* glyph-name<br />
* gradientUnits<br />
* hanging<br />
* height<br />
* horiz-adv-x<br />
* horiz-origin-x<br />
* id<br />
* ideographic<br />
* k<br />
* keyPoints<br />
* keySplines<br />
* keyTimes<br />
* lang<br />
* marker-end<br />
* marker-mid<br />
* marker-start<br />
* markerHeight<br />
* markerUnits<br />
* markerWidth<br />
* mathematical<br />
* max<br />
* min<br />
* name<br />
* offset<br />
* opacity<br />
* orient<br />
* origin<br />
* overline-position<br />
* overline-thickness<br />
* panose-1<br />
* path<br />
* pathLength<br />
* points<br />
* preserveAspectRatio<br />
* r<br />
* refX<br />
* refY<br />
* repeatCount<br />
* repeatDur<br />
* requiredExtensions<br />
* requiredFeatures<br />
* restart<br />
* rotate<br />
* rx<br />
* ry<br />
* slope<br />
* stemh<br />
* stemv<br />
* stop-color<br />
* stop-opacity<br />
* strikethrough-position<br />
* strikethrough-thickness<br />
* stroke<br />
* stroke-dasharray<br />
* stroke-dashoffset<br />
* stroke-linecap<br />
* stroke-linejoin<br />
* stroke-miterlimit<br />
* stroke-opacity<br />
* stroke-width<br />
* systemLanguage<br />
* target<br />
* text-anchor<br />
* to<br />
* transform<br />
* type<br />
* u1<br />
* u2<br />
* underline-position<br />
* underline-thickness<br />
* unicode<br />
* unicode-range<br />
* units-per-em<br />
* values<br />
* version<br />
* viewBox<br />
* visibility<br />
* width<br />
* widths<br />
* x<br />
* x-height<br />
* x1<br />
* x2<br />
* xlink:actuate<br />
* xlink:arcrole<br />
* xlink:href<br />
* xlink:role<br />
* xlink:show<br />
* xlink:title<br />
* xlink:type<br />
* xml:base<br />
* xml:lang<br />
* xml:space<br />
* xmlns<br />
* xmlns:xlink<br />
* y<br />
* y1<br />
* y2<br />
* zoomAndPan<br />
<br />
=== CSS Rules ===<br />
<br />
First <code>urls</code> matching the following regular expression are removed:<br />
<pre>url\s*\(\s*[^\s)]+?\s*\)\s*</pre><br />
<br />
The style strings that don't match the following are deemed obfuscated, and ignored entirely:<br />
<pre>^([:,;#%.\sa-zA-Z0-9!]|\w-\w|'[\s\w]+'|"[\s\w]+"|\([\d,\s]+\))*$</pre><br />
<pre>^(\s*[-\w]+\s*:\s*[^:;]*(;|$))*$</pre><br />
<br />
==== style Properties ====<br />
<br />
* azimuth<br />
* background, background-*<br />
* border, border-*<br />
* clear<br />
* color<br />
* cursor<br />
* direction<br />
* display<br />
* elevation<br />
* float<br />
* font<br />
* font-family<br />
* font-size<br />
* font-style<br />
* font-variant<br />
* font-weight<br />
* height<br />
* letter-spacing<br />
* line-height<br />
* margin, margin-*<br />
* overflow<br />
* padding, padding-*<br />
* pause<br />
* pause-after<br />
* pause-before<br />
* pitch<br />
* pitch-range<br />
* richness<br />
* speak<br />
* speak-header<br />
* speak-numeral<br />
* speak-punctuation<br />
* speech-rate<br />
* stress<br />
* text-align<br />
* text-decoration<br />
* text-indent<br />
* unicode-bidi<br />
* vertical-align<br />
* voice-family<br />
* volume<br />
* white-space<br />
* width<br />
<br />
==== style Property Values ====<br />
<br />
* auto<br />
* aqua<br />
* black<br />
* block<br />
* blue<br />
* bold<br />
* both<br />
* bottom<br />
* brown<br />
* center<br />
* collapse<br />
* dashed<br />
* dotted<br />
* fuchsia<br />
* gray<br />
* green<br />
* !important<br />
* italic<br />
* left<br />
* lime<br />
* maroon<br />
* medium<br />
* none<br />
* navy<br />
* normal<br />
* nowrap<br />
* olive<br />
* pointer<br />
* purple<br />
* red<br />
* right<br />
* solid<br />
* silver<br />
* teal<br />
* top<br />
* transparent<br />
* underline<br />
* white<br />
* yellow<br />
<br />
In addition, values that match the following regular expression are valid:<br />
<br />
<code>^(#[0-9a-f]+|rgb\(\d+%?,\d*%?,?\d*%?\)?|\d{0,2}\.?\d{0,2}(cm|em|ex|in|mm|pc|pt|px|%|,|\))?)$</code><br />
<br />
==== svg style Properties ====<br />
<br />
* fill<br />
* fill-opacity<br />
* fill-rule<br />
* stroke<br />
* stroke-width<br />
* stroke-linecap<br />
* stroke-linejoin<br />
* stroke-opacity<br />
<br />
=== URIs ===<br />
==== Attributes whose value is a URI ====<br />
<br />
* href<br />
* src<br />
* cite<br />
* action<br />
* longdesc<br />
* xlink:href<br />
* xml:base<br />
<br />
==== URI schemes ====<br />
<br />
* afs<br />
* aim<br />
* callto<br />
* data (see [[#Safe data URL content types]])<br />
* ed2k<br />
* feed<br />
* ftp<br />
* gopher<br />
* http<br />
* https<br />
* irc<br />
* mailto<br />
* news<br />
* nntp<br />
* rsync<br />
* rtsp<br />
* sftp<br />
* ssh<br />
* tag<br />
* tel<br />
* telnet<br />
* urn<br />
* webcal<br />
* wtai<br />
* xmpp<br />
<br />
==== Safe data URL content types ====<br />
Note: This section is being [http://wiki.whatwg.org/wiki/Talk:Sanitization_rules discussed].<br />
* text/plain<br />
* image/gif<br />
* image/jpeg<br />
* image/png</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Image_Caption&diff=7266Image Caption2011-10-10T20:16:01Z<p>TheresaOConnor: Reverted edits by RBorja97 (talk) to last revision by Annevk</p>
<hr />
<div>Image caption are often found on the web, but there is no standard markup for this.<br />
<br />
== Problem Description ==<br />
Currently, most people use either a table, custom class names, or simply put the image inside a paragraph, each option either conveying a wrong meaning or being ambiguous with the rest of the content.<br />
<br />
An interesting analysis has been done on the subject by Dan Cederholm in one of his SimpleQuiz. [http://www.simplebits.com/notebook/2004/01/20/sqxi_conclusion.html His conclusion]:<br />
<br />
<blockquote>So in this case, I might choose option A -- because visually it shows the relationship between the items better than the others. But I suppose this is bad semantics. Or maybe just another case where we don't have the 'perfect' set of defined elements for this (very) specific job.</blockquote><br />
<br />
And his option A was:<br />
<pre><br />
<p><img scr="..."><br /><br />
Caption Text</p><br />
</pre><br />
<br />
In other word, he could not figure out anything good using current elements available in HTML, and, as most people do, had to create his own solution.<br />
<br />
Setting a standard for such things -- an explicit association between the caption and the illustration -- would help image search engines, it could enable the automatic creation of a figure index for a page. It would also be benificial for sight-impaired users. The fact that image captions should be treated differently to body text (they are not in the main flow of the document) suggests this element could be important for figure handling by assistive tools allowing e.g. aural browsers to skip captions except on explicit user request.<br />
<br />
=== Current Methods and Workarounds ===<br />
See [[Image Caption Examples]] for a couple of sample cases.<br />
<br />
== Proposed Solutions ==<br />
<br />
=== <figure> with &lt;caption> ===<br />
A <figure> element contains illustrative content for the current section. It can contain a &lt;caption> element, either as the first or the last child, that will be used to describe or give a caption to the content of the figure.<br />
<br />
<pre><br />
<figure><br />
<caption>Caption Text</caption><br />
<img src="..."><br />
</figure><br />
</pre><br />
<br />
==== Processing Model ====<br />
The processing model for HTML files must be changed so that the &lt;caption> is no longer ignored when outside the context of a table. It could also be a good idea to add a new figure insertion mode that would prevent figure captions from being moved to the enclosing table when inside a table cell, otherwise &lt;figure> will break in table-based layouts.<br />
<br />
<pre><br />
<table><br />
<tr><td><br />
<figure><br />
<caption>Caption Text</caption><br />
<img src="..."><br />
</figure><br />
</td></tr><br />
</table><br />
</pre><br />
<br />
==== Limitations ====<br />
&lt;caption> being ignored by current browsers when outside a table makes it impossible to style, and it'll also be terribly broken with table layouts when figure captions end up at the top (or the bottom) of the enclosing layout table.<br />
<br />
==== Implementation ====<br />
Parsing changes in this solution could be hard to implement given &lt;caption> element's legacy within &lt;table>.<br />
<br />
Putting aside the parsing problem, there's not much else to implement for visual browsers. A good display model that could be used to display figures is already available in CSS 2.1:<br />
<br />
<pre><br />
figure { display: table; }<br />
caption { display: table-caption; }<br />
</pre><br />
<br />
This would display the figure as a one-cell table, and the caption either at the top or at the bottom (depending on the [http://www.w3.org/TR/CSS21/tables.html#propdef-caption-side caption-side] property). The interesting part of this model is that the caption's width is constrained by the width of the figure, making it the ideal choice for floated figures.<br />
<br />
==== Adoption ==== <br />
The syntax is pretty straightforward to use. "figure" and "caption" are commonly used terms to designate exactly this feature in the print world. It should be a natural choice to authors that wonder how to markup their images.<br />
<br />
This markup won't work however if an author wants the caption to be elsewhere in the document. (In this proposal, &lt;caption> is pinned to the figure's content.) It does not seem a common use case however.<br />
<br />
=== <figure> with &lt;legend> ===<br />
A <figure> element contains illustrative content for the current section. It can contain a &lt;legend> element, either as the first or the last child, that will be used to describe or give a caption to the content of the figure.<br />
<br />
<pre><br />
<figure><br />
<legend>Caption Text</legend><br />
<img src="..."><br />
</figure><br />
</pre><br />
<br />
==== Processing Model ====<br />
:''To be completed''<br />
<br />
==== Limitations ====<br />
:''To be completed''<br />
<br />
==== Implementation ====<br />
A good display model that could be used to display figures is already available in CSS 2.1, the table model. A default stylesheet could look like this:<br />
<br />
<pre><br />
figure { display: table; }<br />
figure legend { display: table-caption; }<br />
</pre><br />
<br />
This would display the figure as a one-cell table, and the figure legend either at the top or at the bottom (depending on the [http://www.w3.org/TR/CSS21/tables.html#propdef-caption-side caption-side] property). The interesting part of this model is that the legend's width is constrained by the width of the figure, making it the ideal choice for floated figures.<br />
<br />
==== Adoption ==== <br />
"figure" and "legend" are commonly used terms in the print world, so their use could prove natural to authors. It is most likely that authors that need a markup for their figure will chose this one if it is sanctioned in a standard.<br />
<br />
This markup won't work if an author wants the caption to be elsewhere in the document. (In this proposal, &lt;legend> is pinned to the figure's content.) It does not seem a common use case however.<br />
<br />
=== Adjacent &lt;caption> or <legend> ===<br />
&lt;caption> or <legend> elements directly following a <img> element give the caption text for that image.<br />
<br />
<pre><br />
<img src="..."><br />
<caption>Caption Text</caption><br />
</pre><br />
<br />
<pre><br />
<img src="..."><br />
<legend>Caption Text</legend><br />
</pre><br />
<br />
==== Processing Model ====<br />
The processing model for HTML files must be changed so that the &lt;caption> is no longer ignored when outside the context of a table. It could also be a good idea to add a new figure insertion mode that would prevent figure captions from being moved to the enclosing table when inside a table cell, otherwise &lt;figure> will break in table-based layouts.<br />
<br />
:''Are the elements in this construct inline or block-level content? Currently <img> is inline.''<br />
<br />
If any other element, or non-whitespace text nodes are found between <img> and its corresponding caption element, elements are considered to not be adjacent, the semantic link is broken and it generates a parse error.<br />
<br />
==== Limitations ====<br />
<caption> being ignored by current browsers when outside a table makes it impossible to style, and it'll also be terribly broken with table layouts when captions end up at the top (or the bottom) of the enclosing layout table.<br />
<br />
:''To be completed: <legend> parsing''<br />
<br />
==== Implementation ====<br />
Parsing changes in this solution could be hard to implement given <caption> element's legacy within &lt;table>.<br />
<br />
:''To be completed: <legend> parsing implementation''<br />
<br />
Giving a distinctive visual style to figure captions may prove difficult with this design. If a browser wants to treat figures in a distinctive manner, it'll have treat them as a special case; the adjacent element selector in CSS can't distinguish between adjacent elements which are separated by text and those that are not.<br />
<br />
==== Adoption ==== <br />
:''To be completed''<br />
<br />
"legend" and "caption" are commonly used terms in the print world, so their use could prove natural to authors. Difficulties in styling are likely however to cause authors to always warp figures in a <div> element as most already do anyway (see [[Image Caption Examples]]).<br />
<br />
This markup won't work if an author wants the caption to be elsewhere in the document. It does not seem a common use case however.<br />
<br />
=== <label> defining attributes with nested markup ===<br />
A <label> element holds a value which should be treated the same way like the title attribute on <img>, except that it can contain nested markup. The for attribute of the label contains the id of the target element. A new type attribute on the label indicates which attribute the label intend to replace on the target.<br />
<br />
<pre><br />
<img id="img1" src="..."><br />
<label for="img1" type="title">...</label><br />
</pre><br />
<br />
==== Processing Model ====<br />
:''To be completed: Attribute override, progressive rendering, etc.''<br />
<br />
==== Limitations ====<br />
:''To be completed''<br />
<br />
==== Implementation ====<br />
:''To be completed''<br />
<br />
==== Adoption ==== <br />
This markup has the benefit that it'll work if an author wants the caption to be elsewhere in the document.<br />
<br />
:''To be completed''<br />
<br />
<br />
[[Category:Proposals]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=XHTML2_versus_HTML5&diff=7265XHTML2 versus HTML52011-10-10T20:15:50Z<p>TheresaOConnor: Reverted edits by RBorja97 (talk) to last revision by Dean</p>
<hr />
<div>http://www.w3.org/MarkUp/2009/ED-xhtml-modularization2-20090123/<br />
<br />
This is not about HTML versus XHTML, instead this page is an attempt to find out where XHTML2 and HTML5 features overlap, why certain design decisions in HTML5 have been made different, and why HTML5 lacks certain features XHTML2 has.<br />
<br />
It is not an attempt to demonstrate that 5 > 2. We know that.<br />
<br />
It is also very simple at this point. I wish my time was infinite.<br />
<br />
<br />
== XHTML Document Module ==<br />
<br />
=== The html element ===<br />
<br />
XHTML2 has version="" and xsi:schemaLocation="". HTML5 has neither.<br />
<br />
'''Rationale:''' HTML5 does away with versioning in HTML defining it equivalent to CSS in that regard. XXX add something ''nice'' about why we do not have xsi:schemaLocation=""<br />
<br />
=== The head element ===<br />
<br />
XHTML2 has profile="". HTML5 has not.<br />
<br />
'''Rationale:''' it does not appear to be used in the wild.<br />
<br />
'''Note:''' this is still being debated by the HTML WG.<br />
<br />
== XHTML Structural Module ==<br />
<br />
=== The blockcode element ===<br />
<br />
HTML5 does not have this element. In HTML5 you can use &lt;pre>&lt;code> instead.<br />
<br />
'''Rationale:''' the blockcode element is not backwards compatible.<br />
<br />
=== The heading elements ===<br />
<br />
HTML5 does not have the h element. In HTML5 the h1-h6 elements work together with the section element. In XHTML2 only the h element works with the section element.<br />
<br />
'''Rationale:''' the h element is not backwards compatible. Also, it seems important to define interaction between the h1-h6 elements and the section element so authors can more easily reuse existing content and assistive technology can still make sense of invalid pages.<br />
<br />
=== The separator element ===<br />
<br />
HTML5 does not have the separator element. It does have the hr element which means and does the same thing.<br />
<br />
'''Rationale:''' the separator element is not backwards compatible and we cannot do away with the hr element so adding an equivalent element would just make matters more complex.<br />
<br />
== XHTML Text Module ==<br />
<br />
=== The abbr element ===<br />
<br />
XHTML2 has a full attribute that can reference another element which provides the expansion (within the same page). HTML5 does not. HTML5 does this implicitly by comparing element contents.<br />
<br />
'''Rationale:''' Less work for authors.<br />
<br />
=== The l element ===<br />
<br />
XXX The XHTML2 open issues list says that the br element will be added back. Does this element stay though?<br />
<br />
== XHTML Hypertext Module ==<br />
<br />
XXX This module talks about adding the access element to the head element, but the link is broken.<br />
<br />
== XHTML List Module ==<br />
<br />
HTML5 does not have a a caption element to annotate list items.<br />
<br />
'''Rationale:''' XXX<br />
<br />
=== The dl, di, dt and dd elements ===<br />
<br />
HTML5 does not have the di element. (HTML5 is much clearer in defining this, by the way.)<br />
<br />
'''Rationale:''' the di element solves a styling problem.<br />
<br />
=== The nl element ===<br />
<br />
HTML5 does not have the nl element.<br />
<br />
'''Rationale:''' XXX<br />
<br />
== XHTML Core Attributes Module ==<br />
<br />
=== The xml:id attribute ===<br />
<br />
HTML5 does not have this attribute, however, <code>xml:id</code> can be used in XHTML5 web pages.<br />
<br />
'''Rationale:''' there already is an id attribute that works fine and can be used both in HTML and XHTML web pages whereas <code>xml:id</code> can only be used in XML documents.<br />
<br />
=== The layout attribute ===<br />
<br />
HTML5 does not have this attribute.<br />
<br />
'''Rationale:''' the pre element can be used instead.<br />
<br />
== XHTML Hypertext Attributes Module ==<br />
<br />
...</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=HTML5Lib&diff=7264HTML5Lib2011-10-10T20:15:39Z<p>TheresaOConnor: Reverted edits by RBorja97 (talk) to last revision by Annevk</p>
<hr />
<div>[http://code.google.com/p/html5lib/ HTML5Lib] is a project to create both a Python-based and Ruby-based implementations of various parts of the WHATWG spec, in particular, a tokenizer, a parser, and a serializer. It is '''not''' an offical WHATWG project, however we plan to use this wiki to document and discuss the library design. The code is avaliable under an open-source MIT license.<br />
<br />
== SVN ==<br />
Please commit often with sort of detailed descriptions of what you did. If you want to make sure you're not going to redo ask on the [http://groups.google.com/group/html5lib-discuss mailing list]. For questions that could benefit from quick turnaround, talk to people on #whatwg.<br />
<br />
== General ==<br />
<br />
In comments "XXX" indicates something that has yet to be done. Something might be wrong, has not yet been written and other things in that general direction.<br />
<br />
In comments "AT" indicates that the comment documents an alternate implementation technique or strategy.<br />
<br />
== HTMLTokenizer ==<br />
<br />
The tokenizer is controlled by a single HTMLTokenizer class stored in tokenizer.py at the moment. You initialize the HTMLTokenizer with a stream argument that holds an HTMLInputStream. You can iterate over the object created to get tokens back.<br />
<br />
Currently tokens are objects, they will become dicts.<br />
<br />
=== Interface ===<br />
<br />
The parser needs to change the self.contentModelFlag attribute which affects how certain states are handled.<br />
<br />
=== Issues ===<br />
* Use of if statements in the states may be suboptimal (but we should time this)<br />
<br />
== HTMLParser ==<br />
<br />
=== Profiling on web-apps.htm ===<br />
<br />
I did some profiling on web-apps.htm which is a rather large document. Based on that I already changed a number of things which speed us up a bit. Below are some things to consider for future revisions:<br />
<br />
* utils.MethodDispatcher is invoked way too often. By pre declaring some of it in InBody I managed to decrease the amount of invocatoins by over 24.000, but InBody.__init__ is invoked about 7000 times for web-apps.htm so that amount could be higher. Not sure how to put them somewhere else though. First thing I tried was HTMLParser but references get all messed up then...<br />
: We should be able to store a single instance of each InsertionMode rather than creating a new one every time the mode switches. Hopefully we have been disiplined enough not to keep any state in those classes so the change should be painless.<br />
:: That's an interesting idea. How would that work? [[User:Annevk|Annevk]] 12:49, 25 December 2006 (UTC)<br />
::: I got an idea on how it might work and it worked! Still about 3863 invocations to utils.MethodDispatcher but it takes 0.000 CPU seconds. I suppose we can decrease that amount even more, but I wonder if it's worth it. [[User:Annevk|Annevk]] 11:37, 26 December 2006 (UTC)<br />
<br />
* 713194 calls to __contains__ in sets.py makes us slow. Takes about 1.0x CPU seconds. <br />
: I've just switched to the built-in sets type. hopefully this will help a bit [[User:Jgraham|Jgraham]] 00:30, 25 December 2006 (UTC)<br />
:: It did. (Not surprisingly when 700.000 method calls are gone...) [[User:Annevk|Annevk]] 12:49, 25 December 2006 (UTC)<br />
<br />
* 440382 calls to char in tokenizer.py is the runner up with 0.8x CPU seconds.<br />
: This is now the largest time consumer. [[User:Annevk|Annevk]] 12:49, 25 December 2006 (UTC)<br />
<br />
* dataState in tokenizer.py with 0.7 CPU seconds is next.<br />
: This is now at 0.429 CPU seconds. Probably becase the tokenizer switched to dicts instead of custom Token objects. [[User:Annevk|Annevk]]<br />
<br />
* __iter__ in tokenizer.py with 0.59x CPU seconds...<br />
<br />
* Creation of all node objects in web-apps takes .57x CPU seconds.<br />
<br />
* etc.<br />
<br />
== Testcases ==<br />
Testcases are under the /tests directory. They require [http://cheeseshop.python.org/pypi/simplejson simplejson]. New code should not be checked in if it regresses previously functional unit tests. Similarly, new tests that don't pass should not be checked in without both informing others on the [http://groups.google.com/group/html5lib-discuss mailing list] and a concrete plan. Ideally new features should be accompanied by new unit tests for those features. Documentation of the test format is available at [[Parser_tests]].<br />
<br />
<br />
<br />
[[Category:Implementations]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Rationale&diff=6862Rationale2011-08-05T16:50:27Z<p>TheresaOConnor: Reverted edits by Linkbuilidngservices (talk) to last revision by EdwardOConnor</p>
<hr />
<div><!--<br />
notes of things to add<br />
1. explanation of <device> <br />
2. Why the WHATWG version is unversioned and called HTML5...<br />
3. explain difference between W3C and WHATWG version?<br />
4. Explain all the different uses of the header, hgroup, .... elements<br />
6. http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-April/025920.html - add this somewhere.<br />
7. add header/h1 and such explanation<br />
8. Better explain Defer/async<br />
9. skip links??<br />
10. http://www.mail-archive.com/whatwg@lists.whatwg.org/msg23220.html<br />
--><br />
This document serves a rationale document for various parts of the HTML5 specification. Over time this page will be a complete rationale document.<br />
<br />
== General Rationale ==<br />
<br />
=== One Vendor, One Veto === <br />
<br />
Part of the the goal of the WHATWG is to document how web browsers actually handle HTML. As such browser vendors already have veto power - by not following the standard. The W3C and WHATWG do not have any enforcement power and can only write what browsers are willing to implement. Not removing features from the HTML standard that at least one browser vendor has stated they are unwilling to implement causes the HTML spec to not accurately document reality.<ref>http://lists.w3.org/Archives/Public/public-html/2009Jul/0257.html -- Re: Codecs for &lt;video&gt; and &lt;audio&gt;</a></ref><ref>http://lists.w3.org/Archives/Public/www-archive/2009Jul/0075.html --Formal Objection to One vendor, One Veto</ref>. The veto isn't a<br />
power that we grant browsers, it's a right that they earn on their own by virtue of having users. The minimum market share for a veto is somewhere around 1%.<ref>http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-June/026897.html</ref><br />
<br />
=== Using elements where scripts "work" ===<br />
In addition, arguments were made that JavaScript-based implementations of details suffer from problems and limitations. Scripting behavior may be inconsistent across browsers, or even unavailable in some contexts. Accessibility is "bolted on", allowing more opportunity for author error, even when using libraries. The data model is not exposed in a consistent way in the markup. And matching native appearance and behavior across a range of platforms may be impractical.<ref>http://lists.w3.org/Archives/Public/public-html/2010Jun/att-0659/issue-93-decision.html</ref><br />
<br />
=== It isn't just about web browsers ===<br />
Web browsers are not the only programs that use HTML. Sometimes elements and features are needed even when browsers won't use them in any meaningful way. Document authoring tools, validators, search engines, screen readers, outliners, researchers, etc. all need and can use more information than a browser can. Furthermore if you provide more information than is currently used by browsers it opens up room for innovation.<br />
<br />
=== Experimenting with features ===<br />
New unknown and untested features are unlikely to get accepted into the WHATWG spec. Browsers and browser extensions (like Google Gears) are expected to first establish use cases and implementation possibilities before the spec is changed. <ref>http://www.mail-archive.com/whatwg@lists.whatwg.org/msg22577.html</ref><br />
<br />
=== Versioning the spec ===<br />
Most authors don't care about whether or not an implementation supports an entire, full specification; they just want to know "Can I use this feature in this browser?" So saying that all major implementations support much of CSS 2 to a high degree of correctness is useless for knowing if, say, the author can use display: run-in. In other words, the feature tables are what web authors would actually use in real life.<ref>http://www.mail-archive.com/whatwg@lists.whatwg.org/msg23306.html</ref><br />
<br />
<!--=== HTML5 the spec vs HTML5 the buzzword ===<br />
http://www.mail-archive.com/whatwg@lists.whatwg.org/msg23299.html<br />
--><br />
<br />
=== Modifying existing semantics ===<br />
Some elements have different semantics than what HTML4 users would expect. Semantic markup isn't very useful if most pages use elements in a manner that conflicts with the defined semantics. For example, if a search engine treated dd as enclosing a term being defined, for the purposes of searching for definitions (or excluding defining occurrences from results), it would not find many definitions, and it would misclassify things.<ref>http://lists.whatwg.org/htdig.cgi/help-whatwg.org/2010-October/000668.html</ref><br />
<br />
== Specific Elements ==<br />
<br />
=== Doctype ===<br />
Since HTML5 has moved to an unversioned model the doctype does not a have version number. It is necessary for legacy browsers that will switch to standards mode only when a doctype is present.<br />
<br />
=== Plaintext ===<br />
The &lt;plaintext&gt; element is a obsolete precursor to the &lt;pre&gt; element. <ref>http://www.w3.org/MarkUp/draft-ietf-iiir-html-01.txt</ref> It is now in the HTML5 spec as a method of stopping all further html token parsing. It lacks an end tag and just emits the rest of the page as plain text. It throws a parse error upon reaching the end of the document as it is not considered a valid element (and it is missing an end-tag).<br />
<br />
=== Image ===<br />
<br />
&lt;image&gt; element is treated as an alternate (but invalid) name for &lt;img&gt;. This is because some sites (around 0.2%<ref>Email from Ian Hickson; comment in spec source</ref>) make this mistake. It is already treated as an image by most major browsers.<br />
<br />
=== Meter and Progress (are not the same thing) ===<br />
<br />
&lt;meter&gt; is not just a special case of &lt;progress&gt;. The meter element represents a scalar measurement within a known range, such as storage quota usage, a relative popularity rating or relevance indicator. The control allows for the indication of high and low ranges, or minimum, maximum and optimal levels.<br />
<br />
The progress element, on the other hand, represents the completion progress of a task. This could be a real time indicator for background processing task (e.g. using Web Workers or a file upload). Progress elmements can also be in the indeterminate state, indicating that something is in progress, but it's completion progress is unknown.<ref>http://html5doctor.com/your-questions-answered-11/</ref><br />
<br />
The default rendering for a meter element could look something like the following:<br />
<br />
<img src="http://developer.apple.com/mac/library/documentation/userexperience/conceptual/applehiguidelines/art/ct_leveldiscrete.gif" alt="example of proper rendering for the meter element"><br />
<br />
Whereas, the default rendering for the progress element could look like this:<br />
<br />
<img src="http://developer.apple.com/mac/library/documentation/userexperience/conceptual/applehiguidelines/art/ct_determprogsizes.jpg"><br />
<br />
Alternatively, an indeterminate progress bar could also be styled as a throbber, which indicates progress without any indication of the remaining progress:<br />
<br />
<img src="http://developer.apple.com/mac/library/documentation/userexperience/conceptual/applehiguidelines/art/ct_asynchprogindsizes.jpg" alt="picture of the default apple throbber"><br />
<br />
See [http://www.mail-archive.com/whatwg@lists.whatwg.org/msg01308.html Re: &lt;progress&gt; draft] for details.<br />
<br />
=== B, I, EM, STRONG, and MARK ===<br />
&lt;em&gt; is meant to indicate that some text is emphasized. &lt;strong&gt; is meant to confer importance upon text. &lt;b&gt; is meant for text that is stylistically offset from the rest of the text. Finally &lt;i&gt; is used to indicate that some text is meant to be read in an alternate mood.<br />
<br />
<!-- should I use a different sentence for each element or the same one? --><br />
For example <br />
Cats are &lt;em&gt;cute&lt;/em&gt; animals.<br />
could mean that cats are specifically cute.<br />
Cats are &lt;strong&gt;cute&lt;/strong&gt; animals.<br />
could mean that the word cute is in some way important<br />
Cats are &lt;b&gt;cute&lt;/b&gt; animals.<br />
could mean that the word cute is a new word (perhaps in a language lesson) but is not important<br />
Cats are &lt;i&gt;cute&lt;/i&gt; animals.<br />
could mean that the word cute is meant to be read in a different tone (sarcastically for example)<br />
Cats are &lt;mark&gt;cute&lt;/mark&gt; animals.<br />
means that the sentence is to be read normally but the word "cute" should be highlighted or marked in some way. This could be used for search terms on the page or alterations to an original text.<br />
<br />
=== IMG tag & alt text ===<br />
On certain types of pages adding alt text is impossible (like sites that the user could upload images but does not supply a description). Because of this the alt attribute is optional <ref>http://www.paciellogroup.com/resources/articles/altinhtml5.html</ref><ref>http://juicystudio.com/article/requiring-alt-attribute-html5.php</ref><ref>http://lists.w3.org/Archives/Public/public-html/2007Jun/0393.html</ref><br />
A longdesc attribute is not needed <ref>http://juicystudio.com/article/html5-image-element-no-alt.php</ref><br />
<br />
=== textarea ===<br />
<br />
The text area defaults to soft wrapping of the text area. The attribute @wrap can have one of the following values: soft, hard, or off.<ref>http://www.whatwg.org/specs/web-apps/current-work/#the-textarea-element-0</ref>. "off" is considered a non-conforming value because it appears to have no purpose other than a visual presentational effect. <ref>http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-August/022022.html</ref><ref>http://www.mail-archive.com/whatwg@lists.whatwg.org/msg22660.html</ref><br />
<br />
=== hgroup and other heading elements ===<br />
The point of &lt;hgroup&gt; is to hide the subtitle from the outlining algorithm.<br />
<br />
<!--<br />
=== br and linebreaks ===<br />
--><br />
=== details element === <br />
The <details> element is needed to provide an accessible way of reflecting a<br />
common application widget in HTML-based applications without requiring authors<br />
to use extensive scripting, ARIA, and platform-specific CSS to get the same<br />
effect.<ref>http://www.w3.org/Bugs/Public/show_bug.cgi?id=8379#c13</ref><ref>http://www.w3.org/html/wg/wiki/ChangeProposals/removedetails</ref><br />
<br />
== HTML parsing ==<br />
<br />
=== script element ===<br />
<br />
Why the [http://www.whatwg.org/specs/web-apps/current-work/multipage/scripting-1.html#restrictions-for-contents-of-script-elements restrictions for contents of script elements]? Why the [http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html#script-data-double-escaped-dash-dash-state complicated parsing rules for script elements]?<br />
<br />
See http://lists.w3.org/Archives/Public/public-html-comments/2010Mar/0017.html<br />
<br />
==== @DEFER and @ASYNC ====<br />
ASYNC tells the browsers to run the script with its following content at the SAME time(namely, asynchronously).<br />
DEFER tells the browsers to run the script LATER, and to run the following content first(the browsers will run the script until the page is ready).<ref>http://www.mail-archive.com/whatwg@lists.whatwg.org/msg22436.html</ref><br />
<br />
=== quirks mode ===<br />
<br />
The HTML parser has [http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html#parsing-main-inbody the following] behavior difference in quirks mode:<br />
<br />
<blockquote><dl><dt>A start tag whose tag name is "table"<br />
<dd>If the Document is not set to quirks mode, and the stack of open elements has a p element in scope, then act as if an end tag with the tag name "p" had been seen.</dl></blockquote><br />
<br />
Why? See http://hsivonen.iki.fi/last-html-quirk/<br />
<br />
=== ignored white space before head ===<br />
<br />
White space before the <code>&lt;head></code> tag is ignored. The main reason is that, given the markup<br />
<br />
<pre><br />
<!DOCTYPE html><br />
<html><br />
<head><br />
<title>Sample page</title><br />
...,<br />
</pre><br />
<br />
some people expect<br />
<br />
<pre><br />
document.documentElement.firstChild<br />
</pre><br />
<br />
to return the <code>head</code> element.<ref><cite>[http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2008-March/014148.html &#91;whatwg&#93; several messages about the tree construction stage of HTML parsing]</cite></ref><br />
<br />
<!-- needs to be confirmed --><br />
<!--<br />
=== Why all input elements are candidates for Constraint validation ===<br />
Some elements have the API but are barred because it makes it <br />
easier to loop through form.elements and do the validation stuff without <br />
checking if the validation stuff is available on the element. (Same reason <br />
<textarea> has .type.)<br />
<ref>http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-July/027195.html</ref><br />
--><br />
<br />
== Failed proposals ==<br />
=== An "advert" tag for advertisements ===<br />
There is no advert tag because if users had an easy method of plainly disabling all ads from downloading or appearing content authors would cease to use the tag.<ref>http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2008-February/013939.html</ref><br />
<br />
=== sandbox attribute on the html element ===<br />
HTML is the wrong level for disabling scripts or other features. This is the kind of thing we should do at the HTTP layer.<ref>http://www.w3.org/Bugs/Public/show_bug.cgi?id=8849</ref><ref>https://wiki.mozilla.org/Security/CSP</ref><br />
<br />
=== feature queries ===<br />
Various proposals have come up with the idea of being able to determine of a certain feature is available.<ref>http://lists.w3.org/Archives/Public/www-style/2009Dec/0130.html</ref> These fail for a variety of reasons:<br />
Part of the problem is that browser vendors will be economical with the truth. Marketing people always have an over-optimistic view of the compliance of their product, and will always give themselves the benefit of the doubt in borderline cases. Also, changing the compliance statement, to remove false claims that are exposed, is likely to a very low priority for the developers.<ref>http://lists.w3.org/Archives/Public/www-style/2010Jul/0097.html</ref><br />
With regard to CSS feature compliance: Remember that CSS<br />
provides hints and implementations don't have to accept those hints, and<br />
hardware may sometimes prevent their being implemented.<ref>http://lists.w3.org/Archives/Public/www-style/2003Nov/0000.html</ref> <br />
Some other reasons can be found in the footnotes.<ref>http://lists.w3.org/Archives/Public/www-style/2003Oct/0074.html</ref><ref>http://lists.w3.org/Archives/Public/www-style/2004Mar/0282.html</ref><br />
<br />
=== custom HTML elements ===<br />
Custom elements make it impossible for search engines, developers, and browsers to understand the semantics of a page.<ref>http://html5doctor.com/your-questions-13/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+html5doctor+%28HTML5doctor%29</ref><br />
<br />
<!--<br />
=== secure key-value data stores ===<br />
[http://www.nczonline.net/blog/securestore-proposal/ A proposal for secure key-value stores for localstorage]<ref>http://www.mail-archive.com/whatwg@lists.whatwg.org/msg20754.html</ref><br />
--><br />
<br />
== Other Pages ==<br />
<br />
* [[Why no namespaces]]<br />
* [[Why no script implements]]<br />
* [[Why not reuse legend|Why not reuse legend or another ''mini-header'' element.]]<br />
* [http://www.w3.org/html/wg/wiki/ChangeProposals/KeepNewElements Rationale for a variety of elements]<br />
* [[XHTML2 versus HTML5]]<br />
* [http://lists.w3.org/Archives/Public/public-html/2008Aug/0300.html &lt;meta http-equiv=content-language> ]<br />
* [http://www.w3.org/html/wg/wiki/RationalesGathering earlier page started with the same purpose.]<br />
* [http://www.w3.org/html/wg/wiki/ChangeProposals/KeepNewElements rationale for some new HTML5 elements]<br />
* [http://wiki.whatwg.org/wiki/FAQ WHATWG FAQ]<br />
<br />
== References ==<br />
<references/></div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Dialogs&diff=6774Dialogs2011-07-27T21:50:38Z<p>TheresaOConnor: other brainstorming</p>
<hr />
<div>= Problem statement =<br />
<br />
There's no markup or API for dialog boxes, tool palettes, hovering tooltips, the contents of popup widgets, and the like.<br />
<br />
== Real world examples today ==<br />
<br />
=== Dialogs ===<br />
<br />
==== Registration Dialogs ====<br />
<br />
* http://www.reddit.com/ - make sure to be logged out if you have an account, and click the register link<br />
* http://digg.com/ - make sure to be logged out if you have an account, and click the Join Digg! button<br />
* http://slashdot.org/ - make sure to be logged out if you have an account, and click the Join link<br />
<br />
==== Login Dialogs ====<br />
<br />
* http://slashdot.org/ - make sure to be logged out if you have an account, and click the Log In link<br />
* http://digg.com/ - make sure to be logged out if you have an account, and click the Login button<br />
* http://newsvine.com/ - make sure to be logged out if you have an account, and click the Log In | Register link<br />
* http://www.bahn.de/ - Login link is rightmost in main navigation bar - try tapping: funny handling of focus order, skipping positions, at times keyboard trap<br />
<br />
=== Other Dialogs ===<br />
<br />
* http://www.kongregate.com/ - register for account, log in, click Get Kreds, click Fund Your Account button<br />
* GMail - Click "more" on the left, then Create New Label.<br />
<br />
=== Tooltips ===<br />
<br />
* The tooltips in the table of [http://bioinfo-prod.mpl.ird.fr/xantho/x.org/gui/seqterm.php] are interesting because they are currently &lt;div>s and force the parent to be a TD rather than a TH since TH is inline only, even though the visible content is really just phrasing content.<br />
<br />
* GMail's contacts list has rich tooltips.<br />
<br />
=== Lightboxes ===<br />
<br />
* http://www.flickr.com/photos/christina_stasia/5317650777/in/pool-44124373027@N01/ - click on the magnifying glass icon in the top toolbar.<br />
* http://trailers.apple.com/trailers/independent/therift/ - click "View Trailers" and then "Teaser" - video lightbox, many other examples on trailers.apple.com<br />
* http://warmetal.wikia.com/wiki/Aegis - click on the picture of the card<br />
<br />
=== Other ===<br />
<br />
A list of URLs from Steve Faulkner to look at — if anyone has the time to go through these and pick out those that are real use cases (as opposed to demos or examples, since those tend to not reflect real needs but more reflect what's easy to demo!) then please add them where appropriate above.<br />
<br />
http://flowplayer.org/tools/overlay/index.html<br />
http://alloy.liferay.com/deploy/demos/dialog/<br />
http://www.bbc.co.uk/glow/docs/1.5/furtherinfo/widgets/overlay/<br />
http://rightjs.org/ui/dialog/demo<br />
http://jqueryui.com/demos/dialog/<br />
http://download.dojotoolkit.org/release-0.4.2/dojo-0.4.2p1-widget/tests/widget/test_Dialog.html<br />
http://www.sencha.com/examples/pages/window/hello.html<br />
http://www.sencha.com/examples/pages/window/dialog.html<br />
http://www.sencha.com/examples/pages/window/accordion.html<br />
http://dev.sencha.com/deploy/ext-4.0.2a/examples/window/window.html<br />
http://leandrovieira.com/projects/jquery/lightbox/<br />
http://www.huddletogether.com/projects/lightbox/<br />
http://developer.yahoo.com/yui/examples/container/panel.html<br />
http://reghellin.com/milkbox/<br />
http://bertramakers.com/moolabs/imagezoom.php<br />
http://www.aryweb.nl/projects/MooDialog/<br />
<br />
== Code Examples ==<br />
=== Reddit ===<br />
<br />
HTML:<br />
<pre><br />
<a href="#" onclick="return showcover(false);">register</a><br />
...<br />
<div class="login-popup cover-overlay" style="display: none; "<br />
<div class="cover" onclick="return hidecover(this)"></div><br />
<div class="popup"><br />
...<br />
</div><br />
</div><br />
</pre><br />
<br />
Javascript:<br />
<pre><br />
function showcover(a, b) {<br />
$(".login-popup:first").show().find('form input[name="reason"]').val(b || "");<br />
return !1<br />
}<br />
function hidecover(a) {<br />
$(a).parents(".cover-overlay").hide();<br />
return !1<br />
}<br />
</pre><br />
(showcover() has been truncated to remove code not relevant to showing the dialog: if variable a is set as 'true', another element (not found in this page) is also shown)<br />
<br />
CSS:<br />
<pre><br />
.popup {<br />
position: fixed;<br />
left: 10%;<br />
background-color: white;<br />
top: 40px;<br />
width: 80%;<br />
z-index: 1001;<br />
}<br />
.cover {<br />
position: fixed;<br />
top: 0px;<br />
left: 0px;<br />
height: 100%;<br />
width: 100%;<br />
background-color: gray;<br />
opacity: .7;<br />
z-index: 1000;<br />
}<br />
</pre><br />
<br />
=== Slashdot ===<br />
HTML:<br />
<pre><br />
<div id="modal_cover" class="push" onclick="hide_modal_box(); return false;" style="display: none;"></div><br />
<div id="modal_box" class="push" style="display: none;"><br />
...<br />
<div id="modal_box_content">...</div><br />
</div><br />
<br />
<a href="//slashdot.org/my/newuser" onclick="javascript:getModalPrefs('newUserModal', 'Create Account', 1); $('#modal_box').addClass('join'); return false;" class="btn link">Join</a><br />
</pre><br />
<br />
Javascript: (getModalPrefs has been truncated to remove code not relevant to showing the dialog)<br />
<pre><br />
function getModalPrefs(section, title, tabbed, params) {<br />
Slash.busy(BUSY_FETCHING_MODAL, true);<br />
$bg = get_modal_parts('#modal_cover').css('opacity', 0.75).show();<br />
$any('modal_box_content').load('/ajax.pl', $.extend({op: this_op,section: section,reskey: reskey_static,tabbed: tabbed,return_to: return_to}, params || null), function(response, status, transport) {<br />
if (status === 'success') {<br />
$any('preference_title').html(title);<br />
var $modal = show_modal_box().data('tabbed', tabbed);<br />
tabbed && $modal.addClass("tabbed");<br />
} else {<br />
$bg.hide();<br />
}<br />
Slash.busy(BUSY_FETCHING_MODAL, false);<br />
});<br />
}<br />
<br />
function show_modal_box() {<br />
return custom_modal_box('show').keyup(function(e) {<br />
e.which == $.ui.keyCode.ESCAPE && hide_modal_box();<br />
});<br />
}<br />
<br />
function hide_modal_box() {<br />
var retainclass = " ";<br />
if ($('#modal_box').hasClass('push')) {<br />
retainclasses = 'push';<br />
}<br />
custom_modal_box('hide').hide().attr('style', 'display: none;').removeClass().addClass(retainclasses).removeData('tabbed').unbind();<br />
if (document.forms.modal_prefs && document.forms.modal_prefs.refresh_onclose && document.forms.modal_prefs.refresh_onclose.value) {<br />
document.location = document.URL;<br />
}<br />
return false;<br />
}<br />
</pre><br />
<br />
CSS:<br />
<pre><br />
#modal_box.join {<br />
margin: 0px 33% 0;<br />
width: 390px;<br />
height: 440px;<br />
}<br />
#embbeded_login_modal.push, #modal_box.push {<br />
margin-top: 9em !important;<br />
}<br />
#modal_box {<br />
position: fixed;<br />
z-index: 1000001;<br />
}<br />
#modal_cover {<br />
margin-top: -12px;<br />
margin-left: -13px;<br />
background: rgba(0, 0, 0, .6);<br />
height: 100%;<br />
position: fixed;<br />
width: 100%;<br />
z-index: 1000000;<br />
}<br />
</pre><br />
<br />
===DB Dahn===<br />
HTML:<br />
<pre><br />
<li id="mn-login" class="rollover"><br />
<a href="https://fahrkarten.bahn.de/privatkunde/start/start.post?lang=de&amp;scope=login" id="login" class="jhover" rel="nofollow"><span>Login</span></a><br />
<h3><span>Login</span></h3><br />
<ul>...</ul><br />
</li><br />
</pre><br />
<br />
If #mn-login is given class of rollover (done using javascript on focus and mouseover, removed on blur, the h3 and ul tags are displayed in CSS:<br />
<pre><br />
#main-nav ul ul, #main-nav ul h3 {<br />
border: 1px solid #9FA3AB;<br />
display: none;<br />
left: -9999em;<br />
position: absolute;<br />
}<br />
#main-nav li#mn-login.rollover h3 {<br />
left: -6px;<br />
}<br />
#main-nav li#mn-login.rollover ul {<br />
left: auto;<br />
right: 6px;<br />
}<br />
</pre><br />
<br />
<br />
== Brainstorms ==<br />
<br />
(These are random ideas inspired by the above and similar APIs in other languages. They need careful evaluation and are not a proposal.)<br />
<br />
* &lt;dialog; element. defaults to display:none; height:shrinkwrap; width: shrinkwrap; position: center;.<br />
* &lt;dialog> &lt;dialogtitle> ... &lt;/dialogtitle> ... &lt;/dialog><br />
* &lt;dialog caption=""> to give title (instead of &lt;dialogtitle>)<br />
* &lt;dialog canclose=""> to toggle close box<br />
* dialog title area can be dragged (cursor:move).<br />
* dialog.show() / .hide();<br />
* show at cursor position, track cursor position, show at offset from cursor position...<br />
* have to handle showing an element that's descendant of display:none content; does that just not count?<br />
* dilaog.showModal() / .close(returnValue) / .returnValue<br />
* callbacks as arguments to show() and especially showModal(), as in, dialog.showModal(function (returnValue) { ... })<br />
* &lt;input type=dialog-button value=returnValue> / &lt;button type=dialog-button value=returnValue> - default action is to close dialog and set .returnValue to the button's value<br />
* dialog::cover { } to style a position:fixed rect that covers the viewport under a modal dialog<br />
* dialog[open] like details[open]<br />
* what does hidden="" do on such an element?<br />
* &lt;info> as a child of an element for a rich tooltip<br />
* &lt;info for=""> to give tooltip for an element that can't have children, like <img>, <option><br />
* A feature to have info boxes point at a particular other element (think the bubbles on Google maps, the new feature notifications in GMail)<br />
<br />
=== Other brainstorms ===<br />
<br />
(Proposals for similar or related functionality found elsewhere.)<br />
<br />
* http://lists.w3.org/Archives/Public/public-html-comments/2011Jul/0014.html<br />
* http://www.w3.org/Bugs/Public/show_bug.cgi?id=13348<br />
<br />
[[Category:Proposals]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Main_Page&diff=6642Main Page2011-07-05T15:55:10Z<p>TheresaOConnor: Reverted edits by Loveservice (talk) to last revision by Hixie</p>
<hr />
<div>Welcome to the WHATWG Wiki!<br />
<br />
You can be a part of our community, making proposals for the next version of HTML. This wiki is made available for you for drafting proposals, for writing essays, for keeping track of HTML-related issues, and so forth. Anyone can create an account and contribute content.<br />
<br />
Before you begin, you may wish to read our [[WHATWG Wiki:Contribution Guidelines|contribution guidelines]].<br />
<br />
==Quick Links==<br />
* [[FAQ]]<br />
* [[What you can do]] — '''[[Reviewing|Review our work!]]<br />
* [[:Category:Implementations|Implementations]]<br />
* [[Presentations]]<br />
<br />
==Web Developers==<br />
* [[Authoring|Using HTML in your Web site]]<br />
* [[Presentational elements and attributes]]<br />
* [[HTML vs. XHTML]]<br />
<br />
==Spec Development==<br />
* [[:Category:Spec coordination|Spec coordination]]<br />
* [[:Category:Proposals|Proposals]]<br />
* [[:Category:Registries|Registries]]<br />
* [[Issue Discussion]]<br />
* [[Testsuite]]<br />
<br />
==WHATWG Specifications==<br />
* [http://whatwg.org/html HTML]<br />
* [http://whatwg.org/ww Web Workers]<br />
* [http://whatwg.org/C Web Applications 1.0] (all-in-one)<br />
* See also [[FAQ#What_are_the_various_versions_of_the_spec.3F|What are the various versions of the spec?]] in the FAQ.<br />
<br />
==Communicating with the community==<br />
The WHATWG community has several channels of communication:<br />
* [[IRC]] and [http://www.whatwg.org/mailing-list mailing lists]<br />
* [http://forums.whatwg.org/ Forums]<br />
* [http://blog.whatwg.org/ The WHATWG Blog], including [http://blog.whatwg.org/category/weekly-review WHATWG Weekly]<br />
* [http://twitter.com/WHATWG @WHATWG] on twitter<br />
* [http://www.w3.org/html/planet/ W3C's Planet HTML5]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=RelExtensions&diff=6641RelExtensions2011-07-05T15:55:02Z<p>TheresaOConnor: Reverted edits by Loveservice (talk) to last revision by Tburkard</p>
<hr />
<div>=This page is obsolete=<br />
<br />
'''The HTML specification no longer references this page. It now references the Microformats "existing-rel-values" registry: http://microformats.org/wiki/existing-rel-values'''<br />
<br />
==Historical contents==<br />
<br />
''The following are the contents of this page before it was replaced.''<br />
<br />
This page lists the allowed extension values for the rel="" attribute in HTML5. You may add your own values to this list, which makes them legal HTML5 rel values. We ask that you try to avoid redundancy; if someone has already defined a value that does roughly what you want, please reuse it. Note that rel tokens are ASCII-lowercase before comparison against canonical value, so the canonical values should be listed without uppercase ASCII letters.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Keyword<br />
! Effect on <code>link</code><br />
! Effect on <code>a</code>, <code>area</code><br />
! Brief description<br />
! Link to more details<br />
! Synonyms<br />
! Status<br />
|-<br />
| pronunciation<br />
| external resource<br />
| not allowed<br />
| The referenced file contains a set of rules that associates strings of characters (e.g. words) with pronunciation instructions. For example, a rule can define whether the word "tomato" is to be spoken in the british or north-american way. These pronunciation rules should be processed by voice-enabled user-agents (e.g. web browsers that support TTS rendering), but conversely, "pronunciation" link/rel files can be completely ignored by systems that do not have speech capabilities. An example of possible format is W3C PLS (Pronunciation Lexicon Specification), with the MIME type "application/pls+xml" (and usually, the extension ".pls"). When several pronunciation lexicons are referenced within a single HTML document, and/or when a pronunciation rule is specified more than once for a given string of characters, the last occurrence of the rule takes precedence (in document order), such that any previously-defined pronunciation rule gets overridden.<br />
| [http://www.w3.org/TR/pronunciation-lexicon/ Pronunciation Lexicon Specification (PLS) Version 1.0 (W3C Recommendation 14 October 2008)] <br/> [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7601 Previously-filed bug #7601]<br />
| <br />
| Proposal<br />
|-<br />
| accessibility<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains accessibility information for the linking document.<br />
| [http://www.brucelawson.co.uk/2009/rel-accessibility/ Bruce Lawson]<br />
| <br />
| Proposal<br />
|-<br />
| acquaintance<br />
| hyperlink<br />
| hyperlink<br />
| the person represented by the current document considers the person represented by the referenced document to be an acquaintance<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| admin<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains administrative option(s) for the current document and related pages.<br />
| <br />
| option<br />
| Proposal<br />
|-<br />
| ajax<br />
| not allowed<br />
| hyperlink<br />
| The link is controlled through javascript, and will load the page linked to though an ajax interface. Without javascript, it should behave as a normal "a" tag, and content change is done server side.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| alternate<br />
|colspan=6| See HTML5<br />
|-<br />
| answer<br />
| hyperlink<br />
| hyperlink<br />
| A link to the answer to the question this section or document asks, e.g. in a FAQ or in a sample exam. Unlike ‘reply’ or ‘comment’ this resource necessarily solves the problem.<br />
| [[Talk:RelExtensions#Q_and_A|Q&A]]<br />
| (reply, comment)<br />
| Proposal<br />
|-<br />
| application-manifest<br />
| external resource<br />
| Not allowed<br />
| A manifest for this web application. The manifest contains metadata about the web application, such as its name, description, and permissions the application might require.<br />
|<br />
|<br />
| Proposal<br />
|-<br />
| archives<br />
|colspan=6| See HTML5<br />
|-<br />
| author<br />
|colspan=6| See HTML5<br />
|-<br />
| bookmark<br />
|colspan=6| See HTML5<br />
|-<br />
| canonical<br />
| hyperlink<br />
| not allowed<br />
| Robots (e.g., search engines) should treat the document containing the tag as a minor variation of the linked document, which may result in the removal of the former from a web index and in the consolidation of its quality signals in the latter. Links with rel=canonical must not specify a language, type, or different kind of media; the referenced document must have the same language, type and target media.<br />
| [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-domain<br />
| external resource<br />
| not allowed<br />
| More than one domain may have largely similar or identical content but only one of the domains should be indexed for search engines. E.g., a company may have short and long domain names for the same content.<br />
For security against traffic theft, rev must be meaningless.<br />
| [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139066 Google's analogous service] and [[Talk:RelExtensions#On_canonical-domain.2C_canonical-wwwnone.2C_and_canonical-first|Talk for this page]]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-first<br />
| external resource<br />
| hyperlink<br />
| Where the canonical value should point to a group of pages, but the link can point to only one page, the group of pages can be clarified by choosing the first page in the group and assigning the URL for this rel link.<br />
For security against traffic theft, rev must be meaningless.<br /><br />
This is only shorthand for providing two link elements, one on the noncanonical page to a "canonical" page and the other on the canonical page to the "first" page of the group.<br />
Where the group of pages corresponds to a subdirectory and a canonical URL value can point to the subdirectory resulting in a user arriving at the subdirectory's index page which is part of the group, this shorthand is unnecessary and one rel="canonical" will suffice.<br />
| [[Talk:RelExtensions#On_canonical-domain.2C_canonical-wwwnone.2C_and_canonical-first|Talk for this page]]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-human<br />
| external resource<br />
| hyperlink<br />
| Pages about a person across many websites can be associated based on name, nationality, birthplace, dates of birth and death, when flourished, and other identifiers.<br />
Search engines could more consistently aggregate same-person pages with less confusion due to name similarity.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7681 W3C Bug 7681]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-organization<br />
| external resource<br />
| hyperlink<br />
| Pages about an organization across many websites can be associated based on name, headquarters site, and other identifiers.<br />
Search engines could more consistently aggregate same-organization pages with less confusion due to name similarity.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7682 W3C Bug 7682]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-wwwnone<br />
| external resource<br />
| hyperlink<br />
| Both bare and www-prefixed domain names usually direct to the same site. Especially when external links to a site vary in the form used, search engine indexing concentrated on only one domain form may raise its credibility. The rel value is the form preferred for indexing, e.g., href="http://example.net". Nothing to the right of the top-level domain is needed.<br />
For security against traffic theft, rev must be meaningless.<br />
| [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139066 Google's analogous service] and [[Talk:RelExtensions#On_canonical-domain.2C_canonical-wwwnone.2C_and_canonical-first|Talk for this page]]<br />
| <br />
| Proposal<br />
|-<br />
| chapter<br />
| hyperlink<br />
| hyperlink<br />
| Target document is a subdocument of the current document.<br />
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]<br />
| section, subsection, appendix<br />
| Proposal<br />
|-<br />
| child<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a child of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| co-resident<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person lives in the same residence as the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| co-worker<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a co-worker of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| colleague<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a colleague of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| contact<br />
| hyperlink<br />
| hyperlink<br />
| the person represented by the current document considers the person represented by the referenced document to be a contact<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| contributor<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) involved in the production of the content, but not his main author(s).<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| crush<br />
| hyperlink<br />
| hyperlink<br />
| this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| date<br />
| hyperlink<br />
| hyperlink<br />
| this person considers the referenced person to be a date (i.e. is dating the referenced person)<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| dns-prefetch<br />
| external resource<br />
| not allowed<br />
| Force the DNS lookup of specific hostnames.<br />
| [https://developer.mozilla.org/En/Controlling_DNS_prefetching Mozilla DNS Prefetching], <br />[http://dev.chromium.org/developers/design-documents/dns-prefetching Chromium DNS Prefetching]<br />
| <br />
| Proposal<br />
|-<br />
| edit<br />
| hyperlink<br />
| hyperlink<br />
| Target document is an editable version of the current document.<br />
| [http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-11.html#new-link-relation Atom Protocol]<br />
| <br />
| Proposal<br />
|-<br />
| edituri<br />
| hyperlink<br />
| not allowed<br />
| a link to an RSD file describing how to edit the given page.<br />
| [http://cyber.law.harvard.edu/blogs/gems/tech/rsd.htm rsd]<br />
| <br />
| Proposal<br />
|-<br />
| enclosure<br />
| hyperlink<br />
| hyperlink<br />
| the destination of the hyperlink is intended to be downloaded and cached.<br />
| [http://microformats.org/wiki/rel-enclosure rel-enclosure]<br />
| <br />
| Proposal<br />
|-<br />
| enlarged<br />
| not allowed<br />
| hyperlink<br />
| For anchors that have one child image element, indicates that the linked document is an image file which is the same as the child image element of the link except a larger size (dimensions).<br />
| [http://dvdgoss.wordpress.com/2010/04/26/the-case-for-relenlarge-in-html5/ David Goss]<br />
| <br />
| Proposal<br />
|-<br />
| external<br />
|colspan=6| See HTML5<br />
|-<br />
| extension<br />
| hyperlink<br />
| hyperlink<br />
| Browser extension<br />
| [http://mozillalabs.com/jetpack/2010/05/12/indexing-and-auto-detecting-browser-extensions-on-the-web/ Mozilla Labs]<br />
| <br />
| Proposal<br />
|-<br />
| first<br />
|colspan=6| See HTML5<br />
|-<br />
| friend<br />
| hyperlink<br />
| hyperlink<br />
| the person represented by the current document considers the person represented by the referenced document to be a friend<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| gallery<br />
| hyperlink<br />
| hyperlink<br />
| A ''graphic'' index that the current document or section is a part of or that illustrates the same topic.<br />
| <br />
| (index, list)<br />
| Proposal<br />
|-<br />
| glossary<br />
| hyperlink<br />
| hyperlink<br />
| Target document provides definitions for words in current document.<br />
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]<br />
| <br />
| Proposal<br />
|-<br />
| help<br />
|colspan=6| See HTML5<br />
|-<br />
| hub<br />
| hyperlink<br />
| not allowed<br />
| Indicates a URL which implements both sides of the PubSubHubbub protocol.<br />
| [http://code.google.com/p/pubsubhubbub/ PubSubHubbub]<br />
| <br />
| Proposal<br />
|-<br />
| i18nrules<br />
| hyperlink<br />
| not allowed<br />
| Target document provides ITS (Internationalization tag Set) rules for processing the current document.<br />
| [http://www.w3.org/TR/its/ ITS]<br />
| <br />
| Proposal<br />
|-<br />
| icon<br />
|colspan=6| See HTML5<br />
|-<br />
| index<br />
|colspan=6| See HTML5<br />
|-<br />
| jump<br />
| not allowed<br />
| hyperlink<br />
| Indicates a same page jump from the current fragment to another fragment. (E.g. sometimes online newspapers insert direct text saying "article continues below the image/advert" - they could instead use "jump" link. Ultimately, it indicates a page internal link.)<br />
| [[Talk:RelExtensions#On_footnote.2C_note.2C_and_jump|Talk]]<br />
| <br />
| Proposal<br />
|-<br />
| kin<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is part of the extended family of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| lang-alt-[ISO 639-1 code]<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains a version of the current document in an alternative language. "[ISO 639-1 code]" is replaced with the appropriate [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 language code]. The ISO 639-1 code is used when the browser (or other user agent) wants to display either the full name of the language or a flag, as a visual aid for the end user.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| lang-orig-[ISO 639-1 code]<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains a version of the current document in the language the document was originally written in. "[ISO 639-1 code]" is replaced with the appropriate [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 language code]. The ISO 639-1 code is used when the browser (or other user agent) wants to display either the full name of the language or a flag, as a visual aid for the end user.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| last<br />
|colspan=6| See HTML5<br />
|-<br />
| latest-version<br />
| hyperlink<br />
| hyperlink<br />
| The referenced document is the latest version of the current document.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.txt], [http://tools.ietf.org/search/rfc5829#section-3.2 RFC5829]<br />
| <br />
| Proposal<br />
|-<br />
| license<br />
|colspan=6| See HTML5<br />
|-<br />
| login<br />
| hyperlink<br />
| hyperlink<br />
| The login keyword indicates that the referenced document provides an interface (user, pwd) to authenticate a registered user of the page/or to registrate a new user.<br />
| <br />
| search<br />
| Proposal<br />
|-<br />
| logout<br />
| external resource<br />
| not allowed<br />
| The linked document provides a resource for the UA to request when all currently open documents of the same "group" are closed (to facilitate logging out the current user).<br />
| [[LogoutRelExtension]]<br />
| <br />
| Proposal<br />
|-<br />
| <span id="longdesc">longdesc</span><br />
| hyperlink<br />
| hyperlink<br />
| Related to [http://www.w3.org/html/wg/tracker/issues/30 ISSUE-30]. <br/><abbr title="Assistive Technology">AT</abbr> should treat an element wrapped in a link with <code>rel="longdesc"</code> as equivalent to an element with <code>longdesc="URI"</code>. <br />
| (1) [http://lists.w3.org/Archives/Public/public-html/2007Jun/0738.html Eric Eggert's original proposal, 25th of June 2007], <br/>(2) [http://lists.w3.org/Archives/Public/public-html/2007Jun/0798.html Maciej's comment, 25th of June 2007], <br/>(3) [http://www.w3.org/Bugs/Public/show_bug.cgi?id=10434 Bug 10434, the HTMLwg, 2010]<br/>(4) [http://microformats.org/wiki/existing-rel-values#POSH_usage rel="longdesc" listed as POSH in Microformats.org]<br />
| <code>&lt;foo longdesc="URL"/></code> <br/>is synonymous to <br/><code>&lt;a rel="longdesc" href="URL">&lt;foo/>&lt;/a></code><br />
| Proposal<br />
|-<br />
| map<br />
| hyperlink<br />
| hyperlink<br />
| the referenced document represents a map of the location of the subject of the current document; parsers ''may'' use the URI or target page to determine coordinates.<br />
| to follow<br />
| <br />
| Proposal<br />
|-<br />
| me<br />
| hyperlink<br />
| hyperlink<br />
| the referenced document represents the same person as does the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| met<br />
| hyperlink<br />
| hyperlink<br />
| this person has met the referenced person<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| meta<br />
| external resource<br />
| hyperlink<br />
| publishing RDF/FOAF files<br />
| [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport RDF], [http://xmlns.com/foaf/spec/#sec-autodesc FOAF]<br />
| <br />
| Proposal<br />
|-<br />
| muse<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person inspires the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| neighbor<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person lives nearby the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| next<br />
|colspan=6| See HTML5<br />
|-<br />
| next-archive<br />
| hyperlink<br />
| hyperlink<br />
| A URI that refers to the immediately following archive document.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations], <br />[http://tools.ietf.org/html/rfc5005 RFC5005]<br />
| <br />
| Proposal<br />
|-<br />
| nofollow<br />
|colspan=6| See HTML5<br />
|-<br />
| noreferrer<br />
|colspan=6| See HTML5<br />
|-<br />
| noprefetch<br />
| external resource<br />
| hyperlink<br />
| Denies prefetching (not fetching) as a cost-control option for website owners, especially where pages are dynamic, leading to prefetching of wrong and useless pages.<br /><br />
The link provides a per-page denial whereas a and area provide a per-element denial.<br /><br />
For link, attributes rel="noprefetch" denies prefetching of the page at the href URL and rev="noprefetch" denies prefetching of the page bearing the link.<br /><br />
For a and area, rel is as above and rev is meaningless.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7918 W3C Bug 7918]<br />
| <br />
| Proposal<br />
|-<br />
| note<br />
| not allowed<br />
| hyperlink<br />
| An in-page or out-page jump to a footnote. This encompasses ''note'', ''footnote'', ''endnote'', and ''sidenote''.<br />
| [[Talk:RelExtensions#On_footnote.2C_note.2C_and_jump|Talk]]<br />
| <br />
| Proposal<br />
|-<br />
| openid.delegate<br />
| external resource<br />
| not allowed<br />
| OpenID 1.1 authentication delegation<br />
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID specification]<br />
| <br />
| Proposal<br />
|-<br />
| openid.server<br />
| external resource<br />
| not allowed<br />
| OpenID 1.1 authentication delegation<br />
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID specification]<br />
| <br />
| Proposal<br />
|-<br />
| openid2.local_id<br />
| external resource<br />
| not allowed<br />
| OpenID 2.0 authentication delegation<br />
| [http://openid.net/specs/openid-authentication-2_0.html#html_disco OpenID Auth 2.0 section 7.3.3]<br />
| <br />
| Proposal<br />
|-<br />
| openid2.provider<br />
| external resource<br />
| not allowed<br />
| OpenID 2.0 authentication endpoint<br />
| [http://openid.net/specs/openid-authentication-2_0.html#html_disco OpenID Auth 2.0 section 7.3.3]<br />
| <br />
| Proposal<br />
|-<br />
| parent<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a parent of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| payment<br />
| hyperlink<br />
| hyperlink<br />
| A URI where payment is accepted.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations]<br />
| <br />
| Proposal<br />
|-<br />
| pgpkey<br />
| hyperlink<br />
| not allowed<br />
| The linked document is the PGP public key file (which may contain multiple keys) of the author(s) of the page.<br />
| [http://purl.org/net/pgpkey/], [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html]<br />
| <br />
| Proposal<br />
|-<br />
| pingback<br />
|colspan=6| See HTML5<br />
|-<br />
| prefetch<br />
|colspan=6| See HTML5<br />
|-<br />
| prerender<br />
| external resource<br />
| not allowed<br />
| Prerender the specified URL including all subresources and running all scripts.<br />
| [http://dev.chromium.org/developers/design-documents/prerender Chromium Prerendering]<br />
| <br />
| Proposal<br />
|-<br />
| presentation<br />
| external resource<br />
| hyperlink<br />
| Like ‘print’ this relation references a resource that represents the same content or topic, but in a ''very'' different manner. It is similar to media=projection, but is to be used where text is substituted by graphics, animations and sounds, which goes beyond mere style switching.<br />
This relation is also appropriate for links from thumbnail to full resolution images.<br />
| <br />
| slides, slideshow<br />
| Proposal<br />
|-<br />
| prev<br />
|colspan=6| See HTML5<br />
|-<br />
| prev-archive<br />
| hyperlink<br />
| hyperlink<br />
| A URI that refers to the immediately preceding archive document.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations], <br />[http://tools.ietf.org/html/rfc5005 RFC5005]<br />
| <br />
| Proposal<br />
|-<br />
| print<br />
| external resource<br />
| hyperlink<br />
| The referenced document is recommended for printing, even though the referent document is capable of being printed and both documents are of the same type, medium, and language. A typical case is where content spread over multiple pages is also available on a single page that is more convenient to print.<br />
This is semantically more specific than "canonical" and "alternate". Where type, medium, and/or language differ, consider "alternate"; where any of them differ but the purpose is printing, consider applying both values.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7645 W3C Bug 7645]<br />
| <br />
| Proposal<br />
|-<br />
| profile<br />
| hyperlink<br />
| hyperlink<br />
| this referenced link is a metadata profile for the current document<br />
| [http://www.w3.org/TR/html401/struct/global.html#profiles HTML Meta data profiles], <br />[http://www.w3.org/2003/g/glean-profile Example of profile in a-elements]<br />
| <br />
| Proposal<br />
|-<br />
| question<br />
| hyperlink<br />
| hyperlink<br />
| A link to the question this section or document answers, e.g. in a FAQ or in a sample exam. <br />
| [[Talk:RelExtensions#Q_and_A|Q&A]]<br />
| topic, subject, problem, (up)<br />
| Proposal<br />
|-<br />
| related<br />
| hyperlink<br />
| hyperlink<br />
| this referenced link identifies a resource related to the current document<br />
| [http://tools.ietf.org/html/rfc4287#section-4.2.7 Atom Syndication Format]<br />
| <br />
| Proposal<br />
|-<br />
| reply<br />
| hyperlink<br />
| hyperlink<br />
| A follow-up posting to this document or section or in the thread this document or section is an index of.<br />
| [[Talk:RelExtensions#Threading|Thread]]<br />
| posting, comment<br />
| Proposal<br />
|-<br />
| resource-package<br />
| external resource<br />
| not allowed<br />
| The linked document is a zipped resource package<br />
| [http://limi.net/articles/resource-packages/ Resource Packages]<br />
| <br />
| Proposal<br />
|-<br />
| resources<br />
| external resource<br />
| not allowed<br />
| a higher level alternative to HTTP Content Negotiation for other resources linked from the document, in a yet to be specified format<br />
|<br />
| resource-description, content-negotiation<br />
| Proposal<br />
|-<br />
| reviewer<br />
| hyperlink<br />
| not allowed<br />
| The linked document is the page/email an agent (people or firm or...) responsible for reviewing the content.<br />
| [http://wiki.csswg.org/test/css2.1/format#reviewer]<br />
| <br />
| Proposal<br />
|-<br />
| script<br />
| not allowed<br />
| not allowed<br />
| Was proposed to replace &lt;script>. Use &lt;script> instead.<br />
| none<br />
| <br />
| Rejected<br />
|-<br />
| search<br />
|colspan=6| See HTML5<br />
|-<br />
| self<br />
| hyperlink<br />
| hyperlink<br />
| A URI that refers to a resource equivalent to the containing element.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations], <br />[http://tools.ietf.org/html/rfc4287 RFC4287]<br />
| <br />
| Proposal<br />
|-<br />
| service<br />
| external resource<br />
| not allowed<br />
| Points to a resource describing a service API<br />
| [[ServiceRelExtension]]<br />
| <br />
| Proposal<br />
|-<br />
| shortlink<br />
| hyperlink<br />
| hyperlink<br />
| Identifies a shorter form of the URL for the current document, provided by the document owner.<br />
| [http://code.google.com/p/shortlink/wiki/Specification shortlink Specification]<br />
| <br />
| Proposal<br />
|-<br />
| sibling<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a sibling of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| sidebar<br />
|colspan=6| See HTML5<br />
|-<br />
| spouse<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a spouse of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| statechart<br />
| external resource<br />
| not allowed<br />
| A reference to an SCXML document that controls the application-flow of the current HTML document<br />
| [http://www.w3.org/TR/scxml/ SCXML]<br />
|<br />
| Proposal<br />
|-<br />
| stylesheet<br />
|colspan=6| See HTML5<br />
|-<br />
| subresource<br />
| hyperlink<br />
| not allowed<br />
| The referenced document is a subresource of the current document.<br />
| <br />
|<br />
| Proposal<br />
|-<br />
| sweetheart<br />
| hyperlink<br />
| hyperlink<br />
| this person considers the referenced person to be their sweetheart<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| tag<br />
|colspan=6| See HTML5<br />
|-<br />
| technicalauthor<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) responsible for the technical construction of the page (i.e. the HTML/CSS/PHP code), not for the content.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| thread<br />
| hyperlink<br />
| hyperlink<br />
| A hierarchic list of topic(s) and replies where this document or section belongs to either one.<br />
| [[Talk:RelExtensions#Threading|Thread]]<br />
| (index)<br />
| Proposal<br />
|-<br />
| timesheet<br />
| external resource<br />
| not allowed<br />
| SMIL Timesheet<br />
| [http://www.w3.org/TR/timesheets/#smilTimesheetsNS-Elements-Timesheet SMIL Timesheets 1.0]<br />
| <br />
| Proposal<br />
|-<br />
| topic<br />
| hyperlink<br />
| hyperlink<br />
| The initial posting this document or section is a reply to or index of.<br />
| [[Talk:RelExtensions#Threading|Thread]]<br />
| subject, (top)<br />
| Proposal<br />
|-<br />
| translatedfrom<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email that has been translation source for the current document. It also indicates that the current document is a translation and not an original work.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| translator<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) responsible for the translation of the page. It also indicates that the current page is a translation of an other document, which should be linked through a rel="translatedfrom".<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| up<br />
|colspan=6| See HTML5<br />
|-<br />
| us<br />
| hyperlink<br />
| hyperlink<br />
| The referenced document represents the same organisation as does the current document [cf rel-me]<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| webmaster<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) available for requests about the content of the page.<br />
| <br />
| maintainer<br />
| Proposal<br />
|-<br />
| widget<br />
| hyperlink<br />
| hyperlink<br />
| Points to a widget.<br />
| [http://dev.w3.org/2006/waf/widgets/Overview.html#autodiscovery Widgets 1.0 Editor's draft]<br />
| <br />
| Proposal<br />
|-<br />
| wlwmanifest<br />
| hyperlink<br />
| not allowed<br />
| A link to a manifest for Windows Live Writer.<br />
| [http://msdn.microsoft.com/en-us/library/bb463263.aspx msdn]<br />
| <br />
| Proposal<br />
|}<br />
<!-- Science: proof, lemma, theorem --><br />
<br />
The "Effect on link" column must either say "not allowed" if the rel value is not allowed on &lt;link> elements, "hyperlink" if the rel value creates a hyperlink, or "external resource" if the rel value creates a link to an external resource.<br />
<br />
The "Effect on a and area" column must either say "not allowed" or "hyperlink".<br />
<br />
For the "Status" section to be changed to "Accepted", the proposed keyword must either have been through the [http://microformats.org/wiki/process Microformats process], and been approved by the Microformats community; or must be defined by a W3C specification in the Candidate Recommendation or Recommendation state. If it fails to go through this process, it is "Rejected".<br />
<br />
For more details, see [http://whatwg.org/specs/web-apps/current-work/#linkTypes the HTML5 specification].<br />
<br />
===See also===<br />
*[http://microformats.org/wiki/existing-rel-values the Microformats wiki page on this matter].<br />
*[http://blogs.plos.org/mfenner/2011/02/14/how-to-use-citation-typing-ontology-cito-in-your-blog-posts/ How to use Citation Typing Ontology (CiTO) in your blog posts] - proposes several values for marking up academic citations, but confuses the direction of the relationship (note comments)<br />
<br />
[[Category:Registries]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=HTML_vs._XHTML&diff=6640HTML vs. XHTML2011-07-05T15:54:08Z<p>TheresaOConnor: Reverted edits by Loveservice (talk) to last revision by Brettz9</p>
<hr />
<div>== Differences Between HTML and XHTML ==<br />
<br />
<p style="border: 1px dashed lightgray; background-color: #FFEEEE; padding: .5em 1em;"><strong>This page is currently being revised. Some information is incomplete or missing.</strong></p><br />
<br />
<p style="border: 1px dashed lightgray; background-color: #FFF8E4; padding: .5em 1em;">Please note that the information in here is based upon the current spec for (X)HTML5. Some of the issues technically do not apply to previous versions of HTML.</p><br />
<br />
Although HTML and XHTML appear to have similarities in their syntax, they are significantly different in many ways.<br />
<br />
:'''Note''': As the current WHATWG document is a draft, this section will need to track to a moving target.<br />
<br />
The document at http://dev.w3.org/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html provides a similar analysis.<br />
<br />
=== Overlap Language ===<br />
<br />
There is a community who find it valuable to be able to serve HTML5 documents which are also valid XML documents. They may, for example, use XML tools to generate the document, and they and others may process the document using XML tools. These documents are served as text/html.<br />
<br />
This language is sometimes called "polyglot". It is the overlap language of documents which are both HTML5 documents and XML documents. Guidelines are listed below for how one can construct such a polyglot document which will work in either environment. Besides following the well-formedness rules of XML, there are some other restrictions to which one must adhere (for the sake of text/html documents).<br />
<br />
This wiki web page is an example of such a document. You can parse it with an XML parser or an HTML parser.<br />
<br />
=== MIME Types ===<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! Feature<br />
! HTML Requirement<br />
! XHTML Requirement<br />
! Notes<br />
|-<br />
| Mime Type<br />
| Must use <code>text/html</code>.<br />
| Must use an XML MIME type, such as <code>application/xml</code> or <code>application/xhtml+xml</code>.<br />
| It is the MIME type that determines what type of document you are using. Any document, including a document authored with the intention of being XHTML, served as <code>text/html</code> is technically an HTML document.<br />
|}<br />
<br />
Note that XHTML 1.0 previously defined that documents adhering to the compatibility guidelines were allowed to be served as <code>text/html</code>, but HTML 5 now defines that such documents are HTML, not XHTML.<br />
<br />
=== Syntax and Parsing ===<br />
<br />
XHTML uses XML parsing requirements. HTML uses its own which are defined much more closely to the way browsers actually handle HTML today. The following table describes the differences between how each is parsed.<br />
<br />
The column on "Guidance for XHTML-HTML compatibility" lists ways in which a document can be crafted to work in either XHTML or HTML. The item will be bolded if it is a requirement for XHTML-compliant code to be changed, since XHTML will otherwise usually work as HTML, at least if its full features are constrained.<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! Feature<br />
! HTML Requirement<br />
! XHTML Requirement<br />
! Notes<br />
! Guidance for XHTML-HTML compatibility<br />
|-<br />
!Parsing Modes<br />
|Three parsing modes are defined: ''no quirks mode'', ''quirks mode'' and ''limited quirks mode''. The mode is only ever changed from the default by the HTML parser, based on the presence, absence, or value of the DOCTYPE string, respectively. <br />
|XML parsing rules are used. There is only one mode.<br />
|The parsing modes in HTML also have an effect upon script and stylesheet processing. XHTML is considered to be in ''no quirks mode'' for these purposes.<br />
| '''Use an explicit <code>&lt;!DOCTYPE html&gt;</code> (case insensitively) or legacy-compat version <code>&lt;!DOCTYPE html SYSTEM "about:legacy-compat"&gt;</code> for the sake of HTML and thus trigger no quirks parsing.'''<br />
|-<br />
!Error Handling<br />
|HTML does not have a well-formedness constraint, no errors are fatal. Graceful error handling and recovery procedures are thoroughly defined.<br />
|Well-formedness errors are fatal<br />
| <br />
| Ensure there are no well-formedness errors.<br />
|-<br />
! Character Encoding (including XML Declaration, <code>meta</code>)<br />
| The XML declaration is forbidden (treated as a bogus comment, but such style of comments are deprecated), but the <code>meta</code> element with a <code>charset</code> attribute may be used instead.<br />
If the encoding is unspecified in HTML, it should be determined through implementation specific heuristics or fallback to a default value (Note: this section of the spec is not yet finished).<br />
| The XML declaration may be used to [http://wiki.whatwg.org/wiki/FAQ#How_do_I_specify_the_character_encoding.3F specify the character encoding], while <code>meta</code> is only allowed as case-insensitive "UTF-8" (and is ignored if included).<br />
The default character encoding for XHTML is, according to XML rules, <code>UTF-8</code> or <code>UTF-16</code>.<br />
|<br />
| '''If you need to include XML 1.1-only markup, if you do not wish to convert the encoding of the document to UTF-8 or UTF-16 (since use of other encodings also requires a declaration), or if you wish to define an external SYSTEM DTD in the DOCTYPE but use standalone=yes (redundant?), you must use an XML Declaration for XHTML, but this may not be allowable in the future in HTML. For future compatibility, it would be best to avoid XML 1.1-only markup, convert to UTF-8 or UTF-16 (probably UTF-8 which could allow use of a <code>meta</code> tag), and avoid use of a SYSTEM DTD (rendering the standalone=yes unnecessary), respectively. Do not use a <code>meta</code> tag, unless it is UTF-8 (and included in the first 512 bytes of the document), in which case it is probably a good idea to include it for the sake of HTML (as <nowiki><meta charset="UTF-8"></nowiki>) in case you cannot specify such in a content header.'''<br />
|-<br />
!Namespaced elements<br />
|Elements and attributes for known vocabularies (HTML, SVG and MathML) are implicitly assigned to appropriate namespaces, according to the rules specified in the parsing algorithm. Elements in the HTML, SVG, or MathML namespaces may have an <code>xmlns</code> attribute explicitly specified, if, and only if, it has the exact value <code>"http://www.w3.org/1999/xhtml"</code> (see [http://wiki.whatwg.org/wiki/FAQ#What_is_the_namespace_declaration.3F namespace declaration]). The attribute has absolutely no effect. It is basically a talisman. It is allowed merely to make migration to and from XHTML mildly easier. When parsed by an HTML parser, the xmlns attribute itself ends up in no namespace. Foreign elements are also not treated as being in another namespace and will have no effect except for displaying by default as inline elements (and be aware that self-closing elements cannot be used as such since unrecognized elements will be treated as though they are non-void; thus one cannot, for example, type <code><caesura /></code> in HTML or it will be treated as though there is no immediate closing tag). Namespaced prefixes are not allowed on HTML elements; a prefixed xmlns attribute cannot be used even if it is defined in the XHTML namespace.<br />
| The XHTML namespace must be declared for HTML elements according to the rules defined by the ''[http://www.w3.org/TR/REC-xml-names/ Namespaces in XML]'' specification. Namespaces must be explicitly declared. The <code>xmlns</code> attribute ends up in the <code>"http://www.w3.org/2000/xmlns"</code> namespace. Foreign elements can be used independently of HTML elements, as long as they are assigned to their own namespace.<br />
|<br />
| Declare HTML namespaces (or other namespaces) explicitly and do not prefix XHTML elements. '''Do not depend on the behavior of foreign namespaced elements in an HTML setting; if you need to include these, you will probably wish to set this foreign markup via CSS to <code>display:none</code>. You should explicitly close (not self-close) all empty elements defined in a non-XHTML namespace, since otherwise when used in HTML, HTML will treat them as though they have not been closed.'''<br />
|-<br />
!Namespaced attributes on HTML elements<br />
| Attributes of the form <code>xmlns:<var>prefix</var></code> may not be used on HTML elements. <br />
| The <code>xmlns:<var>prefix</var></code> attributes end up in the <code>"http://www.w3.org/2000/xmlns"</code> namespace.<br />
|<br />
| '''Do not use namespaced attributes on HTML elements. Do not depend on the behavior of foreign attributes in an HTML setting.'''<br />
|-<br />
!Namespace attributes on foreign elements<br />
|<br />
Elements in the SVG namespace may have an <code>xmlns</code> attribute specified, if, and only if, it has the exact value <code>"http://www.w3.org/2000/svg"</code>. The attribute is optional because the namespace is implied during parsing.<br />
<br />
Elements in the MathML namespace may have an <code>xmlns</code> attribute specified, if, and only if, it has the exact value <code>"http://www.w3.org/1998/Math/MathML"</code>. The attribute is optional because the namespace is implied during parsing.<br />
<br />
Foreign elements may also have an <code>xmlns:xlink</code> attribute specified, if, and only if, it has the exact value <code>"http://www.w3.org/1999/xlink"</code>. This attribute is optional, even if XLink attributes are used, because the namespaces for XLink attributes is implied during parsing.<br />
<br />
When parsed by an HTML parser, the <code>xmlns</code> and <code>xmlns:xlink</code> attributes end up in the <code>"http://www.w3.org/2000/xmlns"</code> namespace.<br />
|The SVG and MathML namespaces must be declared for SVG and MathML elements, respectively, according to the rules defined by ''Namespaces in XML''. The <code>xmlns</code> and <code>xmlns:<var>prefix</var></code> attributes end up in the <code>"http://www.w3.org/2000/xmlns"</code> namespace.<br />
|<br />
|-<br />
!XLink attributes<br />
|Foreign elements may use the attributes <code>xlink:actuate</code>, <code>xlink:arcrole</code>, <code>xlink:href</code>, <code>xlink:role</code>, <code>xlink:show</code>, <code>xlink:title</code> and <code>xlink:type</code>. These attributes are placed in the <code>"http://www.w3.org/1999/xlink"</code>. The prefix used must be "<code>xlink</code>".<br />
|XLink attributes may be specified on foreign elements using any prefix, subject to the conformance rules defined by ''Namespaces in XML''. The XLink namespace must be declared according to the conformance rules defined by ''Namespaces in XML'' if XLink attributes are used within the document.<br />
|<br />
| '''Do not use XLink attributes on HTML elements and do not depend on them on foreign elements as will not work as such in HTML.''' If being used, ensure they have the appropriate XLink namespace defined.<br />
|-<br />
!XML attributes<br />
|<br />
Foreign elements may use the attributes <code>xml:lang</code>, <code>xml:id</code>, <code>xml:base</code> and <code>xml:space</code>. These attributes are placed in the <code>"http://www.w3.org/XML/1998/namespace"</code>. The prefix used must be "<code>xml</code>".<br />
<br />
HTML elements may use the <code>xml:lang</code> attribute. The attribute in no namespace with no prefix and with the literal localname "<code>xml:lang</code>" has no effect on language processing (as does "<code>lang</code>". HTML elements must not use the <code>xml:base</code>, <code>xml:space</code>, or <code>xml:id</code> attributes.<br />
| Any element, including HTML elements, may use the attributes <code>xml:lang</code>, <code>xml:id</code>, <code>xml:base</code> and <code>xml:space</code>. These attributes are placed in the <code>"http://www.w3.org/XML/1998/namespace"</code>. The prefix used must be "<code>xml</code>".<br />
|<br />
| '''Though they can be used on foreign elements, do not use <code>xml:base</code>, <code>xml:id</code>, or <code>xml:space</code> on HTML elements; use both xml:lang and lang attributes whenever one is to be needed on HTML elements.'''<br />
|-<br />
!Attributes<br />
| Names are not case sensitive. Attribute minimization is allowed (i.e. omitting the equals sign and the value).<br />
| Names are case sensitive (and lower case). Attribute minimization is not allowed. <br />
|<br />
| Use lower case attribute names. Do not minimize attributes. Non-namespaced attributes not belonging to HTML will be included in the DOM tree and accessible to script and stylesheets, but it is discouraged to use these due to the potential for future naming conflicts; <code>data-</code> attributes can be used instead, or if in an XML-only environment, namespaced attributes.<br />
|-<br />
!Attribute values<br />
| White space characters are not normalized. Unquoted attribute values are allowed. Fixed or default attribute values ...?<br />
| White space characters are [http://www.w3.org/TR/REC-xml/#AVNormalize normalized] to single spaces (unless attribute is of CDATA type?). Unquoted attribute values are not allowed. Default attribute values could conceivably be defined with a DTD.<br />
|<br />
| Create whitespace in attribute values which is already normalized (converted to single spaces). Always quote attribute values. '''Do not rely on defining default or fixed attribute values (or elements with exclusively element content) in a DTD (unless it matches HTML behavior).'''<br />
|-<br />
!Space characters<br />
|The space characters are defined as:<br />
* U+0009 CHARACTER TABULATION<br />
* U+000A LINE FEED<br />
* U+000C FORM FEED<br />
* U+000D CARRIAGE RETURN<br />
* U+0020 SPACE<br />
|The space characters are defined as:<br />
* U+0009 CHARACTER TABULATION<br />
* U+000A LINE FEED<br />
* U+000D CARRIAGE RETURN<br />
* U+0020 SPACE<br />
|The difference is the inclusion of Form Feed. Form feed characters are discouraged in XML 1.1.<br />
| Do not use the form feed character.<br />
|-<br />
! The DOCTYPE<br />
|<br />
A DOCTYPE is a mostly useless, but required, header. The DOCTYPE is used during parsing to determing the parsing mode. The keywords "<code>DOCTYPE</code>", "<code>PUBLIC</code>" and "<code>SYSTEM</code>", and the name "<code>html</code>" are treated case insensitively. The system identifier <code>"about:legacy-compat"</code> (and the public and system identifiers for previous versions of HTML) are case sensitive.<br />
<br />
Conforming HTML documents are required to use <code>&lt;!DOCTYPE html&gt;</code> (case insensitively) or the legacy-compat version <code>&lt;!DOCTYPE html SYSTEM "about:legacy-compat"&gt;</code>.<br />
<br />
When using the obsolete but conforming DOCTYPEs based on the HTML 4.0 and 4.01 Strict DTDs, the system identifier is optional. The obsolete but conforming DOCTYPEs based on XHTML 1.0 Strict and XHTML 1.1 may also be specified.<br />
<br />
Use of an internal subset is forbidden. The system identifier is never de-referenced by HTML implementations.<br />
|<br />
The DOCTYPE is optional. XML rules for case sensitivity apply (everything is case sensitive).<br />
<br />
Either of the DOCTYPEs defined in HTML5 may be used, or any other custom DOCTYPE. If the public identifier is specified, the system identifier must also be specified. The obsolete status of the ''obsolete permitted DOCTYPEs'' defined for HTML does not apply to XHTML. Any DOCTYPE may be used, subject to the conformance rules defined by XML.<br />
<br />
Use of an internal subset is permitted according to the requirements of XML. Some validating XML processors may dereference the system identifier, if used, but most browsers use non-validating processors.<br />
|<br />
| '''Use the empty DOCTYPE with no SYSTEM or PUBLIC identifiers and no use of internet subset.'''<br />
|-<br />
! Element names<br />
| Element names are case insensitive.<br />
| Element names are case sensitive and lower-case.<br />
| <br />
| Only use lower-case element names (as with attributes).<br />
|-<br />
! Void vs. Non-void Elements<br />
| Void elements only have a start tag; end tags must not be specified for void elements, and it is impossible for them to contain any content. A trailing slash may optionally be inserted at the end of the element's tag, immediately before the closing greater-than sign. For non-void elements (e.g., <nowiki><script></nowiki>), the trailing slash is a parsing error (ignored and thus treated as unclosed).<br />
| Void elements may use either the empty-element tag syntax (''EmptyElemTag'') or use a start tag immediately followed by an end tag, with no content in between. While it is possible for the element to contain content, this is non-conforming.<br />
|<br />
| '''For void elements (e.g., <nowiki><br /></nowiki>), do not include content or use a closing tag; only use a self-closing element with closing slash at the end (with a space preceding it for the sake of older browsers). For non-void elements, i.e., where content can exist (e.g., <nowiki><script></nowiki>), always use an explicit closing tag (not a self-closing tag) even if there is no content.'''<br />
|-<br />
! Unexpected end tags<br />
| Unexpected end tags (in HTML, an unexpected <code>&lt;/br></code> or <code>&lt;/p></code> can cause the start tag to be implied before it).<br />
| Unexpected end tags are well-formedness errors.<br />
|<br />
| Do not add end tags unless there is an explicit and properly nested open tag before it.<br />
|-<br />
! End tag with attributes<br />
| ?<br />
| An end tag with attributes is not allowed.<br />
|<br />
| Do not use end tags with attributes.<br />
|-<br />
! Raw text elements<br />
|<br />
|<br />
|<br />
|-<br />
! RCDATA elements<br />
|<br />
|<br />
|<br />
|-<br />
! Foreign elements<br />
|<br />
|<br />
|<br />
|-<br />
! Normal elements<br />
|<br />
|<br />
|<br />
|-<br />
! Optional tags<br />
|<br />
For [[#HTML_Elements_with_Optional_Tags|some elements]], the start and/or end tags are optional and are implied by certain specified conditions. For example, the end tag for the <code>p</code> element is implied by a subsequent <code>p</code> element.<br />
<br />
Omitting the end tag for other elements is a parse error and various error recovery procedures are applied appropriately.<br />
| End tags must be explicitly included for all elements, except empty elements using the ''EmptyElemTag'' syntax.<br />
| <br />
| Always use end tags (or self-closing tags for void elements).<br />
|-<br />
! Comment syntax<br />
| Comments must start with the four character sequence "<code>&lt;!--</code>" and must be ended by the three character sequence "<code>--></code>" (bogus comments such as those beginning with "<?" are deprecated). The content of comments must not start with a single U+003E GREATER-THAN SIGN ('>') character, nor start with a U+002D HYPHEN-MINUS (-) character followed by a U+003E GREATER-THAN SIGN ('>') character, nor contain two consecutive U+002D HYPHEN-MINUS (-) characters, nor end with a U+002D HYPHEN-MINUS (-) character. Violating these constraints is a parse error and various error recovery procedures are applied appropriately.<br />
| The content of comments must not contain two consecutive U+002D HYPHEN-MINUS (-) characters, nor end with a hyphen. Violating this is a well-formedness error.<br />
| <br />
| Only use comments of the "<code>&lt;!--...--></code>" variety. Do not use two consecutive U+002D HYPHEN-MINUS (-) characters in comment content or end with such a hyphen (especially for the sake of XML). '''Do not begin comments with a single U+003E GREATER-THAN SIGN ('>') character, nor with a U+002D HYPHEN-MINUS (-) character followed by a U+003E GREATER-THAN SIGN ('>') character.'''<br />
|-<br />
!Processing Instructions<br />
| HTML does not allow processing instructions and deprecates the bogus comments which appear in their form, whether in the form <code>&lt;?foo ...&gt;</code> (without a closing '?') or <code>&lt;?foo ...?&gt;</code>.<br />
| XHTML allows the use of XML processing instructions which are only closed by "?>".<br />
| <br />
| '''Avoid ">" inside processing instructions (as these will close the "instruction" (comment) prematurely) (or one must strip out processing instructions entirely). Processing instructions might need to be avoided entirely in case HTML may in future disallow them completely.'''<br />
|-<br />
!CDATA sections<br />
| <code>&lt;![CDATA[...]]&gt;</code> is a a bogus comment. The sequence of characters &quot;<code>]]&gt;</code>&quot; in content when it does not mark the end of a <code>CDATA</code> section is just regular character data.<br />
| <code>&lt;![CDATA[...]]&gt;</code> is a <code>CDATA</code> section. The sequence of characters &quot;<code>]]&gt;</code>&quot; in content when it does not mark the end of a <code>CDATA</code> section is a well-formedness error.<br />
|<br />
| Ensure sequence &quot;<code>]]&gt;</code>&quot; in content is escaped (not necessary to escape in attribute values). '''Do not use CDATA sections.'''<br />
|-<br />
! Unescaped Special Characters <br />
|<br />
Unescaped ampersands (U+0026 AMPERSAND - <code>&amp;</code>, instead of <code>&amp;amp;</code>) are permitted within the content of ''normal elements'', ''RCDATA elements'', ''foreign elements'' and ''attribute values'' where they are not considered to be ''ambiguous ampersands'', and within ''Raw text elements''.<br />
<br />
Unescaped less than signs (U+003C LESS-THAN SIGN - <code>&lt;</code>, instead of <code>&amp;lt;</code>) are permitted in ''Raw text elements'', ''RCDATA elements'' and ''attribute values'', excluding the ''unquoted attribute value syntax''.<br />
| Unescaped ampersands and less-than signs may not appear within ''CharData'' or ''AttValue'' (basically, the normal text content of elements and attribute values.) Violation of this constraint is a well-formedness error.<br />
| <br />
| Always escape ampersands and less-than signs in text content and attribute values. See CDATA for need to escape sequence "<code>]]&gt;</code>" in text content.<br />
|-<br />
!Character References<br />
|<br />
|<br />
|<br />
|-<br />
!Entity References<br />
| In HTML, all entity references are predefined and do not require a DTD.<br />
| There is no formal DTD for XHTML5, but one could provide an exteranl DTD (if not an internal subset?) for use with one's entity-checking (or validating) parser, but be aware that browsers do not universally use external entity-checking (or validating) parsers and may not read the external DTD. (Some still have bugs in that they mistakenly create a well-formedness error out of such missing entities instead of showing them as missing, making them clickable, or using a entity-checking or validating parser.)<br />
|<br />
| Do not use entity references in XHTML (except for the 5 predefined entities: <code>&amp;amp;</code>, <code>&amp;lt;</code>, <code>&amp;gt;</code>, <code>&amp;quot;</code> and <code>&amp;apos;)</code>; use the equivalent Unicode or numeric character reference sequence instead.<br />
|-<br />
! Character data<br />
| <br />
| <br />
| The valid set of unicode characters in XML 1.0 is limited beyond that in HTML (we need to specify this here).<br />
| <br />
|}<br />
<br />
====Element-specific parsing====<br />
* In HTML, the <code>script</code> and <code>style</code> elements are parsed as <code>CDATA</code> elements. (Note: the definition of <code>CDATA</code> differs from that in XML). In XML, they're parsed as normal elements (which means that things that look like comments are treated as <em>real</em> comments, and things that look like start tags actually are start tags).<br />
* In HTML, the <code>title</code> and <code>textarea</code> elements are parsed as <code>RCDATA</code> elements. (Note: The definition of <code>RCDATA</code> differs from that in SGML and there is no <code>RCDATA</code> in XML).<br />
* In HTML, if scripting is enabled, the <code>noscript</code> element is parsed as an <code>CDATA</code> element. If scripting is disabled, it's parsed as a normal element. In XHTML, the element is always parsed as a normal element, and can't really be used to stop content from being present when script is disabled.<br />
* In HTML, the <code>iframe</code>, <code>noembed</code> and <code>noframes</code> elements are parsed as <code>CDATA</code> elements. In XHTML, they are parsed as normal elements, and therefore do not stop content from being used.<br />
* In HTML, tags for certain elements, which appear out of context, are ignored. This includes <code>caption</code>, <code>col</code>, <code>colgroup</code>, <code>frame</code>, <code>frameset</code>, <code>head</code>, <code>option</code>, <code>optgroup</code>, <code>tbody</code>, <code>td</code>, <code>tfoot</code>, <code>th</code>, <code>thead</code>, <code>tr</code>.<br />
* In XHTML, <code>table</code> elements may contain child <code>tr</code> elements. In the HTML serialisation, due to backwards compatibility constraints, this is not possible (though it may be done through DOM manipulation).<br />
* The <code>plaintext</code> element has a special parsing requirement in HTML. (It is, however, forbidden.)<br />
* In HTML, a line feed that immediately follows a <code>pre</code>, <code>listing</code> or <code>textarea</code> start tag is ignored.<br />
* <em>Many other special handling of edge cases and error conditions, not all of which are listed here, occur in HTML.</em> (such as?)<br />
* The following are void elements in HTML (see void elements in table): In head (<code>base</code>, <code>link</code>, <code>meta</code>), in body (<code>area</code>,<code>br</code>, <code>col</code>, <code>embed</code>, <code>hr</code>, <code>img</code>, <code>input</code>, <code>param</code>)<br />
<br />
==== HTML Elements with Optional Tags ====<br />
<br />
{| class="wikitable" border="1"<br />
|-<br />
! Element<br />
! Start Tag<br />
! End Tag<br />
|-<br />
!html<br />
|optional<br />
|optional<br />
|-<br />
!head<br />
|optional<br />
|optional<br />
|-<br />
!body<br />
|optional<br />
|optional<br />
|-<br />
!li<br />
|required<br />
|optional<br />
|-<br />
!dt<br />
|required<br />
|optional<br />
|-<br />
!dt<br />
|required<br />
|optional<br />
|-<br />
!p<br />
|required<br />
|optional<br />
|-<br />
!colgroup<br />
|optional<br />
|optional<br />
|-<br />
!thead<br />
|required<br />
|optional<br />
|-<br />
!tbody<br />
|optional<br />
|optional<br />
|-<br />
!tfoot<br />
|required<br />
|optional<br />
|-<br />
!tr<br />
|required<br />
|optional<br />
|-<br />
!th<br />
|required<br />
|optional<br />
|-<br />
!td<br />
|required<br />
|optional<br />
|-<br />
!rt<br />
|required<br />
|optional<br />
|-<br />
!rp<br />
|required<br />
|optional<br />
|-<br />
!optgroup<br />
|required<br />
|optional<br />
|-<br />
!option<br />
|required<br />
|optional<br />
|}<br />
<br />
=== Scripts ===<br />
<br />
* <code>document.write()</code> and <code>document.writeln()</code> cannot be used in XHTML, they can in HTML. <br />
* In XHTML, the use of the <code>innerHTML</code> property requires that the string be a well-formed fragment of XML. <br />
* DOM APIs are case sensitive in XHTML and some are case insensitive in HTML. (This does not apply to elements which are not in the HTML namespace)<br />
** Element.tagName and Node.nodeName return the value in uppercase in HTML but lower-case in XHTML (Node.localName is consistent now, as of HTML5).<br />
** Document.createElement() is case insensitive (the canonical form is lowercase).<br />
** Element.setAttributeNode() will change the attribute name to lowercase.<br />
** Element.setAttribute() is case insensitive (the canonical form is lowercase).<br />
** Document.getElementsByTagName() and Element.getElementsByTagName() are case insensitive.<br />
** Document.renameNode(). If the new namespace is the HTML namespace, then the new qualified name will be lowercased before the rename takes place.<br />
* In HTML, Document.createElement() will create an element in the HTML namespace. In XML (including XHTML), the namespace is defined by both DOM2 and DOM3 to be null.<br />
** In XHTML, browsers lack interoperability in this area. In Firefox and Safari, the namespace is dependent upon the MIME type. In Opera, it's dependent upon the root element.<br />
* XPath expressions targeted at pre-HTML5 browsers need to use the XHTML namespace for XHTML and null for HTML. (HTML5 browsers would use the XHTML namespace even in HTML.)<br />
<br />
=== Stylesheets ===<br />
<br />
* Selectors, as used in CSS, match case sensitively in XHTML, but case insensitively in HTML.<br />
* CSS requires special handling of the body element in HTML for painting backgrounds on the canvas, which do not apply to XHTML.<br />
* For polyglot documents, use lower-case element selectors and style the html and body elements appropriately (?).<br />
<br />
== Differences Between HTML4 and HTML5 ==<br />
<br />
See [http://dev.w3.org/html5/html4-differences/ HTML5 differences from HTML4].<br />
<br />
== Differences Between DOM Level 2.0, 3.0 and the HTML 5 DOM APIs ==<br />
<br />
'''This section might belong on a separate page.'''<br />
<br />
* TODO (need to talk about the changes to the DOM API that HTML5 is making, compared with DOM2 and DOM3)<br />
<br />
== Translations ==<br />
<br />
* [http://meiert.com/de/publications/translations/whatwg.org/html-vs-xhtml/ German translation: "HTML 5 und XHTML 5 im Vergleich (WHATWG)"]<br />
* [http://dancewithnet.com/2007/10/28/differences-between-html-and-xhtml/ Chinese translation: "HTML和XHTML的不同"]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=User:TheresaOConnor&diff=6576User:TheresaOConnor2011-06-22T18:16:28Z<p>TheresaOConnor: removed bio-blurb.</p>
<hr />
<div>In addition to keeping an eye on wiki spam, I occasionally [[Special:Contributions/EdwardOConnor|contribute to this wiki]].<br />
<br />
You might also be interested in [http://www.w3.org/html/wg/wiki/Special:Contributions/Eoconnor my contributions to the HTML WG wiki].<br />
<br />
----<br />
{{cc-public-domain-release}}</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Dialogs&diff=6522Dialogs2011-06-15T23:43:45Z<p>TheresaOConnor: +lightboxes</p>
<hr />
<div>= Problem statement =<br />
<br />
There's no markup for dialog boxes, tool palettes, hovering tooltips, the contents of popup widgets, and the like.<br />
<br />
== Real world examples today ==<br />
<br />
=== Dialogs ===<br />
<br />
=== Tooltips ===<br />
<br />
* The tooltips in the table of [http://bioinfo-prod.mpl.ird.fr/xantho/x.org/gui/seqterm.php] are interesting because they are currently &lt;div>s and force the parent to be a TD rather than a TH since TH is inline only, even though the visible content is really just phrasing content.<br />
<br />
=== Lightboxes ===<br />
<br />
[[Category:Proposals]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Presentations&diff=6406Presentations2011-05-04T19:03:48Z<p>TheresaOConnor: /* Speakers */ removed self</p>
<hr />
<div>These are the known presentations related to the WHATWG and/or HTML5.<br />
<br />
=== 2005 ===<br />
* [http://hixie.ch/advocacy/whatwg-presentation/ Proposing extensions to HTML4 and the DOM] by [[User:Hixie|Ian Hickson]] (Presented 2005-05)<br />
* [http://wearehugh.com/public/2005/12/whitelights/ White Lights Lead To Red Lights] by [[User:MarkPilgrim|Mark Pilgrim]] (Presented 2005-12-07 at Mozilla)<br />
=== 2007 ===<br />
* [http://lachy.id.au/dev/presentation/future-of-html/ The Future of HTML] by [[User:Lachlan_Hunt|Lachlan Hunt]] (Presented 2007-01-25)<br />
* [http://simonwillison.net/2007/talks/oxford-html5/ What the heck is HTML 5?] by [[User:SimonW|Simon Willison]] (Presented 2007-04-11)<br />
* [http://lists.w3.org/Archives/Public/www-archive/2007Apr/att-0036/html5.xml Evolving the Web: HTML5] by [[User:Annevk|Anne van Kesteren]] (Presented 2007-04-17 at QUT)<br />
* [http://lists.w3.org/Archives/Public/www-archive/2007May/att-0063/html5-short.xml Evolving the Web: HTML5 (XTech 2007 edition)] by [[User:Annevk|Anne van Kesteren]] (Presented 2007-05-17 at XTech 2007)<br />
* [http://2007.xtech.org/public/asset/attachment/83 Implementing an HTML5 conformance checker using XML tools] by Henri Sivonen (Presented 2007-05-18 at XTech 2007)<br />
* [http://blog.whatwg.org/html5-geekmeet How HTML5 can be used today] by [[User:zcorpan|Simon Pieters]] (Presented 2007-05-23)<br />
* [http://lists.w3.org/Archives/Public/www-archive/2007May/att-0087/html5.htm HTML5: Incremental Improvements to the Web] by [[User:Annevk|Anne van Kesteren]] (Presented 2007-05-31 at reboot 9.0)<br />
* [http://edward.oconnor.cx/2007/BarCamp-San-Diego/ What to expect from HTML5] by [[User:EdwardOConnor|Edward O'Connor]] (Presented 2007-06-03 at BarCamp San Diego)<br />
* [http://lachy.id.au/dev/presentation/developing-with-html5/Developing%20with%20HTML5.ppt Developing with HTML5] by [[User:Lachlan_Hunt|Lachlan Hunt]] (Presented 2007-08-03)<br />
* [http://james.html5.org/presentations/barcamb.pdf HTML 5: The Next Generation of Markup on The Web] by: [[User:jgraham|James Graham]] (Presented 2007-08-24 at BarCamp Cambridge)<br />
=== 2008 ===<br />
* [http://edward.oconnor.cx/2008/04/sdwebstandards/HTML5 Practical HTML5] by [[User:EdwardOConnor|Edward O'Connor]] (Presented 2008-04 at San Diego Web Standards Group)<br />
* [http://annevankesteren.nl/2008/xtech-html5 HTML5] by [[User:Annevk|Anne van Kesteren]] (Presented 2008-05-08 at XTech 2008 and a slightly modified version on 2008-06-27 at reboot10)<br />
* [http://annevankesteren.nl/2008/fronteers-html5-video HTML5] by [[User:Annevk|Anne van Kesteren]] (Presented 2008-09-11 at Fronteers 2008)<br />
* [http://www.whatwg.org/demos/2008-sept/ HTML5: Features you want desperately but still can't use] by [[User:Hixie|Ian Hickson]] (Presented 2008-09-22 at Google)<br />
* [http://lensco.be/2008/11/30/html-5-in-a-big-nutshell-a-presentation-at-barcamp-gent HTML 5 in a big nutshell] by [[User:lensco|Lennart Schoors]] (Presented at Barcamp Ghent 2008-11-29)<br />
=== 2009 ===<br />
* [http://annevankesteren.nl/2009/over-webstandaarden-enzo Over Webstandaarden Enzo] (Dutch) by [[User:Annevk|Anne van Kesteren]] (Presented 2009-01-19 at Fronteers meeting)<br />
* [http://simon.html5.org/presentations/090423-mdh/ HTML5 och Webbläsare] (Swedish) by [[User:zcorpan|Simon Pieters]] (Presented 2009-04-23 at Mälardalens Högskola)<br />
* [http://edward.oconnor.cx/2009/BarCamp-San-Diego-5/ Extensibility, HTML, and the Web ecosystem] by [[User:EdwardOConnor|Edward O'Connor]] (Presented 2009-05-31 at BarCamp San Diego)<br />
* [http://www.ustream.tv/recorded/1642113 HTML5 overview] (English) by [[User:arlen|Arlen Walker]] (Presented 2009-06-11 at Web414) (Presentation begins at 9:30 of the video, alternate camera angle found at [http://www.web414.com/node/877 Web414 video])<br />
* [http://edward.oconnor.cx/2009/preDevCamp/ HTML5 & webOS] by [[User:EdwardOConnor|Edward O'Connor]] (Presented 2009-08-08 at preDevCamp San Diego)<br />
* [http://edward.oconnor.cx/2009/08/ignite HTML 5 for the Working Web: features you can use today] by [[User:EdwardOConnor|Edward O'Connor]] (Presented 2009-08-12 at [http://ignitesandiego.org/ Ignite San Diego])<br />
=== 2010 ===<br />
* [http://simon.html5.org/presentations/html5-video/ HTML5 video] (Swedish) by [[User:zcorpan|Simon Pieters]] (Presented 2010-02-16 at Linköpings Universitet)<br />
* [http://tantek.com/presentations/2010/06/html5-vtm/ HTML5] by [[User:Tantek|Tantek Çelik]] (Presented 2010-06-28 at Voices That Matter: Web Design 2010 in San Francisco)<br />
* [http://tantek.com/presentations/2010/06/html5/hands-on/ Hands-On HTML5] by [[User:Tantek|Tantek Çelik]] (Workshop presentation 2010-06-30 at Voices That Matter: Web Design 2010 in San Francisco)<br />
* [http://tantek.com/presentations/2010/07/cascadesf/ HTML5 + CSS3 + Microformats] by [[User:Tantek|Tantek Çelik]] (Presented 2010-07-01 at CascadeSF in San Francisco)<br />
* [http://tantek.com/presentations/2010/07/html5-connect/ HTML5] by [[User:Tantek|Tantek Çelik]] (Presented 2010-07-13 at ConnectTech in San Francisco)<br />
* [http://tantek.com/presentations/2010/07/html5-owc/ HTML5, microformats, S5 And You] by [[User:Tantek|Tantek Çelik]] (Presented 2010-07-17 at Open Web Camp II at Stanford)<br />
* [http://www.html-lernen.de/blog/category/webdesign/html-webdesign/html5/ HTML5 differences to HTML 4 and HTML5 related article] (German) by [[User:kh4711|Karl Hoegerl]] (Presented 2010-07-24 at Blog [http://www.html-lernen.de/blog/ html-lernen.de])<br />
<br />
== Speakers ==<br />
<br />
The following past and present contributors to HTML5 efforts and members of the WHATWG community are available for speaking engagements:<br />
<br />
* [[User:Tantek|Tantek Çelik]] <tantek at tantek.com>, based in California, USA<br />
* [[User:jgraham|James Graham]] <jgraham at opera.com>, based in Sweden<br />
* [[User:Lachlan_Hunt|Lachlan Hunt]] <lachlan.hunt at lachy.id.au>, based in Norway<br />
* [http://codinginparadise.org/about Brad Neuberg] <bradneuberg at gmail.com>, based in California, USA<br />
* [[User:zcorpan|Simon Pieters]] <simonp at opera.com>, based in Sweden<br />
* [[User:MarkPilgrim|Mark Pilgrim]] <mark at diveintomark.org>, based in North Carolina, USA<br />
* [[User:lensco|Lennart Schoors]] <lensco at gmail.com>, based in Belgium<br />
* [[User:Annevk|Anne van Kesteren]] <annevankesteren at gmail.com>, based in the Netherlands<br />
* [[User:arlen|Arlen Walker]] <arlen.walker at gmail.com>, based in Wisconsin, USA</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Talk:Main_Page&diff=6367Talk:Main Page2011-04-13T17:57:22Z<p>TheresaOConnor: Reverted edits by Wdyniki (talk) to last revision by Hixie</p>
<hr />
<div>== WHATWG Specifications ==<br />
<br />
* I think this whole section should go. Problems should be categorised by what they apply to, not classified by which specification should solve them. The solution, not the problem, is bound to a particular specification. --[[User:Michel Fortin|Michel Fortin]]<br />
** I agree that problems shouldn't be categorised by the specification, but I don't agree this section should go. I think it's ok to provide some documentation about the actual specifications, including the actual features included within. It should be used to provide summaries and examples of actual features. Only when a proposal has been accepted and included in the spec, should it be included in this section. --[[User:Lachlan Hunt|Lachlan Hunt]] 22:03, 15 Nov 2006 (PST)<br />
*** That's fine with me. --[[User:Michel Fortin|Michel Fortin]]<br />
**** That sounds fine, Lachlan. --[[User:Matthew Raymond|Matthew Raymond]]<br />
<br />
== Terms, Acronyms and Abbreviations ==<br />
<br />
* I think this section too should go too. --[[User:Michel Fortin|Michel Fortin]]<br />
** I agree. If needed, we could create a glossary, but I don't think abbreviations and other terms should be on separate pages. --[[User:Lachlan Hunt|Lachlan Hunt]] 22:05, 15 Nov 2006 (PST)<br />
*** I agree that this can be condensed to a single page, but I think we still need a page for this. A glossary is a good idea. --[[User:Matthew Raymond|Matthew Raymond]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Cite_element&diff=6322Cite element2011-03-18T15:20:33Z<p>TheresaOConnor: Reverted edits by Alicethomas (talk) to last revision by Annevk</p>
<hr />
<div>Research, data, use cases, issues, and enhancements related to the HTML5 <code>cite</code> element.<br />
<br />
== Speaker ==<br />
The cite element has been used (and recommended to be used) to refer to speakers in a conversation, or individuals when quoting them, thus HTML5 should explicitly permit and encourage this use.<br />
<br />
This section serves to document both uses in the wild, and long-standing recommendations/documentations thereof.<br />
<br />
=== Examples in the Wild ===<br />
* 2003-08-23: <cite>[http://diveintomark.org/archives/2003/08/29/semantics Won’t somebody please think of the gerbils?]</cite> by <cite>[http://diveintomark.org/ Mark Pilgrim]</cite>: <blockquote>I mark up names of people I link to (like in the list above) with the CITE tag, and I have a script that runs every night that aggregates those tags and creates posts by citation.</blockquote><br />
* [http://www.geekinthepark.co.uk/transcripts/2008/brian-cant.html transcript of the presentation “What Brian Cant Never Taught You About Metadata”, by Drew McLellen] (this is from a template I provided the transcription company; all others are similar structure. brucel)<br />
* Many blog posts on [http://adactio.com/journal/ adactio.com], e.g <cite>[http://adactio.com/journal/1398/ Blame]</cite> from 2008-01-09: <blockquote>...something Bruce Sterling said at last year’s South by Southwest...</blockquote><br />
* Default WordPress theme ("Kubrick") uses cite for name of commenters. That's approx 46 bajillion instances.<br />
* The transcripts for comics (#34 and onward) at [http://www.cssquirrel.com/ CSSquirrel]. The links to the transcripts are hidden from sighted users, one example is: [http://www.cssquirrel.com/comicscripts/script35.htm Transcript #35 2009-09-08]<br />
* 2005-05-16: Speakers in this <cite>[http://erikanderica.org/erik/work/lazarus/playtext/ Towneley Lazarus play]</cite> edition are identified using CITE.<br />
* [http://igofigure.com/page/testimonials/ Testimonials on the website for Go Figure Inc.] use cite to denote the names/locations of the people who provided the testimonial<br />
* [http://guineylaw.com/testimonials/ The Law Offices of Thomas G Guiney] uses cite to mark up the names of speakers for testimonial quotes.<br />
* [http://2009.dconstruct.org/podcast/makeitso/ Podcast transcript] from dConstruct 2009 ([http://2009.dconstruct.org/podcast/ more])<br />
* Various "conversations"/transcripts at [http://peterjanes.ca/blog/ Petroglyphs], e.g. [http://peterjanes.ca/blog/2008/04/04/bang/ dialogue], and [http://peterjanes.ca/blog/wp-content/themes/petroglyphs/style.css CSS classes defined for terms, titles, etc.] ([http://peterjanes.ca/2005/citations/# XMDP])<br />
* any article at Einfach für Alle (major german accessibility resource), e.g. [http://www.einfach-fuer-alle.de/artikel/ueberschriften-strukturen-in-html/] (see sidebar, 4th box from top labelled "mehr dazu:") uses cite to mark up authors' names<br />
* any articles on [http://www.la-grange.net/ La Grange] with a quote from a book or poem, and in addition any kind of references to a blog post. cite class="auteur" and cite class="title" for author and title respectively.<br />
<br />
=== Documentation ===<br />
* 1998-04-24 <cite>[http://www.w3.org/TR/1998/REC-html40-19980424/struct/text.html#h-9.2.1 HTML 4.0 REC]</cite> <blockquote>Contains a citation or a reference to other sources.</blockquote><blockquote><p>As &lt;CITE&gt;Harry S. Truman&lt;/CITE&gt; said,<br>&lt;Q lang="en-us"&gt;The buck stops here.&lt;/Q&gt;</p><p>More information can be found in &lt;CITE&gt;[ISO-0000]&lt;/CITE&gt;.</p></blockquote><br />
* 1999-12-24 <cite>[http://www.w3.org/TR/html401/struct/text.html#edef-CITE HTML 4.01 REC]</cite> (same definition and examples as quoted above).<br />
* 2005-03-13: <cite>[http://tantek.com/presentations/2005/03/elementsofxhtml/ The Elements of Meaningful XHTML]</cite> presentation (to an overflowing room at SXSW Interactive 2005 in Austin, TX) specifically, [http://tantek.com/presentations/2005/03/elementsofxhtml/#slide10 slide10 and following] document blog quote markup, and [http://tantek.com/presentations/2005/03/elementsofxhtml/#slide19 slide 19 and following] document conversation markup.<br />
** 2005-09-29: update: <cite>[http://tantek.com/presentations/2005/09/elements-of-xhtml/ The Elements of Meaningful XHTML]</cite> presentation (to a packed room at Web Essential 05 in Sydney Australia) again [http://tantek.com/presentations/2005/09/elements-of-xhtml/#slide10 slide 10 and following], and [http://tantek.com/presentations/2005/09/elements-of-xhtml/#slide34 slide 34 and following] respectively.<br />
* ...<br />
<br />
=== Counter-arguments ===<br />
==== original intent of cite element ====<br />
* 2007-06-07 <cite>Dan Connolly</cite>, Editor of HTML 2.0, said in IRC that <blockquote cite="http://krijnhoetmer.nl/irc-logs/html-wg/20070607#l-797">&lt;cite&gt; was supposed to capture the chicago-manual-of-style idiom for titles of works. I have lost track of what it means these days.</blockquote><br />
** This may have been the original intent (original theoretical purity), however, based on the example in the HTML4 spec(s) and adoption by the web community over the past 10+ years (see above examples in the wild), it makes more sense to define the &lt;cite&gt; element per actual usage (preferring authors), rather than original intent (theoretical purity), per the [http://www.w3.org/TR/html-design-principles/#priority-of-constituencies priority of constituencies HTML design principle]. - [[User:Tantek|Tantek]] 22:18, 13 August 2010 (UTC)<br />
<br />
* "DanC said allowing <nowiki><cite></nowiki> for speakers was a bug in HTML 4 that happened because he was asleep at the wheel."<br />
** Regardless of what DanC as a <em>specifier</em> may have intended, the authors have widely adopted the usage of cite for speakers, and thus since authors are considered over specifiers (per above-referenced design principle), we should prefer author usage over original specifier intent.<br />
<br />
==== speakers are not italicized typically ====<br />
* "Since speakers aren't italicized typically, using <nowiki><cite></nowiki> for them doesn't really make sense. "<br />
** This sounds like either an argument from presentation, which seems backwards, as semantics should be determined first, and then authors can style semantics however they wish, or it's an argument from default presentation implementation, in which case once again per [http://www.w3.org/TR/html-design-principles/#priority-of-constituencies priority of constituencies HTML design principle], since authors are considered over implementers, we should respect author usage of cite for speakers over any particular implementer opinion of what cite should do or look like.<br />
***The Design Principles don't support the notion of determining semantics first. In fact, the Design Principles were carefully drafted not to treat semantics as having any value on their own right but only as a means to a useful end (such as Device Independence or Accessibility). As for considering authors over implementors or specifiers, we should consider whether an author who hasn't been exposed to advocacy that tries to rationalize the feature set of HTML4 would find a need to mark up speakers in a way that italicizes by default and required additional work to un-italicize as opposed to not marking up speakers at all all using the <code>b</code> element to bold speakers where required by a newspaper-like house style. That is, what authors do after having been exposed to advocacy is bad evidence for determining the needs the authors would have on their own initiative.<br />
<br />
=== Opinions ===<br />
Opinions on whether HTML5 should explicitly permit and encourage use of the cite element to refer to speakers in a conversation, or individuals when quoting them:<br />
<div class="discussion"><br />
* +1 [http://www.zeldman.com/superfriends/ HTML5 Super Friends], specifically [http://www.zeldman.com/superfriends/guide/#cite cite element: review of data].<br />
* +1 [[Tantek]]<br />
* +1 [[User:Adactio|Jeremy Keith]]<br />
* +1 Bruce Lawson, article agreeing with Tantek, July 06 [http://www.brucelawson.co.uk/2006/breaking-news-w3c-specs-are-not-word-of-god/ Breaking news: w3c specs are not the Word of God]<br />
* +1 [http://wiki.whatwg.org/wiki/User:Cssquirrel Kyle Weems]<br />
* +1 [http://wiki.whatwg.org/wiki/User:Erikvorhes Erik Vorhes]<br />
* +1 [http://wiki.whatwg.org/wiki/Themattharris Matt Harris]<br />
* -0 [[User:EdwardOConnor|EdwardOConnor]]<br />
* +1 [[User:Xanthir|Tab Atkins Jr.]]<br />
* +1 [http://www.rachaelmoore.name/web-design/html-web-design/citing-in-html5-cite-attribute-and-cite-tag/ Citing in HTML5] by Rachael L. Moore<br />
* +1 [[User:Tcaspers|Tomas Caspers]]<br />
* +1 [[NickFitz]]<br />
* +1 [[User:Asbjornu|Asbjørn Ulsberg]]<br />
* +1 [http://statichtml.com/2009/html5-cite-element.html HTML5's &lt;cite&gt; element: what is it good for?] by Steve Webster<br />
* +1 [[User:Urlyman|Jonathan Schofield]]<br />
* +1 [[User:Dalizard|Dimitar Haralanov]]<br />
* +1 [[User:Pigsonthewing|Andy Mabbett]]<br />
* +1 [[Tim White]]<br />
* +1 [[Travis Swicegood]]<br />
* -1 [[User:Hsivonen|Henri Sivonen]]<br />
* +1 [[User:KevinMarks|Kevin Marks]]<br />
* +1 [[User:Stefsull|Stephanie (Sullivan) Rewis]]<br />
* +1 Kroc Camen—See my [http://camendesign.com/abbr_redux article on abbr/dfn/cite usage]—Cite is “for giving credit”<br />
</div><br />
<br />
=== articles on speaker cite ===<br />
Articles supporting the use of the cite element for marking up speakers:<br />
* <cite>[http://24ways.org/2009/incite-a-riot 24 Ways: Incite A Riot]</cite>, 2009-12-11, by Jeremy Keith<br />
<br />
=== speaker cite FAQ ===<br />
Frequently Asked Questions about using the cite element for marking up speakers.<br />
<br />
==== how do you connect the speaker cite to what was said ====<br />
'''Question:''' How could we connect the speaker, CITE to what was said, Q, without nesting? Perhaps using FOR, as in form labels:<pre><nowiki><cite for="good">Andy Mabbett</cite> said <q id="good">This is good</q>.</nowiki></pre>On the other hand, if we reverse that we could have a many-to-one relationship:<pre><nowiki><cite id="andy">Andy Mabbett</cite> said <q for="andy">This is good</q></nowiki> and later said <q for="andy">This is better</q>.</nowiki></pre><br />
<br />
'''Answer:''' The existing [http://www.w3.org/TR/html401/struct/text.html#adef-cite-Q 'cite' attribute] on the &lt;q&gt; and &lt;blockquote&gt; elements can be used for this, in HTML4 and later:<br />
<br />
<pre style="background:#efe"><nowiki><br />
<cite id="andy">Andy Mabbett</cite> said <br />
<q cite="#andy">This is good</q><br />
and later said <br />
<q cite="#andy">This is better</q>.<br />
</nowiki></pre><br />
<br />
=== speaker cite related ===<br />
* [[FAQ#The_.3Ccite.3E_element_should_allow_names_of_people_to_be_marked_up|WHATWG FAQ re cite and names of people]]<br />
<br />
== references ==<br />
* [http://www.w3.org/TR/html401/struct/text.html#edef-CITE HTML 4.01 definition of the CITE element]<br />
<br />
[[Category:Proposals]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Rationale&diff=6321Rationale2011-03-18T15:19:07Z<p>TheresaOConnor: Reverted edits by Alicethomas (talk) to last revision by EdwardOConnor</p>
<hr />
<div><!--<br />
notes of things to add<br />
1. explanation of <device> <br />
2. Why the WHATWG version is unversioned and called HTML5...<br />
3. explain difference between W3C and WHATWG version?<br />
4. Explain all the different uses of the header, hgroup, .... elements<br />
6. http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-April/025920.html - add this somewhere.<br />
7. add header/h1 and such explanation<br />
8. Better explain Defer/async<br />
9. skip links??<br />
10. http://www.mail-archive.com/whatwg@lists.whatwg.org/msg23220.html<br />
--><br />
This document serves a rationale document for various parts of the HTML5 specification. Over time this page will be a complete rationale document.<br />
<br />
== General Rationale ==<br />
<br />
=== One Vendor, One Veto === <br />
<br />
Part of the the goal of the WHATWG is to document how web browsers actually handle HTML. As such browser vendors already have veto power - by not following the standard. The W3C and WHATWG do not have any enforcement power and can only write what browsers are willing to implement. Not removing features from the HTML standard that at least one browser vendor has stated they are unwilling to implement causes the HTML spec to not accurately document reality.<ref>http://lists.w3.org/Archives/Public/public-html/2009Jul/0257.html -- Re: Codecs for &lt;video&gt; and &lt;audio&gt;</a></ref><ref>http://lists.w3.org/Archives/Public/www-archive/2009Jul/0075.html --Formal Objection to One vendor, One Veto</ref>. The veto isn't a<br />
power that we grant browsers, it's a right that they earn on their own by virtue of having users. The minimum market share for a veto is somewhere around 1%.<ref>http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-June/026897.html</ref><br />
<br />
=== Using elements where scripts "work" ===<br />
In addition, arguments were made that JavaScript-based implementations of details suffer from problems and limitations. Scripting behavior may be inconsistent across browsers, or even unavailable in some contexts. Accessibility is "bolted on", allowing more opportunity for author error, even when using libraries. The data model is not exposed in a consistent way in the markup. And matching native appearance and behavior across a range of platforms may be impractical.<ref>http://lists.w3.org/Archives/Public/public-html/2010Jun/att-0659/issue-93-decision.html</ref><br />
<br />
=== It isn't just about web browsers ===<br />
Web browsers are not the only programs that use HTML. Sometimes elements and features are needed even when browsers won't use them in any meaningful way. Document authoring tools, validators, search engines, screen readers, outliners, researchers, etc. all need and can use more information than a browser can. Furthermore if you provide more information than is currently used by browsers it opens up room for innovation.<br />
<br />
=== Experimenting with features ===<br />
New unknown and untested features are unlikely to get accepted into the WHATWG spec. Browsers and browser extensions (like Google Gears) are expected to first establish use cases and implementation possibilities before the spec is changed. <ref>http://www.mail-archive.com/whatwg@lists.whatwg.org/msg22577.html</ref><br />
<br />
=== Versioning the spec ===<br />
Most authors don't care about whether or not an implementation supports an entire, full specification; they just want to know "Can I use this feature in this browser?" So saying that all major implementations support much of CSS 2 to a high degree of correctness is useless for knowing if, say, the author can use display: run-in. In other words, the feature tables are what web authors would actually use in real life.<ref>http://www.mail-archive.com/whatwg@lists.whatwg.org/msg23306.html</ref><br />
<br />
<!--=== HTML5 the spec vs HTML5 the buzzword ===<br />
http://www.mail-archive.com/whatwg@lists.whatwg.org/msg23299.html<br />
--><br />
<br />
=== Modifying existing semantics ===<br />
Some elements have different semantics than what HTML4 users would expect. Semantic markup isn't very useful if most pages use elements in a manner that conflicts with the defined semantics. For example, if a search engine treated dd as enclosing a term being defined, for the purposes of searching for definitions (or excluding defining occurrences from results), it would not find many definitions, and it would misclassify things.<ref>http://lists.whatwg.org/htdig.cgi/help-whatwg.org/2010-October/000668.html</ref><br />
<br />
== Specific Elements ==<br />
<br />
=== Doctype ===<br />
Since HTML5 has moved to an unversioned model the doctype does not a have version number. It is necessary for legacy browsers that will switch to standards mode only when a doctype is present.<br />
<br />
=== Plaintext ===<br />
The &lt;plaintext&gt; element is a obsolete precursor to the &lt;pre&gt; element. <ref>http://www.w3.org/MarkUp/draft-ietf-iiir-html-01.txt</ref> It is now in the HTML5 spec as a method of stopping all further html token parsing. It lacks an end tag and just emits the rest of the page as plain text. It throws a parse error upon reaching the end of the document as it is not considered a valid element (and it is missing an end-tag).<br />
<br />
=== Image ===<br />
<br />
&lt;image&gt; element is treated as an alternate (but invalid) name for &lt;img&gt;. This is because some sites (around 0.2%<ref>Email from Ian Hickson; comment in spec source</ref>) make this mistake. It is already treated as an image by most major browsers.<br />
<br />
=== Meter and Progress (are not the same thing) ===<br />
<br />
&lt;meter&gt; is not just a special case of &lt;progress&gt;. The meter element represents a scalar measurement within a known range, such as storage quota usage, a relative popularity rating or relevance indicator. The control allows for the indication of high and low ranges, or minimum, maximum and optimal levels.<br />
<br />
The progress element, on the other hand, represents the completion progress of a task. This could be a real time indicator for background processing task (e.g. using Web Workers or a file upload). Progress elmements can also be in the indeterminate state, indicating that something is in progress, but it's completion progress is unknown.<ref>http://html5doctor.com/your-questions-answered-11/</ref><br />
<br />
The default rendering for a meter element could look something like the following:<br />
<br />
<img src="http://developer.apple.com/mac/library/documentation/userexperience/conceptual/applehiguidelines/art/ct_leveldiscrete.gif" alt="example of proper rendering for the meter element"><br />
<br />
Whereas, the default rendering for the progress element could look like this:<br />
<br />
<img src="http://developer.apple.com/mac/library/documentation/userexperience/conceptual/applehiguidelines/art/ct_determprogsizes.jpg"><br />
<br />
Alternatively, an indeterminate progress bar could also be styled as a throbber, which indicates progress without any indication of the remaining progress:<br />
<br />
<img src="http://developer.apple.com/mac/library/documentation/userexperience/conceptual/applehiguidelines/art/ct_asynchprogindsizes.jpg" alt="picture of the default apple throbber"><br />
<br />
See [http://www.mail-archive.com/whatwg@lists.whatwg.org/msg01308.html Re: &lt;progress&gt; draft] for details.<br />
<br />
=== B, I, EM, STRONG, and MARK ===<br />
&lt;em&gt; is meant to indicate that some text is emphasized. &lt;strong&gt; is meant to confer importance upon text. &lt;b&gt; is meant for text that is stylistically offset from the rest of the text. Finally &lt;i&gt; is used to indicate that some text is meant to be read in an alternate mood.<br />
<br />
<!-- should I use a different sentence for each element or the same one? --><br />
For example <br />
Cats are &lt;em&gt;cute&lt;/em&gt; animals.<br />
could mean that cats are specifically cute.<br />
Cats are &lt;strong&gt;cute&lt;/strong&gt; animals.<br />
could mean that the word cute is in some way important<br />
Cats are &lt;b&gt;cute&lt;/b&gt; animals.<br />
could mean that the word cute is a new word (perhaps in a language lesson) but is not important<br />
Cats are &lt;i&gt;cute&lt;/i&gt; animals.<br />
could mean that the word cute is meant to be read in a different tone (sarcastically for example)<br />
Cats are &lt;mark&gt;cute&lt;/mark&gt; animals.<br />
means that the sentence is to be read normally but the word "cute" should be highlighted or marked in some way. This could be used for search terms on the page or alterations to an original text.<br />
<br />
=== IMG tag & alt text ===<br />
On certain types of pages adding alt text is impossible (like sites that the user could upload images but does not supply a description). Because of this the alt attribute is optional <ref>http://www.paciellogroup.com/resources/articles/altinhtml5.html</ref><ref>http://juicystudio.com/article/requiring-alt-attribute-html5.php</ref><ref>http://lists.w3.org/Archives/Public/public-html/2007Jun/0393.html</ref><br />
A longdesc attribute is not needed <ref>http://juicystudio.com/article/html5-image-element-no-alt.php</ref><br />
<br />
=== textarea ===<br />
<br />
The text area defaults to soft wrapping of the text area. The attribute @wrap can have one of the following values: soft, hard, or off.<ref>http://www.whatwg.org/specs/web-apps/current-work/#the-textarea-element-0</ref>. "off" is considered a non-conforming value because it appears to have no purpose other than a visual presentational effect. <ref>http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-August/022022.html</ref><ref>http://www.mail-archive.com/whatwg@lists.whatwg.org/msg22660.html</ref><br />
<br />
=== hgroup and other heading elements ===<br />
The point of &lt;hgroup&gt; is to hide the subtitle from the outlining algorithm.<br />
<br />
<!--<br />
=== br and linebreaks ===<br />
--><br />
=== details element === <br />
The <details> element is needed to provide an accessible way of reflecting a<br />
common application widget in HTML-based applications without requiring authors<br />
to use extensive scripting, ARIA, and platform-specific CSS to get the same<br />
effect.<ref>http://www.w3.org/Bugs/Public/show_bug.cgi?id=8379#c13</ref><ref>http://www.w3.org/html/wg/wiki/ChangeProposals/removedetails</ref><br />
<br />
== HTML parsing ==<br />
<br />
=== script element ===<br />
<br />
Why the [http://www.whatwg.org/specs/web-apps/current-work/multipage/scripting-1.html#restrictions-for-contents-of-script-elements restrictions for contents of script elements]? Why the [http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html#script-data-double-escaped-dash-dash-state complicated parsing rules for script elements]?<br />
<br />
See http://lists.w3.org/Archives/Public/public-html-comments/2010Mar/0017.html<br />
<br />
==== @DEFER and @ASYNC ====<br />
ASYNC tells the browsers to run the script with its following content at the SAME time(namely, asynchronously).<br />
DEFER tells the browsers to run the script LATER, and to run the following content first(the browsers will run the script until the page is ready).<ref>http://www.mail-archive.com/whatwg@lists.whatwg.org/msg22436.html</ref><br />
<br />
=== quirks mode ===<br />
<br />
The HTML parser has [http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html#parsing-main-inbody the following] behavior difference in quirks mode:<br />
<br />
<blockquote><dl><dt>A start tag whose tag name is "table"<br />
<dd>If the Document is not set to quirks mode, and the stack of open elements has a p element in scope, then act as if an end tag with the tag name "p" had been seen.</dl></blockquote><br />
<br />
Why? See http://hsivonen.iki.fi/last-html-quirk/<br />
<br />
=== ignored white space before head ===<br />
<br />
White space before the <code>&lt;head></code> tag is ignored. The main reason is that, given the markup<br />
<br />
<pre><br />
<!DOCTYPE html><br />
<html><br />
<head><br />
<title>Sample page</title><br />
...,<br />
</pre><br />
<br />
some people expect<br />
<br />
<pre><br />
document.documentElement.firstChild<br />
</pre><br />
<br />
to return the <code>head</code> element.<ref><cite>[http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2008-March/014148.html &#91;whatwg&#93; several messages about the tree construction stage of HTML parsing]</cite></ref><br />
<br />
<!-- needs to be confirmed --><br />
<!--<br />
=== Why all input elements are candidates for Constraint validation ===<br />
Some elements have the API but are barred because it makes it <br />
easier to loop through form.elements and do the validation stuff without <br />
checking if the validation stuff is available on the element. (Same reason <br />
<textarea> has .type.)<br />
<ref>http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-July/027195.html</ref><br />
--><br />
<br />
== Failed proposals ==<br />
=== An "advert" tag for advertisements ===<br />
There is no advert tag because if users had an easy method of plainly disabling all ads from downloading or appearing content authors would cease to use the tag.<ref>http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2008-February/013939.html</ref><br />
<br />
=== sandbox attribute on the html element ===<br />
HTML is the wrong level for disabling scripts or other features. This is the kind of thing we should do at the HTTP layer.<ref>http://www.w3.org/Bugs/Public/show_bug.cgi?id=8849</ref><ref>https://wiki.mozilla.org/Security/CSP</ref><br />
<br />
=== feature queries ===<br />
Various proposals have come up with the idea of being able to determine of a certain feature is available.<ref>http://lists.w3.org/Archives/Public/www-style/2009Dec/0130.html</ref> These fail for a variety of reasons:<br />
Part of the problem is that browser vendors will be economical with the truth. Marketing people always have an over-optimistic view of the compliance of their product, and will always give themselves the benefit of the doubt in borderline cases. Also, changing the compliance statement, to remove false claims that are exposed, is likely to a very low priority for the developers.<ref>http://lists.w3.org/Archives/Public/www-style/2010Jul/0097.html</ref><br />
With regard to CSS feature compliance: Remember that CSS<br />
provides hints and implementations don't have to accept those hints, and<br />
hardware may sometimes prevent their being implemented.<ref>http://lists.w3.org/Archives/Public/www-style/2003Nov/0000.html</ref> <br />
Some other reasons can be found in the footnotes.<ref>http://lists.w3.org/Archives/Public/www-style/2003Oct/0074.html</ref><ref>http://lists.w3.org/Archives/Public/www-style/2004Mar/0282.html</ref><br />
<br />
=== custom HTML elements ===<br />
Custom elements make it impossible for search engines, developers, and browsers to understand the semantics of a page.<ref>http://html5doctor.com/your-questions-13/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+html5doctor+%28HTML5doctor%29</ref><br />
<br />
<!--<br />
=== secure key-value data stores ===<br />
[http://www.nczonline.net/blog/securestore-proposal/ A proposal for secure key-value stores for localstorage]<ref>http://www.mail-archive.com/whatwg@lists.whatwg.org/msg20754.html</ref><br />
--><br />
<br />
== Other Pages ==<br />
<br />
* [[Why no namespaces]]<br />
* [[Why no script implements]]<br />
* [[Why not reuse legend|Why not reuse legend or another ''mini-header'' element.]]<br />
* [http://www.w3.org/html/wg/wiki/ChangeProposals/KeepNewElements Rationale for a variety of elements]<br />
* [[XHTML2 versus HTML5]]<br />
* [http://lists.w3.org/Archives/Public/public-html/2008Aug/0300.html &lt;meta http-equiv=content-language> ]<br />
* [http://www.w3.org/html/wg/wiki/RationalesGathering earlier page started with the same purpose.]<br />
* [http://www.w3.org/html/wg/wiki/ChangeProposals/KeepNewElements rationale for some new HTML5 elements]<br />
* [http://wiki.whatwg.org/wiki/FAQ WHATWG FAQ]<br />
<br />
== References ==<br />
<references/></div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Rationale&diff=5701Rationale2010-12-30T15:41:20Z<p>TheresaOConnor: Reverted edits by Hearme (talk) to last revision by AMWJ</p>
<hr />
<div><!--<br />
notes of things to add<br />
1. explanation of <device> <br />
2. Why the WHATWG version is unversioned and called HTML5...<br />
3. explain difference between W3C and WHATWG version?<br />
4. Explain all the different uses of the header, hgroup, .... elements<br />
6. http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-April/025920.html - add this somewhere.<br />
7. add header/h1 and such explanation<br />
8. Better explain Defer/async<br />
9. skip links??<br />
10. http://www.mail-archive.com/whatwg@lists.whatwg.org/msg23220.html<br />
--><br />
This document serves a rationale document for various parts of the HTML5 specification. Over time this page will be a complete rationale document.<br />
<br />
== General Rationale ==<br />
<br />
=== One Vendor, One Veto === <br />
<br />
Part of the the goal of the WHATWG is to document how web browsers actually handle HTML. As such browser vendors already have veto power - by not following the standard. The W3C and WHATWG do not have any enforcement power and can only write what browsers are willing to implement. Not removing features from the HTML standard that at least one browser vendor has stated they are unwilling to implement causes the HTML spec to not accurately document reality.<ref>http://lists.w3.org/Archives/Public/public-html/2009Jul/0257.html -- Re: Codecs for &lt;video&gt; and &lt;audio&gt;</a></ref><ref>http://lists.w3.org/Archives/Public/www-archive/2009Jul/0075.html --Formal Objection to One vendor, One Veto</ref>. The veto isn't a<br />
power that we grant browsers, it's a right that they earn on their own by virtue of having users. The minimum market share for a veto is somewhere around 1%.<ref>http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-June/026897.html</ref><br />
<br />
=== Using elements where scripts "work" ===<br />
In addition, arguments were made that JavaScript-based implementations of details suffer from problems and limitations. Scripting behavior may be inconsistent across browsers, or even unavailable in some contexts. Accessibility is "bolted on", allowing more opportunity for author error, even when using libraries. The data model is not exposed in a consistent way in the markup. And matching native appearance and behavior across a range of platforms may be impractical.<ref>http://lists.w3.org/Archives/Public/public-html/2010Jun/att-0659/issue-93-decision.html</ref><br />
<br />
=== It isn't just about web browsers ===<br />
Web browsers are not the only programs that use HTML. Sometimes elements and features are needed even when browsers won't use them in any meaningful way. Document authoring tools, validators, search engines, screen readers, outliners, researchers, etc. all need and can use more information than a browser can. Furthermore if you provide more information than is currently used by browsers it opens up room for innovation.<br />
<br />
=== Experimenting with features ===<br />
New unknown and untested features are unlikely to get accepted into the WHATWG spec. Browsers and browser extensions (like Google Gears) are expected to first establish use cases and implementation possibilities before the spec is changed. <ref>http://www.mail-archive.com/whatwg@lists.whatwg.org/msg22577.html</ref><br />
<br />
=== Versioning the spec ===<br />
Most authors don't care about whether or not an implementation supports an entire, full specification; they just want to know "Can I use this feature in this browser?" So saying that all major implementations support much of CSS 2 to a high degree of correctness is useless for knowing if, say, the author can use display: run-in. In other words, the feature tables are what web authors would actually use in real life.<ref>http://www.mail-archive.com/whatwg@lists.whatwg.org/msg23306.html</ref><br />
<br />
<!--=== HTML5 the spec vs HTML5 the buzzword ===<br />
http://www.mail-archive.com/whatwg@lists.whatwg.org/msg23299.html<br />
--><br />
<br />
=== Modifying existing semantics ===<br />
Some elements have different semantics than what HTML4 users would expect. Semantic markup isn't very useful if most pages use elements in a manner that conflicts with the defined semantics. For example, if a search engine treated dd as enclosing a term being defined, for the purposes of searching for definitions (or excluding defining occurrences from results), it would not find many definitions, and it would misclassify things.<ref>http://lists.whatwg.org/htdig.cgi/help-whatwg.org/2010-October/000668.html</ref><br />
<br />
== Specific Elements ==<br />
<br />
=== Doctype ===<br />
Since HTML5 has moved to an unversioned model the doctype does not a have version number. It is necessary for legacy browsers that will switch to standards mode only when a doctype is present.<br />
<br />
=== Plaintext ===<br />
The &lt;plaintext&gt; element is a obsolete precursor to the &lt;pre&gt; element. <ref>http://www.w3.org/MarkUp/draft-ietf-iiir-html-01.txt</ref> It is now in the HTML5 spec as a method of stopping all further html token parsing. It lacks an end tag and just emits the rest of the page as plain text. It throws a parse error upon reaching the end of the document as it is not considered a valid element (and it is missing an end-tag).<br />
<br />
=== Image ===<br />
<br />
&lt;image&gt; element is treated as an alternate (but invalid) name for &lt;img&gt;. This is because some sites (around 0.2%<ref>Email from Ian Hickson; comment in spec source</ref>) make this mistake. It is already treated as an image by most major browsers.<br />
<br />
=== Meter and Progress (are not the same thing) ===<br />
<br />
&lt;meter&gt; is not just a special case of &lt;progress&gt;. The meter element represents a scalar measurement within a known range, such as storage quota usage, a relative popularity rating or relevance indicator. The control allows for the indication of high and low ranges, or minimum, maximum and optimal levels.<br />
<br />
The progress element, on the other hand, represents the completion progress of a task. This could be a real time indicator for background processing task (e.g. using Web Workers or a file upload). Progress elmements can also be in the indeterminate state, indicating that something is in progress, but it's completion progress is unknown.<ref>http://html5doctor.com/your-questions-answered-11/</ref><br />
<br />
The default rendering for a meter element could look something like the following:<br />
<br />
<img src="http://developer.apple.com/mac/library/documentation/userexperience/conceptual/applehiguidelines/art/ct_leveldiscrete.gif" alt="example of proper rendering for the meter element"><br />
<br />
Whereas, the default rendering for the progress element could look like this:<br />
<br />
<img src="http://developer.apple.com/mac/library/documentation/userexperience/conceptual/applehiguidelines/art/ct_determprogsizes.jpg"><br />
<br />
Alternatively, an indeterminate progress bar could also be styled as a throbber, which indicates progress without any indication of the remaining progress:<br />
<br />
<img src="http://developer.apple.com/mac/library/documentation/userexperience/conceptual/applehiguidelines/art/ct_asynchprogindsizes.jpg" alt="picture of the default apple throbber"><br />
<br />
See [http://www.mail-archive.com/whatwg@lists.whatwg.org/msg01308.html Re: &lt;progress&gt; draft] for details.<br />
<br />
=== B, I, EM, STRONG, and MARK ===<br />
&lt;em&gt; is meant to indicate that some text is emphasized. &lt;strong&gt; is meant to confer importance upon text. &lt;b&gt; is meant for text that is stylistically offset from the rest of the text. Finally &lt;i&gt; is used to indicate that some text is meant to be read in an alternate mood.<br />
<br />
<!-- should I use a different sentence for each element or the same one? --><br />
For example <br />
Cats are &lt;em&gt;cute&lt;/em&gt; animals.<br />
could mean that cats are specifically cute.<br />
Cats are &lt;strong&gt;cute&lt;/strong&gt; animals.<br />
could mean that the word cute is in some way important<br />
Cats are &lt;b&gt;cute&lt;/b&gt; animals.<br />
could mean that the word cute is a new word (perhaps in a language lesson) but is not important<br />
Cats are &lt;i&gt;cute&lt;/i&gt; animals.<br />
could mean that the word cute is meant to be read in a different tone (sarcastically for example)<br />
Cats are &lt;mark&gt;cute&lt;/mark&gt; animals.<br />
means that the sentence is to be read normally but the word "cute" should be highlighted or marked in some way. This could be used for search terms on the page or alterations to an original text.<br />
<br />
=== IMG tag & alt text ===<br />
On certain types of pages adding alt text is impossible (like sites that the user could upload images but does not supply a description). Because of this the alt attribute is optional <ref>http://www.paciellogroup.com/resources/articles/altinhtml5.html</ref><ref>http://juicystudio.com/article/requiring-alt-attribute-html5.php</ref><ref>http://lists.w3.org/Archives/Public/public-html/2007Jun/0393.html</ref><br />
A longdesc attribute is not needed <ref>http://juicystudio.com/article/html5-image-element-no-alt.php</ref><br />
<br />
=== textarea ===<br />
<br />
The text area defaults to soft wrapping of the text area. The attribute @wrap can have one of the following values: soft, hard, or off.<ref>http://www.whatwg.org/specs/web-apps/current-work/#the-textarea-element-0</ref>. "off" is considered a non-conforming value because it appears to have no purpose other than a visual presentational effect. <ref>http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-August/022022.html</ref><ref>http://www.mail-archive.com/whatwg@lists.whatwg.org/msg22660.html</ref><br />
<br />
=== hgroup and other heading elements ===<br />
The point of &lt;hgroup&gt; is to hide the subtitle from the outlining algorithm.<br />
<br />
<!--<br />
=== br and linebreaks ===<br />
--><br />
=== details element === <br />
The <details> element is needed to provide an accessible way of reflecting a<br />
common application widget in HTML-based applications without requiring authors<br />
to use extensive scripting, ARIA, and platform-specific CSS to get the same<br />
effect.<ref>http://www.w3.org/Bugs/Public/show_bug.cgi?id=8379#c13</ref><ref>http://www.w3.org/html/wg/wiki/ChangeProposals/removedetails</ref><br />
<br />
== HTML parsing ==<br />
<br />
=== script element ===<br />
<br />
Why the [http://www.whatwg.org/specs/web-apps/current-work/multipage/scripting-1.html#restrictions-for-contents-of-script-elements restrictions for contents of script elements]? Why the [http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html#script-data-double-escaped-dash-dash-state complicated parsing rules for script elements]?<br />
<br />
See http://lists.w3.org/Archives/Public/public-html-comments/2010Mar/0017.html<br />
<br />
==== @DEFER and @ASYNC ====<br />
ASYNC tells the browsers to run the script with its following content at the SAME time(namely, asynchronously).<br />
DEFER tells the browsers to run the script LATER, and to run the following content first(the browsers will run the script until the page is ready).<ref>http://www.mail-archive.com/whatwg@lists.whatwg.org/msg22436.html</ref><br />
<br />
=== quirks mode ===<br />
<br />
The HTML parser has [http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html#parsing-main-inbody the following] behavior difference in quirks mode:<br />
<br />
<blockquote><dl><dt>A start tag whose tag name is "table"<br />
<dd>If the Document is not set to quirks mode, and the stack of open elements has a p element in scope, then act as if an end tag with the tag name "p" had been seen.</dl></blockquote><br />
<br />
Why? See http://hsivonen.iki.fi/last-html-quirk/<br />
<br />
=== ignored white space before head ===<br />
<br />
White space before the <code>&lt;head></code> tag is ignored. The main reason is that, given the markup<br />
<br />
<pre><br />
<!DOCTYPE html><br />
<html><br />
<head><br />
<title>Sample page</title><br />
...,<br />
</pre><br />
<br />
some people expect<br />
<br />
<pre><br />
document.documentElement.firstChild<br />
</pre><br />
<br />
to return the <code>head</code> element.<ref><cite>[http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2008-March/014148.html &#91;whatwg&#93; several messages about the tree construction stage of HTML parsing]</cite></ref><br />
<br />
<!-- needs to be confirmed --><br />
<!--<br />
=== Why all input elements are candidates for Constraint validation ===<br />
Some elements have the API but are barred because it makes it <br />
easier to loop through form.elements and do the validation stuff without <br />
checking if the validation stuff is available on the element. (Same reason <br />
<textarea> has .type.)<br />
<ref>http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-July/027195.html</ref><br />
--><br />
<br />
== Failed proposals ==<br />
=== An "advert" tag for advertisements ===<br />
There is no advert tag because if users had an easy method of plainly disabling all ads from downloading or appearing content authors would cease to use the tag.<ref>http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2008-February/013939.html</ref><br />
<br />
=== sandbox attribute on the html element ===<br />
HTML is the wrong level for disabling scripts or other features. This is the kind of thing we should do at the HTTP layer.<ref>http://www.w3.org/Bugs/Public/show_bug.cgi?id=8849</ref><ref>https://wiki.mozilla.org/Security/CSP</ref><br />
<br />
=== feature queries ===<br />
Various proposals have come up with the idea of being able to determine of a certain feature is available.<ref>http://lists.w3.org/Archives/Public/www-style/2009Dec/0130.html</ref> These fail for a variety of reasons:<br />
Part of the problem is that browser vendors will be economical with the truth. Marketing people always have an over-optimistic view of the compliance of their product, and will always give themselves the benefit of the doubt in borderline cases. Also, changing the compliance statement, to remove false claims that are exposed, is likely to a very low priority for the developers.<ref>http://lists.w3.org/Archives/Public/www-style/2010Jul/0097.html</ref><br />
With regard to CSS feature compliance: Remember that CSS<br />
provides hints and implementations don't have to accept those hints, and<br />
hardware may sometimes prevent their being implemented.<ref>http://lists.w3.org/Archives/Public/www-style/2003Nov/0000.html</ref> <br />
Some other reasons can be found in the footnotes.<ref>http://lists.w3.org/Archives/Public/www-style/2003Oct/0074.html</ref><ref>http://lists.w3.org/Archives/Public/www-style/2004Mar/0282.html</ref><br />
<br />
=== custom HTML elements ===<br />
Custom elements make it impossible for search engines, developers, and browsers to understand the semantics of a page.<ref>http://html5doctor.com/your-questions-13/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+html5doctor+%28HTML5doctor%29</ref><br />
<br />
<!--<br />
=== secure key-value data stores ===<br />
[http://www.nczonline.net/blog/securestore-proposal/ A proposal for secure key-value stores for localstorage]<ref>http://www.mail-archive.com/whatwg@lists.whatwg.org/msg20754.html</ref><br />
--><br />
<br />
== Other Pages ==<br />
<br />
* [[Why no namespaces]]<br />
* [[Why no script implements]]<br />
* [[Why not reuse legend|Why not reuse legend or another ''mini-header'' element.]]<br />
* [http://www.w3.org/html/wg/wiki/ChangeProposals/KeepNewElements Rationale for a variety of elements]<br />
* [[XHTML2 versus HTML5]]<br />
* [http://lists.w3.org/Archives/Public/public-html/2008Aug/0300.html &lt;meta http-equiv=content-language> ]<br />
* [http://www.w3.org/html/wg/wiki/RationalesGathering earlier page started with the same purpose.]<br />
* [http://www.w3.org/html/wg/wiki/ChangeProposals/KeepNewElements rationale for some new HTML5 elements]<br />
* [http://wiki.whatwg.org/wiki/FAQ WHATWG FAQ]<br />
<br />
== References ==<br />
<references/></div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=RelExtensions&diff=5606RelExtensions2010-12-04T19:30:33Z<p>TheresaOConnor: fix error made while removing rel=details</p>
<hr />
<div>This page lists the allowed extension values for the rel="" attribute in HTML5. You may add your own values to this list, which makes them legal HTML5 rel values. We ask that you try to avoid redundancy; if someone has already defined a value that does roughly what you want, please reuse it. Note that rel tokens are ASCII-lowercase before comparison against canonical value, so the canonical values should be listed without uppercase ASCII letters.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Keyword<br />
! Effect on <code>link</code><br />
! Effect on <code>a</code>, <code>area</code><br />
! Brief description<br />
! Link to more details<br />
! Synonyms<br />
! Status<br />
|-<br />
| accessibility<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains accessibility information for the linking document.<br />
| [http://www.brucelawson.co.uk/2009/rel-accessibility/ Bruce Lawson]<br />
| <br />
| Proposal<br />
|-<br />
| acquaintance<br />
| hyperlink<br />
| hyperlink<br />
| the person represented by the current document considers the person represented by the referenced document to be an acquaintance<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| ajax<br />
| not allowed<br />
| hyperlink<br />
| The link is controlled through javascript, and will load the page linked to though an ajax interface. Without javascript, it should behave as a normal "a" tag, and content change is done server side.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| alternate<br />
|colspan=6| See HTML5<br />
|-<br />
| answer<br />
| hyperlink<br />
| hyperlink<br />
| A link to the answer to the question this section or document asks, e.g. in a FAQ or in a sample exam. Unlike ‘reply’ or ‘comment’ this resource necessarily solves the problem.<br />
| [[Talk:RelExtensions#Q_and_A|Q&A]]<br />
| (reply, comment)<br />
| Proposal<br />
|-<br />
| application-manifest<br />
| external resource<br />
| Not allowed<br />
| A manifest for this web application. The manifest contains metadata about the web application, such as its name, description, and permissions the application might require.<br />
|<br />
|<br />
| Proposal<br />
|-<br />
| archives<br />
|colspan=6| See HTML5<br />
|-<br />
| author<br />
|colspan=6| See HTML5<br />
|-<br />
| bookmark<br />
|colspan=6| See HTML5<br />
|-<br />
| canonical<br />
| hyperlink<br />
| not allowed<br />
| Robots (e.g., search engines) should treat the document containing the tag as a minor variation of the linked document, which may result in the removal of the former from a web index and in the consolidation of its quality signals in the latter.<br />
| [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-domain<br />
| external resource<br />
| not allowed<br />
| More than one domain may have largely similar or identical content but only one of the domains should be indexed for search engines. E.g., a company may have short and long domain names for the same content.<br />
For security against traffic theft, rev must be meaningless.<br />
| [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139066 Google's analogous service] and [[Talk:RelExtensions#On_canonical-domain.2C_canonical-wwwnone.2C_and_canonical-first|Talk for this page]]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-first<br />
| external resource<br />
| hyperlink<br />
| Where the canonical value should point to a group of pages, but the link can point to only one page, the group of pages can be clarified by choosing the first page in the group and assigning the URL for this rel link.<br />
For security against traffic theft, rev must be meaningless.<br /><br />
This is only shorthand for providing two link elements, one on the noncanonical page to a "canonical" page and the other on the canonical page to the "first" page of the group.<br />
Where the group of pages corresponds to a subdirectory and a canonical URL value can point to the subdirectory resulting in a user arriving at the subdirectory's index page which is part of the group, this shorthand is unnecessary and one rel="canonical" will suffice.<br />
| [[Talk:RelExtensions#On_canonical-domain.2C_canonical-wwwnone.2C_and_canonical-first|Talk for this page]]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-human<br />
| external resource<br />
| hyperlink<br />
| Pages about a person across many websites can be associated based on name, nationality, birthplace, dates of birth and death, when flourished, and other identifiers.<br />
Search engines could more consistently aggregate same-person pages with less confusion due to name similarity.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7681 W3C Bug 7681]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-organization<br />
| external resource<br />
| hyperlink<br />
| Pages about an organization across many websites can be associated based on name, headquarters site, and other identifiers.<br />
Search engines could more consistently aggregate same-organization pages with less confusion due to name similarity.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7682 W3C Bug 7682]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-wwwnone<br />
| external resource<br />
| hyperlink<br />
| Both bare and www-prefixed domain names usually direct to the same site. Especially when external links to a site vary in the form used, search engine indexing concentrated on only one domain form may raise its credibility. The rel value is the form preferred for indexing, e.g., href="http://example.net". Nothing to the right of the top-level domain is needed.<br />
For security against traffic theft, rev must be meaningless.<br />
| [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139066 Google's analogous service] and [[Talk:RelExtensions#On_canonical-domain.2C_canonical-wwwnone.2C_and_canonical-first|Talk for this page]]<br />
| <br />
| Proposal<br />
|-<br />
| chapter<br />
| hyperlink<br />
| hyperlink<br />
| Target document is a subdocument of the current document.<br />
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]<br />
| section, subsection, appendix<br />
| Proposal<br />
|-<br />
| child<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a child of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| co-resident<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person lives in the same residence as the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| co-worker<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a co-worker of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| colleague<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a colleague of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| contact<br />
| hyperlink<br />
| hyperlink<br />
| the person represented by the current document considers the person represented by the referenced document to be a contact<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| contributor<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) involved in the production of the content, but not his main author(s).<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| crush<br />
| hyperlink<br />
| hyperlink<br />
| this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| date<br />
| hyperlink<br />
| hyperlink<br />
| this person considers the referenced person to be a date (i.e. is dating the referenced person)<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| dns-prefetch<br />
| external resource<br />
| not allowed<br />
| Force the DNS lookup of specific hostnames.<br />
| [https://developer.mozilla.org/En/Controlling_DNS_prefetching Mozilla DNS Prefetching], <br />[http://dev.chromium.org/developers/design-documents/dns-prefetching Chromium DNS Prefetching]<br />
| <br />
| Proposal<br />
|-<br />
| edit<br />
| hyperlink<br />
| hyperlink<br />
| Target document is an editable version of the current document.<br />
| [http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-11.html#new-link-relation Atom Protocol]<br />
| <br />
| Proposal<br />
|-<br />
| edituri<br />
| hyperlink<br />
| not allowed<br />
| a link to an RSD file describing how to edit the given page.<br />
| [http://cyber.law.harvard.edu/blogs/gems/tech/rsd.htm rsd]<br />
| <br />
| Proposal<br />
|-<br />
| enclosure<br />
| hyperlink<br />
| hyperlink<br />
| the destination of the hyperlink is intended to be downloaded and cached.<br />
| [http://microformats.org/wiki/rel-enclosure rel-enclosure]<br />
| <br />
| Proposal<br />
|-<br />
| enlarged<br />
| not allowed<br />
| hyperlink<br />
| For anchors that have one child image element, indicates that the linked document is an image file which is the same as the child image element of the link except a larger size (dimensions).<br />
| [http://dvdgoss.wordpress.com/2010/04/26/the-case-for-relenlarge-in-html5/ David Goss]<br />
| <br />
| Proposal<br />
|-<br />
| external<br />
|colspan=6| See HTML5<br />
|-<br />
| extension<br />
| hyperlink<br />
| hyperlink<br />
| Browser extension<br />
| [http://mozillalabs.com/jetpack/2010/05/12/indexing-and-auto-detecting-browser-extensions-on-the-web/ Mozilla Labs]<br />
| <br />
| Proposal<br />
|-<br />
| first<br />
|colspan=6| See HTML5<br />
|-<br />
| friend<br />
| hyperlink<br />
| hyperlink<br />
| the person represented by the current document considers the person represented by the referenced document to be a friend<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| gallery<br />
| hyperlink<br />
| hyperlink<br />
| A ''graphic'' index that the current document or section is a part of or that illustrates the same topic.<br />
| <br />
| (index, list)<br />
| Proposal<br />
|-<br />
| glossary<br />
| hyperlink<br />
| hyperlink<br />
| Target document provides definitions for words in current document.<br />
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]<br />
| <br />
| Proposal<br />
|-<br />
| help<br />
|colspan=6| See HTML5<br />
|-<br />
| hub<br />
| hyperlink<br />
| not allowed<br />
| Indicates a URL which implements both sides of the PubSubHubbub protocol.<br />
| [http://code.google.com/p/pubsubhubbub/ PubSubHubbub]<br />
| <br />
| Proposal<br />
|-<br />
| i18nrules<br />
| hyperlink<br />
| not allowed<br />
| Target document provides ITS (Internationalization tag Set) rules for processing the current document.<br />
| [http://www.w3.org/TR/its/ ITS]<br />
| <br />
| Proposal<br />
|-<br />
| icon<br />
|colspan=6| See HTML5<br />
|-<br />
| index<br />
|colspan=6| See HTML5<br />
|-<br />
| jump<br />
| not allowed<br />
| hyperlink<br />
| Indicates a same page jump from the current fragment to another fragment. (E.g. sometimes online newspapers insert direct text saying "article continues below the image/advert" - they could instead use "jump" link. Ultimately, it indicates a page internal link.)<br />
| [[Talk:RelExtensions#On_footnote.2C_note.2C_and_jump|Talk]]<br />
| <br />
| Proposal<br />
|-<br />
| kin<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is part of the extended family of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| lang-alt-[ISO 639-1 code]<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains a version of the current document in an alternative language. "[ISO 639-1 code]" is replaced with the appropriate [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 language code]. The ISO 639-1 code is used when the browser (or other user agent) wants to display either the full name of the language or a flag, as a visual aid for the end user.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| lang-orig-[ISO 639-1 code]<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains a version of the current document in the language the document was originally written in. "[ISO 639-1 code]" is replaced with the appropriate [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 language code]. The ISO 639-1 code is used when the browser (or other user agent) wants to display either the full name of the language or a flag, as a visual aid for the end user.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| last<br />
|colspan=6| See HTML5<br />
|-<br />
| latest-version<br />
| hyperlink<br />
| hyperlink<br />
| The referenced document is the latest version of the current document.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.txt], [http://tools.ietf.org/search/rfc5829#section-3.2 RFC5829]<br />
| <br />
| Proposal<br />
|-<br />
| license<br />
|colspan=6| See HTML5<br />
|-<br />
| logout<br />
| external resource<br />
| not allowed<br />
| The linked document provides a resource for the UA to request when all currently open documents of the same "group" are closed (to facilitate logging out the current user).<br />
| [[LogoutRelExtension]]<br />
| <br />
| Proposal<br />
|-<br />
| <span id="longdesc">longdesc</span><br />
| hyperlink<br />
| hyperlink<br />
| Related to [http://www.w3.org/html/wg/tracker/issues/30 ISSUE-30]. <br/><abbr title="Assistive Technology">AT</abbr> should treat an element wrapped in a link with <code>rel="longdesc"</code> as equivalent to an element with <code>longdesc="URI"</code>. <br />
| (1) [http://lists.w3.org/Archives/Public/public-html/2007Jun/0738.html Eric Eggert's original proposal, 25th of June 2007], <br/>(2) [http://lists.w3.org/Archives/Public/public-html/2007Jun/0798.html Maciej's comment, 25th of June 2007], <br/>(3) [http://www.w3.org/Bugs/Public/show_bug.cgi?id=10434 Bug 10434, the HTMLwg, 2010]<br/>(4) [http://microformats.org/wiki/existing-rel-values#POSH_usage rel="longdesc" listed as POSH in Microformats.org]<br />
| <code>&lt;foo longdesc="URL"/></code> <br/>is synonymous to <br/><code>&lt;a rel="longdesc" href="URL">&lt;foo/>&lt;/a></code><br />
| Proposal<br />
|-<br />
| map<br />
| hyperlink<br />
| hyperlink<br />
| the referenced document represents a map of the location of the subject of the current document; parsers ''may'' use the URI or target page to determine coordinates.<br />
| to follow<br />
| <br />
| Proposal<br />
|-<br />
| me<br />
| hyperlink<br />
| hyperlink<br />
| the referenced document represents the same person as does the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| met<br />
| hyperlink<br />
| hyperlink<br />
| this person has met the referenced person<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| meta<br />
| external resource<br />
| hyperlink<br />
| publishing RDF/FOAF files<br />
| [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport RDF], [http://xmlns.com/foaf/spec/#sec-autodesc FOAF]<br />
| <br />
| Proposal<br />
|-<br />
| muse<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person inspires the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| neighbor<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person lives nearby the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| next<br />
|colspan=6| See HTML5<br />
|-<br />
| next-archive<br />
| hyperlink<br />
| hyperlink<br />
| A URI that refers to the immediately following archive document.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations], <br />[http://tools.ietf.org/html/rfc5005 RFC5005]<br />
| <br />
| Proposal<br />
|-<br />
| nofollow<br />
|colspan=6| See HTML5<br />
|-<br />
| noreferrer<br />
|colspan=6| See HTML5<br />
|-<br />
| noprefetch<br />
| external resource<br />
| hyperlink<br />
| Denies prefetching (not fetching) as a cost-control option for website owners, especially where pages are dynamic, leading to prefetching of wrong and useless pages.<br /><br />
The link provides a per-page denial whereas a and area provide a per-element denial.<br /><br />
For link, attributes rel="noprefetch" denies prefetching of the page at the href URL and rev="noprefetch" denies prefetching of the page bearing the link.<br /><br />
For a and area, rel is as above and rev is meaningless.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7918 W3C Bug 7918]<br />
| <br />
| Proposal<br />
|-<br />
| note<br />
| not allowed<br />
| hyperlink<br />
| An in-page or out-page jump to a footnote. This encompasses ''note'', ''footnote'', ''endnote'', and ''sidenote''.<br />
| [[Talk:RelExtensions#On_footnote.2C_note.2C_and_jump|Talk]]<br />
| <br />
| Proposal<br />
|-<br />
| openid.delegate<br />
| external resource<br />
| not allowed<br />
| OpenID 1.1 authentication delegation<br />
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID specification]<br />
| <br />
| Proposal<br />
|-<br />
| openid.server<br />
| external resource<br />
| not allowed<br />
| OpenID 1.1 authentication delegation<br />
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID specification]<br />
| <br />
| Proposal<br />
|-<br />
| openid2.local_id<br />
| external resource<br />
| not allowed<br />
| OpenID 2.0 authentication delegation<br />
| [http://openid.net/specs/openid-authentication-2_0.html#html_disco OpenID Auth 2.0 section 7.3.3]<br />
| <br />
| Proposal<br />
|-<br />
| openid2.provider<br />
| external resource<br />
| not allowed<br />
| OpenID 2.0 authentication endpoint<br />
| [http://openid.net/specs/openid-authentication-2_0.html#html_disco OpenID Auth 2.0 section 7.3.3]<br />
| <br />
| Proposal<br />
|-<br />
| parent<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a parent of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| payment<br />
| hyperlink<br />
| hyperlink<br />
| A URI where payment is accepted.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations]<br />
| <br />
| Proposal<br />
|-<br />
| pgpkey<br />
| hyperlink<br />
| not allowed<br />
| The linked document is the PGP public key file (which may contain multiple keys) of the author(s) of the page.<br />
| [http://purl.org/net/pgpkey/], [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html]<br />
| <br />
| Proposal<br />
|-<br />
| pingback<br />
|colspan=6| See HTML5<br />
|-<br />
| prefetch<br />
|colspan=6| See HTML5<br />
|-<br />
| presentation<br />
| external resource<br />
| hyperlink<br />
| Like ‘print’ this relation references a resource that represents the same content or topic, but in a ''very'' different manner. It is similar to media=projection, but is to be used where text is substituted by graphics, animations and sounds, which goes beyond mere style switching.<br />
This relation is also appropriate for links from thumbnail to full resolution images.<br />
| <br />
| slides, slideshow<br />
| Proposal<br />
|-<br />
| prev<br />
|colspan=6| See HTML5<br />
|-<br />
| prev-archive<br />
| hyperlink<br />
| hyperlink<br />
| A URI that refers to the immediately preceding archive document.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations], <br />[http://tools.ietf.org/html/rfc5005 RFC5005]<br />
| <br />
| Proposal<br />
|-<br />
| print<br />
| external resource<br />
| hyperlink<br />
| The referenced document is recommended for printing, even though the referent document is capable of being printed and both documents are of the same type, medium, and language. A typical case is where content spread over multiple pages is also available on a single page that is more convenient to print.<br />
This is semantically more specific than "canonical" and "alternate". Where type, medium, and/or language differ, consider "alternate"; where any of them differ but the purpose is printing, consider applying both values.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7645 W3C Bug 7645]<br />
| <br />
| Proposal<br />
|-<br />
| profile<br />
| hyperlink<br />
| hyperlink<br />
| this referenced link is a metadata profile for the current document<br />
| [http://www.w3.org/TR/html401/struct/global.html#profiles HTML Meta data profiles], <br />[http://www.w3.org/2003/g/glean-profile Example of profile in a-elements]<br />
| <br />
| Proposal<br />
|-<br />
| question<br />
| hyperlink<br />
| hyperlink<br />
| A link to the question this section or document answers, e.g. in a FAQ or in a sample exam. <br />
| [[Talk:RelExtensions#Q_and_A|Q&A]]<br />
| topic, subject, problem, (up)<br />
| Proposal<br />
|-<br />
| related<br />
| hyperlink<br />
| hyperlink<br />
| this referenced link identifies a resource related to the current document<br />
| [http://tools.ietf.org/html/rfc4287#section-4.2.7 Atom Syndication Format]<br />
| <br />
| Proposal<br />
|-<br />
| reply<br />
| hyperlink<br />
| hyperlink<br />
| A follow-up posting to this document or section or in the thread this document or section is an index of.<br />
| [[Talk:RelExtensions#Threading|Thread]]<br />
| posting, comment<br />
| Proposal<br />
|-<br />
| resource-package<br />
| external resource<br />
| not allowed<br />
| The linked document is a zipped resource package<br />
| [http://limi.net/articles/resource-packages/ Resource Packages]<br />
| <br />
| Proposal<br />
|-<br />
| resources<br />
| external resource<br />
| not allowed<br />
| a higher level alternative to HTTP Content Negotiation for other resources linked from the document, in a yet to be specified format<br />
|<br />
| resource-description, content-negotiation<br />
| Proposal<br />
|-<br />
| reviewer<br />
| hyperlink<br />
| not allowed<br />
| The linked document is the page/email an agent (people or firm or...) responsible for reviewing the content.<br />
| [http://wiki.csswg.org/test/css2.1/format#reviewer]<br />
| <br />
| Proposal<br />
|-<br />
| script<br />
| not allowed<br />
| not allowed<br />
| Was proposed to replace &lt;script>. Use &lt;script> instead.<br />
| none<br />
| <br />
| Rejected<br />
|-<br />
| search<br />
|colspan=6| See HTML5<br />
|-<br />
| self<br />
| hyperlink<br />
| hyperlink<br />
| A URI that refers to a resource equivalent to the containing element.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations], <br />[http://tools.ietf.org/html/rfc4287 RFC4287]<br />
| <br />
| Proposal<br />
|-<br />
| service<br />
| external resource<br />
| not allowed<br />
| Points to a resource describing a service API<br />
| [[ServiceRelExtension]]<br />
| <br />
| Proposal<br />
|-<br />
| shortlink<br />
| hyperlink<br />
| hyperlink<br />
| Identifies a shorter form of the URL for the current document, provided by the document owner.<br />
| [http://code.google.com/p/shortlink/wiki/Specification shortlink Specification]<br />
| <br />
| Proposal<br />
|-<br />
| sibling<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a sibling of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| sidebar<br />
|colspan=6| See HTML5<br />
|-<br />
| spouse<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a spouse of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| statechart<br />
| external resource<br />
| not allowed<br />
| A reference to an SCXML document that controls the application-flow of the current HTML document<br />
| [http://www.w3.org/TR/scxml/ SCXML]<br />
|<br />
| Proposal<br />
|-<br />
| stylesheet<br />
|colspan=6| See HTML5<br />
|-<br />
| subresource<br />
| hyperlink<br />
| not allowed<br />
| The referenced document is a subresource of the current document.<br />
| <br />
|<br />
| Proposal<br />
|-<br />
| sweetheart<br />
| hyperlink<br />
| hyperlink<br />
| this person considers the referenced person to be their sweetheart<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| tag<br />
|colspan=6| See HTML5<br />
|-<br />
| technicalauthor<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) responsible for the technical construction of the page (i.e. the HTML/CSS/PHP code), not for the content.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| thread<br />
| hyperlink<br />
| hyperlink<br />
| A hierarchic list of topic(s) and replies where this document or section belongs to either one.<br />
| [[Talk:RelExtensions#Threading|Thread]]<br />
| (index)<br />
| Proposal<br />
|-<br />
| timesheet<br />
| external resource<br />
| not allowed<br />
| SMIL Timesheet<br />
| [http://www.w3.org/TR/timesheets/#smilTimesheetsNS-Elements-Timesheet SMIL Timesheets 1.0]<br />
| <br />
| Proposal<br />
|-<br />
| topic<br />
| hyperlink<br />
| hyperlink<br />
| The initial posting this document or section is a reply to or index of.<br />
| [[Talk:RelExtensions#Threading|Thread]]<br />
| subject, (top)<br />
| Proposal<br />
|-<br />
| translatedfrom<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email that has been translation source for the current document. It also indicates that the current document is a translation and not an original work.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| translator<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) responsible for the translation of the page. It also indicates that the current page is a translation of an other document, which should be linked through a rel="translatedfrom".<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| up<br />
|colspan=6| See HTML5<br />
|-<br />
| us<br />
| hyperlink<br />
| hyperlink<br />
| The referenced document represents the same organisation as does the current document [cf rel-me]<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| webmaster<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) available for requests about the content of the page.<br />
| <br />
| maintainer<br />
| Proposal<br />
|-<br />
| widget<br />
| hyperlink<br />
| hyperlink<br />
| Points to a widget.<br />
| [http://dev.w3.org/2006/waf/widgets/Overview.html#autodiscovery Widgets 1.0 Editor's draft]<br />
| <br />
| Proposal<br />
|-<br />
| wlwmanifest<br />
| hyperlink<br />
| not allowed<br />
| A link to a manifest for Windows Live Writer.<br />
| [http://msdn.microsoft.com/en-us/library/bb463263.aspx msdn]<br />
| <br />
| Proposal<br />
|}<br />
<!-- Science: proof, lemma, theorem --><br />
<br />
The "Effect on link" column must either say "not allowed" if the rel value is not allowed on &lt;link> elements, "hyperlink" if the rel value creates a hyperlink, or "external resource" if the rel value creates a link to an external resource.<br />
<br />
The "Effect on a and area" column must either say "not allowed" or "hyperlink".<br />
<br />
For the "Status" section to be changed to "Accepted", the proposed keyword must either have been through the [http://microformats.org/wiki/process Microformats process], and been approved by the Microformats community; or must be defined by a W3C specification in the Candidate Recommendation or Recommendation state. If it fails to go through this process, it is "Rejected".<br />
<br />
For more details, see [http://whatwg.org/specs/web-apps/current-work/#linkTypes the HTML5 specification]. See also [http://microformats.org/wiki/existing-rel-values the Microformats wiki page on this matter].</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=RelExtensions&diff=5605RelExtensions2010-12-04T19:29:21Z<p>TheresaOConnor: removed rel=details per investigation of the value. see http://krijnhoetmer.nl/irc-logs/microformats/20101204#l-17 for details.</p>
<hr />
<div>This page lists the allowed extension values for the rel="" attribute in HTML5. You may add your own values to this list, which makes them legal HTML5 rel values. We ask that you try to avoid redundancy; if someone has already defined a value that does roughly what you want, please reuse it. Note that rel tokens are ASCII-lowercase before comparison against canonical value, so the canonical values should be listed without uppercase ASCII letters.<br />
<br />
{| class="wikitable sortable"<br />
|-<br />
! Keyword<br />
! Effect on <code>link</code><br />
! Effect on <code>a</code>, <code>area</code><br />
! Brief description<br />
! Link to more details<br />
! Synonyms<br />
! Status<br />
|-<br />
| accessibility<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains accessibility information for the linking document.<br />
| [http://www.brucelawson.co.uk/2009/rel-accessibility/ Bruce Lawson]<br />
| <br />
| Proposal<br />
|-<br />
| acquaintance<br />
| hyperlink<br />
| hyperlink<br />
| the person represented by the current document considers the person represented by the referenced document to be an acquaintance<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| ajax<br />
| not allowed<br />
| hyperlink<br />
| The link is controlled through javascript, and will load the page linked to though an ajax interface. Without javascript, it should behave as a normal "a" tag, and content change is done server side.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| alternate<br />
|colspan=6| See HTML5<br />
|-<br />
| answer<br />
| hyperlink<br />
| hyperlink<br />
| A link to the answer to the question this section or document asks, e.g. in a FAQ or in a sample exam. Unlike ‘reply’ or ‘comment’ this resource necessarily solves the problem.<br />
| [[Talk:RelExtensions#Q_and_A|Q&A]]<br />
| (reply, comment)<br />
| Proposal<br />
|-<br />
| application-manifest<br />
| external resource<br />
| Not allowed<br />
| A manifest for this web application. The manifest contains metadata about the web application, such as its name, description, and permissions the application might require.<br />
|<br />
|<br />
| Proposal<br />
|-<br />
| archives<br />
|colspan=6| See HTML5<br />
|-<br />
| author<br />
|colspan=6| See HTML5<br />
|-<br />
| bookmark<br />
|colspan=6| See HTML5<br />
|-<br />
| canonical<br />
| hyperlink<br />
| not allowed<br />
| Robots (e.g., search engines) should treat the document containing the tag as a minor variation of the linked document, which may result in the removal of the former from a web index and in the consolidation of its quality signals in the latter.<br />
| [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-domain<br />
| external resource<br />
| not allowed<br />
| More than one domain may have largely similar or identical content but only one of the domains should be indexed for search engines. E.g., a company may have short and long domain names for the same content.<br />
For security against traffic theft, rev must be meaningless.<br />
| [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139066 Google's analogous service] and [[Talk:RelExtensions#On_canonical-domain.2C_canonical-wwwnone.2C_and_canonical-first|Talk for this page]]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-first<br />
| external resource<br />
| hyperlink<br />
| Where the canonical value should point to a group of pages, but the link can point to only one page, the group of pages can be clarified by choosing the first page in the group and assigning the URL for this rel link.<br />
For security against traffic theft, rev must be meaningless.<br /><br />
This is only shorthand for providing two link elements, one on the noncanonical page to a "canonical" page and the other on the canonical page to the "first" page of the group.<br />
Where the group of pages corresponds to a subdirectory and a canonical URL value can point to the subdirectory resulting in a user arriving at the subdirectory's index page which is part of the group, this shorthand is unnecessary and one rel="canonical" will suffice.<br />
| [[Talk:RelExtensions#On_canonical-domain.2C_canonical-wwwnone.2C_and_canonical-first|Talk for this page]]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-human<br />
| external resource<br />
| hyperlink<br />
| Pages about a person across many websites can be associated based on name, nationality, birthplace, dates of birth and death, when flourished, and other identifiers.<br />
Search engines could more consistently aggregate same-person pages with less confusion due to name similarity.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7681 W3C Bug 7681]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-organization<br />
| external resource<br />
| hyperlink<br />
| Pages about an organization across many websites can be associated based on name, headquarters site, and other identifiers.<br />
Search engines could more consistently aggregate same-organization pages with less confusion due to name similarity.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7682 W3C Bug 7682]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-wwwnone<br />
| external resource<br />
| hyperlink<br />
| Both bare and www-prefixed domain names usually direct to the same site. Especially when external links to a site vary in the form used, search engine indexing concentrated on only one domain form may raise its credibility. The rel value is the form preferred for indexing, e.g., href="http://example.net". Nothing to the right of the top-level domain is needed.<br />
For security against traffic theft, rev must be meaningless.<br />
| [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139066 Google's analogous service] and [[Talk:RelExtensions#On_canonical-domain.2C_canonical-wwwnone.2C_and_canonical-first|Talk for this page]]<br />
| <br />
| Proposal<br />
|-<br />
| chapter<br />
| hyperlink<br />
| hyperlink<br />
| Target document is a subdocument of the current document.<br />
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]<br />
| section, subsection, appendix<br />
| Proposal<br />
|-<br />
| child<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a child of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| co-resident<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person lives in the same residence as the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| co-worker<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a co-worker of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| colleague<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a colleague of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| contact<br />
| hyperlink<br />
| hyperlink<br />
| the person represented by the current document considers the person represented by the referenced document to be a contact<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| contributor<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) involved in the production of the content, but not his main author(s).<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| crush<br />
| hyperlink<br />
| hyperlink<br />
| this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| date<br />
| hyperlink<br />
| hyperlink<br />
| this person considers the referenced person to be a date (i.e. is dating the referenced person)<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Proposal<br />
|-<br />
| dns-prefetch<br />
| external resource<br />
| not allowed<br />
| Force the DNS lookup of specific hostnames.<br />
| [https://developer.mozilla.org/En/Controlling_DNS_prefetching Mozilla DNS Prefetching], <br />[http://dev.chromium.org/developers/design-documents/dns-prefetching Chromium DNS Prefetching]<br />
| <br />
| Proposal<br />
|-<br />
| edit<br />
| hyperlink<br />
| hyperlink<br />
| Target document is an editable version of the current document.<br />
| [http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-11.html#new-link-relation Atom Protocol]<br />
| <br />
| Proposal<br />
|-<br />
| edituri<br />
| hyperlink<br />
| not allowed<br />
| a link to an RSD file describing how to edit the given page.<br />
| [http://cyber.law.harvard.edu/blogs/gems/tech/rsd.htm rsd]<br />
| <br />
| Proposal<br />
|-<br />
| enclosure<br />
| hyperlink<br />
| hyperlink<br />
| the destination of the hyperlink is intended to be downloaded and cached.<br />
| [http://microformats.org/wiki/rel-enclosure rel-enclosure]<br />
| <br />
| Proposal<br />
|-<br />
| enlarged<br />
| not allowed<br />
| hyperlink<br />
| For anchors that have one child image element, indicates that the linked document is an image file which is the same as the child image element of the link except a larger size (dimensions).<br />
| [http://dvdgoss.wordpress.com/2010/04/26/the-case-for-relenlarge-in-html5/ David Goss]<br />
| <br />
| Proposal<br />
|-<br />
| external<br />
|colspan=6| See HTML5<br />
|-<br />
| extension<br />
| hyperlink<br />
| hyperlink<br />
| Browser extension<br />
| [http://mozillalabs.com/jetpack/2010/05/12/indexing-and-auto-detecting-browser-extensions-on-the-web/ Mozilla Labs]<br />
| <br />
| Proposal<br />
|-<br />
| first<br />
|colspan=6| See HTML5<br />
|-<br />
| friend<br />
| hyperlink<br />
| hyperlink<br />
| the person represented by the current document considers the person represented by the referenced document to be a friend<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| gallery<br />
| hyperlink<br />
| hyperlink<br />
| A ''graphic'' index that the current document or section is a part of or that illustrates the same topic.<br />
| <br />
| (index, list)<br />
| Proposal<br />
|-<br />
| glossary<br />
| hyperlink<br />
| hyperlink<br />
| Target document provides definitions for words in current document.<br />
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]<br />
| <br />
| Proposal<br />
|-<br />
| help<br />
|colspan=6| See HTML5<br />
|-<br />
| hub<br />
| hyperlink<br />
| not allowed<br />
| Indicates a URL which implements both sides of the PubSubHubbub protocol.<br />
| [http://code.google.com/p/pubsubhubbub/ PubSubHubbub]<br />
| <br />
| Proposal<br />
|-<br />
| i18nrules<br />
| hyperlink<br />
| not allowed<br />
| Target document provides ITS (Internationalization tag Set) rules for processing the current document.<br />
| [http://www.w3.org/TR/its/ ITS]<br />
| <br />
| Proposal<br />
|-<br />
| icon<br />
|colspan=6| See HTML5<br />
|-<br />
| index<br />
|colspan=6| See HTML5<br />
|-<br />
| jump<br />
| not allowed<br />
| hyperlink<br />
| Indicates a same page jump from the current fragment to another fragment. (E.g. sometimes online newspapers insert direct text saying "article continues below the image/advert" - they could instead use "jump" link. Ultimately, it indicates a page internal link.)<br />
| [[Talk:RelExtensions#On_footnote.2C_note.2C_and_jump|Talk]]<br />
| <br />
| Proposal<br />
|-<br />
| kin<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is part of the extended family of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| lang-alt-[ISO 639-1 code]<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains a version of the current document in an alternative language. "[ISO 639-1 code]" is replaced with the appropriate [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 language code]. The ISO 639-1 code is used when the browser (or other user agent) wants to display either the full name of the language or a flag, as a visual aid for the end user.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| lang-orig-[ISO 639-1 code]<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains a version of the current document in the language the document was originally written in. "[ISO 639-1 code]" is replaced with the appropriate [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 language code]. The ISO 639-1 code is used when the browser (or other user agent) wants to display either the full name of the language or a flag, as a visual aid for the end user.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| last<br />
|colspan=6| See HTML5<br />
|-<br />
| latest-version<br />
| hyperlink<br />
| hyperlink<br />
| The referenced document is the latest version of the current document.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.txt], [http://tools.ietf.org/search/rfc5829#section-3.2 RFC5829]<br />
| <br />
| Proposal<br />
|-<br />
| license<br />
|colspan=6| See HTML5<br />
|-<br />
| logout<br />
| external resource<br />
| not allowed<br />
| The linked document provides a resource for the UA to request when all currently open documents of the same "group" are closed (to facilitate logging out the current user).<br />
| [[LogoutRelExtension]]<br />
| <br />
| Proposal<br />
|-<br />
| <span id="longdesc">longdesc</span><br />
| hyperlink<br />
| hyperlink<br />
| Related to [http://www.w3.org/html/wg/tracker/issues/30 ISSUE-30]. <br/><abbr title="Assistive Technology">AT</abbr> should treat an element wrapped in a link with <code>rel="longdesc"</code> as equivalent to an element with <code>longdesc="URI"</code>. <br />
| (1) [http://lists.w3.org/Archives/Public/public-html/2007Jun/0738.html Eric Eggert's original proposal, 25th of June 2007], <br/>(2) [http://lists.w3.org/Archives/Public/public-html/2007Jun/0798.html Maciej's comment, 25th of June 2007], <br/>(3) [http://www.w3.org/Bugs/Public/show_bug.cgi?id=10434 Bug 10434, the HTMLwg, 2010]<br/>(4) [http://microformats.org/wiki/existing-rel-values#POSH_usage rel="longdesc" listed as POSH in Microformats.org]<br />
| <code>&lt;foo longdesc="URL"/></code> <br/>is synonymous to <br/><code>&lt;a rel="longdesc" href="URL">&lt;foo/>&lt;/a></code><br />
| Proposal<br />
|-<br />
| map<br />
| hyperlink<br />
| hyperlink<br />
| the referenced document represents a map of the location of the subject of the current document; parsers ''may'' use the URI or target page to determine coordinates.<br />
| to follow<br />
| <br />
| Proposal<br />
|-<br />
| me<br />
| hyperlink<br />
| hyperlink<br />
| the referenced document represents the same person as does the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| met<br />
| hyperlink<br />
| hyperlink<br />
| this person has met the referenced person<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| meta<br />
| external resource<br />
| hyperlink<br />
| publishing RDF/FOAF files<br />
| [http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/#transport RDF], [http://xmlns.com/foaf/spec/#sec-autodesc FOAF]<br />
| <br />
| Proposal<br />
|-<br />
| muse<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person inspires the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| neighbor<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person lives nearby the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| next<br />
|colspan=6| See HTML5<br />
|-<br />
| next-archive<br />
| hyperlink<br />
| hyperlink<br />
| A URI that refers to the immediately following archive document.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations], <br />[http://tools.ietf.org/html/rfc5005 RFC5005]<br />
| <br />
| Proposal<br />
|-<br />
| nofollow<br />
|colspan=6| See HTML5<br />
|-<br />
| noreferrer<br />
|colspan=6| See HTML5<br />
|-<br />
| noprefetch<br />
| external resource<br />
| hyperlink<br />
| Denies prefetching (not fetching) as a cost-control option for website owners, especially where pages are dynamic, leading to prefetching of wrong and useless pages.<br /><br />
The link provides a per-page denial whereas a and area provide a per-element denial.<br /><br />
For link, attributes rel="noprefetch" denies prefetching of the page at the href URL and rev="noprefetch" denies prefetching of the page bearing the link.<br /><br />
For a and area, rel is as above and rev is meaningless.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7918 W3C Bug 7918]<br />
| <br />
| Proposal<br />
|-<br />
| note<br />
| not allowed<br />
| hyperlink<br />
| An in-page or out-page jump to a footnote. This encompasses ''note'', ''footnote'', ''endnote'', and ''sidenote''.<br />
| [[Talk:RelExtensions#On_footnote.2C_note.2C_and_jump|Talk]]<br />
| <br />
| Proposal<br />
|-<br />
| openid.delegate<br />
| external resource<br />
| not allowed<br />
| OpenID 1.1 authentication delegation<br />
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID specification]<br />
| <br />
| Proposal<br />
|-<br />
| openid.server<br />
| external resource<br />
| not allowed<br />
| OpenID 1.1 authentication delegation<br />
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID specification]<br />
| <br />
| Proposal<br />
|-<br />
| openid2.local_id<br />
| external resource<br />
| not allowed<br />
| OpenID 2.0 authentication delegation<br />
| [http://openid.net/specs/openid-authentication-2_0.html#html_disco OpenID Auth 2.0 section 7.3.3]<br />
| <br />
| Proposal<br />
|-<br />
| openid2.provider<br />
| external resource<br />
| not allowed<br />
| OpenID 2.0 authentication endpoint<br />
| [http://openid.net/specs/openid-authentication-2_0.html#html_disco OpenID Auth 2.0 section 7.3.3]<br />
| <br />
| Proposal<br />
|-<br />
| parent<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a parent of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| payment<br />
| hyperlink<br />
| hyperlink<br />
| A URI where payment is accepted.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations]<br />
| <br />
| Proposal<br />
|-<br />
| pgpkey<br />
| hyperlink<br />
| not allowed<br />
| The linked document is the PGP public key file (which may contain multiple keys) of the author(s) of the page.<br />
| [http://purl.org/net/pgpkey/], [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html]<br />
| <br />
| Proposal<br />
|-<br />
| pingback<br />
|colspan=6| See HTML5<br />
|-<br />
| prefetch<br />
|colspan=6| See HTML5<br />
|-<br />
| presentation<br />
| external resource<br />
| hyperlink<br />
| Like ‘print’ this relation references a resource that represents the same content or topic, but in a ''very'' different manner. It is similar to media=projection, but is to be used where text is substituted by graphics, animations and sounds, which goes beyond mere style switching.<br />
This relation is also appropriate for links from thumbnail to full resolution images.<br />
| <br />
| slides, slideshow<br />
| Proposal<br />
|-<br />
| prev<br />
|colspan=6| See HTML5<br />
|-<br />
| prev-archive<br />
| hyperlink<br />
| hyperlink<br />
| A URI that refers to the immediately preceding archive document.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations], <br />[http://tools.ietf.org/html/rfc5005 RFC5005]<br />
| <br />
| Proposal<br />
|-<br />
| print<br />
| external resource<br />
| hyperlink<br />
| The referenced document is recommended for printing, even though the referent document is capable of being printed and both documents are of the same type, medium, and language. A typical case is where content spread over multiple pages is also available on a single page that is more convenient to print.<br />
This is semantically more specific than "canonical" and "alternate". Where type, medium, and/or language differ, consider "alternate"; where any of them differ but the purpose is printing, consider applying both values.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7645 W3C Bug 7645]<br />
| <br />
| Proposal<br />
|-<br />
| profile<br />
| hyperlink<br />
| hyperlink<br />
| this referenced link is a metadata profile for the current document<br />
| [http://www.w3.org/TR/html401/struct/global.html#profiles HTML Meta data profiles], <br />[http://www.w3.org/2003/g/glean-profile Example of profile in a-elements]<br />
| <br />
| Proposal<br />
|-<br />
| question<br />
| hyperlink<br />
| hyperlink<br />
| A link to the question this section or document answers, e.g. in a FAQ or in a sample exam. <br />
| [[Talk:RelExtensions#Q_and_A|Q&A]]<br />
| topic, subject, problem, (up)<br />
| Proposal<br />
|-<br />
| related<br />
| hyperlink<br />
| hyperlink<br />
| this referenced link identifies a resource related to the current document<br />
| [http://tools.ietf.org/html/rfc4287#section-4.2.7 Atom Syndication Format]<br />
| <br />
| Proposal<br />
|-<br />
| reply<br />
| hyperlink<br />
| hyperlink<br />
| A follow-up posting to this document or section or in the thread this document or section is an index of.<br />
| [[Talk:RelExtensions#Threading|Thread]]<br />
| posting, comment<br />
| Proposal<br />
|-<br />
| resource-package<br />
| external resource<br />
| not allowed<br />
| The linked document is a zipped resource package<br />
| [http://limi.net/articles/resource-packages/ Resource Packages]<br />
| <br />
| Proposal<br />
|-<br />
| resources<br />
| external resource<br />
| not allowed<br />
| a higher level alternative to HTTP Content Negotiation for other resources linked from the document, in a yet to be specified format<br />
|<br />
| resource-description, content-negotiation<br />
| Proposal<br />
|-<br />
| reviewer<br />
| hyperlink<br />
| not allowed<br />
| The linked document is the page/email an agent (people or firm or...) responsible for reviewing the content.<br />
| [http://wiki.csswg.org/test/css2.1/format#reviewer]<br />
| <br />
| Proposal<br />
|-<br />
| script<br />
| not allowed<br />
| not allowed<br />
| Was proposed to replace &lt;script>. Use &lt;script> instead.<br />
| none<br />
| <br />
| Rejected<br />
|-<br />
| search<br />
|colspan=6| See HTML5<br />
|-<br />
| self<br />
| hyperlink<br />
| hyperlink<br />
| A URI that refers to a resource equivalent to the containing element.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations], <br />[http://tools.ietf.org/html/rfc4287 RFC4287]<br />
| <br />
| Proposal<br />
|-<br />
| service<br />
| external resource<br />
| not allowed<br />
| Points to a resource describing a service API<br />
| [[ServiceRelExtension]]<br />
| <br />
| Proposal<br />
|-<br />
| shortlink<br />
| hyperlink<br />
| hyperlink<br />
| Identifies a shorter form of the URL for the current document, provided by the document owner.<br />
| [http://code.google.com/p/shortlink/wiki/Specification shortlink Specification]<br />
| <br />
| Proposal<br />
|-<br />
| sibling<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a sibling of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| sidebar<br />
|colspan=6| See HTML5<br />
|-<br />
| spouse<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a spouse of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| statechart<br />
| external resource<br />
| not allowed<br />
| A reference to an SCXML document that controls the application-flow of the current HTML document<br />
| [http://www.w3.org/TR/scxml/ SCXML]<br />
|<br />
| Proposal<br />
|-<br />
| stylesheet<br />
|colspan=6| See HTML5<br />
|-<br />
| subresource<br />
| hyperlink<br />
| not allowed<br />
| The referenced document is a subresource of the current document.<br />
| <br />
|<br />
| Proposal<br />
|-<br />
| sweetheart<br />
| hyperlink<br />
| hyperlink<br />
| this person considers the referenced person to be their sweetheart<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| tag<br />
|colspan=6| See HTML5<br />
|-<br />
| technicalauthor<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) responsible for the technical construction of the page (i.e. the HTML/CSS/PHP code), not for the content.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| thread<br />
| hyperlink<br />
| hyperlink<br />
| A hierarchic list of topic(s) and replies where this document or section belongs to either one.<br />
| [[Talk:RelExtensions#Threading|Thread]]<br />
| (index)<br />
| Proposal<br />
|-<br />
| timesheet<br />
| external resource<br />
| not allowed<br />
| SMIL Timesheet<br />
| [http://www.w3.org/TR/timesheets/#smilTimesheetsNS-Elements-Timesheet SMIL Timesheets 1.0]<br />
| <br />
| Proposal<br />
|-<br />
| topic<br />
| hyperlink<br />
| hyperlink<br />
| The initial posting this document or section is a reply to or index of.<br />
| [[Talk:RelExtensions#Threading|Thread]]<br />
| subject, (top)<br />
| Proposal<br />
|-<br />
| translatedfrom<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email that has been translation source for the current document. It also indicates that the current document is a translation and not an original work.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| translator<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) responsible for the translation of the page. It also indicates that the current page is a translation of an other document, which should be linked through a rel="translatedfrom".<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| up<br />
|colspan=6| See HTML5<br />
|-<br />
| us<br />
| hyperlink<br />
| hyperlink<br />
| The referenced document represents the same organisation as does the current document [cf rel-me]<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| webmaster<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) available for requests about the content of the page.<br />
| <br />
| maintainer<br />
| Proposal<br />
|-<br />
| widget<br />
| hyperlink<br />
| hyperlink<br />
| Points to a widget.<br />
| [http://dev.w3.org/2006/waf/widgets/Overview.html#autodiscovery Widgets 1.0 Editor's draft]<br />
| <br />
| Proposal<br />
|-<br />
| wlwmanifest<br />
| hyperlink<br />
| not allowed<br />
| A link to a manifest for Windows Live Writer.<br />
| [http://msdn.microsoft.com/en-us/library/bb463263.aspx msdn]<br />
| <br />
| Proposal<br />
|}<br />
<!-- Science: proof, lemma, theorem --><br />
<br />
The "Effect on link" column must either say "not allowed" if the rel value is not allowed on &lt;link> elements, "hyperlink" if the rel value creates a hyperlink, or "external resource" if the rel value creates a link to an external resource.<br />
<br />
The "Effect on a and area" column must either say "not allowed" or "hyperlink".<br />
<br />
For the "Status" section to be changed to "Accepted", the proposed keyword must either have been through the [http://microformats.org/wiki/process Microformats process], and been approved by the Microformats community; or must be defined by a W3C specification in the Candidate Recommendation or Recommendation state. If it fails to go through this process, it is "Rejected".<br />
<br />
For more details, see [http://whatwg.org/specs/web-apps/current-work/#linkTypes the HTML5 specification]. See also [http://microformats.org/wiki/existing-rel-values the Microformats wiki page on this matter].</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Image_Caption&diff=5492Image Caption2010-09-16T17:35:55Z<p>TheresaOConnor: revert spam</p>
<hr />
<div>Image caption are often found on the web, but there is no standard markup for this.<br />
<br />
== Problem Description ==<br />
Currently, most people use either a table, custom class names, or simply put the image inside a paragraph, each option either conveying a wrong meaning or being ambiguous with the rest of the content.<br />
<br />
An interesting analysis has been done on the subject by Dan Cederholm in one of his SimpleQuiz. [http://www.simplebits.com/notebook/2004/01/20/sqxi_conclusion.html His conclusion]:<br />
<br />
<blockquote>So in this case, I might choose option A -- because visually it shows the relationship between the items better than the others. But I suppose this is bad semantics. Or maybe just another case where we don't have the 'perfect' set of defined elements for this (very) specific job.</blockquote><br />
<br />
And his option A was:<br />
<pre><br />
<p><img scr="..."><br /><br />
Caption Text</p><br />
</pre><br />
<br />
In other word, he could not figure out anything good using current elements available in HTML, and, as most people do, had to create his own solution.<br />
<br />
Setting a standard for such things -- an explicit association between the caption and the illustration -- would help image search engines, it could enable the automatic creation of a figure index for a page. It would also be benificial for sight-impaired users. The fact that image captions should be treated differently to body text (they are not in the main flow of the document) suggests this element could be important for figure handling by assistive tools allowing e.g. aural browsers to skip captions except on explicit user request.<br />
<br />
=== Current Methods and Workarounds ===<br />
See [[Image Caption Examples]] for a couple of sample cases.<br />
<br />
== Proposed Solutions ==<br />
<br />
=== <figure> with &lt;caption> ===<br />
A <figure> element contains illustrative content for the current section. It can contain a &lt;caption> element, either as the first or the last child, that will be used to describe or give a caption to the content of the figure.<br />
<br />
<pre><br />
<figure><br />
<caption>Caption Text</caption><br />
<img src="..."><br />
</figure><br />
</pre><br />
<br />
==== Processing Model ====<br />
The processing model for HTML files must be changed so that the &lt;caption> is no longer ignored when outside the context of a table. It could also be a good idea to add a new figure insertion mode that would prevent figure captions from being moved to the enclosing table when inside a table cell, otherwise &lt;figure> will break in table-based layouts.<br />
<br />
<pre><br />
<table><br />
<tr><td><br />
<figure><br />
<caption>Caption Text</caption><br />
<img src="..."><br />
</figure><br />
</td></tr><br />
</table><br />
</pre><br />
<br />
==== Limitations ====<br />
&lt;caption> being ignored by current browsers when outside a table makes it impossible to style, and it'll also be terribly broken with table layouts when figure captions end up at the top (or the bottom) of the enclosing layout table.<br />
<br />
==== Implementation ====<br />
Parsing changes in this solution could be hard to implement given &lt;caption> element's legacy within &lt;table>.<br />
<br />
Putting aside the parsing problem, there's not much else to implement for visual browsers. A good display model that could be used to display figures is already available in CSS 2.1:<br />
<br />
<pre><br />
figure { display: table; }<br />
caption { display: table-caption; }<br />
</pre><br />
<br />
This would display the figure as a one-cell table, and the caption either at the top or at the bottom (depending on the [http://www.w3.org/TR/CSS21/tables.html#propdef-caption-side caption-side] property). The interesting part of this model is that the caption's width is constrained by the width of the figure, making it the ideal choice for floated figures.<br />
<br />
==== Adoption ==== <br />
The syntax is pretty straightforward to use. "figure" and "caption" are commonly used terms to designate exactly this feature in the print world. It should be a natural choice to authors that wonder how to markup their images.<br />
<br />
This markup won't work however if an author wants the caption to be elsewhere in the document. (In this proposal, &lt;caption> is pinned to the figure's content.) It does not seem a common use case however.<br />
<br />
=== <figure> with &lt;legend> ===<br />
A <figure> element contains illustrative content for the current section. It can contain a &lt;legend> element, either as the first or the last child, that will be used to describe or give a caption to the content of the figure.<br />
<br />
<pre><br />
<figure><br />
<legend>Caption Text</legend><br />
<img src="..."><br />
</figure><br />
</pre><br />
<br />
==== Processing Model ====<br />
:''To be completed''<br />
<br />
==== Limitations ====<br />
:''To be completed''<br />
<br />
==== Implementation ====<br />
A good display model that could be used to display figures is already available in CSS 2.1, the table model. A default stylesheet could look like this:<br />
<br />
<pre><br />
figure { display: table; }<br />
figure legend { display: table-caption; }<br />
</pre><br />
<br />
This would display the figure as a one-cell table, and the figure legend either at the top or at the bottom (depending on the [http://www.w3.org/TR/CSS21/tables.html#propdef-caption-side caption-side] property). The interesting part of this model is that the legend's width is constrained by the width of the figure, making it the ideal choice for floated figures.<br />
<br />
==== Adoption ==== <br />
"figure" and "legend" are commonly used terms in the print world, so their use could prove natural to authors. It is most likely that authors that need a markup for their figure will chose this one if it is sanctioned in a standard.<br />
<br />
This markup won't work if an author wants the caption to be elsewhere in the document. (In this proposal, &lt;legend> is pinned to the figure's content.) It does not seem a common use case however.<br />
<br />
=== Adjacent &lt;caption> or <legend> ===<br />
&lt;caption> or <legend> elements directly following a <img> element give the caption text for that image.<br />
<br />
<pre><br />
<img src="..."><br />
<caption>Caption Text</caption><br />
</pre><br />
<br />
<pre><br />
<img src="..."><br />
<legend>Caption Text</legend><br />
</pre><br />
<br />
==== Processing Model ====<br />
The processing model for HTML files must be changed so that the &lt;caption> is no longer ignored when outside the context of a table. It could also be a good idea to add a new figure insertion mode that would prevent figure captions from being moved to the enclosing table when inside a table cell, otherwise &lt;figure> will break in table-based layouts.<br />
<br />
:''Are the elements in this construct inline or block-level content? Currently <img> is inline.''<br />
<br />
If any other element, or non-whitespace text nodes are found between <img> and its corresponding caption element, elements are considered to not be adjacent, the semantic link is broken and it generates a parse error.<br />
<br />
==== Limitations ====<br />
<caption> being ignored by current browsers when outside a table makes it impossible to style, and it'll also be terribly broken with table layouts when captions end up at the top (or the bottom) of the enclosing layout table.<br />
<br />
:''To be completed: <legend> parsing''<br />
<br />
==== Implementation ====<br />
Parsing changes in this solution could be hard to implement given <caption> element's legacy within &lt;table>.<br />
<br />
:''To be completed: <legend> parsing implementation''<br />
<br />
Giving a distinctive visual style to figure captions may prove difficult with this design. If a browser wants to treat figures in a distinctive manner, it'll have treat them as a special case; the adjacent element selector in CSS can't distinguish between adjacent elements which are separated by text and those that are not.<br />
<br />
==== Adoption ==== <br />
:''To be completed''<br />
<br />
"legend" and "caption" are commonly used terms in the print world, so their use could prove natural to authors. Difficulties in styling are likely however to cause authors to always warp figures in a <div> element as most already do anyway (see [[Image Caption Examples]]).<br />
<br />
This markup won't work if an author wants the caption to be elsewhere in the document. It does not seem a common use case however.<br />
<br />
=== <label> defining attributes with nested markup ===<br />
A <label> element holds a value which should be treated the same way like the title attribute on <img>, except that it can contain nested markup. The for attribute of the label contains the id of the target element. A new type attribute on the label indicates which attribute the label intend to replace on the target.<br />
<br />
<pre><br />
<img id="img1" src="..."><br />
<label for="img1" type="title">...</label><br />
</pre><br />
<br />
==== Processing Model ====<br />
:''To be completed: Attribute override, progressive rendering, etc.''<br />
<br />
==== Limitations ====<br />
:''To be completed''<br />
<br />
==== Implementation ====<br />
:''To be completed''<br />
<br />
==== Adoption ==== <br />
This markup has the benefit that it'll work if an author wants the caption to be elsewhere in the document.<br />
<br />
:''To be completed''<br />
<br />
<br />
[[Category:Feature Request]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Talk:Reviewing&diff=5489Talk:Reviewing2010-09-15T15:46:20Z<p>TheresaOConnor: Reverted edits by Shaeha (talk) to last revision by EdwardOConnor</p>
<hr />
<div>Suggest a new tag:<br />
<do_not_reformat_source><br />
</do_not_reformat_source><br />
To provide a standardize way to tell tools like html tidy that the code in that section should not be reformatted without an explicit override. It would do nothing in the browser. Some markup is best left as is. For example, tables, embedded structured data, etc.<br />
<br />
[[User:Whitis|Whitis]] 21:51, 6 May 2009 (UTC)<br />
<br />
I would recommend asking the developers of the tools you use (e.g. tidy) to support a "class" value that would do this, that way it can work even with HTML4 documents, no need to add an element or anything. [[User:Hixie|Hixie]] 21:55, 6 May 2009 (UTC) <br />
<br />
No good. That would be specific to individual tools. There needs to be a standard used by all tools. If you want to<br />
include a standard class instead of a tag, that is fine. But it should be mentioned in the markup spec as that is one <br />
document that all the the tool developers will read. This does fall within the domain of the spec, just as providing<br />
print media support, handicapped support, etc. View source (or edit) is another presentation.<br />
<div class="do_not_reformat_source">...</div><br />
Consider this a source code accessibility issue. [[User:Whitis|Whitis]] 07:25, 7 May 2009 (UTC)<br />
<br />
<br />
4.11.2 datagrid element/folds/tabs<br />
Note: this comment and the ones which follow evolved as they were written. Some evolved with parts moving from tags to attributes or to CSS. Some evolved with new names based on finding existing precedent. Some of the changes were backpatched into the text, but not all.<br />
<br />
There should also be a <fold> tag (or equivalent functionality) that is very similar but less table/list oriented.<br />
<fold status="open"><br />
<h2>Section one</h2><br />
<p><br />
...<br />
</p><br />
<p><br />
...<br />
</p><br />
</fold><br />
<fold><br />
<h2>Section two</h2><br />
...<br />
</fold><br />
<br />
Attributes might be another way to do this which avoids inserting a tag between body and h2.<br />
<section fold="open"><br />
<h2 fold="open">Section one</h2><br />
...<br />
</section><br />
<ul><br />
<li fold="open"><br />
<fold_title>blah blah</fold_title> <!-- displayed whether folded or not --><br />
<br /><br />
blah blah <!-- not displayed when folded --><br />
<ul><br />
<li fold="open"><br />
<fold_title>Blah blah </fold_title><br />
<br /><br />
blah blah<br />
<li><br />
<ul><br />
<li><br />
</ul><br />
<br />
Absence of fold attribute makes it unfoldable unless the user allows it.<br />
<br />
This is similar to the hidden attribute but with some key differences. A fold Icon would still be present, along with descriptive text. Folding and unfolding would be accomplished by the user agent without any scripts to set the disabled attribute.<br />
In the case of sections, there would be special handling in that the text of any H1...H6 tag would not go away when folded. For other contexts, there may need to be a <fold_title>...</fold_title> or similar tag or a fold_title="tagname" attribute that lists<br />
what tag contents will be displayed when folded.<br />
<br />
This can be done in CSS as well. However folds and tabs are a basic logical construct and could exist in both domains. If the basic construct isn't defined at the HTML level, documents will be missing fold/tab titles that can be used by user stylesheets or user controls to override document behavior. Even if new tags/attributes are not defined, the basic markup using <div class="fold"> or <div class="tab"> (or other elements which can also be tabbed or folded) should be mentioned in the HTML5 spec.<br />
I.E. This is how you define where the folds/tabs would occur and this is what to use for a title and CSS is used to make it actually happen. You can not leave this to be fragmented by different folks using different classes. Since class allows multiple classes to be specifified, standard classes could be used while still retaining the ability to style each object individually (or as a subgroup) by specifying multiple classes. HTML5 at least needs to specify the classes to be used and make sure that the classes alone are adequate.<br />
<br />
Now technically, datagrid allows flow context. It is not at all clear how it handles flow content. The spaces for examples desparately need to be filled in and more examples given (flow content, sections, lists). If you are going to use it like the fold tag/attribute, <section> should be explictly mentioned and an example given, as that is an important case, though not the only one. As should numbered/unnumbered lists and definition lists. <pre><code> blocks are another important case where folding is reasonably expected. <br />
User agents may provide an ability to, at the users request, fold all sections, whether or not they have a fold attribute (it basically sets fold to yes if it exists and creates it if it doesn't. The user agent can also provide an unfold all. This would work for <section> tags but wouldn't work as well for (un)numbered lists as existing content doesn't identify a title to be retained when folded (unless it has a <br /> tag).<br />
<br />
"The data being presented is provided by script using the methods described in the following sections." No. That probably isn't what you meant to say. It can be provided by a script but it must be possible to provide it without one.<br />
<br />
The section on datagrids should spell out how you define the nesting levels and initial fold state on grid rows, even if that is described elsewhere.<br />
<br />
I don't see support for tabs. Maybe I didn't missed it, or maybe it is done using CSS. Tabs in the modern GUI sense. Not to be confused with the obsolete HTML3 tab tag (typewriter tabs) that were replaced with tables.<br />
<section tabs="true"><br />
<h2>Title</h2><br />
<section><br />
<h3>Tab title</h3><br />
....<br />
</section><br />
<section><br />
<h3>Tab Title</h3><br />
...<br />
</section><br />
</section><br />
If the browser doesn't support tabs, it can display the sections in a normal vertical orientation. section should take a title attribute, to be used when there isn't an h1...h6 section title.<br />
<br />
Another place where tabs are needed is in tables. Consider the tables here which are really subsets of a larger table. <br />
http://en.wikipedia.org/wiki/Comparison_of_media_players#Subtitle_support<br />
<colgroup tabs="true"><br />
<colgroup title="Tab 1"> <!-- first tab --><br />
...<br />
</colgroup><br />
<colgroup title="Tab 2"> <!-- second tab --><br />
...<br />
</colgroup><br />
</colgroup><br />
<br />
Browsers should be encouraged to provide a control that would convert sections or table column groups to tabs. <br />
Also to freeze or repeat row/column headings when a table wider/higher than the window scrolls, under user control.<br />
And they should provide an untabify control.<br />
<br />
Tabs may, and often will, occur inside forms.<br />
<br />
This could be provided via CSS, provided the base HTML contains provisions for a tab title. The same mechanism for titles can be used for both folding and tabbing.<br />
<br />
Note: looks like <legend> tag could be used for folding/tab titles, with H1...H6 used if not present. Needs to be allowed in <section> and <li>. <section><legend>...</legend> ... </section> would be a suitable docbook style replacement for the broken H1...H6 tags. This would make more sense than the <section><h1>...</h1> ... </section> kludge. I really don't like the idea of using H1 for lower level sections. Either use the right numbered level or use the unnumbered <legend>.<br />
<br />
<br />
~~~<br />
<br />
VIDEO<br />
Go visit hulu.com and youtube and imagine doing what they are doing with the video tag. We really need to make it possible to use standards to do what they are doing and not require Flash or Silverlight so the stuff will play across multiple operating systems, multiple browsers, on portable devices, and on set top boxes.<br />
<br />
It should not be necessary to use flash, silverlight, or scripts. Do it right and users have a case for insisting on standard compliant video players. The functionality I describe here is easy enough to implement and provides for the functionality offered by those services.<br />
<br />
Examples have been updated to be more consistent with SMIL, but not<br />
entirely. SMIL uses CamelCase, doesn't let you specify codecs (the<br />
SMIL type attribute is inadquate as it is only sufficient to identify<br />
the container format. The container format doesn't tell you if you<br />
can play what is inside. There are also some cases where it may make<br />
more sense to reuse existing HTML semantics. SMIL seemed a little<br />
week in some areas when it came to defining the global timeline<br />
without first reading the files, which might not be downloaded yet,<br />
but that may have just been due to some bad examples. SMIL doesn't<br />
seem to clearly define the difference between a playlist and a single<br />
playlist item composed of multiple clips (such as commercials). We<br />
aren't implementing SMIL just trying to be similar where we do the<br />
same thing unless there is a reason to do otherwise.<br />
<br />
<seq single_program="true"><br />
<!-- single program = false would be a playlist of separate logical programs --><br />
<br />
<base href="http:/www.example.com/media/webchurns/" /><br />
<!-- scope limited to within parent tag, optional, shortens urls --><br />
<br />
<segments total_time="17:37" title="As the Web Churns: Episode 13" ><br />
<video src="commercial1.ogg" noskip="true" vcodec="codec/FourCC" acodec="codec/FourCC" /><br />
<par><br />
<video src="chapter1.ogg" vcodec="codec/FourCC" acodec="codec/FourCC" /><br />
<textstream src="subtitles1_en.xxx" type="subtitle/subrip" captions="on" ><br />
initial_time="0:30" title="Chapter 1"><br />
<chapter_mark timestamp="5:00" /><br />
<chapter_mark timestamp="10:00" /><br />
<overlay start_time="0:00" end_time="0:05><br />
<img src="logo.png" /><br />
</overlay><br />
</segment><br />
<video src="commercial2.ogg" initial_time="12:00" noskip="true" vcodec="codec/FourCC" acodec="codec/FourCC" ><br />
<video src="chapter2.ogg" subtitle_src="subtitles2_en.xxx" initial_time="12:30" title="Chapter title 2" vcodec="codec/FourCC" acodec="codec/FourCC" /><br />
<segment src="chapter3.ogg" subtitle_src="subtitles3_en.xxx" initial_time="15:00" clip_begin="0:10" clip_end="0.20" vcodec="codec/FourCC" acodec="codec/FourCC" /><br />
<!-- previous plays a subset of the entire video --><br />
<overlay start_time="end"> <br />
<!-- <br />
When the video finishes playing, this content overlays <br />
the video. See youtube. Probably an image (with optional <br />
transparency) accompanied by an image map). Possibly a canvas. <br />
If no image map used, img can be contained with an <a href="..."> <br />
hypertext link <br />
--><br />
<img src="final_overlay.jpg" use_map="#shapes" /><br />
<map name="shapes"><br />
...<br />
</map><br />
</overlay><br />
</segments><br />
<alt><br />
Alternate content<br />
</alt><br />
</seq><br />
<br />
<br />
Chapter marks can be displayed as a mark on the timeline (see hulu, where they coincide with commercial breaks) and the next/prev chapter buttons can be used to skip between chapters as when watching a DVD. total_time and initial_time attributes allow the player to construct a timeline without loading all the video files to know their length. <br />
<br />
This next one allows a video to be played that is contained in a single file with the commericals inserted. An alternate syntax using sublips follows, which might be simpler.<br />
<br />
<br />
<seq><br />
<inserts><br />
<par><br />
<video src="episode15.mpg" title="Episode 15" /><br />
<textstream src="subtitles15.xxx" type="subtitles/subrip/" offset="-0.05" /><br />
</par> <br />
<insert src="commercial1.mpg" timestamp="0:00" duration="0:30" vcodec="codec/FourCC" acodec="codec/FourCC" ><br />
<insert src="commercial2.mpg" timestamp="0.15" duration=0:30><br />
<overlay start_time="0:00" end_time="0.10"><br />
<img src="..." use_map=""><br />
</vid_overlay><br />
<overlay start_time="0:15" end_time="0:20"><br />
<text><br />
Join the Mobile Infantry and save the Galaxy. <br />
Service guarantees citizenship. <br />
<a href="http://www.imdb.com/title/tt0120201/quotes"><br />
Would you like to know more?</a> <br />
<!-- Starship Troopers movie had an early example<br />
of hyperlinks over video --><br />
</text><br />
</overlay><br />
<inserts><br />
</seq> <br />
<br />
Or instead of inserts, you can list the main video multiple times with clip_begin, clip_end tags. <br />
<br />
<seq total_time=><br />
<video src=commercial1.mpg" initial_time="0:00" duration="0:30"/><br />
<video src="episode15.mpg" initial_time="0:30" clip_begin="0:00" clip_end="15:00/><br />
<video src="commercial2.mpg" initial_time="15:30" duration="0:30"/><br />
<video src="episode15.mpg" initial_time="16:00" clipBegin="15:00" clipEnd="15:30" ><br />
<overlay><br />
...<br />
</overlay><br />
</video><br />
<!-- this example doesn't include subtitles or chapter marks --><br />
<!-- vcodec and acodec left off in this example --><br />
</seq><br />
<br />
However, browsers may have trouble playing subclips, other than those which resume where the previous one left off (like after a commercial break). Randomly jumping 20 minutes into a video file requires the browser to download the 20 minutes that were not played and, if there is no index, scan through it to find the approriate time point. This can require too much bandwidth and prefetching. So, authors should be discouraged from jumping deep into the middle of clips which haven't already been played up to that point.<br />
<br />
If an overlay occurs at the end of a sequence, the overlay will overlay the<br />
last frame. However, it may be a non-transparent image or specify a background, in which case it doesn't.<br />
<br />
This next one is similar to the first except instead of the segments being presented as a single video, it allows multiple<br />
separate videos to be presented (similar feature for audio tag, also). The next/previous playlist item buttons on the viewer<br />
can be used.<br />
<seq single_program="false" ><br />
<video src="episode1.ogg" title="Episode 1" vcodec="codec/FourCC" acodec="codec/FourCC"/><br />
<video src="episode2.ogg" title="Episode 2" vcodec="codec/FourCC" acodec="codec/FourCC" /><br />
</video><br />
<seq single_program="false" ><br />
<audio src="song1.ogg" title="Song 1" acodec="FourCC"/><br />
<audio src="song2.ogg" title="Song 2" acodec="FourCC"/><br />
</audio><br />
Instead of "title=", we can include a <legend>. This allows formatting, though player may not support complex formating and may be separate from browser, so needs to be simple.<br />
<br />
When considering alternate video formats needed to support content and alternate languages, we are likely to end up with video/audio/text inside <switch> inside <par> inside <seq> as the general structure (though not all levels are always required). We could also have <seq> inside <par> for cases like full length subtitles overlaid on top of a video divided into shorter clips (possibly with commercial breaks).<br />
<seq><br />
<par><br />
<switch> <br />
<video ... /><br />
<video ... /><br />
<video ... /><br />
</switch><br />
<switch><br />
<textstream ...><br />
</switch><br />
<switch><br />
<audio ... /> <!-- usually embedded in video --><br />
</switch><br />
<overlay><br />
...<br />
</overlay><br />
</par><br />
<par><br />
<!-- next clip --><br />
</par><br />
</seq><br />
<br />
Still need to markup:<br />
- Whether the timestamps in subtitle files refer to the global timeline <br />
(appropriate for multimedia presentations) or within a particular clip<br />
(more appropriate for commercials inserted into a program)<br />
- Whether particular clips occupy space on the global timeline or not.<br />
For commercials, it may be better for them to appear as a singularity<br />
in the timeline so the timeline of the original material is maintained.<br />
<br />
If a browser uses an external player, it can stream the tags, preceeded by a basename tag, to stdin on the player. For a primitive player that doesn't support the xml tags, it can generate a simple playlist (with the inserts first?) or invoke the player with all the segments on the command line. mplayer, for example supports AX, Winamp, SMIL, or a simple one per line format). Xine supports asx, toxine m3u, pls, sfv, and raw text. Both support external subtitle files.<br />
External players may not understand complex html text overlays, image <br />
overlays (easily added), or image maps. It is possible some might support smilText. On the other hand, for built in players, these come naturally for the browser. <br />
<br />
Some systems, such as the X Video Extension, may have trouble with full overlays. They can do chroma keying to give full or no transparency but not partial transparency. However, OpenGL allows full compositing. Overlays at the end, when the video is paused, aren't a problem.<br />
<br />
Note that you can also do things like play a video and pause it and insert other video clips or audio + text/image as commentary with the above markup. You can also do a Mystery Science Theater 3000 audio+image overlay or audio+video overlay if the player supports it using the same markup format (requires a player that can mix audio and/or video and transparency in video stream). A DVD style commentary is somewhat problematic because we haven't included a volume control for the main video audio.<br />
<br />
SMIL tiny profile could be used. It doesn't support appear to support all the stuff above, but it can be added, possibly from the full profile. Or by trying to reuse existing HTML elements as I have done above. I changed my <video> and <audio> to <seq> and my segments to <video> and <audio>, above to resemble SMIL. http://www.w3.org/TR/SMIL/smil-tiny-profile.html<br />
<br />
Subtitles/captions are an important accessibility feature that SMIL tiny profile doesn't appear to adequately address. They may be included in the video stream or in a separate file. A separate file may not even be on the same server. the <par>,<smilText>,<br />
and <textStream> tags appear to be usable for subtitles:<br />
<par><br />
<video src="movie-vid.rm"/><br />
<textstream src="movie-sub-en.rt" systemLanguage="en" systemOverdubOrSubtitle="subtitle"/><br />
</par><br />
And the <switch> can be used to select a language. SubRip seems to be the most widely supported subtitle format at the moment.<br />
http://en.wikipedia.org/wiki/Comparison_of_media_players#Subtitle_support<br />
<br />
Thus adding <seq>, <par>, <textstream>, and <switch> to the <audio> and <video> tags and adding smil time options to the <video> and <audio> tags would do much of what I described (except the overlays at the end which I think there are other smil tags to accomplish though reusing built in img/imgmap/canvas might be easier to implement). If these tags are contained in a <smil> tag then they are SMIL (XHTML+SMIL) and if they are not, then HTML semantics would apply. <par> also allows you to merge separate audio and video files. <br />
<seq> (SMIL) Play items in sequence<br />
<par> (SMIL) Play items simultaneously<br />
<switch> (SMIL) Play one of the alternate items listed<br />
<video> (SMIL) video stream<br />
<audio> (SMIL) audio stream<br />
<textstream> (SMIL) text stream (subtitles)<br />
<img> (HTML) still image to overlay, or part of a slideshow. Needs additional timing tags.<br />
<map> (HTML) image map<br />
<a> (HTML) Hypertext link if use clicks on non transparent portion of image overlay and there is no imagemap.<br />
attributes Distinquish between a sequence of clips that make up one logical video (or audio) and a <br />
sequence that makes up multiple videos (playlist vs. fragments).<br />
<chapter> chapter marks<br />
<smil> NOT USED. If present, then you have XHTML+SMIL and a bunch of other options are available.<br />
<ref> (SMIL) other content types: SVG, flash (best avoided), etc.<br />
<alt> Alternate content when not using <object> semantics.<br />
<loop> Replay content ad-infitium (used for overlays at end of video).<br />
<br />
Streams need attributes that define the start and end positions within the stream to play and where the clip starts in the timeline.<br />
Same syntax will work for video, audio, and slideshows. Also allows subtitling audio (lyrics for song, transcript for radio broadcast). <Object> semantics could be used to specify multiple alternative formats since browsers may support only some audio, video, and subtitle formats. However, additional attributes may be needed to advise the browser in advance which formats are used in the referenced files so it can decide which to load without having to try to load and parse each one in turn.<br />
<br />
This example lets the browser choose a video source file based on whether or not it supports the Dirac video codec:<br />
<br />
<seq><br />
<switch><br />
<video src="episode15_dirac.ogg" acodec="codec/vrbs" vcodec="codec/dirac" type="applicaton/ogg"/><br />
<video src="episode15_theora.ogg" acodec="codec/vrbs" vcodec="codec/ther" type="application/ogg"/><br />
</switch><br />
</seq><br />
Dirac doesn't seem to have a FourCC yet, so I used the long ID.<br />
Here switch is used assuming we can't use the <object> semantics of including alternates in the tag body. If we use <par>, we can put overlays there, and could also put chapter marks there. We then need a general container that can be put inside <par> to contain html text, images, imagemaps, etc.<br />
<br />
<br />
There is a use for a special hypertext link tag (or attributes on the standard tag) that specifies:<br />
- The URL of a web page to load<br />
- An xpath that identifies a video object on that page<br />
- The URL of a subtitle file to insert when playing.<br />
This allows a website to provide links to another site where a video is viewed with the normal content of that site but subtitles are added by the first site providing the link. Since this alters the content at that site, the browser should popup a message<br />
that indicates this is being done so it doesn't appear the target site has been hacked if the user thinks they have followed<br />
a normal hypertext link.<br />
<br />
~~~~<br />
<br />
CANVAS<br />
<br />
I object to canvas only being scriptable. For each of the DOM drawing function calls, there should be an element.<br />
<canvas><br />
<canvas_scale x="1.2" y="1.2" /><br />
<canvas_rotate angle="90 /><br />
<canvas_translate x="1.2" y="2.3 /><br />
<canvas_transform ... /><br />
<canvas_set_transform ... /><br />
<!-- Note, if these tags are not empty, their effect could be limited to the tags contained within --><br />
<br />
<canvas_path><br />
<canvas_move_to x="1.23" y="2.35" /><br />
<canvas_line_to(x="1.23 y="4.56 >/<br />
<canvas_quadratic_curve_to cpx="1.23" cpy="4.56" x="7.89" y="0.12" /><br />
<canvas_bezier_curve_to cp1x="1.2" cp1y="3.4" cp2x="4.5" cp2y="6.7" x="8.9" y="0.1" /><br />
<canvas_arc_to x="1.2" y="3.4" radius="5.5" direction="ccw" /><br />
<closepath /><br />
<stroke /><br />
<fill /><br />
</canvas_path><br />
<canvas_rect x="1.2" y="3.4" w="5.6" h="6.7" /><br />
<canvas_arc x="1.2" y="2.3" radius="5.6", start_angle="7.8" send_angle="9.0", direction="cw");<br />
<br />
<!-- etc. for other function calls --><br />
</canvas><br />
<br />
SaveState()/RestoreState():<br />
<canvas_save_state /><br />
</canvas_restore_state /><br />
<canvas_push> <!-- SaveState() --><br />
<!-- drawing commands here --><br />
</canvas_push> <!-- RestoreState() ---><br />
<br />
It costs almost nothing to add these tags compared to the work of implementing the canvas. It provides a simple alternative to<br />
SVG that uses built in functionality, is less complex, and is XML friendly (no storing paths inside attribute strings), and allows<br />
drawing simple graphs without scripts, or when scripts are disabled for security reasons or not implemented. The javascript functions already defined could populate the display list, stored as XML tags in the DOM hierarchy.<br />
<br />
arcTo(), should only take one coordinate; it is inconsistent with other path operators. If you want the current functionality, call moveTo() first. It should use the current position as the starting point to be consistent with the others. It is also missing a direction which makes it ambiguous as there are always two arcs that satisfy the endpoints and radius.<br />
I also have doubts about using width and height rather than two coordinates for rect.<br />
~~~~<br />
<br />
Smarter subscripts/superscripts:<br />
superscripts and subscripts do not behave properly when both are used, nor do the accomodate all the positions needed.<br />
There is a center, plus 8/16 compass rose positions, plus two extra far left and far right positions. Started with 9, then was improved.<br />
<br />
<compass style="{child-font-size: -2}"><br />
<C></C> <!-- center --><br />
<E></E> <!-- east, suffix --><br />
<ENE></ENE> <!-- east northeast, superscript position --><br />
<NE></NE> <!-- northeast --><br />
<N></N> <!-- north, over--><br />
<NW></NW> <!-- northwest --><br />
<WNW></WNW> <!-- west northwest, presuperscipt postition --><br />
<W></W> <!-- west, prefix --><br />
<WSW><WSW> <!-- west southwest, presubscript position --><br />
<SW></SW> <!-- southwest, presubscript --><br />
<S></S> <!-- south, under --><br />
<SE></SE> <! -- southeast --><br />
<ESE><ESE> <!-- east southeast, subscript position --> <br />
<EE></EE> <!-- east of east, suffix --><br />
<WW></WW> <!-- west of west, prefix --><br />
<!-- four more halfway postions NNW, SSW, NNE, SSE --><br />
</compass><br />
Useful for Periodic table elements, simple, simultaneous super and subscripts, various linguistic stuff, etc.<br />
Without halfway positions and the far east and west positions, it acts like a 3x3 table with a concise notation and the appropriate cells populated. The four alternate corner cells positions are shifted half a cell towards the midline (to super/subscript positions) and the alternate far east and far west cells are shifted outward to new columns centered on the midline providing a way to guarantee that text which preceeds or follows is aligned with the midline.<br />
<br />
would look if super and sub scripts were placed over/above each other.<br />
<ninebox><WW>x=</WW><C>&integral_sign;</C><SE>&negative_infity;</SE><NE>&positive_infinity;</NE><WW>sin(x)/x</WW><ninebox><br />
http://preparatorychemistry.com/Bishop_Isotope_Notation.htm Sodium with isotope, weight, and charge.<br />
<ninebox><WNW>23</NW><ESE>11</ESE><C>Na</C><ENE>+</ENE></ninebox><br />
Instead of squash, you can have ENE, ENW, ESW, ESE for the four alternate corner locations. <br />
Of course, ninebox can be added to CSS, instead. display=ninebox, display=NW, display=NE, etc.<br />
This is good if you style:<br />
<element><name>NA</name><mass>23</mass><number>11</number><charge>+<charge></element><br />
But it does get verbose if you have to use <SPAN class="element">, etc. Styles might apply to change the size or shift position, but the fundamental structural orientation is more basic. <br />
<br />
This is finishing the job that subscript and superscript started and is arguably not just a style. It may not be that abstract but it is fundamentally structural and not just a superficial styling detail. And it eliminates some incredibly contorted use of tables for non-tabular data. You need a 11x9 table with lots of rowspans and colspans, to define the overlapping cell locations occupied by these locations. <br />
<br />
The basic tags could be defined and CSS used to fine tune the position or to apply equivalent behavior to abstract div/span markup or other xml namespaces.<br />
<br />
Note that even unicode deviates from its left-to-right/right-to-left model to provide an over and under code, but doesn't finish the job.<br />
<br />
This is more basic than MathML which also fails to be a suitably abstract math notation - you can't actually evaluate MathML expressions (hence the creation of OpenMath). This also applies to various areas outside the math domain.<br />
<br />
Started out as 9 boxes, hence the name, but a more suitable one should be used. Maybe compass?<br />
~~~~ <br />
<br />
<br />
Nine slice images<br />
<br />
(Note: this one is in CSS3, so it only needs mention in HTML5 spec)<br />
<br />
Various systems use an image divided into 9 parts (like a tic-tac-toe board). Some names include scale-9 and 9-scale This defines two X and two Y image slice locations. When the image is scaled, the four corners are not scaled and the four edge squares and the center square are expanded. Very handy for buttons, tabs, window borders, etc. An example would be a rectangle with rounded edges. <br />
<br />
To implement this, you need a slice_x1, slice_x2, slice_y1, and slice_y2 attribute to be added wherever a tag has an attribute that can point to an image. (Note that this could also include pointing to an SVG file, though SVG tools probably haven't added this functionality. <br />
<br />
In the simplest cases, this would be replaced with desparately needed corner rounding on CSS. But it may contain much more detail.<br />
<br />
http://rwillustrator.blogspot.com/2007/04/understanding-9-slice-scaling.html<br />
This, with <br />
width="640" height="480" slice_x1="8" slice_y1="8" slice_x2="24" slice_y2="24"<br />
or more succinctly <br />
width=640 height=480 img_slice="8,8,24,24"<br />
or even more succinctly:<br />
width=640 height=480 img_slice="8" <br />
replaces an entire screenfull of HTML and reduces 9 image WGETS to one. It also eliminates additional structural damage because<br />
you can simply say <br />
background="foo.png" img_slice="8,8,24,24"<br />
And not put have your content in the middle of this 9x9 table monstrosity. Or better yet, style="{background-image=foo.png; background_img_slice=8,8,24,24;}" (actually, the slices have been added to border-image as:<br />
border-image: url("border.png") 8 8 8 8;<br />
<br />
<br />
http://www.neverpanic.de/blog/single/9-slice-scaling-in-html/<br />
http://blog.hempton.com/2008/11/9-grid-scaling-support-in-javascriptcss/<br />
http://www.bytearray.org/?p=118<br />
http://grub.enbug.org/ThemeFormat<br />
<br />
These are supported in flash, adobe illustrator, fireworks, a jQuery plugin, an actionscript module, and a number of user interface toolkits. Even the grub bootloader supports it, after a fashion, automatically loading 9 images using a wildcard. Apparently, some even scale SWF animated backgrounds this way as if they were images.<br />
<br />
This should be pushed to CSS3 with the appropriate CSS3 module being released before HTML5 with the HTML5 specification specifically calling for HTML5 compliant tools to implement it and advising users to avoid the 9 separate images plus hideous markup. It would be a good addition to PNG, as well. CSS3 appears to accomodate 8 of the 9 slices, as 8 seperate images in the border module. But it also allows border-image to use a 9-slice. This will apparently be in firefox 3.1. I do think this merits some mention in the HTML5 spec. http://www.lrbabe.com/sdoms/borderImage/index.html<br />
<br />
~~~<br />
<br />
<pre>blocks could have a numbering option <pre number="100"> sets the initial line number to 100 and activates line numbering. This allows the text which accompanies a <pre><code> block to reference individual lines. The initial number needs to be settable because in an online source code browser, numbers should line up with original file. This can, however, be done by including<br />
the text of the numbers for autogenerated content. <textareas> could also have numbering; this is very useful for matching up error messages with lines of markedup text when a wysiwyg editor is not used (for example, in a wiki); also, this is compatible with javascript wysiwig editors that take over a text area. Low priority, but worth mentioning.<br />
~~~~</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Time_element&diff=5442Time element2010-08-26T15:29:06Z<p>TheresaOConnor: Reverted edits by Myrrhman (talk) to last revision by Pigsonthewing</p>
<hr />
<div>Summary: Research, data, use cases, issues, and enhancements related to the [http://www.w3.org/TR/html5/text-level-semantics.html#the-time-element HTML5 <code>time</code> element].<br />
<br />
<br />
HTML5's new &lt;time&gt; element presents a huge opportunity to improve the publishing of datetime information on the web, the biggest opportunity since the introduction of hCalendar and other time-based microformats.<br />
<br />
However, the &lt;time&gt; element currently has several shortcomings that both prevent it from being used in numerous use-cases, and are suboptimal for authoring and data longevity.<br />
<br />
Please read the following proposals for improving the &lt;time&gt; element, grouped by category, and offer your opinions, use-cases, evidence and - hopefully - support in the respective discussion sections.<br />
<br />
<br />
Thanks for your consideration,<br />
<br />
[[User:Tantek|Tantek]] (and other proposal authors).<br />
<br />
<br />
Please add new proposals to the end of the most relevantly related section, or if you're not sure where (or if there is no related section), at the end of the [[Time_element#Miscellaneous_proposals|Miscellaneous proposals]] section.<br />
<br />
=Date granularity=<br />
== year only ==<br />
The time element should accept just a year.<br />
;ISO8601 syntax<br />
:YYYY<br />
=== year only use cases ===<br />
use case research:<br />
* http://microformats.org/wiki/birthday-examples#year_only<br />
* use cases in VCARDDAV & EDTF - see external links<br />
* [http://en.wikipedia.org/wiki/Template:Start_date Wikipedia 'Start date' template] - thousands of [http://bit.ly/aKhmdQ YYYY instances]<br />
* [http://en.wikipedia.org/w/index.php?title=Ethan_Stiefel&oldid=377074089 Wikipedia infobox with YYYY birthdate] (unknown MM-DD)<br />
* Copyright notices are often year-only; e.g. that at the foot of [http://www.rspb.org.uk/groups/suttoncoldfield/]<br />
* In biological taxonomy, a species', genus' or other rank's ''authority'' (the person who named it, and the year they did so) always includes a whole-year date value. For example:<br />
**Barn Owl, ''Tyto alba'' (Scopoli, 1769) [http://en.wikipedia.org/wiki/Barn_owl]<br />
**Strigiformes (Wagler, 1830) [http://en.wikipedia.org/wiki/Owl]<br />
*Citations from a bibliography which list two or more works by the same author disambiguate them by year<br />
*Commerce<br />
** "a piece of jewellery hallmarked 1933"<br />
** "a 1973 Chevy"<br />
*Sport<br />
**2008 Olympics<br />
**1966 World Cup<br />
*Awards<br />
**"1973 Oscar for best film"<br />
**"1988 Nobel Peace Prize"<br />
*Restyling dates for localisation and to follow user conventions<br />
**2010 to 平22年 to 2010年 (all acceptable ways to represent 2010 in Japan)<br />
* Relative dates in texts: news websites and blogs often use phrases such as<br />
** "damages during last year's Gaza offensive" [http://www.un.org/apps/news/story.asp?NewsID=33559],<br />
** "recession next year almost inevitable" [http://www.reuters.com/article/idUSTRE65E5K520100615]<br />
<br />
=== year only discussion ===<br />
<div class="discussion"><br />
Opinions / discussion:<br />
* +1 [[Faruk]] (per [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7145 Bug 7145 - Valid date strings should accept ambiguous inputs, like "2009" or "2007-01"]) One example is the very common archive view found on most blogs, which contain distinct links or headers for each year, each month per year, and often each date within a chosen or highlighted month. Currently, the <code>&lt;time&gt;</code> element only allows for <code>datetime</code> values as precise as a specific day, e.g. YYYY-MM-DD.<br />
* -1 [[Hixie]] - "Without clear use cases, I don't intend to change the spec here." (ibid)<br />
* +1 [[Tantek]] (per [http://www.zeldman.com/superfriends/guide/#time HTML5 Super Friends Technical Details: time element])<br />
* +1 [[User:Pigsonthewing|Andy Mabbett]] (Per use cases in VCARDDAV & EDTF - see external links)<br />
* +1 [[User:Philipj|Philip Jägenstedt]] - for marking up [http://musicbrainz.org/release/aa82c130-c734-4d9c-b06a-5bba9b44295d.html release dates on e.g. MusicBrainz] where the date is given as YYYY, YYYY-MM or YYYY-MM-DD.<br />
* +1 [[User:asbjornu|Asbjørn Ulsberg]] - for marking up [http://en.wikipedia.org/wiki/World_war_2 years on Wikipedia] ("...global military conflict lasting from 1939 to 1945...").<br />
* +1 [[User:GlennJones|Glenn Jones]] - This is often used to format date description for resume's Stackoverflow http://careers.stackoverflow.com/klmr I could list more cases in the wild. Like YYYY, YYYY-MM or YYYY-MM-DD its part of the http://www.w3.org/TR/NOTE-datetime profile.<br />
* +1 [[User:Oli|Oli Studholme]] This would be useful for semantically marking up years, as in Japan there’s an additional era-based method of representing years (and even Japanese people find it difficult to convert between them), and it would allow the browser to automatically display the user-preferred format. It would also also enable browser-based localisation (adding a 年 after the year). Finally it would be useful for marking up future imprecise dates (e.g. events being planned), allowing someone to add these dates to a calendar automatically (rather than marking up teh events plus manually adding them to a calendar). ref: [http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/028025.html email to WHATWG]<br />
* +1 [[User:Ocolon|Martin Janecke]] - This would be great to mark up relative dates ("next year I will …") that actually refer to an absolute date in the context of the text and the publication date of the text respectively.<br />
* ...<br />
</div><br />
<br />
=== year only related posts ===<br />
Related posts (listed with quotes directly related to year only) :<br />
* [http://pigsonthewing.org.uk/dates-and-coordinates-in-html5/ 2009-02-23 Dates and coordinates in HTML5] blog post by Andy Mabbett - <blockquote cite="http://pigsonthewing.org.uk/dates-and-coordinates-in-html5/">hCalendar microformats are already used to mark up imprecise dates (“June 1977″; “2009″). ISO8601 already supports them. Why not HTML5?</blockquote><br />
* [http://www.brucelawson.co.uk/2009/html-5-politics-and-me/ 2009-02-25 HTML 5, politics and me] blog post by Bruce Lawson - look for mention of "time element" which mentions: <blockquote cite="http://www.brucelawson.co.uk/2009/html-5-politics-and-me/">I see no reason why authors shouldn’t be able to mark up ... dates like ... “1935″ which are currently disallowed by the spec</blockquote><br />
<br />
== year month only ==<br />
The time element should accept just a year and a month.<br />
;ISO8601 syntax<br />
:YYYY-MM<br />
<br />
=== year month use cases ===<br />
* Blog/publishing archive pages - see Benward.me, ablognotlimited.com (need specific links to archive pages)<br />
** http://www.flickr.com/photos/tantek/archives/<br />
** [http://lists.whatwg.org/htdig.cgi/help-whatwg.org/ whatwg's own mailing list archives] (!)<br />
* output equivalent of <code>&lt;input type="month"&gt;</code>, see [[Time_element#impedance_match_new_date_time_inputs|impedance match new date time inputs]].<br />
* use cases in VCARDDAV & EDTF - see external links<br />
* [http://en.wikipedia.org/wiki/Template:Start_date Wikipedia 'Start date' template] - thousands of [http://bit.ly/aKhmdQ YYYY-MM instances]<br />
* Credit/ debit card expiry dates, entered into, then republished for verification on, e-commerce sites (security concerns prohibit use of example URL)<br />
* Restyling dates for localisation and to follow user conventions<br />
** 2010-08 to 08-2010 to 平22年8月 to 2010年8月 (all acceptable ways to represent August 2010 in Japan)<br />
* Relative dates in text: news websites, blogs and statistical institutes often use phrases like:<br />
** "in June 2010, the turnover […] decreased by 10.5% compared to the same month of the previous year." [http://www.nsi.bg/eventen.php?n=568]<br />
** "George W. Bush leaves office in January next year" [http://afp.google.com/article/ALeqM5hm2kKrBzl5p5Psm-EryzKK_m8H_A]<br />
<br />
=== year month discussion ===<br />
<div class="discussion"><br />
Opinions / discussion:<br />
* +1 [[Faruk]] (per [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7145 Bug 7145 - Valid date strings should accept ambiguous inputs, like "2009" or "2007-01"]) One example is the very common archive view found on most blogs, which contain distinct links or headers for each year, each month per year, and often each date within a chosen or highlighted month. Currently, the <code>&lt;time&gt;</code> element only allows for <code>datetime</code> values as precise as a specific day, e.g. YYYY-MM-DD.<br />
* -1 [[Hixie]] - "Without clear use cases, I don't intend to change the spec here." (ibid)<br />
* +1 [[User:Tantek|Tantek]] I think the blog archives use case (where blogs often link to their archives by a specific month and year) is sufficient to justify adding this capability to the time element. Content hosting sites like Flickr also list archives by specific year/month, e.g. see http://www.flickr.com/photos/tantek/archives/<br />
* +1 [[User:Pigsonthewing|Andy Mabbett]] (Per use cases in VCARDDAV & EDTF - see external links)<br />
* +1 [[User:Philipj|Philip Jägenstedt]] - for marking up [http://musicbrainz.org/release/aa82c130-c734-4d9c-b06a-5bba9b44295d.html release dates on e.g. MusicBrainz] where the date is given as YYYY, YYYY-MM or YYYY-MM-DD.<br />
* +1 [[User:asbjornu|Asbjørn Ulsberg]] - for marking up [http://en.wikipedia.org/wiki/World_war_2#Japanese_invasion_of_China month+year on Wikipedia] ("In July 1937, Japan captured the former Chinese imperial capital of Beiping...").<br />
* +1 [[User:GlennJones|Glenn Jones]] - This is the most commonly used format date description for Resume's. Linked-in use it http://www.linkedin.com/in/steveganz and Stackoverflow http://careers.stackoverflow.com/klmr I could list many more cases in the wild.<br />
* +1 [[User:Oli|Oli Studholme]] As with the year example above, this would be useful for semantically marking up year-month dates, as in Japan there’s an additional era-based method of representing years (and even Japanese people find it difficult to convert between them), and it would allow the browser to automatically display the user-preferred format. It would also also enable browser-based localisation (adding a 年 after the year, and 月 after the month). Having this data semantically notated would help make the use in Japan of 2-digit years on credit cards and in e-commerce more accessible. Finally it would be useful for marking up future imprecise dates (e.g. events being planned), allowing someone to add these dates to a calendar automatically (rather than marking up teh events plus manually adding them to a calendar). [ref: [http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/028025.html email to WHATWG]]<br />
* +1 [[User:Ocolon|Martin Janecke]] - This would be great to mark up relative dates ("next January I will …") that actually refer to an absolute date in the context of the text and the publication date of the text respectively.<br />
* ...<br />
</div><br />
<br />
=== year month related posts ===<br />
Related posts (listed with quotes directly related to year-month) :<br />
* [http://pigsonthewing.org.uk/dates-and-coordinates-in-html5/ 2009-02-23 Dates and coordinates in HTML5] blog post by Andy Mabbett - <blockquote cite="http://pigsonthewing.org.uk/dates-and-coordinates-in-html5/">hCalendar microformats are already used to mark up imprecise dates (“June 1977″; “2009″). ISO8601 already supports them. Why not HTML5?</blockquote><br />
* [http://www.brucelawson.co.uk/2009/html-5-politics-and-me/ 2009-02-25 HTML 5, politics and me] blog post by Bruce Lawson - look for mention of "time element" which mentions: <blockquote cite="http://www.brucelawson.co.uk/2009/html-5-politics-and-me/">I see no reason why authors shouldn’t be able to mark up ... dates like “July 2008″ ... which are currently disallowed by the spec</blockquote><br />
* [http://www.brucelawson.co.uk/2009/marking-up-a-blog-with-html-5-part-2/#time 2009-03-06 Marking up a blog with HTML 5 (part 2) : Time] blog post by Bruce Lawson: <blockquote>I suggest the spec be amended to allow dates like "July 1966"</blockquote><br />
* [http://www.brucelawson.co.uk/2009/html-5-whats-hot-whats-not/ 2009-08-20 HTML 5: what’s hot, what’s not] blog post by Bruce Lawson - see section on TIME which explicitly mentions: <blockquote cite="http://www.brucelawson.co.uk/2009/html-5-whats-hot-whats-not/">The time element is still hamstrung by not being able to markup ... dates like “December 1935″</blockquote><br />
* [http://adactio.com/journal/1604/ 2009-08-30 HTML5 and me] blog post by Jeremy Keith - see section on "time" which explicitly mentions <blockquote cite="http://adactio.com/journal/1604/">make a piece of information like “April 1912” machine-readable</blockquote><br />
* [http://html5doctor.com/the-time-element/ 2010-02-09 The time element (and microformats)] blog post on HTML5 Doctor by Bruce Lawson - mentions: <blockquote>The only trouble with &lt;time&gt; is that the <nowiki>[sic]</nowiki> it must contain positive date on the Proleptic Gregorian calendar, meaning you can’t encode a date before the Christian Era. Neither can you encode imprecise dates such as “July 1904″.</blockquote><br />
<br />
== year week only ==<br />
The time element should accept just a year and a week number.<br />
;ISO8601 syntax<br />
:YYYY-WNN<br />
;use case research<br />
:no examples in the wild currently. If anyone knows of any sites which publish references to specific weeks of a year, either by name / expression (e.g. "first week of the year") or by specific number (e.g. "weeks 1-26"), please provide URLs and quotes of example content.<br />
:output equivalent of <code>&lt;input type="week"&gt;</code>, see [[Time_element#impedance_match_new_date_time_inputs|impedance match new date time inputs]] above.<br />
<br />
;reasoning<br />
:to provide the output equivalent of <code>&lt;input type="week"&gt;</code><br />
<br />
See [[Time_element#impedance_match_new_date_time_inputs|impedance match new date time inputs]] above.<br />
<br />
<div class="discussion"><br />
Opinions / discussion:<br />
* +1 [[Tantek]] per good design of impedance matching date time inputs.<br />
* ...<br />
</div><br />
<br />
== month day only ==<br />
The time element should accept just a month and a day.<br />
;ISO8601 syntax<br />
:--MM-DD<br />
;use case research<br />
:http://microformats.org/wiki/birthday-examples#month_and_day_only<br />
:[http://www.ietf.org/mail-archive/web/vcarddav/current/msg00999.html use cases discussed in VCARDDAV] & EDTF - see external links<br />
:Facebook - allows users to elect to show their birthday as, for example, "17 December", with no year.<br />
<br />
<div class="discussion"><br />
Opinions / discussion:<br />
* +1 [[Tantek]] (per [http://www.zeldman.com/superfriends/guide/#time HTML5 Super Friends Technical Details: time element])<br />
* +1 "radiz" implied support for --MM-DD with the use case question: "How to use &lt;time&gt; with a date in astrology?" in the article http://html5doctor.com/your-questions-answered-6/<br />
* +1 [[User:Pigsonthewing|Andy Mabbett]] (Per [http://www.ietf.org/mail-archive/web/vcarddav/current/msg00999.html use cases discussed in VCARDDAV] & EDTF, e.g. birthdays, wedding anniversaries - see external links)<br />
** [http://portablecontacts.net/draft-spec.html#anchor16 Portable contacts allows this] using a "0000" year value.<br />
* ...<br />
</div><br />
<br />
= HTML5 internal consistency =<br />
== impedance match new date time inputs ==<br />
The time element should be able to represent every granularity of times and dates that the new date time <code>&lt;input&gt;</code> elements allow. Here is a list of all the date time <code>&lt;input&gt;</code> elements along with the corresponding <code>&lt;time&gt;</code> element usage (if applicable)<br />
<br />
<pre><nowiki><br />
<input type="date"> - <time>YYYY-MM-DD</time><br />
<input type="datetime"> - <time>YYYY-MM-DDTHH:MM:SS</time><br />
<input type="month"> - not supported in current time element<br />
<input type="week"> - not supported in current time element<br />
<input type="time"> - <time>HH:MM:SS</time><br />
<input type="datetime-local"> - <time>HH:MM:SS-ZZ:YY</time><br />
New proposed input elements:<br />
<input type="year"> - not supported in current time element<br />
<input type="month-day"> - not supported in current time element<br />
</nowiki></pre><br />
<br />
In particular the <code>&lt;time&gt;</code> element is missing support for the following date inputs:<br />
<br />
* input type="month" - this would be satisfied by the [[Time_element#year_month_only|time element year month proposal]].<br />
* input type="week" - this would be satisfied by the [[Time_element#year_week_only|time element year week proposal]].<br />
<br />
In addition, if the new proposed [[input]] elements are accepted, the respective time element support should be added as well:<br />
<br />
* input type="year" - this would be satisfied by the [[Time_element#year_only|time element year proposal]].<br />
* input type="month-day" - this would be satisfied by the [[Time_element#month_day_only|time element month day proposal]].<br />
<br />
<div class="discussion"><br />
Opinions / discussion:<br />
* +1 [[Tantek]]<br />
* +1 [[User:Pigsonthewing|Andy Mabbett]]<br />
* +1 [[User:asbjornu|Asbjørn Ulsberg]]<br />
* ...<br />
</div><br />
<br />
= Proposals extending scope =<br />
<br />
== Fuzzy dates ==<br />
The time element should accept ''fuzzy'' (uncertain, approximate) dates ("around 18 June 1855" "summer 1970", "circa December 1963", "flourished 1580"), centuries, and allow eras ("Edwardian", "bronze age", "Jurassic") in a manner to be determined; perhaps once defined by EDTF efforts.<br />
<br />
;Use cases:<br />
:1. "... an application that might input Wikipedia data and output an annotated visual timeline. For movements or trends rather than events, it would need to output rough dates and date ranges like 2001-2003, rather than exact dates."[http://www.zeldman.com/superfriends/guide/#time] <br />
::Implemented, see [http://en.wikipedia.org/w/index.php?title=Bob_Brettle&oldid=376645341#External_links], (target site currently broken, but worked previously; a fix is promised shortly), but can only map precise dates, because there is currently no way to mark up fuzzy dates in a machine-readable format. The acceptance of this proposal would allow this implementation and others to map all such dates. Note that the implementation works with any site, not just Wikipedia, by parsing hCalendar microformats.<br />
:2. [http://hypermedia.research.glam.ac.uk/kos/star/time-periods/ Time periods in astronomy]<br />
:: building on the English Heritage Periods list and Timelines thesaurus - see [https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind1008&L=FISH&F=&S=&P=3927 Douglas Tudhope's mailing list post] and prior discussion<br />
:3. [http://www.fish-forum.info/i_apl_e.htm http://www.fish-forum.info/i_apl_e.htm Archaeological Periods list] via [http://www.fish-forum.info/i_apl.htm Archaeological Periods list meta page] - see [https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind1008&L=FISH&F=&S=&P=1738 Nick Boldrini's mailing list post]<br />
:4 ...<br />
<br />
<div class="discussion"><br />
Opinions / discussion:<br />
* +1 [[User:Pigsonthewing|Andy Mabbett]] (Per use cases in "Extended Date Time Format" proposals & TEI - see external links)<br />
**Uncertainty possibly resolved by a "certainty" attribute: <pre><nowiki><time datetime="1855-06-18" certainty="3days">around 18 June 1855</time></nowiki></pre><pre><nowiki><time datetime="1970-06" certainty="45days">summer 1970</time></nowiki></pre>(with "45days" meaning "+/- 45 days" - in other words, a 90-day window, and similar allowance for year or other ranges; or: <pre><nowiki><time datetime="1963-12" certainty="circa">circa December 1963</time></nowiki></pre>with pre-defined prose values allowed, such as "flourished", "notbefore", "notafter", etc.<br />
* +1 [[User:eatyourgreens|Jim O'Donnell]] (Dates such as 'circa 1910' published on Flickr eg. [http://www.flickr.com/photos/nationalmaritimemuseum/4793356412/ The RNVR Training Ship 'Buzzard'…] also [http://www.flickr.com/photos/nationalmaritimemuseum/archives/ a list of fuzzy dates for a set of photos].)<br />
* 0 (comments) [[User:Tantek|Tantek]] - Update: the syntax still seems a bit loose/imprecise, however, I appreciate the improvements being made. Some additional changes for consideration:<br />
** certainty attribute, empty or missing is equivalent to "0" (absolute certainty presumably)<br />
** certainty attribute takes an ISO8601 duration.<br />
** alternatively it might make more sense to introduce a compound time structure for ranges such as the use case example of 2001-2003. Here is a strawman markup example (feel free to pick alternative markup, but re-using nested time elements for portions of a range seem useful)<br />
*** <pre><nowiki><range><time>2001</time>-<time>2003</time></range></nowiki></pre><br />
* +1 [http://listserv.loc.gov/cgi-bin/wa?A2=ind1008&L=datetime&T=0&X=4659876DD4D919D154&Y=andy%40pigsonthewing.org.uk&P=765 Bruce Darcus says]: "[While] I definitely think the use case is important...<br />
**"...I'm of the very strong opinion that an extended data-time format ought to be self-contained, and so not rely on format-specific extensions like X/HTML attributes. One ought to be able to use the same representation in an HTML attribute, or a JSON or RDF value, and losslessly convert among them. For that reason, I very much prefer the current [http://www.loc.gov/standards/datetime/features.html#300 draft idea in EDTF of doing "2000?" or "2000~".]"<br />
* +1 [[User:asbjornu|Asbjørn Ulsberg]] I like the concept, but the syntax should be less verbose and more precise.<br />
** "Circa" can be indicated with a tilde prefix "~"<br />
** Ranges can use [http://en.wikipedia.org/wiki/ISO_8601#Time_intervals ISO-8601 time interval syntax], like "2007/2008" or "2007-2008" which is also allowed (according to section 4.4.2).<br />
* 0 [[User:itpastorn|Lars Gunther]] One of the benefits of the time element is machine parsability. I can't see what benefit it adds for non-parsable text. There are bigger fish to fry.<br />
**The proposal is to make such dates machine parsable. [[User:Pigsonthewing|Pigsonthewing]] 09:54, 17 August 2010 (UTC)<br />
* -1 [[User:Ocolon|Martin Janecke]] - I don't object to the idea of fuzzy dates in general (a well defined certainty attribute sounds interesting) but this doesn't seem to be well thought through yet. E.g. "bronze age" rather defines a stage of development of a culture than a time, just as "adolescence" does for a human. The time element could be suitable for adding markup to the term "bronze age" in a text talking about a specific culture. But you would really add markup to the term, not use this term as time markup, exactly because "bronze age" does not tell a time. Please don't make the time element too unspecific as I am afraid this would reduce its usability rather than adding to it. [[User:Ocolon|Ocolon]] 12:54, 22 August 2010 (UTC)<br />
**It is not proposed to define terms like "bronze age" here; but to cater for a) any definitions emerging from the EDTF efforts and/or b) a publisher using their own definition, such as, say <code><time datetime="[3300-1200 BC]">Bronze age</time></code>. It's not that "this isn't well thought through" so much as "this is brought here for the community to think through". [[User:Pigsonthewing|Pigsonthewing]] 22:34, 22 August 2010 (UTC)<br />
*** I wrote "this doesn't seem to be well thought through '''yet'''", of course implying this can change. Thanks for the details on the "bronze age" example. Should the introduction sentence to the [http://wiki.whatwg.org/index.php?title=Time_element&oldid=5419#Fuzzy_dates fuzzy date section] be edited to reflect this? Currently it does propose "bronze age" etc. as examples for future time values. [[User:Ocolon|Ocolon]] 01:17, 23 August 2010 (UTC)<br />
****Done. [[User:Pigsonthewing|Pigsonthewing]] 11:24, 23 August 2010 (UTC)<br />
* ...<br />
</div><br />
<br />
== Calendar scale ==<br />
The time element should accept a calendar scale (CALSCALE; default is GREGORIAN) per (and to facilitate interoperability with) the [http://tools.ietf.org/html/draft-ietf-vcarddav-vcardrev-11#section-5.7 emergent vCard 4 specification], to allow for the the mark-up of non-Gregorian (e.g. Julian) dates, using one of a set of pre-defined CALSCALE types.<br />
<br />
=== Calendar scale example ===<br />
Example:<br />
<br />
<pre><nowiki><time datetime="1330-06-01" calscale="julian">1 June 1330</time></nowiki></pre><br />
<br />
=== Calendar scale processing ===<br />
User agents could be instructed to ignore any unrecognised CALSCALE value, treating the contents of the element as plain text for data-processing (but not styling) purposes. This would prevent, for example the processing of the above example by an agent written to deal only with Gregorian dates. (At some point, CSS should recognise CALSCALE, allowing authors to, say, style all Julian dates differently to Gregorian dates.)<br />
<br />
=== Calendar scale use cases ===<br />
Use case research:<br />
* The Wikipedia timeline example in [http://www.zeldman.com/superfriends/guide/#time HTML5 Super Friends Technical Details: time element] proposes to map a timeline of dates from Wikipedia (e.g. 2001-2003 Gregorian). However, Wikipedia includes several thousand articles about or referring to <em>pre</em>-Gregorian era events, usually using the Julian calendar, such as the birth and death of [http://en.wikipedia.org/wiki/Julius_ceasar Julius Ceaser] and, in the same article, the Ides of March (15 March) 44 BC. The existing timeline implementation (see [http://en.wikipedia.org/w/index.php?title=Bob_Brettle&oldid=376645341#External_links] - target site currently broken, but worked previously; a fix is promised shortly) can only map Wikipedia's Gregorian dates, because there is currently no way to mark up Julian dates in a machine-readable format. The use of CALSCALE as suggested would allow this implementation and others to map all of these dates. (Note that the implementation works with any site, not just Wikipedia, parsing hCalendar microformats.)<br />
* Julian dates in [http://ourgeorgiahistory.com/year/1577 timeline of Georgia]: <br />
* General: non-Gregorian dates are published in documents about museum artifacts, history, archaeology, genealogy etc. and in archives of historic documents.<br />
* See also various use cases under [[#Fuzzy dates]], above for eras pre-dating the Gregorian calendar<br />
<br />
=== Calendar scale discussion ===<br />
<div class="discussion"><br />
Opinions / discussion:<br />
* +1 [[User:Pigsonthewing|Andy Mabbett]] (Per use cases in VCARDDAV, EDTF & TEI - see external links)<br />
* 0 [[User:Tantek|Tantek]] - Update: I have mixed feelings about this. On one hand, despite years of the presence of the CALSCALE feature in iCalendar etc., there are no implementations (AFAIK) of non-GREGORIAN CALSCALE values in iCalendar etc. user agents, thus there is no reason to believe that specifying it in HTML5 would actually encourage any other user agents to implement it either. On the other hand the Wikipedia long-term timeline use case <em>does</em> appeal to me so overall I've upgraded my opinion on this from -1 to 0 neutral.<br />
* 0 [[User:Ocolon|Martin Janecke]] - I'm afraid the current proposal is too "Western World" centered. If you plan to allow Julian and Gregorian dates – what about the Islamic, Chinese, Hebrew, …, Mesopotamian and Mayan calenders? I don't mean to say we mustn't incorporate other calender scales – but if we do, we'll probably have to implement all of them, making things easier in some and much more complicated in many aspects. This could result in many parsers not being able to understand many of the dates, making the time element less useful. I'd rather use just one scale as it is in the spec right now. The Gregorian calender is an international standard, so it should be fine. But I don't know if it is right to expect others to use "my" calendar (which the Gregorian calender is), hence the neutral vote.<br />
**Dates from 2000+ years ago in non-European calendars such as those you mention can be converted to Julian calendar dates (but not Gregorian dates), just as modern dates in those calendars can be converted to the Gregorian calendar. The use of Julian extends the range of dates which can be expressed. [[User:Pigsonthewing|Pigsonthewing]] 22:40, 22 August 2010 (UTC)<br />
* …<br />
</div><br />
<br />
=== Calendar scale related posts ===<br />
Related posts (listed with quotes directly related to Calendar scale) :<br />
* [http://pigsonthewing.org.uk/dates-and-coordinates-in-html5/ 2009-02-23 Dates and coordinates in HTML5] blog post by Andy Mabbett - <blockquote cite="http://pigsonthewing.org.uk/dates-and-coordinates-in-html5/">The issue of non-Gregorian (chiefly Julian) dates is a vexing one; and has already caused problems on Wikipedia. So far as I am aware, there is no ISO-, RFC- or similar standard for such dates, other than converting them to Gregorian dates. It is not the job of the HTML5 working group to solve this problem; but I think the group should recognise that at some point a solution must be forthcoming. One way to do so would be allow something like [(refers to prototype CALSCALE)] where the schema defaults to ISO 8601 if not stated, and the whole element is treated as simply [date in plain text] if the schema is unrecognised; thereby ensuring backwards compatibility. That way, if a hypothetical ISO- or other standard for Julian dates emerges in the future, authors may simply start to use it without any revision to HTML 5 being required.</blockquote><br />
* [http://www.brucelawson.co.uk/2009/html-5-politics-and-me/ 2009-02-25 HTML 5, politics and me] blog post by Bruce Lawson - look for mention of "time element" which mentions: <blockquote cite="http://www.brucelawson.co.uk/2009/html-5-politics-and-me/">I see no reason why authors shouldn’t be able to mark up BCE dates... which are currently disallowed by the spec</blockquote> BCE dates are typically in the Julian (or other?) calendar and thus a request for BCE dates markup implies something at least like Calendar scale<br />
* [http://html5doctor.com/the-time-element/ 2010-02-09 The time element (and microformats)] blog post on HTML5 Doctor by Bruce Lawson - mentions: <blockquote>The only trouble with &lt;time&gt; is that the it must contain positive date on the Proleptic Gregorian calendar, meaning you can’t encode a date before the Christian Era.</blockquote> Again, seemingly implying a desire for non-Gregorian calendars as well.<br />
<br />
= Syntax improvements for reducing DRY violations =<br />
<br />
We know from experience with past methods of duplicated invisible (meta)data, and more recently, development/use/experience with visible microformats, that when we are able to re-use the visible data, published *once*, by humans for humans, we get more accurate data over time, than when we have at times asked for *duplicating* the data in a different (more machine readable) format (or location).<br />
<br />
This experience yielded the microformats adoption of the DRY principle - '''D'''on't '''R'''epeat '''Y'''ourself - in application to (meta)dataformat designs and techniques.<br />
<br />
<br />
The &lt;time&gt; element currently encourages DRY violations in most of its use cases (duplication of datetime information inside the 'datetime' attribute in addition to the visible content of the element). This duplication can result in inaccurate data (e.g. [http://microformats.org/discuss/mail/microformats-dev/2010-August/000663.html]).<br />
<br />
This is not a new problem, we've had much the same DRY problem in microformats representations of dates and times, originally with (excessive and in many cases inaccessible) use of the &lt;abbr&gt; element.<br />
<br />
Subsequently (through years of debate, experimentation, iteration) we've largely addressed both most of the DRY violations (or greatly mitigated their impact) and resolved accessibility related &lt;abbr&gt; problems with the introduction and successful adoption of the Value Class Pattern (developed in parallel with the time element, and not surprisingly with some newer improvements).<br />
<br />
http://microformats.org/wiki/value-class-pattern#Date_and_time_values<br />
<br />
We'd like to see the lessons learned (and improvements made as a result of the value class pattern) adopted in HTML5 as well, for much the same reasons, to make the HTML5 &lt;time&gt; element the best and most long term accurate way to represent all date and time information in microformats (or microdata for that matter).<br />
<br />
Accordingly, please consider the following &lt;time&gt; syntax processing improvements for better DRY (and mitigation) and thus more accurate data over time.<br />
<br />
<br />
== composite nested time elements ==<br />
A time element should permit child time elements which may contain only partial date time information which can then be composed into more complete date time information.<br />
<br />
This is intended as a cleaner way to provide functionality equivalent to the microformats [http://microformats.org/wiki/value-class-pattern#Date_and_time_values value-class-pattern date and time values pattern].<br />
<br />
In short, instead of this (actual example derived from markup of blog post [http://adactio.com/journal/1632/ HTML5 watch by Jeremy Keith])<br />
<br />
<pre><nowiki><br />
<time class="published" datetime="2009-12-13T17:43:29"><br />
Sunday, December 13th, 2009<br />
5:43pm<br />
</time><br />
</nowiki></pre><br />
<br />
We want to be able to do this:<br />
<br />
<pre style="background:#efe"><nowiki><br />
<time class="published"><br />
<time datetime="2009-12-13">Sunday, December 13th, 2009</time> <br />
<time datetime="17:43:29">5:43pm</time><br />
</time><br />
</nowiki></pre><br />
<br />
and have the parent &lt;time&gt; element composite a complete datetime from the child &lt;time&gt; elements with separate date and time.<br />
<br />
The <em>separate</em> date and time <code>datetime</code> attribute values are more readable (per accessibility research etc.), and thus more easily human verifiable as being the "same" value as the in-content text, thus resulting in incrementally more accurate data over time.<br />
<br />
This type of date and time compositing as spec'd in the Value Class Pattern has been interoperably implemented and shipped (Operator, X2V). Thus we think it is reasonable to add this similar feature to HTML5.<br />
<br />
=== background ===<br />
Currently the &lt;time&gt; element forces you to duplicate and hide date time information if you want to avoid displaying the not-very-friendly full ISO datetime:<br />
<br />
<pre><nowiki><br />
<p class="vevent"><br />
<span class="summary">I went to the cafe</span> at <br />
<time class="dtstart"<br />
datetime="2010-08-05T18:00:00">18:00 on 2010-08-05</time>.<br />
</p><br />
</nowiki></pre><br />
<br />
Note the date and time information is duplicated (violating DRY, placing the content at risk of divergence).<br />
<br />
=== microformats value class pattern DRY advantage ===<br />
With the microformats value-class-pattern date and time values pattern you could instead mark this up like this:<br />
<br />
<pre><nowiki><br />
<p class="vevent"><br />
<span class="summary">I went to the cafe</span> at <br />
<span class="dtstart"><br />
<span class="value">18:00</span> on <br />
<span class="value">2010-08-05</span><br />
</span>.<br />
</p><br />
</nowiki></pre><br />
<br />
Advantages: no duplication of time and date data! (avoiding DRY violation) If you need to update the info, you only have to update it in one place, thus reducing the chances of inforot.<br />
<br />
Disadvantage: the loss of the HTML5 time semantic and related processing.<br />
<br />
=== simple nested time example improvement ===<br />
We'd like to have our <code>&lt;time&gt;</code> and date time separation as well, so this should work:<br />
<br />
<pre><nowiki><br />
<p class="vevent"><br />
<span class="summary">I went to the cafe</span> at <br />
<time class="dtstart"><br />
<time>18:00</time> on <br />
<time>2010-08-05</time><br />
</time>.<br />
</p><br />
</nowiki></pre><br />
<br />
=== summary of updated datetime algorithm ===<br />
In short: the algorithm for determining the "datetime" of a time element should:<br />
# check for an explicit 'datetime' attribute (allowing a local to element override regardless of child elements)<br />
# check for nested &lt;time&gt; elements, and if any are found, compose their values into a more complete date and time (use the first date found if any, then the first time found, if any. thus latter dates or times are gracefully ignored)<br />
# use the complete contents of the &lt;time&gt; element as its datetime value.<br />
<br />
Essentially, step 2 is added to enable composing nested child time elements.<br />
<br />
=== applicability to microdata ===<br />
All of the aforementioned advantages for microformats apply to microdata use of the &lt;time&gt; element as well. microformats are used in the above examples as that is the type of content (including the value class pattern) that is being published today (e.g. see http://microformats.org/wiki/events - the markup on that page itself).<br />
<br />
=== nested time example with datetime attribute ===<br />
If the publisher prefers to publish a "localized" form of dates (rather than the previous simple example with the most overall internationally human-friendly/readable YYYY-MM-DD ISODate), they can still do so:<br />
<br />
<pre><nowiki><br />
<p class="vevent"><br />
<span class="summary">I went to the cafe</span> at <br />
<time class="dtstart"><br />
<time>18:00</time> on <br />
<time datetime="2010-08-05">August 5th, 2010</time><br />
</time>.<br />
</p><br />
</nowiki></pre><br />
<br />
Advantage: The advantage here over the current time element is that the DRY violation is <em>limited</em> to only the date information (instead of date <em>and time</em> information), thus reducing the risk of data divergence due to duplication.<br />
<br />
=== nested time example with two datetimes ===<br />
If the publisher prefers to publish a "localized" form of times, they can do that as well:<br />
<br />
<pre><nowiki><br />
<p class="vevent"><br />
<span class="summary">I went to the cafe</span> at <br />
<time class="dtstart"><br />
<time datetime="18:00:00">6pm</time> on <br />
<time datetime="2010-08-05">August 5th, 2010</time><br />
</time>.<br />
</p><br />
</nowiki></pre><br />
<br />
Advantage: The two separate <code>datetime</code> attributes (containing just the time and just the date) are <em>more</em> human-readable than a single datetime attribute containing both, and thus there is a slightly better chance that the few humans that check would correctly determine whether the times and dates in the datetime attributes represent the same value as the content of the element.<br />
<br />
The AM/PM proposal below further helps improve this example.<br />
<br />
=== nested time discussion ===<br />
<div class="discussion"><br />
Opinions / discussion:<br />
* +1 [[Tantek]] - I'd really like to be able to more cleanly markup dates and times than the best we have been able to do so far with microformats (the aforementioned value-class-pattern), and HTML5 presents us with the potential to do so.<br />
* -1 [[User:Pigsonthewing|Andy Mabbett]] - Introduces excessive complexity on the apparent assumption that a significant proportion of dates in the wild (or even in microformats in the wild) use the format "2010-08-05" and not more human-readable and accessible prose such as, say, "5 August 2010" or "August 5th, 2010". No evidence (also supposedly required by the microformats "process") has been provided to show that this is the case. {If the apparent assumption is not made, then this fails 80/20.) '''Update''': Subsequent changes have addressed some of my concerns. The proposal to separate times from dates ''with datetime attributes'' is a better one. However, we still lack supporting evidence and I object to any wording in the spec which perpetuates the myth that YYYY-MM-DD dates are in any way "human-friendly/readable" compared to prose dates: "international" readability is irrelevant, when pages are otherwise in one language or another.<br />
* +1 [[User:asbjornu|Asbjørn Ulsberg]] - With nesting (and [http://en.wikipedia.org/wiki/ISO_8601#Time_intervals ISO-8601 time intervals]), the hCalendar example can be made more precise and less verbose like so:<br />
<pre><nowiki><br />
<div class="vevent"><br />
<a class="url" href="http://www.web2con.com/">http://www.web2con.com/</a><br />
<span class="summary">Web 2.0 Conference</span>: <br />
<time datetime="2005-10-05/2005-10-07"><br />
<time class="dtstart">October 5</time>-<br />
<time class="dtend">7</time><br />
</time>, at the <span class="location">Argent Hotel, San Francisco, CA</span><br />
</div></nowiki></pre><br />
** Appreciate the support of the proposal. To clarify, the modified markup example provided won't work as microformats processors will look for "dtstart" information only inside that time element and its children, and find an English abbreviation, or just a number without context in the case of "dtend". This modification also moves the duplicate ISO8601 machine date data <em>farther</em> from the individual human readable components which increases the chance of drift (more distance between data duplicates = more drift between the duplicates over time). [[User:Tantek|Tantek]] 19:39, 11 August 2010 (UTC)<br />
* ...<br />
</div><br />
<br />
== am pm and coarser time parsing ==<br />
Right now time values inside a &lt;time&gt; element are required to specify hours in 24 hour time. We want the time element to accept am/pm times as well.<br />
<br />
In short, instead of this (actual example derived from markup of blog post [http://adactio.com/journal/1632/ HTML5 watch by Jeremy Keith], with nested time elements per previous proposal)<br />
<br />
<pre><nowiki><br />
<time class="published"><br />
<time datetime="2009-12-13">Sunday, December 13th, 2009</time> <br />
<time datetime="17:43:29">5:43pm</time><br />
</time><br />
</nowiki></pre><br />
<br />
We want to be able to do this:<br />
<br />
<pre style="background:#efe"><nowiki><br />
<time class="published"><br />
<time datetime="2009-12-13">Sunday, December 13th, 2009</time> <br />
<time>5:43pm</time><br />
</time><br />
</nowiki></pre><br />
<br />
It's a minor DRY improvement (time info is no longer duplicated), but one that we think is worth it across the numerous pieces of content authored as such and the resulting increased accuracy from DRY reduction.<br />
<br />
This type of am pm parsing as spec'd in the Value Class Pattern has been interoperably implemented and shipped (Operator, X2V). Thus we think it is reasonable to add this similar feature to HTML5.<br />
<br />
=== am pm syntax summary ===<br />
<br />
In our experience with the microformats value class pattern date and time values we've found it is relatively easy to both specify and implement (multiple implementations) parsing of (potentially coarser) am and pm values to permit a broader set of values to marked up directly (rather than with a separate datetime/title attribute).<br />
<br />
In short, the current &lt;time&gt; element only allows for the following time syntax:<br />
<br />
* HH:MM:SS - where HH is in 24 hour time.<br />
<br />
This proposal expands the allowed time syntax to:<br />
<br />
* HH:MM:SSam<br />
* HH:MM:SSpm<br />
* HH:MMam<br />
* HH:MMpm<br />
* HHam<br />
* HHpm<br />
<br />
=== am pm syntax details ===<br />
* '''periods, white-space, case-insensitivity.''' "am" and "pm" mean "am or a.m." and "pm or p.m." with optional leading ("6 pm") and intermittent ("6 p. m.") white-space; and are case-insensitive ("6 PM").<br />
* '''implied 00 minutes and seconds.''' When :SS or :MM:SS is omitted, infer :00 or :00:00, respectively.;<br />
* '''handling of 12am and 12pm.''' "12am" is treated as "00:00:00" (midnight at the start of the day). "12pm" is treated as "12:00:00" (noon).<br />
<br />
=== simple am pm example ===<br />
A simple example:<br />
<br />
<pre><nowiki><br />
I went to the cafe at <time>6pm</time>.<br />
</nowiki></pre><br />
<br />
Advantage: by specifying am and pm times that can be parsed directly from the contents of the <time> element, we reduce the need to violate DRY (can omit an explicit datetime attribute) in more cases, and thus encourage higher fidelity time data over time.<br />
<br />
=== am pm example with nested time elements ===<br />
Example (uses aforementioned composite nested time element proposal as well)<br />
<br />
<pre><nowiki><br />
<p class="vevent"><br />
<span class="summary">I went to the cafe</span> at <br />
<time class="dtstart"><br />
<time>6pm</time> on <br />
<time>2010-08-05</time><br />
</time>.<br />
</p><br />
</nowiki></pre><br />
<br />
Advantage: again, this reduces DRY violations, in this case further improving upon the composite nested time elements case.<br />
<br />
=== am pm discussion ===<br />
<div class="discussion"><br />
Opinions / discussion:<br />
* +1 [[Tantek]] - in practice we in the microformats community have found that enabling users to markup am/pm times leads to many more cases where we can avoid violating DRY and thus encourage greater accuracy over time for such content. I think the HTML5 &lt;time&gt; element presents us with the opportunity to more cleanly markup times (than what we've been able to do with the aforementioned microformats value-class-pattern), and thus we should do so.<br />
* 0(query) [[User:Pigsonthewing|Andy Mabbett]] - see above for concerns over date formatting.<br />
** queries moved to am pm FAQ section with answers. - [[User:Tantek|Tantek]] 16:57, 6 August 2010 (UTC)<br />
* ...<br />
</div><br />
<br />
=== am pm FAQ ===<br />
==== noon and midnight ====<br />
'''Question:''' How does this cater for "noon" and "midnight", and the [http://en.wikipedia.org/wiki/12-hour_clock#Confusion_at_noon_and_midnight ambiguity] over "12am" and "12pm"?<br />
<br />
'''Answer:''' This proposal does not address the (English) language specific terms of "noon" and "midnight". Proposal clarified to explicitly treat 12am as 00:00:00, and 12pm as 12:00:00.<br />
<br />
==== am pm i18n ====<br />
'''Question:''' How does this internationalise "am" and "pm", for languages which do not use them? <br />
<br />
'''Answer:''' For languages that do not use "am" or "pm", the am pm proposal does not confer any additional advantage.<br />
<br />
= Minor editorial fixes =<br />
<br />
== Update hCalendar example ==<br />
<br />
Summary: please update the hCalendar example with the following fixes which make it consistent with hCalendar 1.0 with resolved issues.<br />
<br />
=== Current example ===<br />
<br />
The HTML5 spec currently has this hCalendar example:<br />
<br />
<pre><nowiki><br />
<div class="vevent"><br />
<a class="url" href="http://www.web2con.com/">http://www.web2con.com/</a><br />
<span class="summary">Web 2.0 Conference</span>:<br />
<time class="dtstart" datetime="2007-10-05">October 5</time> -<br />
<time class="dtend" datetime="2007-10-20">19</time>,<br />
at the <span class="location">Argent Hotel, San Francisco, CA</span><br />
</div><br />
<br />
(The end date is encoded as one day after the last date of the event because in the iCalendar format, end dates are exclusive, not inclusive.)<br />
</nowiki></pre><br />
<br />
This appears to have been copy/pasted from a past version of the [http://microformats.org/wiki/hcalendar#Examples hCalendar spec] that was both mid-update (the dates are incorrect/inconsistent), and notes an issue which has since been resolved.<br />
<br />
=== Updated example ===<br />
<br />
Here is a suggested update:<br />
<br />
<pre style="background:#efe"><nowiki><br />
<div class="vevent"><br />
<a class="url" href="http://www.web2con.com/">http://www.web2con.com/</a><br />
<span class="summary">Web 2.0 Conference</span>: <br />
<time class="dtstart" datetime="2005-10-05">October 5</time>-<br />
<time class="dtend" datetime="2005-10-07">7</time>,<br />
at the <span class="location">Argent Hotel, San Francisco, CA</span><br />
</div><br />
</nowiki></pre><br />
<br />
The parenthetical paragraph about end date inconsistency has been removed since hCalendar 1.0 has resolved that issue (see [http://microformats.org/wiki/dtend-issue dtend issue] for details).<br />
<br />
= Miscellaneous proposals =<br />
<br />
==Choose different default date==<br />
The statement that valueAsDate IDL attribute should return the value 1970-01-01 plus the appropriate time when the time element contains no date creates a problem that there are likely to be time elements that explicitly contain that date.<br />
<br />
A better choice would be a value that is highly unlikely to be encountered, and would be implausible as an actual date in most applications, perhaps 9999-12-31.<br />
<br />
<div class="discussion"><br />
Opinions / discussion:<br />
* 0 (comment) [[User:Pigsonthewing|Andy Mabbett]] - 9999-12-31 may well occur in real applications (projected comet sightings, say). Can we return either an invalid date (perhaps 9999-02-31) or an error code?<br />
* -1 [[User:Tantek|Tantek]] - I don't see any other default date as being significantly different.<br />
* ...<br />
</div><br />
<br />
= Issues without specific proposals =<br />
==Specification ambiguities==<br />
The specification requires that time be expressed as UTC (or another time zone with a specified offset from UTC). However, the representation of leap seconds is not specified. Further, the algorithms to convert between string and number are flawed, because the number is described as "number of milliseconds elapsed from midnight UTC on the morning of 1970-01-01" but the actual number of milliseconds includes all kinds of strange decisecond offsets during the period 1961-01-01 to 1972-01-01. Also, UTC did not exist before about 1960.<br />
<br />
Unix timekeeping has a long history of terrible definitions, and Unix notions of time should be totally rejected and expunged.<br />
<br />
<br />
= See Also =<br />
* [[input]] - the input element, related proposals expanding upon the new datetime inputs.<br />
<br />
= External links =<br />
<br />
== Tag ==<br />
Blog posts, Twitter updates etc. may be tagged HTML5time or #HTML5time <!-- links to follow --><br />
<br />
== Prior discussion ==<br />
<br />
* [http://pigsonthewing.org.uk/dates-and-coordinates-in-html5/ Dates and coordinates in HTML5] - blog post by [[User:Pigsonthewing|Andy Mabbett]]<br />
** [http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-February/018639.html whatwg mailing list discussion of the above, Feb 2009]<br />
** [http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-March/018685.html further whatwg mailing list discussion of the above, Mar 2009]<br />
** [http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-March/018759.html Another mailing list thread Mar 2009]<br />
** [http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2009-March/018888.html Spec editor's response to the above threads and further discussion, late Mar 2009]<br />
* [http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-November/024184.html 2009-11-26 Use cases for the time element] whatwg email by Jeremy Keith<br />
* [http://html5doctor.com/the-time-element/ HTML5 Doctor: The Time Element]<br />
<br />
== Resources ==<br />
<br />
* [http://www.loc.gov/standards/datetime/ Extended Date Time Format efforts] based at the USA's Library of Congress (Covers unspecific dates; date periods and non-Gregorian dates)<br />
** [http://www.loc.gov/standards/datetime/proposals.html EDTF proposals] (use-cases)<br />
* [http://www.w3.org/TR/NOTE-datetime W3C Date and Time Formats discussion note]<br />
** mailing list was datetime-comments@w3.org. - anyone have archives URL?<br />
* [http://tools.ietf.org/html/draft-ietf-vcarddav-vcardrev-11 vCard Format Specification draft-ietf-vcarddav-vcardrev-11] (latest draft as at July 2010)<br />
** [http://tools.ietf.org/html/draft-ietf-vcarddav-vcardrev-11#section-4.3 Section 4.3, date & time]<br />
** [http://tools.ietf.org/html/draft-ietf-vcarddav-vcardrev-11#section-5.7 Section 5.7, CALSCALE] (specifies Gregorian or other (e.g. Julian) calendar)<br />
*** [http://www.ietf.org/mail-archive/web/vcarddav/current/msg01307.html VCARDDAV discussion of CALSCALE]<br />
* [http://www.tei-c.org/Guidelines/P4/html/ref-DATE.html TEI dates], widely used by archives and libraries to mark up texts, including non-Gregorian ISO8601 & uncertain/ approximate dates<br />
** [http://www.tei-c.org/Guidelines/P4/html/CO.html#CONADA TEI dates+times]<br />
* [http://en.wikipedia.org/wiki/ISO_8601 ISO 8601 (Wikipedia article)]<br />
* [http://en.wikipedia.org/wiki/Proleptic_Gregorian_calendar Proleptic Gregorian calendar (Wikipedia article)]<br />
* Dublin Core terms, e.g. <br />
**<code>dcterms:temporal</code> at http://dublincore.org/groups/collections/collection-application-profile/#coldctermstemporal<br />
*** [http://www.nmm.ac.uk/collections/feeds/docs/ example using dcterms:temporal]<br />
**<code>dcterms:created</code> http://dublincore.org/groups/collections/collection-application-profile/#coldctermsdcterms:created<br />
* [http://www.w3.org/TR/owl-time/ Time Ontology in OWL]<br />
** [http://www.semanticoverflow.com/questions/836/use-a-custom-datatype-or-a-property-for-approximate-dates Use a custom datatype or a property for approximate dates?] - discussion of the above.</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Summary_element&diff=5356Summary element2010-08-14T04:05:51Z<p>TheresaOConnor: -0</p>
<hr />
<div>{{stub}}<br />
<br />
The <code>&lt;summary&gt;</code> element is a new element in HTML5, a child of the new <code>&lt;[[details]]&gt;</code> element.<br />
<br />
{{For|the summary attribute|Table Summary}}<br />
<br />
== summary naming or flexibility ==<br />
<br />
Currently the <code>&lt;summary&gt;</code> element is a special element specifically for use for the label inside the <code>&lt;details&gt;</code> element.<br />
<br />
The name of the <code>&lt;summary&gt;</code> element however is too generic sounding of an element name for this special usage. <br />
<br />
It is inevitable that people will begin using the <code>&lt;summary&gt;</code> element when they simply mean a semantic "summary", perhaps of a <code>&lt;section&gt;</code> or <code>&lt;article&gt;</code>.<br />
<br />
I say inevitable due to the broad evidence presented by the known existing problem with the <code>&lt;address&gt;</code> element (special use - for contact information for the document, but used and often errantly taught as a generic "address" for street addresses).<br />
<br />
Thus we should <em>either</em>:<br />
<br />
# '''Rename the details <code>&lt;summary&gt;</code>''' to something more specific (suggestions welcome), <em>OR</em>:<br />
# '''Alternatively make the <code>&lt;summary&gt;</code> element generic.''' Make it an actual summary inside <code>&lt;article&gt;</code> or <code>&lt;body&gt;</code>, as well as inside <code>&lt;details&gt;</code>. Allow <code>&lt;summary&gt;</code> anywhere <code>&lt;header&gt;</code> is allowed (basically, make it a part of the new section related elements).<br />
<br />
I prefer the second solution, make the <code>&lt;summary&gt;</code> element more generic/flexible. — [[User:Tantek|Tantek]] 20:38, 3 August 2010 (UTC)<br />
<br />
=== summary flexibility advantages ===<br />
Advantages of making the <code>&lt;summary&gt;</code> element more generic and flexible:<br />
* This is '''close to the semantic of the Atom "summary" element''', and the hAtom microformat 'entry-summary' property.<br />
* This would allow an '''enhancement of the algorithm for converting HTML5 to Atom''': take the first HTML5 <code>&lt;summary&gt;</code> inside an <code>&lt;article&gt;</code> being converted to an entry, and use that HTML5 <code>&lt;summary&gt;</code> as the Atom entry <code>&lt;summary&gt;</code>.<br />
<br />
<br />
<div class="discussion"><br />
Opinions / discussion:<br />
* +1 [[User:Tantek|Tantek]] - I think web authors would make good use of a new generic <code>&lt;summary&gt;</code> element.<br />
* Bruce Lawson: I don't think there's a need for a generic summary element. But I'd support renaming the summary attribute of details (because it doesn't really summarise). Perhaps "rubric" could replace details>summary and figure>figcaption ?<br />
</div><br />
* +1 [http://twitter.com/dalmaer/status/20318049663 Dion Almaer:] <nowiki><figcaption></nowiki> or just reuse <nowiki><summary></nowiki> in more places. I am with @t on that one :)<br />
* -0 [[User:EdwardOConnor|EdwardOConnor]] - I'm OK with the status quo; barring that, I'd prefer renaming <nowiki><summary></nowiki> to more specifically describe its use in <nowiki><details></nowiki>.<br />
* ...</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Iframe_Sandbox&diff=5355Iframe Sandbox2010-08-14T04:04:14Z<p>TheresaOConnor: -1</p>
<hr />
<div>{{stub}}<br />
<br />
= iframe sandbox attribute =<br />
<br />
This page is for collecting issues and proposals related to the new <code>&lt;iframe&gt;</code> <code>sandbox</code> attribute.<br />
<br />
== proposal drop sandbox attribute ==<br />
<br />
The new 'sandbox' feature on <code>&lt;iframe&gt;</code> should be considered for removal.<br />
<br />
In speaking with fellow developers at Mozilla, I've collected the following feedback:<br />
<br />
* The sandbox feature and functionality needs a thorough security review.<br />
* It will be a lot of work to implement properly.<br />
* It may not actually solve the problem it is intending to solve.<br />
<br />
— [[User:Tantek|Tantek]] 01:56, 2 August 2010 (UTC)<br />
<br />
=== opinions and discussion ===<br />
* +1 [[User:Tantek|Tantek Çelik]]<br />
* -1 [http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027484.html Ian Fette]<br />
* -1 [http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027485.html Adam Barth]<br />
* -1 [http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027491.html Maciej Stachowiak]<br />
* -1 [[User:EdwardOConnor|EdwardOConnor]] - While I'm put off by the syntax (markup in attribute values looks quite gross), I think the feature is needed and the design certainly meets the need.<br />
* ...<br />
<br />
== why sandbox should be kept ==<br />
=== implementation experience ===<br />
[http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027491.html Per Maciej], support for the new 'sandbox' feature on <code>&lt;iframe&gt;</code> is "shipping in current versions of Safari and Chrome."<br />
<br />
The initial patch implementing it for WebKit can be seen here: http://trac.webkit.org/changeset/51577. <br />
<br />
This patch was 100k, but more than half of it is tests and the ChangeLog entry.<br />
<br />
=== security ===<br />
"There's been a lot of security review, both on this list and in the W3C HTML WG. I've been meaning to write up a summary of all the discussion, but I haven't gotten around to it yet. We ended up tweaking a few aspects, but generally the design seems solid." — [http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027485.html Adam Barth 2010-08-01]<br />
<br />
Also [http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027491.html from Maciej]:<br />
Security experts have reviewed it (which security experts? links?). 'sandbox' itself seems pretty solid, although there are possibly issues with related features such as text/html-sandboxed and 'seamless' attribute.<br />
<br />
While more security review is always welcome, it seems like the basic idea is solid, and it's demonstrably implementable. <br />
<br />
=== examples in the wild ===<br />
[http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027491.html Per Maciej], Content has been built using it.<br />
<br />
Which content? URLs to examples in the wild?<br />
<br />
=== use cases ===<br />
[http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2010-August/027491.html Per Maciej], while it's unclear if &lt;iframe sandbox&gt; will work well for comments or other such cases of seamless untrusted content, it seems clearly useful for use cases like:<br />
* gadgets<br />
* ads<br />
<br />
Examples? Could someone provide code examples of how &lt;iframe sandbox&gt; could be used for gadgets or ads or other use cases?</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Del_element&diff=5354Del element2010-08-14T04:02:38Z<p>TheresaOConnor: added my +1s</p>
<hr />
<div>Research, data, use cases, issues, and enhancements related to the [http://www.w3.org/TR/html5/edits.html#the-del-element HTML5 <code>del</code> element]. <br />
<br />
== datetime attribute ==<br />
The <code>del</code> element has a <code>datetime</code> attribute that requires an explicit date and time.<br />
<br />
=== dates without times ===<br />
Summary: the <code>datetime</code> attribute (on both del and ins elements) should permit just a date value, in addition to permitting explicit dates with times.<br />
<br />
;ISO8601 syntax<br />
:YYYY-MM-DD<br />
<br />
Currently the <code>datetime</code> attribute requires <em>both</em> a date and a time.<br />
<br />
On the other hand, the [[time]] element's datetime attribute allows just a date.<br />
<br />
Allowing just a date has the following advantages:<br />
# easier for hand-authoring (per the preferring authors principle of the HTML5 design principles). Authors can more easily add ins/del elements with explicit datetime attributes if they are permitted to specify only the date (they might not know or care about the precise time), e.g. in blog posts that are updated by the author.<br />
# avoids artificial precision. Forcing an explicit date and time forces authors to enter artificial precision (e.g. YYYY-MM-DDT00:00:00Z instead of YYYY-MM-DD). Allowing just dates permits authors to convey that a del/ins occurred on a certain day, and that the precise time is unknown or irrelevant.<br />
<br />
Example:<br />
<pre><nowiki><br />
<p>Here is a paragraph of text with some important information.<br />
<del datetime="2010-07-29">That was rushed out hurriedly.</del><br />
<ins datetime="2010-07-29">Update: here is some new information</ins><br />
</p><br />
</nowiki></pre><br />
<br />
Opinions / discussion: <br />
* +1 [[User:Tantek|Tantek Çelik]] - this happens to me often when I have blog-like or other essay content that I update by hand. Since I typically do updates to any particular content about once a day, day-level granularity is sufficient. Picking an arbitrary time seems like being forced to provide "fake" metadata which I don't want to do.<br />
* +1 [[User:EdwardOConnor|EdwardOConnor]] - I have the same sort of experience as Tantek in this case; confabulating precision where none exists feels quite wrong.<br />
<br />
=== timeref ===<br />
Summary: add a new <code>timeref</code> attribute (of type <code>idref</code>) that can be used to reference the <code>id</code> of a local to document <code>&lt;time&gt;</code> element which is then used as the <code>datetime</code> value of when the deletion or insertion occurred.<br />
<br />
Example:<br />
<pre><nowiki><br />
<p>Here is a paragraph of text with some important information.<br />
<del timeref="change1">That was rushed out hurriedly.</del><br />
<ins timeref="change1">Update <br />
<time id="change1">2010-07-29</time>: <br />
Here is some new information</ins><br />
</p><br />
</nowiki></pre><br />
<br />
Advantages:<br />
* <strong>visible metadata!</strong> the date of the change can be shown visibly (as many real world examples do (citations needed), rather than invisibly in a hidden datetime attribute, which encourages higher fidelity metadata.<br />
* <strong>DRY! (don't repeat yourself).</strong> compare the previous example to the timeref one - the timeref example provides the date only <em>once</em> instead of duplicating it. Whenever multiple del/ins edits occur at the same date/time they can all reference a single <code>&lt;time&gt</code> element.<br />
<br />
Opinions / discussion: <br />
* +1 [[User:Tantek|Tantek Çelik]]<br />
* +1 [[User:EdwardOConnor|EdwardOConnor]] - This would be great for blog post authoring.</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Implementations_in_Web_browsers&diff=5275Implementations in Web browsers2010-08-09T15:37:40Z<p>TheresaOConnor: Reverted edits by Robbar (talk) to last revision by Annevk</p>
<hr />
<div>This is a list of known implementations of HTML5 and related features in web browsers. (It is incomplete, feel free to fix it.)<br />
<br />
==HTML5==<br />
<br />
===General===<br />
<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#the-canvas canvas]''' with some limitation implemented in Firefox, Opera, Safari, and Konqueror 4, with [http://excanvas.sourceforge.net/ ExplorerCanvas] emulated in Internet Explorer<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#getelementsbyclassname getElementsByClassName]''' implemented in Firefox 3, Safari 3.1, Opera 9.5<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#storage localStorage and sessionStorage]''' implemented in Firefox 2, IE 8, Safari 4<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#sql Database storage]'''implemented in Safari 3.1 and iPhone Safari 2.0<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#custom-handlers Custom content handlers]''' partially implemented in Firefox 2<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#ping ping attribute]''' implemented in Firefox 3 ([https://bugzilla.mozilla.org/show_bug.cgi?id=415168 turned off by default]) - note the implementation does not reflect the latest changes in the specification<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#crossDocumentMessages cross-document messaging]''' implemented in Opera 9, Safari and Firefox 3, IE 8<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#sound Audio interface]''' implemented in Opera 9, Konqueror 4, Safari 3.1<br />
* ''' [http://www.whatwg.org/specs/web-apps/current-work/multipage/section-video.html#video video element]''' implemented in Safari 3.1 and Firefox 3.1 alfa 2, basic implementation in [http://people.opera.com/howcome/2007/video/ experimental Opera build]; with [http://metavid.ucsc.edu/blog/2007/06/07/html5-video-the-future-is-now/ mv_embed script] in every browser with Java support <br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#server-sent-events Server-sent DOM events]''' implemented in Opera 9<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#contenteditable contenteditable attribute]''' implemented by Opera, Internet Explorer, Safari and Firefox 3<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#dnd Drag & drop]''' (partially) implemented in Internet Explorer, Safari and Firefox nightly builds.<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#the-end event DOMContentLoaded]''' implemented in Firefox, Safari, Opera<br />
* '''[http://www.whatwg.org/specs/web-workers/current-work/ Web Workers]''' partly implemented in Firefox 3.1 alfa 2<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#offline Offline Web applications]''' implemented in Chrome (via Gears plugin), Safari 4, iPhone Safari 2.1 and Firefox 3.1<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#mathml inline MathML]''' implemented in Firefox, partially in Opera (xhtml5 serialization only)<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#svg inline SVG]''' partially implemented in Firefox, Safari, Opera (xhtml5 serialization only)<br />
<br />
====Emulation====<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#the-localstorage localStorage]''' [http://translate.google.com/translate?u=http%3A%2F%2Fd.hatena.ne.jp%2FZIGOROu%2F20080924%2F1222221363&hl=ja&ie=UTF-8&sl=ja&tl=en emulation for IE6 and IE7]<br />
<br />
* '''[http://dev.w3.org/html5/webstorage/ LocalStorage], [http://dev.w3.org/html5/webdatabase/ Web Database] and [http://www.w3.org/TR/geolocation-API/ Geolocation API]''' [http://translate.google.com/translate?hl=en&sl=ja&tl=en&u=http%3A%2F%2Fcode.google.com%2Fp%2Fgear5%2Fwiki%2FUsingGear5_ja emulated using Gears]<br />
<br />
* '''[http://www.whatwg.org/specs/web-workers/current-work/ Web Workers]''' [http://translate.google.com/translate?prev=hp&hl=en&js=y&u=http%3A%2F%2Fcode.google.com%2Fp%2Ffakeworker-js%2Fwiki%2FOverviewAndUsage_ja&sl=ja&tl=en&history_state0= partly implemented using eval() and setTimeout()]<br />
<br />
* '''[http://www.whatwg.org/specs/web-apps/current-work/#outlines The outline algorithm]''' [http://d.hatena.ne.jp/amachang/20090915/1252999677 JavaScript implementation]<br />
<br />
<br />
===Web Forms 2.0===<br />
<br />
* Opera 9 fully implemented [http://www.whatwg.org/wf2 Web Forms 2].<br />
* Firefox 2 implemented '''[http://www.whatwg.org/specs/web-forms/current-work/#the-change input event]''' (there is still [https://bugzilla.mozilla.org/show_bug.cgi?id=195696 bug #195696])<br />
* List of future Firefox [https://wiki.mozilla.org/User:Mounir.lamouri/HTML5_Forms implementation tracking bugs]<br />
<br />
====Emulation====<br />
<br />
* Project '''[http://code.google.com/p/webforms2/ webforms2]''' emulates a big part of WF2 in every browser<br />
* '''date input element''' with [http://code.google.com/p/input-type-date/ input-type-date] works in Firefox, IE6/7, Safari<br />
* '''Repetition Model''' (dropped from the spec) - Opera 9 (native), with [http://code.google.com/p/repetitionmodel/ repetitionmodel] works in Firefox, IE6/7, Safari 2.0.4<br />
* Project [http://sourceforge.net/projects/wf2/] emulate in IE6/7 validation, date and time types, range, repetition, calculated fields, datalist, autofocus.<br />
<br />
==Web Sockets==<br />
<br />
* Chrome dev channel (4.0.238.0 or later) implemented [http://dev.w3.org/html5/websockets/ WebSocket].<br />
* There is work ongoing to implement this for [https://bugzilla.mozilla.org/show_bug.cgi?id=472529 Firefox] and Safari/WebKit.<br />
* [http://code.google.com/p/pywebsocket pywebsocket] implemented server side.<br />
* [http://jwebsocket.org jWebSocket] High Speed Java WebSocket Server including JavaScript/HTML5 WebSocket Client<br />
<br />
== See also ==<br />
* [http://en.wikipedia.org/wiki/Comparison_of_layout_engines_(HTML5) Comparison of layout engines (HTML5)] on Wikipedia.<br />
* [http://a.deveria.com/caniuse/ An interactive view of features and which browsers they work in]<br />
* [http://people.w3.org/mike/html5/implementations.txt Mike Smith's notes]<br />
<br />
[[Category:Implementations]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Talk:Reviewing&diff=5105Talk:Reviewing2010-07-26T15:21:01Z<p>TheresaOConnor: reverting spam</p>
<hr />
<div>Suggest a new tag:<br />
<do_not_reformat_source><br />
</do_not_reformat_source><br />
To provide a standardize way to tell tools like html tidy that the code in that section should not be reformatted without an explicit override. It would do nothing in the browser. Some markup is best left as is. For example, tables, embedded structured data, etc.<br />
<br />
[[User:Whitis|Whitis]] 21:51, 6 May 2009 (UTC)<br />
<br />
I would recommend asking the developers of the tools you use (e.g. tidy) to support a "class" value that would do this, that way it can work even with HTML4 documents, no need to add an element or anything. [[User:Hixie|Hixie]] 21:55, 6 May 2009 (UTC) <br />
<br />
No good. That would be specific to individual tools. There needs to be a standard used by all tools. If you want to<br />
include a standard class instead of a tag, that is fine. But it should be mentioned in the markup spec as that is one <br />
document that all the the tool developers will read. This does fall within the domain of the spec, just as providing<br />
print media support, handicapped support, etc. View source (or edit) is another presentation.<br />
<div class="do_not_reformat_source">...</div><br />
Consider this a source code accessibility issue. [[User:Whitis|Whitis]] 07:25, 7 May 2009 (UTC)<br />
<br />
<br />
4.11.2 datagrid element/folds/tabs<br />
Note: this comment and the ones which follow evolved as they were written. Some evolved with parts moving from tags to attributes or to CSS. Some evolved with new names based on finding existing precedent. Some of the changes were backpatched into the text, but not all.<br />
<br />
There should also be a <fold> tag (or equivalent functionality) that is very similar but less table/list oriented.<br />
<fold status="open"><br />
<h2>Section one</h2><br />
<p><br />
...<br />
</p><br />
<p><br />
...<br />
</p><br />
</fold><br />
<fold><br />
<h2>Section two</h2><br />
...<br />
</fold><br />
<br />
Attributes might be another way to do this which avoids inserting a tag between body and h2.<br />
<section fold="open"><br />
<h2 fold="open">Section one</h2><br />
...<br />
</section><br />
<ul><br />
<li fold="open"><br />
<fold_title>blah blah</fold_title> <!-- displayed whether folded or not --><br />
<br /><br />
blah blah <!-- not displayed when folded --><br />
<ul><br />
<li fold="open"><br />
<fold_title>Blah blah </fold_title><br />
<br /><br />
blah blah<br />
<li><br />
<ul><br />
<li><br />
</ul><br />
<br />
Absence of fold attribute makes it unfoldable unless the user allows it.<br />
<br />
This is similar to the hidden attribute but with some key differences. A fold Icon would still be present, along with descriptive text. Folding and unfolding would be accomplished by the user agent without any scripts to set the disabled attribute.<br />
In the case of sections, there would be special handling in that the text of any H1...H6 tag would not go away when folded. For other contexts, there may need to be a <fold_title>...</fold_title> or similar tag or a fold_title="tagname" attribute that lists<br />
what tag contents will be displayed when folded.<br />
<br />
This can be done in CSS as well. However folds and tabs are a basic logical construct and could exist in both domains. If the basic construct isn't defined at the HTML level, documents will be missing fold/tab titles that can be used by user stylesheets or user controls to override document behavior. Even if new tags/attributes are not defined, the basic markup using <div class="fold"> or <div class="tab"> (or other elements which can also be tabbed or folded) should be mentioned in the HTML5 spec.<br />
I.E. This is how you define where the folds/tabs would occur and this is what to use for a title and CSS is used to make it actually happen. You can not leave this to be fragmented by different folks using different classes. Since class allows multiple classes to be specifified, standard classes could be used while still retaining the ability to style each object individually (or as a subgroup) by specifying multiple classes. HTML5 at least needs to specify the classes to be used and make sure that the classes alone are adequate.<br />
<br />
Now technically, datagrid allows flow context. It is not at all clear how it handles flow content. The spaces for examples desparately need to be filled in and more examples given (flow content, sections, lists). If you are going to use it like the fold tag/attribute, <section> should be explictly mentioned and an example given, as that is an important case, though not the only one. As should numbered/unnumbered lists and definition lists. <pre><code> blocks are another important case where folding is reasonably expected. <br />
User agents may provide an ability to, at the users request, fold all sections, whether or not they have a fold attribute (it basically sets fold to yes if it exists and creates it if it doesn't. The user agent can also provide an unfold all. This would work for <section> tags but wouldn't work as well for (un)numbered lists as existing content doesn't identify a title to be retained when folded (unless it has a <br /> tag).<br />
<br />
"The data being presented is provided by script using the methods described in the following sections." No. That probably isn't what you meant to say. It can be provided by a script but it must be possible to provide it without one.<br />
<br />
The section on datagrids should spell out how you define the nesting levels and initial fold state on grid rows, even if that is described elsewhere.<br />
<br />
I don't see support for tabs. Maybe I didn't missed it, or maybe it is done using CSS. Tabs in the modern GUI sense. Not to be confused with the obsolete HTML3 tab tag (typewriter tabs) that were replaced with tables.<br />
<section tabs="true"><br />
<h2>Title</h2><br />
<section><br />
<h3>Tab title</h3><br />
....<br />
</section><br />
<section><br />
<h3>Tab Title</h3><br />
...<br />
</section><br />
</section><br />
If the browser doesn't support tabs, it can display the sections in a normal vertical orientation. section should take a title attribute, to be used when there isn't an h1...h6 section title.<br />
<br />
Another place where tabs are needed is in tables. Consider the tables here which are really subsets of a larger table. <br />
http://en.wikipedia.org/wiki/Comparison_of_media_players#Subtitle_support<br />
<colgroup tabs="true"><br />
<colgroup title="Tab 1"> <!-- first tab --><br />
...<br />
</colgroup><br />
<colgroup title="Tab 2"> <!-- second tab --><br />
...<br />
</colgroup><br />
</colgroup><br />
<br />
Browsers should be encouraged to provide a control that would convert sections or table column groups to tabs. <br />
Also to freeze or repeat row/column headings when a table wider/higher than the window scrolls, under user control.<br />
And they should provide an untabify control.<br />
<br />
Tabs may, and often will, occur inside forms.<br />
<br />
This could be provided via CSS, provided the base HTML contains provisions for a tab title. The same mechanism for titles can be used for both folding and tabbing.<br />
<br />
Note: looks like <legend> tag could be used for folding/tab titles, with H1...H6 used if not present. Needs to be allowed in <section> and <li>. <section><legend>...</legend> ... </section> would be a suitable docbook style replacement for the broken H1...H6 tags. This would make more sense than the <section><h1>...</h1> ... </section> kludge. I really don't like the idea of using H1 for lower level sections. Either use the right numbered level or use the unnumbered <legend>.<br />
<br />
<br />
~~~<br />
<br />
VIDEO<br />
Go visit hulu.com and youtube and imagine doing what they are doing with the video tag. We really need to make it possible to use standards to do what they are doing and not require Flash or Silverlight so the stuff will play across multiple operating systems, multiple browsers, on portable devices, and on set top boxes.<br />
<br />
It should not be necessary to use flash, silverlight, or scripts. Do it right and users have a case for insisting on standard compliant video players. The functionality I describe here is easy enough to implement and provides for the functionality offered by those services.<br />
<br />
Examples have been updated to be more consistent with SMIL, but not<br />
entirely. SMIL uses CamelCase, doesn't let you specify codecs (the<br />
SMIL type attribute is inadquate as it is only sufficient to identify<br />
the container format. The container format doesn't tell you if you<br />
can play what is inside. There are also some cases where it may make<br />
more sense to reuse existing HTML semantics. SMIL seemed a little<br />
week in some areas when it came to defining the global timeline<br />
without first reading the files, which might not be downloaded yet,<br />
but that may have just been due to some bad examples. SMIL doesn't<br />
seem to clearly define the difference between a playlist and a single<br />
playlist item composed of multiple clips (such as commercials). We<br />
aren't implementing SMIL just trying to be similar where we do the<br />
same thing unless there is a reason to do otherwise.<br />
<br />
<seq single_program="true"><br />
<!-- single program = false would be a playlist of separate logical programs --><br />
<br />
<base href="http:/www.example.com/media/webchurns/" /><br />
<!-- scope limited to within parent tag, optional, shortens urls --><br />
<br />
<segments total_time="17:37" title="As the Web Churns: Episode 13" ><br />
<video src="commercial1.ogg" noskip="true" vcodec="codec/FourCC" acodec="codec/FourCC" /><br />
<par><br />
<video src="chapter1.ogg" vcodec="codec/FourCC" acodec="codec/FourCC" /><br />
<textstream src="subtitles1_en.xxx" type="subtitle/subrip" captions="on" ><br />
initial_time="0:30" title="Chapter 1"><br />
<chapter_mark timestamp="5:00" /><br />
<chapter_mark timestamp="10:00" /><br />
<overlay start_time="0:00" end_time="0:05><br />
<img src="logo.png" /><br />
</overlay><br />
</segment><br />
<video src="commercial2.ogg" initial_time="12:00" noskip="true" vcodec="codec/FourCC" acodec="codec/FourCC" ><br />
<video src="chapter2.ogg" subtitle_src="subtitles2_en.xxx" initial_time="12:30" title="Chapter title 2" vcodec="codec/FourCC" acodec="codec/FourCC" /><br />
<segment src="chapter3.ogg" subtitle_src="subtitles3_en.xxx" initial_time="15:00" clip_begin="0:10" clip_end="0.20" vcodec="codec/FourCC" acodec="codec/FourCC" /><br />
<!-- previous plays a subset of the entire video --><br />
<overlay start_time="end"> <br />
<!-- <br />
When the video finishes playing, this content overlays <br />
the video. See youtube. Probably an image (with optional <br />
transparency) accompanied by an image map). Possibly a canvas. <br />
If no image map used, img can be contained with an <a href="..."> <br />
hypertext link <br />
--><br />
<img src="final_overlay.jpg" use_map="#shapes" /><br />
<map name="shapes"><br />
...<br />
</map><br />
</overlay><br />
</segments><br />
<alt><br />
Alternate content<br />
</alt><br />
</seq><br />
<br />
<br />
Chapter marks can be displayed as a mark on the timeline (see hulu, where they coincide with commercial breaks) and the next/prev chapter buttons can be used to skip between chapters as when watching a DVD. total_time and initial_time attributes allow the player to construct a timeline without loading all the video files to know their length. <br />
<br />
This next one allows a video to be played that is contained in a single file with the commericals inserted. An alternate syntax using sublips follows, which might be simpler.<br />
<br />
<br />
<seq><br />
<inserts><br />
<par><br />
<video src="episode15.mpg" title="Episode 15" /><br />
<textstream src="subtitles15.xxx" type="subtitles/subrip/" offset="-0.05" /><br />
</par> <br />
<insert src="commercial1.mpg" timestamp="0:00" duration="0:30" vcodec="codec/FourCC" acodec="codec/FourCC" ><br />
<insert src="commercial2.mpg" timestamp="0.15" duration=0:30><br />
<overlay start_time="0:00" end_time="0.10"><br />
<img src="..." use_map=""><br />
</vid_overlay><br />
<overlay start_time="0:15" end_time="0:20"><br />
<text><br />
Join the Mobile Infantry and save the Galaxy. <br />
Service guarantees citizenship. <br />
<a href="http://www.imdb.com/title/tt0120201/quotes"><br />
Would you like to know more?</a> <br />
<!-- Starship Troopers movie had an early example<br />
of hyperlinks over video --><br />
</text><br />
</overlay><br />
<inserts><br />
</seq> <br />
<br />
Or instead of inserts, you can list the main video multiple times with clip_begin, clip_end tags. <br />
<br />
<seq total_time=><br />
<video src=commercial1.mpg" initial_time="0:00" duration="0:30"/><br />
<video src="episode15.mpg" initial_time="0:30" clip_begin="0:00" clip_end="15:00/><br />
<video src="commercial2.mpg" initial_time="15:30" duration="0:30"/><br />
<video src="episode15.mpg" initial_time="16:00" clipBegin="15:00" clipEnd="15:30" ><br />
<overlay><br />
...<br />
</overlay><br />
</video><br />
<!-- this example doesn't include subtitles or chapter marks --><br />
<!-- vcodec and acodec left off in this example --><br />
</seq><br />
<br />
However, browsers may have trouble playing subclips, other than those which resume where the previous one left off (like after a commercial break). Randomly jumping 20 minutes into a video file requires the browser to download the 20 minutes that were not played and, if there is no index, scan through it to find the approriate time point. This can require too much bandwidth and prefetching. So, authors should be discouraged from jumping deep into the middle of clips which haven't already been played up to that point.<br />
<br />
If an overlay occurs at the end of a sequence, the overlay will overlay the<br />
last frame. However, it may be a non-transparent image or specify a background, in which case it doesn't.<br />
<br />
This next one is similar to the first except instead of the segments being presented as a single video, it allows multiple<br />
separate videos to be presented (similar feature for audio tag, also). The next/previous playlist item buttons on the viewer<br />
can be used.<br />
<seq single_program="false" ><br />
<video src="episode1.ogg" title="Episode 1" vcodec="codec/FourCC" acodec="codec/FourCC"/><br />
<video src="episode2.ogg" title="Episode 2" vcodec="codec/FourCC" acodec="codec/FourCC" /><br />
</video><br />
<seq single_program="false" ><br />
<audio src="song1.ogg" title="Song 1" acodec="FourCC"/><br />
<audio src="song2.ogg" title="Song 2" acodec="FourCC"/><br />
</audio><br />
Instead of "title=", we can include a <legend>. This allows formatting, though player may not support complex formating and may be separate from browser, so needs to be simple.<br />
<br />
When considering alternate video formats needed to support content and alternate languages, we are likely to end up with video/audio/text inside <switch> inside <par> inside <seq> as the general structure (though not all levels are always required). We could also have <seq> inside <par> for cases like full length subtitles overlaid on top of a video divided into shorter clips (possibly with commercial breaks).<br />
<seq><br />
<par><br />
<switch> <br />
<video ... /><br />
<video ... /><br />
<video ... /><br />
</switch><br />
<switch><br />
<textstream ...><br />
</switch><br />
<switch><br />
<audio ... /> <!-- usually embedded in video --><br />
</switch><br />
<overlay><br />
...<br />
</overlay><br />
</par><br />
<par><br />
<!-- next clip --><br />
</par><br />
</seq><br />
<br />
Still need to markup:<br />
- Whether the timestamps in subtitle files refer to the global timeline <br />
(appropriate for multimedia presentations) or within a particular clip<br />
(more appropriate for commercials inserted into a program)<br />
- Whether particular clips occupy space on the global timeline or not.<br />
For commercials, it may be better for them to appear as a singularity<br />
in the timeline so the timeline of the original material is maintained.<br />
<br />
If a browser uses an external player, it can stream the tags, preceeded by a basename tag, to stdin on the player. For a primitive player that doesn't support the xml tags, it can generate a simple playlist (with the inserts first?) or invoke the player with all the segments on the command line. mplayer, for example supports AX, Winamp, SMIL, or a simple one per line format). Xine supports asx, toxine m3u, pls, sfv, and raw text. Both support external subtitle files.<br />
External players may not understand complex html text overlays, image <br />
overlays (easily added), or image maps. It is possible some might support smilText. On the other hand, for built in players, these come naturally for the browser. <br />
<br />
Some systems, such as the X Video Extension, may have trouble with full overlays. They can do chroma keying to give full or no transparency but not partial transparency. However, OpenGL allows full compositing. Overlays at the end, when the video is paused, aren't a problem.<br />
<br />
Note that you can also do things like play a video and pause it and insert other video clips or audio + text/image as commentary with the above markup. You can also do a Mystery Science Theater 3000 audio+image overlay or audio+video overlay if the player supports it using the same markup format (requires a player that can mix audio and/or video and transparency in video stream). A DVD style commentary is somewhat problematic because we haven't included a volume control for the main video audio.<br />
<br />
SMIL tiny profile could be used. It doesn't support appear to support all the stuff above, but it can be added, possibly from the full profile. Or by trying to reuse existing HTML elements as I have done above. I changed my <video> and <audio> to <seq> and my segments to <video> and <audio>, above to resemble SMIL. http://www.w3.org/TR/SMIL/smil-tiny-profile.html<br />
<br />
Subtitles/captions are an important accessibility feature that SMIL tiny profile doesn't appear to adequately address. They may be included in the video stream or in a separate file. A separate file may not even be on the same server. the <par>,<smilText>,<br />
and <textStream> tags appear to be usable for subtitles:<br />
<par><br />
<video src="movie-vid.rm"/><br />
<textstream src="movie-sub-en.rt" systemLanguage="en" systemOverdubOrSubtitle="subtitle"/><br />
</par><br />
And the <switch> can be used to select a language. SubRip seems to be the most widely supported subtitle format at the moment.<br />
http://en.wikipedia.org/wiki/Comparison_of_media_players#Subtitle_support<br />
<br />
Thus adding <seq>, <par>, <textstream>, and <switch> to the <audio> and <video> tags and adding smil time options to the <video> and <audio> tags would do much of what I described (except the overlays at the end which I think there are other smil tags to accomplish though reusing built in img/imgmap/canvas might be easier to implement). If these tags are contained in a <smil> tag then they are SMIL (XHTML+SMIL) and if they are not, then HTML semantics would apply. <par> also allows you to merge separate audio and video files. <br />
<seq> (SMIL) Play items in sequence<br />
<par> (SMIL) Play items simultaneously<br />
<switch> (SMIL) Play one of the alternate items listed<br />
<video> (SMIL) video stream<br />
<audio> (SMIL) audio stream<br />
<textstream> (SMIL) text stream (subtitles)<br />
<img> (HTML) still image to overlay, or part of a slideshow. Needs additional timing tags.<br />
<map> (HTML) image map<br />
<a> (HTML) Hypertext link if use clicks on non transparent portion of image overlay and there is no imagemap.<br />
attributes Distinquish between a sequence of clips that make up one logical video (or audio) and a <br />
sequence that makes up multiple videos (playlist vs. fragments).<br />
<chapter> chapter marks<br />
<smil> NOT USED. If present, then you have XHTML+SMIL and a bunch of other options are available.<br />
<ref> (SMIL) other content types: SVG, flash (best avoided), etc.<br />
<alt> Alternate content when not using <object> semantics.<br />
<loop> Replay content ad-infitium (used for overlays at end of video).<br />
<br />
Streams need attributes that define the start and end positions within the stream to play and where the clip starts in the timeline.<br />
Same syntax will work for video, audio, and slideshows. Also allows subtitling audio (lyrics for song, transcript for radio broadcast). <Object> semantics could be used to specify multiple alternative formats since browsers may support only some audio, video, and subtitle formats. However, additional attributes may be needed to advise the browser in advance which formats are used in the referenced files so it can decide which to load without having to try to load and parse each one in turn.<br />
<br />
This example lets the browser choose a video source file based on whether or not it supports the Dirac video codec:<br />
<br />
<seq><br />
<switch><br />
<video src="episode15_dirac.ogg" acodec="codec/vrbs" vcodec="codec/dirac" type="applicaton/ogg"/><br />
<video src="episode15_theora.ogg" acodec="codec/vrbs" vcodec="codec/ther" type="application/ogg"/><br />
</switch><br />
</seq><br />
Dirac doesn't seem to have a FourCC yet, so I used the long ID.<br />
Here switch is used assuming we can't use the <object> semantics of including alternates in the tag body. If we use <par>, we can put overlays there, and could also put chapter marks there. We then need a general container that can be put inside <par> to contain html text, images, imagemaps, etc.<br />
<br />
<br />
There is a use for a special hypertext link tag (or attributes on the standard tag) that specifies:<br />
- The URL of a web page to load<br />
- An xpath that identifies a video object on that page<br />
- The URL of a subtitle file to insert when playing.<br />
This allows a website to provide links to another site where a video is viewed with the normal content of that site but subtitles are added by the first site providing the link. Since this alters the content at that site, the browser should popup a message<br />
that indicates this is being done so it doesn't appear the target site has been hacked if the user thinks they have followed<br />
a normal hypertext link.<br />
<br />
~~~~<br />
<br />
CANVAS<br />
<br />
I object to canvas only being scriptable. For each of the DOM drawing function calls, there should be an element.<br />
<canvas><br />
<canvas_scale x="1.2" y="1.2" /><br />
<canvas_rotate angle="90 /><br />
<canvas_translate x="1.2" y="2.3 /><br />
<canvas_transform ... /><br />
<canvas_set_transform ... /><br />
<!-- Note, if these tags are not empty, their effect could be limited to the tags contained within --><br />
<br />
<canvas_path><br />
<canvas_move_to x="1.23" y="2.35" /><br />
<canvas_line_to(x="1.23 y="4.56 >/<br />
<canvas_quadratic_curve_to cpx="1.23" cpy="4.56" x="7.89" y="0.12" /><br />
<canvas_bezier_curve_to cp1x="1.2" cp1y="3.4" cp2x="4.5" cp2y="6.7" x="8.9" y="0.1" /><br />
<canvas_arc_to x="1.2" y="3.4" radius="5.5" direction="ccw" /><br />
<closepath /><br />
<stroke /><br />
<fill /><br />
</canvas_path><br />
<canvas_rect x="1.2" y="3.4" w="5.6" h="6.7" /><br />
<canvas_arc x="1.2" y="2.3" radius="5.6", start_angle="7.8" send_angle="9.0", direction="cw");<br />
<br />
<!-- etc. for other function calls --><br />
</canvas><br />
<br />
SaveState()/RestoreState():<br />
<canvas_save_state /><br />
</canvas_restore_state /><br />
<canvas_push> <!-- SaveState() --><br />
<!-- drawing commands here --><br />
</canvas_push> <!-- RestoreState() ---><br />
<br />
It costs almost nothing to add these tags compared to the work of implementing the canvas. It provides a simple alternative to<br />
SVG that uses built in functionality, is less complex, and is XML friendly (no storing paths inside attribute strings), and allows<br />
drawing simple graphs without scripts, or when scripts are disabled for security reasons or not implemented. The javascript functions already defined could populate the display list, stored as XML tags in the DOM hierarchy.<br />
<br />
arcTo(), should only take one coordinate; it is inconsistent with other path operators. If you want the current functionality, call moveTo() first. It should use the current position as the starting point to be consistent with the others. It is also missing a direction which makes it ambiguous as there are always two arcs that satisfy the endpoints and radius.<br />
I also have doubts about using width and height rather than two coordinates for rect.<br />
~~~~<br />
<br />
Smarter subscripts/superscripts:<br />
superscripts and subscripts do not behave properly when both are used, nor do the accomodate all the positions needed.<br />
There is a center, plus 8/16 compass rose positions, plus two extra far left and far right positions. Started with 9, then was improved.<br />
<br />
<compass style="{child-font-size: -2}"><br />
<C></C> <!-- center --><br />
<E></E> <!-- east, suffix --><br />
<ENE></ENE> <!-- east northeast, superscript position --><br />
<NE></NE> <!-- northeast --><br />
<N></N> <!-- north, over--><br />
<NW></NW> <!-- northwest --><br />
<WNW></WNW> <!-- west northwest, presuperscipt postition --><br />
<W></W> <!-- west, prefix --><br />
<WSW><WSW> <!-- west southwest, presubscript position --><br />
<SW></SW> <!-- southwest, presubscript --><br />
<S></S> <!-- south, under --><br />
<SE></SE> <! -- southeast --><br />
<ESE><ESE> <!-- east southeast, subscript position --> <br />
<EE></EE> <!-- east of east, suffix --><br />
<WW></WW> <!-- west of west, prefix --><br />
<!-- four more halfway postions NNW, SSW, NNE, SSE --><br />
</compass><br />
Useful for Periodic table elements, simple, simultaneous super and subscripts, various linguistic stuff, etc.<br />
Without halfway positions and the far east and west positions, it acts like a 3x3 table with a concise notation and the appropriate cells populated. The four alternate corner cells positions are shifted half a cell towards the midline (to super/subscript positions) and the alternate far east and far west cells are shifted outward to new columns centered on the midline providing a way to guarantee that text which preceeds or follows is aligned with the midline.<br />
<br />
would look if super and sub scripts were placed over/above each other.<br />
<ninebox><WW>x=</WW><C>&integral_sign;</C><SE>&negative_infity;</SE><NE>&positive_infinity;</NE><WW>sin(x)/x</WW><ninebox><br />
http://preparatorychemistry.com/Bishop_Isotope_Notation.htm Sodium with isotope, weight, and charge.<br />
<ninebox><WNW>23</NW><ESE>11</ESE><C>Na</C><ENE>+</ENE></ninebox><br />
Instead of squash, you can have ENE, ENW, ESW, ESE for the four alternate corner locations. <br />
Of course, ninebox can be added to CSS, instead. display=ninebox, display=NW, display=NE, etc.<br />
This is good if you style:<br />
<element><name>NA</name><mass>23</mass><number>11</number><charge>+<charge></element><br />
But it does get verbose if you have to use <SPAN class="element">, etc. Styles might apply to change the size or shift position, but the fundamental structural orientation is more basic. <br />
<br />
This is finishing the job that subscript and superscript started and is arguably not just a style. It may not be that abstract but it is fundamentally structural and not just a superficial styling detail. And it eliminates some incredibly contorted use of tables for non-tabular data. You need a 11x9 table with lots of rowspans and colspans, to define the overlapping cell locations occupied by these locations. <br />
<br />
The basic tags could be defined and CSS used to fine tune the position or to apply equivalent behavior to abstract div/span markup or other xml namespaces.<br />
<br />
Note that even unicode deviates from its left-to-right/right-to-left model to provide an over and under code, but doesn't finish the job.<br />
<br />
This is more basic than MathML which also fails to be a suitably abstract math notation - you can't actually evaluate MathML expressions (hence the creation of OpenMath). This also applies to various areas outside the math domain.<br />
<br />
Started out as 9 boxes, hence the name, but a more suitable one should be used. Maybe compass?<br />
~~~~ <br />
<br />
<br />
Nine slice images<br />
<br />
(Note: this one is in CSS3, so it only needs mention in HTML5 spec)<br />
<br />
Various systems use an image divided into 9 parts (like a tic-tac-toe board). Some names include scale-9 and 9-scale This defines two X and two Y image slice locations. When the image is scaled, the four corners are not scaled and the four edge squares and the center square are expanded. Very handy for buttons, tabs, window borders, etc. An example would be a rectangle with rounded edges. <br />
<br />
To implement this, you need a slice_x1, slice_x2, slice_y1, and slice_y2 attribute to be added wherever a tag has an attribute that can point to an image. (Note that this could also include pointing to an SVG file, though SVG tools probably haven't added this functionality. <br />
<br />
In the simplest cases, this would be replaced with desparately needed corner rounding on CSS. But it may contain much more detail.<br />
<br />
http://rwillustrator.blogspot.com/2007/04/understanding-9-slice-scaling.html<br />
This, with <br />
width="640" height="480" slice_x1="8" slice_y1="8" slice_x2="24" slice_y2="24"<br />
or more succinctly <br />
width=640 height=480 img_slice="8,8,24,24"<br />
or even more succinctly:<br />
width=640 height=480 img_slice="8" <br />
replaces an entire screenfull of HTML and reduces 9 image WGETS to one. It also eliminates additional structural damage because<br />
you can simply say <br />
background="foo.png" img_slice="8,8,24,24"<br />
And not put have your content in the middle of this 9x9 table monstrosity. Or better yet, style="{background-image=foo.png; background_img_slice=8,8,24,24;}" (actually, the slices have been added to border-image as:<br />
border-image: url("border.png") 8 8 8 8;<br />
<br />
<br />
http://www.neverpanic.de/blog/single/9-slice-scaling-in-html/<br />
http://blog.hempton.com/2008/11/9-grid-scaling-support-in-javascriptcss/<br />
http://www.bytearray.org/?p=118<br />
http://grub.enbug.org/ThemeFormat<br />
<br />
These are supported in flash, adobe illustrator, fireworks, a jQuery plugin, an actionscript module, and a number of user interface toolkits. Even the grub bootloader supports it, after a fashion, automatically loading 9 images using a wildcard. Apparently, some even scale SWF animated backgrounds this way as if they were images.<br />
<br />
This should be pushed to CSS3 with the appropriate CSS3 module being released before HTML5 with the HTML5 specification specifically calling for HTML5 compliant tools to implement it and advising users to avoid the 9 separate images plus hideous markup. It would be a good addition to PNG, as well. CSS3 appears to accomodate 8 of the 9 slices, as 8 seperate images in the border module. But it also allows border-image to use a 9-slice. This will apparently be in firefox 3.1. I do think this merits some mention in the HTML5 spec. http://www.lrbabe.com/sdoms/borderImage/index.html<br />
<br />
~~~<br />
<br />
<pre>blocks could have a numbering option <pre number="100"> sets the initial line number to 100 and activates line numbering. This allows the text which accompanies a <pre><code> block to reference individual lines. The initial number needs to be settable because in an online source code browser, numbers should line up with original file. This can, however, be done by including<br />
the text of the numbers for autogenerated content. <textareas> could also have numbering; this is very useful for matching up error messages with lines of markedup text when a wysiwyg editor is not used (for example, in a wiki); also, this is compatible with javascript wysiwig editors that take over a text area. Low priority, but worth mentioning.<br />
~~~~</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Main_Page&diff=5102Main Page2010-07-24T15:20:53Z<p>TheresaOConnor: revert spam</p>
<hr />
<div>Welcome to the WHATWG Wiki!<br />
<br />
You can be a part of our community, making proposals for the next version of HTML5. This wiki is made available for you for drafting proposals, for writing essays, for keeping track of HTML-related issues, and so forth. Anyone can create an account and contribute content.<br />
<br />
Before you begin, you may wish to read our [[WHATWG Wiki:Contribution Guidelines|contribution guidelines]].<br />
<br />
==Purpose==<br />
The purpose of the WHATWG Wiki is to create a place for WHATWG contributors to post and compile their own proposals and ideas regarding WHATWG specifications. The specifications themselves will not be available for editing via this wiki. However, ideas you post here may find their way into current and future WHATWG specifications.<br />
<br />
== Main sections and Quick links ==<br />
* [[FAQ]]<br />
* [[Implementations]]<br />
* [[What you can do]] — '''[[Reviewing HTML5|Help us review HTML5!]]<br />
* [[Authoring|Using HTML 5 in your Web site]]<br />
* [[HTML vs. XHTML]]<br />
* [[HTML5 Presentations]]<br />
* [[Spec coordination]]<br />
* [[IDE]]<br />
* [[Testsuite]]<br />
<br />
==WHATWG Specifications==<br />
* [[HTML5]]<br />
* [[Web Workers]]<br />
* See also [[FAQ#What_are_the_various_versions_of_the_spec.3F|What are the various versions of the spec?]] in the FAQ.<br />
<br />
==Communicating with the community==<br />
The WHATWG community has several channels of communication:<br />
* [http://www.whatwg.org/mailing-list Mailing lists]<br />
* [http://blog.whatwg.org/ The blog], including [http://blog.whatwg.org/category/whats-next Mark Pilgrim's column "What's next in HTML5"]<br />
* [http://www.w3.org/html/planet/ W3C's "HTML5 planet"]<br />
* [http://forums.whatwg.org/ The forum]<br />
* [[IRC]]<br />
* [http://wiki.whatwg.org/ This wiki]<br />
<br />
== Research and data ==<br />
Research pertaining to and data on publishing behavior for various bits of markup, used to help drive decisions made in/for HTML5 for specific elements and attributes.<br />
=== feature areas ===<br />
* [[timed tracks]]<br />
=== elements ===<br />
* [[cite]]<br />
* [[time]]<br />
=== attributes ===<br />
* [[charset]] <br />
* [[longdesc]]<br />
* [[summary]]<br />
=== meta ===<br />
* [[Content-Language]]<br />
<br />
These pages may also be of interest:<br />
<br />
* [[Issue Discussion]]<br />
* [[Feature Proposals]]<br />
* [[Presentational elements and attributes]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Testsuite&diff=5090Testsuite2010-07-19T06:49:13Z<p>TheresaOConnor: Reverted edits by Maria (talk) to last revision by Ms2ger</p>
<hr />
<div>Existing tests URI: http://dev.w3.org/html5/tests/<br />
<br />
== Requirements ==<br />
<br />
* Each test needs a "reviewed" marker of some sort<br />
* It must be easy to find tests where the spec has changed under them<br />
* The barrier to contribution must be as low as possible<br />
* Testcases should have somewhat stable URIs<br />
* If test can be done using JavaScript preferably require it to be in JavaScript so engines can be more efficiently tested (i.e. automated).<br />
* It must be easy to review tests<br />
* Standardize a test format?<br />
<br />
== Non-requirements ==<br />
<br />
* There does not need to be a single consistent test harness for the whole of HTML5. (When sections can be tested in isolation, each section should use a test harness that is suited to that section's testing requirements. E.g. there is little value in fitting canvas tests and parser tests into the same framework, and it may add a lot of complexity.)<br />
<br />
== Format proposal ==<br />
<br />
See http://omocha.w3.org/wiki/newformat for a format proposal that should meet most of these requirements. That format is based on the Mozilla Mochitest format for running JavaScript based client-side tests which can be run automatically.<br />
<br />
== Existing tests ==<br />
* [[Test cases]]<br />
* [http://www.whatwg.org/html5 The specification] has links to test in the status boxes.<br />
* [http://samples.msdn.microsoft.com/ietestcenter/ IE's tests]<br />
* [http://tc.labs.opera.com/html/ Opera's tests]<br />
* [http://trac.webkit.org/browser/trunk/LayoutTests (Some of?) WebKit's tests]<br />
* [http://mxr.mozilla.org/mozilla-central/find?string=test_.*%28html|svg%29%24&tree=mozilla-central&hint= Some of Mozilla's mochitests]<br />
** [[Testsuite/Mozilla]]<br />
* [http://mxr.mozilla.org/mozilla-central/find?string=reftest.list Some of Mozilla's reftests]<br />
* [http://philip.html5.org/tests/canvas/suite/tests/ Philip's canvas tests]<br />
* [http://hixie.ch/tests/adhoc/html/ Hixie's ad-hoc tests]<br />
* [http://lachy.id.au/dev/markup/tests/html5/ Lachlan's tests]<br />
* [http://hg.gsnedders.com/php-html-5-direct/file/tip/tests/numbersTest gsnedders' number parsing tests]<br />
* [http://simon.html5.org/test/html/ zcorpan's tests]<br />
* [http://code.google.com/p/html5lib/source/browse/testdata html5lib tests]<br />
* [http://hsivonen.iki.fi/test/moz/video-selection/ hsivonen's video tests]<br />
* [http://www.w3.org/DOM/Test/ Document Object Model (DOM) Conformance Test Suites]<br />
* [http://dev.w3.org/2006/webapi/WindowTestSuite/ Window test suite]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=RelExtensions&diff=5082RelExtensions2010-07-14T15:07:51Z<p>TheresaOConnor: Reverted edits by Rebeca123 (talk) to last revision by EdwardOConnor</p>
<hr />
<div>This page lists the allowed extension values for the rel="" attribute in HTML5. You may add your own values to this list, which makes them legal HTML5 rel values. We ask that you try to avoid redundancy; if someone has already defined a value that does roughly what you want, please reuse it. Note that rel tokens are ASCII-lowercase before comparison against canonical value, so the canonical values should be listed without uppercase ASCII letters.<br />
<br />
{| class=wikitable<br />
|-<br />
! rowspan=2 | Keyword<br />
! colspan=2 | Effect on...<br />
! rowspan=2 | Brief description<br />
! rowspan=2 | Link to more details<br />
! rowspan=2 | Synonyms<br />
! rowspan=2 | Status<br />
|- <br />
! link<br />
! a and area<br />
|-<br />
| accessibility<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains accessibility information for the linking document.<br />
| [http://www.brucelawson.co.uk/2009/rel-accessibility/ Bruce Lawson]<br />
| <br />
| Proposal<br />
|-<br />
| acquaintance<br />
| hyperlink<br />
| hyperlink<br />
| the person represented by the current document considers the person represented by the referenced document to be an acquaintance<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| ajax<br />
| not allowed<br />
| hyperlink<br />
| The link is controlled through javascript, and will load the page linked to though an ajax interface. Without javascript, it should behave as a normal "a" tag, and content change is done server side.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| alternate<br />
|colspan=6| See HTML5<br />
|-<br />
| archives<br />
|colspan=6| See HTML5<br />
|-<br />
| author<br />
|colspan=6| See HTML5<br />
|-<br />
| bookmark<br />
|colspan=6| See HTML5<br />
|-<br />
| canonical<br />
| hyperlink<br />
| not allowed<br />
| Robots (e.g., search engines) should treat the document containing the tag as a minor variation of the linked document, which may result in the removal of the former from a web index and in the consolidation of its quality signals in the latter.<br />
| [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-domain<br />
| external resource<br />
| not allowed<br />
| More than one domain may have largely similar or identical content but only one of the domains should be indexed for search engines. E.g., a company may have short and long domain names for the same content.<br />
For security against traffic theft, rev must be meaningless.<br />
| [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139066 Google's analogous service] and [[Talk:RelExtensions#On_canonical-domain.2C_canonical-wwwnone.2C_and_canonical-first|Talk for this page]]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-first<br />
| external resource<br />
| hyperlink<br />
| Where the canonical value should point to a group of pages, but the link can point to only one page, the group of pages can be clarified by choosing the first page in the group and assigning the URL for this rel link.<br />
For security against traffic theft, rev must be meaningless.<br /><br />
This is only shorthand for providing two link elements, one on the noncanonical page to a "canonical" page and the other on the canonical page to the "first" page of the group.<br />
Where the group of pages corresponds to a subdirectory and a canonical URL value can point to the subdirectory resulting in a user arriving at the subdirectory's index page which is part of the group, this shorthand is unnecessary and one rel="canonical" will suffice.<br />
| [[Talk:RelExtensions#On_canonical-domain.2C_canonical-wwwnone.2C_and_canonical-first|Talk for this page]]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-human<br />
| external resource<br />
| hyperlink<br />
| Pages about a person across many websites can be associated based on name, nationality, birthplace, dates of birth and death, when flourished, and other identifiers.<br />
Search engines could more consistently aggregate same-person pages with less confusion due to name similarity.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7681 W3C Bug 7681]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-organization<br />
| external resource<br />
| hyperlink<br />
| Pages about an organization across many websites can be associated based on name, headquarters site, and other identifiers.<br />
Search engines could more consistently aggregate same-organization pages with less confusion due to name similarity.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7682 W3C Bug 7682]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-wwwnone<br />
| external resource<br />
| hyperlink<br />
| Both bare and www-prefixed domain names usually direct to the same site. Especially when external links to a site vary in the form used, search engine indexing concentrated on only one domain form may raise its credibility. The rel value is the form preferred for indexing, e.g., rel="http://example.net". Nothing to the right of the top-level domain is needed.<br />
For security against traffic theft, rev must be meaningless.<br />
| [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139066 Google's analogous service] and [[Talk:RelExtensions#On_canonical-domain.2C_canonical-wwwnone.2C_and_canonical-first|Talk for this page]]<br />
| <br />
| Proposal<br />
|-<br />
| chapter<br />
| hyperlink<br />
| hyperlink<br />
| Target document is a subdocument of the current document.<br />
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]<br />
| section, subsection, appendix<br />
| Proposal<br />
|-<br />
| child<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a child of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| co-resident<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person lives in the same residence as the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| co-worker<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a co-worker of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| colleague<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a colleague of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| contact<br />
| hyperlink<br />
| hyperlink<br />
| the person represented by the current document considers the person represented by the referenced document to be a contact<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| contributor<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) involved in the production of the content, but not his main author(s).<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| crush<br />
| hyperlink<br />
| hyperlink<br />
| this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| date<br />
| hyperlink<br />
| hyperlink<br />
| this person considers the referenced person to be a date (i.e. is dating the referenced person)<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| details<br />
| hyperlink<br />
| hyperlink<br />
| The referenced document contains additional (or complete) details about the current document (for example, a "read more..." hyperlink on a blog page that leads to the full posting).<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| dns-prefetch<br />
| external resource<br />
| not allowed<br />
| Force the DNS lookup of specific hostnames.<br />
| [https://developer.mozilla.org/En/Controlling_DNS_prefetching Mozilla DNS Prefetching], <br />[http://dev.chromium.org/developers/design-documents/dns-prefetching Chromium DNS Prefetching]<br />
| <br />
| Proposal<br />
|-<br />
| edit<br />
| hyperlink<br />
| hyperlink<br />
| Target document is an editable version of the current document.<br />
| [http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-11.html#new-link-relation Atom Protocol]<br />
| <br />
| Proposal<br />
|-<br />
| edituri<br />
| hyperlink<br />
| not allowed<br />
| a link to an RSD file describing how to edit the given page.<br />
| [http://cyber.law.harvard.edu/blogs/gems/tech/rsd.htm rsd]<br />
| <br />
| Proposal<br />
|-<br />
| enclosure<br />
| hyperlink<br />
| hyperlink<br />
| the destination of the hyperlink is intended to be downloaded and cached.<br />
| [http://microformats.org/wiki/rel-enclosure rel-enclosure]<br />
| <br />
| Proposal<br />
|-<br />
| enlarged<br />
| not allowed<br />
| hyperlink<br />
| For anchors that have one child image element, indicates that the linked document is an image file which is the same as the child image element of the link except a larger size (dimensions).<br />
| [http://dvdgoss.wordpress.com/2010/04/26/the-case-for-relenlarge-in-html5/ David Goss]<br />
| <br />
| Proposal<br />
|-<br />
| external<br />
|colspan=6| See HTML5<br />
|-<br />
| extension<br />
| hyperlink<br />
| hyperlink<br />
| Browser extension<br />
| [http://mozillalabs.com/jetpack/2010/05/12/indexing-and-auto-detecting-browser-extensions-on-the-web/ Mozilla Labs]<br />
| <br />
| Proposal<br />
|-<br />
| first<br />
|colspan=6| See HTML5<br />
|-<br />
| friend<br />
| hyperlink<br />
| hyperlink<br />
| the person represented by the current document considers the person represented by the referenced document to be a friend<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| glossary<br />
| hyperlink<br />
| hyperlink<br />
| Target document provides definitions for words in current document.<br />
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]<br />
| <br />
| Proposal<br />
|-<br />
| help<br />
|colspan=6| See HTML5<br />
|-<br />
| hub<br />
| hyperlink<br />
| not allowed<br />
| Indicates a URL which implements both sides of the PubSubHubbub protocol.<br />
| [http://code.google.com/p/pubsubhubbub/ PubSubHubbub]<br />
| <br />
| Proposal<br />
|-<br />
| i18nrules<br />
| hyperlink<br />
| not allowed<br />
| Target document provides ITS (Internationalization tag Set) rules for processing the current document.<br />
| [http://www.w3.org/TR/its/ ITS]<br />
| <br />
| Proposal<br />
|-<br />
| icon<br />
|colspan=6| See HTML5<br />
|-<br />
| index<br />
|colspan=6| See HTML5<br />
|-<br />
| jump<br />
| not allowed<br />
| hyperlink<br />
| Indicates a same page jump from the current fragment to another fragment. (E.g. sometimes online newspapers insert direct text saying "article continues below the image/advert" - they could instead use "jump" link. Ultimately, it indicates a page internal link.)<br />
| [[Talk:RelExtensions#On_footnote.2C_note.2C_and_jump|Talk]]<br />
| <br />
| Proposal<br />
|-<br />
| kin<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is part of the extended family of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| lang-alt-[ISO 639-1 code]<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains a version of the current document in an alternative language. "[ISO 639-1 code]" is replaced with the appropriate [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 language code]. The ISO 639-1 code is used when the browser (or other user agent) wants to display either the full name of the language or a flag, as a visual aid for the end user.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| lang-orig-[ISO 639-1 code]<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains a version of the current document in the language the document was originally written in. "[ISO 639-1 code]" is replaced with the appropriate [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 language code]. The ISO 639-1 code is used when the browser (or other user agent) wants to display either the full name of the language or a flag, as a visual aid for the end user.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| last<br />
|colspan=6| See HTML5<br />
|-<br />
| license<br />
|colspan=6| See HTML5<br />
|-<br />
| logout<br />
| external resource<br />
| not allowed<br />
| The linked document provides a resource for the UA to request when all currently open documents of the same "group" are closed (to facilitate logging out the current user).<br />
| [[LogoutRelExtension]]<br />
| <br />
| Proposal<br />
|-<br />
| me<br />
| hyperlink<br />
| hyperlink<br />
| the referenced document represents the same person as does the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| met<br />
| hyperlink<br />
| hyperlink<br />
| this person has met the referenced person<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| muse<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person inspires the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| neighbor<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person lives nearby the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| next<br />
|colspan=6| See HTML5<br />
|-<br />
| next-archive<br />
| hyperlink<br />
| hyperlink<br />
| A URI that refers to the immediately following archive document.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations], <br />[http://tools.ietf.org/html/rfc5005 RFC5005]<br />
| <br />
| Proposal<br />
|-<br />
| nofollow<br />
|colspan=6| See HTML5<br />
|-<br />
| noreferrer<br />
|colspan=6| See HTML5<br />
|-<br />
| noprefetch<br />
| external resource<br />
| hyperlink<br />
| Denies prefetching (not fetching) as a cost-control option for website owners, especially where pages are dynamic, leading to prefetching of wrong and useless pages.<br /><br />
The link provides a per-page denial whereas a and area provide a per-element denial.<br /><br />
For link, attributes rel="noprefetch" denies prefetching of the page at the href URL and rev="noprefetch" denies prefetching of the page bearing the link.<br /><br />
For a and area, rel is as above and rev is meaningless.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7918 W3C Bug 7918]<br />
| <br />
| Proposal<br />
|-<br />
| note<br />
| not allowed<br />
| hyperlink<br />
| An in-page or out-page jump to a footnote. This encompasses ''note'', ''footnote'', ''endnote'', and ''sidenote''.<br />
| [[Talk:RelExtensions#On_footnote.2C_note.2C_and_jump|Talk]]<br />
| <br />
| Proposal<br />
|-<br />
| openid.delegate<br />
| external resource<br />
| not allowed<br />
| OpenID 1.1 authentication delegation<br />
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID specification]<br />
| <br />
| Proposal<br />
|-<br />
| openid.server<br />
| external resource<br />
| not allowed<br />
| OpenID 1.1 authentication delegation<br />
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID specification]<br />
| <br />
| Proposal<br />
|-<br />
| openid2.local_id<br />
| external resource<br />
| not allowed<br />
| OpenID 2.0 authentication delegation<br />
| [http://openid.net/specs/openid-authentication-2_0.html#html_disco OpenID Auth 2.0 section 7.3.3]<br />
| <br />
| Proposal<br />
|-<br />
| openid2.provider<br />
| external resource<br />
| not allowed<br />
| OpenID 2.0 authentication endpoint<br />
| [http://openid.net/specs/openid-authentication-2_0.html#html_disco OpenID Auth 2.0 section 7.3.3]<br />
| <br />
| Proposal<br />
|-<br />
| parent<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a parent of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| payment<br />
| hyperlink<br />
| hyperlink<br />
| A URI where payment is accepted.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations]<br />
| <br />
| Proposal<br />
|-<br />
| pgpkey<br />
| hyperlink<br />
| not allowed<br />
| The linked document is the PGP public key file (which may contain multiple keys) of the author(s) of the page.<br />
| [http://purl.org/net/pgpkey/], [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html]<br />
| <br />
| Proposal<br />
|-<br />
| pingback<br />
|colspan=6| See HTML5<br />
|-<br />
| prefetch<br />
|colspan=6| See HTML5<br />
|-<br />
| prev<br />
|colspan=6| See HTML5<br />
|-<br />
| prev-archive<br />
| hyperlink<br />
| hyperlink<br />
| A URI that refers to the immediately preceding archive document.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations], <br />[http://tools.ietf.org/html/rfc5005 RFC5005]<br />
| <br />
| Proposal<br />
|-<br />
| print<br />
| external resource<br />
| hyperlink<br />
| The referenced document is recommended for printing, even though the referent document is capable of being printed and both documents are of the same type, medium, and language. A typical case is where content spread over multiple pages is also available on a single page that is more convenient to print.<br />
This is semantically more specific than "canonical" and "alternate". Where type, medium, and/or language differ, consider "alternate"; where any of them differ but the purpose is printing, consider applying both values.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7645 W3C Bug 7645]<br />
| <br />
| Proposal<br />
|-<br />
| profile<br />
| hyperlink<br />
| hyperlink<br />
| this referenced link is a metadata profile for the current document<br />
| [http://www.w3.org/TR/html401/struct/global.html#profiles HTML Meta data profiles], <br />[http://www.w3.org/2003/g/glean-profile Example of profile in a-elements]<br />
| <br />
| Proposal<br />
|-<br />
| related<br />
| hyperlink<br />
| hyperlink<br />
| this referenced link identifies a resource related to the current document<br />
| [http://tools.ietf.org/html/rfc4287#section-4.2.7 Atom Syndication Format]<br />
| <br />
| Proposal<br />
|-<br />
| resource-package<br />
| external resource<br />
| not allowed<br />
| The linked document is a zipped resource package<br />
| [http://limi.net/articles/resource-packages/ Resource Packages]<br />
| <br />
| Proposal<br />
|-<br />
| reviewer<br />
| hyperlink<br />
| not allowed<br />
| The linked document is the page/email an agent (people or firm or...) responsible for reviewing the content.<br />
| [http://wiki.csswg.org/test/css2.1/format#reviewer]<br />
| <br />
| Proposal<br />
|-<br />
| script<br />
| not allowed<br />
| not allowed<br />
| Was proposed to replace &lt;script>. Use &lt;script> instead.<br />
| none<br />
| <br />
| Rejected<br />
|-<br />
| search<br />
|colspan=6| See HTML5<br />
|-<br />
| self<br />
| hyperlink<br />
| hyperlink<br />
| A URI that refers to a resource equivalent to the containing element.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations], <br />[http://tools.ietf.org/html/rfc4287 RFC4287]<br />
| <br />
| Proposal<br />
|-<br />
| service<br />
| external resource<br />
| not allowed<br />
| Points to a resource describing a service API<br />
| [[ServiceRelExtension]]<br />
| <br />
| Proposal<br />
|-<br />
| shortlink<br />
| hyperlink<br />
| hyperlink<br />
| Identifies a shorter form of the URL for the current document, provided by the document owner.<br />
| [http://code.google.com/p/shortlink/wiki/Specification shortlink Specification]<br />
| <br />
| Proposal<br />
|-<br />
| sibling<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a sibling of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| sidebar<br />
|colspan=6| See HTML5<br />
|-<br />
| spouse<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a spouse of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| statechart<br />
| external resource<br />
| not allowed<br />
| A reference to an SCXML document that controls the application-flow of the current HTML document<br />
| [http://www.w3.org/TR/scxml/ SCXML]<br />
|<br />
| Proposal<br />
|-<br />
| stylesheet<br />
|colspan=6| See HTML5<br />
|-<br />
| sweetheart<br />
| hyperlink<br />
| hyperlink<br />
| this person considers the referenced person to be their sweetheart<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| tag<br />
|colspan=6| See HTML5<br />
|-<br />
| technicalauthor<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) responsible for the technical construction of the page (i.e. the HTML/CSS/PHP code), not for the content.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| timesheet<br />
| external resource<br />
| not allowed<br />
| SMIL Timesheet<br />
| [http://www.w3.org/TR/timesheets/#smilTimesheetsNS-Elements-Timesheet SMIL Timesheets 1.0]<br />
| <br />
| Proposal<br />
|-<br />
| translatedfrom<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email that has been translation source for the current document. It also indicates that the current document is a translation and not an original work.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| translator<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) responsible for the translation of the page. It also indicates that the current page is a translation of an other document, which should be linked through a rel="translatedfrom".<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| up<br />
|colspan=6| See HTML5<br />
|-<br />
| us<br />
| hyperlink<br />
| hyperlink<br />
| The referenced document represents the same organisation as does the current document [cf rel-me]<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| webmaster<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) available for requests about the content of the page.<br />
| <br />
| maintainer<br />
| Proposal<br />
|-<br />
| widget<br />
| hyperlink<br />
| hyperlink<br />
| Points to a widget.<br />
| [http://dev.w3.org/2006/waf/widgets/Overview.html#autodiscovery Widgets 1.0 Editor's draft]<br />
| <br />
| Proposal<br />
|-<br />
| wlwmanifest<br />
| hyperlink<br />
| not allowed<br />
| A link to a manifest for Windows Live Writer.<br />
| [http://msdn.microsoft.com/en-us/library/bb463263.aspx msdn]<br />
| <br />
| Proposal<br />
|}<br />
<br />
The "Effect on... link" column must either say "not allowed" if the rel value is not allowed on &lt;link> elements, "hyperlink" if the rel value creates a hyperlink, or "external resource" if the rel value creates a link to an external resource.<br />
<br />
The "Effect on... a and area" column must either say "not allowed" or "hyperlink".<br />
<br />
For the "Status" section to be changed to "Accepted", the proposed keyword must either have been through the [http://microformats.org/wiki/process Microformats process], and been approved by the Microformats community; or must be defined by a W3C specification in the Candidate Recommendation or Recommendation state. If it fails to go through this process, it is "Rejected".<br />
<br />
For more details, see [http://whatwg.org/specs/web-apps/current-work/#linkTypes the HTML5 specification]. See also [http://microformats.org/wiki/existing-rel-values the Microformats wiki page on this matter].</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=RelExtensions&diff=5019RelExtensions2010-07-07T02:21:38Z<p>TheresaOConnor: Reverted edits by Bleach23 (talk) to last revision by Annevk</p>
<hr />
<div>This page lists the allowed extension values for the rel="" attribute in HTML5. You may add your own values to this list, which makes them legal HTML5 rel values. We ask that you try to avoid redundancy; if someone has already defined a value that does roughly what you want, please reuse it. Note that rel tokens are ASCII-lowercase before comparison against canonical value, so the canonical values should be listed without uppercase ASCII letters.<br />
<br />
{| class=wikitable<br />
|-<br />
! rowspan=2 | Keyword<br />
! colspan=2 | Effect on...<br />
! rowspan=2 | Brief description<br />
! rowspan=2 | Link to more details<br />
! rowspan=2 | Synonyms<br />
! rowspan=2 | Status<br />
|- <br />
! link<br />
! a and area<br />
|-<br />
| accessibility<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains accessibility information for the linking document.<br />
| [http://www.brucelawson.co.uk/2009/rel-accessibility/ Bruce Lawson]<br />
| <br />
| Proposal<br />
|-<br />
| acquaintance<br />
| hyperlink<br />
| hyperlink<br />
| the person represented by the current document considers the person represented by the referenced document to be an acquaintance<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| ajax<br />
| not allowed<br />
| hyperlink<br />
| The link is controlled through javascript, and will load the page linked to though an ajax interface. Without javascript, it should behave as a normal "a" tag, and content change is done server side.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| alternate<br />
|colspan=6| See HTML5<br />
|-<br />
| archives<br />
|colspan=6| See HTML5<br />
|-<br />
| author<br />
|colspan=6| See HTML5<br />
|-<br />
| bookmark<br />
|colspan=6| See HTML5<br />
|-<br />
| canonical<br />
| hyperlink<br />
| not allowed<br />
| Robots (e.g., search engines) should treat the document containing the tag as a minor variation of the linked document, which may result in the removal of the former from a web index and in the consolidation of its quality signals in the latter.<br />
| [http://googlewebmastercentral.blogspot.com/2009/02/specify-your-canonical.html]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-domain<br />
| external resource<br />
| not allowed<br />
| More than one domain may have largely similar or identical content but only one of the domains should be indexed for search engines. E.g., a company may have short and long domain names for the same content.<br />
For security against traffic theft, rev must be meaningless.<br />
| [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139066 Google's analogous service] and [[Talk:RelExtensions#On_canonical-domain.2C_canonical-wwwnone.2C_and_canonical-first|Talk for this page]]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-first<br />
| external resource<br />
| hyperlink<br />
| Where the canonical value should point to a group of pages, but the link can point to only one page, the group of pages can be clarified by choosing the first page in the group and assigning the URL for this rel link.<br />
For security against traffic theft, rev must be meaningless.<br /><br />
This is only shorthand for providing two link elements, one on the noncanonical page to a "canonical" page and the other on the canonical page to the "first" page of the group.<br />
Where the group of pages corresponds to a subdirectory and a canonical URL value can point to the subdirectory resulting in a user arriving at the subdirectory's index page which is part of the group, this shorthand is unnecessary and one rel="canonical" will suffice.<br />
| [[Talk:RelExtensions#On_canonical-domain.2C_canonical-wwwnone.2C_and_canonical-first|Talk for this page]]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-human<br />
| external resource<br />
| hyperlink<br />
| Pages about a person across many websites can be associated based on name, nationality, birthplace, dates of birth and death, when flourished, and other identifiers.<br />
Search engines could more consistently aggregate same-person pages with less confusion due to name similarity.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7681 W3C Bug 7681]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-organization<br />
| external resource<br />
| hyperlink<br />
| Pages about an organization across many websites can be associated based on name, headquarters site, and other identifiers.<br />
Search engines could more consistently aggregate same-organization pages with less confusion due to name similarity.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7682 W3C Bug 7682]<br />
| <br />
| Proposal<br />
|-<br />
| canonical-wwwnone<br />
| external resource<br />
| hyperlink<br />
| Both bare and www-prefixed domain names usually direct to the same site. Especially when external links to a site vary in the form used, search engine indexing concentrated on only one domain form may raise its credibility. The rel value is the form preferred for indexing, e.g., rel="http://example.net". Nothing to the right of the top-level domain is needed.<br />
For security against traffic theft, rev must be meaningless.<br />
| [http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=139066 Google's analogous service] and [[Talk:RelExtensions#On_canonical-domain.2C_canonical-wwwnone.2C_and_canonical-first|Talk for this page]]<br />
| <br />
| Proposal<br />
|-<br />
| chapter<br />
| hyperlink<br />
| hyperlink<br />
| Target document is a subdocument of the current document.<br />
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]<br />
| section, subsection, appendix<br />
| Proposal<br />
|-<br />
| child<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a child of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| co-resident<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person lives in the same residence as the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| co-worker<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a co-worker of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| colleague<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a colleague of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| contact<br />
| hyperlink<br />
| hyperlink<br />
| the person represented by the current document considers the person represented by the referenced document to be a contact<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| contributor<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) involved in the production of the content, but not his main author(s).<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| crush<br />
| hyperlink<br />
| hyperlink<br />
| this person considers the referenced person to be a crush (i.e. has a crush on the referenced person)<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| date<br />
| hyperlink<br />
| hyperlink<br />
| this person considers the referenced person to be a date (i.e. is dating the referenced person)<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| details<br />
| hyperlink<br />
| hyperlink<br />
| The referenced document contains additional (or complete) details about the current document (for example, a "read more..." hyperlink on a blog page that leads to the full posting).<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| dns-prefetch<br />
| external resource<br />
| not allowed<br />
| Force the DNS lookup of specific hostnames.<br />
| [https://developer.mozilla.org/En/Controlling_DNS_prefetching Mozilla DNS Prefetching], <br />[http://dev.chromium.org/developers/design-documents/dns-prefetching Chromium DNS Prefetching]<br />
| <br />
| Proposal<br />
|-<br />
| edit<br />
| hyperlink<br />
| hyperlink<br />
| Target document is an editable version of the current document.<br />
| [http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-11.html#new-link-relation Atom Protocol]<br />
| <br />
| Proposal<br />
|-<br />
| edituri<br />
| hyperlink<br />
| not allowed<br />
| a link to an RSD file describing how to edit the given page.<br />
| [http://cyber.law.harvard.edu/blogs/gems/tech/rsd.htm rsd]<br />
| <br />
| Proposal<br />
|-<br />
| enclosure<br />
| hyperlink<br />
| hyperlink<br />
| the destination of the hyperlink is intended to be downloaded and cached.<br />
| [http://microformats.org/wiki/rel-enclosure rel-enclosure]<br />
| <br />
| Proposal<br />
|-<br />
| enlarged<br />
| not allowed<br />
| hyperlink<br />
| For anchors that have one child image element, indicates that the linked document is an image file which is the same as the child image element of the link except a larger size (dimensions).<br />
| [http://dvdgoss.wordpress.com/2010/04/26/the-case-for-relenlarge-in-html5/ David Goss]<br />
| <br />
| Proposal<br />
|-<br />
| external<br />
|colspan=6| See HTML5<br />
|-<br />
| extension<br />
| hyperlink<br />
| hyperlink<br />
| Browser extension<br />
| [http://mozillalabs.com/jetpack/2010/05/12/indexing-and-auto-detecting-browser-extensions-on-the-web/ Mozilla Labs]<br />
| <br />
| Proposal<br />
|-<br />
| first<br />
|colspan=6| See HTML5<br />
|-<br />
| friend<br />
| hyperlink<br />
| hyperlink<br />
| the person represented by the current document considers the person represented by the referenced document to be a friend<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| glossary<br />
| hyperlink<br />
| hyperlink<br />
| Target document provides definitions for words in current document.<br />
| [http://www.w3.org/TR/html4/types.html#h-6.12 HTML4]<br />
| <br />
| Proposal<br />
|-<br />
| help<br />
|colspan=6| See HTML5<br />
|-<br />
| hub<br />
| hyperlink<br />
| not allowed<br />
| Indicates a URL which implements both sides of the PubSubHubbub protocol.<br />
| [http://code.google.com/p/pubsubhubbub/ PubSubHubbub]<br />
| <br />
| Proposal<br />
|-<br />
| i18nrules<br />
| hyperlink<br />
| not allowed<br />
| Target document provides ITS (Internationalization tag Set) rules for processing the current document.<br />
| [http://www.w3.org/TR/its/ ITS]<br />
| <br />
| Proposal<br />
|-<br />
| icon<br />
|colspan=6| See HTML5<br />
|-<br />
| index<br />
|colspan=6| See HTML5<br />
|-<br />
| jump<br />
| not allowed<br />
| hyperlink<br />
| Indicates a same page jump from the current fragment to another fragment. (E.g. sometimes online newspapers insert direct text saying "article continues below the image/advert" - they could instead use "jump" link. Ultimately, it indicates a page internal link.)<br />
| [[Talk:RelExtensions#On_footnote.2C_note.2C_and_jump|Talk]]<br />
| <br />
| Proposal<br />
|-<br />
| kin<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is part of the extended family of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| lang-alt-[ISO 639-1 code]<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains a version of the current document in an alternative language. "[ISO 639-1 code]" is replaced with the appropriate [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 language code]. The ISO 639-1 code is used when the browser (or other user agent) wants to display either the full name of the language or a flag, as a visual aid for the end user.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| lang-orig-[ISO 639-1 code]<br />
| hyperlink<br />
| hyperlink<br />
| The linked document contains a version of the current document in the language the document was originally written in. "[ISO 639-1 code]" is replaced with the appropriate [http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes ISO 639-1 language code]. The ISO 639-1 code is used when the browser (or other user agent) wants to display either the full name of the language or a flag, as a visual aid for the end user.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| last<br />
|colspan=6| See HTML5<br />
|-<br />
| license<br />
|colspan=6| See HTML5<br />
|-<br />
| logout<br />
| external resource<br />
| not allowed<br />
| The linked document provides a resource for the UA to request when all currently open documents of the same "group" are closed (to facilitate logging out the current user).<br />
| [[LogoutRelExtension]]<br />
| <br />
| Proposal<br />
|-<br />
| me<br />
| hyperlink<br />
| hyperlink<br />
| the referenced document represents the same person as does the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| met<br />
| hyperlink<br />
| hyperlink<br />
| this person has met the referenced person<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| muse<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person inspires the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| neighbor<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person lives nearby the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| next<br />
|colspan=6| See HTML5<br />
|-<br />
| next-archive<br />
| hyperlink<br />
| hyperlink<br />
| A URI that refers to the immediately following archive document.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations], <br />[http://tools.ietf.org/html/rfc5005 RFC5005]<br />
| <br />
| Proposal<br />
|-<br />
| nofollow<br />
|colspan=6| See HTML5<br />
|-<br />
| noreferrer<br />
|colspan=6| See HTML5<br />
|-<br />
| noprefetch<br />
| external resource<br />
| hyperlink<br />
| Denies prefetching (not fetching) as a cost-control option for website owners, especially where pages are dynamic, leading to prefetching of wrong and useless pages.<br /><br />
The link provides a per-page denial whereas a and area provide a per-element denial.<br /><br />
For link, attributes rel="noprefetch" denies prefetching of the page at the href URL and rev="noprefetch" denies prefetching of the page bearing the link.<br /><br />
For a and area, rel is as above and rev is meaningless.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7918 W3C Bug 7918]<br />
| <br />
| Proposal<br />
|-<br />
| note<br />
| not allowed<br />
| hyperlink<br />
| An in-page or out-page jump to a footnote. This encompasses ''note'', ''footnote'', ''endnote'', and ''sidenote''.<br />
| [[Talk:RelExtensions#On_footnote.2C_note.2C_and_jump|Talk]]<br />
| <br />
| Proposal<br />
|-<br />
| openid.delegate<br />
| external resource<br />
| not allowed<br />
| OpenID 1.1 authentication delegation<br />
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID specification]<br />
| <br />
| Proposal<br />
|-<br />
| openid.server<br />
| external resource<br />
| not allowed<br />
| OpenID 1.1 authentication delegation<br />
| [http://openid.net/specs/openid-authentication-1_1.html#delegating_authentication OpenID specification]<br />
| <br />
| Proposal<br />
|-<br />
| openid2.local_id<br />
| external resource<br />
| not allowed<br />
| OpenID 2.0 authentication delegation<br />
| [http://openid.net/specs/openid-authentication-2_0.html#html_disco OpenID Auth 2.0 section 7.3.3]<br />
| <br />
| Proposal<br />
|-<br />
| openid2.provider<br />
| external resource<br />
| not allowed<br />
| OpenID 2.0 authentication endpoint<br />
| [http://openid.net/specs/openid-authentication-2_0.html#html_disco OpenID Auth 2.0 section 7.3.3]<br />
| <br />
| Proposal<br />
|-<br />
| parent<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a parent of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| payment<br />
| hyperlink<br />
| hyperlink<br />
| A URI where payment is accepted.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations]<br />
| <br />
| Proposal<br />
|-<br />
| pgpkey<br />
| hyperlink<br />
| not allowed<br />
| The linked document is the PGP public key file (which may contain multiple keys) of the author(s) of the page.<br />
| [http://purl.org/net/pgpkey/], [http://golem.ph.utexas.edu/~distler/blog/archives/000320.html]<br />
| <br />
| Proposal<br />
|-<br />
| pingback<br />
|colspan=6| See HTML5<br />
|-<br />
| prefetch<br />
|colspan=6| See HTML5<br />
|-<br />
| prev<br />
|colspan=6| See HTML5<br />
|-<br />
| prev-archive<br />
| hyperlink<br />
| hyperlink<br />
| A URI that refers to the immediately preceding archive document.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations], <br />[http://tools.ietf.org/html/rfc5005 RFC5005]<br />
| <br />
| Proposal<br />
|-<br />
| print<br />
| external resource<br />
| hyperlink<br />
| The referenced document is recommended for printing, even though the referent document is capable of being printed and both documents are of the same type, medium, and language. A typical case is where content spread over multiple pages is also available on a single page that is more convenient to print.<br />
This is semantically more specific than "canonical" and "alternate". Where type, medium, and/or language differ, consider "alternate"; where any of them differ but the purpose is printing, consider applying both values.<br />
| [http://www.w3.org/Bugs/Public/show_bug.cgi?id=7645 W3C Bug 7645]<br />
| <br />
| Proposal<br />
|-<br />
| profile<br />
| hyperlink<br />
| hyperlink<br />
| this referenced link is a metadata profile for the current document<br />
| [http://www.w3.org/TR/html401/struct/global.html#profiles HTML Meta data profiles], <br />[http://www.w3.org/2003/g/glean-profile Example of profile in a-elements]<br />
| <br />
| Proposal<br />
|-<br />
| related<br />
| hyperlink<br />
| hyperlink<br />
| this referenced link identifies a resource related to the current document<br />
| [http://tools.ietf.org/html/rfc4287#section-4.2.7 Atom Syndication Format]<br />
| <br />
| Proposal<br />
|-<br />
| resource-package<br />
| external resource<br />
| not allowed<br />
| The linked document is a zipped resource package<br />
| [http://limi.net/articles/resource-packages/ Resource Packages]<br />
| <br />
| Proposal<br />
|-<br />
| reviewer<br />
| hyperlink<br />
| not allowed<br />
| The linked document is the page/email an agent (people or firm or...) responsible for reviewing the content.<br />
| [http://wiki.csswg.org/test/css2.1/format#reviewer]<br />
| <br />
| Proposal<br />
|-<br />
| script<br />
| not allowed<br />
| not allowed<br />
| Was proposed to replace &lt;script>. Use &lt;script> instead.<br />
| none<br />
| <br />
| Rejected<br />
|-<br />
| search<br />
|colspan=6| See HTML5<br />
|-<br />
| self<br />
| hyperlink<br />
| hyperlink<br />
| A URI that refers to a resource equivalent to the containing element.<br />
| [http://www.iana.org/assignments/link-relations/link-relations.xhtml Atom Link Relations], <br />[http://tools.ietf.org/html/rfc4287 RFC4287]<br />
| <br />
| Proposal<br />
|-<br />
| service<br />
| external resource<br />
| not allowed<br />
| Points to a resource describing a service API<br />
| [[ServiceRelExtension]]<br />
| <br />
| Proposal<br />
|-<br />
| shortlink<br />
| hyperlink<br />
| hyperlink<br />
| Identifies a shorter form of the URL for the current document, provided by the document owner.<br />
| [http://code.google.com/p/shortlink/wiki/Specification shortlink Specification]<br />
| <br />
| Proposal<br />
|-<br />
| sibling<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a sibling of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| sidebar<br />
|colspan=6| See HTML5<br />
|-<br />
| spouse<br />
| hyperlink<br />
| hyperlink<br />
| the referenced person is a spouse of the person represented by the current document<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| statechart<br />
| external resource<br />
| not allowed<br />
| A reference to an SCXML document that controls the application-flow of the current HTML document<br />
| [http://www.w3.org/TR/scxml/ SCXML]<br />
|<br />
| Proposal<br />
|-<br />
| stylesheet<br />
|colspan=6| See HTML5<br />
|-<br />
| sweetheart<br />
| hyperlink<br />
| hyperlink<br />
| this person considers the referenced person to be their sweetheart<br />
| [http://gmpg.org/xfn/11 XFN]<br />
| <br />
| Accepted<br />
|-<br />
| tag<br />
|colspan=6| See HTML5<br />
|-<br />
| technicalauthor<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) responsible for the technical construction of the page (i.e. the HTML/CSS/PHP code), not for the content.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| timesheet<br />
| external resource<br />
| not allowed<br />
| SMIL Timesheet<br />
| [http://www.w3.org/TR/timesheets/#smilTimesheetsNS-Elements-Timesheet SMIL Timesheets 1.0]<br />
| <br />
| Proposal<br />
|-<br />
| translatedfrom<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email that has been translation source for the current document. It also indicates that the current document is a translation and not an original work.<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| translator<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) responsible for the translation of the page. It also indicates that the current page is a translation of an other document, which should be linked through a rel="translatedfrom".<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| up<br />
|colspan=6| See HTML5<br />
|-<br />
| us<br />
| hyperlink<br />
| hyperlink<br />
| The referenced document represents the same organisation as does the current document [cf rel-me]<br />
| <br />
| <br />
| Proposal<br />
|-<br />
| webmaster<br />
| hyperlink<br />
| hyperlink<br />
| The linked document is the page/email an agent (people or firm or...) available for requests about the content of the page.<br />
| <br />
| maintainer<br />
| Proposal<br />
|-<br />
| widget<br />
| hyperlink<br />
| hyperlink<br />
| Points to a widget.<br />
| [http://dev.w3.org/2006/waf/widgets/Overview.html#autodiscovery Widgets 1.0 Editor's draft]<br />
| <br />
| Proposal<br />
|-<br />
| wlwmanifest<br />
| hyperlink<br />
| not allowed<br />
| A link to a manifest for Windows Live Writer.<br />
| [http://msdn.microsoft.com/en-us/library/bb463263.aspx msdn]<br />
| <br />
| Proposal<br />
|}<br />
<br />
The "Effect on... link" column must either say "not allowed" if the rel value is not allowed on &lt;link> elements, "hyperlink" if the rel value creates a hyperlink, or "external resource" if the rel value creates a link to an external resource.<br />
<br />
The "Effect on... a and area" column must either say "not allowed" or "hyperlink".<br />
<br />
For the "Status" section to be changed to "Accepted", the proposed keyword must either have been through the [http://microformats.org/wiki/process Microformats process], and been approved by the Microformats community; or must be defined by a W3C specification in the Candidate Recommendation or Recommendation state. If it fails to go through this process, it is "Rejected".<br />
<br />
For more details, see [http://whatwg.org/specs/web-apps/current-work/#linkTypes the HTML5 specification]. See also [http://microformats.org/wiki/existing-rel-values the Microformats wiki page on this matter].</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Longdesc_usage&diff=5017Longdesc usage2010-07-06T05:19:49Z<p>TheresaOConnor: Reverted edits by Vsimon213 (talk) to last revision by Tantek</p>
<hr />
<div>This is an analysis of how the <img longdesc=""> attribute is used in the wild, based on the list of 62 pages which used the attribute, available at:<br />
http://canvex.lazyilluminati.com/survey/2007-07-17/analyse.cgi/pages/tagattr/img/longdesc<br />
<br />
The document list is included at the end of this page, numbered. When referring to pages, I just use their number.<br />
<br />
== Errors ==<br />
<br />
* 3, 10, 27, 31, and 46 were redirects; I did not check the pages their pointed to.<br />
* 22, 35, and 37 no longer have the string "longdesc" in them. <br />
<br />
== Results ==<br />
<br />
A large number of the pages were from Wikipedia (or other MediaWiki installations): 1, 2, 6, 9, 11, 17, 19, 21, 24, 25, 29, 30, 36, 43, 45, 54, and 59. MediaWiki has a way of using longdesc particular to itself. Ignoring MediaWiki results:<br />
<br />
* 2 pages used longdesc="" (5, 42)<br />
* 3 pages used longdesc="..." linking to an image of some description (41, 44, 56)<br />
* 12 pages used longdesc="..." not as an URL, but as a human-readable description:<br />
** 4 of which look like SEO attempts (13, 18, 48, 61)<br />
** 3 of which used the same string as they used for alt text (7, 23, 53)<br />
** 3 of which has different alt and longdesc text (16, 28, 52)<br />
** 1 of which used the same string as they did for title="" (15)<br />
** 1 of which used URL-escaped text (49)<br />
** 1 of which is in Russian, which I don't understand (32)<br />
* 20 pages used longdesc="..." as an URL:<br />
** 11 of which point to a location the same as one pointed to with a link nearby (20, 33, 34, 38, 40, 47, 50, 55, 57, 58, 60)<br />
** 4 of which are broken links (4, 14, 26, 57)<br />
** 2 of which are valid links but seems not to comply with the spec (12, 39)<br />
** 2 of which is a correct use of the element (51, 62)<br />
** 1 of which seems to be better dealt with as a hyperlink rather than a longdesc attribute (8)<br />
<br />
On 51, ironically, the only longdesc attribute is used on a link to an automated accessibility checker's website. 62 seems to serve up rather unhelpful text/plain one-liners for longdesc, claiming to be accessible made by a company that does accessible web design.<br />
<br />
== Links list ==<br />
<br />
1: http://fr.wikipedia.org/wiki/Francesco_Borromini<br><br />
2: http://en.wikipedia.org/wiki/Motivation<br><br />
3: http://www.schirmer.com/composers/schoenberg_essay.html<br><br />
4: http://www.huntingtonhousing.com<br><br />
5: http://osierra.com<br><br />
6: http://ru.wikipedia.org/wiki/%D0%98%D1%81%D1%82%D0%BE%D1%80%D0%B8%D1%8F_%D0%90%D1%80%D0%BC%D0%B5%D0%BD%D0%B8%D0%B8 <br><br />
7: http://www.norwalkoh.com/<br><br />
8: http://www.domnowski.de/<br><br />
9: http://de.wikipedia.org/wiki/Morscheid<br><br />
10: http://www.eng.rpi.edu<br><br />
11: http://en.wikipedia.org/wiki/Transport_in_Yemen<br><br />
12: http://www.aclu-ia.org/<br><br />
13: http://airbrush-tanning.us<br><br />
14: http://www.pr-photography.org/<br><br />
15: http://www.shakedown.fi/<br><br />
16: http://www.vds.org.uk<br><br />
17: http://it.wikipedia.org/wiki/Voghiera<br><br />
18: http://www.babylaundryboutique.com/<br><br />
19: http://de.wikipedia.org/wiki/D%C3%A4nische_Sprache<br><br />
20: http://www.coastal-fisherman.com/<br><br />
21: http://fr.wikipedia.org/wiki/Anthemius_de_Tralles<br><br />
22: http://www.hometown.aol.co.uk/thewoburnrally/<br><br />
23: http://www.oblates.us/spiritual_directory.htm<br><br />
24: http://en.wikipedia.org/wiki/Sint_Maarten_national_football_team<br><br />
25: http://en.wikipedia.org/wiki/Long_Grove,_Iowa<br><br />
26: http://www.integracomunicaciones.com/<br><br />
27: http://www.bayern-evangelisch.de/<br><br />
28: http://www.almaprnjavorac.com<br><br />
29: http://en.wikipedia.org/wiki/Osage,_Iowa<br><br />
30: http://en.wikipedia.org/wiki/Bob_Menendez<br><br />
31: http://weatheroffice.ec.gc.ca/city/pages/qc-150_metric_e.html<br><br />
32: http://www.paralife.narod.ru<br><br />
33: http://www.jagdhof.com<br><br />
34: http://www.austria-lustenau.at/<br><br />
35: http://www.expressrealestateschool.com<br><br />
36: http://de.wikipedia.org/wiki/Guckheim<br><br />
37: http://www.vivian-cat.narod.ru/<br><br />
38: http://www.svirp.dk/<br><br />
39: http://www.francedirect.net<br><br />
40: http://www.pointvue.com/cis/<br><br />
41: http://www.arabicdancer.co.uk/<br><br />
42: http://kepek.utcaigyorsulas.hu<br><br />
43: http://es.wikipedia.org/wiki/Tomatina<br><br />
44: http://www.stopitnow.com/<br><br />
45: http://en.wikipedia.org/wiki/THEOS<br><br />
46: http://www.wirtschaft.fh-gelsenkirchen.de/<br><br />
47: http://www.sannong.com<br><br />
48: http://www.integrated-robotics.com<br><br />
49: http://www.waveney.gov.uk/<br><br />
50: http://www.libraryspot.com/<br><br />
51: http://www.teachers.ash.org.au/aussieed/<br><br />
52: http://www.webmeister.dk<br><br />
53: http://www.magicdomico.com/<br><br />
54: http://es.wikipedia.org/wiki/Azerbaiy%C3%A1n<br><br />
55: http://www.puntoluce.tv/<br><br />
56: http://www.bss-ev.de/<br><br />
57: http://www.lowvillegolf.com/<br><br />
58: http://www.brandunity.com/<br><br />
59: http://en.wikipedia.org/wiki/Minos<br><br />
60: http://www.cotondetulear.be/<br><br />
61: http://www.granhotelguadalpinbanus.com<br><br />
62: http://www.libertas-solutions.com<br />
<br />
== See Also ==<br />
* [[Change_Proposal_for_not_including_longdesc]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Main_Page&diff=4904Main Page2010-05-27T14:37:29Z<p>TheresaOConnor: Reverted edits by RonD (talk) to last revision by Hixie</p>
<hr />
<div>Welcome to the WHATWG Wiki!<br />
<br />
You can be a part of our community, making proposals for the next version of HTML5. This wiki is made available for you for drafting proposals, for writing essays, for keeping track of HTML-related issues, and so forth. Anyone can create an account and contribute content.<br />
<br />
Before you begin, you may wish to read our [[WHATWG Wiki:Contribution Guidelines|contribution guidelines]].<br />
<br />
==Purpose==<br />
The purpose of the WHATWG Wiki is to create a place for WHATWG contributors to post and compile their own proposals and ideas regarding WHATWG specifications. The specifications themselves will not be available for editing via this wiki. However, ideas you post here may find their way into current and future WHATWG specifications.<br />
<br />
== Main sections and Quick links ==<br />
* [[FAQ]]<br />
* [[Implementations]]<br />
* [[What you can do]] — '''[[Reviewing HTML5|Help us review HTML5!]]<br />
* [[Authoring|Using HTML 5 in your Web site]]<br />
* [[HTML vs. XHTML]]<br />
* [[HTML5 Presentations]]<br />
* [[Spec coordination]]<br />
* [[IDE]]<br />
* [[Testsuite]]<br />
<br />
==WHATWG Specifications==<br />
* [[HTML5]]<br />
* [[Web Workers]]<br />
* See also [[FAQ#What_are_the_various_versions_of_the_spec.3F|What are the various versions of the spec?]] in the FAQ.<br />
<br />
==Communicating with the community==<br />
The WHATWG community has several channels of communication:<br />
* [http://www.whatwg.org/mailing-list Mailing lists]<br />
* [http://blog.whatwg.org/ The blog], including [http://blog.whatwg.org/category/whats-next Mark Pilgrim's column "What's next in HTML5"]<br />
* [http://www.w3.org/html/planet/ W3C's "HTML5 planet"]<br />
* [http://forums.whatwg.org/ The forum]<br />
* [[IRC]]<br />
* [http://wiki.whatwg.org/ This wiki]<br />
<br />
== Research and data ==<br />
Research pertaining to and data on publishing behavior for various bits of markup, used to help drive decisions made in/for HTML5 for specific elements and attributes.<br />
<br />
* [[timed tracks]]<br />
* [[cite]]<br />
* [[time]] <br />
* [[charset]] <br />
* [[summary]]<br />
<br />
These pages may also be of interest:<br />
<br />
* [[Issue Discussion]]<br />
* [[Feature Proposals]]<br />
* [[Presentational elements and attributes]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=User:TheresaOConnor&diff=4760User:TheresaOConnor2010-04-29T16:42:15Z<p>TheresaOConnor: fix markup</p>
<hr />
<div><div class="vcard">I'm <span class="fn">Edward O'Connor</span>. <ul><li class="url">http://edward.oconnor.cx/</li><li class="email">hober0@gmail.com</li></ul></div><br />
<br />
In addition to keeping an eye on wiki spam, I occasionally [[Special:Contributions/EdwardOConnor|contribute to this wiki]].<br />
<br />
You might also be interested in [http://www.w3.org/html/wg/wiki/Special:Contributions/Eoconnor my contributions to the HTML WG wiki].<br />
<br />
----<br />
{{cc-public-domain-release}}</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=User:TheresaOConnor&diff=4759User:TheresaOConnor2010-04-29T16:40:56Z<p>TheresaOConnor: add more contact info.</p>
<hr />
<div><div class="vcard">I'm <span class="fn">Edward O'Connor</span>. <ul><li>My home page: <a class="url" href="http://edward.oconnor.cx/">http://edward.oconnor.cx/</a></li><li><a href="mailto:hober0@gmail.com" class="email">hober0@gmail.com</a></li></ul></div><br />
<br />
In addition to keeping an eye on wiki spam, I occasionally [[Special:Contributions/EdwardOConnor|contribute to this wiki]].<br />
<br />
You might also be interested in [http://www.w3.org/html/wg/wiki/Special:Contributions/Eoconnor my contributions to the HTML WG wiki].<br />
<br />
----<br />
{{cc-public-domain-release}}</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=FAQ&diff=4721FAQ2010-04-26T20:18:07Z<p>TheresaOConnor: Reverted edits by Ilana (talk) to last revision by Hixie</p>
<hr />
<div>== The WHATWG ==<br />
<br />
=== What is the WHATWG? ===<br />
<br />
The Web Hypertext Application Technology Working Group (WHATWG) is a growing community of people interested in evolving the Web. It focuses primarily on the development of HTML and APIs needed for Web applications.<br />
<br />
The WHATWG was founded by individuals of Apple, the Mozilla Foundation, and Opera Software in 2004, after a W3C workshop. Apple, Mozilla and Opera were becoming increasingly concerned about the W3C’s direction with XHTML, lack of interest in HTML and apparent disregard for the needs of real-world authors. So, in response, these organisations set out with a mission to address these concerns and the Web Hypertext Application Technology Working Group was born.<br />
<br />
=== What is the WHATWG working on? === <br />
<br />
The WHATWG's main focus is HTML5. The WHATWG also works on Web Workers and occasionally specifications outside WHATWG space are discussed on the WHATWG mailing list and forwarded when appropriate.<br />
<br />
In the past it has worked on Web Forms 2.0 and Web Controls 1.0. Web Forms 2.0 has been integrated into HTML5 and Web Controls 1.0 has been abandoned for now, awaiting what [http://www.w3.org/TR/xbl/ XBL 2.0] will bring us.<br />
<br />
=== How can I get involved? === <br />
<br />
There are lots of ways you can get involved, take a look and see ''[[What you can do]]''!<br />
<br />
=== Is participation free? === <br />
<br />
Yes, everyone can contribute. There are no memberships fees involved, it's an open process. You may easily subscribe to the WHATWG [http://whatwg.org/mailing-list mailing lists]. You may also [http://blog.whatwg.org/w3c-restarts-html-effort join the the W3C's new HTMLWG] by going through the slightly longer application process.<br />
<br />
== The WHATWG Process ==<br />
<br />
=== How does the WHATWG work? ===<br />
<br />
People send e-mail to [http://www.whatwg.org/mailing-list#specs the mailing list]. The editor then reads that [http://www.whatwg.org/issues/ feedback] and, taking it into account along with research, studies, and feedback from many other sources (blogs, forums, IRC, etc) makes language design decisions intended to address everyone's needs as well as possible while keeping the language consistent.<br />
<br />
This continues, with people sending more feedback, until nobody is able to convince the editor to change the spec any more (e.g. because two people want opposite things, and the editor has considered all the information available and decided that one of the two proposals is the better one).<br />
<br />
This is not a consensus-based approach -- there's no guarantee that everyone will be happy! There is also no voting.<br />
<br />
There is a small oversight committee (known as the "WHATWG members", see the [http://www.whatwg.org/charter charter]) who have the authority to override or replace the editor if he starts making bad decisions.<br />
<br />
Currently the editor is Ian Hickson.<br />
<br />
=== How should tool developers, screen reader developers, browser vendors, search engine vendors, and other implementors interact with the WHATWG? ===<br />
<br />
Feedback on a feature should be sent to whatwg@whatwg.org (but you have to [http://whatwg.org/mailing-list#specs join the mailing list] first), or ian@hixie.ch. All feedback will receive a reply in due course.<br />
<br />
If you want feedback to be dealt with faster than "eventually", e.g. because you are about to work on that feature and need the spec to be updated to take into account all previous feedback, let the editor know by either e-mailing him (ian@hixie.ch), or contacting him on [[IRC]] (Hixie on Freenode). Requests for priority feedback handling are handled confidentially so other implementors won't know that you are working on that feature.<br />
<br />
Questions and requests for clarifications should be asked either on the mailing list or on [[IRC]], in the #whatwg channel on Freenode.<br />
<br />
=== Is there a process for removing bad ideas from a specification? ===<br />
<br />
There are several processes by which we trim weeds from the specifications.<br />
<br />
* On a regular basis, especially around explicit call-for-comments, we go through every section and mark areas as being considered for removal. This happened early in 2008 with the data templates, repetition blocks, and DFN-element cross references, for example. If no feedback is received to give us strong reasons to keep such features, then they eventually are removed altogether.<br />
<br />
* Anyone can ask for a feature to be removed; such feedback is considered like all other feedback and is based on the merits of the arguments put forward.<br />
<br />
* If browsers don't widely implement a feature, or if authors don't use a feature, or if the uses of the feature are inconsequential or fundamentally wrong or damaging, then, after due consideration, features will be removed.<br />
<br />
Removing features is a critical part of spec development.<br />
<br />
=== Is there a process for adding new features to a specification? ===<br />
<br />
The process is rather informal, but basically boils down to this:<br />
# Research the use cases and requirements by discussing the issue with authors and implementors.<br />
# Come up with a clear description of the problem that needs to be solved.<br />
# Discuss your proposal with authors and implementors. Read the responses. Listen to the feedback. Consider whether your ideas are good solutions to the use cases and requirements put forward. Discussions here should be done in public, e.g. on an archived public mailing list or documented in blogs.<br />
# Get implementors to commit to implementing the feature. If you can't get several implementors to implement the feature, then get at least one user agent to implement it experimentally. Experimental implementations should be publicly available.<br />
# Bring the experimental implementations to the attention of the spec's editor. Document the experience found from any implementations, the use cases and requirements that were found in the first step, the data that the design was based on.<br />
# Demonstrate the importance of the problem. Demonstrate that the solution is one that will be used correctly and widely enough for it to solve the stated problem.<br />
# Participate in the subsequent design discussions, considering all the proposals carefully. Typically at this step the original design gets thrown out and a significantly better design is developed, informed by the previous research, new research, and implementation and author experience with experimental implementations. Sometimes, the idea is abandoned at this stage.<br />
<br />
If the idea survives the above design process, the spec will be eventually updated to reflect the new design. Implementations will then be updated to reflect the new design (if they aren't, that indicates the new design is not good, and it will be reworked or removed). The spec will be updated to fix the many problems discovered by authors and implementors, over a period of several years, as more authors and implementors are exposed to the design. Eventually, a number of provably interoperable implementations are deployed. At this point development of the feature is somewhat frozen.<br />
<br />
Writing a comprehensive test suite is also an important step, which should start a bit before implementations start being written to the spec. (Test suites usually find as many problems with implementations as they do with the spec; they aren't just for finding browser bugs.) We don't yet have a good story with respect to test suites, sadly. If you want to help us out, let the mailing list know! Be aware, though, it's a lot of work.<br />
<br />
== HTML5 ==<br />
<br />
=== What is HTML5? === <br />
<br />
[http://www.whatwg.org/specs/web-apps/current-work/ HTML5] is the main focus of the WHATWG community and also that of the W3C HTML Working Group. HTML5 is a new version of HTML4, XHTML1, and DOM Level 2 HTML addressing many of the issues of those specifications while at the same time enhancing (X)HTML to more adequately address Web applications. Besides defining a markup language that can be written in both HTML (HTML5) and XML (XHTML5) it also defines many APIs that form the basis of the Web architecture. Some of these APIs were known as "DOM Level 0" and were never documented before. Yet they are extremely important for browser vendors to support existing Web content and for authors to be able to build Web applications.<br />
<br />
=== How can I keep track of changes to the spec? === <br />
<br />
There are a number of ways to track changes to the spec.<br />
<br />
* The specification is available in the [http://svn.whatwg.org/ subversion repository]. You may use any svn client to check out the latest version and use your clients diff tools in order compare revisions and see what has been changed.<br />
<br />
* You may use the online [http://html5.org/tools/web-apps-tracker (X)HTML5 Tracking tool]. The tool provides an online interface for selecting and comparing revisions of the spec.<br />
<br />
* There is a commit-watchers mailing list that is notified of every edit: http://lists.whatwg.org/listinfo.cgi/commit-watchers-whatwg.org<br />
<br />
* The W3C provide a Web view of their CVS mirror of the HTML5 spec: http://dev.w3.org/cvsweb/html5/spec/Overview.html<br />
<br />
* The W3C provide diff-marked HTML versions for each change that affect the W3C copy of the spec by e-mail: http://lists.w3.org/Archives/Public/public-html-diffs/latest<br />
<br />
* Non-editorial changes get broadcast on the WHATWG Twitter feed: http://twitter.com/WHATWG<br />
<br />
* All changes that affect the W3C copy of the spec get broadcast on the HTML5 Twitter feed: http://twitter.com/HTML5<br />
<br />
* The latest changes are visible in coloured diff form: http://whatwg.org/specs/web-apps/current-work/index-diff<br />
<br />
<br />
=== What are the various versions of the spec? ===<br />
<br />
All active work at WHATWG is gathered in the (very large) [http://www.whatwg.org/specs/web-apps/current-work/complete.html Web Applications 1.0] document.<br />
<br />
WHATWG HTML is a subset containing only the HTML-specific material. It is available as [http://www.whatwg.org/specs/web-apps/current-work/ single-page]<br />
and '''[http://whatwg.org/html multi-page]''', as well as in PDF [http://www.whatwg.org/specs/web-apps/current-work/html5-a4.pdf A4] and<br />
[http://www.whatwg.org/specs/web-apps/current-work/html5-letter.pdf Letter].<br />
<br />
The following table lists in the individual specifications included:<br />
<br />
{| class="wikitable" border=1 cellpadding=3 cellspacing=0<br />
|-<br />
!<br />
! WHATWG Specifications <br> (and sections therein)<br />
! Section links for <br> Web Applications 1.0<br />
! W3C/IETF Specifications<br />
|-<br />
! HTML5 only (excluding newer features)<br />
|<br />
|<br />
| [http://dev.w3.org/html5/spec/Overview.html Single-page], [http://dev.w3.org/html5/spec/spec.html Multi-page] (HTMLWG)<br />
|-<br />
! Microdata<br />
| [http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#microdata In WHATWG HTML]<br />
| [http://www.whatwg.org/specs/web-apps/current-work/complete.html#microdata Microdata]<br />
| [http://dev.w3.org/html5/md/Overview.html Microdata] (HTMLWG)<br />
|-<br />
! 2D Context<br />
| [http://www.whatwg.org/specs/web-apps/current-work/multipage/the-canvas-element.html#the-2d-context In WHATWG HTML]<br />
| [http://www.whatwg.org/specs/web-apps/current-work/complete.html#the-2d-context 2D Context]<br />
| [http://dev.w3.org/html5/2dcontext/Overview.html 2D Context] (HTMLWG)<br />
|-<br />
! Communications - Cross-document messaging<br />
| [http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html#crossDocumentMessages In WHATWG HTML]<br />
| [http://www.whatwg.org/specs/web-apps/current-work/complete.html#crossDocumentMessages Cross-document messaging]<br />
| [http://dev.w3.org/html5/postmsg/Overview.html#crossDocumentMessages Communications] (HTMLWG)<br />
|-<br />
! Communications - Channel messaging<br />
| [http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html#channel-messaging In WHATWG HTML]<br />
| [http://www.whatwg.org/specs/web-apps/current-work/complete.html#channel-messaging Channel messaging]<br />
| [http://dev.w3.org/html5/postmsg/Overview.html#channel-messaging Communications] (HTMLWG)<br />
|-<br />
! Device Element<br />
| [http://www.whatwg.org/specs/web-apps/current-work/multipage/commands.html#devices In WHATWG HTML]<br />
| [http://www.whatwg.org/specs/web-apps/current-work/complete.html#devices Device]<br />
| [http://dev.w3.org/html5/html-device/ HTML Device] (HTMLWG)<br />
|-<br />
! Web Workers<br />
| [http://www.whatwg.org/specs/web-workers/current-work/ Web Workers specification]<br />
| [http://www.whatwg.org/specs/web-apps/current-work/complete.html#workers Web Workers]<br />
| [http://dev.w3.org/html5/workers/Overview.html Web Workers] (WebApps WG)<br />
|-<br />
! Web Storage<br />
|<br />
| [http://www.whatwg.org/specs/web-apps/current-work/complete.html#webstorage Web Storage]<br />
| [http://dev.w3.org/html5/webstorage/ Web Storage] (WebApps WG)<br />
|-<br />
! Web Sockets API<br />
|<br />
| [http://www.whatwg.org/specs/web-apps/current-work/complete.html#network Web Sockets API]<br />
| [http://dev.w3.org/html5/websockets/ Web Sockets API] (WebApps WG)<br />
|-<br />
! Web Sockets Protocol<br />
|<br />
| [http://www.whatwg.org/specs/web-apps/current-work/complete.html#websocket-protocol Web Sockets Protocol]<br />
| [http://www.whatwg.org/specs/web-socket-protocol/ The Web Socket Protocol] (IETF)<br />
|-<br />
! Server-Sent Events<br />
|<br />
| [http://www.whatwg.org/specs/web-apps/current-work/complete.html#server-sent-events Server-sent Events]<br />
| [http://dev.w3.org/html5/eventsource/ Server-sent Events] (WebApps WG)<br />
|-<br />
! Web SQL Database (stalled)<br />
|<br />
|<br />
| [http://dev.w3.org/html5/webdatabase/ Web SQL Database] (WebApps WG)<br />
|}<br />
<br />
<br />
All of the above are generated from one [http://www.whatwg.org/specs/web-apps/current-work/source source document].<br />
<br />
=== Are there versions of the specification aimed specifically at authors/implementors? ===<br />
<br />
There are no standalone author or implementor specifications. However, the WHATWG HTML and the HTML5 specifications (and their multipage versions) can be customized to either hide or emphasize user-agent-specific material. The mode can be selected using radio buttons at the top right of those documents.<br />
<br />
It is also possible to toggle the mode by changing the URL, here is an example for the multipage WHATWG HTML specification:<br />
<br />
* As a normal spec: http://www.whatwg.org/specs/web-apps/current-work/multipage/?style=complete<br />
* Author view (hiding the user-agent-specific material): http://www.whatwg.org/specs/web-apps/current-work/multipage/?style=author<br />
* Implementor view (highlighting the user-agent-specific material): http://www.whatwg.org/specs/web-apps/current-work/multipage/?style=highlight<br />
<br />
=== When will we be able to start using these new features? ===<br />
<br />
You can use some of them now. Others might take a few more years to get widely implemented. Here are some sites that might help you work out what you can use in the meantime:<br />
<br />
* http://diveintohtml5.org/<br />
<br />
If you know of any more (or if you have some yourself) then add them to the list! If there are some on the list that aren't very useful compared to the rest, them remove them!<br />
<br />
=== When will HTML5 be finished? ===<br />
<br />
"Finished" is a big deal... You'll be able to use HTML5 long before then. See [[FAQ#When_will_we_be_able_to_start_using_these_new_features.3F|When will we be able to start using these new features?]]<br />
<br />
It is estimated by the editor that HTML5 will reach the W3C Candidate Recommendation stage during 2012. That doesn't mean you can't start using it yet, though. Different parts of the specification are at different maturity levels. Some sections are already relatively stable and there are implementations that are already quite close to completion, and those features can be used today (e.g. &lt;canvas&gt;). But other sections are still being actively worked on and changed regularly, or not even written yet.<br />
<br />
'''You can see annotations in the margins showing the estimated stability of each section.'''<br />
<br />
The possible states are:<br />
<br />
* ''Idea; yet to be specified'' -- the section is a placeholder.<br />
* ''First draft'' -- An early stage.<br />
* ''Working draft'' -- An early stage, but more mature than just "first draft".<br />
* ''Last call for comments'' -- The section is nearly done, but there may be feedback still to be processed. Send feedback sooner rather than later, or it might be too late.<br />
* ''Awaiting implementation feedback'' -- The section is basically done, but might change in response to feedback from implementors. Major changes are unlikely past this point unless it is found that the feature, as specified, really doesn't work well.<br />
* ''Implemented and widely deployed'' -- the feature is specified and complete. Once a section is interoperably implemented, it&#8217;s quite stable and unlikely to change significantly. Any changes to such a section would most likely only be editorial in nature, particularly if the feature is already in widespread use.<br />
<br />
There are also two special states:<br />
<br />
* ''Being edited right now'' -- the section is in high flux and is actively being edited. Contact Hixie on [[IRC]] if you have immediate feedback.<br />
* ''Being considered for removal'' -- for one reason or another, the section is being considered for removal. Send feedback soon to help with the decision.<br />
<br />
The point to all this is that you shouldn&#8217;t place too much weight on the status of the specification as a whole. You need to consider the stability and maturity level of each section individually.<br />
<br />
It is estimated, again by the editor, that HTML5 will reach a W3C recommendation in the year 2022 or later. This will be approximately 18-20 years of development, since beginning in mid-2004. That's actually not that crazy, though. Work on HTML4 started in the mid 90s, and HTML4 ''still'', more than ten years later, hasn't reached the level that we want to reach with HTML5. There is no real test suite, there are many parts of the spec that are lacking real implementations, there are big parts that aren't interoperable, and the spec has hundreds if not thousands of known errors that haven't been fixed. When HTML4 came out, REC meant something much less exciting than it does now.<br />
<br />
For a spec to become a REC today, it requires two 100% complete and fully interoperable implementations, which is proven by each successfully passing literally thousands of test cases (20,000 tests for the whole spec would probably be a conservative estimate). When you consider how long it takes to write that many test cases and how long it takes to implement each feature, you&#8217;ll begin to understand why the time frame seems so long.<br />
<br />
(In the interests of full disclosure, the W3C's [http://www.w3.org/2007/03/HTML-WG-charter.html#deliverables official line] is that the HTML5 spec will be complete, with interoperable implementations, in late 2010. However, that same timetable gave a date for First Public Working Draft that was eight months premature, and the W3C, as of the predicted date for the third milestone, Candidate Recommendation, had still not come anywhere near reaching the second milestone, Last Call. You can make your own judgements regarding the W3C timetable's credibility.)<br />
<br />
=== What about Microsoft and Internet Explorer? === <br />
<br />
Microsoft has already started implementing parts of HTML5 in IE8.<br />
<br />
HTML5 is being developed with compatibility with existing browsers in mind, though (including IE). Support for many features can be simulated using JavaScript.<br />
<br />
=== Is design rationale documented? ===<br />
<br />
Sort of. Often the documentation can be found in the mailing list or IRC channel archives. Sometimes an issue was raised formally, and resolution is recorded in the issue tracker. Sometimes, there is an explanation in the specification, but doing that everywhere would make the specification huge.<br />
<br />
For a few cases that someone did take the time document, the information can be found at the following locations:<br />
<br />
* [[Why no namespaces]]<br />
* [[Why no script implements]]<br />
* [[Why not reuse legend]]—or another ''mini-header'' element.<br />
<br />
Also see HTML5 feature proposals below.<br />
<br />
== HTML5 syntax issues ==<br />
<br />
=== Will HTML5 finally put an end to the XHTML as <code>text/html</code> debate? === <br />
<br />
Yes. Unlike HTML4 and XHTML1, the choice of HTML or XHTML is solely dependent upon the choice of the media type, rather than the DOCTYPE. See [[HTML vs. XHTML]]''<br />
<br />
=== What will the DOCTYPE be? === <br />
<br />
In HTML:<br />
<br />
<code>&lt;!DOCTYPE html&gt;</code><br />
<br />
In XHTML: no DOCTYPE is required and its use is generally unnecessary. However, you may use one if you want (see the following question). Note that the above is well-formed XML and so it may also appear in XHTML documents.<br />
<br />
For compatibility with legacy producers designed for outputting HTML, but which are unable to easily output the above DOCTYPE, this alternative legacy-compat version may be used instead.<br />
<br />
<code>&lt;!DOCTYPE html SYSTEM "about:legacy-compat"&gt;</code><br />
<br />
Note that this is '''not''' intended for dealing with any compatibility issues with legacy browsers. It is meant for legacy authoring tools only.<br />
<br />
Excluding the string <code>"about:legacy-compat"</code>, the DOCTYPE is case insensitive in HTML. In XHTML, it is case sensitive and must be either of the two variants given above. For this reason, the DOCTYPEs given above are recommended to be used over other case variants, such as <code>&lt;!DOCTYPE HTML&gt;</code> or <code>&lt;!doctype html&gt;</code>.<br />
<br />
These alternatives were chosen because they meet the following criteria:<br />
<br />
* They trigger standards mode in all current and all relevant legacy browsers.<br />
* They are well-formed in XML and can appear in XHTML documents.<br />
* It is possible to output at least one of the alternatives, if not both, with extant markup generators.<br />
* They intentionally contain no language version identifier so the DOCTYPE will remain usable for all future revisions of HTML.<br />
* The first is short and memorable to encourage its use.<br />
* The legacy-compat DOCTYPE is intentionally unattractive and self descriptive of purpose to discourage unnecessary use.<br />
<br />
=== Under what conditions should a DOCTYPE be used in XHTML? ===<br />
<br />
Generally, the use of a DOCTYPE in XHTML is unnecessary. However, there are cases where inclusion of a DOCTYPE is a reasonable thing to do:<br />
<br />
# The document is intended to be a polyglot document that may be served as both HTML or XHTML.<br />
# You wish to declare entity references for use within the document. Note that most browsers only read the internal subset and do not retrieve external entities. (This is not compatible with HTML, and thus not suitable for polyglot documents.)<br />
# You wish to use a custom DTD for DTD-based validation. But take note of [http://about.validator.nu/#faq what's wrong with DTDs].<br />
<br />
=== How are pre-HTML5 documents parsed? ===<br />
<br />
All documents with a text/html media type (that is, including those without or with an HTML 2.0, HTML 3.2, HTML4, or XHTML1 DOCTYPE) will be parsed using the same parser algorithm as defined by HTML5. This matches what Web browsers have done for HTML documents so far and keeps code complexity down. That in turn is good for security, maintainability, and in general keeping the amount of bugs down. The HTML syntax of HTML5 therefore does not require a new parser and documents with an HTML4 DOCTYPE for example will be parsed using the HTML5 parser.<br />
<br />
Validators are allowed to have different code paths for previous levels of HTML.<br />
<br />
=== If there is no DTD, how can I validate my page? === <br />
<br />
With an [http://validator.whatwg.org/ HTML5 validator].<br />
<br />
=== What is an HTML Serialization? === <br />
<br />
The HTML serialization refers to the syntax of an HTML document defined in HTML5. The syntax is inspired by the SGML syntax from earlier versions of HTML, bits of XML (e.g. allowing a trailing slash on void elements, xmlns attributes), and reality of deployed content on the Web.<br />
<br />
Any document whose MIME type is determined to be <code>text/html</code> is considered to be an HTML serialization and must be parsed using an HTML parser.<br />
<br />
=== What is an XML (or XHTML) Serialization? === <br />
<br />
The XML Serialization refers to the syntax defined by XML 1.0 and Namespaces in XML 1.0. A resource that has an XML MIME type, such as <code>application/xhtml+xml</code> or <code>application/xml</code>, is an XML document and if it uses elements in the HTML namespace, it contains XHTML. If the root element is &#8220;html&#8221; in the HTML namespace, the document is referred to as an XHTML document.<br />
<br />
=== What MIME type does HTML5 use? === <br />
<br />
The HTML serialization ''must'' be served using the <code>text/html</code> MIME type.<br />
<br />
The XHTML serialization ''must'' be served using an XML MIME type, such as <code>application/xhtml+xml</code> or <code>application/xml</code>. Unlike XHTML1, XHTML5 ''must not'' be served as <code>text/html</code>.<br />
<br />
Using the incorrect MIME type (<code>text/html</code>) for XHTML will cause the document to be parsed according to parsing requirements for HTML. In other words, it will be treated as tag soup. Ensuring the use of an XML MIME type is the only way to ensure that browsers handle the document as XML.<br />
<br />
=== Should I close empty elements with <code>/&gt;</code> or <code>&gt;</code>? === <br />
<br />
Void elements in HTML (e.g. the <code>br</code>, <code>img</code> and <code>input</code> elements) do not require a trailing slash. e.g. Instead of writing <code>&lt;br /&gt;</code>, you only need to write <code>&lt;br&gt;</code>. This is the same as in HTML4. However, due to the widespread attempts to use XHTML1, there are a significant number of pages using the trailing slash. Because of this, the trailing slash syntax has been permitted on void elements in HTML in order to ease migration from XHTML1 to HTML5.<br />
<br />
HTML5 also introduces the ability to embed MathML elements. On elements inside a <code>math</code> element the trailing slash works just like it does in XML. I.e. it closes the element. This is only inside that context however, it does not work for normal HTML elements.<br />
<br />
=== If I&#8217;m careful with the syntax I use in my HTML document, can I process it with an XML parser? === <br />
<br />
No, HTML and XML have [[HTML_vs._XHTML#Differences_Between_HTML_and_XHTML|many significant differences]], particularly parsing requirements, and you cannot process one using tools designed for the other. However, since HTML5 is defined in terms of the DOM, in most cases there are both HTML and XHTML serializations available that can represent the same document. There are, however, a few differences explained later that make it impossible to represent some HTML documents accurately as XHTML and vice versa. <br />
<br />
If you wish to process an HTML document as XHTML, it requires that you and convert it into XHTML first; and vice versa for processing XHTML as HTML.<br />
<br />
=== What is the namespace declaration? === <br />
<br />
In XHTML, you are required to specify the [http://www.w3schools.com/xml/xml_namespaces.asp namespace.]<br />
<br />
&lt;html xmlns="http://www.w3.org/1999/xhtml"&gt;<br />
<br />
In HTML, the <code>xmlns</code> attribute is currently allowed on any HTML element, but only if it has the value &#8220;<code>http://www.w3.org/1999/xhtml</code>&#8220;. It doesn&#8217;t do anything at all, it is merely allowed to ease migration from XHTML1. It is not actually a namespace declaration in HTML, because HTML doesn&#8217;t yet support namespaces. See the question [[FAQ#Will_there_be_support_for_namespaces_in_HTML.3F|will there be support for namespaces in HTML]].<br />
<br />
=== Will there be support for namespaces in HTML? === <br />
<br />
HTML5 is being defined in terms of the DOM and during parsing of a text/html all HTML elements will be automatically put in the HTML namespace, <code>http://www.w3.org/1999/xhtml</code>. However, unlike the XHTML serialization, there is no real namespace syntax available in the HTML serialization (see previous question). In other words, you do not need to declare the namespace in your HTML markup, as you do in XHTML. However, you are permitted to put an <code>xmlns</code> attribute on each HTML element as long as the namespace is <code>http://www.w3.org/1999/xhtml</code>.<br />
<br />
In addition, the HTML syntax provides for a way to embed elements from MathML and SVG. Elements placed inside the container element <code>math</code> or <code>svg</code> will automatically be put in the MathML namespace or the SVG namespace, respectively, by the parser. Namespace syntax is not required, but again an <code>xmlns</code> attribute is allowed if its value is the right namespace.<br />
<br />
In conclusion, while HTML5 does not allow the XML namespace syntax, there is a way to embed MathML and SVG and the xmlns attribute can be used on any element under the given constraints, in a way that is reasonably compatible on the DOM level.<br />
<br />
=== How do I specify the character encoding? === <br />
<br />
For HTML, it is strongly recommended that you specify the encoding using the HTTP <code>Content-Type</code> header. If you are unable to [http://www.w3.org/International/O-HTTP-charset configure your server] to send the correct headers, then you may use the <code>meta</code> element:<br />
<br />
&lt;meta charset="UTF-8"&gt;<br />
<br />
The following restrictions apply to character encoding declarations:<br />
<br />
* The character encoding name given must be the name of the character encoding used to serialize the file.<br />
* The value must be a [http://www.iana.org/assignments/character-sets valid character encoding name], and must be the preferred name for that encoding.<br />
* The character encoding declaration must be serialized without the use of character references or character escapes of any kind.<br />
* The <code>meta</code> element used for this purpose must occur within the first 512 bytes of the file. It is considered good practice for this to be the first child of the <code>head</code> element so that it is as close to the beginning of the file as possible.<br />
<br />
Note that this <code>meta</code> element is different from HTML 4, though it is compatible with many browsers because of the way encoding detection has been implemented.<br />
<br />
For polyglot documents, which may be served as either HTML or XHTML, you may also include that in XHTML documents, but only if the encoding is "UTF-8".<br />
<br />
To ease transition from HTML4 to HTML5, although the former is the recommended syntax, you may also use the following. (This does not apply to XHTML or polyglot documents)<br />
<br />
&lt;meta http-equiv="Content-Type" content="text/html; charset=UTF-8"&gt;<br />
<br />
In XHTML, XML rules for determining the character encoding apply. The meta element is never used for determining the encoding of an XHTML document (although it may appear in UTF-8 encoded XHTML documents). You should use either the HTTP <code>Content-Type</code> header or the XML declaration to specify the encoding.<br />
<br />
&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;<br />
<br />
Otherwise, you must use the default of <code>UTF-8</code> or <code>UTF-16</code>. It is recommended that you use <code>UTF-8</code>.<br />
<br />
=== What are the differences between HTML and XHTML? === <br />
<br />
See the list of [[HTML vs. XHTML#Differences_Between_HTML_and_XHTML|differences between HTML and XHTML]] in the wiki.<br />
<br />
=== What are best practices to be compatible with HTML DOM and XHTML DOM? ===<br />
<br />
Though the intent is that HTML and XHTML can both produce identical DOMs, there still are some differences between working with an HTML DOM and an XHTML one.<br />
<br />
Case sensitivity :<br />
* Whenever possible, avoid testing Element.tagName and Node.nodeName (or do toLowerCase() before testing).<br />
Namespaces:<br />
* Use the namespace-aware version for creating elements: Document.createElementNS(ns, elementName)<br />
<br />
=== Why does HTML5 legitimise tag soup? === <br />
<br />
Actually it doesn&#8217;t. This is a misconception that comes from the confusion between conformance requirements for documents, and the requirements for user agents.<br />
<br />
Due to the fundamental design principle of supporting existing content, the spec must define how to handle all HTML, regardless of whether documents are conforming or not. Therefore, the spec defines (or will define) precisely how to handle and recover from erroneous markup, much of which would be considered tag soup.<br />
<br />
For example, the spec defines algorithms for dealing with syntax errors such as incorrectly nested tags, which will ensure that a well structured DOM tree can be produced.<br />
<br />
Defining that is essential for one day achieving interoperability between browsers and reducing the dependence upon reverse engineering each other.<br />
<br />
However, the conformance requirements for authors are defined separately from the processing requirements. Just because browsers are required to handle erroneous content, it does not make such markup conforming.<br />
<br />
For example, user agents will be required to support the marquee element, but authors must not use the marquee element in conforming documents.<br />
<br />
It is important to make the distinction between the rules that apply to user agents and the rules that apply to authors for producing conforming documents. They are completely orthogonal.<br />
<br />
== HTML5 feature proposals ==<br />
<br />
=== HTML5 should support <code>href</code> on any element! === <br />
<br />
The spec allows &lt;a&gt; to contain blocks. It doesn't support putting href="" on any element, though.<br />
<br />
Supporting <code>href</code> on any element has several problems associated with it that make it difficult to support in HTML5. The main reason this isn't in HTML5 is that browser vendors have reported that implementing it would be extremely complex. Browser vendors get to decide what they implement, and there's no point to us telling them to do something they aren't going to do. In addition:<br />
<br />
* It isn&#8217;t backwards compatible with existing browsers.<br />
* It adds no new functionality that can&#8217;t already be achieved using the <code>a</code> element and a little script.<br />
* It doesn&#8217;t make sense for all elements, such as interactive elements like <code>input</code> and <code>button</code>, where the use of href would interfere with their normal function.<br />
<br />
The only advantage it seems to add is that it reduces typing for authors in some cases, but that is not a strong enough reason to support it in light of the other reasons.<br />
<br />
Wrapping &lt;a&gt; elements around blocks solves most use cases. It doesn't handle making rows in tables into links, though; for those just do something like this instead:<br />
<pre><br />
<tr onclick="location = this.getElementsByTagName('a')[0]"> ... </tr><br />
</pre><br />
<br />
=== HTML5 should support list headers! ===<br />
<br />
You can give a header to a list using the <figure> and <legend> elements:<br />
<br />
<pre><br />
<figure><br />
<legend>Apples</legend><br />
<ul><br />
<li>Granny Smith</li><br />
<li>Evil Apple of Knowledge</li><br />
<li>Apple, Inc</li><br />
</ul><br />
</figure><br />
</pre><br />
<br />
You can also label a group of lists using a definition list:<br />
<br />
<pre><br />
<dl><br />
<dt>Dry:</dt><br />
<dd><br />
<ul> <br />
<li>1c flour</li> <br />
<li>1/4c sugar</li><br />
<li>1tsp baking soda</li><br />
</ul><br />
</dd><br />
<dt>Wet:</dt><br />
<dd><br />
<ul> <br />
<li>1 egg </li><br />
<li>1/2c milk</li><br />
<li>1tsp vanilla extract</li><br />
</ul><br />
</dd><br />
</dl><br />
</pre><br />
<br />
These techniques are preferred over adding an <lh> element as proposed in the old HTML3 draft, mostly because of thorny issues with parsing near &lt;li> elements.<br />
<br />
=== HTML5 should support a way for anyone to invent new elements! ===<br />
<br />
There are actually quite a number of ways for people to invent their own extensions to HTML:<br />
<br />
* Authors can use the ''class'' attribute to extend elements, effectively creating their own elements, while using the most applicable existing "real" HTML element, so that browsers and other tools that don't know of the extension can still support it somewhat well. This is the tack used by Microformats, for example.<br />
* Authors can include data for scripts to process using the ''data-*=""'' attributes. These are guaranteed to never be touched by browsers, and allow scripts to include data on HTML elements that scripts can then look for and process.<br />
* Authors can use the ''<meta name="" content="">'' mechanism to include page-wide metadata. Names should be registered on the wiki's [[MetaExtensions]] page.<br />
* Authors can use the ''rel=""'' mechanism to annotate links with specific meanings. This is also used by Microformats. Names should be registered on the wiki's [[RelExtensions]] page.<br />
* Authors can embed raw data using the ''<script type="">'' mechanism with a custom type, for further handling by a script.<br />
* Authors can create plugins and invoke them using the ''<embed>'' element. This is how Flash works.<br />
* Authors can extend APIs using the JS prototyping mechanism. This is widely used by script libraries, for instance.<br />
* Authors can use the microdata feature (the item="" and itemprop="" attributes) to embed nested name-value pairs of data to be shared with other applications and sites.<br />
* Authors can propose new elements and attributes to the working group and, if the wider community agrees that they are worth the effort, they are added to the language. (If an addition is urgent, please let us know when proposing it, and we will try to address it quickly.)<br />
<br />
There is currently no mechanism for introducing new proprietary features in HTML documents (i.e. for introducing new elements and attributes) without discussing the extension with user agent vendors and the wider Web community. This is intentional; we don't want user agents inventing their own proprietary elements and attributes like in the "bad old days" without working with interested parties to make sure their feature is well designed.<br />
<br />
We request that people not invent new elements and attributes to add to HTML without first contacting the working group and getting a proposal discussed with interested parties.<br />
<br />
=== HTML5 should group &lt;dt>s and &lt;dd>s together in <di>s! === <br />
<br />
This is a styling problem and should be fixed in CSS. There's no reason to add a grouping element to HTML, as the semantics are already unambiguous.<br />
<br />
=== Why are some presentational elements like &lt;b>, &lt;i> and &lt;small> still included? ===<br />
<br />
The inclusion of these elements is a largely pragmatic decision based upon their widespread usage, and their usefulness for use cases which are not covered by more specific elements.<br />
<br />
While there are a number of common use cases for italics which are covered by more specific elements, such as emphasis (em), citations (cite), definitions (dfn) and variables (var), there are many other use cases which are not covered well by these elements. For example, a taxonomic designation, a technical term, an idiomatic phrase from another language, a thought, or a ship name.<br />
<br />
Similarly, although a number of common use cases for bold text are also covered by more specific elements such as strong emphasis (strong), headings (h1-h6) or table headers (th); there are others which are not, such as key words in a document abstract or product names in a review.<br />
<br />
Some people argue that in such cases, the span element should be used with an appropriate class name and associated stylesheet. However, the b and i elements provide for a reasonable fallback styling in environments that don't support stylesheets or which do not render visually, such as screen readers, and they also provide some indication that the text is somehow distinct from its surrounding content.<br />
<br />
In essence, they convey distinct, though non-specific, semantics, which are to be determined by the reader in the context of their use. In other words, although they don’t convey specific semantics by themselves, they indicate that that the content is somehow distinct from its surroundings and leaves the interpretation of the semantics up to the reader.<br />
<br />
This is further explained in the article <cite>[http://lachy.id.au/log/2007/05/b-and-i The &lt;b> and &lt;i> Elements]</cite><br />
<br />
Similarly, the small element is defined for content that is commonly typographically rendered in small print, and which often referred to as fine print. This could include copyright statements, disclaimers and other legal text commonly found at the end of a document.<br />
<br />
==== But they are PRESENTATIONAL! ====<br />
<br />
The problem with elements like &lt;font> isn't that they are ''presentational'' per se, it's that they are media-dependent (they apply to visual browsers but not to speech browsers). While &lt;b>, &lt;i> and &lt;small> historically have been presentational, they are defined in a media-independent manner in HTML5. For example, &lt;small> corresponds to the really quickly spoken part at the end of radio advertisements.<br />
<br />
=== The &lt;cite> element should allow names of people to be marked up ===<br />
<br />
From what some have seen, &lt;cite> is almost always used to mean "italics". More careful authors have used the element to mark up names and titles, and some people have gone out of their way to only mark up citations.<br />
<br />
So, we can't really decide what the element should be based on past practice, like we usually do.<br />
<br />
This leaves the question of what is the most useful use we can put the element to, if we keep it. The conclusion so far has been that the most useful use for &lt;cite> is as an element to allow typographic control over titles, since those are often made italics, and that semantic is roughly close to what it meant in previous versions, and happens to match at least one of the common uses for the element. Generally, however, names and titles aren't typeset the same way, so making the element apply to both would lead to confusing typography.<br />
<br />
There are already many ways of marking up names already (e.g. the [http://microformats.org/wiki/hcard hCard microformat], the microdata vCard vocabulary, &lt;span> and class names, etc), if you really need it.<br />
<br />
<strong>Note:</strong> research and opinions are being gathered that support the use of the &lt;cite> element to markup the names of speakers (e.g. for quotations). Please contribute yours:<br />
* [[Cite_element#examples_in_the_wild|cite element: examples in the wild of speakers marked up with cite]]<br />
* [[Cite_element#opinions|cite element: opinions on use of cite to markup names of speakers]]<br />
<br />
=== The &lt;time> element should allow vague times ("March") and times from ancient history to be marked up ===<br />
<br />
This has been discussed a number of times. For an overview of the topic, please see these e-mails:<br />
* http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-March/018888.html<br />
* http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-August/021745.html<br />
At this stage, as discussed in the second of those e-mails, the best way forward is to demonstrate that there are communities interested in solving this problem, by using existing techniques such as microdata to address it. If such a solution achieves a high adoption rate, that will substantially increase the strength of the proposals.<br />
<br />
=== &lt;input type="text"> needs a minlength="" attribute ===<br />
<br />
This has been discussed, but we are waiting for browsers to catch up with the many new form features before adding new ones like minlength="".<br />
<br />
== WHATWG and the W3C HTML WG ==<br />
<br />
=== Are there plans to merge the groups? ===<br />
<br />
Not especially. There are people who for a number of reasons are unable to join the W3C group, and there are others who are unable to join the WHATWG group. The editor is in both groups and takes all input into account -- and there are far more places where input on HTML5 is sent than just these two mailing lists (e.g. blogs, www-html@w3.org, forums, direct mail, meetings, etc).<br />
<br />
=== Which group has authority in the event of a dispute? ===<br />
<br />
The editor takes feedback from everyone into account and does not look at the source of those arguments for technical arguments.<br />
<br />
=== What is the history of HTML? ===<br />
<br />
Here are some documents that detail the history of HTML:<br />
* [http://esw.w3.org/topic/HTML/history HTML's timeline on the ESW wiki]<br />
* [http://www.whatwg.org/specs/web-apps/current-work/multipage/introduction.html#history0 The history section in HTML5 itself]<br />
<br />
== Web Workers ==<br />
<br />
Besides HTML5 the WHATWG works on [http://www.whatwg.org/specs/web-workers/current-work/ Web Workers]. It does this together with the W3C WebApps Working Group.<br />
<br />
== Mailing List ==<br />
<br />
=== Should I top-post or reply inline? ===<br />
<br />
Please reply inline or make the reply self-contained.<br />
<br />
Basically, please remove anything after the last line you have written, so that people don't have to scroll down to find out what else you wrote, and make sure that your e-mail makes sense on its own, as it will probably be read out of context years later.<br />
<br />
That is, you should reply like this:<br />
<br />
<pre><br />
Ian wrote:<br />
> What do you want? <br />
<br />
I want cats!<br />
<br />
> When do you want it?<br />
<br />
Now!<br />
</pre><br />
<br />
You should definitely not reply like this (because this requires people to read your e-mail backwards):<br />
<br />
<pre class="error" ><br />
No<br />
<br />
Ian wrote:<br />
> Is this a good example of how to post e-mails?<br />
</pre><br />
<br />
You should also not reply like this (because this leaves people to wonder if there is any text lower down that you have written):<br />
<br />
<pre class="error" ><br />
This is a bad way to write e-mail.<br />
<br />
Ian wrote:<br />
> Is this a good way to write e-mail?<br />
> Lorem ipsum foo bar baz.<br />
> Unrelated other bits that aren't replied to.<br />
> Yet more text<br />
</pre><br />
<br />
You should also not reply like this (with no context at all), because the reader will not know what you are referring to:<br />
<br />
<pre class="error" ><br />
No, I think that's a bad idea. It wouldn't be good for the readers, for instance.<br />
</pre><br />
<br />
Quote enough original text or provide an introduction yourself.<br />
<br />
If you use Outlook or Outlook Express, you can use either [http://home.in.tum.de/~jain/software/outlook-quotefix/ Outlook-QuoteFix] or [http://home.in.tum.de/~jain/software/oe-quotefix/ OE-QuoteFix]. These plugins fix several of Outlook's problems with sending properly formatted emails.<br />
H</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=User:TheresaOConnor&diff=4662User:TheresaOConnor2010-04-22T17:30:14Z<p>TheresaOConnor: </p>
<hr />
<div><div class="vcard">I'm <span class="fn">Edward O'Connor</span>. My home page: <span class="url">http://edward.oconnor.cx/</span></div><br />
<br />
In addition to keeping an eye on wiki spam, I occasionally [[Special:Contributions/EdwardOConnor|contribute to this wiki]].<br />
<br />
You might also be interested in [http://www.w3.org/html/wg/wiki/Special:Contributions/Eoconnor my contributions to the HTML WG wiki].<br />
<br />
----<br />
{{cc-public-domain-release}}</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=User:TheresaOConnor&diff=4661User:TheresaOConnor2010-04-22T17:28:41Z<p>TheresaOConnor: </p>
<hr />
<div><div class="vcard">I'm <span class="fn">Edward O'Connor</span>. My home page: <span class="url">http://edward.oconnor.cx/</span></div><br />
<br />
In addition to keeping an eye on wiki spam, I occasionally [[Special:Contributions/EdwardOConnor|contribute to this wiki]].<br />
<br />
----<br />
{{cc-public-domain-release}}</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Main_Page&diff=4472Main Page2010-03-13T17:57:54Z<p>TheresaOConnor: Reverted edits by Tara90 (talk) to last revision by Hixie</p>
<hr />
<div>Welcome to the WHATWG Wiki!<br />
<br />
You can be a part of our community, making proposals for the next version of HTML5. This wiki is made available for you for drafting proposals, for writing essays, for keeping track of HTML-related issues, and so forth. Anyone can create an account and contribute content.<br />
<br />
Before you begin, you may wish to read our [[WHATWG Wiki:Contribution Guidelines|contribution guidelines]].<br />
<br />
==Purpose==<br />
The purpose of the WHATWG Wiki is to create a place for WHATWG contributors to post and compile their own proposals and ideas regarding WHATWG specifications. The specifications themselves will not be available for editing via this wiki. However, ideas you post here may find their way into current and future WHATWG specifications.<br />
<br />
== Main sections and Quick links ==<br />
* [[FAQ]]<br />
* [[Implementations]]<br />
* [[What you can do]] — '''[[Reviewing HTML5|Help us review HTML5!]]<br />
* [[Authoring|Using HTML 5 in your Web site]]<br />
* [[Presentational elements and attributes]]<br />
* [[HTML vs. XHTML]]<br />
* [[HTML5 Presentations]]<br />
* [[Issue Discussion]]<br />
* [[Feature Proposals]]<br />
* [[Spec coordination]]<br />
* [[IDE]]<br />
* [[Testsuite]]<br />
<br />
==WHATWG Specifications==<br />
* [[HTML5]]<br />
* [[Web Workers]]<br />
* See also [[FAQ#What_are_the_various_versions_of_the_spec.3F|What are the various versions of the spec?]] in the FAQ.<br />
<br />
==Communicating with the community==<br />
The WHATWG community has several channels of communication:<br />
* [http://www.whatwg.org/mailing-list Mailing lists]<br />
* [http://blog.whatwg.org/ The blog], including [http://blog.whatwg.org/category/whats-next Mark Pilgrim's column "What's next in HTML5"]<br />
* [http://www.w3.org/html/planet/ W3C's "HTML5 planet"]<br />
* [http://forums.whatwg.org/ The forum]<br />
* [[IRC]]<br />
* [http://wiki.whatwg.org/ This wiki]<br />
<br />
== Research and data ==<br />
Research pertaining to and data on publishing behavior for various bits of markup, used to help drive decisions made in/for HTML5 for specific elements and attributes.<br />
<br />
Elements: (perhaps abstract to an [[elements]] page if many more are added)<br />
* [[cite]]<br />
* [[time]] <br />
Attributes: (perhaps abstract to an [[attributes]] page if many more are added)<br />
* [[charset]] <br />
* [[summary]]</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Presentations&diff=4471Presentations2010-03-13T17:57:46Z<p>TheresaOConnor: Reverted edits by Tara90 (talk) to last revision by Hixie</p>
<hr />
<div>These are the known presentations related to the WHATWG and/or HTML5.<br />
<br />
* [http://hixie.ch/advocacy/whatwg-presentation/ Proposing extensions to HTML4 and the DOM] by [[User:Hixie|Ian Hickson]] (Presented 2005-05)<br />
* [http://wearehugh.com/public/2005/12/whitelights/ White Lights Lead To Red Lights] by Mark Pilgrim (Presented 2005-12-07 at Mozilla)<br />
* [http://lachy.id.au/dev/presentation/future-of-html/ The Future of HTML] by [[User:Lachlan_Hunt|Lachlan Hunt]] (Presented 2007-01-25)<br />
* [http://simonwillison.net/2007/talks/oxford-html5/ What the heck is HTML 5?] by [[User:SimonW|Simon Willison]] (Presented 2007-04-11)<br />
* [http://lists.w3.org/Archives/Public/www-archive/2007Apr/att-0036/html5.xml Evolving the Web: HTML5] by [[User:Annevk|Anne van Kesteren]] (Presented 2007-04-17 at QUT)<br />
* [http://lists.w3.org/Archives/Public/www-archive/2007May/att-0063/html5-short.xml Evolving the Web: HTML5 (XTech 2007 edition)] by [[User:Annevk|Anne van Kesteren]] (Presented 2007-05-17 at XTech 2007)<br />
* [http://2007.xtech.org/public/asset/attachment/83 Implementing an HTML5 conformance checker using XML tools] by Henri Sivonen (Presented 2007-05-18 at XTech 2007)<br />
* [http://blog.whatwg.org/html5-geekmeet How HTML5 can be used today] by [[User:zcorpan|Simon Pieters]] (Presented 2007-05-23)<br />
* [http://lists.w3.org/Archives/Public/www-archive/2007May/att-0087/html5.htm HTML5: Incremental Improvements to the Web] by [[User:Annevk|Anne van Kesteren]] (Presented 2007-05-31 at reboot 9.0)<br />
* [http://edward.oconnor.cx/2007/BarCamp-San-Diego/ What to expect from HTML5] by [[User:EdwardOConnor|Edward O'Connor]] (Presented 2007-06-03 at BarCamp San Diego)<br />
* [http://lachy.id.au/dev/presentation/developing-with-html5/Developing%20with%20HTML5.ppt Developing with HTML5] by [[User:Lachlan_Hunt|Lachlan Hunt]] (Presented 2007-08-03)<br />
* [http://james.html5.org/presentations/barcamb.pdf HTML 5: The Next Generation of Markup on The Web] by: [[User:jgraham|James Graham]] (Presented 2007-08-24 at BarCamp Cambridge)<br />
* [http://edward.oconnor.cx/2008/04/sdwebstandards/HTML5 Practical HTML5] by [[User:EdwardOConnor|Edward O'Connor]] (Presented 2008-04 at San Diego Web Standards Group)<br />
* [http://annevankesteren.nl/2008/xtech-html5 HTML5] by [[User:Annevk|Anne van Kesteren]] (Presented 2008-05-08 at XTech 2008 and a slightly modified version on 2008-06-27 at reboot10)<br />
* [http://annevankesteren.nl/2008/fronteers-html5-video HTML5] by [[User:Annevk|Anne van Kesteren]] (Presented 2008-09-11 at Fronteers 2008)<br />
* [http://www.whatwg.org/demos/2008-sept/ HTML5: Features you want desperately but still can't use] by [[User:Hixie|Ian Hickson]] (Presented 2008-09-22 at Google)<br />
* [http://lensco.be/2008/11/30/html-5-in-a-big-nutshell-a-presentation-at-barcamp-gent HTML 5 in a big nutshell] by [[User:lensco|Lennart Schoors]] (Presented at Barcamp Ghent 2008-11-29)<br />
* [http://annevankesteren.nl/2009/over-webstandaarden-enzo Over Webstandaarden Enzo] (Dutch) by [[User:Annevk|Anne van Kesteren]] (Presented 2009-01-19 at Fronteers meeting)<br />
* [http://simon.html5.org/presentations/090423-mdh/ HTML5 och Webbläsare] (Swedish) by [[User:zcorpan|Simon Pieters]] (Presented 2009-04-23 at Mälardalens Högskola)<br />
* [http://edward.oconnor.cx/2009/BarCamp-San-Diego-5/ Extensibility, HTML, and the Web ecosystem] by [[User:EdwardOConnor|Edward O'Connor]] (Presented 2009-05-31 at BarCamp San Diego)<br />
* [http://www.ustream.tv/recorded/1642113 HTML5 overview] (English) by [[User:arlen|Arlen Walker]] (Presented 2009-06-11 at Web414) (Presentation begins at 9:30 of the video, alternate camera angle found at [http://www.web414.com/node/877 Web414 video])<br />
* [http://edward.oconnor.cx/2009/preDevCamp/ HTML5 & webOS] by [[User:EdwardOConnor|Edward O'Connor]] (Presented 2009-08-08 at preDevCamp San Diego)<br />
* [http://edward.oconnor.cx/2009/08/ignite HTML 5 for the Working Web: features you can use today] by [[User:EdwardOConnor|Edward O'Connor]] (Presented 2009-08-12 at [http://ignitesandiego.org/ Ignite San Diego])<br />
* [http://simon.html5.org/presentations/html5-video/ HTML5 video] (Swedish) by [[User:zcorpan|Simon Pieters]] (Presented 2010-02-16 at Linköpings Universitet)</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=Presentations&diff=4464Presentations2010-02-26T15:48:16Z<p>TheresaOConnor: Reverted edits by Lakama (talk) to last revision by Zcorpan</p>
<hr />
<div>These are the known presentations related to the WHATWG and/or HTML5.<br />
<br />
* [http://hixie.ch/advocacy/whatwg-presentation/ Proposing extensions to HTML4 and the DOM] by [[User:Hixie|Ian Hickson]] (Presented 2005-05)<br />
* [http://wearehugh.com/public/2005/12/whitelights/ White Lights Lead To Red Lights] by Mark Pilgrim (Presented 2005-12-07 at Mozilla)<br />
* [http://lachy.id.au/dev/presentation/future-of-html/ The Future of HTML] by [[User:Lachlan_Hunt|Lachlan Hunt]] (Presented 2007-01-25)<br />
* [http://simonwillison.net/2007/talks/oxford-html5/ What the heck is HTML 5?] by [[User:SimonW|Simon Willison]] (Presented 2007-04-11)<br />
* [http://lists.w3.org/Archives/Public/www-archive/2007Apr/att-0036/html5.xml Evolving the Web: HTML5] by [[User:Annevk|Anne van Kesteren]] (Presented 2007-04-17 at QUT)<br />
* [http://lists.w3.org/Archives/Public/www-archive/2007May/att-0063/html5-short.xml Evolving the Web: HTML5 (XTech 2007 edition)] by [[User:Annevk|Anne van Kesteren]] (Presented 2007-05-17 at XTech 2007)<br />
* [http://2007.xtech.org/public/asset/attachment/83 Implementing an HTML5 conformance checker using XML tools] by Henri Sivonen (Presented 2007-05-18 at XTech 2007)<br />
* [http://blog.whatwg.org/html5-geekmeet How HTML5 can be used today] by [[User:zcorpan|Simon Pieters]] (Presented 2007-05-23)<br />
* [http://lists.w3.org/Archives/Public/www-archive/2007May/att-0087/html5.htm HTML5: Incremental Improvements to the Web] by [[User:Annevk|Anne van Kesteren]] (Presented 2007-05-31 at reboot 9.0)<br />
* [http://edward.oconnor.cx/2007/BarCamp-San-Diego/ What to expect from HTML5] by [[User:EdwardOConnor|Edward O'Connor]] (Presented 2007-06-03 at BarCamp San Diego)<br />
* [http://lachy.id.au/dev/presentation/developing-with-html5/Developing%20with%20HTML5.ppt Developing with HTML5] by [[User:Lachlan_Hunt|Lachlan Hunt]] (Presented 2007-08-03)<br />
* [http://james.html5.org/presentations/barcamb.pdf HTML 5: The Next Generation of Markup on The Web] by: [[User:jgraham|James Graham]] (Presented 2007-08-24 at BarCamp Cambridge)<br />
* [http://edward.oconnor.cx/2008/04/sdwebstandards/HTML5 Practical HTML5] by [[User:EdwardOConnor|Edward O'Connor]] (Presented 2008-04 at San Diego Web Standards Group)<br />
* [http://annevankesteren.nl/2008/xtech-html5 HTML5] by [[User:Annevk|Anne van Kesteren]] (Presented 2008-05-08 at XTech 2008 and a slightly modified version on 2008-06-27 at reboot10)<br />
* [http://annevankesteren.nl/2008/fronteers-html5-video HTML5] by [[User:Annevk|Anne van Kesteren]] (Presented 2008-09-11 at Fronteers 2008)<br />
* [http://www.whatwg.org/demos/2008-sept/ HTML5: Features you want deparately but still can't use] by [[User:Hixie|Ian Hickson]] (Presented 2008-09-22 at Google)<br />
* [http://lensco.be/2008/11/30/html-5-in-a-big-nutshell-a-presentation-at-barcamp-gent HTML 5 in a big nutshell] by [[User:lensco|Lennart Schoors]] (Presented at Barcamp Ghent 2008-11-29)<br />
* [http://annevankesteren.nl/2009/over-webstandaarden-enzo Over Webstandaarden Enzo] (Dutch) by [[User:Annevk|Anne van Kesteren]] (Presented 2009-01-19 at Fronteers meeting)<br />
* [http://simon.html5.org/presentations/090423-mdh/ HTML5 och Webbläsare] (Swedish) by [[User:zcorpan|Simon Pieters]] (Presented 2009-04-23 at Mälardalens Högskola)<br />
* [http://edward.oconnor.cx/2009/BarCamp-San-Diego-5/ Extensibility, HTML, and the Web ecosystem] by [[User:EdwardOConnor|Edward O'Connor]] (Presented 2009-05-31 at BarCamp San Diego)<br />
* [http://www.ustream.tv/recorded/1642113 HTML5 overview] (English) by [[User:arlen|Arlen Walker]] (Presented 2009-06-11 at Web414) (Presentation begins at 9:30 of the video, alternate camera angle found at [http://www.web414.com/node/877 Web414 video])<br />
* [http://edward.oconnor.cx/2009/preDevCamp/ HTML5 & webOS] by [[User:EdwardOConnor|Edward O'Connor]] (Presented 2009-08-08 at preDevCamp San Diego)<br />
* [http://edward.oconnor.cx/2009/08/ignite HTML 5 for the Working Web: features you can use today] by [[User:EdwardOConnor|Edward O'Connor]] (Presented 2009-08-12 at [http://ignitesandiego.org/ Ignite San Diego])<br />
* [http://simon.html5.org/presentations/html5-video/ HTML5 video] (Swedish) by [[User:zcorpan|Simon Pieters]] (Presented 2010-02-16 at Linköpings Universitet)</div>TheresaOConnorhttps://wiki.whatwg.org/index.php?title=IDE&diff=4463IDE2010-02-26T15:47:44Z<p>TheresaOConnor: Reverted edits by Lakama (talk) to last revision by Hendry</p>
<hr />
<div>= vim =<br />
<br />
=== HTML5 text/html syntax ===<br />
<br />
https://vim.svn.sourceforge.net/svnroot/vim/vim7/runtime/autoload/xml/ and ''':help xml-omni-datafile''' might help you get started.<br />
<br />
Ideally some sort of tool to convert http://syntax.whattf.org/relaxng/ into a '''xml-omni-datafile''' is required. Updating https://vim.svn.sourceforge.net/svnroot/vim/vim7/runtime/autoload/xml/html40s.vim looks a bit too painful.<br />
<br />
=== Lint ===<br />
<br />
See the [http://blog.whatwg.org/vim-checker HTML5 conformance checking in Vim blog entry] for an introduction.<br />
<br />
Idea is to integrate Web services via [http://en.wikipedia.org/wiki/CURL curl] with your editor that supports [[Validator.nu_GNU_Output]], e.g. [http://en.wikipedia.org/wiki/Vim_editor vim]:<br />
<br />
* HTML validation with [http://validator.nu/ validator.nu] script<br />
* JavaScript validation with [http://www.jslint.com/ JSlint] script - [http://git.webvm.net/?p=jslint service source]<br />
* CSS validation is [http://lists.w3.org/Archives/Public/www-validator-css/2008Jul/thread.html being worked on]<br />
<br />
=== Installation instructions ===<br />
<br />
http://svn.natalian.org/projects/html5/INSTALL<br />
<br />
Any suggestions? Please get in contact with [http://hendry.iki.fi/ Kai Hendry]<br />
<br />
Caveats:<br />
* Vim's makeprg syntax requires some horrible escaping, hence the need for an external script<br />
* Vim's errorformat has issues parsing anything too complex, so best edit the stream for the errorformat (not the other way around)<br />
* Vim's quickfix list (:cope) seems to require a filename (%f) in the error format<br />
<br />
<br />
= Emacs =<br />
<br />
=== XHTML5 or polyglot documents ===<br />
<br />
Emacs ships with [http://www.thaiopensource.com/nxml-mode/ nxml-mode], a major mode for editing XML which does on-the-fly validation with RELAX NG schema. You can plug [http://wiki.whatwg.org/wiki/HTML5_Conformance_Checker#The_Schemas fantasai and hsivonen's schema] into nxml-mode. The necessary shim code is included in the [http://github.com/hober/html5-el/tree/master hober/html5-el project on github].</div>TheresaOConnor