lundi 31 mai 2010

Android-Powered Sensors Monitors Vital Signs

In science fiction films from Aliens to Avatar, commanders back at the base station always know when soldiers of the future get taken out by hostiles--because their vital signs are being monitored in real time. Doing that with present-day technology is a challenge, not least because collecting and transmitting all of the data that can be gathered by even a handful of motion and vital-signs sensors would be a huge drain on battery power and wireless bandwidth.
By equipping the clothing and bodies of users with a mesh of multiple sensors - known as "smart dust" - that report to an Android-powered phone, researchers are pioneering an open-source route to realizing the dream of always-on medical monitoring. Their work has already allowed them to measure how much test subjects exercise, how well their hearts are doing and how much air pollution they're being exposed to.
The resulting data have a number of applications:
  • Incorporation of historical and real-time data on vital signs into permanent medical records
  • Automatically inform a patient when to adjust their heart medication
  • Turn exercise and daily activity levels into a Foursquare-style competition
  • Allow users to avoid locations and times of day when air pollution is worst
The technology (pdf) is described in a paper to be delivered in late June at the 2010 International conference on Pervasive technologies for assistive environment in Samos, Greece. It outlines a hierarchy of processing steps that make 24/7 monitoring of vital signs (such as breathing and heart rate) realistic given the battery life issues and bandwidth constraints of mobile phones
Three-layer architecture of the DexterNet system with example hardware, communication and software implementation.
This hierarchy, known as DexterNet, includes sequential processing at each level of the hardware involved: the sensors, known as the body sensor layer, the smartphone orpersonal network layer, and finally in the "cloud" or global network layer that backs up and does final processing of all of the user's data. The purpose of in-device processing in each layer is the reduction of the amount of information transmitted wirelessly between each device.
The lowest level of this hierarchy, individual sensors on the user's limbs and torso, can gather data on a number of parameters: motion in 3 axes (realized with a three-axis accelerometer and a two-axis gyroscope), heart ECG, levels of airborne particulate matter, and, for breathing movements, "electrical impedance pneumography."
To reduce the frequency with which these sensors must communicate with the user's smartphone (and the volume of information they have to transmit) these sensors are capable of basic signal-processing algorithms across a programmer-definable time period, including minimum, maximum, average and mean values for any particular parameter.
Two types of sensors were used, one, known as the TelosB, is about the size of a USB thumb drive, and sports a Texas Instruments processor often found in embedded applications and 10k of integrated RAM. The other, Intel's SHIMMER sensor, runs theTinyOS operating system designed specifically for remote sensors, weighs only 15 grams and is not much bigger than a quarter.
Led by Edmund Seto of the School of Public Health at UC Berkeley, the researchers involved were able to further integrate data gathered from the wireless sensors with data gathered by the phones themselves. By combining location, time of day and air-quality data, for example, the researchers were able to create maps of user's days that highlight the places and times when they were exposed to greatest levels of air pollution.
Because phones and sensors can communicate with each other wirelessly via Bluetooth, the number of sensors that can be embedded both on a user and in his or her environment is practically limitless. In one application, the researchers put a sensor into the digital bathroom scale of users and their blood pressure monitors to quantify daily changes related to too much fluid retention in patients. The resulting data allowed their algorithms, processed in by the server to which the smartphone sends its data, to suggest possible modification of dosage of blood pressure medication.
Seto et al. cited the Android platform as a unique enabler of their work, not only because Android phones, like all smart phones, are fairly capable wearable computers in their own right. Because Android is open-source, the researchers were able to develop on top of it using the SPINE platform for remote sensing, and to add to it their own API, known as WAVE (not to be confused with Google's Wave). In combination, these research platforms allow them free reign to experiment.
So far the only drawback to using the Android platform in this work, note the researchers, is that it can't locate users indoors. The researchers spend a portion of their paper trying to re-invent the wheel by speculating about ways to accomplish this via the use of Wifi nodes and even visual recognition of interior spaces using the phone's camera, without ever realizing, apparently, that Skyhook Wireless already has an API and an international database of wifi networks that can accomplish this.

mardi 18 mai 2010

The XML Security Working Group has published three Last Call Working Drafts

  The XML Security Working Group has published three Last Call
  Working Drafts: "XML Encryption Syntax and Processing Version 1.1," "XML Signature Syntax and Processing Version 1.1," and "XML Security Generic Hybrid Ciphers." The group also published a Working Draft of "XML Security Algorithm Cross-Reference." XML Encryption specifies a process for encrypting data and representing the result in XML. XML Signatures provide integrity, message authentication, and/or signer authentication services for data of any type, whether located within the XML that includes the signature or elsewhere. The third document augments XML Encryption by defining algorithms, XML types and elements necessary to enable use of generic hybrid ciphers in XML Security applications. The final document summarizes XML Security algorithm URI identifiers and the specifications associated with them. Last Call comments are welcome through 10 June. Learn more about the Security Activity.

  http://www.w3.org/2008/xmlsec/
  http://www.w3.org/TR/2010/WD-xmlenc-core1-20100513/
  http://www.w3.org/TR/2010/WD-xmldsig-core1-20100513/
  http://www.w3.org/TR/2010/WD-xmlsec-generic-hybrid-20100513/
  http://www.w3.org/TR/2010/WD-xmlsec-algorithms-20100513/
  http://www.w3.org/Security/



Source :  http://www.w3.org/News/2010#entry-8801

XProc Standard Defines Way to Organize and Share XML Workflows

  Today W3C announced a powerful tool for managing XML-rich processes such as business processes used in enterprise environments. The W3C Recommendation " "XProc: An XML Pipeline Language,"" provides a standard framework for composing XML processes. XProc streamlines the automation, sequencing and management of complex computations involving XML by leveraging existing technologies widely adopted in the enterprise setting.
  "XML is tremendously versatile," said Norman Walsh, MarkLogic, and one of the co-editors of the specification. "Just off the top of my head, I can name standard ways to store, validate, query, transform, include, label, and link XML. What we haven't had is any standard way to describe how to combine them to accomplish any particular task. That's what XProc provides."
  Read more in the press release and learn more about XML.

  http://www.w3.org/TR/2010/REC-xproc-20100511/
  http://www.w3.org/2010/05/xproc-pr
  http://www.w3.org/standards/xml/

Source :   http://www.w3.org/News/2010#entry-8793

jeudi 13 mai 2010

European Commission Releases New Version of Open e-PRIOR To Push eProcurement Across EU

The Directorate-General for Informatics (DIGIT) has recently announced that a new version of Open e-PRIOR, the open-source version of the e-PRIOR (electronic PRocurement, Invoicing and Ordering) platform has been published on the Open Source Observatory and Repository for European public administrations (OSOR.eu). 



Based on the success and the positive response received on the technical sneak preview published in November 2009, the Open e-PRIOR team has been working on adding the functionality foreseen under the IDABC (Interoperable Delivery of European eGovernment Services to public Administrations, Business and Citizens) programme, as well as taking on feedback received by different parties. 
The new version of Open e-PRIOR delivers an embedded PEPPOL (Pan-European Public Procurement Online) Access Point, which provides a great opportunity for Customers wishing to participate in the PEPPOL pilot that will commence in May 2010.  Through the use of this Access Point, Customers will be able to connect to their Suppliers by exchanging Invoices over the PEPPOL network.  For this purpose a PEPPOL test client is also being provided in the package together with a detailed Software Architecture Document. 
Open e-PRIOR is the first eProcurement implementation which enables the exchange of electronic business documents using the data models of CEN/ISSS WS/BII.
Those willing to know more about Open e-PRIOR can:
download the new version of Open e-PRIOR from OSOR.eu at http://forge.osor.eu/frs/?group_id=188 
join the Open e-PRIOR community in order to learn more about the project, contribute with their feedback and participate in the making of this platform throughhttp://www.osor.eu/projects/openeprior 
read documentation about Open e-PRIOR, including a guide on how to get Open e-PRIOR running and to understand the Software Architecture through http://forge.osor.eu/docman/?group_id=188 
Interested parties can contact the dedicated team who is ready to share knowledge, experiences and to provide support, by e-mail DIGIT-EPRIOR-SUPPORT@ec.europa.eu or through OSOR athttps://forge.osor.eu/forum/forum.php?forum_id=508.

XML Linking Language (XLink) 1.1 is a W3C Recommendation

  The XML Core Working Group has published a W3C Recommendation of "XML Linking Language (XLink) Version 1.1." This
  specification defines the XML Linking Language (XLink) Version 1.1, which allows elements to be inserted into XML documents in order to create and describe links between resources. It uses XML syntax to create structures that can describe links similar to the simple unidirectional hyperlinks of today's HTML, as well as more sophisticated links. "Changes from XLink 1.0" include: xlink:type is no longer required for simple links, IRIs are used instead of URIs, and the specification includes
  non-normative sample XML Schema and RELAX NG grammars. 


Learn more about the Extensible Markup Language (XML) Activity.

  http://www.w3.org/XML/Core
  http://www.w3.org/TR/2010/REC-xlink11-20100506/
  http://www.w3.org/TR/2010/REC-xlink11-20100506/#changes
  http://www.w3.org/XML/


Source :  http://www.w3.org/News/2010#entry-8791