One of the issues with Exhibit is that if data resides in json files (or sparql queries, or rdf/xml files jsonized on the fly via Babel, or any other way that is not embedded in HTML) search engines won't see it.
The benefit of having data served thru another URL is that it helps separating the concerns between the data producers and the data consumer (in this case, Exhibit itself). But it really sucks that in doing so, we have enabled a much better user experience for such data, but we have made it invisible to crawlers... which is less then ideal for many people that would like their pages to be found. So, one idea to keep the data and the exhibit page separate is to put the data in an iframe as HTML (eRDF, RDF/A or whatever other way of embedding exhibit data into HTML) and hide it with CSS declarations. The question was: would Google index that data if it's stored into an iframe that is made invisible? It turns out they do! http://www.google.com/search?q=34234387438474874 I added the above number to a page that is embedded in the simile.mit.edu home page and is kept hidden. I made sure that number was not available in the google index before, and now it is! Now, the only concern is that because of cross-site scripting security issues, the exhibit javascript would trigger a security exception if it tried to access the content of the iframe if the content is served from another domain. So, the question is: is there a jsonp-equivalent trick for an iframe that we can use to route around the security exception requirements? -- Stefano Mazzocchi Digital Libraries Research Group Research Scientist Massachusetts Institute of Technology E25-131, 77 Massachusetts Ave skype: stefanomazzocchi Cambridge, MA 02139-4307, USA email: stefanom at mit . edu ------------------------------------------------------------------- _______________________________________________ General mailing list General@simile.mit.edu http://simile.mit.edu/mailman/listinfo/general
