W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2005

[Bug 1244] [XSLT 2.0] question about result-document/@href

From: <bugzilla@wiggum.w3.org>
Date: Fri, 29 Apr 2005 11:13:17 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1DRTQr-0003Jf-K7@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=1244


lbzwischenbrugger@fh-stpoelten.ac.at changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |




------- Additional Comments From lbzwischenbrugger@fh-stpoelten.ac.at  2005-04-29 11:13 -------
> but presumably you'll want to
> know what response the service sent back, which result-document
> is not going to handle.


The thing I need is the return value from "result-document".
-----

I try to make most of my software with xslt und try to reduce the
procedural part of my software. 

The procedural part of the software is written in PHP, JAVA, Python ...
and generates XML to feed the XSLT.

---

I try an approach where the input of the stylesheet is a XML message, generates 
by XFORMS (or other clients). 

The XML received from the Browser (XFROMS) may look like:

(<soap ...>
..)
<command name="callWebservice">
<webservice-url>http://xy.com/webservice/weather.xyz</webservice-url>
<parameter>
   <city>Vienna</city>
   <country>austria</country>	
</parameter>
</command>
(..
</soap>)

Without having an extended "result-document" functionality I have to process
the Browser request for example with DOM.

Old method:
parse XML, connect to webservice, give XML to XSLT for styling 

desired method:
XFORMS gives data directly to XSLT, XSLT makes the connection to the webservice
und produces a designed webpage.

It should also be possible to make more than one connection to webservices with one
Stylesheet.

I have a picture in my mind that XSLT is able to convert AND ROUTE XML messages.
This is very easy to implement in XSLT-Processors.

----

With XSLT 1.0 I did some tests using the "document" function to make the same thing:
...

<xsl:variable name="weather">
http://xy.com/getservice?location=<xsl:value-of
select="//city"/>&country=<xsl:value-of select="//coutnry"/>
</xsl:variable>

<xsl:apply-templates select="exsl:node-set(document($weather))"
mode="svgWeatherMap"/>
...

The problem with this method is, that it is not possible to use webservices.
To do everything with GET variables is ugly.

-------------

The procedural part of the software is reduced to:

---snip---
#/bin/sh
xsltproc weather.xslt /dev/stdin
---snap---

########################################################
# All I need is a return value from "result-document". #
########################################################

In combination with webservices or jabber protocol (http pull JEP-0124), XSLT could 
be used as a complete
programming language for websites (or maybe XAML applications).

The security of XSLT is not influenced. With the "document" function it is already 
possible (processor dependent) to contact maschines in the Internet.

----
Sorry for the late input.
Maybe in the new functions of XSLT 2.0 there is already a way to that, but I
couldn't
find one jet.

Thanx for reading.

Bernhard Zwischenbrugger
FH St. Pölten 
http://www.fh-stpoelten.ac.at
Received on Friday, 29 April 2005 11:13:31 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:14:37 GMT