[![W3C][1]][2]

# Device APIs Working Group Teleconference

## 05 Jun 2013

[Agenda][3]

See also: [IRC log][4]

## Attendees

Present

    Anssi_Kostiainen, Frederick_Hirsch, Giri_Mandyam, Josh_Soref, dom

Regrets


Chair

    Frederick_Hirsch

Scribe

    Josh_Soref

## Contents

  * [Topics][5]

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

    2. [Minutes approval][7]

    3. [Charter Extension][8]

    4. [Vibration][9]

    5. [Proximity, Light][10]

    6. [Network Service Discovery][11]

    7. [Test cases and Interop][12]

    8. [Action Review][13]

    9. [Issue Review][14]

    10. [Other Business][15]

  * [Summary of Action Items][16]

* * *

<trackbot> Date: 05 June 2013

<scribe> scribe: Josh_Soref

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

<fjh> Please review Media Capture and Streams by 15 June,
[http://lists.w3.org/Archives/Public/public-device-apis/2013May/0080.html][17]

<dom> [Bugzilla list of bugs for Media Capture (with link to "submit new
bug")][18]

### Minutes approval

fjh: thanks Josh_Soref for sending out the minutes yesterday

... is there any concern about approving them?

<fjh> Approve minutes from 29 May 2013

<fjh> [http://lists.w3.org/Archives/Public/public-device-
apis/2013Jun/att-0007/minutes-2013-05-29.html][19]

fjh: we talked a lot about testing

**RESOLUTION: Minutes from 29 May 2013 are approved**

### Charter Extension

<fjh> [http://lists.w3.org/Archives/Public/public-device-
apis/2013May/0078.html][20]

<fjh> No comments received, extend charter through 31 December 2014?

dom: i'll take the action

... i need to get internal feedback on this activity

... i can do this as part of my action item

<fjh> **ACTION:** dom to arrange for DAP charter extension, per
[http://lists.w3.org/Archives/Public/public-device-apis/2013May/0078.html][20]
[recorded in [http://www.w3.org/2013/06/05-dap-minutes.html#action01][21]]

<trackbot> Created ACTION-637 - Arrange for DAP charter extension, per
[http://lists.w3.org/Archives/Public/public-device-apis/2013May/0078.html][20]
[on Dominique Hazaël-Massieux - due 2013-06-12].

### Vibration

<fjh> LC period ends 13 June.

<fjh> Updated to mention web notifications,
[http://lists.w3.org/Archives/Public/public-device-apis/2013May/0073.html][22]
(Anssi)

<fjh> minor editorial suggestion, [http://lists.w3.org/Archives/Public/public-
device-apis/2013Jun/0006.html][23]

fjh: anything else to discuss on this?

<fjh> anssik, are you able to update draft based on my comment?

<anssik> yes

### Proximity, Light

fjh: we said we'd wait until the end of May

... we had no list discussion

... we could wait a little longer, but i don't want to wait until the end of
July

... i propose we wait another week, and i'll send a message after that

anssik: i'm looking for feedback from anne and dougt

... let me check the Mozilla Bugzilla

... to give you a quick summary

<anssik> [https://bugzilla.mozilla.org/show_bug.cgi?id=842952][24]

anssik: they don't have experience merging the interfaces

fjh: is there a way to watch bugzilla?

anssik: you can create an account

... and you can cc yourself to the bugs

Josh_Soref: you can also watch others

... either placeholder accounts/components

... or interesting people

anssik: i'll include links to their bugs in the wiki

fjh: i don't know if you'll be on the Futures calls

... it will be interesting

... so we're still waiting

... and we need to make a decision in a week or two

... who's doing this work?

... dougt?

anssik: dougt was the original author

... Mozilla has many contributors

... some are volunteering

... so you can't expect schedules

... they aren't committing to schedules

... the guy working on this seems to be a volunteer

fjh: is this Jeremy?

anssik: yes, and i don't recognize him

### Network Service Discovery

<fjh> prefix issue , [http://lists.w3.org/Archives/Public/public-device-
apis/2013Apr/0054.html][25] (Jean-Claude)

<fjh> status [http://lists.w3.org/Archives/Public/public-device-
apis/2013May/0028.html][26] (Rich)

<fjh> Awaiting further activity

### Test cases and Interop

<fjh> Test cases and Interop

<fjh> Request for implementation status, [http://lists.w3.org/Archives/Public
/public-device-apis/2013May/0069.html][27]

<fjh> Test case approval process [http://lists.w3.org/Archives/Public/public-
device-apis/2013Jun/0003.html][28]

<fjh> new version of jean-claude implementation at
[http://lists.w3.org/Archives/Public/public-device-apis/2013Jun/0009.html][29]

fjh: all of the web tests are in a single repository

... and people in-w3 and outside-w3 can contribute using git

... and then there's a question about Approval

... and people said it's cumbersome to use WG to deal with approving

... and the pull-request

... is handled by people relevant to the test

... is that it, dom?

dom: not sure where you got that

fjh: you sent questions to the list

dom: i sent questions to the list

... but i don't know that i saw a process detailed

... let me state what i understand of the current situation

... until last week, i thought moving to github was aligning the Repo aspects
of our test-work

... tobie indicated as part of using GitHub repository

... we'd have to align w/ a given process for submitting-reviewing-approving
test cases

... and the reason is so we have a single process to make it easy for people
to understand it

... and be open to external people

... afaik, the process itself hasn't been defined yet

... in particular, i don't know what the review and approval process is
supposed to be

fjh: tobie said he'd write something down based on what i was reading between
the lines

... we'll see, we're waiting for tobie to write it down

... i did see a message from him to you saying yes, we need to write things
down

... it doesn't affect us in the interim

... we still need tests

... and anssik is working on this?

anssik: yes

dom: if we want to exit CR

... for some of our specs, we need our testcases reviewed and approved by the
WG

... i guess we could still do the old approval process

... without waiting for the new centralized process

... if we do wait for this new process, it'll create a time dependency, that
we won't be happy with

fjh: with GitHub, you need to use pull requests

Josh_Soref: not precisely true

fjh: and wait for someone to merge things

dom: i can merge things

fjh: so we're good basically, we don't have a problem

dom: we still need to define a plan for reviewing+approving testcases

... it needs to be done sooner or later

fjh: the issue is adequate coverage

... and we want to interop for all features

... and given we want to make the spec simple and modular

... so the WG can do a CfC of "do we have coverage"

... i'm hoping it isn't a big issue

dom: who would do coverage analysis

... and when would the CfC happen?

fjh: a test writer (e.g. anssik) could decide they think they have coverage

... and the WG would have a CfC

... given the simplicity of the specs we're doing now

... Vibration

... but NSD is different

... not sure how we'd do that given the limited expertise in the group

... i guess the Media Capture TF will review test cases for their work

... that's an action

<fjh> **ACTION:** fjh to review webapps approach to reviewing test cases
[recorded in [http://www.w3.org/2013/06/05-dap-minutes.html#action02][30]]

<trackbot> Created ACTION-638 - Review webapps approach to reviewing test
cases [on Frederick Hirsch - due 2013-06-12].

### Action Review

<fjh> ACTION-523?

<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][31]

<fjh> ACTION-621?

<trackbot> ACTION-621 -- Anssi Kostiainen to create test cases for HTML Media
Capture -- due 2013-03-13 -- OPEN

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

anssik: there haven't been updates

... i haven't had much time

<fjh> ACTION-634?

<trackbot> ACTION-634 -- Anssi Kostiainen to update introduction of vibration
to refer to notification API -- due 2013-06-05 -- OPEN

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

fjh: you did action-634

... i can close that

<fjh> close ACTION-634

<trackbot> Closed ACTION-634 Update introduction of vibration to refer to
notification API.

anssik: yes that can be closed

### Issue Review

<fjh> ISSUE-128?

<trackbot> ISSUE-128 -- Need more description on how bandwidth should be
estimated -- open

<trackbot> [http://www.w3.org/2009/dap/track/issues/128][34]

### Other Business

fjh:

<dom> (regrets for next week from me)

Josh_Soref: there's a Futures call in 35 minutes

<fjh> futures call [http://lists.w3.org/Archives/Public/public-media-
capture/2013Jun/0009.html][35]

[ adjourned ]

trackbot, end meeting

## Summary of Action Items

**[NEW]** **ACTION:** dom to arrange for DAP charter extension, per
[http://lists.w3.org/Archives/Public/public-device-apis/2013May/0078.html][20]
[recorded in [http://www.w3.org/2013/06/05-dap-minutes.html#action01][21]]

**[NEW]** **ACTION:** fjh to review webapps approach to reviewing test cases
[recorded in [http://www.w3.org/2013/06/05-dap-minutes.html#action02][30]]


[End of minutes]

* * *

Minutes formatted by David Booth's [scribe.perl][36] version 1.135 ([CVS
log][37])

$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-
apis/2013Jun/0008.html

   [4]: http://www.w3.org/2013/06/05-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]: #ActionSummary

   [17]: http://lists.w3.org/Archives/Public/public-device-
apis/2013May/0080.html

   [18]: https://www.w3.org/Bugs/Public/buglist.cgi?product=WebRTC%20Working%2
0Group&component=Media%20Capture%20and%20Streams&resolution=---&list_id=13529

   [19]: http://lists.w3.org/Archives/Public/public-device-
apis/2013Jun/att-0007/minutes-2013-05-29.html

   [20]: http://lists.w3.org/Archives/Public/public-device-
apis/2013May/0078.html

   [21]: http://www.w3.org/2013/06/05-dap-minutes.html#action01

   [22]: http://lists.w3.org/Archives/Public/public-device-
apis/2013May/0073.html

   [23]: http://lists.w3.org/Archives/Public/public-device-
apis/2013Jun/0006.html

   [24]: https://bugzilla.mozilla.org/show_bug.cgi?id=842952

   [25]: http://lists.w3.org/Archives/Public/public-device-
apis/2013Apr/0054.html

   [26]: http://lists.w3.org/Archives/Public/public-device-
apis/2013May/0028.html

   [27]: http://lists.w3.org/Archives/Public/public-device-
apis/2013May/0069.html

   [28]: http://lists.w3.org/Archives/Public/public-device-
apis/2013Jun/0003.html

   [29]: http://lists.w3.org/Archives/Public/public-device-
apis/2013Jun/0009.html

   [30]: http://www.w3.org/2013/06/05-dap-minutes.html#action02

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

   [32]: http://www.w3.org/2009/dap/track/actions/621

   [33]: http://www.w3.org/2009/dap/track/actions/634

   [34]: http://www.w3.org/2009/dap/track/issues/128

   [35]: http://lists.w3.org/Archives/Public/public-media-
capture/2013Jun/0009.html

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

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