0

I currently write the markup for an article page and have a problem with nested microdata. See the markup below:

<article itemscope itemtype="http://schema.org/Article">
    (...)

    <footer>
        <figure itemprop="author" itemscope itemtype="http://schema.org/Person">
            <img itemprop="image">
            <figcaption>
                posted by
                <a itemprop="name">John Doe</a>
                about
                <a itemprop="about">love</a>
            </figcaption>
        </figure>
    </footer>
</article>

I want to use the itemprop="about" for itemtype="http://schema.org/Article". But the Google testig tool says that itemprop="about" is not valid for itemtype="http://schema.org/Person".

Is it possible to declare that itemprop="about" refers to itemtype="http://schema.org/Article" and not to itemtype="http://schema.org/Person" without changing the Markup?

Toni Feistauer
  • 411
  • 4
  • 10
  • Google testing seems to only select and validate certain microdata tags, while the schema.org website listing shows many tags that I think are all the possible ones. To be honest the whole act of implementing microdata is a tedious pain in the arse and I look forward to the developers of microdata making it easier to implement. I remember having issues with About and instead used "descr", I think. Good luck – Martin Mar 25 '15 at 13:43
  • yes it is a pain... When i take the prop `about` out of type `Person` it works fine. But this is not possible due to the design of the page. The author and the tag ("love") have to be in the same sentence. – Toni Feistauer Mar 25 '15 at 13:57
  • "without changing the Markup": What *exactly* can’t be changed, and what may be changed? Is adding additional `div`/`span` elements okay? Changing attributes okay? – unor Mar 25 '15 at 14:09
  • yes adding attributes or additional elements is ok, but I can't move `love` out of `
    `. Like I said, `John Doe about love` has to be in one sentence.
     – Toni Feistauer Mar 25 '15 at 15:47
  • 1
    I have suggested that this is a duplicate - see above. In your case though, you would need to use a `` element around the `` to have an element to which the hiding itemscope attribute can be applied. – Alohci Mar 30 '15 at 00:01

0 Answers0