Just to put all my previous thinking in one place, I think we should
support something like this:
<html>
<head>
<link rel="exhibit-data" type="application/json"
href="my-data.json" />
<link rel="exhibit-data" type="application/rdf+xml"
href="rdf-xml-blob.rdf" />
<link rel="exhibit-data" type="application/n3"
href="n3-blob.n3" />
<link ref="exhibit-data" type="text/html"
href="#an-html-table-of-data" />
<link ref="exhibit-data" type="text/plain"
href="#a-cdata-section" />
<link rel="exhibit-data" type="text/bibtex"
ex:importer="..."
href="my-papers.bib" />
<link rel="exhibit-data" type="application/jsonp"
ex:importer="..."
href="http://spreadsheets.google.com/..."; />
<script src=".../exhibit-api.js"></script>
</head>
<body ex:ondataload="do something with 'database' variable">
...
</body>
</html>
You don't have to have ex:ondataload. By default, that will be a handler
for constructing an exhibit. But if you have it, then you can do custom
things with 'database'.
Now we can tell Google: there is *zero* javascript to execute; so, don't
be afraid, just scrape those <link>s.
But obviously, spammers can hide spam in those links, too. RDF will be a
great place to hide spam--hope somebody is making an RDF spam filter. :)
I suppose in the future one might code one of those unsolvable logic
puzzles in RDF and gets the Google crawler to reason it out... :)
Eventually, "exhibit-data" in that code above will just become "data"
and <script src=".../exhibit-api.js"></script> will go away.
David
David Karger wrote:
> one other question about your method: can I combine it with the standard
> method? eg put a pointer to some schema in a link from the head while
> putting actual data into the html table?
_______________________________________________
General mailing list
[email protected]
http://simile.mit.edu/mailman/listinfo/general
