- From: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
- Date: Sat, 13 Sep 2014 08:52:50 +1000
- To: delfin <delfin@segonquart.net>
- Cc: sanjoy.pal@samsung.com, Arpita Bahuguna <arpitabahuguna@gmail.com>, sanjoy.net@gmail.com, WHAT Working Group Mailing List <whatwg@whatwg.org>, Arpita Bahuguna <a.bah@samsung.com>, Erik Reppen <erik.reppen@gmail.com>
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" <delfin@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 > > delfin@segonquart.net > > twitter: delfinramirez > > IRC: segonquart > > Skype: segonquart > > http://segonquart.net, http://delfiramirez.info >
Received on Friday, 12 September 2014 22:53:18 UTC