RE: Agenda - Distributed Meeting 2010-12-14

Regrets due to travel...


-----Original Message-----
[] On Behalf Of
Sent: Tuesday, December 14, 2010 4:27 PM
Subject: Agenda - Distributed Meeting 2010-12-14

Agenda - Device APIs and Policy Working Group - Distributed Meeting  #48

Meeting details at the bottom of this email.

1) Welcome, agenda review, scribe selection
* Note any additions or changes to agenda
* Select scribe: <>

2) Announcements, meeting planning, logistics

2a)  new WD of the Contacts API spec published -

2b) no meeting 22, 29 December. Next meeting 5 January,

3) Minutes approval

Approve 8 December minutes

proposed RESOLUTION: Minutes from 8 December 2010 approved

4) Permissions

4a) Permission for pop-up windows,
(Tim Allen)

4b) Next step for Feature Permissions (from Notification WG)

5) Contacts 

5a) Contacts & Timezones

5b) Contact Blob Writer

6) Media Capture - HTML5 role attribute

7) Gallery Use Cases

8) Messaging API

9) Action and Issue review

9a) Pending actions - closed without discussion unless concern raised.

ACTION-306   Review Contact Blob writer proposal ; Dom

9b) Open Action review

Please review your actions at

When completed change status to "Pending" and send email to public list
indicating conclusion, as well as referencing ACTION-nnn in email (for

ACTION-86 Update Core Devices	Robin Berjon	2010-01-27

ACTION-104 Domain spoofing in network layer ; David Rogers; 2010-03-17

ACTION-130 Propose changes to calendar specification to address privacy
minimization	Richard Tibbett	2010-10-22

ACTION-145 Provide an architectural flow for Policy Reqs	Bryan
Sullivan	2010-03-25	Policy Framework Requirements

ACTION-148 Compare user interaction input with what already available in
HTML5 / WebApps	Bryan Sullivan	2010-03-25	User Interaction API

ACTION-150 Send BONDI experience with testing for device APIs	David
Rogers	2010-03-25

ACTION-173 Implement privacy changes noted by alissa, see
Dzung Tran	2010-05-26	hidingIsHard

ACTION-181 to review API and Ontology for Media Resource API	Bryan
Sullivan	2010-07-07	Gallery API

ACTION-188 Propose clarification language around prompting, involving
Paddy and James as needed	Laura Arribas	2010-06-16	Policy
Framework Requirements

ACTION-200 Provide clarifications to framework document as well as to
address concerns raised by Suresh
Paddy Byers	2010-06-30	Policy Framework

ACTION-202 Include changes from ACTION-191
Dzung Tran	2010-06-30	System Information and Events API

ACTION-210 Summarize and add issues to ruleset doc	Alissa Cooper

ACTION-213 Review sysinfo draft after edits made	Dong-Young Lee
2010-07-21	System Information and Events API

ACTION-214 Request IETF community review of sysinfo API Last Call WD
through W3C/IETF liaison channel	Thomas Roessler	2010-11-24

ACTION-218 Provide proposal for feature architecture text regarding web
and widgets cases for feature document	Paddy Byers	2010-07-21

ACTION-229 Go through and ensure the
bindings provided map	Richard Tibbett	2010-10-22	dataModelDiff

ACTION-230 Specify "add to calendar" based on ICS-objects opening
Wojciech Maslowski	2010-08-05	Calendar API

ACTION-231 Look into what he can share re javascript-based android
prototype of PowerBox	Claes Nilsson	2010-07-22	restfulAPIs

ACTION-232 Coordinate with Tyler on exposing Contacts through Powerbox
Robin Berjon	2010-08-05	restfulAPIs

ACTION-251 Review privacy text related to ISSUE-78 for capture	John
Morris	2010-10-2

9c) Issue review

ISSUE-72, close?
clarifying whether a JS API even makes sense when URI schemes have been
defined as an alternative mechanism for at least some of the technology.
Have determined JS APIs make sense in some cases.

10) AOB

11) Adjourn

Meeting Details:

Zakim Bridge: +1.617.761.6200, +, or +44.117.370.6152
Conference code: 3279 ("DAPW", or "EASY")
IRC channel: 

Instructions on meetings :

Attendance of WG members or at discretion of chairs.


This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

Received on Tuesday, 14 December 2010 22:53:42 UTC