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

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

From: <bugzilla@wiggum.w3.org>
Date: Thu, 26 May 2005 11:04:48 +0000
To: public-qt-comments@w3.org
Cc:
Message-Id: <E1DbGAS-0008QI-Fl@wiggum.w3.org>

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





------- Additional Comments From lbzwischenbrugger@fh-stpoelten.ac.at  2005-05-26 11:04 -------


Hi Michael

Thank you very much for information!

> We did have some informal discussion on the topic. I think
> that
> what you're asking for is essentially a mechanism for invoking web
services from
> XSLT code.

If the term "web sevices" isn't reduced to SOAP that's correct.

> We don't think that's part of the job of xsl:result-document,
> we
> think it's essentially another kind of function call.

I did lots of work with SAP Business Connector.
Calling a Business Connector "function" is sending RFC-XML, IDoc-XML,
BAPI-XML, BizTalk or SOAP to BC.

The work is always the same. receiving XML, convert the XML , send XML.
(Or convert, send,  receive, convert, send, receive, ...)

I don't really understand what the difference is between
o sending XML to a http-server
o sending an XML to the file system
o calling a webservice.

For me it is the same.

If I send a 1000 lines BAPI-XML to SAP Business Connector, is it calling
a remote function or sending a document to an URL?

> Those members who
> were
> present at the discussion seemed inclined to the view that the current
mechanism
> for extension function calls should be adequate to enable vendors to
provide the
> facility if they think there is a user demand, and that this kind of
implementation experience is desirable before trying to standardize anything.

(of course I disagree completely ;-)

The sockets already exists in various forms and are used in daily
business.
Also XSLT can be used as a socket for http/xml.
An Apache Module could look like:
http://example.com/xslt-app/calendar.xslt?param1=2004&param2=dec

If xslt can connect to webservices the process can look like:
stdin(xforms delivers xml)-->XSLT-->stdout(xhtml)

The plug is missing. I'm not at all a good programmer.
I don't know why, but the only programming language I was able to learn,
is XSLT. The only possibility for me is to influence standards ;-)

In XSLT 1.0 nobody at W3C thought about this:
---snip---
<xsl:apply-templates
select="exsl:node-set(document($http_url))//elementXY" mode="content"/>
---snap---

In XQuery this is now the FIRST usecase in:
http://www.w3.org/TR/2005/WD-xquery-use-cases-20050404/

(still reduced to HTTP-GET parameters)
---------
Some new W3C Standards use HTTP-POST to send XML (cgi stdin).
XForms, SVG (postURL), SOAP, (AJAX);
SAP has this things;
B2B Communication works this way;
This are the things I have to do with in daily business.


-----
Here are some visuals:
http://lamp2.fh-stpoelten.ac.at/~lbz/xslt2.0/
(needs Adobe SVG 3.0)
---
BTW: If I try to write a file to the filesystem but don't have the
permissions - where does the error go? Is it possible to transform this
error message to html, svg, ...? (is the error message in XML Format?)



thanks

Bernhard
Received on Thursday, 26 May 2005 11:04:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:05 UTC