By reading the diference between schema.org and Facebook Open Graph I can see that the first one is better suited to list more than one entity in a single page, I quote:

“Q: How does schema.org relate to Facebook Open Graph?

Facebook Open Graph serves its purpose well, but it doesn’t provide the detailed information search engines need to improve the user experience. A single web page may have many components, and it may talk about more than one thing. If search engines understand the various components of a page, we can improve our presentation of the data. Even if you mark up your content using the Facebook Open Graph protocol, schema.org provides a mechanism for providing more detail about particular entities on the page.
For example, a page about a band could include any or all of the following:

A list of albums
A price for each album
A list of songs for each album, along with a link to hear samples of each song
A list of upcoming shows
Bios of the band members”

Could the correct use of schema.org microdata and a well structured sitemap.xml serve the purpose of getting a one single page indexed in Google for every data it contains seperatly with a link containing the hashtag?

Sorry if I’m pointing an issue that this article doesn’t aim.

All these news capabilities with HTML 5 and JavaScript have brought the same problems raised in the past with Adobe Flash websites. Everything is limited to only one page and all content gets loaded through Ajax or flash calls to the server.

We know that search engines crawl servers for what Google calls a “HTML snapshot” in order to understand the data a website holds. Problem is that when you’re using a JavaScript page that has nothing to show up until there is an Ajax call with or without human interaction nothing exists to be analised. There are techniques for creating deep linking by using the hashtag but none of this is used at server level. So to get all content of this kind of website indexed on Google you need to go through these steps shown at https://developers.google.com/webmasters/ajax-crawling/docs/getting-started

Now this is a process that requires some knowledge programing server side scripts and forces a swap of the page location in order to provide a version for servers and a version for JavaScript, and therefore to make a website have JavaScript deep linking while still being indexed at all it’s content in search engines.

Here comes my question:

Would it be possible to provide snippets of content inserted in one page only (index.html), having all the schema.org provided for each content with the related link containing the hashtag logic, and in the end get indexed for all content?

An example would be a website containing an animated timeline with:

Avatar
read

Gladiator
read

….

and in the end have Google recognize the content for:

Avatar
http://www.domain.com/#/event-01

and

Gladiator
http://www.domain.com/#/event-02

Thanks
Peter

Regarding: ” Because RDFa simply was not going to be incorporated into HTML5, something else was needed to fill the gap.” Thankfully, this isn’t the case nowadays. See e.g.: http://dev.w3.org/html5/rdfa/

RDFa 1.1, now in Last Call, is rapidly approaching a final recommendation. It addresses a huge amount of the criticism of 1.0. Most importantly, by virtue of RDF, it already handles all kinds of data challenges by design, such as schema extensibility and making precise, decentralized statements about any kinds of things (i.e. not only the pieces of a page). Not to mention the huge toolset and storage implementations available, and the general Linked Data movement (and research space) at large.

I really recommend trying out RDFa 1.1. Note that Lite is mainly designed for newcomers to grasp the basic shape and features of RDFa. Any RDFa 1.1 processor shall support RDFa 1.1 in full though, so depending on the richness and variety of your data, you have the precision available to you if you need it. That said, the Lite subset should cover most regular needs, unless you use e.g. specific datatypes (other than date and time types, which should be covered by @datetime for RDFa in HTML5) or need @rev.

I have made an RDFa 1.1 version of your example which I put at together with a Turtle extract. (Along with attribution of course, as per your license. Naturally I’ll remove it anyway if you don’t approve of it being there.) It is mostly RDFa Lite, but I used @datatype to capture the geo coordinates as decimals, and I used @resource throughout instead of @about, which is currently under debate. Of course in any case it should be valid RDFa 1.1.

(Granted, there may be some conflations of identity here (the PNG not being the original photograph and the freebase resource possibly not being the LandmarksOrHistoricalBuildings but a record about it). But that’s another discussion.)

… it’s always the same game.

There is no real magic in Microdata :)