would it be bad to put <span> tags within the <head>, for grouping meta data in schema.org format?

Posted by hdavis84 on Pro Webmasters See other posts from Pro Webmasters or by hdavis84
Published on 2012-07-01T02:55:23Z Indexed on 2012/07/01 3:24 UTC
Read the original article Hit count: 212

Filed under:
|

Alright, I'm currently practicing schema.org microdata, and trying to find the best route for every site I build. I have found that i can piggyback itemprops on open graph meta tags. I would like to piggyback more itemprops on opengraph meta tags. However, schema.org requires you to change itemtypes to define all aspects of a "thing".

Say I'm defining a LocalBusiness. Open graph has street address, locality, and region i'd like to piggyback on. I'd have to do something like:

<html lang="en" itemscope itemtype="http://schema.org/LocalBusiness">
  <head>
    ...
    <meta itemprop="name" content="Business Name" />
    <meta property="og:url" itemprop="url" content="http://example.com" />
    <meta property="og:image" itemprop="image" content="http://example.com/logo.png" />
    <span itemprop="address" itemscope itemtype="http://schema.org/PostalAddress">
      <meta property="og:street-address" itemprop="streetAddress" content="1234 Amazing Rd." />
      <meta property="og:locality" itemprop="addressLocality" content="Greenfield" />
      <meta property="og:region" itemprop="addressRegion" content="IN" />
    </span>
  </head>

Although there's more that can be added in, this is enough of an example to show what I'm trying to achieve. I've searched the web to see if it is an issue to use spans in the head or not, because I don't want invalid markup. I know I can mark up the address information in the body of the pages, but the route above would be more efficient. Does anyone have an answer for this?

© Pro Webmasters or respective owner

Related posts about html5

Related posts about microdata