schema.org - Why does Google Testing Tool use the "id" attribute to generate a URL for the Microdata item? -



schema.org - Why does Google Testing Tool use the "id" attribute to generate a URL for the Microdata item? -

i'm using microdata describe blog post, , i'm surprised value homecoming schema.org’s blogposting google developers testing tool.

i have expected itemprop url, not merge of website url , item id. doing wrong, or google display issue?

class="lang-html prettyprint-override"><div itemscope="itemscope" itemprop="blogpost" itemtype="http://schema.org/blogposting" id="foobar"> <a itemprop="url" href="/realone">real</a> </div>

value returned https://developers.google.com/structured-data/testing-tool/:

class="lang-none prettyprint-override"> blogposting: http://www.example.com/foobar url: http://www.example.com/realone

this strange.

it’s not conforming microdata note. apart microdata’s itemref attribute, html5’s id attribute has no special meaning in microdata.

if google wants utilize id value anyway, should @ to the lowest degree generate url fragment identifier, i.e., http://www.example.com/#foobar.

my guess (probably unintentionally) handling html5’s id attribute same way microdata’s itemid attribute. if using itemid instead of id in example, google’s testing tool output same, time correct.

schema.org microdata google-rich-snippets structured-data

Comments

Popular posts from this blog

java - How to set log4j.defaultInitOverride property to false in jboss server 6 -

c - GStreamer 1.0 1.4.5 RTSP Example Server sends 503 Service unavailable -

Using ajax with sonata admin list view pagination -