• Resolved Dan Knauss

    (@dpknauss)


    This is what the source will look like for a phone number that’s part of the schema.org microformat for a small business:

    <div itemscope itemtype="http://schema.org/LocalBusiness" class="address">
       <span itemprop="name">
       <a href="/" title="name">Business Name</a></span>
       <div itemprop="address" itemscope itemtype="http://schema.org/PostalAddress" class="address">
         <span itemprop="streetAddress">555 North 55th Street,</span> 
         <span itemprop="addressLocality">City</span>, <span itemprop="addressRegion">State</span> 
         <span itemprop="postalCode">55555</span>
       </div>
       Phone: <span itemprop="telephone"><script type="text/javascript">(function(){var ml=" 28(-041)",mi="36768066642155",o="";for(var j=0,l=mi.length;j<l;j++){o+=ml.charAt(mi.charCodeAt(j)-48);}document.write(o);}());</script><noscript>*protected email*</noscript></span>
    </div>

    I’m guessing this is probably not kosher.

    And what if you have made a phone number into a link?

    There is no established convention for semantic markup for phone numbers, but something like this should generate a link that’s understood as a phone number in most devices and browsers:

    <span itemprop="telephone">
        <a href="tel:+1-888-888-8888">(888) 888-8888</a>
    </span>

    It there a way to do this with EEB?

Viewing 1 replies (of 1 total)
  • Pi Zi

    (@freelancephp)

    You could use this within your posts:

    <span itemprop="telephone">
        [eeb_content]<a href="tel:+1-888-888-8888">(888) 888-8888</a>[/eeb_content]
    </span>

    Or this within your templates:

    <span itemprop="telephone">
    <?php
    if (function_exists('eeb_content')) {
        echo eeb_content('<a href="tel:+1-888-888-8888">(888) 888-8888</a>');
    }
    ?>
    </span>
Viewing 1 replies (of 1 total)

The topic ‘Is encoding OK with microformats?’ is closed to new replies.