Re: [whatwg] Web API for Health Sensors
W3C Web Bluetooth Community Group http://www.w3.org/community/web-bluetooth/ Use cases Security model, Explainer, and Specification draft https://github.com/WebBluetoothCG/web-bluetooth On Wed, Oct 8, 2014 at 12:40 AM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Indeed, a Web Bluetooth API would be a great start! Also, we are writing standards here, so standardizing the communication of the data between the devices and UAs would be useful. Both would probably fall within the work of a device API group like http://www.w3.org/2009/dap/ , where media capture was standardized. Silvia. On Wed, Oct 8, 2014 at 2:40 PM, Sangwhan Moon sangw...@iki.fi wrote: Implementing a abstracted API on top of the browser will only work based on the assumption that the protocol that is used to communicate between the host and these devices have been standardized. Sadly, I don't think this is the case. (Correct me if I am wrong) IMHO what is needed is Bluetooth API that can be used (on top of a sane permission model) to communicate with Bluetooth devices, and the user friendly abstraction should be built on top of that. Otherwise there is the problem of browser vendors having to test and support every single known health band on earth. Pretty unlikely to happen. Sangwhan Original Message: What I'd you're a long way away from any medical help? In my mind this is part of the larger drive of the web of things (IoT applied to the web) and needs device APIs. This might not be the right group to discuss it in though. Best Regards, Silvia. On 13 Sep 2014 10:53, Erik Reppen erik.rep...@gmail.com wrote: That's a stronger argument than I would have thought of (and mind you I'm just a lurker without anything in the way of influence so don't let me shoot you down or anything). But audio/video capture is a general media/communication thing. To me it's like the difference between geolocation and having an API on top of geolocation that tells you how close you are to a hospital. You have the tools for that. Why the desire for a specific API for something that, IMO, would really benefit more from consideration by subject matter experts and devs within that field than general web technology nerds? On Fri, Sep 12, 2014 at 5:52 PM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Browsers have been dealing with private personal data for a while now, that includes video camera microphone input, geolocation and more. Health data isn't so different in that respect. There are mechanisms to deal with privacy already in the browser. But indeed: a spec would need to consider such issues. Best Regards, Silvia. On 13 Sep 2014 08:42, delfin del...@segonquart.net wrote: Hi All: Use and transmission of private/personal Health data, as other sensitive personal data, is ruled by law and regional regulations in some -- or in most of the -- developed countries. Please, take this aspect in consideration. - I would not recommend to read health data within a browser. - JSON transferred data, as I understood, might be 'seen' by a semi-experienced user with, for example, the web inspector's tools a desktop browser has. Not exactly, but nearly. - Not to mention more sophisticated public methods of to collect this JSON/JSONP data. - One might use an existent API or develop a new one for this purpose. The data of an unknown user is viewable by third-parties. An standard development should take this scenarios in consideration. 1. Laws and regulations in countries/govs referring the use and transfer of private/sensitive data. 2. Open-sourceness and distribution via a web browser. Best - -- Delfin Ramirez +34 633 589231 del...@segonquart.net twitter: delfinramirez IRC: segonquart Skype: segonquart http://segonquart.net, http://delfiramirez.info
Re: [whatwg] Web API for Health Sensors
On Oct 10, 2014, at 14:40 , Vincent Scheib sch...@google.com wrote: W3C Web Bluetooth Community Group http://www.w3.org/community/web-bluetooth/ Use cases Security model, Explainer, and Specification draft https://github.com/WebBluetoothCG/web-bluetooth On Wed, Oct 8, 2014 at 12:40 AM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Indeed, a Web Bluetooth API would be a great start! How the browser is connected to the device should be an OS question, not an API one. The ‘wire’ is not terribly relevant (wifi, bluetooth, usb, ethernet, serial, IEEE488, IBM BiSync…) Be very careful with anything health-related. It is subject to reams of regulation in many countries. The question is usefully “can I sense the local gravitational field” not “is there a bluetooth gravity sensor in the vicinity” Also, we are writing standards here, so standardizing the communication of the data between the devices and UAs would be useful. Both would probably fall within the work of a device API group like http://www.w3.org/2009/dap/ , where media capture was standardized. Silvia. On Wed, Oct 8, 2014 at 2:40 PM, Sangwhan Moon sangw...@iki.fi wrote: Implementing a abstracted API on top of the browser will only work based on the assumption that the protocol that is used to communicate between the host and these devices have been standardized. Sadly, I don't think this is the case. (Correct me if I am wrong) IMHO what is needed is Bluetooth API that can be used (on top of a sane permission model) to communicate with Bluetooth devices, and the user friendly abstraction should be built on top of that. Otherwise there is the problem of browser vendors having to test and support every single known health band on earth. Pretty unlikely to happen. Sangwhan Original Message: What I'd you're a long way away from any medical help? In my mind this is part of the larger drive of the web of things (IoT applied to the web) and needs device APIs. This might not be the right group to discuss it in though. Best Regards, Silvia. On 13 Sep 2014 10:53, Erik Reppen erik.rep...@gmail.com wrote: That's a stronger argument than I would have thought of (and mind you I'm just a lurker without anything in the way of influence so don't let me shoot you down or anything). But audio/video capture is a general media/communication thing. To me it's like the difference between geolocation and having an API on top of geolocation that tells you how close you are to a hospital. You have the tools for that. Why the desire for a specific API for something that, IMO, would really benefit more from consideration by subject matter experts and devs within that field than general web technology nerds? On Fri, Sep 12, 2014 at 5:52 PM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Browsers have been dealing with private personal data for a while now, that includes video camera microphone input, geolocation and more. Health data isn't so different in that respect. There are mechanisms to deal with privacy already in the browser. But indeed: a spec would need to consider such issues. Best Regards, Silvia. On 13 Sep 2014 08:42, delfin del...@segonquart.net wrote: Hi All: Use and transmission of private/personal Health data, as other sensitive personal data, is ruled by law and regional regulations in some -- or in most of the -- developed countries. Please, take this aspect in consideration. - I would not recommend to read health data within a browser. - JSON transferred data, as I understood, might be 'seen' by a semi-experienced user with, for example, the web inspector's tools a desktop browser has. Not exactly, but nearly. - Not to mention more sophisticated public methods of to collect this JSON/JSONP data. - One might use an existent API or develop a new one for this purpose. The data of an unknown user is viewable by third-parties. An standard development should take this scenarios in consideration. 1. Laws and regulations in countries/govs referring the use and transfer of private/sensitive data. 2. Open-sourceness and distribution via a web browser. Best - -- Delfin Ramirez +34 633 589231 del...@segonquart.net twitter: delfinramirez IRC: segonquart Skype: segonquart http://segonquart.net, http://delfiramirez.info David Singer Manager, Software Standards, Apple Inc.
Re: [whatwg] Web API for Health Sensors
On Wed, Oct 8, 2014 at 9:40 AM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Indeed, a Web Bluetooth API would be a great start! Also, we are writing standards here, so standardizing the communication of the data between the devices and UAs would be useful. Both would probably fall within the work of a device API group like http://www.w3.org/2009/dap/ , where media capture was standardized. Absolutely. This seems to tie in pretty well with the Generic Sensor API discussion planned at this year's TPAC[1]. --tobie --- [1]: https://www.w3.org/wiki/TPAC2014/SessionIdeas#Generic_Sensor_API
Re: [whatwg] Web API for Health Sensors
Implementing a abstracted API on top of the browser will only work based on the assumption that the protocol that is used to communicate between the host and these devices have been standardized. Sadly, I don't think this is the case. (Correct me if I am wrong) IMHO what is needed is Bluetooth API that can be used (on top of a sane permission model) to communicate with Bluetooth devices, and the user friendly abstraction should be built on top of that. Otherwise there is the problem of browser vendors having to test and support every single known health band on earth. Pretty unlikely to happen. Sangwhan Original Message: What I'd you're a long way away from any medical help? In my mind this is part of the larger drive of the web of things (IoT applied to the web) and needs device APIs. This might not be the right group to discuss it in though. Best Regards, Silvia. On 13 Sep 2014 10:53, Erik Reppen erik.rep...@gmail.com wrote: That's a stronger argument than I would have thought of (and mind you I'm just a lurker without anything in the way of influence so don't let me shoot you down or anything). But audio/video capture is a general media/communication thing. To me it's like the difference between geolocation and having an API on top of geolocation that tells you how close you are to a hospital. You have the tools for that. Why the desire for a specific API for something that, IMO, would really benefit more from consideration by subject matter experts and devs within that field than general web technology nerds? On Fri, Sep 12, 2014 at 5:52 PM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Browsers have been dealing with private personal data for a while now, that includes video camera microphone input, geolocation and more. Health data isn't so different in that respect. There are mechanisms to deal with privacy already in the browser. But indeed: a spec would need to consider such issues. Best Regards, Silvia. On 13 Sep 2014 08:42, delfin del...@segonquart.net wrote: Hi All: Use and transmission of private/personal Health data, as other sensitive personal data, is ruled by law and regional regulations in some -- or in most of the -- developed countries. Please, take this aspect in consideration. - I would not recommend to read health data within a browser. - JSON transferred data, as I understood, might be 'seen' by a semi-experienced user with, for example, the web inspector's tools a desktop browser has. Not exactly, but nearly. - Not to mention more sophisticated public methods of to collect this JSON/JSONP data. - One might use an existent API or develop a new one for this purpose. The data of an unknown user is viewable by third-parties. An standard development should take this scenarios in consideration. 1. Laws and regulations in countries/govs referring the use and transfer of private/sensitive data. 2. Open-sourceness and distribution via a web browser. Best - -- Delfin Ramirez +34 633 589231 del...@segonquart.net twitter: delfinramirez IRC: segonquart Skype: segonquart http://segonquart.net, http://delfiramirez.info
Re: [whatwg] Web API for Health Sensors
I'm not sure I understand the problem. Lack of a formal web API doesn't block these devices from exposing data through web services, does it? Coming up with a web service or JSON standard for the data would make sense but that's more of an industry-specific concern that would best be dealt with by people working within that sector. I don't see how this would be in scope for whatwg. On Fri, Sep 12, 2014 at 5:45 AM, Arpita Bahuguna a@samsung.com wrote: Hello all, Some of us were pondering over the need of having Web API(s) for health and similar other sensors. With the growing presence of such sensors on smart-watches and such, we believe a Web interface for retrieving data from such sensors is required (especially for Web Apps). Towards that end, we would like to know whether any work has been done towards creating a Web API for Health Sensors (and the like). Currently, the health sensor data is available only for native apps. Would appreciate the community's opinion on the same. Also, if such a standard is already under development, could someone kindly point us in the right direction? Regards, Arpita Bahuguna
Re: [whatwg] Web API for Health Sensors
Hello All: I do not think an API would be the solution for facing the need of standards in sensors. I agree, however in the need of a solution -- a kind of standarized solution -- for the forthcoming trends in data collection. XML worked pretty well for this half a decade a go or more, I guess. Personally, I do not see JSON as a solution appliable to this concern. --- Delfin Ramirez +34 633 589231 del...@segonquart.net twitter: delfinramirez IRC: segonquart Skype: segonquart http://segonquart.net http://delfiramirez.info On 2014-09-12 12:45, Arpita Bahuguna wrote: Hello all, Some of us were pondering over the need of having Web API(s) for health and similar other sensors. With the growing presence of such sensors on smart-watches and such, we believe a Web interface for retrieving data from such sensors is required (especially for Web Apps). Towards that end, we would like to know whether any work has been done towards creating a Web API for Health Sensors (and the like). Currently, the health sensor data is available only for native apps. Would appreciate the community's opinion on the same. Also, if such a standard is already under development, could someone kindly point us in the right direction? Regards, Arpita Bahuguna
Re: [whatwg] Web API for Health Sensors
It's just a more compact data format that happens to evaluate as an object literal in JS and is perfectly interchangeable with XML and similar data structures like Python dictionaries. Most modern web services offer both. You might prefer one or the other, but I can assure that it's perfectly applicable and client-side oriented devs are going to be wary of any service that doesn't offer JSON because it would be terribly silly not to for reasons I would hope are obvious given what I've just stated. But that's a conversation for another committee perhaps. On Fri, Sep 12, 2014 at 12:17 PM, delfin del...@segonquart.net wrote: Hello All: I do not think an API would be the solution for facing the need of standards in sensors. I agree, however in the need of a solution -- a kind of standarized solution -- for the forthcoming trends in data collection. XML worked pretty well for this half a decade a go or more, I guess. Personally, I do not see JSON as a solution appliable to this concern. --- Delfin Ramirez +34 633 589231 del...@segonquart.net twitter: delfinramirez IRC: segonquart Skype: segonquart http://segonquart.net http://delfiramirez.info On 2014-09-12 12:45, Arpita Bahuguna wrote: Hello all, Some of us were pondering over the need of having Web API(s) for health and similar other sensors. With the growing presence of such sensors on smart-watches and such, we believe a Web interface for retrieving data from such sensors is required (especially for Web Apps). Towards that end, we would like to know whether any work has been done towards creating a Web API for Health Sensors (and the like). Currently, the health sensor data is available only for native apps. Would appreciate the community's opinion on the same. Also, if such a standard is already under development, could someone kindly point us in the right direction? Regards, Arpita Bahuguna
Re: [whatwg] Web API for Health Sensors
Erik Reppen erik.rep...@gmail.com writes: It's just a more compact data format that happens to evaluate as an object literal in JS Not always: http://timelessrepo.com/json-isnt-a-javascript-subset -- Nils Dagsson Moskopp // erlehmann http://dieweltistgarnichtso.net
Re: [whatwg] Web API for Health Sensors
I believe a way to directly read health data into web apps with a browser api (JavaScript) is an interesting idea. You could then have a webrtc video conference with your doctor and he could read out your pulse and other health data directly from your device live and give you an opinion. Seeing as health sensors are increasingly part of devices that have a web browser built in, it would be useful to get to that data from a browser. Cheers, Silvia. On 12 Sep 2014 22:09, Erik Reppen erik.rep...@gmail.com wrote: I'm not sure I understand the problem. Lack of a formal web API doesn't block these devices from exposing data through web services, does it? Coming up with a web service or JSON standard for the data would make sense but that's more of an industry-specific concern that would best be dealt with by people working within that sector. I don't see how this would be in scope for whatwg. On Fri, Sep 12, 2014 at 5:45 AM, Arpita Bahuguna a@samsung.com wrote: Hello all, Some of us were pondering over the need of having Web API(s) for health and similar other sensors. With the growing presence of such sensors on smart-watches and such, we believe a Web interface for retrieving data from such sensors is required (especially for Web Apps). Towards that end, we would like to know whether any work has been done towards creating a Web API for Health Sensors (and the like). Currently, the health sensor data is available only for native apps. Would appreciate the community's opinion on the same. Also, if such a standard is already under development, could someone kindly point us in the right direction? Regards, Arpita Bahuguna
Re: [whatwg] Web API for Health Sensors
Hi All: Use and transmission of private/personal Health data, as other sensitive personal data, is ruled by law and regional regulations in some -- or in most of the -- developed countries. Please, take this aspect in consideration. * I would not recommend to read health data within a browser. * JSON transferred data, as I understood, might be 'seen' by a semi-experienced user with, for example, the web inspector's tools a desktop browser has. Not exactly, but nearly. * Not to mention more sophisticated public methods of to collect this JSON/JSONP data. * One might use an existent API or develop a new one for this purpose. The data of an unknown user is viewable by third-parties. An standard development should take this scenarios in consideration. * Laws and regulations in countries/govs referring the use and transfer of private/sensitive data. * Open-sourceness and distribution via a web browser. Best - -- Delfin Ramirez +34 633 589231 del...@segonquart.net twitter: delfinramirez IRC: segonquart Skype: segonquart http://segonquart.net, http://delfiramirez.info
Re: [whatwg] Web API for Health Sensors
Browsers have been dealing with private personal data for a while now, that includes video camera microphone input, geolocation and more. Health data isn't so different in that respect. There are mechanisms to deal with privacy already in the browser. But indeed: a spec would need to consider such issues. Best Regards, Silvia. On 13 Sep 2014 08:42, delfin del...@segonquart.net wrote: Hi All: Use and transmission of private/personal Health data, as other sensitive personal data, is ruled by law and regional regulations in some -- or in most of the -- developed countries. Please, take this aspect in consideration. - I would not recommend to read health data within a browser. - JSON transferred data, as I understood, might be 'seen' by a semi-experienced user with, for example, the web inspector's tools a desktop browser has. Not exactly, but nearly. - Not to mention more sophisticated public methods of to collect this JSON/JSONP data. - One might use an existent API or develop a new one for this purpose. The data of an unknown user is viewable by third-parties. An standard development should take this scenarios in consideration. 1. Laws and regulations in countries/govs referring the use and transfer of private/sensitive data. 2. Open-sourceness and distribution via a web browser. Best - -- Delfin Ramirez +34 633 589231 del...@segonquart.net twitter: delfinramirez IRC: segonquart Skype: segonquart http://segonquart.net, http://delfiramirez.info
Re: [whatwg] Web API for Health Sensors
hello all: please, might you point me some were I can find part of this solutions ( ie video/audio encrypt . That would be really helpful to me. br --- Delfin Ramirez +34 633 589231 del...@segonquart.net [4] twitter: delfinramirez IRC: segonquart Skype: segonquart [5] http://segonquart.net [2] http://delfiramirez.info [3] On 2014-09-13 00:52, Silvia Pfeiffer wrote: Browsers have been dealing with private personal data for a while now, that includes video camera microphone input, geolocation and more. Health data isn't so different in that respect. There are mechanisms to deal with privacy already in the browser. But indeed: a spec would need to consider such issues. Best Regards, Silvia. On 13 Sep 2014 08:42, delfin del...@segonquart.net wrote: Hi All: Use and transmission of private/personal Health data, as other sensitive personal data, is ruled by law and regional regulations in some -- or in most of the -- developed countries. Please, take this aspect in consideration. * I would not recommend to read health data within a browser. * JSON transferred data, as I understood, might be 'seen' by a semi-experienced user with, for example, the web inspector's tools a desktop browser has. Not exactly, but nearly. * Not to mention more sophisticated public methods of to collect this JSON/JSONP data. * One might use an existent API or develop a new one for this purpose. The data of an unknown user is viewable by third-parties. An standard development should take this scenarios in consideration. * Laws and regulations in countries/govs referring the use and transfer of private/sensitive data. * Open-sourceness and distribution via a web browser. Best - -- Delfin Ramirez +34 633 589231 [1] del...@segonquart.net twitter: delfinramirez IRC: segonquart Skype: segonquart http://segonquart.net [2], http://delfiramirez.info [3] Links: -- [1] tel:%2B34%20633%20589231 [2] http://segonquart.net [3] http://delfiramirez.info [4] mail:%20del...@segonquart.net [5] skype:segonquart
Re: [whatwg] Web API for Health Sensors
Search for webrtc. Best Regards, Silvia. On 13 Sep 2014 09:57, delfin del...@segonquart.net wrote: hello all: please, might you point me some were I can find part of this solutions ( ie video/audio encrypt . That would be really helpful to me. br --- Delfin Ramirez +34 633 589231 del...@segonquart.net twitter: delfinramirez IRC: segonquart Skype: segonquart http://segonquart.net http://delfiramirez.info On 2014-09-13 00:52, Silvia Pfeiffer wrote: Browsers have been dealing with private personal data for a while now, that includes video camera microphone input, geolocation and more. Health data isn't so different in that respect. There are mechanisms to deal with privacy already in the browser. But indeed: a spec would need to consider such issues. Best Regards, Silvia. On 13 Sep 2014 08:42, delfin del...@segonquart.net wrote: Hi All: Use and transmission of private/personal Health data, as other sensitive personal data, is ruled by law and regional regulations in some -- or in most of the -- developed countries. Please, take this aspect in consideration. - I would not recommend to read health data within a browser. - JSON transferred data, as I understood, might be 'seen' by a semi-experienced user with, for example, the web inspector's tools a desktop browser has. Not exactly, but nearly. - Not to mention more sophisticated public methods of to collect this JSON/JSONP data. - One might use an existent API or develop a new one for this purpose. The data of an unknown user is viewable by third-parties. An standard development should take this scenarios in consideration. 1. Laws and regulations in countries/govs referring the use and transfer of private/sensitive data. 2. Open-sourceness and distribution via a web browser. Best - -- Delfin Ramirez +34 633 589231 del...@segonquart.net twitter: delfinramirez IRC: segonquart Skype: segonquart http://segonquart.net, http://delfiramirez.info
Re: [whatwg] Web API for Health Sensors
That's a stronger argument than I would have thought of (and mind you I'm just a lurker without anything in the way of influence so don't let me shoot you down or anything). But audio/video capture is a general media/communication thing. To me it's like the difference between geolocation and having an API on top of geolocation that tells you how close you are to a hospital. You have the tools for that. Why the desire for a specific API for something that, IMO, would really benefit more from consideration by subject matter experts and devs within that field than general web technology nerds? On Fri, Sep 12, 2014 at 5:52 PM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Browsers have been dealing with private personal data for a while now, that includes video camera microphone input, geolocation and more. Health data isn't so different in that respect. There are mechanisms to deal with privacy already in the browser. But indeed: a spec would need to consider such issues. Best Regards, Silvia. On 13 Sep 2014 08:42, delfin del...@segonquart.net wrote: Hi All: Use and transmission of private/personal Health data, as other sensitive personal data, is ruled by law and regional regulations in some -- or in most of the -- developed countries. Please, take this aspect in consideration. - I would not recommend to read health data within a browser. - JSON transferred data, as I understood, might be 'seen' by a semi-experienced user with, for example, the web inspector's tools a desktop browser has. Not exactly, but nearly. - Not to mention more sophisticated public methods of to collect this JSON/JSONP data. - One might use an existent API or develop a new one for this purpose. The data of an unknown user is viewable by third-parties. An standard development should take this scenarios in consideration. 1. Laws and regulations in countries/govs referring the use and transfer of private/sensitive data. 2. Open-sourceness and distribution via a web browser. Best - -- Delfin Ramirez +34 633 589231 del...@segonquart.net twitter: delfinramirez IRC: segonquart Skype: segonquart http://segonquart.net, http://delfiramirez.info
Re: [whatwg] Web API for Health Sensors
What I'd you're a long way away from any medical help? In my mind this is part of the larger drive of the web of things (IoT applied to the web) and needs device APIs. This might not be the right group to discuss it in though. Best Regards, Silvia. On 13 Sep 2014 10:53, Erik Reppen erik.rep...@gmail.com wrote: That's a stronger argument than I would have thought of (and mind you I'm just a lurker without anything in the way of influence so don't let me shoot you down or anything). But audio/video capture is a general media/communication thing. To me it's like the difference between geolocation and having an API on top of geolocation that tells you how close you are to a hospital. You have the tools for that. Why the desire for a specific API for something that, IMO, would really benefit more from consideration by subject matter experts and devs within that field than general web technology nerds? On Fri, Sep 12, 2014 at 5:52 PM, Silvia Pfeiffer silviapfeiff...@gmail.com wrote: Browsers have been dealing with private personal data for a while now, that includes video camera microphone input, geolocation and more. Health data isn't so different in that respect. There are mechanisms to deal with privacy already in the browser. But indeed: a spec would need to consider such issues. Best Regards, Silvia. On 13 Sep 2014 08:42, delfin del...@segonquart.net wrote: Hi All: Use and transmission of private/personal Health data, as other sensitive personal data, is ruled by law and regional regulations in some -- or in most of the -- developed countries. Please, take this aspect in consideration. - I would not recommend to read health data within a browser. - JSON transferred data, as I understood, might be 'seen' by a semi-experienced user with, for example, the web inspector's tools a desktop browser has. Not exactly, but nearly. - Not to mention more sophisticated public methods of to collect this JSON/JSONP data. - One might use an existent API or develop a new one for this purpose. The data of an unknown user is viewable by third-parties. An standard development should take this scenarios in consideration. 1. Laws and regulations in countries/govs referring the use and transfer of private/sensitive data. 2. Open-sourceness and distribution via a web browser. Best - -- Delfin Ramirez +34 633 589231 del...@segonquart.net twitter: delfinramirez IRC: segonquart Skype: segonquart http://segonquart.net, http://delfiramirez.info
