[uf-discuss] class="url"?

Siegfried Gipp siegfried at rorkvell.de
Sun Nov 5 13:15:33 PST 2006

Am Sonntag, 5. November 2006 19:50 schrieb Scott Reynen:

> <div id="footer2" class="vcard">
>    <address><span class="fn org">The British Museum</span>, <span
> class="street-address">Great Russell Street</span>, <span
> class="locality">London</span> <span class="postal-code">WC1B 3DG</
> span>  | <a href="http://www.finds.org.uk/legal/disclaimer.php"
> title="Legal disclaimer">Disclaimer</a> | <a href="http://
> www.finds.org.uk/legal/privacy.php" title="Our privacy
> policy">Privacy Policy</a> | &copy; 2006 <br>
>    E: <a href="mailto:info at finds.org.uk" title="Contact the Scheme"
> class="email">info at finds.org.uk</a> <span class="tel">T: +44 (0)20
> 7323 8611</span></address> </div>
> They have a link to their privacy policy and legal disclaimer within
> the vCard.  Any suggested change to hCard needs to allow for this,
> because this is what publishers do on the web today.

Interesting, and quite logical. This has no <a class="url">. So which of these 
urls to export to a VCARD URL property? So first i would replace this:
<span class="fn org">The British Museum</span>
with this:
<a class="fn org" href="http://....">The British Museum</a>
Then either you may simply define that a link related to a persons or 
organisations name is most related to that person or organisation, thus avoid 
the url class name. Or you might add the class name of url to explicitely 
specify that exactly this url is the one to be exported. But then the 
microformats url is different from the w3c url. According to w3c, f.ex. the 
email url is a url, too. According microformats syntax, only the content of 
the <a> element with the class name of url is _the_ url. The usage of the 
word "url" is different then. That would be fine, but should be clarified.

> >> It may seem redundant, but it is the only way to disambiguate random
> >> links with links associated with the vcard/vevent
> >
> > That is a point already mentioned. And this may indeed be true.
> > Although still
> > i think _inside_ a vCard or vEvent record there sould not be random
> > links,
> > but only links related to that hCard or vEvent.
> We're not telling publishers what they should be publishing.  We're
> just helping them publish it with more descriptive markup.
> >> It may seem redundant, but it is the only way to disambiguate random
> >> links with links associated with the vcard/vevent
> >
> > So what now?
> That depends: what practical problem are we trying to solve here?
> > Do we define that any link within a hCard/vEvent record is by
> > definition related to that record?
> No.  That doesn't accurately describe the intended meaning of
> publishers using links with a block of contact information.
> > Or,
> > does a hCard/vEvent record contain random urls, of which only one
> > is related
> > to the record?
> Yes.
> > Then you may consider to classify this one and only link with
> > class="url".
> That's what hCard does.
> > But then the meaning of this url is not "any general url", since
> > it is not any url to any random data, but it is _the one specific_
> > url. This
> > is different from the w3c definitions.
> Yes, it is different.  The more specific meaning comes from the more
> specific context.  Why is this a problem?
> Peace,
> Scott
> _______________________________________________
> microformats-discuss mailing list
> microformats-discuss at microformats.org
> http://microformats.org/mailman/listinfo/microformats-discuss

More information about the microformats-discuss mailing list