See also: IRC log
<trackbot> Date: 12 June 2014
<scribe> ScribeNick: fjh
Welcome to new group participants:
Zhiqiang (intel), Mikio (Mitsubishi Electric) http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/0018.html
Publishing moratoria for end of 2014 : http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/0001.html
Approve minutes from 15 May 2014
RESOLUTION: Minutes from 15 May 2014 are approved
Vibration API CfC: http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/0026.html
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
fjh: CfC on list ends tomorrow
... no comments, so good to go
HTML Media Capture CfC; http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/0028.html
fjh: minor typo found by Cathy, http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/0056.html
... other than that, no issues, so should be included
fjh: some editional proposed edits based on Tim’s comments: http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/0048.html
... I also had comment on default
anssik: if unknown or unable to report values use default of full, eases development
... 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: https://bugzilla.mozilla.org/show_bug.cgi?id=890715
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
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: 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: 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-minutes.html#action01]
<trackbot> Created ACTION-699 - Review battery and how low battery threshold is handled [on Giridhar Mandyam - due 2014-06-19].
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]
<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-pages/flexbox/keypad.html#L233
<anssik> battery status playground -> http://anssiko.github.io/battery-status/
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: http://apache.markmail.org/search/?q=org.apache.incubator.callback-dev+list%3Aorg.apache.incubator.callback-dev+order%3Adate-backward+battery+plugin+api+drains#query:org.apache.incubator.callback-dev%20list%3Aorg.apache.incubator.callback-dev%20order%3Adate-backward%20battery%20plugin%20api%20drains+page:1+mid:4auqqxne2pfvnpm2+state:results
<marcosc> example battery indicator: http://marcoscaceres.github.io/playground/flexbox/keypad.html
Proximity waiting on implementer interest/use cases: http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/0019.html
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
sent summary and updated questions to Web & TV group http://lists.w3.org/Archives/Public/public-device-apis/2014Jun/0012.html
added issues based on Youenn feedback: http://lists.w3.org/Archives/Public/public-device-apis/2014May/0029.html
All DAP issues are NSD issues: http://www.w3.org/2009/dap/track/issues/open
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
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
Proposed approach to progressing Standby API with respect to DAP Charter http://lists.w3.org/Archives/Public/public-device-apis/2014May/0077.html
Start of thread, initial proposal attached: http://lists.w3.org/Archives/Public/public-device-apis/2014Feb/0001.html (Dariel Marlow)
Info on implementation work http://lists.w3.org/Archives/Public/public-device-apis/2014May/0034.html (Anssi)
Related earlier technical work http://lists.w3.org/Archives/Public/public-device-apis/2014May/0038.html (Anssi)
Marcos alternative proposal http://lists.w3.org/Archives/Public/public-device-apis/2014May/0054.html
fjh: suggest we continue this on the list
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
... seems that this API could be premature at this point
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-device-apis/2014Jun/0016.html
<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-minutes.html#action03]
<trackbot> Error finding 'zhiquiang'. You can review and register nicknames at <http://www.w3.org/2009/dap/track/users>.
<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-minutes.html#action04]
<trackbot> Created ACTION-701 - Provide summary of test status and next steps to dap wg [on Zhiqiang Zhang - due 2014-06-19].
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
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
<trackbot> ACTION-523 -- Anssi Kostiainen to Work on test cases for battery, vibration, and HTML Media Capture -- due 2012-08-31 -- OPEN
<trackbot> Closed ACTION-689.
<trackbot> ACTION-690 -- Frederick Hirsch to Reply to youenn re use cases etc -- due 2014-05-22 -- PENDINGREVIEW
<trackbot> Closed ACTION-690.
<trackbot> Closed ACTION-691.
<trackbot> Closed ACTION-692.
<trackbot> Closed ACTION-693.
<trackbot> Closed ACTION-695.
<trackbot> Closed ACTION-696.
<trackbot> Closed ACTION-697.
<trackbot> Closed ACTION-698.
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-minutes.html#action05]
<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 http://www.w3.org/2014/06/12-dap-minutes.html#action06]
<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 2014-06-19].
fjh: all please review Named Web Sockets
... Marcos, dom and anssi to review applications for Standby API use case confirmation