Would this make it harder to convince Google to scrape Exhibit data? Using JSONP to get data from a few well known sites like Google Spreadsheets and EditGrid is OK, I think, and Google won't be so reluctant to scrape them. But JSONP on arbitrary sites doesn't sound appetizing to Google, I think.
David David Karger wrote: > I wonder if it is worth "standardizing" around the jsonp callback so > that people don't have to fiddle with files as exhibits move from site > to site. ie, to require that _every_ exhibit file use the foo() > convention. If it is local and we care, then exhibit can strip the > foo() wrapper and parse the file itself, instead of invoking. Could > also use a standard function name so there is no need to add the > jsonp-callback attribute either. > > Johan Sundström wrote: > >> On 5/4/07, David Navarro Arnao <[EMAIL PROTECTED]> wrote: >> >> >>> Hello, >>> >>> Can Exhibit read remote files instead of local files?. For example: >>> >>> <link href="http://simile.mit.edu/exhibit/examples/nobelists/nobelists.js"; >>> type="application/json" rel="exhibit/data" /> >>> >>> >> Not pure json files, but it does handle jsonp files or services, >> especially in the forthcoming exhibit 2.0 api. Then it looks like >> this: >> >> <link href="http://remote.site/nobelists.jsonp"; >> type="application/jsonp" rel="exhibit/data" jsonp-callback="foo" /> >> >> Then prepend "foo(" to the json file and append a ")" at the end >> (changing extension isn't necessary; feel free to keep calling it >> .js). >> >> >> > _______________________________________________ > General mailing list > [email protected] > http://simile.mit.edu/mailman/listinfo/general > _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
