rel-profile - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:32:05Z

Replace <entry-title> with {{DISPLAYTITLE:}}

← Older revision		Revision as of 16:32, 18 July 2020
Line 1:		Line 1:
	~~<entry-title>~~rel profile~~</entry-title>~~		{{DISPLAYTITLE:rel profile}}

	rel="profile" was originally introduced in a draft of XHTML 2.0 (citation needed) as a result of a proposal by [[User:Tantek\|Tantek Çelik]] during an early HTML Working Group meeting (sometime in the early 2000s, working group minutes citation needed) to solve the problem of profile URLs being limited to a single one-off invisible attribute of the <code><head></code> element.		rel="profile" was originally introduced in a draft of XHTML 2.0 (citation needed) as a result of a proposal by [[User:Tantek\|Tantek Çelik]] during an early HTML Working Group meeting (sometime in the early 2000s, working group minutes citation needed) to solve the problem of profile URLs being limited to a single one-off invisible attribute of the <code><head></code> element.

PlNG: /* processing model */ corrected incorrect template:must usage.

2012-10-21T20:07:26Z

processing model: corrected incorrect template:must usage.

← Older revision		Revision as of 20:07, 21 October 2012
Line 13:		Line 13:
	More specifically:		More specifically:

	* All processors {{must}} use the DOM of a document parsed per HTML5 or an algorithm that provides an equivalent result. All references to elements, attributes, accessing, traversing refer to in the context of the DOM. All processing steps are required ({{~~MUST~~}}) unless otherwise specified.		* All processors {{must}} use the DOM of a document parsed per HTML5 or an algorithm that provides an equivalent result. All references to elements, attributes, accessing, traversing refer to in the context of the DOM. All processing steps are required ({{must}}) unless otherwise specified.

	Processing model for determing the profile dictionary for a document:		Processing model for determing the profile dictionary for a document:

Tantek: drafted rel-profile processing model per HTML5 and tightened up the descriptions, advantages

2011-06-18T20:45:52Z

drafted rel-profile processing model per HTML5 and tightened up the descriptions, advantages

