See also: IRC log
<trackbot> Date: 15 May 2013
<scribe> ScribeNick: fjh
Reminder, June F2F has been canceled, http://lists.w3.org/Archives/Public/public-device-apis/2013Mar/0035.html
HTML Media Capture CR draft published last Thursday, 9 May, http://www.w3.org/TR/2013/CR-html-media-capture-20130509/
Approve minutes from 8 May 2013
http://lists.w3.org/Archives/Public/public-device-apis/2013May/att-0039/minutes-2013-05-08.html
RESOLUTION: Minutes from 8 May 2013 are approved
fjh: sent CfC to shelve, ends this Friday 17 May, general support for shelving
... Art suggested we publish Web Intents as WG Note, I agree that is a good idea, please indicate support for that in response to CfC
http://lists.w3.org/Archives/Public/public-device-apis/2013May/0020.html
fjh: I think we can plan to publish Note next Thur assuming CfC ok, have suggested edits and status section changes to Greg, Art had some further additions
updated editors draft: http://lists.w3.org/Archives/Public/public-device-apis/2013May/0025.html
CfC to publish another Last Call WD (CfC ends 21 May please respond): http://lists.w3.org/Archives/Public/public-device-apis/2013May/0037.html
fjh: please indicate support on list, I'm assuming that this process of going to LC then CR again will not cause delay or problems
dom: the transition request might be handled by email if no more LC concerns
Plans to update technical approach: http://lists.w3.org/Archives/Public/public-device-apis/2013May/0026.html
Suggested update to privacy considerations section http://lists.w3.org/Archives/Public/public-device-apis/2013May/0022.html (Frederick)
fjh: I suggested privacy considerations, have not seen feedback, Anssi?
anssik: looks ok to me, I can update the specification
fjh: I think we can go ahead and update the specifications, currently the security and privacy considerations are blank, we can still accept further constructive comments
Open issue: http://lists.w3.org/Archives/Public/public-device-apis/2013May/0034.html
fjh: how do we handle the issue, wait a while, note the issue in the spec
anssik: would prefer to wait and if we do not have a proposal, then revert the specification
<dom> +1 on waiting
anssik: just got concern yesterday, open issue in bug tracker, so hope they are doing prototyping
fjh: maybe you can ask if they are prototyping
anssik: asked this implicitly
... so lets wait
... they are definitely implementing, so I think they need time to experiment and think about the issue. Can get ideas from working code.
fjh: suggest we revisit at end of this month
anssik: sounds reasonable
fjh: the issue of the consolidated sensor spec has come up again, a previous issue that we decided against, should we be revisiting it?
anssik: suggest we wait for a concrete proposal
fjh: that sounds reasonable and all should know that addressing an issue would require another proposal to consider
gmandyam: not good sensor APIs on handheld devices in native APIs
fjh: this is part of the reason we separated the functionality and went with modular specs - to enable implementation and testing of items; we are aware of commonality concerns but wanted modular approach
gmandyam: this answers my question
prefix issue , http://lists.w3.org/Archives/Public/public-device-apis/2013Apr/0054.html (Jean-Claude)
status http://lists.w3.org/Archives/Public/public-device-apis/2013May/0028.html (Rich)
fjh: Rich responded indicating we may want to wait until Cathy returns in July, I suggest if any discussion can happen on list in advance that would be helpful
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
anssik: starting with HTML Media Capture
fjh: good if others can help as well, so if you share on list that might encourage them
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
ACTION-625?
<trackbot> ACTION-625 -- Dominique Hazaël-Massieux to move DAP tests to Git, with help from others as needed -- due 2013-05-01 -- OPEN
<trackbot> http://www.w3.org/2009/dap/track/actions/625
fjh: i believe still in progress
... not sure how much work is involved
dom: technical work is easy but need help making sure we are clear on tests WG has approved
<scribe> pending items
ACTION-446?
<trackbot> ACTION-446 -- Frederick Hirsch to review security issue http://lists.w3.org/Archives/Public/public-device-apis/2011Aug/0006.html -- due 2011-08-24 -- PENDINGREVIEW
<trackbot> http://www.w3.org/2009/dap/track/actions/446
fjh: did this, nothing directly relevant now
close ACTION-446
<trackbot> Closed ACTION-446 Review security issue http://lists.w3.org/Archives/Public/public-device-apis/2011Aug/0006.html.
ACTION-591?
<trackbot> ACTION-591 -- Greg Billock to work with Mounir and James to create new webintents draft that reflects web activities and issues -- due 2013-03-29 -- PENDINGREVIEW
<trackbot> http://www.w3.org/2009/dap/track/actions/591
fjh: Greg and Mounir agreed to close, meeting was held and documented, further work will depend on implementation experience and experiments
close ACTION-591
<trackbot> Closed ACTION-591 Work with Mounir and James to create new webintents draft that reflects web activities and issues.
ACTION-622?
<trackbot> ACTION-622 -- Frederick Hirsch to follow up on concrete actions based on PING input -- due 2013-03-13 -- PENDINGREVIEW
<trackbot> http://www.w3.org/2009/dap/track/actions/622
fjh: I shared concrete suggestions, see http://lists.w3.org/Archives/Public/public-device-apis/2013May/0022.html
ACTION-622: I shared concrete suggestions, see http://lists.w3.org/Archives/Public/public-device-apis/2013May/0022.html
<trackbot> Notes added to ACTION-622 Follow up on concrete actions based on PING input.
close ACTION-622
<trackbot> Closed ACTION-622 Follow up on concrete actions based on PING input.
ACTION-630?
<trackbot> ACTION-630 -- Frederick Hirsch to send CfC re shelving Web Intents, Web Intents Addendum, Pick Media Intent, Pick Contacts intent -- due 2013-05-15 -- PENDINGREVIEW
<trackbot> http://www.w3.org/2009/dap/track/actions/630
ACTION-630: CfC sent http://lists.w3.org/Archives/Public/public-device-apis/2013May/0018.html
<trackbot> Notes added to ACTION-630 Send CfC re shelving Web Intents, Web Intents Addendum, Pick Media Intent, Pick Contacts intent.
ACTION-630: suggestion to publish Web Intents as WG Note http://lists.w3.org/Archives/Public/public-device-apis/2013May/0020.html
<trackbot> Notes added to ACTION-630 Send CfC re shelving Web Intents, Web Intents Addendum, Pick Media Intent, Pick Contacts intent.
close ACTION-630
<trackbot> Closed ACTION-630 Send CfC re shelving Web Intents, Web Intents Addendum, Pick Media Intent, Pick Contacts intent.
ISSUE-127?
<trackbot> ISSUE-127 -- Status section of Battery CR draft should include exit criteria and at-risk items -- open
<trackbot> http://www.w3.org/2009/dap/track/issues/127
fjh: need to check this
... checked, Battery CR draft does not include this information in status section - http://www.w3.org/TR/2012/CR-battery-status-20120508/
... however this was recorded in the transition announcement, so I will close this issue
ISSUE-127: information is included in member-only transition announcement, https://lists.w3.org/Archives/Member/chairs/2012AprJun/0032.html
<trackbot> Notes added to ISSUE-127 Status section of Battery CR draft should include exit criteria and at-risk items.
close ISSUE-127
<trackbot> Closed ISSUE-127 Status section of Battery CR draft should include exit criteria and at-risk items.
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
fjh: discussion ongoing on list
ISSUE-128: recent discussion thread starts here: http://lists.w3.org/Archives/Public/public-device-apis/2013May/0010.html
<trackbot> Notes added to ISSUE-128 Need more description on how bandwidth should be estimated.
ISSUE-128: concerns, http://lists.w3.org/Archives/Public/public-device-apis/2013May/0012.html
<trackbot> Notes added to ISSUE-128 Need more description on how bandwidth should be estimated.
ISSUE-128: support for concerns, http://lists.w3.org/Archives/Public/public-device-apis/2013May/0014.html
<trackbot> Notes added to ISSUE-128 Need more description on how bandwidth should be estimated.
fjh: have scheduled DAP F2F during TPAC in China for Thur/Fri 14-15 November
... consistent with Sys Apps on Mon/Tue
... anticipate joint session with Media Capture TF on Thur or Fri, they cannot do this Mon/Tue due to Mon/Tue Web RTC meeting
... thus Thur/Fri makes sense
... expect with this and ongoing work enough work, probably 1.5 days, depends on the details - if we have Web Intents topics then more than we will have time for
... will need to review as we get nearer to make sure we have appropriate agenda for f2f
... Dom, how do we get an invitation letter and what we need to get a Visa?
dom: the registration page will include information and form to request invitation letter, should have that registration well in advance of f2f
fjh: good, thanks
none