[Standards] Proposed XMPP Extension: IO DATA
ola.spjuth at farmbio.uu.se
Fri Apr 4 12:06:12 UTC 2008
I'd like to add our strong support to the "IO DATA" XEP proposal. I
represent the Bioclipse project (www.bioclipse.net) providing a
workbench for life science that currently relies heavily on SOAP Web
services for remote execution of jobs. The biggest problem for us is
long lasting calls, as many of the calculations in life science are
computationally expensive and we have had big problems with
asynchronous calls over SOAP. This XEP looks very promising, and I
think it could bring several long-desired features that have been
requested by our users, such as stable long-running jobs and service-
In my opinion, Bioclipse will be an excellent showcase for XMPP-
based Web services, and we will continue to support this technology
in the future.
Ola Spjuth, M.Sc.
Dept. Pharmaceutical Biosciences
BMC, Husargatan 3
Uppsala University, Sweden
> Proposed XMPP Extension: IO DATA
> here I submit a proposal for a new XEP called "IO DATA".
> The XEP is already located in the XEP inbox directory:
> URL: http://www.xmpp.org/extensions/inbox/io-data.html
> However, the initial version is erroneously missing some namespaces in
> the examples, therefore we append the current fixed version as PDF to
> the mail directly to the standards mailing list.
> Abstract: This specification defines an XMPP protocol extension for
> handling the input to and output from a remote entity.
> Further explanation comes here:
> We want to do dynamic Web Services over XMPP. For certain reasons we
> explain in the XEP we think neither SOAP over XMPP nor Jabber-RPC
> is the
> way to go. We think future asynchronous Web Services can be best
> implemented with the session based Ad-Hoc Commands XEP-0050.
> Thus, and as already suggested in Ad-Hoc Commands we describe an
> alternative data container IO DATA that can transport more complex
> than Data Forms. The specification describes a way to discover the
> Schemata of the IO DATA input and output at runtime, too. Thus a
> implementation can dynamically marshal an API for the input and output
> of a certain service.
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: io-data-0.0.2.pdf
> Type: application/pdf
> Size: 47838 bytes
> Desc: not available
> Url : http://mail.jabber.org/pipermail/standards/attachments/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Standards