W3C home > Mailing lists > Public > public-device-apis@w3.org > June 2014

[admin] Corrected Draft Minutes 12 June 2014 teleconference

From: Frederick Hirsch <w3c@fjhirsch.com>
Date: Fri, 13 Jun 2014 18:06:45 -0400
Cc: Frederick Hirsch <frederick.hirsch@nokia.com>
Message-Id: <055139C5-55DC-4CB4-95EA-F4BB6BA0F744@fjhirsch.com>
To: W3C Device APIs WG <public-device-apis@w3.org>
Attached are correct draft minutes from 12 June - updated Light topic to include URL for the Light CfC.

regards, Frederick

Frederick Hirsch, Nokia
Chair DAP

On Jun 12, 2014, at 11:55 AM, <frederick.hirsch@nokia.com> <frederick.hirsch@nokia.com> wrote:

> Attached are draft minutes from today’s DAP teleconference. I scribed.
> Please send any comments or corrections to the public list.
> Our next call is scheduled in 2 weeks on 26 June, see http://www.w3.org/2009/dap/minutes.html#upcoming-teleconferences
> Thanks
> regards, Frederick
> Frederick Hirsch, Nokia
> @fjhirsch
> <minutes-2014-06-12.html><minutes-2014-06-12.txt>


# Device APIs Working Group Teleconference

## 12 Jun 2014


See also: [IRC log][4]

## Attendees


    Anssi_Kostiainen, Cathy_Chan, Clarke_Stevens, Frederick_Hirsch,
Giri_Mandyam, Lisa_DeLuca, Marcos_Caceres, Mats_Wichmann, Rich_Tibbett,







## Contents

  * [Topics][5]

    1. [Welcome, agenda review, scribe selection, announcements][6]

    2. [Minutes approval][7]

    3. [Vibration][8]

    4. [Light][9]

    5. [HTML Media Capture][10]

    6. [Battery][11]

    7. [Proximity][12]

    8. [Network Service Discovery][13]

    9. [Named Web Sockets][14]

    10. [Standby API and Charter][15]

    11. [Standby API][16]

    12. [Testing & Implementations][17]

    13. [Cordova update][18]

    14. [Action Items][19]

    15. [Pending Actions][20]

    16. [Other business][21]

    17. [Adjourn][22]

  * [Summary of Action Items][23]

* * *

<trackbot> Date: 12 June 2014

<scribe> ScribeNick: fjh

### Welcome, agenda review, scribe selection, announcements

Welcome to new group participants:

