On 1/25/07, David Huynh <[EMAIL PROTECTED]> wrote: > Oh that might work! So, maybe something like this? > > <head> > <link rel="exhibit/data" type="application/json" > href="my-data.json" /> > > <link rel="exhibit/google-spreadsheets-data" type="application/jsonp" > > href="http://spreadsheets.google.com/feeds/list/o08841867754116283182.6102151849127695926/od6/public/basic?alt=json-in-javscript"; > /> > > <!-- Just for you, Google! --> > <link rel="alternate" type="application/rss+xml" title="RSS 2.0" > > href="http://www.foo.com/convert-exhibit-json-to-rss?url=http://people.csail.mit.edu/dfhuynh/my-data.json"; > /> > > <link rel="alternate" type="application/rss+xml" title="RSS 2.0" > > href="http://spreadsheets.google.com/feeds/list/o08841867754116283182.6102151849127695926/od6/public/basic"; > /> > </head> > > How confident are we that this will work?
At the very least, it is worth a shot and doing some field testing. My own take on the problem is that we could add an exporter (the options you see in the "Copy" menus of exhibits) that exports exhibit html tables that could be put on pages that then need only be decorated with a script tag pointing Simile-wards, and an onload handler, creating your exhibit given an id of the table (or tables) involved. Google is at least provably already very good at scraping content like that, and will certainly serve the correct URL. Not completely beautiful, as the data gets embedded in quite a lot of HTML cruft (html tables never were very compact, storage-wise either), but it gets the job done, and is dead simple. -- / Johan Sundström, http://ecmanaut.blogspot.com/ _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
