[microformats-discuss] Shouldn't hCard use <address>?

[Stephen Malone]

Oh, so it's situational?  I guess that makes a bit of sense.  Thanks for
clearing it up.

Stephen
On Sat, 2005-06-25 at 09:06 -0700, Tantek Çelik wrote:
> The short answer about <address> is:
> 
> 1. Yes it is more semantic, but
> 
> 2. It is *too* specifically semantic for most hCard uses.
> 
> The poorly named <address> really means <contact-info-for-this-web-page>
> 
> So it only makes sense to use <address> for an hCard *IF* that hCard
> represents the contact information for the page.  Hence the usage on my
> blog.
> 
> Another way of saying this:
> 
> Every <address> on a page SHOULD be an hCard.
> 
> But not every hCard should be an <address>
> 
> I think this question has come up often enough (and I've seen it on some
> blogs too) that it deserves top billing in the hcard-faq.  Just created:
> 
>  http://microformats.org/wiki/hcard-faq
> 
> Thanks,
> 
> Tantek
> 
> 
> On 6/25/05 4:30 AM, "Bud Gibson" <bud at thecommunityengine.com> wrote:
> 
> > Well, the example helps clear up the point.  Probably a good practice
> > for moving these conversations along.
> > 
> > The list is very new.  There is a link to the archive at:
> > 
> > <http://microformats.org/mailman/listinfo/microformats-discuss/>
> > 
> > but when I tried it yesterday, it returned a file not found error.
> > 
> > Ryan, are you the guy to fix that?
> > 
> > Bud
> > On Jun 25, 2005, at 7:21, Robert Bachmann wrote:
> > 
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >> 
> >> Bud Gibson wrote:
> >> 
> >>> Stephen:
> >>> 
> >>> You are right that <div>s and <span>s do not imply any special
> >>> semantics.  All of that comes in the class (and where relevant rel)
> >>> attributes for these elements.
> >>> 
> >>> The trick to microformats is that they use standard xhtml markup
> >>> elements but qualify their meaning
> >>> through the class attribute.  This admittedly can be less
> >>> powerful  than
> >>> going and defining new markup elements (say through a namespace)
> >>> that
> >>> could then have their own special attributes, etc.  However, by
> >>> avoiding namespaces or even defining whole new vocabularies,
> >>> microformats remove a lot of barriers to implementation.
> >>> Perhaps,  most
> >>> importantly, implementers can use markup they are familiar with.
> >>> 
> >> 
> >> I think that Stephen wanted to say that something like e.g:
> >> 
> >> <address class="vcard">
> >>  <a class="url fn" href="http://tantek.com/">
> >>   Tantek Çelik
> >>  </a>
> >>  <div class="org">Technorati</div>
> >> </address>
> >> 
> >> ... is more semantic, than e.g:
> >> 
> >> <div class="vcard">
> >>  <a class="url fn" href="http://tantek.com/">
> >>   Tantek Çelik
> >>  </a>
> >>  <div class="org">Technorati</div>
> >> </div>
> >> 
> >> Robert
> >> 
> >> P.S:
> >> I'm new to this list.
> >> Is there an archiv of this malinglist?
> >> http://microformats.org/mailman/listinfo/microformats-discuss/
> >> links to
> >> the non-existing page
> >> http://microformats.org/pipermail/microformats-discuss/
> >> 
> >> - --
> >> Robert Bachmann <rbach at rbach.priv.at> (OpenPGP KeyID: 0x4A5CCF10)
> >> -----BEGIN PGP SIGNATURE-----
> >> Version: GnuPG v1.4.1 (MingW32)
> >> 
> >> iD8DBQFCvT4lmnUcPUpczxARAhwHAJ9Cc+aAyQX5SWmNMf90fitGzCAY6ACZAVM7
> >> tEQEvhzN8GvK/aPuOoEeN+w=
> >> =CoYi
> >> -----END PGP SIGNATURE-----
> >> _______________________________________________
> >> microformats-discuss mailing list
> >> microformats-discuss at microformats.org
> >> http://microformats.org/mailman/listinfo/microformats-discuss
> >> 
> >> 
> > 
> > _______________________________________________
> > microformats-discuss mailing list
> > microformats-discuss at microformats.org
> > http://microformats.org/mailman/listinfo/microformats-discuss
> 
> _______________________________________________
> microformats-discuss mailing list
> microformats-discuss at microformats.org
> http://microformats.org/mailman/listinfo/microformats-discuss