representative-hcard-brainstorming - Revision history

Tantek: explicitly separate current proposal from other proposals to better clarify and hopefully reduce confusion about possible existence of a bunch of proposals, update user scenario for current proposal

2009-06-03T18:20:24Z

explicitly separate current proposal from other proposals to better clarify and hopefully reduce confusion about possible existence of a bunch of proposals, update user scenario for current proposal

← Older revision		Revision as of 18:20, 3 June 2009
Line 2:		Line 2:
	{{TOC-right}}		{{TOC-right}}
	Proposals for indicating on pages that represent individual people which [[hcard\|hCards]] represents that person. Part of the [[representative-hcard]] effort.		Proposals for indicating on pages that represent individual people which [[hcard\|hCards]] represents that person. Part of the [[representative-hcard]] effort.


	== summary ==		== summary ==
Line 7:		Line 8:
	* [[representative-hcard-parsing]] for the current best proposal for how to find a representative hCard on a page.		* [[representative-hcard-parsing]] for the current best proposal for how to find a representative hCard on a page.

	== ~~proposals~~ ==
	~~Ways~~ to auto discover the representative hCard for a page, that is the hCard that is the person (or organization) that the page represents.		== current proposal ==
			This <span id="proposals">proposal</span> is the most current and has evolved from a number of other proposals to auto discover the representative hCard for a page, that is the hCard that is the person (or organization) that the page represents.

	=== url uid source and rel me ===		=== url uid source and rel me ===
Line 17:		Line 19:
	# '''rel="me" on class="url"'''. otherwise use the first hCard which has a rel="me" class="url". That is, the first hCard that has a <code>url</code> property on an <code>a href</code> which also has <code>rel="me"</code>. Since a [[rel-me]] hyperlink {{must}} be from a page that represents a person to another page that represents the same person, if that "to" page is a <code>url</code> property value for an hCard then that hCard {{must}} be representative of both the "to" page and the page that the hCard is on. <!-- Since [[rel-me]] indicates that the referenced page is another URL that represents the person represented by the current page, it therefore follows that if that rel-me hyperlink is also a "url" property of an hCard, that hCard {{must}} must be a representative hCard for the current page. -->		# '''rel="me" on class="url"'''. otherwise use the first hCard which has a rel="me" class="url". That is, the first hCard that has a <code>url</code> property on an <code>a href</code> which also has <code>rel="me"</code>. Since a [[rel-me]] hyperlink {{must}} be from a page that represents a person to another page that represents the same person, if that "to" page is a <code>url</code> property value for an hCard then that hCard {{must}} be representative of both the "to" page and the page that the hCard is on. <!-- Since [[rel-me]] indicates that the referenced page is another URL that represents the person represented by the current page, it therefore follows that if that rel-me hyperlink is also a "url" property of an hCard, that hCard {{must}} must be a representative hCard for the current page. -->
	# otherwise no representative hCard can be identified.		# otherwise no representative hCard can be identified.

			==== user scenario ====
			User scenario:
			Here is a scenario that outlines a proposed representative hCard auto-discovery process:

			# I (as user) give the URL of my homepage or hCard or other profile URL, to a site that wants a profile icon
			# That site goes and gets it (e.g. using [[hKit]]), and then:
			## checks to see if there is an hCard with a "url" property equal to its "uid" property which is also the same as the URL of the page. if an hCard contains such a URL==UID that also points to the current page, then it is likely that the hCard is about the current page. (if there is more than one such hCard on the page, use the first such hCard.)
			## if no such hCard was found, the site checks to see if there is an hCard with a "url" property on a rel="me" hyperlink (since rel="me" only works from a whole page to a whole page. if an hCard contains such a URL, then that hCard must represent the page. see [http://gmpg.org/xfn/and/#idconsolidation XFN identity consolidation] for more details.), and uses it if it finds it. (if there is more than one such hCard on the page, use the first such hCard.)
			## otherwise uses the first hCard it finds. while this does not provide an explicit representative hCard, at least it falls back to providing an hCard which will work in many cases, e.g. profile URLs which have a single hCard like on [http://flickr.com Flickr] and [http://technorati.com/ Technorati].
			# The site looks in the hCard for a "logo" property and uses the first one if it finds any.
			# Otherwise it looks for a "photo" property and uses the first one if it finds any.
			# Otherwise the site uses a default icon, but subscribes to the URL with the hCard and checks it for a "logo" or "photo", say, once a day.


			== other proposals ==
			Other (some historical) thoughts to auto discover the representative hCard for a page, that is the hCard that is the person (or organization) that the page represents.

	=== rel me and url source else first ===		=== rel me and url source else first ===
