W3C home > Mailing lists > Public > public-device-apis@w3.org > April 2010

Draft minutes 2010-04-21

From: Frederick Hirsch <frederick.hirsch@nokia.com>
Date: Wed, 21 Apr 2010 10:56:35 -0400
Message-Id: <F404ACC9-D634-48F6-8B96-76612F62CA10@nokia.com>
To: W3C Device APIs and Policy WG <public-device-apis@w3.org>
Cc: Frederick Hirsch <frederick.hirsch@nokia.com>
Enclosed are draft minutes from 2010-04-21 teleconference. HTML  
follows text. Thanks to Claes for scribing.

regards, Frederick

Frederick Hirsch

# Device APIs and Policy Working Group Teleconference

## 21 Apr 2010


See also: [IRC log][4]

## Attendees


    Robin_Berjon, Frederick_Hirsch, Dzung_Tran, Wonsuk_Lee, Max_Froumentin,
Alissa_Cooper, Suresh_Chitturi, Ilkka_Oksanen, Claes_Nilsson,
Dominique_Hazael-Massieux, DanielColoma, Anssi_Kostiainen, Maria_Oteo


    John_Morris, Marco_Marengo, Laura__Arribas, David_Rogers, Marcin_Hanclik,


    Robin_Berjon, Frederick_Hirsch



## Contents

  * [Topics][5]

    1. [Administrative][6]

    2. [Minutes approval][7]

    3. [Policy discussion][8]

    4. [APIs][9]

  * [Summary of Action Items][10]

* * *

<trackbot> Date: 21 April 2010

### Administrative

<scribe> scribenick: Claes

IRC web client updated. New link at DAP page

