<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.network.jabber.ws-xmpp">
    <title>gmane.network.jabber.ws-xmpp</title>
    <link>http://blog.gmane.org/gmane.network.jabber.ws-xmpp</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/223"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/221"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/219"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/218"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/217"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/206"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/200"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/197"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/195"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/194"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/189"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/185"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/183"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/223">
    <title>evolution?</title>
    <link>http://comments.gmane.org/gmane.network.jabber.ws-xmpp/223</link>
    <description>&lt;pre&gt;Hi all,

I have already briefly spoken with Johannes about this some time ago,
but I like to update XEP-0244 to for two reasons:

1. tighten the XML Schema support by denoting the expected root element
2. support Resource Description Framework payload

About 1

The current proposal specifies which schema payload should comply to,
e.g. in Example 5. However, with large schemas it becomes increasingly
easy to pick the wrong part of the schema, and still get useless
input. That is, in that particular example, we service can get a
crystal, molecule, list of molecules, whatever... I think that example
should be updated to indicating an exact root element

Task: update Example 5

About 2

This is trickier. There might very well be an XML Schemata for
RDF/XML, but that is not enough. We also need to indicate the rdf:type
or rdfs:subClassOf of the in and out. We need both of them, to service
the two common options to represent a concept in RDF, as a class
(rdfs:subClassOf) or as an instance (rdf:type).

We can requi&lt;/pre&gt;</description>
    <dc:creator>Egon Willighagen</dc:creator>
    <dc:date>2011-11-19T11:14:00</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/221">
    <title>Maxime_Malenfant-uecKe64/AqPR7s880joybQ&lt; at &gt;public.gmane.org</title>
    <link>http://comments.gmane.org/gmane.network.jabber.ws-xmpp/221</link>
    <description>&lt;pre&gt;Want this adress

Envoyé de mon iPod


&lt;/pre&gt;</description>
    <dc:creator>Maxime Malenfant</dc:creator>
    <dc:date>2010-10-11T02:33:35</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/219">
    <title>Kyungae Lim/Iris is out of office</title>
    <link>http://comments.gmane.org/gmane.network.jabber.ws-xmpp/219</link>
    <description>&lt;pre&gt;
I will be out of the office starting  08/17/2010 and will not return until
08/25/2010.

I will check email upon returning as I do not have access while I'm out of
office.   Please contact my manager, Cheryl Spera, if you need assistance
in the meantime.


&lt;/pre&gt;</description>
    <dc:creator>Kyungae Lim</dc:creator>
    <dc:date>2010-08-20T08:02:25</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/218">
    <title>Funny fact.</title>
    <link>http://comments.gmane.org/gmane.network.jabber.ws-xmpp/218</link>
    <description>&lt;pre&gt;http://googletalk.blogspot.com/#LinkList1

Look at the "XMPP" link.
http://web.archive.org/web/20060427155319/www.jabber.org/

:)


&lt;/pre&gt;</description>
    <dc:creator>Sonny Piers</dc:creator>
    <dc:date>2010-08-20T03:27:40</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/217">
    <title>(Hijacked from jdev list) buddycloud update,and what next?</title>
    <link>http://comments.gmane.org/gmane.network.jabber.ws-xmpp/217</link>
    <description>&lt;pre&gt;Hi WS Devs!


Someone in this list might find this interesting:


http://mail.jabber.org/pipermail/jdev/2010-July/088302.html

It's about microblogging service buddycloud build using XMPP.


Cheers,
--
tuomas
xmpp:tuomas-tTojw+NF3p7WzaYB42WVTgmWJwt+BgR4&amp;lt; at &amp;gt;public.gmane.org

&lt;/pre&gt;</description>
    <dc:creator>Tuomas Koski</dc:creator>
    <dc:date>2010-07-07T16:59:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/206">
    <title>Microblogging over XMPP XEP</title>
    <link>http://comments.gmane.org/gmane.network.jabber.ws-xmpp/206</link>
    <description>&lt;pre&gt;All Email originating from UWC is covered by disclaimer http://www.uwc.ac.za/portal
