See also: IRC log
<trackbot> Date: 30 March 2011
<darobin> ScribeNick: cmarc
<darobin> Scribe: Cécile
<fjh> Identity in the Browser workshop, http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/0105.html
<fjh> Opera, augmented reality, http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/0119.html
<fjh> June/July DAP F2F questionnaire, http://www.w3.org/2002/09/wbs/43696/juljun-f2f/
<scribe> Agenda: please register your availability for next f2f
<fjh> cancel 27 April teleconference
RESOLUTION: 27 April teleconference is cancelled.
<fjh> Approve F2F minutes, 15-16 March 2011
<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/att-0097/minutes-2011-03-15.html
<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/att-0097/minutes-2011-03-16.html
<darobin> current charter
RESOLUTION: Minutes from 15-16 March 2011 F2F are approved
<darobin> ongoing draft charter
<fjh> Current charter, http://www.w3.org/2009/05/DeviceAPICharter.html
<fjh> Proposed charter, http://www.w3.org/2010/11/DeviceAPICharter.html
<fjh> proposed additions, see #2 http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/0112.html
Web introducer : there is an IPR problem to be in a charter
need to discuss the web introducer, the charter should be proposed to W3C for end of april
<fjh> we are running out of time, really need to have draft charter from WG in mid april. decision needed
<fjh> probably cannot include in charter if no participation due to IPR concerns
<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/0112.html
agreed to remove communication log during f2f
<fjh> also agreed user interaction - vibration, beeps, menus, broken up into separate items
charter has to be changed in that sense
<fjh> Issue remains to narrow discovery topic or we won't be able to put in charter
<fjh> Robin is looking at this and joined home networking task force
the task force started yesterday
have to be precise about what we want, web introducer different from other discovery use cases
<fjh> Claes is talking with Google and will remind them of urgency of joining WG
<fjh> Anssi mentions concern of maintaining focus of DAP wg
a simple discovery mechanism should be the solution, on TV: electroni Program guide, etc. discovery is generic
coupling between APi, should be protocol agnostic
we should make sure it does map to "real world" protocols, even decoupled
<fjh> privacy and the charter ->
<fjh> add explicit deliverable for privacy REC deliverable with note that this might be taken over by another group
<fjh> add explicit deliverable for privacy use cases and requirements NOTE
<AnssiK> if the discovery API will get into the revised Charter I'd like to see it loosely coupled from any underlying discovery protocols
have to figure out with gallery
<fjh> sense we can keep it in charter and later not progress if not needed
App Launcher replaced by web intent..
<fjh> WG has decided not to have app launcher listed in charter
<fjh> We need to clarify status of Web Introducer and I believe web Intents in order to have a charter item in this area.
we need to make progress on publication
<fjh> ACTION-343?
<trackbot> ACTION-343 -- Richard Tibbett to propose better wording for System information and events api in new charter -- due 2011-03-02 -- OPEN
<trackbot> http://www.w3.org/2009/dap/track/actions/343
<fjh> HTML Media Capture, role attribute update (Dom), WD update, then Last Call CfC
<fjh> FPWD of Message draft based on alternative URI based approach
<fjh> await Dom
<fjh> Contacts
<fjh> ACTION-257?
<trackbot> ACTION-257 -- Richard Tibbett to define what goes on for concurrent calls to find() when there is no error callback (and step three also needs to define that); then report to group so we can do the same to SysInfo get -- due 2010-09-29 -- OPEN
<trackbot> http://www.w3.org/2009/dap/track/actions/257
<fjh> ACTION-271?
<trackbot> ACTION-271 -- Robin Berjon to figure out the event loop stuff for contacts -- due 2011-03-23 -- OPEN
<trackbot> http://www.w3.org/2009/dap/track/actions/271
<fjh> ACTION-278?
<trackbot> ACTION-278 -- Suresh Chitturi to propose harmonisation descriptions for Contacts fields -- due 2010-10-06 -- OPEN
<trackbot> http://www.w3.org/2009/dap/track/actions/278
<darobin> ACTION-271?
<trackbot> ACTION-271 -- Robin Berjon to figure out the event loop stuff for contacts -- due 2011-03-23 -- OPEN
<trackbot> http://www.w3.org/2009/dap/track/actions/271
<fjh> ACTION-278: http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/0128.html
<trackbot> ACTION-278 Propose harmonisation descriptions for Contacts fields notes added
<fjh> ACTION-278: closed
<trackbot> ACTION-278 Propose harmonisation descriptions for Contacts fields notes added
<trackbot> If you meant to close ACTION-278, please use 'close ACTION-278'
<fjh> Robin to talk to Rich regarding ACTION-271
<fjh> Calendar, action done during F2F
adding notes regarding timezones on calendar
action . can be closed .
<trackbot> Sorry, couldn't find user - .
<fjh> CfC for FPWD
<darobin> ACTION: Robin CfC for Calendar [recorded in http://www.w3.org/2011/03/30-dap-minutes.html#action01]
<trackbot> Created ACTION-376 - CfC for Calendar [on Robin Berjon - due 2011-04-06].
<fjh> API Requirements, Dom
<fjh> Access Requirements Note, published, see http://www.w3.org/News/2011#entry-9037
<fjh> Editorial updates and prototyping
<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/0110.html
<fjh> we have already agreed to have Feature Permissions in charter
<fjh> anssi: status - update needed from Laszlo
<darobin> Capabilities Container
web notification Working group concerned or not,..
<darobin> ACTION: Robin to bring a Capabilities Container proposal to the WG [recorded in http://www.w3.org/2011/03/30-dap-minutes.html#action02]
<trackbot> Created ACTION-377 - Bring a Capabilities Container proposal to the WG [on Robin Berjon - due 2011-04-06].
Container discussion : there are also discussions about installed web apps
hard to say about what it does: so need for code examples...
are there challenges on this, face to existing apis.
need some feedbacks, on proposals, from implmentors
<fjh> we need a proposal on the list so WG members can understand
need to see what the browsers already do : can send a link on this
<fjh> Note, clarification of Permissions charter item to include containers might be appropriate for charter draft
the notion of permissions with user dialog , need to be trusted by the user
with proper permissions
<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/0122.html
<nwidell> sorry need to drop off
<fjh> request for implementer feedback to see if this works and should be progressed as drafted
inspired by device orientation
do we have a guaranty to handle immediately when desired ?
this is undefined, will be fired when
up to the implementation for device orientation
for battery level this is less critical
darobin: device orientation, only to the window object
battery status of other device : no text to say that it only applys to wndow
if you have a camera separated to the laptop, for example/
ok
<darobin> robin: problem 1) need guarantee that it triggers the callback immediately upon handler registration, 2) should not be limited to applying to window
remove the limitation that is on device orientation for the battery
next steps start with that one
<fjh> Anssi will produce draft battery status even spec using ReSpec
<fjh> ACTION-358?
<trackbot> ACTION-358 -- Anssi Kostiainen to provide first editors draft of a Battery status API -- due 2011-03-23 -- OPEN
<trackbot> http://www.w3.org/2009/dap/track/actions/358
<darobin> this relates to ACTION-358
<fjh> ACTION-358: problem 1) need guarantee that it triggers the callback immediately upon handler registration, 2) should not be limited to applying to window
<trackbot> ACTION-358 Provide first editors draft of a Battery status API notes added
<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/0123.html (Suresh)
<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/0125.html
<fjh> use cases, http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/0126.html (Dzung)
<fjh> ACTION-294Create an editors draft for new proposed network connection APIRichard Tibbett
Suresh is not there
<fjh> discuss on list
so continue discussion on the mail
<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/0102.html (Robin)
<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/0109.html
<fjh> current syntax will remain good but hopefully simpler syntax will be available
<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Mar/0111.html
dom3 events will remain specific document, not finished yet
ways to trigger on input elements
<fjh> anssi: will need standard for this at some time
<fjh> robin: something to be aware of
no specific things to raise on this today
<fjh> discussion off list
just to recap : think about generic sensor api
asking for inputs on this
<fjh> Bryan asking for input on sensors, will share information related to topic
<fjh> ACTION-173?
<trackbot> ACTION-173 -- Dzung Tran to implement privacy changes noted by alissa, see http://lists.w3.org/Archives/Public/public-device-apis/2010May/0072.html -- due 2010-05-26 -- OPEN
<trackbot> http://www.w3.org/2009/dap/track/actions/173
<fjh> ACTION-202?
<trackbot> ACTION-202 -- Dzung Tran to include changes from ACTION-191 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0253.html -- due 2010-06-30 -- OPEN
<trackbot> http://www.w3.org/2009/dap/track/actions/202
<fjh> ACTION-219?
<trackbot> ACTION-219 -- Kangchan Lee to make a concrete proposal for AppLauncher -- due 2010-07-22 -- OPEN
<trackbot> http://www.w3.org/2009/dap/track/actions/219
<fjh> ACTION-220?
<trackbot> ACTION-220 -- Bryan Sullivan to make a concrete proposal for AppLauncher -- due 2010-07-22 -- OPEN
<trackbot> http://www.w3.org/2009/dap/track/actions/220
<fjh> ACTION-173 closed
<trackbot> ACTION-173 Implement privacy changes noted by alissa, see http://lists.w3.org/Archives/Public/public-device-apis/2010May/0072.html closed
<fjh> ISSUE-78?
<trackbot> ISSUE-78 -- Capture has a minimisation problem with EXIF data (e.g. it could be Geotagged) -- open
<trackbot> http://www.w3.org/2009/dap/track/issues/78
<fjh> ACTION-202 closed
<trackbot> ACTION-202 Include changes from ACTION-191 http://lists.w3.org/Archives/Public/public-device-apis/2010Jun/0253.html closed
<fjh> ACTION-219 closed
<trackbot> ACTION-219 Make a concrete proposal for AppLauncher closed
<fjh> ACTION-220 closed
<trackbot> ACTION-220 Make a concrete proposal for AppLauncher closed
<fjh> ISSUE-78: note already added to document
<trackbot> ISSUE-78 Capture has a minimisation problem with EXIF data (e.g. it could be Geotagged) notes added
<fjh> ISSUE-78 closed
<trackbot> ISSUE-78 Capture has a minimisation problem with EXIF data (e.g. it could be Geotagged) closed
<fjh> ACTION-278?
<trackbot> ACTION-278 -- Suresh Chitturi to propose harmonisation descriptions for Contacts fields -- due 2010-10-06 -- OPEN
<trackbot> http://www.w3.org/2009/dap/track/actions/278
<fjh> ACTION-278 closed
<trackbot> ACTION-278 Propose harmonisation descriptions for Contacts fields closed