QuadraSpace Team is happy to announce the collaboration with Sensaris (http://www.sensaris.com). First result of this collaboration is the Senslink application for Android, which connects to Senspod sensors using Bluetooth. Next step will be integrating the Senspod in the QuadraSpace architecture.
We are very happy to publish the XML Schemas of the QuadraSpace protocol. The Schemas, kindly written by Antonio Pintus, are being used to generate stubs on the QuadraServer implementation and they can be used by anyone that wants to implent his own QuadraSpace-compliant server or client.
XML Schemas are available on the Specification page.
Just a photo, stay tuned for details…
QuadraSpace first sensor prototype
Libelium, a Spanish company specialized in sensors and wireless modules, has just announced the availability of Waspmote, presented as “The sensor device for developers”.
The entire development environment is opensource software and the Waspmote development kit includes demo boards for lot of sensors, including GAS, position and others, with lots of communication options (GPRS, 802.15.4, ZigBee and long-range radio).
We intend to adopt Waspmote as reference platform for upcoming first QuadraSpace system prototype, which we expect to present in early 2010.
Great job, Libelium! Keep running!
Some weeks ago Vlad Trifa and Dominique Guinard, the team of Web Of Things, has published the
Web of Things Manifesto, that you can read below:
This document is a bright and clear analysis of what the Internet of Things is moving towards the Web 2.0 paradigms. Vlad and Dominique are doing a very good job to define concepts and approaches of the Web of Things, focusing more on what it implies to the Internet world instead of working on a specific protocol or technology.
We really appreciate their effort and, as QuadraSpace project team, we “virtually sign” the Web of Things Manifesto. Quoting Vlad and Dominque doc:
[...] little attention has been paid to the development of simple and … functional open systems that focus on sharing and reuse of physical things. [...] The creation of a global and flexible eco-system of connected real-world devices calls for a common ground that allows physical objects to interact and exchange information seamlessly [...] As seen with the success of several Web 2.0 applications, massive projects have been developed cheaply by fostering collaboration and sharing of information. Open access to data through services onf the Web has enabled information to be reused across independent system, therefore has lowered the access barrier that allows people to develop their own applications. For all these reasons, we foster the development of novel composition platforms for networked objects by leveraging as much as possible the existing Web and by extending the current Web to include the real-world. Creation of a new generation of Web-enabled devices will result in the Web of Things, and in our vision the future Web will be a collection of devices that can be (re-)combined at runtime to solve any task. Our research is focused on the development of composite applications on top of the open and simple standards that made the Web so
successful (REST, XML, HTTP, or Atom) to interconnect physical devices.
We hope QuadraSpace will effectively contribute to realize that.
QuadraSpace aims to be a “green computing project”: we will try to use low consumption hardware on both servers and motes and to limit electromagnetic pollution when using wireless connections. The first step to reach this goal is to (try to) use low-power computers for the backend and to prefer motes powered by renewable energy whenever possible.
First action on backend-side is the adoption of a Acer Aspire Revo R3600, an “eco-computer” based on Intel’s Atom 230 processor and NVIDIA ION platform, as first QuadraServer node.
This small computer runs with a 65W power supply for its internal components (everything but an optical drive); in current QuadraServer setup there are also two external hard drives used respectively for the RAID-ed data storage and backup for internal system disk. Total power consuption will be about 100W. Having QuadraServer always-on 365/24/7 requires 0.1 * 24 * 365 = 876KWh, that produce about 470 kg of CO2 (just for reference, a typical SUV equipped with a 3 litres engine, produces the same amount of CO2 to run less than 2000km!).
Next week we will setup the server and we hope to have the QuadraServer instance up&running in a couple of weeks.
Stay tuned! 
First QuadraSpace mobile mote has appeared on a HTC Magic Androd phone:
Stay tuned 
Fourth draft of the QuadraSpace protocol has just been published!
First of all, we’d like to thank all friends that have sent their comments about previous drafts of QuadraSpace: your help has been valuable for improving the protocol, include features you expected and to find pitfalls in the specifications. We have carefully taken into account some considerations about REST approach (thank you Emanuele), and we finally changed QuadraSpace to support all main HTTP methods (GET/POST/PUT/DELETE) but to guarantee access to the backend also for those devices (Java ME CLDC/MIDP in primis) that lack full HTTP client in their standard library. We will give ore details about that in upcoming articles. Finally, each event has a type, that can be “sample” or “heartbeat”. “Sample” is the event as it was originally described (a notification of some data read by a sensor). “heartbeat” is a “still-alive” message sent by the mote to notify that it is fully operative (thank you Dadaista for reminder!).
The first draft was 47 slides long: the new 4th draft nearly doubles that size (84 slides)! QuadraGrowing!
Find it at:
http://quadraspace.googlegroups.com/web/qs_protocol_DRAFT4.pdf
or browse it on this web site:
Third draft of the QuadraSpace protocol has just been published!
Find it at:
http://quadraspace.googlegroups.com/web/qs_protocol_DRAFT3.pdf
