[uf-discuss] tel scheme for hcard? - RFC 2806
brian.suda at gmail.com
Thu Nov 10 14:53:18 PST 2005
Dougal Campbell wrote:
> brian suda wrote:
>> <a href="tapi://123456789" class="tel"><span
>> class="value">+123.456.7890</span> <abbr class="type"
>> while you COULD extract the machine readable data from the href, hcard
>> really wants the human readable format anyway. So what would be the
>> reason for using the machine data?
> Because browsers and other apps that will actually use the tapi: or
> tel: URI will want the machine-readable portion? That's part of
> semantics, too, isn't it?
With URL, hCard extracts the entire value of the @href attribute. With
EMAIL, hcard looks to see if it is in an 'a' element, if so, then it
uses the @href attribute, but only everything after the ':' in
'mailto:'. With TEL vCard is looking for a general string, so it will
always be looking for the node value of the HTML element, no matter
which is used (a, span, div, etc.) So if you wanted to mark-up your TEL
properties using an 'a' element, and use the protocol of your choice -
that is up to you, the protocol does not add/subtract any parsing value
to this situation. hCard microformat should not be effected, because it
will always be looking to the node value rather than the @href attribute.
There has been a similar discussion about using the ISBN:// protocol
as well in dealing with citations and other microformats.
 - http://microformats.org/wiki/cite-brainstorming#ISBN:.2F.2F_Protocol
More information about the microformats-discuss