Line 41:		Line 60:
	Use of an additional class name, say <code>class="representative vcard"</code> (as an alternative to, or in addition to, the above patterns), would deal with the problems with the above proposals, as raised on [[representative-hcard-issues]]. It would also be quickly reusable for <code>class="representative vevent"</code> and other such microformats. A rule would require only one use of <code>class="representative"</code>, per microformat, per page. [[User:AndyMabbett\|Andy Mabbett]] 16:10, 2 Feb 2008 (PST)		Use of an additional class name, say <code>class="representative vcard"</code> (as an alternative to, or in addition to, the above patterns), would deal with the problems with the above proposals, as raised on [[representative-hcard-issues]]. It would also be quickly reusable for <code>class="representative vevent"</code> and other such microformats. A rule would require only one use of <code>class="representative"</code>, per microformat, per page. [[User:AndyMabbett\|Andy Mabbett]] 16:10, 2 Feb 2008 (PST)

			<div class="discussion">
	* As per Semantic XHTML Design Principles, wouldn't id="representative" be better than a class? [[User:TobyInk\|TobyInk]] 09:01, 18 Feb 2008 (PST)		* As per Semantic XHTML Design Principles, wouldn't id="representative" be better than a class? [[User:TobyInk\|TobyInk]] 09:01, 18 Feb 2008 (PST)

	**A page could have a representative hCard and a representative hCalendar (or some other pair of representative microformats); but ID can only be used once. A workaround (I state this for the record, not as a recommendation) would be <code>ID="representative-hcard"</code>, etc. [[User:AndyMabbett\|Andy Mabbett]] 09:31, 18 Feb 2008 (PST)		**A page could have a representative hCard and a representative hCalendar (or some other pair of representative microformats); but ID can only be used once. A workaround (I state this for the record, not as a recommendation) would be <code>ID="representative-hcard"</code>, etc. [[User:AndyMabbett\|Andy Mabbett]] 09:31, 18 Feb 2008 (PST)
			* <p>+0 (combined +1 and -1).</p><p>+1: I believe the idea of class="representative" may be worthy of consideration at some point, as it provides a pattern that would automatically work for any microformat.</p><p>-1: However for currently documented real-world cases of hCards it appears that the [[#current_proposal\|current proposal]] is sufficient, and similar rules can be used for [[hCalendar]] events, since hCalendar also has <code>uid</code> and <code>url</code> classes.</p><p>Thus per the [[microformats]] design [[principle]] of [[minimal-vocabulary]], we should avoid introducing another term (until there is a demonstrated need for something like representative hReview), but given potential future utility, it may be wise to ''reserve'' the term <code>representative</code> for this use at some point. </p><p>[[User:Tantek\|Tantek]] 18:20, 3 June 2009 (UTC)</p>
			</div>

	== author hcard / contact hcard ==		== author hcard / contact hcard ==
Line 86:		Line 107:

	== related pages ==		== related pages ==
	* {{representative-hcard-related-pages}}		{{representative-hcard-related-pages}}

Mart: /* using XFN "me" link from page to hcard element */

2008-11-16T03:06:22Z

using XFN "me" link from page to hcard element

← Older revision		Revision as of 03:06, 16 November 2008
Line 83:		Line 83:
	The above doesn't necessarily imply that contact.html itself represents the same person as this page. contact.html might itself be about contacting several different people or departments.		The above doesn't necessarily imply that contact.html itself represents the same person as this page. contact.html might itself be about contacting several different people or departments.

	If the hcard is indeed on a different page, it can reciprocate the link by linking back from ~~with in~~ the hCard ~~with <code>rel="me"</code>~~, ideally within the hCard "url" field. If the hCard is on the page it represents, this reciprocal link is implied.		If the hcard is indeed on a different page, it can reciprocate the link by linking back from within the hCard, ideally within the hCard "url" field. If the hCard is on the page it represents, this reciprocal link is implied. <code>rel="me"</code> should not be included on this link unless the page containing the hcard represents the same person as the target of the link, to avoid confusing XFN-only (i.e. non-hCard) parsers.

	== related pages ==		== related pages ==
	* {{representative-hcard-related-pages}}		* {{representative-hcard-related-pages}}

Mart: /* using XFN "me" link from page to hcard element */

2008-11-16T03:04:17Z

using XFN "me" link from page to hcard element

← Older revision		Revision as of 03:04, 16 November 2008
Line 82:		Line 82:

	The above doesn't necessarily imply that contact.html itself represents the same person as this page. contact.html might itself be about contacting several different people or departments.		The above doesn't necessarily imply that contact.html itself represents the same person as this page. contact.html might itself be about contacting several different people or departments.

			If the hcard is indeed on a different page, it can reciprocate the link by linking back from with in the hCard with <code>rel="me"</code>, ideally within the hCard "url" field. If the hCard is on the page it represents, this reciprocal link is implied.

	== related pages ==		== related pages ==
	* {{representative-hcard-related-pages}}		* {{representative-hcard-related-pages}}

Mart: /* using XFN "me" link from page to hcard element */

2008-11-16T02:56:31Z

using XFN "me" link from page to hcard element

← Older revision		Revision as of 02:56, 16 November 2008
Line 80:		Line 80:

	<code><a rel="me" href="/contact.html#contactinfo">Contact Me</a></code>		<code><a rel="me" href="/contact.html#contactinfo">Contact Me</a></code>

			The above doesn't necessarily imply that contact.html itself represents the same person as this page. contact.html might itself be about contacting several different people or departments.

	== related pages ==		== related pages ==
	* {{representative-hcard-related-pages}}		* {{representative-hcard-related-pages}}

Mart: Add proposal for

2008-11-16T02:52:41Z

Add proposal for

@@ Line 62: / Line 62: @@
 It is important to note that <address> is block level and may only contain inline elements, so is very hard to include into existing designs.
 == related pages ==
 * {{representative-hcard-related-pages}}

CiaranMc: /* contact hcard */

2008-03-25T17:27:21Z

contact hcard

← Older revision		Revision as of 17:27, 25 March 2008
Line 59:		Line 59:
	=== contact hcard ===		=== contact hcard ===

	An hCard found in an ~~<~~address> element represents the contact for the page, or for a major section of the page.		An hCard found in an <address> element represents the contact for the page, or for a major section of the page.

			It is important to note that <address> is block level and may only contain inline elements, so is very hard to include into existing designs.

	== related pages ==		== related pages ==
	* {{representative-hcard-related-pages}}		* {{representative-hcard-related-pages}}

CiaranMc: /* author hcard */

2008-03-25T17:25:55Z

author hcard

← Older revision		Revision as of 17:25, 25 March 2008
Line 54:		Line 54:

	An hCard linked to with rel="author" (for hysterical raisins, rev="made" should also be recognised), is the author hCard. A page may have multiple authors. rel="author" and rev="made" are defined by HTML 5.		An hCard linked to with rel="author" (for hysterical raisins, rev="made" should also be recognised), is the author hCard. A page may have multiple authors. rel="author" and rev="made" are defined by HTML 5.

			hAtom already uses class="author vcard" to identify the feed author, which also has the advantage (or maybe limitation) that it does not have an existing 'applies to the whole page' semantic like rel does (consider a page of blog posts with different authors).

	=== contact hcard ===		=== contact hcard ===

TobyInk: Author hCard / Contact hCard

2008-03-22T17:24:24Z

Author hCard / Contact hCard

@@ Line 44: / Line 44: @@
 **A page could have a representative hCard and a representative hCalendar (or some other pair of representative microformats); but ID can only be used once. A workaround (I state this for the record, not as a recommendation) would be <code>ID="representative-hcard"</code>, etc. [[User:AndyMabbett|Andy Mabbett]] 09:31, 18 Feb 2008 (PST)
 == related pages ==
 * {{representative-hcard-related-pages}}

AndyMabbett: /* class=representative vcard */ tweak

2008-02-18T18:01:09Z

class=representative vcard: tweak

← Older revision		Revision as of 18:01, 18 February 2008
Line 43:		Line 43:
	* As per Semantic XHTML Design Principles, wouldn't id="representative" be better than a class? [[User:TobyInk\|TobyInk]] 09:01, 18 Feb 2008 (PST)		* As per Semantic XHTML Design Principles, wouldn't id="representative" be better than a class? [[User:TobyInk\|TobyInk]] 09:01, 18 Feb 2008 (PST)

	**A page could have a representative hCard and a representative hCalendar (or some other pair of representative microformats); but ID can only be used once. A workaround (I state this for the record, not as a recommendation) would be ID-representative-hcard".) [[User:AndyMabbett\|Andy Mabbett]] 09:31, 18 Feb 2008 (PST)		**A page could have a representative hCard and a representative hCalendar (or some other pair of representative microformats); but ID can only be used once. A workaround (I state this for the record, not as a recommendation) would be <code>ID="representative-hcard"</code>, etc. [[User:AndyMabbett\|Andy Mabbett]] 09:31, 18 Feb 2008 (PST)

	== related pages ==		== related pages ==
	* {{representative-hcard-related-pages}}		* {{representative-hcard-related-pages}}

AndyMabbett: /* class=representative vcard */ id vs class

2008-02-18T17:31:12Z

class=representative vcard: id vs class

← Older revision		Revision as of 17:31, 18 February 2008
Line 42:		Line 42:

	* As per Semantic XHTML Design Principles, wouldn't id="representative" be better than a class? [[User:TobyInk\|TobyInk]] 09:01, 18 Feb 2008 (PST)		* As per Semantic XHTML Design Principles, wouldn't id="representative" be better than a class? [[User:TobyInk\|TobyInk]] 09:01, 18 Feb 2008 (PST)

			**A page could have a representative hCard and a representative hCalendar (or some other pair of representative microformats); but ID can only be used once. A workaround (I state this for the record, not as a recommendation) would be ID-representative-hcard".) [[User:AndyMabbett\|Andy Mabbett]] 09:31, 18 Feb 2008 (PST)

	== related pages ==		== related pages ==
	* {{representative-hcard-related-pages}}		* {{representative-hcard-related-pages}}