representative-hcard - Revision history

Aaronpk: Replace with {{DISPLAYTITLE:}}

2020-07-18T16:32:38Z

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

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

	This page is for keeping track of the representative [[hcard\|hCard]] effort, which is part of [[hcard-brainstorming]], specifically to figure out how to both explicitly specify and discover the representative hCard for a page.		This page is for keeping track of the representative [[hcard\|hCard]] effort, which is part of [[hcard-brainstorming]], specifically to figure out how to both explicitly specify and discover the representative hCard for a page.

Tantek: entry-title, auto toc, should not use hidden meta data or files

2010-07-22T19:00:50Z

entry-title, auto toc, should not use hidden meta data or files

← Older revision		Revision as of 19:00, 22 July 2010
Line 1:		Line 1:
	<h1>representative hCard</h1>		<entry-title>representative hCard</entry-title>
	~~{{TOC-right}}~~
	This page is for keeping track of the representative [[hcard\|hCard]] effort, which is part of [[hcard-brainstorming]], specifically to figure out how to both explicitly specify and discover the representative hCard for a page.		This page is for keeping track of the representative [[hcard\|hCard]] effort, which is part of [[hcard-brainstorming]], specifically to figure out how to both explicitly specify and discover the representative hCard for a page.

Line 11:		Line 11:
	Ok I get it, show me how to both publish and find the representative hCard for a person on a page.		Ok I get it, show me how to both publish and find the representative hCard for a person on a page.
	* how to publish: [[representative-hcard-authoring]]		* how to publish: [[representative-hcard-authoring]]
	* how to find: [[representative-hcard-parsing]]		* how to find/discover and parse: [[representative-hcard-parsing]]

	== use cases ==		== use cases ==
Line 22:		Line 22:
	* should leverage current hCard information publishing patterns		* should leverage current hCard information publishing patterns
	* should not require any additional user interface elements (i.e. links) on any [[hcard-supporting-user-profiles\|hCard supporting user profiles]].		* should not require any additional user interface elements (i.e. links) on any [[hcard-supporting-user-profiles\|hCard supporting user profiles]].
			* should not use any hidden metadata on the page
			* should not use any hidden side files (e.g. random XML)

	== methodology ==		== methodology ==

Tantek: added synonyms section to increase ambient findability when conceptually similar topics are discussed or asked about.

2008-08-28T17:45:37Z

added synonyms section to increase ambient findability when conceptually similar topics are discussed or asked about.

← Older revision		Revision as of 17:45, 28 August 2008
Line 31:		Line 31:
	* [[representative-hcard-formats]] - previous attempts at providing representative hCard or "person info" in general for a page that represents a person.		* [[representative-hcard-formats]] - previous attempts at providing representative hCard or "person info" in general for a page that represents a person.
	* [[representative-hcard-brainstorming]] - proposals for solving the problem		* [[representative-hcard-brainstorming]] - proposals for solving the problem

			== synonyms ==
			This question has also been asked as:
			* What is the authoritative hCard for a page?
			* What is the authority of hCards on a page?
			* hCard authority?

	== related ==		== related ==
Line 46:		Line 52:

	== see also ==		== see also ==
	* {{representative-hcard-related-pages}}		{{representative-hcard-related-pages}}
	* [[hcard-brainstorming]]		* [[hcard-brainstorming]]

Tantek: hcards and pages

2008-06-08T00:13:12Z

hcards and pages

← Older revision		Revision as of 00:13, 8 June 2008
Line 42:		Line 42:

	"'''representative hCard'''", "contact hCard", "author hCard", and "owner hCard" are all ''different'' semantics and can be different people for any given page, even if for many pages some or all of them might be the same person.		"'''representative hCard'''", "contact hCard", "author hCard", and "owner hCard" are all ''different'' semantics and can be different people for any given page, even if for many pages some or all of them might be the same person.

			For more on these semantic distinctions, see [[hcards-and-pages]].

	== see also ==		== see also ==
	* {{representative-hcard-related-pages}}		* {{representative-hcard-related-pages}}
	* [[hcard-brainstorming]]		* [[hcard-brainstorming]]

AndyMabbett: template

2008-02-02T23:51:51Z

template

← Older revision		Revision as of 23:51, 2 February 2008
Line 44:		Line 44:

	== see also ==		== see also ==
	* [[representative-hcard-~~authoring]]~~		* {{representative-hcard-related-pages}}
	* [[representative-hcard-parsing]]
	* [[representative-hcard-examples]]
	* [[representative-hcard-formats]]
	* [[representative-hcard-~~brainstorming]]~~
	* [[hcard]]
	* [[hcard-brainstorming]]		* [[hcard-brainstorming]]

Tantek: see also, how to

2007-11-19T03:07:24Z

Tantek: simplify problem statement, added how to section, representative-hcard-authoring, representative-hcard-parsing, use cases org'ing

2007-11-19T01:06:14Z

simplify problem statement, added how to section, representative-hcard-authoring, representative-hcard-parsing, use cases org'ing

