On Monday, September 18, 2006 9:59 AM Ryan King wrote > > Using a compound class name of "hcard contact" might be a good way to > > distinguish the contact info for the author in lieu of using the > > <address> element.
> I agree it may be worthwhile to require a classname to > distinguish the person's current contact information from > previous hCards. We need to look at more existing examples > first, though (I haven't looked at David's post below, yet). Excellent. From the discussion at blogmatrix [1], David mentions the need for distinguishing class name on hCards in the experience section as well. > Essentially, the "title" of an experience unit is brought in from a hCard; > however, there is no explicit class name for the hCard, so it's possible > that a different hCard in the experience unit (say, the contact information > for your supervisor) could be interpretted as the wrong hCard." [1] http://blogmatrix.blogmatrix.com/:entry:blogmatrix-2006-09-16-0000/ _______________________________________________ microformats-discuss mailing list microformats-discuss@microformats.org http://microformats.org/mailman/listinfo/microformats-discuss
