14:42:14 <RRSAgent> RRSAgent has joined #dap
14:42:14 <RRSAgent> logging to http://www.w3.org/2010/02/10-dap-irc
14:42:16 <trackbot> RRSAgent, make logs world
14:42:16 <Zakim> Zakim has joined #dap
14:42:18 <trackbot> Zakim, this will be DAP
14:42:18 <Zakim> ok, trackbot; I see UW_DAP()10:00AM scheduled to start in 18 minutes
14:42:19 <trackbot> Meeting: Device APIs and Policy Working Group Teleconference
14:42:19 <trackbot> Date: 10 February 2010
14:42:48 <fjh> Chair: Robin_Berjon, Frederick_Hirsch
14:43:02 <fjh> Agenda: http://lists.w3.org/Archives/Public/public-device-apis/2010Feb/0050.html
14:44:49 <fjh> Regrets: David_Rogers, John_Morris
14:44:57 <fjh> Present: Robin_Berjon, Frederick_Hirsch
14:46:02 <fjh> Topic: Administrative, Agenda Review, Scribe selection
14:50:01 <Suresh> Suresh has joined #dap
14:53:13 <fjh> http://www.w3.org/2009/dap/victims-list.html
14:53:53 <arve> arve has joined #dap
14:55:02 <aguillou> aguillou has joined #dap
14:55:12 <Dzung_Tran> Dzung_Tran has joined #dap
14:55:18 <Dzung_Tran> Present+ Dzung_Tran
14:56:02 <aguillou> Present+ Aurelien_Guillou
14:56:46 <tlr> Present+ Thomas_Roessler
14:56:46 <fjh> Aurelien, you are not listed on the scribe list. Would you pls be able to scribe today?
14:57:49 <paddy> paddy has joined #dap
14:58:03 <marengo> marengo has joined #dap
14:58:04 <Suresh> Present+ Suresh_Chitturi
14:58:09 <Zakim> UW_DAP()10:00AM has now started
14:58:15 <Zakim> + +0208849aaaa
14:58:50 <Zakim> + +1.408.216.aabb
14:59:13 <tlr> zakim, call thoas-781
14:59:13 <Zakim> I am sorry, tlr; I do not know a number for thoas-781
14:59:15 <tlr> zakim, call thomas-781
14:59:15 <Zakim> ok, tlr; the call is being made
14:59:17 <Zakim> +Thomas
14:59:25 <Zakim> +??P10
14:59:34 <AnssiK> AnssiK has joined #dap
14:59:35 <paddy> present+ Paddy_Byers
14:59:41 <LauraA> LauraA has joined #dap
14:59:54 <Zakim> +??P12
14:59:57 <Zakim> + +358.504.86aacc
15:00:02 <darobin> Zakim, ??P12 is me
15:00:02 <Zakim> +darobin; got it
15:00:09 <Zakim> + +0472369aadd
15:00:15 <maxf> zakim, aadd is me
15:00:15 <Zakim> +maxf; got it
15:00:16 <Zakim> + +035850486aaee
15:00:26 <Zakim> +??P14
15:00:27 <Zakim> + +04610715aaff
15:00:31 <tlr> zakim, I am thomas
15:00:31 <Zakim> ok, tlr, I now associate you with Thomas
15:00:33 <fjh> zakim, ??P14 is me
15:00:33 <Zakim> +fjh; got it
15:00:34 <ilkka> Present+ Ilkka_Oksanen
15:00:38 <fjh> zakim, who is here?
15:00:38 <Zakim> On the phone I see +0208849aaaa, +1.408.216.aabb, Thomas, ??P10, darobin, +358.504.86aacc, maxf, +035850486aaee, +04610715aaff, fjh
15:00:39 <aguillou> aguillou: i'm not sure to be able to scribe today, as my english level is not very good.
15:00:42 <Zakim> On IRC I see LauraA, AnssiK, marengo, paddy, Dzung_Tran, aguillou, arve, Suresh, Zakim, RRSAgent, fjh, darobin, trackbot, tlr, blassey, dom, ilkka, Marcos, maxf
15:00:45 <AnssiK> zakim, aaee is me
15:00:47 <Zakim> +AnssiK; got it
15:00:55 <ilkka> zakim, aaee is me
15:00:55 <Zakim> sorry, ilkka, I do not recognize a party named 'aaee'
15:01:15 <AnssiK> Present+ Anssi_Kostiainen
15:01:17 <ilkka> zakim, aacc is me
15:01:17 <Zakim> +ilkka; got it
15:01:26 <fjh> zakim, who is here?
15:01:30 <Suresh> aabb is me
15:01:31 <Zakim> On the phone I see +0208849aaaa, +1.408.216.aabb, Thomas, ??P10, darobin, ilkka, maxf, AnssiK, +04610715aaff, fjh
15:01:34 <nwidell> nwidell has joined #dap
15:01:34 <Zakim> On IRC I see LauraA, AnssiK, marengo, paddy, Dzung_Tran, aguillou, arve, Suresh, Zakim, RRSAgent, fjh, darobin, trackbot, tlr, blassey, dom, ilkka, Marcos, maxf
15:01:47 <Zakim> + +0777541aagg
15:01:58 <Zakim> + +47.66.99.aahh
15:02:02 <arve> zakim, aahh is me
15:02:02 <Zakim> +arve; got it
15:02:14 <fjh> zakim, who is here?
15:02:14 <Zakim> On the phone I see +0208849aaaa, +1.408.216.aabb, Thomas, ??P10, darobin, ilkka, maxf, AnssiK, +04610715aaff, fjh, +0777541aagg, arve
15:02:16 <Zakim> On IRC I see nwidell, LauraA, AnssiK, marengo, paddy, Dzung_Tran, aguillou, arve, Suresh, Zakim, RRSAgent, fjh, darobin, trackbot, tlr, blassey, dom, ilkka, Marcos, maxf
15:02:19 <LauraA> zakim, +0777541aagg is LauraA
15:02:19 <Zakim> +LauraA; got it
15:02:32 <nwidell> zakim, aaff is me
15:02:32 <Zakim> +nwidell; got it
15:02:45 <Suresh> +1.408.216.aabb is Suresh
15:03:22 <darobin> zakim, aabb is Suresh 
15:03:22 <Zakim> +Suresh; got it
15:03:34 <darobin> blassey?
15:03:50 <Zakim> +Bryan_Sullivan
15:04:26 <darobin> ScribeNick: Suresh 
15:05:20 <nwidell> Present+ Niklas_Widell
15:05:50 <fjh> Topic: Minutes approval
15:06:00 <fjh> proposed RESOLUTION: minutes from 2 Feb approved
15:06:14 <Suresh> Resolution: minutes from 3rd Feb approved
15:06:17 <darobin> s/2 Feb/3 Feb/
15:06:21 <fjh> Topic: Policy 
15:06:28 <Suresh> Topic: Policy
15:06:30 <fjh> action-16?
15:06:30 <trackbot> ACTION-16 -- Bryan Sullivan to help review/compare device capabilities and features -- due 2009-11-02 -- OPEN
15:06:30 <trackbot> http://www.w3.org/2009/dap/track/actions/16
15:06:49 <wonsuk> wonsuk has joined #dap
15:07:02 <Suresh> Bryan: leave it open
15:07:10 <darobin> action-16 due 2010-02-24
15:07:10 <trackbot> ACTION-16 Help review/compare device capabilities and features due date now 2010-02-24
15:07:23 <Suresh> Due date: Feb 24
15:07:25 <fjh> action-45?
15:07:25 <trackbot> ACTION-45 -- David Rogers to provide use case with threat model scenarios -- due 2009-11-10 -- OPEN
15:07:25 <trackbot> http://www.w3.org/2009/dap/track/actions/45
15:07:32 <fjh> action-48?
15:07:32 <trackbot> ACTION-48 -- Suresh Chitturi to propose a definition for API access control, and a possible model for policy enforcement -- due 2010-02-10 -- OPEN
15:07:32 <trackbot> http://www.w3.org/2009/dap/track/actions/48
15:07:37 <marcin> marcin has joined #dap
15:07:45 <marcin> Present+ Marcin_Hanclik
15:08:12 <bsulliva> bsulliva has joined #dap
15:08:24 <fjh> suresh notes access control from requirements, policy enforcement for design
15:08:44 <Zakim> +??P20
15:08:51 <Zakim> +[T-Systems]
15:09:04 <marcin> Zakim, P20 is marcin
15:09:04 <Zakim> sorry, marcin, I do not recognize a party named 'P20'
15:09:06 <Zakim> + +82.10.58.00.aaii
15:09:13 <fjh> note suresh action for 2 wks
15:09:16 <marcin> Zakim, ??P20 is marcin
15:09:16 <Zakim> +marcin; got it
15:09:22 <fjh> action-77?
15:09:22 <trackbot> ACTION-77 -- John Morris to provide a discussion of requirements for privacy -- due 2010-01-19 -- OPEN
15:09:22 <trackbot> http://www.w3.org/2009/dap/track/actions/77
15:09:23 <Suresh> Due date for Action-48: Feb 24
15:09:24 <wonsuk> zakim, +82.10.58.00.aaii is wonsuk
15:09:24 <Zakim> +wonsuk; got it
15:09:25 <richt> richt has joined #dap
15:09:28 <darobin> action-48 due 2010-02-24
15:09:28 <trackbot> ACTION-48 Propose a definition for API access control, and a possible model for policy enforcement due date now 2010-02-24
15:09:34 <richt> Present+ Richard_Tibbett
15:09:45 <fjh> action-79?
15:09:45 <trackbot> ACTION-79 -- Paddy Byers to integrate his use cases in policy requirements -- due 2010-01-13 -- OPEN
15:09:45 <trackbot> http://www.w3.org/2009/dap/track/actions/79
15:09:54 <wonsuk> Present+ Wonsuk_Lee
15:09:57 <bsulliva> Present+ bryan_sullivan
15:10:00 <Claes> Claes has joined #dap
15:10:05 <Suresh> action-48 due 2010-02-24
15:10:05 <trackbot> ACTION-48 Propose a definition for API access control, and a possible model for policy enforcement due date now 2010-02-24
15:10:14 <fjh> available for call in 2 wks
15:10:34 <Suresh> action-79 due 2010-02-24
15:10:34 <trackbot> ACTION-79 Integrate his use cases in policy requirements due date now 2010-02-24
15:10:36 <fjh> Dan Applequist's TAG message about privacy per api or grouping
15:10:45 <fjh> http://lists.w3.org/Archives/Public/public-device-apis/2010Feb/0032.html
15:10:50 <Zakim> -darobin
15:11:16 <fjh> http://lists.w3.org/Archives/Public/public-device-apis/2010Feb/0067.html
15:11:21 <Suresh> fjh: Essentially TAG recommends the privacy to be dealt on per-API basis
15:11:39 <Zakim> + +04610801aajj
15:12:02 <Zakim> +??P1
15:12:08 <Claes> Present+ Claes_Nilsson
15:12:12 <fjh> Do we want to indicate use cases/requirements related to the REST 
15:12:26 <fjh> Incorporate material from currently open actions
15:12:35 <Suresh> we need to incorporate open action results
15:12:39 <fjh> Issues noted in document, next steps?
15:13:13 <Ingmar> Ingmar has joined #dap
15:13:17 <Suresh> fjh: trust, granularity, access control need to be adddressed
15:13:42 <Suresh> fjh: rename to "common security" or similar from "policy"?
15:14:20 <Suresh> fjh: trying to understand how to go forward?
15:14:44 <paddy> q+
15:14:46 <Suresh> move to FPWD? doesn't seem like we are there yet, and what to do with REST issue?
15:14:59 <fjh> ack paddy
15:15:00 <darobin> ack paddy 
15:15:12 <Suresh> paddy: we need to see a concrete proposal realy..
15:15:25 <fjh> need concrete proposal for REST approach, also address concerns raised by Paddy
15:16:06 <AnssiK> re RESTful APIs and OAuth darobin said on the ML: "Our friends from Google have been working on something here "
15:16:09 <Suresh> fjh: the email discussions are vague and unless we get a concrete proposal we cannot move forward
15:17:04 <Suresh> robin: there some offline documents from Google, that can be useful related to OAuth, etc.
15:17:17 <bsulliva> q+
15:17:30 <fjh> ack bsulliva
15:17:47 <Suresh> fjh: if we are taking REST approach, i would like to see it mentioned in a document
15:17:59 <fjh> s/a document/requirements document
15:18:13 <Suresh> bryan: trying to understand the shift in the direction here
15:18:35 <Suresh> bryan: charter explicitly talks about device
15:18:41 <tlr> q+
15:19:17 <Suresh> fjh: the REST approach is to let access based on rest apis but the functionality could be on the device
15:19:46 <AnssiK> this is what the charter says: "Devices in this context include desktop computers, laptop computers, mobile internet devices (MIDs), cellular phones, etc. "
15:20:06 <bsulliva> Q-
15:20:08 <Suresh> bryan: Are we going to rework everything based on REST approach, e.g. dom objects, session storage, etc
15:20:17 <fjh> ack Thomas
15:20:43 <fjh> note that REST approach could be limited to contacts/PIM, could be implemented without web server or actual protocol exchangs
15:20:47 <fjh> on device
15:21:02 <fjh> benefit to allowing local and or network access
15:21:26 <fjh> I suggest that even with OAuth, device will still require access control policy regardless
15:22:03 <Suresh> thomas: The abstraction here is about javascript objects.....
15:22:08 <fjh> tlr notes that we cannot wait very long for EST proposal
15:22:09 <Zakim> -darobin
15:22:11 <fjh> s/EST/REST
15:22:42 <fjh> tlr notes we need to decide on network based abstraction versus local
15:22:54 <fjh> q+
15:23:07 <fjh> tlr allows OAuth authorization delegation
15:23:12 <Zakim> +??P1
15:23:22 <fjh> question - how would OAuth address local non-delegated case?
15:23:38 <fjh> tlr agrees with fjh that Oauth does not eliminate need for policy file
15:23:43 <ag> ag has joined #dap
15:23:48 <fjh> q?
15:23:49 <Suresh> tlr: OAuth would be useful indegredient for REST approach
15:23:50 <fjh> q-
15:23:59 <fjh> q+ to ask about criteria
15:24:07 <fjh> ack fjh
15:24:07 <Zakim> fjh, you wanted to ask about criteria
15:24:13 <darobin> darobin has joined #dap
15:24:23 <Suresh> tlr: The REST approach makes sense in some cases and in some cases not
15:24:46 <Suresh> fjh: having a criteria is helpful
15:25:07 <Suresh> fjh: local device access is core to our work
15:25:38 <Suresh> policy work is still required regardless of the approach, do you agree?
15:25:49 <bsulliva> q+
15:25:50 <darobin> q?
15:26:17 <fjh> focus on policy exchange versus defining policy itself
15:26:27 <Suresh> tlr: some mechanism needs to be there, but can't tell to what extent we need to specify
15:27:03 <Suresh> fjh: from proposals like BONDI, we have concrete cases for policy based on trust...
15:27:25 <Suresh> fjh: but how long can we wait?
15:27:51 <Suresh> tlr: if we do not have a champion, we cannot progress
15:28:35 <Suresh> fjh: Robin has worked on it, but how much longer should we wait?
15:28:50 <paddy> q+
15:29:10 <Suresh> robin: we do not have all the API drafts, e.g. gallery that could help us make the decision
15:29:23 <fjh> ack bsulliva
15:29:34 <Suresh> fjh: would two more weeks be sufficient?
15:29:48 <fjh> bsullivan notes that we need detail on how OAuth would work for device context from REST proponents
15:30:01 <fjh> ack paddy
15:30:07 <fjh> paddy +1 this
15:30:21 <fjh> do not want to see backtracking
15:30:41 <fjh> paddy notes we do not want to be stuck, need to move forward, need concrete proposal
15:30:45 <Suresh> paddy: all the policy has been paralyzed due to the diversion with REST
15:31:26 <fjh> proposed resolution: if the wg does not have a concrete REST/OAuth proposal in 2 weeks we will move forward with existing policy and API plans
15:31:43 <Suresh> +1
15:32:39 <Zakim> -arve
15:32:43 <fjh> not sure we want to require HTTP within device for local access, sounds not so good
15:32:44 <Suresh> tlr: critical decision is whether we take the RESTful approach
15:33:04 <Zakim> -??P1
15:33:09 <Suresh> tlr: OAuth is a follw-up
15:33:34 <fjh> proposed resolution: if the wg does not have a concrete REST proposal including policy concerns, in 2 weeks, we will move forward with existing policy and API plans
15:33:47 <Suresh> tlr: i do not want to link the two together i.e. REST and OAuth
15:34:00 <arve> arve has joined #dap
15:34:15 <Zakim> +[IPcaller]
15:34:21 <nwidell> q+
15:34:23 <Suresh> waiting for robin
15:34:45 <Suresh> proposed resolution: if the wg does not have a concrete REST proposal including policy concerns, in 2 weeks, we will move forward with existing policy and API plans
15:34:47 <darobin> Zakim, [IPCaller] is me
15:34:47 <Zakim> +darobin; got it
15:34:48 <Zakim> + +47.23.69.aakk
15:35:28 <Suresh> robin: two weeks is realistic, i believe
15:35:57 <Suresh> robin: perhaps, sending an email to the list making the resolution visible
15:36:06 <Suresh> fjh: can we make the resolution here then?
15:36:14 <Suresh> proposed resolution: if the wg does not have a concrete REST proposal including policy concerns, in 2 weeks, we will move forward with existing policy and API plans
15:36:29 <Suresh> if the wg does not have a concrete REST proposal including policy concerns, in 2 weeks, we will move forward with existing policy and API plans
15:37:14 <Suresh> RESOLUTION: if the WG does nto have a concrete REST proposal including policy concerns, in 2 weeks, we will move forward with existing policy and API plans
15:37:28 <darobin> s/nto have/not have
15:37:41 <Claes> Sorry, need to drop off
15:38:21 <fjh> proposed resolution: Change title of policy requirements to "Device API Security, privacy and policy requirements"
15:39:13 <Suresh> RESOLUTION: Change title of policy requirements to "Device API Security, privacy and policy requirements"
15:39:46 <Zakim> - +04610801aajj
15:39:51 <Suresh> ???: if we take the REST approach wouldn't that change the landscape e.g. more interested participants
15:39:57 <tlr> s/???/Niklas/
15:40:03 <darobin> s/???/Niklas
15:40:17 <bsulliva> I agree - that was my point re the charter, this changes the nature of what DAP was envisioned to do.
15:40:28 <Suresh> good point
15:41:11 <richt> I didn't know W3C was in the business of defining web services...but it is an interesting solution to the problem
15:41:14 <fjh> niklas notes concern that REST would expand the scope, bring in additional stakeholders, and increase risks for project
15:42:03 <fjh> q?
15:42:14 <richt> ..except for SOAP but that was the defintion rather than specific SOAP services
15:42:54 <fjh> It would be good to keep usability for Javascript programmers
15:43:15 <bsulliva> q+
15:43:46 <fjh> ack nwidell
15:44:04 <paddy> q+
15:44:13 <fjh> note that REST would expand the work even if in scope of charter
15:44:13 <Suresh> Claes: just trying to understand the group's understanding, from practical viewpoint it opens the scope up
15:44:17 <Zakim> -darobin
15:44:21 <fjh> ack bsulliva
15:44:49 <fjh> brian notes that OAuth will not solve problems, usability issues, allows repeated authorization but not initial authorization
15:44:55 <Suresh> bryan: from my reading, there is no support in Oauth for automatic authorization
15:45:16 <Zakim> +??P1
15:45:24 <darobin> Zakim, ??P1 is me
15:45:24 <Zakim> +darobin; got it
15:45:34 <fjh> tlr consent step could be be policy enforcement step
15:45:40 <fjh> s/tlr/tlr notes
15:46:01 <fjh> q+ to note that REST proponents are arguing that OAuth is only one
15:46:04 <fjh> ack paddy
15:46:05 <Suresh> tlr: there is no reason why the user needs to be in the path, but let's discuss the Oauth after we decide on the approach
15:46:10 <bsulliva> q-
15:46:37 <tlr> Agree with Paddy that this is a design choice.
15:46:43 <fjh> paddy notes that REST API has design choices regarding abstraction for local resources and/or remote
15:46:58 <Suresh> q+
15:47:03 <fjh> ack fjh
15:47:03 <Zakim> fjh, you wanted to note that REST proponents are arguing that OAuth is only one
15:47:06 <richt> +1 agree with paddy. Currently DAP is abstracted from whether it is a web service or not. It is a lower level design choice.
15:47:52 <fjh> ack Suresh
15:48:14 <fjh> action: fjh to update title of Policy requirements document
15:48:14 <trackbot> Created ACTION-94 - Update title of Policy requirements document [on Frederick Hirsch - due 2010-02-17].
15:49:24 <Suresh> Suresh: i am little confused here, we seem to be going in circles,
15:50:16 <Suresh> shouldn't we just stick to the charter and the current approach rather than waiting...
15:50:34 <fjh> have deadline for concrete proposal so we will await that
15:50:35 <Suresh> if REST is viable, then we can look at it
15:50:50 <ag> what's the value added of using REST style APIs in a developer point of view (from JS) ? 
15:51:07 <Suresh> Topic: APIs
15:51:19 <maxf> OAuth sounds like a concrete proposal to me (maybe a bad one, but concrete nevertheless)
15:51:28 <maxf> q+
15:51:32 <darobin> ack maxf 
15:52:33 <Suresh> robin: any idea when we can publish something?
15:52:56 <fjh> Regrets+ Daniel_Jesus_Coloma_Baiges
15:53:19 <Suresh> Suresh has joined #dap
15:53:26 <Suresh> joined back
15:53:35 <Suresh> Topic: Messaging APIs
15:54:45 <Zakim> -darobin
15:55:28 <Suresh> will have a more complete draft to the list by next week
15:55:52 <Zakim> -nwidell
15:56:14 <nwidell> sorry random call drop
15:56:24 <Zakim> +??P1
15:56:31 <Suresh> nwidell: will have a more complete draft on messaging APIs to the list by next week
15:57:02 <Zakim> -marcin
15:57:06 <Zakim> +nwidell
15:57:06 <darobin> Zakim, ??P1 is me
15:57:08 <Zakim> +darobin; got it
15:57:53 <Suresh> Topic: File API
15:58:22 <darobin> -> http://www.w3.org/mid/44b058fe1001291332g1bec627cu3555819ac1eb0404@mail.gmail.com
15:58:22 <Suresh> robin: Eric from google will be joining the group and will contribute to the work
15:59:04 <Suresh> Topic: heads-up on WebApps Rechartering
15:59:28 <Suresh> robin: recommend the group to pay attention to these discussions
15:59:30 <Suresh> q+
15:59:36 <darobin> ack Suresh 
16:00:00 <bsulliva> q+
16:00:13 <Suresh> q-
16:00:27 <paddy> apologies but I have to drop off
16:00:45 <darobin> ack bsulliva 
16:01:34 <Suresh> bryan: also recommends to follow the discussion on re-chartering
16:01:52 <shepazu> shepazu has joined #dap
16:01:52 <darobin> APIs with no taker: Gallery, Tasks, Application Launcher, User Interaction, and Communication Log
16:02:30 <Suresh> bandwidth problem i think:-)
16:02:32 <Dzung_Tran> I thought the Gallery was put to rest due the the proposal of Media metadata Annotation
16:02:36 <bsulliva> bandwidth
16:03:42 <Suresh> robin; perhaps we can revisit this issue at the F2F
16:03:53 <fjh> zakim, who i shere?
16:04:09 <wonsuk> I am sorry for late about Gallery API, but i think i can prepare the initial draft until the end of this month.
16:04:13 <Suresh> there is an echo
16:04:19 <fjh> zakim, who is here?
16:05:13 <Dzung_Tran> http://lists.w3.org/Archives/Public/public-device-apis/2009Nov/0002.html
16:05:18 <Suresh> robin: any other topics?
16:05:31 <fjh> in 2 weeks should start planning for f2f
16:05:47 <fjh> as part of decisions
16:05:59 <fjh> any other business?
16:06:01 <Suresh> dropped out...
16:06:19 <Zakim> Zakim has joined #dap
16:06:22 <tlr> zakim, this is dap
16:06:22 <Zakim> ok, tlr; that matches UW_DAP()10:00AM
16:06:26 <tlr> zakim, who is making noise?
16:06:33 <darobin> darobin has joined #dap
16:06:37 <Zakim> tlr, listening for 10 seconds I heard sound from the following: Suresh (54%), fjh (71%)
16:06:52 <aguillou> aguillou has joined #dap
16:07:18 <Suresh> meeting adjourned
16:07:27 <Zakim> -Thomas
16:07:31 <Zakim> -Suresh
16:07:32 <Zakim> -Bryan_Sullivan
16:07:32 <Zakim> -ilkka
16:07:34 <fjh> rrsagent, generate minutes
16:07:34 <RRSAgent> I have made the request to generate http://www.w3.org/2010/02/10-dap-minutes.html fjh
16:07:34 <Zakim> -richt
16:07:36 <Zakim> -LauraA
16:07:38 <Zakim> -maxf
16:07:42 <Zakim> -AnssiK
16:07:46 <Zakim> -fjh
16:07:50 <Zakim> -[T-Systems]
16:07:54 <Zakim> -wonsuk
16:07:57 <wonsuk> wonsuk has left #dap
16:08:11 <Zakim> -nwidell
16:16:27 <AnssiK> AnssiK has left #dap
16:35:01 <Zakim> disconnecting the lone participant, arve, in UW_DAP()10:00AM
16:35:03 <Zakim> UW_DAP()10:00AM has ended
16:35:05 <Zakim> Attendees were richt, Suresh, Thomas, ilkka, maxf, AnssiK, fjh, LauraA, Bryan_Sullivan, [T-Systems], wonsuk, arve, darobin, nwidell
17:34:25 <Marcos> Marcos has joined #dap
17:36:45 <arve> huh?  I hung up at the same time as everyone else
18:04:52 <paddy> paddy has joined #dap
18:27:17 <shepazu> shepazu has joined #dap
18:33:12 <Zakim> Zakim has left #dap
20:05:34 <tlr> tlr has joined #dap
22:14:25 <shepazu> shepazu has joined #dap