html - Is this proper Schema.org/Microdata markup for a building? -


i trying add microdata notation (using schema.org) website talks buildings. i’ve been reading lot i’m still having trouble figuring out use itemscope, itemtype , itemprop.

can tell me if microdata/schema.org markup or if i’m missing something?

<div class="infobox infobox_building" itemscope itemtype="http://schema.org/landmarksorhistoricalbuildings">      <!-- building name -->     <h1 class="page_title">puente golden horn metro</h1>      <!-- architect -->     <div class="data_row architect" itemscope itemtype="http://schema.org/creator">         <div class="tag cell">arquitecto</div>         <div class="value cell">             <a href="https://stage.wikiarquitectura.com/arquitecto/virlogeux-michel/" itemprop="person">michel virlogeux</a>             <a href="https://stage.wikiarquitectura.com/arquitecto/kiran-hakan/" itemprop="person">hakan kıran</a>                                                           </div>     </div>      <!-- height -->     <div class="data_row" itemscope itemtype="http://schema.org/height">         <div class="tag cell">altura</div>         <div class="value cell" itemprop="quantitativevalue">65m</div>     </div>      <!-- width -->     <div class="data_row" itemscope itemtype="http://schema.org/width">         <div class="tag cell">ancho</div>         <div class="value cell" itemprop="quantitativevalue">12,6m</div>     </div>      <!-- location -->     <div class="data_row" itemprop="address" itemscope itemtype="http://schema.org/postaladdress">         <div class="tag cell">ubicación</div>         <div class="value cell" itemprop="streetaddress">arap cami mahallesi, beyoğlu/İstanbul, turquía</div>     </div>  </div> <!-- infobox --> 

you seem confuse properties , types.

in microdata, properties specified in itemprop attribute, while types specified in itemtype attribute.

if use vocabulary schema.org, you’ll use full uri types (itemtype="http://schema.org/postaladdress"), while use slug properties (itemprop="address").

in schema.org, it’s easy see what, because follow the convention first letter of properties lowercase (address), , first letter of types uppercase (postaladdress).


syntactically, doing correctly address+postaladdress, wrong creator+person , height/width+quantitativevalue.

that said, making vocabulary errors. landmarksorhistoricalbuildings type can’t have creator nor height nor width property in first place.

you can see properties type can have visiting type’s page (landmarksorhistoricalbuildings) , checking first table.


Comments

Popular posts from this blog

php - Vagrant up error - Uncaught Reflection Exception: Class DOMDocument does not exist -

vue.js - Create hooks for automated testing -

Add new key value to json node in java -