RelExtensions - Revision history

GPHemsley: Use {{obsolete}}.

2012-11-03T18:32:44Z

Use {{obsolete}}.

← Older revision		Revision as of 18:32, 3 November 2012
Line 1:		Line 1:
	~~=This page is~~ obsolete=		{{obsolete\|see=[http://microformats.org/wiki/existing-rel-values Microformats: existing rel values]}}

	~~'''The HTML specification no longer references this page. It now references the Microformats "existing-rel-values" registry:~~ http://microformats.org/wiki/existing-rel-values~~'''~~

	~~==Historical contents==~~

	~~''The following are the contents of this page before it was replaced.''~~

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

Hixie: Protected "RelExtensions": Obsolete page ([edit=sysop] (indefinite) [move=sysop] (indefinite))

2011-12-02T16:39:46Z

Protected "RelExtensions": Obsolete page ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision	Revision as of 16:39, 2 December 2011
(No difference)

TheresaOConnor: Reverted edits by Loveservice (talk) to last revision by Tburkard

2011-07-05T15:55:02Z

Reverted edits by Loveservice (talk) to last revision by Tburkard

← Older revision		Revision as of 15:55, 5 July 2011
Line 805:		Line 805:
	===See also===		===See also===
	*[http://microformats.org/wiki/existing-rel-values the Microformats wiki page on this matter].		*[http://microformats.org/wiki/existing-rel-values the Microformats wiki page on this matter].
	*[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		*[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)
	*[http://www.hostgatorcouponsreview.com HostGator Coupons]
	*[http://www.thegrizasonline.com/inmotion-hosting-review-inmotion-hosting-coupon InMotion Review]
	(note comments)

	[[Category:Registries]]		[[Category:Registries]]

Loveservice at 12:35, 5 July 2011

2011-07-05T12:35:54Z

← Older revision		Revision as of 12:35, 5 July 2011
Line 805:		Line 805:
	===See also===		===See also===
	*[http://microformats.org/wiki/existing-rel-values the Microformats wiki page on this matter].		*[http://microformats.org/wiki/existing-rel-values the Microformats wiki page on this matter].
	*[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)		*[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
			*[http://www.hostgatorcouponsreview.com HostGator Coupons]
			*[http://www.thegrizasonline.com/inmotion-hosting-review-inmotion-hosting-coupon InMotion Review]
			(note comments)

	[[Category:Registries]]		[[Category:Registries]]

Tburkard: /* Historical contents */

2011-05-17T18:55:37Z

Historical contents

← Older revision		Revision as of 18:55, 17 May 2011
Line 532:		Line 532:
	\| prefetch		\| prefetch
	\|colspan=6\| See HTML5		\|colspan=6\| See HTML5
			\|-
			\| prerender
			\| external resource
			\| not allowed
			\| Prerender the specified URL including all subresources and running all scripts.
			\| [http://dev.chromium.org/developers/design-documents/prerender Chromium Prerendering]
			\|
			\| Proposal
	\|-		\|-
	\| presentation		\| presentation

Hixie at 00:30, 13 April 2011

2011-04-13T00:30:18Z

← Older revision		Revision as of 00:30, 13 April 2011
Line 1:		Line 1:
			=This page is obsolete=

			'''The HTML specification no longer references this page. It now references the Microformats "existing-rel-values" registry: http://microformats.org/wiki/existing-rel-values'''

			==Historical contents==

			''The following are the contents of this page before it was replaced.''

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

Pigsonthewing: Citation Typing Ontology (CiTO)

2011-03-19T00:14:51Z

Citation Typing Ontology (CiTO)

← Older revision		Revision as of 00:14, 19 March 2011
Line 785:		Line 785:
	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".		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".

	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].		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].
			*[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)

	[[Category:Registries]]		[[Category:Registries]]

Tb006 at 11:03, 9 March 2011

2011-03-09T11:03:32Z

← Older revision		Revision as of 11:03, 9 March 2011
Line 354:		Line 354:
	\| license		\| license
	\|colspan=6\| See HTML5		\|colspan=6\| See HTML5
			\|-
			\| login
			\| hyperlink
			\| hyperlink
			\| 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.
			\|
			\| search
			\| Proposal
	\|-		\|-
	\| logout		\| logout

Daniel.weck at 22:28, 2 February 2011

2011-02-02T22:28:00Z

← Older revision		Revision as of 22:28, 2 February 2011
Line 14:		Line 14:
	\| external resource		\| external resource
	\| not allowed		\| not allowed
	\| 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 pronunciation ~~rules are~~ specified more than once for a given string of characters, the last occurrence of the rule takes precedence (in document order), such that previously-defined pronunciation ~~rules get~~ overridden.		\| 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.
	\| [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]		\| [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]
	\|		\|

Daniel.weck at 22:18, 2 February 2011

2011-02-02T22:18:11Z

← Older revision		Revision as of 22:18, 2 February 2011
Line 14:		Line 14:
	\| external resource		\| external resource
	\| not allowed		\| not allowed
	\| 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, a "pronunciation" link/rel ~~file~~ 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 pronunciation rules are specified more than once for a given string of characters, the last occurrence of the rule takes precedence (in document order), so that ~~previous~~ pronunciation rules get overridden.		\| 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 pronunciation rules are specified more than once for a given string of characters, the last occurrence of the rule takes precedence (in document order), such that previously-defined pronunciation rules get overridden.
	\| [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]		\| [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]
	\|		\|