Is it possible to use the same meta tag for opengraph and schema.org

Question

I dont like the amount of tags in the head of my document. here is an example of some meta tags.

<!--w3c-->    
<title>Page Title</title>
<meta name="description" content="great description">

<!--schema.org-->
<meta itemprop="name" content="Page Title">
<meta itemprop="description" content="great description">

<!-- opengraph-->
<meta property="og:title" content="Page Title">
<meta property="og:description" content="great description">

Is it possible to combine the tags/properties to reduce the code size without affecting SEO? for example
<title itemprop="name">Page Title</title>
itemprop attributes can be used anywhere so I'm pretty sure this is fine but as far as i am aware the property="og:*" attribute must be used with a meta tag.
So is the following markup acceptable?

<meta name="description" itemprop="description" property="og:description" content="great description">

and how will this affect SEO?

many thanks

Answer 1

HTML+RDFa 1.1 and Microdata extend HTML5’s meta element.

HTML+RDFa 1.1 (W3C Recommendation) defines:

If the RDFa @property attribute is present on the meta element, neither the @name, @http-equiv, nor @charset attributes are required and the @content attribute MUST be specified.

Microdata (W3C Note) defines:

If a meta element has an itemprop attribute, the name, http-equiv, and charset attributes must be omitted, and the content attribute must be present.

That means:

• It’s not allowed to use Microdata’s itemprop attribute together with HTML5’s name attribute.

• It’s allowed to use RDFa’s property attribute together with HTML5’s name attribute:

  <meta name="description" property="og:description" content="great description" />
  

  (possibly an issue with having this in the body instead of the head)

• It seems to be allowed to use Microdata’s itemprop attribute together with RDFa’s property attribute if HTML5’s name attribute is not provided:

  <meta itemprop="description" property="og:description" content="great description" />
  

  (but the W3C Nu Html Checker reports an error)