# Device APIs and Policy Working Group Teleconference

## 09 Feb 2011

[Agenda][3]

See also: [IRC log][4]

## Attendees

Present

    Robin_Berjon, Frederick_Hirsch, Anssi_Kostiainen, Dominique_Hazael-
Massieux, Niklas_Widell, Rich_Tibbett, Dzung_Tran, Claes_Nilsson,
Manyoung_Cho, Ingmar_Kliche, Laszlo_Gombos

Regrets

    Suresh_Chitturi, Dong-Young_Lee, Marengo_Marco, John_Morris, Cécile_Marc

Chair

    Robin_Berjon, Frederick_Hirsch

Scribe

    Laszlo

## Contents

  * [Topics][5]

    1. [Administrative][6]

    2. [Minutes Approval][7]

    3. [Contacts][8]

    4. [Messaging][9]

    5. [gallery][10]

    6. [Calendar][11]

    7. [Privacy][12]

  * [Summary of Action Items][13]

* * *

<trackbot> Date: 09 February 2011

### Administrative

<fjh> Will also include last week's agenda,
[http://lists.w3.org/Archives/Public/public-device-apis/2011Feb/0002.html][14]

<dom> [our charter says "To be successful, this Working Group is expected to
have 10 or more active participants for its duration, and to have the
participation of the industry leaders in fields relevant to the specifications
it produces. "]

<darobin> can we close down and declare victory?

<manyoung> I think so

<fjh> Seoul F2F and workshop planning

<fjh> please complete registration page, [http://www.w3.org/2002/09/wbs/43696
/seoul-f2f-reg/][15]

<fjh> UK/French dial in access; calling zakim via voip,
[http://lists.w3.org/Archives/Member/member-device-apis/2011Feb/0000.html][16]

<fjh> Messaging API draft update published, see [http://www.w3.org/TR/2011/WD-
messaging-api-20110120/][17]

<fjh> Web Introducer prototype update, [http://lists.w3.org/Archives/Public
/public-device-apis/2011Jan/0096.html][18] (Claes)

<darobin> Scribe: Laszlo

<darobin> ScribeNick: lgombos

<fjh> TAG on minimization

<fjh> [http://www.w3.org/2001/tag/2011/02/08-agenda.html#apis][19] (Draft TAG
minimization draft)

<fjh> [http://lists.w3.org/Archives/Public/www-tag/2011Feb/0059.html][20]
(comment, Frederick)

<fjh> implementer feedback? [http://lists.w3.org/Archives/Public/public-
device-apis/2011Feb/0020.html][21]

<fjh> "Mobile Develop for Privacy Challenge"

<fjh> [http://lists.w3.org/Archives/Public/www-tag/2011Feb/0067.html][22]

### Minutes Approval

<fjh> Approve 2 February minutes

<fjh> [http://lists.w3.org/Archives/Public/public-device-
apis/2011Feb/att-0037/minutes-2011-02-02.html][23]

**RESOLUTION: Minutes from 2 February 2011 approved.**

### Contacts

<fjh> Draft updated, [http://lists.w3.org/Archives/Public/public-device-
apis/2011Jan/0091.html][24]

<fjh> clarification of non-supported field vs empty array,
[http://lists.w3.org/Archives/Public/public-device-apis/2011Feb/0027.html][25]

<fjh> variety of scripting approaches to contact interface invocation,
[http://lists.w3.org/Archives/Public/public-device-apis/2011Feb/0018.html][26]

richt: Feedback collected from list, will put in the spec in the next few days

fjh: timeframe ?

<dom> AFAIK, the obstacles to Last Call are utcOffset issue (ISSUE-106), and
defining PendingOp (in Core device or elsewhere)

<dom> ISSUE-106?

<trackbot> ISSUE-106 -- Does Contacts API having a timezone field make sense,
should it be utfOffset or utcOffset and tz to better match vCard? -- open

<trackbot> [http://www.w3.org/2009/dap/track/issues/106][27]

<fjh> plan to publish updated public working draft soon?

<Zakim> AnssiK, you wanted to ask about ContactName.formatted and
ContactAddress.formatted

AnssiK: what is formatted fields are for ?

richt: get the full contact in a single string

<fjh> Using agenda from last week at this point -
[http://lists.w3.org/Archives/Public/public-device-apis/2011Feb/0002.html][14]
.

<fjh> ISSUE-106?

<trackbot> ISSUE-106 -- Does Contacts API having a timezone field make sense,
should it be utfOffset or utcOffset and tz to better match vCard? -- open

<trackbot> [http://www.w3.org/2009/dap/track/issues/106][27]

<Zakim> dom, you wanted to respond

<fjh> using terms family name, given is clearer that first last,
internationally?

<dom> dom: formattedName allows to take into account that depending on
countries you would address someone with "familyName givenName" and not with
"givenName familyName"

<dom> ... so doesn't duplicate info, adds an additional bit, important I18N-
wise

<richt> [http://dev.w3.org/2009/dap/contacts/#search-cardinality][28]

<dom> [I wonder how we're planning to make progress on ISSUE-106: any
volunteer to draft a proposal to resolve that issue?]

<darobin> [right, I'd like people to take actions and go do them :)]

<darobin> [and if that includes someone other than I doing PendingOp, it's
even nicer]

<dom> **ACTION:** Richard to draft a proposal for utcOffset based on mailing
list feedback (re ISSUE-106) [recorded in [http://www.w3.org/2011/02/09-dap-
minutes.html#action01][29]]

<trackbot> Created ACTION-333 - Draft a proposal for utcOffset based on
mailing list feedback (re ISSUE-106) [on Richard Tibbett - due 2011-02-16].

<fjh> **ACTION:** richt to propose resolution for ISSUE-106 [recorded in
[http://www.w3.org/2011/02/09-dap-minutes.html#action02][30]]

<trackbot> Created ACTION-334 - Propose resolution for ISSUE-106 [on Richard
Tibbett - due 2011-02-16].

<dom> ACTION-334: dup of ACTION-333

<trackbot> ACTION-334 Propose resolution for ISSUE-106 notes added

<dom> close ACTION-334

<trackbot> ACTION-334 Propose resolution for ISSUE-106 closed

<Zakim> AnssiK, you wanted to comment on Search Qualifiers: when zero-length,
returns nothing or array of empty objects (having length of matched objects)?
and to

<fjh> anssi asks about extended properties

AnssiK: what is the difference between MUST and SHOULD

richt: we can try MUST

... SHOULD is just a guideline, MUST would be better

<AnssiK> [http://dev.w3.org/2009/dap/contacts/#extended-contact-properties-
and-parameters][31]

AnssiK: what about other DAP specs ?

<fjh> ISSUE: should Contacts API have MUST instead of SHOULD for extended
attributes, is this a general issue for all specs?

<trackbot> Created ISSUE-108 - Should Contacts API have MUST instead of SHOULD
for extended attributes, is this a general issue for all specs? ; please
complete additional details at
[http://www.w3.org/2009/dap/track/issues/108/edit][32] .

<fjh> laszlo notes Optionally can extend spec, but if you do you must do it a
certain way

<fjh> +1 to that approach

<dom> [I suggest using the same approach/wording other specs do this, e.g. the
CSS specs]

<darobin> +1 to using the same wording as elsewhere

<fjh> [http://lists.w3.org/Archives/Public/public-device-
apis/2011Jan/0106.html][33]

<Zakim> darobin, you wanted to PendingOp

darobin: We do not have a device and servcie object spec

... what about navigator.contacts instead of navigator.service.contact ?

richt: finds cool that one could cancel a pending op

darobin: could be confusing of a picker is cancelled/discarded programatically

lgombos: PendingOp only usefull if HW resources are involved

**RESOLUTION: remove PendingOp from Contacts**

<fjh> proposed RESOLUTION: remove PendingOp from Contacts

<richt> could we have navigator.contact (minus the 's')

<richt> or do we want the 's' (and do we really want to bikeshed ;))

<darobin> [that's bikeshedding, pick whichever :)]

**RESOLUTION: use navigator.contact in Contacts (no service object)**

<richt> done.

### Messaging

fjh: Need to discuss how to move forward given new approach, also determine
interest of current editors, discuss further on list.

<darobin> +1 to talking on the list, could bring people to the calls!

<richt> [http://lists.w3.org/Archives/Public/public-device-
apis/2011Jan/0105.html][34]

fjh: initiate discussion on the list to move this forward

richt: concerned about being specific about mms and sms

<darobin> [I look forward to using it with [http://xmpp.org/internet-
drafts/attic/draft-saintandre-xmpp-uri-01.html][35]]

### gallery

<fjh> [http://lists.w3.org/Archives/Public/public-device-
apis/2011Jan/0101.html][36]

<dom> ACTION-314?

<trackbot> ACTION-314 -- Anssi Kostiainen to react on media gallery use cases
-- due 2010-12-15 -- OPEN

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

darobin: Connected Media Experience people are interested ..

### Calendar

<fjh> edits to align with Contacts, comments

<fjh> [http://lists.w3.org/Archives/Public/public-device-
apis/2011Feb/0001.html][38]

### Privacy

<fjh> Mozilla, "Do Not Track", [http://lists.w3.org/Archives/Public/public-
device-apis/2011Jan/0095.html][39]

<fjh> Microsoft, [http://lists.w3.org/Archives/Public/public-device-
apis/2011Jan/0100.html][40]

<fjh> Ruleset issue questions, [http://lists.w3.org/Archives/Public/public-
device-apis/2011Jan/0097.html][41]

<fjh> [http://lists.w3.org/Archives/Public/public-device-
apis/2011Feb/0000.html][42]

<dom> (regrets for next week - will be at MWC)

## Summary of Action Items

**[NEW]** **ACTION:** Richard to draft a proposal for utcOffset based on
mailing list feedback (re ISSUE-106) [recorded in
[http://www.w3.org/2011/02/09-dap-minutes.html#action01][29]]

**[NEW]** **ACTION:** richt to propose resolution for ISSUE-106 [recorded in
[http://www.w3.org/2011/02/09-dap-minutes.html#action02][30]]


[End of minutes]

* * *

Minutes formatted by David Booth's [scribe.perl][43] version 1.135 ([CVS
log][44])

$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-
apis/2011Feb/0045.html

   [4]: http://www.w3.org/2011/02/09-dap-irc

   [5]: #agenda

   [6]: #item01

   [7]: #item02

   [8]: #item03

   [9]: #item04

   [10]: #item05

   [11]: #item06

   [12]: #item07

   [13]: #ActionSummary

   [14]: http://lists.w3.org/Archives/Public/public-device-
apis/2011Feb/0002.html

   [15]: http://www.w3.org/2002/09/wbs/43696/seoul-f2f-reg/

   [16]: http://lists.w3.org/Archives/Member/member-device-
apis/2011Feb/0000.html

   [17]: http://www.w3.org/TR/2011/WD-messaging-api-20110120/

   [18]: http://lists.w3.org/Archives/Public/public-device-
apis/2011Jan/0096.html

   [19]: http://www.w3.org/2001/tag/2011/02/08-agenda.html#apis

   [20]: http://lists.w3.org/Archives/Public/www-tag/2011Feb/0059.html

   [21]: http://lists.w3.org/Archives/Public/public-device-
apis/2011Feb/0020.html

   [22]: http://lists.w3.org/Archives/Public/www-tag/2011Feb/0067.html

   [23]: http://lists.w3.org/Archives/Public/public-device-
apis/2011Feb/att-0037/minutes-2011-02-02.html

   [24]: http://lists.w3.org/Archives/Public/public-device-
apis/2011Jan/0091.html

   [25]: http://lists.w3.org/Archives/Public/public-device-
apis/2011Feb/0027.html

   [26]: http://lists.w3.org/Archives/Public/public-device-
apis/2011Feb/0018.html

   [27]: http://www.w3.org/2009/dap/track/issues/106

   [28]: http://dev.w3.org/2009/dap/contacts/#search-cardinality

   [29]: http://www.w3.org/2011/02/09-dap-minutes.html#action01

   [30]: http://www.w3.org/2011/02/09-dap-minutes.html#action02

   [31]: http://dev.w3.org/2009/dap/contacts/#extended-contact-properties-and-
parameters

   [32]: http://www.w3.org/2009/dap/track/issues/108/edit

   [33]: http://lists.w3.org/Archives/Public/public-device-
apis/2011Jan/0106.html

   [34]: http://lists.w3.org/Archives/Public/public-device-
apis/2011Jan/0105.html

   [35]: http://xmpp.org/internet-drafts/attic/draft-saintandre-xmpp-
uri-01.html

   [36]: http://lists.w3.org/Archives/Public/public-device-
apis/2011Jan/0101.html

   [37]: http://www.w3.org/2009/dap/track/actions/314

   [38]: http://lists.w3.org/Archives/Public/public-device-
apis/2011Feb/0001.html

   [39]: http://lists.w3.org/Archives/Public/public-device-
apis/2011Jan/0095.html

   [40]: http://lists.w3.org/Archives/Public/public-device-
apis/2011Jan/0100.html

   [41]: http://lists.w3.org/Archives/Public/public-device-
apis/2011Jan/0097.html

   [42]: http://lists.w3.org/Archives/Public/public-device-
apis/2011Feb/0000.html

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

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