Difference between revisions of "hcard-examples-in-wild-with-problems"

From Microformats Wiki
hcard-examples-in-wild-with-problems
Jump to navigation Jump to search
(Sylphen)
(www.bo.ingv.it)
Line 17: Line 17:
 
==Examples with problems==
 
==Examples with problems==
  
 +
* [http://www.bo.ingv.it/contents/INGV-Bologna/Staff.html INGV Bologna] implemented hcards for staff-members, marked-up as HTML table-rows ([http://microformats.org/wiki/include-pattern include-pattern] also used to add organization-name and fax-number to each hcard).
 +
**'''sub-optimal''': missing includes. [[User:AndyMabbett|Andy Mabbett]] 13:53, 3 Oct 2007 (PDT)
 
* [http://www.Sylphen.com Sylphen] is a IT-solutions-provider and uses hCards on the [http://www.sylphen.com/content/kontakt/kontakt.htm Contact]
 
* [http://www.Sylphen.com Sylphen] is a IT-solutions-provider and uses hCards on the [http://www.sylphen.com/content/kontakt/kontakt.htm Contact]
 
** '''invalid''' two of the three examples lack the required <code>fn</code> or <code>fn org</code> property
 
** '''invalid''' two of the three examples lack the required <code>fn</code> or <code>fn org</code> property

Revision as of 20:53, 3 October 2007

hCard examples in the wild, with problems

This page is an informative section of the hCard specification.

The following sites have published hCards, which are either invalid or problematic.

Guidelines for use

Entries may be moved here, from hCard Examples in the wild, if there's a problem with the way hCards are used on the page concerned. If the page is yours, and you want to improve it, see the hCard FAQ, or raise any queries on hCard Issues or the mailing list, where people will be happy to help you.

Please consider distinguishing problems as:

  • invalid - the hCard is invalid and cannot be parsed by a parser for any information due to the problem.
  • suboptimal - the hCard is technically valid, yet either has one or more properties that have no data due to a markup problem (e.g. adr without children), and/or there is data inside the hCard markup which could be marked up with an hCard (sub)property but isn't.
  • hidden - one or more of the hCard's (sub)properties are hidden via CSS or other mechanism and are thus potentially out-of-date or vulnerable to being labelled as spam by search engines.

Examples with problems

Related Pages

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.