<fjh> web based IRC client updated [http://lists.w3.org/Archives/Member

### Minutes approval

<fjh> [http://lists.w3.org/Archives/Public/public-device-

**RESOLUTION: April 14 Minutes approved**

### Policy discussion

<fjh> Privacy rulesets

Alissa: Fine for WD ?

<fjh> Editorial update - ReSpec conversion

Fjh: Wants policy req and ruleset as WD simultaneously

... still some actions on Alissa and John on priv reqs

<fjh> alissa asks if we need to clarify rulesets before FPWD of policy

<fjh> I suggest we try to have FPWD of both privacy requirements and policy
rulesets at same time, ask that focus now on actions related to privacy

<fjh> action-153?

<trackbot> ACTION-153 -- Alissa Cooper to refine privacy requirements (with
John) -- due 2010-04-07 -- OPEN

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

<fjh> action-158?

<trackbot> ACTION-158 -- John Morris to send proposed changes to list re
privacy requirements -- due 2010-04-14 -- OPEN

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

<fjh> action-112?

<trackbot> ACTION-112 -- Alissa Cooper to separate privacy requirements on UA
from other privacy requirements (on APIs, for user policies, and for best
practices for recipients) -- due 2010-03-23 -- OPEN

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

<fjh> alissa notes privacy requirements on APIs versus UA requirements

Need to define how ruleset is used, not API specific req

<fjh> action-112 closed

<trackbot> ACTION-112 Separate privacy requirements on UA from other privacy
requirements (on APIs, for user policies, and for best practices for
recipients) closed

<fjh> Privacy section for API documents

<fjh> action-116?

<trackbot> ACTION-116 -- Bryan Sullivan to provide input on DCO mapping for
SysInfo -- due 2010-03-24 -- OPEN

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

<darobin> [I note that the editors for the privacy requirements document
aren't the right ones]

<fjh> Phrase the temporary privacy section

<fjh> action-130?

<trackbot> ACTION-130 -- Richard Tibbett to propose changes to calendar
specification to address privacy minimization -- due 2010-03-24 -- OPEN

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

fjh: FPWD early next month

<fjh> Richard is starting with contacts should be applicable to calendar

Rich: Dealing with "Privacy by design section in contacts. Needs to be dealt
with also in cal

### APIs

Dom: Wants not to bundle policy reqs and rule set

<fjh> goal is to let people know of rulesets and approach

Dom: suggests to publich privacy reqs when done

fjh: Wants to get peoples attention and feedback

<darobin> [feedback from the TAG?]

<fjh> dom suggests getting feedback from html cg, webapps and internally in WG
first before FPWD

<fjh> dom notes requirements doc can link to rulesets doc

fjh: Have a problem with publish a req doc with issues and no proposal for a

... Focus more on privacy doc

<fjh> alissa notes need stated requirements on retention, secondary use


<fjh> [http://lists.w3.org/Archives/Public/public-device-

<dom> [Last week discussions on messaging][20]

Discussion on publishing

<Zakim> dom, you wanted to say he doesn't think we've addressed his concern
about scoping

Darobin: Suggest moving Messaging to FPWD

<dom> ACTION-161?

<trackbot> ACTION-161 -- Max Froumentin to make a proposal for Message
Management, including whether it would be split from the main spec or not --
due 2010-04-21 -- OPEN

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

<fjh> suresh asks about supporting inspection, is it the same as message

<fjh> robin notes yes

Suresh: Message (folder) managment to be included before FPWD?

Suresh suggests that we should wait until Max has made a proposal for message

<fjh> s/fjh: Topic APIs//

Max: Ok

Daniel: Feedback from Bondi: Decided to merge messaging API and folder

<darobin> ACTION daniel to email the list explaining the differences between
the successive BONDI approaches to messaging, and why the functionality got
merged into a single API

<trackbot> Created ACTION-164 - Email the list explaining the differences
between the successive BONDI approaches to messaging, and why the
functionality got merged into a single API [on Daniel Coloma - due

<fjh> Timezoned dates - [http://lists.w3.org/Archives/Public/public-device-

Calendar Time zones and dates

<dom> (I prefer solution #2 in Richard's summary, but then, that's my proposal
:) )

<fjh> didn't we decide earlier that we wanted to be REST compatible in our

Rich: Two proposals. Need decsion. Blocking cal API.

... Needs feedback on preferred solution.

<dom> [this relates to ISSUE-81]

<dom> (there is more than end and start; recurrence rules, for instance)

<dom> [http://lists.w3.org/Archives/Public/public-device-

Rich: 3rd option, Rich can you state this in IRC?

<darobin> [I agree with Dom's feedback on this one]

<Zakim> dom, you wanted to say we should strive to make developers' life
easier, rather than implementers or ourselves

<Suresh> Suresh: A 3rd proposal would be to specify a tz attribute in the
Event interface

Dom: We should make a solution that is easier for developers

<darobin> "In case of conflict, consider users over authors over implementors
over specifiers over theoretical purity."

<darobin> [][24]

Rich: Provide feedback on list

fjh: Implications on a RESTful approach?

Darobin: Not a big deal

<dom> (and bring it to public-script-coord as well)

Darobin: Suggest put a draft up wth option 2 and get feedbac

<dom> [public-script-coord@w3.org Mail Archives][25]

<darobin> ACTION Robin to take the TZDate discussion to public-script-coord

<trackbot> Created ACTION-165 - Take the TZDate discussion to public-script-
coord [on Robin Berjon - due 2010-04-28].

<dom> ACTION-163?

<trackbot> ACTION-163 -- Robin Berjon to email i18n about the various options
for calendaring -- due 2010-04-21 -- OPEN

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

Blocking factors for Cal is timezone issues and internatioization (Gregorian

File Writer

<dom> [storage for Web APIs][27]

Dom: Long disc in Web Apps on storage for web apps. Also aplicable for File

<richt> [calendar] My understanding is that blocking for calendar API is
TimezonedDate object, expressing i18n dates/times and fixing the recurrence


<richt> [calendar] non-blocking issue is to address minimization in the draft

<fjh> Thanks for scribing Claes.

## Summary of Action Items

[End of minutes]

* * *

Minutes formatted by David Booth's [scribe.perl][28] version 1.135 ([CVS

$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-

   [4]: http://www.w3.org/2010/04/21-dap-irc

   [5]: #agenda

   [6]: #item01

   [7]: #item02

   [8]: #item03

   [9]: #item04

   [10]: #ActionSummary

   [11]: http://lists.w3.org/Archives/Member/member-device-

   [12]: http://lists.w3.org/Archives/Public/public-device-

   [13]: http://lists.w3.org/Archives/Public/public-device-

   [14]: http://www.w3.org/2009/dap/track/actions/153

   [15]: http://www.w3.org/2009/dap/track/actions/158

   [16]: http://www.w3.org/2009/dap/track/actions/112

   [17]: http://www.w3.org/2009/dap/track/actions/116

   [18]: http://www.w3.org/2009/dap/track/actions/130

   [19]: http://lists.w3.org/Archives/Public/public-device-

   [20]: http://lists.w3.org/Archives/Public/public-device-

   [21]: http://www.w3.org/2009/dap/track/actions/161

   [22]: http://lists.w3.org/Archives/Public/public-device-

   [23]: http://lists.w3.org/Archives/Public/public-device-

   [24]: http://www.w3.org/TR/html-design-principles/#priority-of-

   [25]: http://lists.w3.org/Archives/Public/public-script-coord/

   [26]: http://www.w3.org/2009/dap/track/actions/163

   [27]: http://lists.w3.org/Archives/Public/public-

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

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

Received on Wednesday, 21 April 2010 14:57:16 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 14:53:43 UTC