Closed (fixed)
Project:
Addresses
Version:
6.x-1.0-alpha1
Component:
User interface
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
27 Jul 2008 at 15:54 UTC
Updated:
16 Aug 2008 at 02:12 UTC
Jump to comment: Most recent file
Comments
Comment #1
brmassa commentedPierre,
instead of replacing these classes, i added. Im relying on you for this fix.
soon on the next version.
regards
massa
Comment #2
pbuyle commentedThanks.
According to the hCard specification a 'vcard' element must contain exactly one 'fn' element (a 'formatted name'). If hCard compliance is not a goal, this is not an issue. Otherwise, addresses without a 'fn' element shouldn't have the 'vcard' class.
If you want to keep the 'vcard' class on the main element but reach hCard compliance, a 'fn' element should be provided. If the address has an name ('aname' field), adding a 'fn org' class attribute to its element should be enough. If the address doesn't have a name, either the 'vcard' class should be dropped or an hidden element with some default name must be created. For these 'fn' elements, the 'org' class is required to let parsers know the hCard represents contact information for a company, organization or place (see http://microformats.org/wiki/hcard#Organization_Contact_Info).
The simple attached patch (done as an exercice to refresh my CVS knowledge :)) add the vcard class only if an address name is provided and set the class of address name's element to 'fn org'.
Since 'city' is not an hCard property, leaving it in the city element should not be a problem.
Comment #3
brmassa commentedPierre,
great. patch commited!
regards,
massa
Comment #4
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.