On Tue, Dec 03, 2002 at 03:04:46PM +0100, Eric van der Vlist wrote:
Hi Daniel,
On Tue, 2002-12-03 at 14:43, Daniel Veillard wrote:
That would be sufficient for XML-RPC driven XSLT interraction.
Simple framework, easy deployment, and everything is kept at the markup
and structure level.
Speaking of simple framework and easy deployment, the simplest thing I
have seen so far is sometimes called REST :-) .
Translated into XSLT, this gives something such as:
<xsl:variable name="response"
select="document('http://example.com/bar.cgi?order=Gimme+beer')"/>
It doesn't even need any exslt extension (except maybe to encode the
query string) and is just plain standard XSLT.
For those of you who read French, I came to the same (controversial)
conclusion on a real world case recently on XMLfr:
The problem is if you want to pass a bit more structure. That ought
to be possible in an XSLT/XML framework (and without requiring hundred
of pages of underlying specifications :-)
Daniel
--
Daniel Veillard | Red Hat Network http://redhat.com/products/network/
veillard(_at_)redhat(_dot_)com | libxml Gnome XML XSLT toolkit
http://xmlsoft.org/
http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list