Difference between revisions of "representative-hcard"

From Microformats Wiki
representative-hcard
Jump to navigation Jump to search
(more content organization)
m
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.
  

Revision as of 01:26, 25 October 2007

This article is actively undergoing a major edit for a short while.

As a courtesy, please do not edit this page while this message is displayed.

The user who added this notice will be listed in the page history. If this page has not been edited for over an hour, please remove this template.

This message is intended to help reduce edit conflicts; please remove it between editing sessions to allow others to edit the page.

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.

problem statement

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:

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

  • should leverage current hCard information publishing patterns
  • should not require any additional user interface elements (i.e. links) on any hCard supporting user profiles.

methodology

Methodology for a solution: The preferred option is to use only visible semantic HTML (posh).

effort

related

Related but slightly different concepts:

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

see also