See also: IRC log
<trackbot> Date: 16 November 2011
<fjh> trackbot, start telecon
<trackbot> Meeting: Device APIs Working Group Teleconference
<trackbot> Date: 16 November 2011
<scribe> Scribe: Josh_Soref
<fjh> Please complete questionnaire for dates of next F2F in March 2012: http://lists.w3.org/Archives/Member/member-device-apis/2011Nov/0003.html (Dom)
<fjh> Review: Geolocation WG will publish the DeviceOrientation Event specification as a Last Call - http://lists.w3.org/Archives/Member/member-device-apis/2011Nov/0002.html
<fjh> A big thank you to Josh for scribing the F2F
<darobin> +1
fjh: There's a Survey, with 3 weeks available
... please fill it in
... especially possible hosts, please look into whether you're available
<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/0131.html
<AnssiK> +1 to approve the minutes
RESOLUTION: Minutes from F2F are approved
<fjh> CfC to publish FPWD, http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/0016.html
<fjh> proposed RESOLUTION: Publish FPWD of Vibration API on 22 November 2011
<AnssiK> +1 to publish FPWD
<wonsuk> +1
<dom> +1 on FPWD
<fjh> +1 to FPWD
<Kihong_Kwon> +1
<darobin> +1 too
AnssiK: there's a discussion about Method Overloading and type coercion
... but that shouldn't hold up a FPWD
RESOLUTION: Publish FPWD of Vibration API
<darobin> ACTION: Robin to publish Vibration FPWD [recorded in http://www.w3.org/2011/11/16-dap-minutes.html#action01]
<trackbot> Created ACTION-488 - Publish Vibration FPWD [on Robin Berjon - due 2011-11-23].
fjh: I'm away next week, darobin please arrange for next week + publication
<fjh> DAP API Requirements - http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/0027.html
<fjh> System information - http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/0028.html
<fjh> Messaging API - http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/0029.html
<fjh> Gallery API - http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/0035.html
<fjh> Suggested change to warning text: http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/0123.html (Frederick)
<fjh> discussion re system information.
<fjh> proposed RESOLUTION: Update status of editors drafts to indicate shelving, for DAP API Requirements, System Information, Messaging, Gallery APIs and update Roadmap to move to archived section.
darobin: I'm going to tweak the Shelving proposal on jcantera's input
Claes: I'm reading the new warning text here
... I have a comment on the Gallery API
<AnssiK> +1 to shelve all the above
Claes: If we shelve that API, I need to know what that means
... We have work based on it
... If we shelve it, can we reopen it at any time?
darobin: definitely
... we have a problem, we've published a bunch of documents
... some we're currently working on
... some which we haven't worked on recently
<fjh> if shelved we note the document should not be used, we aren't working on it, but we can always resume the work etc
darobin: there's a certain amount of confusion about what we're doing
... among people outside the WG
... some of our documents haven't had a refresh because we haven't reached a newer conclusion
... With shelving, we're just adding a Warning that it's not our current belief
... we can at a later time remove the shelving warning
... either updating the document to a new view
... or having decided we like the view as published
Claes: so for Webinos
... if we have input
<fjh> shelving is not a charter change
darobin: everything in the Charter, if we have new input
... we can continue working on at any time
fjh: It's just about making clear what's going on
... There's been discussion about SysInfo as well
... But i'd suggest we do this for now
darobin: I'd suggest we go ahead and do it
<fjh> proposed RESOLUTION: Update status of editors drafts to indicate shelving, for DAP API Requirements, System Information, Messaging, Gallery APIs and update Roadmap to move to archived section.
darobin: it's reversible
Deepanshu: I have concerns about shelving Device API Requirements
... it would be fine if we could have what is discussed in this warning text
... this warning text implies that this document can be taken up in future
... but I have been told that the group has decided not to revise that Document
... so the Warning text for the Requirements document should be changed to address that
<AnssiK> [ I think that for requirements gathering wiki might work better ]
darobin: We said that the Warning text should be specific to the individual shelved documents
<Zakim> Josh_Soref, you wanted to speak on shelving text
<darobin> ACTION: Robin to prepare Requirements, SysInfo, Messaging, Gallery for shelving (wait for text from Deepanshu for Reqs) [recorded in http://www.w3.org/2011/11/16-dap-minutes.html#action02]
<trackbot> Created ACTION-489 - Prepare Requirements, SysInfo, Messaging, Gallery for shelving (wait for text from Deepanshu for Reqs) [on Robin Berjon - due 2011-11-23].
Josh_Soref: I spoke with Suresh, will also try to suggest text
<darobin> ACTION-489: wait for text from Josh, include input from Jose and Frederick
<trackbot> ACTION-489 Prepare Requirements, SysInfo, Messaging, Gallery for shelving (wait for text from Deepanshu for Reqs) notes added
<fjh> proposed RESOLUTION: Update status of editors drafts to indicate shelving, for DAP API Requirements, System Information, Messaging, Gallery APIs and update Roadmap to move to archived section.
darobin: I need to coordinate with w3 communications so that we don't get Announced for these documents
fjh: I'd agree it's best that we don't Announce
<dom> no, wonsuk was arguing for integrating requirements in each spec, to make it easier for the reader
<darobin> +1 to Wonsuk
fjh: there's a Draft Charter
... we're just waiting for the mailing list to be created
... dom, do you know its status?
<fjh> draft charter, http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/0054.html
dom: I don't
... I think shepazu is in charge of this
... but he's at the W3C conference right now
... there was some concern about the Naming
... and there was a concern about naming
darobin: in terms of naming, I think that ship has sailed
... we'll just have a mailing list
... i'd rather not use the same system as used for public-device-status
... it was rather buggy last time around
<fjh> need a task force for IPR obligations
dom: there's an issue of who is Formally a Member of the TF
... we want an open mailing list where anyone can subscribe
darobin: We can track who contributed
... by following the mailing list
... and seeing who has made the IPR commitments
... in the same way we track the DAP public mailing list
dom: so ok with just having a mailing list?
darobin: if there are big concerns, we can do something else
... but I don't see how this is different from DAP's public mailing list or WebApps, etc.
fjh: I'll talk w/ shepazu
darobin: I don't know that there's much to talk about beyond that
<Zakim> Josh_Soref, you wanted to talk about delays
Josh_Soref: I'm concerned about delays and cross-posting, so wants this to be done quickly
darobin: we all agree
<darobin> http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/0058.html
<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/0058.html
<darobin> http://scriptlib-cg.github.com/api-design-cookbook/
fjh: darobin, I know you've worked on this
... i don't know if there's much more to do
darobin: this has been done openly on GitHub
<darobin> https://github.com/scriptlib-cg/api-design-cookbook
darobin: if you want changes made to it, you just clone from the repository
... make your changes
... and make a pull request
... and then i'll integrate them
... it's handled like a regular open source project
... it's like a Cook Book
... and not a BBB
... The idea is to help people writing APIs inside or outside of W3C
... to be able to refer to this document
... to find best practices
... input is welcome
... preferably in the form of patches
... but otherwise as well
... Two sections have been fleshed out
... but others are coming
fjh: AnssiK, where are we?
<wonsuk> To make clear our specs, an requirement part should be included to the each spec to make it easier for the reader. In addition to make a consistency among requirement and other parts of the spec.
AnssiK: last time we discussed the topic at the F2F
... the only remaining issue was the Threshold feature
... spoussa sent a proposal
... it was discussed on the mailing list
... we found out that we don't have a design that meets the quality requirements
... so we're going to push it to v2
... given that, we're ready for CfC to LC
... so we can iron out any last bits
... I'd like to note that this is shipping in Firefox 10 (Aurora)
... so you can grab that
<fjh> +1 to CfC for Last Call
<darobin> [that will only work on Android or Linux]
AnssiK: that's about it
<spoussa> +1
<AnssiK> +1 to CfC for Last Call
<wonsuk> +1
fjh: dom / darobin : any concerns about CfC to LC?
darobin: not at all
fjh: let's do this
... AnssiK, can you do the paper/prep work for LC?
AnssiK: I haven't done it, but i'm willing to learn
darobin: sure, we can help you
... I'll do the CfC
fjh: great
<darobin> ACTION: Robin to CfC Battery LC [recorded in http://www.w3.org/2011/11/16-dap-minutes.html#action03]
<trackbot> Created ACTION-490 - CfC Battery LC [on Robin Berjon - due 2011-11-23].
fjh: there's a demo online
... i'm not sure what else is new
<fjh> discovery demo online, http://lists.w3.org/Archives/Public/public-device-apis/2011Nov/0085.html
fjh: i don't know if Clarke is on the call
... i don't know if there's anything to discuss
darobin: I don't think so
... a lot of the action has been around Intents
... and Battery and Vibration
... before the call, I sent a draft of a Media Capture TF charter
<darobin> http://www.w3.org/mid/22C84B78-685C-4B6F-85E4-A12BC073D075@berjon.com
darobin: another Joint TF
... we're trying to get that off the ground quickly
<fjh> regrets from me for next week
darobin: The WebRTC people want to get it out early next year
fjh: darobin, can you send out the agenda for next week?
... thanks Josh_Soref for scribing
[ Adjourned ]