(Difference between revisions)

Jump to: navigation, search
m (letoelli)
m (Reverted edits by AcelcOzell (Talk) to last version by Brian)
Line 1: Line 1:
<h1> hCard User Interface </h1>
<h1> hCard User Interface </h1>
Line 6: Line 5:
== Authors ==
== Authors ==
* [http://allinthehead.com/ Drew McLellan]
* [http://allinthehead.com/ Drew McLellan]
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]
* [http://tantek.com/ Tantek Çelik], [http://technorati.com Technorati, Inc]
== Single Input Field for Names ==
== Single Input Field for Names ==

Revision as of 10:09, 8 January 2009

hCard User Interface


This page is for techniques and issues surrounding user-interfaces to author, publish, and display hCards.


Single Input Field for Names

When capturing name data that is later to be presented as a hCard, it's important that the data is collected at the highest fidelity possible. As not all names are suitable for hCard's implied-n optimisation (and therefore can't be output as fn, with n omitted), capturing component parts of the name individually enables the proper construction on n when generating the hCard.

Sometimes, however, constraints require a name be collected with a single field. Once such example is common blog CMSs (WordPress, TextPattern) that use a single database field to store the name against each post comment. In such cases it is always desirable to find a way to collect the name with higher fidelity. However, if this simply cannot be done, the implementer could chose to attempt to best-guess the component parts of the name to form a valid n.

One suggested 'best-guess' algorithm might be:

  1. If the name is one word, attempt implied nickname optimization
  2. If the name is two words, attempt implied n optimization
  3. For three or more words
    1. Perform a lookup against known sub-name combinations (e.g. 'Sarah Jane', 'Vander Wal')
    2. Apply the grammar "(honorific-prefix) given-name additional-name(s) family-name (honorific-suffix)"

The principal behind this suggestion is that it's better to make a good guess and potentially miscategorise an ambiguous name component than to generate an invalid hCard.

Additional user interface

Some examples of additional user interface for hCard. Note that most of these actions should be applicable to all instances of the microformat on the page at once (e.g. export all contacts), of for a selection of instances (e.g. export selected contacts), or one just one specific instance (e.g. export contact XYZ).

address book integration

desktop to phone transfer

telephony integration

fax integration

birthday planning

address canonicalization

data export

see also

The hCard specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.

hcard-user-interface was last modified: Wednesday, December 31st, 1969