On 1/24/07, Philip Cooper <[EMAIL PROTECTED]> wrote: > Why Google spreadsheet if you want JSON?
Because it offers JSONP. Not perfect, and certainly about as much cruft overhead as an xml feed, but good enough for basic functionality. > Has anyone looked at > > http://www.EditGrid.com Nobody has yet presented a way of getting it to expose JSONP data access, which Exhibit needs, being a 100% client side application. > Even better, you can upload an xsl file and define the extension > associated with the xslt transformed file (rdf/xml or perhaps JSON > anyone?). This sounds potentially workable, if a bit roundabout. Can we upload an xslt template of our own to reformat a spreadsheet however we want? That would make Exhibit integration *possible*, in a slightly perverted sort of way. :-) At 100% wire format efficiency, even, if a tad more setup work for data owners. (Unless we can specify our arbitrary xslt file in the URL as data consumers.) > Sorry if it's OT. I am just looking at JSON/exhibit as I am exposing > my rdf to the web with turbogears which has JSON built in. Genshi > transforms on the exhibit json standard ... I'd say we're pretty much on topic, anyway. https://wiki.editgrid.com/wiki/API does not seem to confirm we can do any of the above without providing our own server side software, though, but I could be wrong. Asking them to add JSONP might be another route; given that, we can do the rest of the work tying it to Exhibit. Should you feel like coaxing them into that, you might have some use for this article, aimed at web service data providers of all sorts, describing the whys and hows in much context and detail: http://ecmanaut.blogspot.com/2006/01/jsonp-recipe-for-visitor-innovation.html -- / Johan Sundström, http://ecmanaut.blogspot.com/ _______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