← Older revision		Revision as of 01:06, 19 November 2007
Line 4:		Line 4:

	== problem statement ==		== problem statement ==
	~~Short version:~~ '''Given a URL, how do you determine which hCard is the representative hCard for that page?'''		'''Given a URL, how do you determine which hCard is the representative hCard for that page?'''

	Longer: Given a URL to a page that represents a person, how do you determine which hCard on that page is the hCard for that person? ~~Variants:~~		Longer: Given a URL to a page that represents a person (e.g. an [[hcard-supporting-user-profiles\|hCard supporting user profile]]), how do you determine which hCard on that page is the hCard for that person?
	* Given a URL to a person's [[hcard-~~supporting~~-~~user~~-~~profiles\|hCard supporting user profile~~]]~~, how do you determine which hCard on the profile page represents that person?~~
			== how to ==
			Ok I get it, show me how to both publish and parse the representative hCard for a person on a page.
			* [[representative-hcard-authoring]]
			* [[representative-hcard-parsing]]

	== use cases ==		== use cases ==
	~~Applications~~ for auto-discovery of the representative hCard for the page		What are the real world use cases, applications, for auto-discovery of the representative hCard for the page?
	* ~~representative vCard auto extraction from the page~~		* '''[[social-network-portability]]''', in particular [[hcard-supporting-user-profiles#Services_that_import_hCard_profiles\|import or preferably subscribe to a person's hCard]].
	* profile icon discovery (e.g. what people use gravatar for and have proposed pavatar for).		** profile icon discovery (e.g. what people use gravatar for and have proposed pavatar for). This appears to just be a subset of the profile import/subscribe use case and is thus listed as a nested use case.
	* ~~[[social-network-portability]]~~		* '''representative vCard auto extraction''' from the page. given a page representing a person, if you can determine the representative hCard on the page, you can convert that hCard to a vCard automatically and aggregate it into an address book service or application.

	== goals ==		== goals ==
Line 40:		Line 44:

	== see also ==		== see also ==
			* [[representative-hcard-authoring]]
			* [[representative-hcard-parsing]]
	* [[representative-hcard-examples]]		* [[representative-hcard-examples]]
	* [[representative-hcard-formats]]		* [[representative-hcard-formats]]

Tantek: clarify related but not

2007-10-25T01:36:25Z

clarify related but not

← Older revision		Revision as of 01:36, 25 October 2007
Line 1:		Line 1:
	~~{{inuse}}~~

	<h1>representative hCard</h1>		<h1>representative hCard</h1>
	{{TOC-right}}		{{TOC-right}}
Line 31:		Line 29:

	== related ==		== related ==
			The '''representative hCard''' is merely the hCard that provides information about the person that the page ''represents''.

	~~Related but slightly different concepts~~:		It is '''NOT''':
	* contact for the page. similarly, the person a page represents is usually the person to contact for/about the page. as [[hcard-faq#Should_I_use_ADDRESS_for_hCards\|documented in the hCard FAQ]], the contact for a page {{should}} be marked up with an <code><address></code> hCard.		* '''contact''' for the page. similarly, the person a page represents is usually the person to contact for/about the page. as [[hcard-faq#Should_I_use_ADDRESS_for_hCards\|documented in the hCard FAQ]], the contact for a page {{should}} be marked up with an <code><address></code> hCard.
	* author hCard. typically the person that a page represents is also the author of the page. possible (theoretical until someone finds/cites real world) examples: biographies, e.g. a page that represents person A is authored by person B.		* '''author''' hCard. typically the person that a page represents is also the author of the page. possible (theoretical until someone finds/cites real world) examples: biographies, e.g. a page that represents person A is authored by person B.
	** common misconception: ''"[http://microformats.org/discuss/mail/microformats-discuss/2007-July/010170.html using <address> works when the person is the principal author of the page]"''. This is misleading at best. It may "work", but <code><address></code> means <em>contact</em> for the page (as documented above), not necessarily the <em>author</em>. The two might coincidentally (even typically) be the same, but are not semantically equivalent.		** common misconception: ''"[http://microformats.org/discuss/mail/microformats-discuss/2007-July/010170.html using <address> works when the person is the principal author of the page]"''. This is misleading at best. It may "work", but <code><address></code> means <em>contact</em> for the page (as documented above), not necessarily the <em>author</em>. The two might coincidentally (even typically) be the same, but are not semantically equivalent.
	* owner hCard. more often than not, the person that a page represents is also the person that owns (meaning has primary control over, in the property sense) the page.		* '''owner''' hCard. more often than not, the person that a page represents is also the person that owns (meaning has primary control over, in the property sense) the page.

			"'''representative hCard'''", "contact hCard", "author hCard", and "owner hCard" are all ''different'' semantics and can be different people for any given page, even if for many pages some or all of them might be the same person.

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

Tantek at 01:26, 25 October 2007

2007-10-25T01:26:19Z

← Older revision		Revision as of 01:26, 25 October 2007
Line 2:		Line 2:

	<h1>representative hCard</h1>		<h1>representative hCard</h1>
			{{TOC-right}}
	This page is for keeping track of the representative [[hcard\|hCard]] effort, which is part of [[hcard-brainstorming]], specifically to figure out how to both explicitly specify and discover the representative hCard for a page.		This page is for keeping track of the representative [[hcard\|hCard]] effort, which is part of [[hcard-brainstorming]], specifically to figure out how to both explicitly specify and discover the representative hCard for a page.

Tantek: more content organization

2007-10-25T01:25:47Z

more content organization

← Older revision		Revision as of 01:25, 25 October 2007
Line 6:		Line 6:

	== problem statement ==		== problem statement ==

	Short version: '''Given a URL, how do you determine which hCard is the representative hCard for that page?'''		Short version: '''Given a URL, how do you determine which hCard is the representative hCard for that page?'''

	Longer: Given a URL to a page that represents a person, how do you determine which hCard on that page is the hCard for that person? Variants:		Longer: Given a URL to a page that represents a person, how do you determine which hCard on that page is the hCard for that person? Variants:
	* Given a URL to a person's [[hcard-supporting-user-profiles\|hCard supporting user profile]], how do you determine which hCard on the profile page represents that person?		* Given a URL to a person's [[hcard-supporting-user-profiles\|hCard supporting user profile]], how do you determine which hCard on the profile page represents that person?

			== use cases ==
			Applications for auto-discovery of the representative hCard for the page
			* representative vCard auto extraction from the page
			* profile icon discovery (e.g. what people use gravatar for and have proposed pavatar for).
			* [[social-network-portability]]

	== goals ==		== goals ==

	* should leverage current hCard information publishing patterns		* should leverage current hCard information publishing patterns
	* should not require any additional user interface elements (i.e. links) on any [[hcard-supporting-user-profiles\|hCard supporting user profiles]].		* should not require any additional user interface elements (i.e. links) on any [[hcard-supporting-user-profiles\|hCard supporting user profiles]].

			== methodology ==
			Methodology for a solution:
			The preferred option is to use only visible semantic HTML ([[POSH]]).

	== effort ==		== effort ==

	* [[representative-hcard-examples]] - analysis of examples of [[hcard-examples-in-wild\|hCards in the wild]] on pages representing individual people		* [[representative-hcard-examples]] - analysis of examples of [[hcard-examples-in-wild\|hCards in the wild]] on pages representing individual people
	* [[representative-hcard-formats]] - previous attempts at providing representative hCard or "person info" in general for a page that represents a person.		* [[representative-hcard-formats]] - previous attempts at providing representative hCard or "person info" in general for a page that represents a person.
	* [[representative-hcard-brainstorming]] - proposals for solving the problem		* [[representative-hcard-brainstorming]] - proposals for solving the problem

	=== ~~Representative hCard discovery~~ ===		== related ==

	~~See [[representative-hcard]].~~

	~~Ways to auto discover the representative hCard for a page, that is the hCard that is the person (or organization) that the page represents.~~

	~~Applications for auto-discovery of the representative hCard for the page~~
	* representative vCard auto extraction from the page
	* profile icon discovery (e.g. what people use gravatar for and have proposed pavatar for).
	* [[social-network-portability]]

	Related but slightly different concepts:		Related but slightly different concepts:
Line 40:		Line 38:
	* owner hCard. more often than not, the person that a page represents is also the person that owns (meaning has primary control over, in the property sense) the page.		* owner hCard. more often than not, the person that a page represents is also the person that owns (meaning has primary control over, in the property sense) the page.

	~~Methodology for a solution:~~		== see also ==
	~~The preferred option is to use only visible semantic HTML (~~[[~~POSH~~]]).		* [[representative-hcard-examples]]
			* [[representative-hcard-formats]]
	~~User scenario:~~		* [[representative-hcard-brainstorming]]
	~~Here is a scenario that outlines the proposed 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 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? for now use the first such hCard.)
	## checks to see if there is an hCard with a "url" property that points to the current page, and uses it if it finds it. similar to the above rel="me" case, if an hCard is pointing 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? for now use the first such hCard.)
	## checks to see if there is an <nowiki><address></nowiki> hCard (thus meaning contact for the page), and uses it if it finds it. (what if there is more than one such hCard on the page? e.g. such as the multiple address hCards for hAtom entries. for now use the first such hCard.)
	~~## otherwise uses the first hCard it finds (which in cases of profile URLs which have a single hCard like on~~ [~~http://flickr.com Flickr~~] ~~and [http://technorati.com/ Technorati~~]~~, will work as expected).~~
	~~# 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.~~

	~~== See Also ==~~
	* [[hcard]]		* [[hcard]]
	* [[hcard-brainstorming]]		* [[hcard-brainstorming]]

← Older revision		Revision as of 03:07, 19 November 2007
Line 9:		Line 9:

	== how to ==		== how to ==
	Ok I get it, show me how to both publish and ~~parse~~ the representative hCard for a person on a page.		Ok I get it, show me how to both publish and find the representative hCard for a person on a page.
	* [[representative-hcard-authoring]]		* how to publish: [[representative-hcard-authoring]]
	* [[representative-hcard-parsing]]		* how to find: [[representative-hcard-parsing]]

	== use cases ==		== use cases ==