Woops! Just a little more detail:
Having a GET version of Babel may be useful for some for the following reasons: 1. If you are generating one of the source formats (N3, RDF/XML, etc) automatically via a a PHP, Perl, or Python script that's already web-enabled, here's a way to basically "pipe" that information into Babel with a single request. 2. Amazon.com (among others) does XSL transformations on-the-fly with something like there, where they have their Data (in XML), the presentation (an XML Stylesheet), and then both of those are presented in the URL, the server then renders the final HTML to the user based on those two. 3. This allows URLS to become filters, more or less... as in, if I know of data in one of the source formats, and I'd like to see it in Exhibit, I can merely tack that URL onto the end of a Babel URL, and then, viola, Babel renders the Exhibit directly from the data, with no form submission required. Would be interested in hearing others thoughts, or if anyone does similar with other technologies, and what has perhaps been important there. Thanks, Thomas On 1/30/07, Thomas Winningham <[EMAIL PROTECTED]> wrote:
On the Dev list, David pointed out that the traffic from something like this might not be good for the production Babel server, but here's the source. Any ideas? Comments? See below, and attached. /uripreview?reader=n3&writer=exhibit-json&mimetype=default&template= exhibit.vt&URI=http%3A%2F%2Fwww.example.org%2Fexample.n3 /uritranslator?reader=n3&writer= rss1.0&mimetype=application%2Fxml&URI=http%3A%2F%2Fwww.example.org%2Fexample.n3 ... as GET requests. Thanks, Thomas ---------- Forwarded message ---------- From: Thomas Winningham < [EMAIL PROTECTED]> Date: Jan 28, 2007 2:16 PM Subject: Babel Idea: livetranslator & livepreview To: [EMAIL PROTECTED] See source. Perhaps something like this is doable? /uripreview?reader=n3&writer=exhibit-json&mimetype=default&template= exhibit.vt&URI=http%3A%2F%2Fwww.example.org%2Fexample.n3 /uritranslator?reader=n3&writer= rss1.0&mimetype=application%2Fxml&URI=http%3A%2F%2Fwww.example.org%2Fexample.n3 This is a GET request, and an extra querystring variable. See the source! I'd hate for the code to be duplicated so much between the servlets, however... but the source here works well. The general idea is to provide Babel's services via GET instead of POST for a single net-available source. Thanks, Thomas
_______________________________________________ General mailing list [email protected] http://simile.mit.edu/mailman/listinfo/general
