Difference between revisions of "representative-hcard"

From Microformats Wiki
representative-hcard
Jump to navigation Jump to search
(drafted)
 
m (Replace <entry-title> with {{DISPLAYTITLE:}})
 
(10 intermediate revisions by 2 users not shown)
Line 1: Line 1:
<h1>representative hCard</h1>
+
{{DISPLAYTITLE:representative hCard}}
  
This page is for keeping track of the representative 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.
  
=== Representative hCard discovery ===
+
== problem statement ==
 +
'''Given a URL, how do you determine which hCard is the representative hCard for that page?'''
  
See [[representative-hcard]].
+
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?
  
Ways to auto discover the representative hCard for a page, that is the hCard that is the person (or organization) that the page represents.
+
== how to ==
 +
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 find/discover and parse: [[representative-hcard-parsing]]
  
Applications for auto-discovery of the representative hCard for the page
+
== use cases ==
* representative vCard auto extraction from the page
+
What are the real world use cases, applications, for auto-discovery of the representative hCard for the page?
* profile icon discovery (e.g. what people use gravatar for and have proposed pavatar for).
+
* '''[[social-network-portability]]''', in particular [[hcard-supporting-user-profiles#Services_that_import_hCard_profiles|import or preferably subscribe to a person's hCard]].
* [[social-network-portability]]
+
** 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.
 +
* '''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.
  
Related but slightly different concepts:
+
== goals ==
* 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>&lt;address&gt;</code> hCard.
+
* should leverage current hCard information publishing patterns
* 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.
+
* should not require any additional user interface elements (i.e. links) on any [[hcard-supporting-user-profiles|hCard supporting user profiles]].
** common misconception: ''"[http://microformats.org/discuss/mail/microformats-discuss/2007-July/010170.html using &lt;address&gt; works when the person is the principal author of the page]"''.  This is misleading at best. It may "work", but <code>&lt;address&gt;</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.
+
* should not use any hidden metadata on 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.
+
* should not use any hidden side files (e.g. random XML)
  
 +
== methodology ==
 
Methodology for a solution:
 
Methodology for a solution:
 
The preferred option is to use only visible semantic HTML ([[POSH]]).  
 
The preferred option is to use only visible semantic HTML ([[POSH]]).  
  
User scenario:
+
== effort ==
Here is a scenario that outlines the proposed auto-discovery process:
+
* [[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-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 ==
 +
The '''representative hCard''' is merely the hCard that provides information about the person that the page ''represents''.
 +
 
 +
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>&lt;address&gt;</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.
 +
** common misconception: ''"[http://microformats.org/discuss/mail/microformats-discuss/2007-July/010170.html using &lt;address&gt; works when the person is the principal author of the page]"''.  This is misleading at best. It may "work", but <code>&lt;address&gt;</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.
 +
 
 +
"'''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.
  
# I (as user) give the URL of my homepage or hCard or other profile URL, to a site that wants a profile icon
+
For more on these semantic distinctions, see [[hcards-and-pages]].
# 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 ==
+
== see also ==
* [[hcard]]
+
{{representative-hcard-related-pages}}
 
* [[hcard-brainstorming]]
 
* [[hcard-brainstorming]]

Latest revision as of 16:32, 18 July 2020


This page is for keeping track of the representative 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.

problem statement

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 (e.g. an hCard supporting user profile), how do you determine which hCard on that page is the hCard for that person?

how to

Ok I get it, show me how to both publish and find the representative hCard for a person on a page.

use cases

What are the real world use cases, applications, for auto-discovery of the representative hCard for the page?

  • social-network-portability, in particular import or preferably subscribe to a person's hCard.
    • 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.
  • 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

  • should leverage current hCard information publishing patterns
  • should not require any additional user interface elements (i.e. links) on any 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 for a solution: The preferred option is to use only visible semantic HTML (posh).

effort

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

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

It is NOT:

  • contact for the page. similarly, the person a page represents is usually the person to contact for/about the page. as documented in the hCard FAQ, the contact for a page SHOULD be marked up with an <address> 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.
  • 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.

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

see also