&lt;/pre&gt;</description>
    <dc:creator>Paul Scott</dc:creator>
    <dc:date>2010-01-16T10:20:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/200">
    <title>Couple of frameworks/toolkits: Gaelyk and iBeans</title>
    <link>http://comments.gmane.org/gmane.network.jabber.ws-xmpp/200</link>
    <description>&lt;pre&gt;Hi all,

I participated Devoxx 09 (http://www.devoxx.com) conference last week.
I got introduced to two new web frameworks/toolkits that uses also
XMPP:

* Gaelyk - a lightweight Groovy toolkit for Google App Engine Java.
[http://gaelyk.appspot.com/] Presentation slides here:
http://www.slideshare.net/glaforge/google-app-engine-java-groovy-baby

* iBeans presented by mulesoft. Presentation slides here:
http://blogs.mulesoft.org/ibeans-from-devoxx/


Nothing very special and new, but I think they might be interesting
for some of this mailing list's readers.

Cheers,
--
Tuomas

&lt;/pre&gt;</description>
    <dc:creator>Tuomas Koski</dc:creator>
    <dc:date>2009-11-23T21:50:57</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/197">
    <title>Yet another xmpp manuscript</title>
    <link>http://comments.gmane.org/gmane.network.jabber.ws-xmpp/197</link>
    <description>&lt;pre&gt;Yet another manuscript that discusses grid computing over XMPP.

http://www.springerlink.com/content/ng08772325k627j6/

Orbweb - a network substrate for peer-to-peer grid computing based on
open standards. Journal of Grid Computing, 2009 Journal of Grid Computing
S. Schulz, W. Blochinger, and M. Poths.
DOI 10.1007/s10723-009-9121-8




&lt;/pre&gt;</description>
    <dc:creator>Johannes Wagener</dc:creator>
    <dc:date>2009-09-24T20:45:52</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/195">
    <title>XMPP applied in bioinformatics</title>
    <link>http://comments.gmane.org/gmane.network.jabber.ws-xmpp/195</link>
    <description>&lt;pre&gt;Hi,

our bioinformatics project, which applies XMPP and XEP-0244 IO Data, was 
published:

XMPP for cloud computing in bioinformatics supporting discovery and 
invocation of asynchronous Web services
Johannes Wagener, Ola Spjuth, Egon L Willighagen, Jarl ES Wikberg
BMC Bioinformatics 2009, 10:279 (4 September 2009)

here: http://www.biomedcentral.com/1471-2105/10/279/abstract


More links:

http://xws4j.sourceforge.net/ a java library to create and invoke 
services that are based on XEP-0244 IO Data
http://pele.farmbio.uu.se/xmpp-services/index.php/Main_Page a wiki 
providing more software, a test setup, and sample scripts for the 
bioinformatics workbench Bioclipse for demonstrating how this approach 
is utilized in bioinformatics

Have a great week,


Johannes

&lt;/pre&gt;</description>
    <dc:creator>Johannes Wagener</dc:creator>
    <dc:date>2009-09-08T08:35:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/194">
    <title>Breaking news webservice - example of publishing data"real time" and still using cache</title>
    <link>http://comments.gmane.org/gmane.network.jabber.ws-xmpp/194</link>
    <description>&lt;pre&gt;Cheers all,

I have made a simple Breaking News web page with the help of
Superfeedr.com. I have made this for my personal use and as a test,
but maybe someone else finds it interesting too.

It can be read more about it here:
http://www.lobstermonster.org/post/breaking-news .

With this kind of basic system anything could be displayed on web
"realtime" (when really needed for example with Formula 1 race status)
with very minimum hardware. This is due the initial page view is
loaded from the cache managed by the XMPP components and later updated
with PubSub event's received from a xmpp server.


Great week for all,
--
tuomas

(PS. yes, there are some character encoding bugs I have not fixed.)

&lt;/pre&gt;</description>
    <dc:creator>Tuomas Koski</dc:creator>
    <dc:date>2009-08-31T20:31:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/189">
    <title>queuing &lt;iq&gt; stanzas</title>
    <link>http://comments.gmane.org/gmane.network.jabber.ws-xmpp/189</link>
    <description>&lt;pre&gt;hi all,

i'm implementing an asynchronous RPC service in XMPP. i see from XEP-0009
[jabber-RPC] that &amp;lt;iq/&amp;gt; stanzas are used, which looks pretty correct to me.

however, is it right that &amp;lt;iq/&amp;gt; stanzas do not get queued in most XMPP
servers? i have used ejabberd 2.0.1 and, unless i've missed something [which
may very well be since the outside temperature is melting me down], i have
not been able to queue &amp;lt;iq/&amp;gt; stanzas, while &amp;lt;message/&amp;gt; ones natively are.

i'm using XMPP especially for the fact that i can build asynchronous calls.
if the recipient of an RPC request is offline ,i want it to receive the
stanza asa it gets back online. and when it responds, if the original
requester is offline, i want the latter to receive the response asa it gets
too back online. however, in my experience &amp;lt;iq/&amp;gt; gets out as request, and if
the intended recipient is offline, well, the stanza is simply lost since it
is not queued, and of course no error messages are received by the original
requester.

i'm therefore currently using &lt;/pre&gt;</description>
    <dc:creator>Roberto Ostinelli</dc:creator>
    <dc:date>2009-08-19T09:32:28</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/185">
    <title>AUTO: Itai Zapler is out of the office (returning23/08/2009)</title>
    <link>http://comments.gmane.org/gmane.network.jabber.ws-xmpp/185</link>
    <description>&lt;pre&gt;
I am out of the office until 23/08/2009.




Note: This is an automated response to your message  "Re: [WS-XMPP]
[Standards] LAST CALL: XEP-0244 (IO Data)" sent on 15/8/09 10:14:34.

This is the only notification you will receive while this person is away.


&lt;/pre&gt;</description>
    <dc:creator>Itai Zapler</dc:creator>
    <dc:date>2009-08-15T13:07:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.jabber.ws-xmpp/183">
    <title>Start of discussion: architectures used?</title>
    <link>http://comments.gmane.org/gmane.network.jabber.ws-xmpp/183</link>
    <description>&lt;pre&gt;Hi all,

Let's start an overall discussion: What kind of architectures you have
used to create web services over XMPP?

I have now done couple of services using the following architecture. I
have found quite straight forward and fast to implement:

Users (web browsers) &amp;lt;-&amp;gt; Web site (Apache + PHP) &amp;lt;-&amp;gt; Memcache &amp;lt;-&amp;gt; XMPP
( bots, components )

So in other words, when the page is executed for browsers, the needed
dynamic data is read from memcache. The data in memcache is created by
bots and components that are doing their magic (communicating,
launching services, being subscribed to pubsub services, etc) over
XMPP.

Following architecture gives support for:
 * pretty good and easy scalability
 * real time (if needed) information on websites
 * fast page execution times


This is just a simple architecture example to start discussion. Your
turn! What have you done? How could things be improved in my solution?

Cheers,
--
tuomas
www.lobstermonster.org
xmpp:tuomas-tTojw+NF3p7WzaYB42WVTgmWJwt+BgR4&amp;lt; at &amp;gt;public.gmane.org

&lt;/pre&gt;</description>
    <dc:creator>Tuomas Koski</dc:creator>
    <dc:date>2009-08-10T21:37:50</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.network.jabber.ws-xmpp">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.network.jabber.ws-xmpp</link>
  </textinput>
</rdf:RDF>
