- From: Brian Suda <brian.suda@gmail.com>
- Date: Fri, 25 Aug 2006 00:10:39 -0500
- To: public-grddl-wg <public-grddl-wg@w3.org>
Harry (and anyone else) i have read through the ECMAscript description, but i think i am still slightly confused. Can some one go through a step-by-step example of how an ECMAscript transformation would work? The reason why I ask, is because of all this XMLHTTPRequest Ajax stuff always runs into problems making requests to servers that are not within the same domain. This is a "security feature" so you can not load untrusted code. Could/would a GRDDL transformation on the client-side load some script that is "suppose to do a transformation" but could do anything from a foreign host? I guess you can already use any URL as the @src on a script element already, so browsers have to deal with this already in some way. Am i missing something? -brian Harry Halpin wrote: > > Not sure: Do people think GRDDL "MUST support ECMAscript[1]" I mean, I > > think it makes sense, as most GRDDL implementations should be able to > > call javascript easily enough - what do people think?" > > > > A GRDDL implementation MUST use the content type of the transformation > > to determine the what the transformation is." > > > > Although we have "application/ecmascript" and "application/javascript", > > it appears that there isn't a media type for "application/xslt+xml" > > quite yet [2]... > >
Received on Friday, 25 August 2006 05:12:26 UTC