W3C home > Mailing lists > Public > whatwg@whatwg.org > September 2014

Re: [whatwg] Web API for Health Sensors

From: Erik Reppen <erik.reppen@gmail.com>
Date: Fri, 12 Sep 2014 19:53:51 -0500
Message-ID: <CALtP259QSJjh3yP0=athThbkhFLQVrKdwoNGPgDdAdh5QbKFzg@mail.gmail.com>
To: Silvia Pfeiffer <silviapfeiffer1@gmail.com>
Cc: sanjoy.pal@samsung.com, WHAT Working Group Mailing List <whatwg@whatwg.org>, Arpita Bahuguna <arpitabahuguna@gmail.com>, sanjoy.net@gmail.com, Arpita Bahuguna <a.bah@samsung.com>
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 <silviapfeiffer1@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 Saturday, 13 September 2014 00:54:16 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:23 UTC