Twitter + XMPP = intelligent Twitter - ProcessOne. Our Twitter gateway, running at Tweet.IM, has been designed not only for desktop/laptop users, but also with mobile users in mind: we add real push and availability to Twitter. We started from a simple observation: on one hand the successful Twitter is very basic, being based on polling and stateless technologies, and on the other hand XMPP is featureful, being based on push and presence technologies. Push against polling, and stateless against presence… we just had to do something: Tweet.IM. In this post, I will describe the configuration I use for my daily Twitter needs, and show its efficiency, by adding native XMPP features to Twitter.
Add push and availability to Twitter Now you need to play with your presence in order to filter the type of event you want to receive: Mobility context More XMPP features to Twitter Besides these push and availability features, you also benefit even more features from XMPP: Even further with OneTeam Conclusion. SPARQL XMPP Communications » crschmidt.net. Introduction XMPP, the protocol behind the more commonly known Jabber chat services, is an XML based communications format with significant support for extensibility.
This messaging framework makes for an ideal method of transportation of SPARQL queries to various endpoints, querying the RDF data stored at those endpoints using SPARQL and receving data in the standardized SPARQL XML query results format. Why SPARQL? SPARQL is the W3C's standardized language for querying RDF datastores.
It is implemented in a number of libraries in several different programming languages, and is on the track to become a W3C Recommendation in the near future. SPARQL features a similarly specified XML results format - the only such format in existance. Why XMPP? The extensible and open Jabber protocol is the only existing instant messaging protocol which is defined and specified via the IETF standards board. The Format meta: This element is reserved for information about the query. Existing Implementations. JQbus - Jabber chat query services. Update: this work continues in 2009 as Buttons...
For discussion of this and SPARQL/XMPP bindings, please join the foaf-protocols list... JQbus uses off-the-shelf Jabber chat services as a generic information bus, passing SPARQL queries and results via user accounts, encoded as XMPP IQ messages. JQbus provides a Jabber (XMPP) transport for SPARQL queries and responses, using Java. Each question comes "from" some Jabber account (possibly shared with a human user) and is routed by Jabber magic to code attached to another such account, whose response is transmitted back, addressed only to a jabber: ID. What does it do? Given a pair of Jabber accounts capable of exchanging messages (and in particular, custom IQ queries), we provide basic glue code that handles the passing of SPARQL queries and their corresponding XML-encoded responses. The Jabber layers, in turn, take care of ugly details such as authentication, buddylists, getting messages through NAT/firewalls.
Documentation Protocol Overview. Spark IM Client. Dear Community, after some more weeks of testing, debugging and developing, we would like to ask for your support and publish the first beta of Spark 2.7.0.
Ultimately, we would like to move Spark to Java 7, but that is currently not implemented via the installers. This will change in January after an update to the lastest version von Install4j provided by ej-Technologies. You can find the nightly build for Windows here: l4j About Java 7: Spark 2.7.0 will run with Java 7. Important Note: Oracle has introduced a bug in Java 1.6.0 u 25-27 that prevents Spark from closing automatically during the log-off on the Windows plattform. About file transfer: Spark 2.7.0 beta 1 is fixing an big bug with file transfer.
Spark 2.7.0 will also move to a standard implementation for IBB file transfer. About plugins: There were large scale changes in the way Spark is dealing internally with plugins/extensions. About GUI: The Spark developers are only supporting JTattoo Luna. SPARK-1379 Support for XEP-0147.