W3C

- DRAFT -

Device APIs and Policy Working Group Teleconference

12 Jan 2011

Agenda

See also: IRC log

Attendees

Present
Frederick_Hirsch, Robin_Berjon, Rich_Tibbett, Cecile_Marc, Dong-Young_Lee, Kyung-Tak_Lee, Suresh_Chitturi, jerome_giraud, Claes_Nilsson, arun_prasath, Maria_Oteo, Anssi_Kostiainen, Dzung_Tran, Daniel_Coloma, Dom
Regrets
John_Morris
Chair
Frederick_Hirsch, Robin_Berjon
Scribe
claes

Contents

<trackbot> Date: 12 January 2011

<fjh> trackbot-ng, start telecon

<trackbot> Meeting: Device APIs and Policy Working Group Teleconference

<trackbot> Date: 12 January 2011

<fjh> http://lists.w3.org/Archives/Member/member-device-apis/2011Jan/0002.html

<fjh> seoul logistics avaiable

<fjh> ScribeNick: claes

Administrative

Minutes

<fjh> Approve 5 January minutes

<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Jan/att-0014/minutes-2011-01-05.html

RESOLUTION: 5 January minutes approved

Access Control Requirements

<fjh> update, http://lists.w3.org/Archives/Public/public-device-apis/2011Jan/0020.html

PROPOSED RESOLUTION: Publish Access Control Requirements

RESOLUTION: Publish Access Control Requirements

Web Introducer

<fjh> Services Discovery and Permissions - "Web Introducer"

<fjh> http://lists.w3.org/Archives/Public/public-device-apis/2011Jan/0016.html (Tyler)

<fjh> prototyping, http://lists.w3.org/Archives/Public/public-device-apis/2011Jan/0021.html

Encourage people to read the Web Introducer specification and check the web site

Messaging

<fjh> dom notes that messaging could be layer on URI schemes, thus changing the scope of messaging

<fjh> dom notes however that change in scope not yet clear

<fjh> we need a concrete proposal on the list

<fjh> dom notes can defer uri scheme aspect, but update direction

<fjh> can that be sotd

Dom: 2 aspects, how to tie with URI schemes? send clear message where we are going

Dom proposes not to publish until document it clearer in terms of our direction with this API

<fjh> ACTION: fjh to prepare access reqmts for publishing, pubrules etc [recorded in http://www.w3.org/2011/01/12-dap-minutes.html#action01]

<trackbot> Created ACTION-324 - Prepare access reqmts for publishing, pubrules etc [on Frederick Hirsch - due 2011-01-19].

<fjh> ok with publishing early and often

<AnssiK> +1 to Rich's proposal

Rich: Prefere not to publish until clearer

<fjh> rich would like not to publish, remove dependency on permissions

Rich: we can publish but prefer a better specification before this

<fjh> dom offers to make changes over the next week, allowing publication next week

Dom: Give another week to give time for scope etc clarifications
... wants to clarify security considerations in relation to URI schemes

Daniel: Agree with Suresh.

Suresh: Clarify scope ok but not major changes

<fjh> ACTION: dom to update Messaging to clarify security considerations and URI schemes [recorded in http://www.w3.org/2011/01/12-dap-minutes.html#action02]

<trackbot> Created ACTION-325 - Update Messaging to clarify security considerations and URI schemes [on Dominique Hazaël-Massieux - due 2011-01-19].

RESOLUTION: Dom updates on scope etc and postpone publication until next week

Contacts

<fjh> updates, http://lists.w3.org/Archives/Public/public-device-apis/2011Jan/0018.html

<fjh> message from Anssi, http://lists.w3.org/Archives/Public/public-device-apis/2011Jan/0031.html

Rich: Have difficulties interpreting Rich

<fjh> suresh is concerned about not having a clear javascript api

Rich: so missed to document discussion

<fjh> richt notes that can use other approaches beyond javascript api

<fjh> richt suggests using existing web framework

Rich:

IRC problems but back again

<richt> Suresh, my key question is: for adding and updating contacts, why do we need a programmatic API rather than reusing the existing web platform?

Fjh: Suresh, please document your issues in the chat or in a mail

<richt> ...we need new content on this subject. We've got a JS API. It kills the user experience. Please assume policy and permissioning is not possible.

Suresh: I willsend an e-mail on the Contacts API issues.

Calendar

Rich: Aligned with Contacts API done

<richt> Suresh, please put your thoughts in an email on the Contact API Adding and Updating contacts.

Rich: optimizations
... feedback appreciated

Suresh: Have looked at it and have proposed changes

<fjh> Updated draft available, suresh has additional proposed changes. Will work with Rich offline

<fjh> note - due to IRC issues part of chat transcript was apparently lost.

Adjourn

Summary of Action Items

[NEW] ACTION: dom to update Messaging to clarify security considerations and URI schemes [recorded in http://www.w3.org/2011/01/12-dap-minutes.html#action02]
[NEW] ACTION: fjh to prepare access reqmts for publishing, pubrules etc [recorded in http://www.w3.org/2011/01/12-dap-minutes.html#action01]
 
[End of minutes]
Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2011/01/12 16:16:08 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/weher/weher/
Succeeded: s/weher/where/
Succeeded: s/calrify/clarify/
Succeeded: s/Present?//
Succeeded: s/(+33)//
Succeeded: s/i'll call back//
Succeeded: s/Sorry, had IRC problems and had to reload IRC//
Succeeded: s/it can't be MaxF//
Succeeded: s/0299 12 is cmarc//
Succeeded: s/docuemnt/document/
Found ScribeNick: claes
Inferring Scribes: claes
Present: Frederick_Hirsch Robin_Berjon Rich_Tibbett Cecile_Marc Dong-Young_Lee Kyung-Tak_Lee Suresh_Chitturi jerome_giraud Claes_Nilsson arun_prasath Maria_Oteo Anssi_Kostiainen Dzung_Tran Daniel_Coloma Dom
Regrets: John_Morris
Agenda: http://lists.w3.org/Archives/Public/public-device-apis/2011Jan/0022.html
Found Date: 12 Jan 2011
Guessing minutes URL: http://www.w3.org/2011/01/12-dap-minutes.html
People with action items: dom fjh
[End of scribe.perl diagnostic output]