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
You can identify a node by giving it a URI, specified in the @id keyword. This URI can be used to reference that node. See the section “Node Identifiers” in the JSON-LD spec. So your main event could get the URI http://example.com/2016-04-21#main-event: <script type=”application/ld+json”> { “@id”: “http://example.com/2016-04-21#main-event”, “@context”: “http://schema.org”, “@type”: “Event”, “name”: “MainEvent”, “startDate”: “2016-04-21T12:00” … Read more