Your markup is valid HTML5+Microdata and you are using the Schema.org vocabulary appropriately. With “validator”, you probably refer to Google’s Structured Data Testing Tool. Note that errors shown in this tool don’t necessarily mean that your markup is wrong; they often mean that you won’t get a certain Google search result feature unless you provide … Read more
If SiteNavigationElement is meant for the whole navigation (i.e., a navigation link list), your first example is correct. If SiteNavigationElement is meant for a single navigation entry (i.e., a link in the navigation link list), your second example is correct. I think Schema.org doesn’t unambiguously define which variant is meant, as they only say: A … Read more
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, … Read more
The usual HTML way would be to use one attribute and separate several values with space characters. Looking into the Microdata specification, you’ll notice that this is the case for the itemprop attribute, too: The itemprop attribute, if specified, must have a value that is an unordered set of unique space-separated tokens […] So this … Read more
There is no benefit in having single or multiple data blocks, other than limitations around how you might store and manage schema data in your website. For example, you might need them separate if different components within your website are responsible for generating each data block independently. Alternatively, if your website is able to manage … Read more
The Microdata specification only differs between these types of values, which get derived from the HTML5 markup: item (if an element has an itemprop and an itemscope attribute) absolute URL (if the itemprop is specified on an URL property element like a, video etc.) datetime (if the itemprop is specified on a time element) string, … Read more
The data can be placed anywhere. From Google’s documentation: The data, enclosed within the <script type=”application/ld+json”> … </script> tags as shown in the examples below, may be placed in either the <HEAD> or <BODY> region of the page that displays that event. You can also use data dynamically fetched using AJAX: JSON-LD markup inserted by … Read more
So, to start with a couple of cliche’s and mangled metaphors – we’re talking apples and oranges a bit comparing OG and Schema.org, and when it comes to this metadata it’s horses for courses. The right answer depends on your intent, in adding metadata to your page. What is it that you’re hoping to gain? … Read more
Google’s documentation only mentions that they can consume dynamically added structured data if the syntax JSON-LD is used: Also, Google can read JSON-LD data even when it is dynamically injected into the page’s contents, such as by Javascript code or embedded “widgets”. This does not necessarily mean that they can’t read it in case of … Read more
About itemref: it has to be specified on elements with itemscope it is used to reference other properties (= itemprop in Microdata) So this means for you: move itemref to the Hotel move itemprop=”branchOf” to the Organization Minimal example: <div itemprop=”branchOf” itemscope itemtype=”http://schema.org/Organization” id=”schema-organization”> <h1 itemprop=”name”>The Hotel Chain</h1> </div> <div itemscope itemtype=”http://schema.org/Hotel” itemref=”schema-organization”> <h2 itemprop=”name”>Hotel … Read more