@@ Line 10: / Line 10: @@
 == processing model ==
 In brief: the head[profile] takes precedence per current [http://gmpg.org/xmdp/description XMDP description] (for backward compat), and then the same first defined rules apply, that is in cases where more than one profile from an <code>&lt;a rel="profile"&gt;</code> defines the same term, first definition wins.
 == advantages ==
-Using rel="profile" has numerous advantages aside from the obvious and originally intended advantage of enabling a future version of HTML to depend less on the "profile" attribute of the <code>&lt;head&gt;</code> element, and simply use the existing <code>&lt;link&gt;</code> element instead.
+Using rel="profile" has numerous advantages aside from the obvious and originally intended advantage of enabling HTML5 documents to not depend on the "profile" attribute of the <code>&lt;head&gt;</code> element, and simply use the existing <code>&lt;link&gt;</code> element instead. E.g.
 Most of these advantages come from the ability to use <code>&lt;a&gt;</code> hyperlinks instead of (or in addition to) <code>&lt;head&gt;</code> and <code>&lt;link&gt;</code> elements and are based on the microformats [[principles]].
 === visibility ===
-The idea is that a document that uses a particular microformat, e.g. [[hCard]], can explicitly link to the profile for that microformat and indicate the profile relationship, via existing visible content hyperlink text such as "This document uses hCard", or an hCard badge image, both of which have been seen in real world web content.
+The idea is that a document that uses a particular microformat, e.g. [[hCard]], can explicitly link to the profile for that microformat and indicate the profile relationship, via existing visible content hyperlink text such as "This document uses hCard", or an hCard badge image, both of which have been seen in real world web content. E.g.
 === modularity ===
-Hyperlinks with rel="profile" provide the potential for contextual definitions of terms. That is, we could define vocabularies included by a hyperlink with rel="profile" to apply only within the context of the hyperlink (either the parent element and all its descendants, or perhaps just the latter siblings of the hyperlinks and all their descendants).
+Hyperlinks with rel="profile" provide the potential for contextual definitions of terms. That is, we define vocabularies included by a hyperlink with rel="profile" to apply only within the context of the hyperlink (the parent element and all its descendants).
-These fragments of self-defining portable [[semantic HTML]] would enable more modular HTML for transclusion and other purposes.
+These fragments of self-defining portable [[semantic HTML]] enable more modular HTML for transclusion and other purposes.
 == additional languages ==

Tantek: document use of rel-profile inside Atom as suggested by tobyink in irc

2010-04-28T13:53:26Z

document use of rel-profile inside Atom as suggested by tobyink in irc

@@ Line 23: / Line 23: @@
 These fragments of self-defining portable [[semantic HTML]] would enable more modular HTML for transclusion and other purposes.
 == implementations ==
 [http://buzzword.org.uk/cognition/ Cognition] has supported <code>rel=profile</code> since March 2008. Cognition has two microformat parsing modes:
 * '''Strict mode:''' pages using microformats are required to include a [[profile-uris|well-known profile URI]] for each microformat they use, essentially as a "flag" to enable parsing of that microformat.

Tantek: rel-profile now incorporated into XMDP, added explicit editorship as we now need this as part of XMDP infrastructure for microformats

2009-10-04T19:34:15Z

rel-profile now incorporated into XMDP, added explicit editorship as we now need this as part of XMDP infrastructure for microformats

← Older revision		Revision as of 19:34, 4 October 2009
Line 3:		Line 3:
	rel="profile" was originally introduced in a draft of XHTML 2.0 (citation needed) as a result of a proposal by [[User:Tantek\|Tantek Çelik]] during an early HTML Working Group meeting (sometime in the early 2000s, working group minutes citation needed) to solve the problem of profile URLs being limited to a single one-off invisible attribute of the <code><head></code> element.		rel="profile" was originally introduced in a draft of XHTML 2.0 (citation needed) as a result of a proposal by [[User:Tantek\|Tantek Çelik]] during an early HTML Working Group meeting (sometime in the early 2000s, working group minutes citation needed) to solve the problem of profile URLs being limited to a single one-off invisible attribute of the <code><head></code> element.

	This same meaning, that of a link to a metadata profile for the current document, is ~~being strongly considered for an update to~~ [[XMDP]]. See [[xmdp-brainstorming]], in particular, [[xmdp-brainstorming#resolving_when_microformats_may_be_in_use\|when microformats may be in use]].		This same meaning, that of a link to a metadata profile for the current document, is has been incorporated into [[XMDP]] since [[HTML5]] drops the "profile" attribute. See also [[xmdp-brainstorming]], in particular, [[xmdp-brainstorming#resolving_when_microformats_may_be_in_use\|when microformats may be in use]].

			;Editor
			:[[User:Tantek\|Tantek Çelik]]

	== processing model ==		== processing model ==

Tantek: entry-title, autotoc

2009-10-04T19:32:19Z

entry-title, autotoc

← Older revision		Revision as of 19:32, 4 October 2009
Line 1:		Line 1:
	<h1>rel profile</h1>		<entry-title>rel profile</entry-title>
	~~{{TOC-right}}~~
	rel="profile" was originally introduced in a draft of XHTML 2.0 (citation needed) as a result of a proposal by [[User:Tantek\|Tantek Çelik]] during an early HTML Working Group meeting (sometime in the early 2000s, working group minutes citation needed) to solve the problem of profile URLs being limited to a single one-off invisible attribute of the <code><head></code> element.		rel="profile" was originally introduced in a draft of XHTML 2.0 (citation needed) as a result of a proposal by [[User:Tantek\|Tantek Çelik]] during an early HTML Working Group meeting (sometime in the early 2000s, working group minutes citation needed) to solve the problem of profile URLs being limited to a single one-off invisible attribute of the <code><head></code> element.

TobyInk: implementations

2008-07-29T07:50:12Z

implementations

← Older revision		Revision as of 07:50, 29 July 2008
Line 20:		Line 20:

	These fragments of self-defining portable [[semantic HTML]] would enable more modular HTML for transclusion and other purposes.		These fragments of self-defining portable [[semantic HTML]] would enable more modular HTML for transclusion and other purposes.

			== implementations ==

			[http://buzzword.org.uk/cognition/ Cognition] has supported <code>rel=profile</code> since March 2008. Cognition has two microformat parsing modes:
			* '''Strict mode:''' pages using microformats are required to include a [[profile-uris\|well-known profile URI]] for each microformat they use, essentially as a "flag" to enable parsing of that microformat.
			* '''Loose mode (default):''' most microformats will be parsed without a profile being explicitly included (though authors are still recommended to include profile URIs for any microformats they use). Some obscure microformats (e.g. [http://gmpg.org/xfn/1 XFN 1.0], [http://xen.adactio.com XEN]) still require a profile URI to work.

	== see also ==		== see also ==

Tantek: drafted, brainstormed, braindumped lots as a result of some IRC triggering thoughts from quite a while back.

2008-07-28T21:50:44Z

drafted, brainstormed, braindumped lots as a result of some IRC triggering thoughts from quite a while back.

New page

<h1>rel profile</h1>
{{TOC-right}}
rel="profile" was originally introduced in a draft of XHTML 2.0 (citation needed) as a result of a proposal by [[User:Tantek|Tantek Çelik]] during an early HTML Working Group meeting (sometime in the early 2000s, working group minutes citation needed) to solve the problem of profile URLs being limited to a single one-off invisible attribute of the <code><head></code> element.

This same meaning, that of a link to a metadata profile for the current document, is being strongly considered for an update to [[XMDP]]. See [[xmdp-brainstorming]], in particular, [[xmdp-brainstorming#resolving_when_microformats_may_be_in_use|when microformats may be in use]].

== processing model ==
In brief: the head[profile] takes precedence per current [http://gmpg.org/xmdp/description XMDP description] (for backward compat), and then the same first defined rules apply, that is in cases where more than one profile from an <code><a rel="profile"></code> defines the same term, first definition wins.

== advantages ==
Using rel="profile" has numerous advantages aside from the obvious and originally intended advantage of enabling a future version of HTML to depend less on the "profile" attribute of the <code><head></code> element, and simply use the existing <code><link></code> element instead.

Most of these advantages come from the ability to use <code><a></code> hyperlinks instead of (or in addition to) <code><head></code> and <code><link></code> elements and are based on the microformats [[principles]].

=== visibility ===
The idea is that a document that uses a particular microformat, e.g. [[hCard]], can explicitly link to the profile for that microformat and indicate the profile relationship, via existing visible content hyperlink text such as "This document uses hCard", or an hCard badge image, both of which have been seen in real world web content.

=== modularity ===
Hyperlinks with rel="profile" provide the potential for contextual definitions of terms. That is, we could define vocabularies included by a hyperlink with rel="profile" to apply only within the context of the hyperlink (either the parent element and all its descendants, or perhaps just the latter siblings of the hyperlinks and all their descendants).

These fragments of self-defining portable [[semantic HTML]] would enable more modular HTML for transclusion and other purposes.

== see also ==
* [[existing-rel-values]]
* [[xmdp]]
* [[xmdp-brainstorming]]
* [[xmdp-faq]]