Ilya (Yandex) [http://lists.w3.org/Archives/Public/public-device-

Yuan (Microsoft) [http://lists.w3.org/Archives/Public/public-device-

Zhiqiang (intel), Mikio (Mitsubishi Electric)

Publishing moratoria for end of 2014 : [http://lists.w3.org/Archives/Public

### Minutes approval

Approve minutes from 15 May 2014


**RESOLUTION: Minutes from 15 May 2014 are approved**

### Vibration

Vibration API CfC: [http://lists.w3.org/Archives/Public/public-device-

Plan to publish 19 June with LC End 25 July (5 weeks)

fjh: anssik we will need to prepare snapshots for publishing, including adding
diffs, pubrules check, link check etc

... need to give time for publication request

anssik: can do this by ET monday morning

fjh: great, thanks

... all, if you haven't looked at the various CfCs please do so, ends tomorrow

### Light

Light API CfC: [http://lists.w3.org/Archives/Public/public-device-

fjh: CfC on list ends tomorrow

... no comments, so good to go

### HTML Media Capture

HTML Media Capture CfC; [http://lists.w3.org/Archives/Public/public-device-

fjh: minor typo found by Cathy, [http://lists.w3.org/Archives/Public/public-

... other than that, no issues, so should be included

### Battery

Battery CfC; [http://lists.w3.org/Archives/Public/public-device-

fjh: some editional proposed edits based on Tim’s comments:

... I also had comment on default

anssik: if unknown or unable to report values use default of full, eases

... before sync provided, always had to provide value, but now using promises,
so if don't know how, can not resolve promise

... also had fingerprinting concern

fjh: we need a paragraph exlaining this model, reader would not know

... I don't believe this one is ready for last call, need to let it settle, do
you agree

anssik: yes, I think we need feedback from Tim

marcos: the spec is probably good enough as it is

... haven't seen impact on performance, depends on implementation or hardware

<marcosc> for example:

gmandyam: misleading, since there could be better

<gmandyam> Will clarify: browser can implement a power monitor using non-
kernel approaches, e.g. Intel's PMIC proposal in TPAC 2013

<gmandyam> See [https://docs.google.com/presentation/d/1lpOlTtq93XtPCtZNsX00zm

fjh: anssik may have more to add on this, do not want to hold up LC

... josh concerns may be valid in some cases, may be implementation dependent

<anssik> [http://lists.w3.org/Archives/Public/public-device-

<anssik> [https://dvcs.w3.org/hg/dap/rev/7476e089d3d9][38]

anssik: if system unable to report charging time or discharging time, can it
report default?

... Tim suggests that if cannot report some values should default from all
values, but could be handled individually

fjh: how do you distinguish between default value and real value?

<anssik> [https://dvcs.w3.org/hg/dap/rev/7476e089d3d9][38]

anssik: I am proposing this edit

<anssik> fjh: correct

<scribe> **ACTION:** gmandyam to review battery and how low battery threshold
is handled [recorded in [http://www.w3.org/2014/06/12-dap-

<trackbot> Created ACTION-699 - Review battery and how low battery threshold
is handled [on Giridhar Mandyam - due 2014-06-19].

<anssik> [http://www.w3.org/TR/2011/WD-battery-status-20110915/][40]

anssik: we are starting to revisit previous decisions, have implementations

marcos: can base event on current API to do this

gmandyam: not clear to developer that hardware will be shutting down soon

marcos: can you really do this

... I have done this, have github example

fjh: what was your concern with the examples

marcos: not a major concern, look too complicated

anssik: examples could be simple, may rearrange

<scribe> **ACTION:** anssik to propose example revisions for battery [recorded
in [http://www.w3.org/2014/06/12-dap-minutes.html#action02][41]]

<trackbot> Created ACTION-700 - Propose example revisions for battery [on
Anssi Kostiainen - due 2014-06-19].

<marcosc> gmandyam, see [https://github.com/marcoscaceres/playground/blob/gh-

<anssik> battery status playground -> [http://anssiko.github.io/battery-

fjh: so it is decided to defer battery LC until we have resolved issues raised
on list and call

<LisaDeLuca_IBM> email from the cordova mailing list related to battery

<LisaDeLuca_IBM> just saw it

<LisaDeLuca_IBM> here is the cordova dev list thread that talks about some of
the issues with the battery spec:

### Proximity

<marcosc> example battery indicator:

Proximity waiting on implementer interest/use cases:

fjh: need more implementer interest in proximity before we can proceed

anssik: maybe can learn from ambient light implementation, agree with waiting
for interest

fjh: any action we should take

anssik: some think this can be implemented with ambient light

fjh: maybe depend on hardware details

dom: not always appropriate to use light as substitute for proximity API

... webRTC is likely to use proximity API

... fine to wait and revisit, maybe ask Mounir

anssik: gaming is another potential area to use this API

... we need to see if people get what they need using ambient light

### Network Service Discovery

sent summary and updated questions to Web & TV group

added issues based on Youenn feedback: [http://lists.w3.org/Archives/Public

All DAP issues are NSD issues:

richt: would like to get more feedback on NSD, including UpNP

cathy: perhaps Clarke Stevens has some feedback from that community

Clarke: need to be able to local discovery, NSD is not the only manner, we
should also look at alternative

### Named Web Sockets

see [http://lists.w3.org/Archives/Public/public-device-

richt: alternative to NSD is lighter weight named web sockets

... currently uses DNS service discovery, Bonjour

... similar to broadcast channel

... handles lots of use cases, based on pre-agreed key to establish channel

... enables collaboration without centralized authority

... lots of functionality is enabled without much complexity

... another use case is to bootstap 2nd screen sharing

fjh: builds on top of web sockets

richt: do not need to reinvent things

fjh: might need to make hard to guess names

richt: certainly possible

anssik: is this similar to BroadcastChannel, new feature in HTML

richt: cross origin and cross user agent capabilities are new

### Standby API and Charter

Proposed approach to progressing Standby API with respect to DAP Charter

<dom> [BroadcastChannel][52]

### Standby API

Start of thread, initial proposal attached:
(Dariel Marlow)

Info on implementation work [http://lists.w3.org/Archives/Public/public-
device-apis/2014May/0034.html][54] (Anssi)

Related earlier technical work [http://lists.w3.org/Archives/Public/public-
device-apis/2014May/0038.html][55] (Anssi)

Dom Proposal [http://lists.w3.org/Archives/Public/public-device-

Marcos alternative proposal [http://lists.w3.org/Archives/Public/public-

fjh: suggest we continue this on the list

<marcosc> +q

marcos: no strong opinion on API, need to flesh out the use cases

... not finding a lot of apps that do this, so not sure how much of a need
there is for this API

... need to look at more apps to find real examples for API use

... have been looking at ios apps

anssik: I have a voip phone that keeps screen on all the time

marcos: lets find the use cases first then the API that fits

dom: bring back to WebMob

marcos: this has no huge rush so we should gather more input

... we should do a document like for NetInfo, can you, me, Dom do this

anssik: yes

... seems that this API could be premature at this point

marcos: agreed

### Testing & Implementations

Test Facilitators: Zhiqiang volunteered for all apart from Battery. Marcos
volunteered for battery.

Status update and next steps? [http://lists.w3.org/Archives/Public/public-

<scribe> **ACTION:** zhiquiang to provide summary of test status and next
steps to DAP WG [recorded in [http://www.w3.org/2014/06/12-dap-

<trackbot> Error finding 'zhiquiang'. You can review and register nicknames at

<scribe> **ACTION:** Zhiqiang to provide summary of test status and next steps
to DAP WG [recorded in [http://www.w3.org/2014/06/12-dap-

<trackbot> Created ACTION-701 - Provide summary of test status and next steps
to dap wg [on Zhiqiang Zhang - due 2014-06-19].

### Cordova update

LisaDeLuca_IBM: met with Dom last week regarding spec alignment, decided to
start with Vibration as use case to show alignment

... 4 APIs not in Cordova that are in spec, identified gaps, created Jira
issues for Cordova committers

<dom> [https://github.com/MSOpenTech/cordova-api-audit/compare/w3][62]

LisaDeLuca_IBM: monthly cordova call, microsoft and mozilla have been doing
alignment checks, should make it easier

... next step is developers update

fjh: degree of implementer interest

LisaDeLuca_IBM: new developers are looking for work shoudl be able to help

... will send email updates as appropriate

### Action Items


<trackbot> ACTION-523 -- Anssi Kostiainen to Work on test cases for battery,
vibration, and HTML Media Capture -- due 2012-08-31 -- OPEN

<trackbot> [http://www.w3.org/2009/dap/track/actions/523][63]

### Pending Actions


<trackbot> [http://www.w3.org/2009/dap/track/actions/689][64]

close ACTION-689

<trackbot> Closed ACTION-689.


<trackbot> ACTION-690 -- Frederick Hirsch to Reply to youenn re use cases etc
-- due 2014-05-22 -- PENDINGREVIEW

<trackbot> [http://www.w3.org/2009/dap/track/actions/690][65]

close ACTION-690

<trackbot> Closed ACTION-690.


<trackbot> [http://www.w3.org/2009/dap/track/actions/691][66]

close ACTION-691

<trackbot> Closed ACTION-691.


<trackbot> [http://www.w3.org/2009/dap/track/actions/692][67]

close ACTION-692

<trackbot> Closed ACTION-692.


<trackbot> [http://www.w3.org/2009/dap/track/actions/693][68]

close ACTION-693

<trackbot> Closed ACTION-693.


<trackbot> [http://www.w3.org/2009/dap/track/actions/695][69]

close ACTION-695

<trackbot> Closed ACTION-695.


<trackbot> [http://www.w3.org/2009/dap/track/actions/696][70]

close ACTION-696

<trackbot> Closed ACTION-696.


<trackbot> [http://www.w3.org/2009/dap/track/actions/697][71]

close ACTION-697

<trackbot> Closed ACTION-697.


<trackbot> [http://www.w3.org/2009/dap/track/actions/698][72]

close ACTION-698

<trackbot> Closed ACTION-698.

### Other business

next call 26 June

fjh: to reiterate, Anssi will prepare 3 publication drafts including
validation, link check, pubrules and adding diff links to sotd for monday
morning ET - Vibration, Light, HTML Media Capture

... Giri has action to review battery , Anssi to add changes proposed by fjh,
add paragraph to explain model, review feedback from Tim

<scribe> **ACTION:** anssik to add paragraph to battery explaining model,
update to 6.1 proposed by fjh [recorded in [http://www.w3.org/2014/06/12-dap-

<trackbot> Created ACTION-702 - Add paragraph to battery explaining model,
update to 6.1 proposed by fjh [on Anssi Kostiainen - due 2014-06-19].

<scribe> **ACTION:** anssik to prepare 3 publication drafts including
validation, link check, pubrules and adding diff links to sotd for monday
morning ET - Vibration, Light, HTML Media Capture [recorded in

<trackbot> Created ACTION-703 - Prepare 3 publication drafts including
validation, link check, pubrules and adding diff links to sotd for monday
morning et - vibration, light, html media capture [on Anssi Kostiainen - due

fjh: all please review Named Web Sockets

... Marcos, dom and anssi to review applications for Standby API use case

### Adjourn

## Summary of Action Items

**[NEW]** **ACTION:** anssik to add paragraph to battery explaining model,
update to 6.1 proposed by fjh [recorded in [http://www.w3.org/2014/06/12-dap-

**[NEW]** **ACTION:** anssik to prepare 3 publication drafts including
validation, link check, pubrules and adding diff links to sotd for monday
morning ET - Vibration, Light, HTML Media Capture [recorded in

**[NEW]** **ACTION:** anssik to propose example revisions for battery
[recorded in [http://www.w3.org/2014/06/12-dap-minutes.html#action02][41]]

**[NEW]** **ACTION:** gmandyam to review battery and how low battery threshold
is handled [recorded in [http://www.w3.org/2014/06/12-dap-

**[NEW]** **ACTION:** Zhiqiang to provide summary of test status and next
steps to DAP WG [recorded in [http://www.w3.org/2014/06/12-dap-

**[NEW]** **ACTION:** zhiquiang to provide summary of test status and next
steps to DAP WG [recorded in [http://www.w3.org/2014/06/12-dap-

[End of minutes]

* * *

Minutes formatted by David Booth's [scribe.perl][75] version 1.135 ([CVS

$Date: 2009-03-02 03:52:20 $

   [1]: http://www.w3.org/Icons/w3c_home

   [2]: http://www.w3.org/

   [3]: http://lists.w3.org/Archives/Public/public-device-

   [4]: http://www.w3.org/2014/06/12-dap-irc

   [5]: #agenda

   [6]: #item01

   [7]: #item02

   [8]: #item03

   [9]: #item04

   [10]: #item05

   [11]: #item06

   [12]: #item07

   [13]: #item08

   [14]: #item09

   [15]: #item10

   [16]: #item11

   [17]: #item12

   [18]: #item13

   [19]: #item14

   [20]: #item15

   [21]: #item16

   [22]: #item17

   [23]: #ActionSummary

   [24]: http://lists.w3.org/Archives/Public/public-device-

   [25]: http://lists.w3.org/Archives/Public/public-device-

   [26]: http://lists.w3.org/Archives/Public/public-device-

   [27]: http://lists.w3.org/Archives/Public/public-device-

   [28]: http://lists.w3.org/Archives/Public/public-device-

   [29]: http://lists.w3.org/Archives/Public/public-device-

   [30]: http://lists.w3.org/Archives/Public/public-device-

   [31]: http://lists.w3.org/Archives/Public/public-device-

   [32]: http://lists.w3.org/Archives/Public/public-device-

   [33]: http://lists.w3.org/Archives/Public/public-device-

   [34]: http://lists.w3.org/Archives/Public/public-device-

   [35]: https://bugzilla.mozilla.org/show_bug.cgi?id=890715

   [36]: https://docs.google.com/presentation/d/1lpOlTtq93XtPCtZNsX00zmSJ6idO7

   [37]: http://lists.w3.org/Archives/Public/public-device-

   [38]: https://dvcs.w3.org/hg/dap/rev/7476e089d3d9

   [39]: http://www.w3.org/2014/06/12-dap-minutes.html#action01

   [40]: http://www.w3.org/TR/2011/WD-battery-status-20110915/

   [41]: http://www.w3.org/2014/06/12-dap-minutes.html#action02

   [42]: https://github.com/marcoscaceres/playground/blob/gh-

   [43]: http://anssiko.github.io/battery-status/

   [44]: http://apache.markmail.org/search/?q=org.apache.incubator.callback-

   [45]: http://marcoscaceres.github.io/playground/flexbox/keypad.html

   [46]: http://lists.w3.org/Archives/Public/public-device-

   [47]: http://lists.w3.org/Archives/Public/public-device-

   [48]: http://lists.w3.org/Archives/Public/public-device-

   [49]: http://www.w3.org/2009/dap/track/issues/open

   [50]: http://lists.w3.org/Archives/Public/public-device-

   [51]: http://lists.w3.org/Archives/Public/public-device-

   [52]: http://www.whatwg.org/specs/web-apps/current-work/multipage/web-

   [53]: http://lists.w3.org/Archives/Public/public-device-

   [54]: http://lists.w3.org/Archives/Public/public-device-

   [55]: http://lists.w3.org/Archives/Public/public-device-

   [56]: http://lists.w3.org/Archives/Public/public-device-

   [57]: http://lists.w3.org/Archives/Public/public-device-

   [58]: http://lists.w3.org/Archives/Public/public-device-

   [59]: http://www.w3.org/2014/06/12-dap-minutes.html#action03

   [60]: http://www.w3.org/2009/dap/track/users>.

   [61]: http://www.w3.org/2014/06/12-dap-minutes.html#action04

   [62]: https://github.com/MSOpenTech/cordova-api-audit/compare/w3

   [63]: http://www.w3.org/2009/dap/track/actions/523

   [64]: http://www.w3.org/2009/dap/track/actions/689

   [65]: http://www.w3.org/2009/dap/track/actions/690

   [66]: http://www.w3.org/2009/dap/track/actions/691

   [67]: http://www.w3.org/2009/dap/track/actions/692

   [68]: http://www.w3.org/2009/dap/track/actions/693

   [69]: http://www.w3.org/2009/dap/track/actions/695

   [70]: http://www.w3.org/2009/dap/track/actions/696

   [71]: http://www.w3.org/2009/dap/track/actions/697

   [72]: http://www.w3.org/2009/dap/track/actions/698

   [73]: http://www.w3.org/2014/06/12-dap-minutes.html#action05

   [74]: http://www.w3.org/2014/06/12-dap-minutes.html#action06

   [75]: http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm

   [76]: http://dev.w3.org/cvsweb/2002/scribe/

Received on Friday, 13 June 2014 22:07:16 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:54:03 UTC