[was: Exhibits invisible to Google]
David Karger wrote:
> I would posit the following pessimistic principle: that the only way a
> google search for exhibit data will point back to the html page wrapping
> the exhibit is if the exhibit data is actually in the html page. I
> think the question to focus on is, what is the easiest way to get
> exhibit data into the html page. There are some actual advantages to
> this approach---people without javascript can still get a look at the
> data. Options we've discussed include:
>
> [snip]
All of these options are indeed pessimistic--our unconditional
submission to the search engine super-power(s).
It is ironic that in the beginning, the search engines submitted to
dirty HTML that existed before them, swallowing broken code just to
provide a competitive service. Now, as we are making Web data "cleaner"
and presumably more palatable to search engines, we are being completely
ignored by them.
And this problem applies to RDF/XML and N3, not just to Exhibit JSON.
Correct me if I'm wrong, but I don't think Google crawls RDF/XML and N3
files.
While I'm totally flattered that Ivan Herman has tried Exhibit himself,
e.g.,
http://homepages.cwi.nl/~ivan/AboutMe/CV/Publ.html
I'm afraid I might have done him a disservice--making his publications
page invisible to Google! Sorry :-(
And, more sadly, that "RDF" link at the top of the page--bait for the
promised AI of the future--doesn't help in the presence.
What can we do?!
David
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
