RE: Proposed additional topic for joint DAP/WebApps Widgets F2F session
Hi, As discussed on the webapps call, in addition to Fredrick's proposal I think we need to understand the relationship between DAP / Widgets / WebApps / HTML5 more clearly. There are overlaps and architectural disparities which we should highlight and come up with a plan for dealing with. Would it be possible for the chairs to come up with some input in terms of an architecture diagram of where they think we are? Thanks, David. -Original Message- From: public-device-apis-requ...@w3.org [mailto:public-device-apis-requ...@w3.org] On Behalf Of Frederick Hirsch Sent: 29 October 2009 14:28 To: public-Webapps@w3.org WG Cc: Frederick Hirsch; Charles McCathieNevile; W3C Device APIs and Policy WG Subject: Proposed additional topic for joint DAP/WebApps Widgets F2F session If we have time and interest, I suggest we might also discuss in the joint DAP/WebApps Widgets session HTML5 security model, even if we also discuss in the joint DAP/WebApps API session, depending on the expertise in the room. I would like to make sure we transfer understanding to the DAP WG from everyone who can help the DAP WG and I'd like to make sure that somehow we have this discussion during TPAC. Thus Agenda topic for joint DAP/Webapps-Widget is Security Considerations, including HTML5. regards, Frederick Frederick Hirsch, Nokia Co-Chair, W3C DAP Working Group
Re: Proposed additional topic for joint DAP/WebApps Widgets F2F session
David Would it be possible for you to summarize what you think the issue is, as far as architecture and technical disparities, as a first step? regards, Frederick Frederick Hirsch Nokia On Oct 29, 2009, at 11:54 AM, ext David Rogers wrote: Hi, As discussed on the webapps call, in addition to Fredrick's proposal I think we need to understand the relationship between DAP / Widgets / WebApps / HTML5 more clearly. There are overlaps and architectural disparities which we should highlight and come up with a plan for dealing with. Would it be possible for the chairs to come up with some input in terms of an architecture diagram of where they think we are? Thanks, David. -Original Message- From: public-device-apis-requ...@w3.org [mailto:public-device-apis-requ...@w3.org] On Behalf Of Frederick Hirsch Sent: 29 October 2009 14:28 To: public-Webapps@w3.org WG Cc: Frederick Hirsch; Charles McCathieNevile; W3C Device APIs and Policy WG Subject: Proposed additional topic for joint DAP/WebApps Widgets F2F session If we have time and interest, I suggest we might also discuss in the joint DAP/WebApps Widgets session HTML5 security model, even if we also discuss in the joint DAP/WebApps API session, depending on the expertise in the room. I would like to make sure we transfer understanding to the DAP WG from everyone who can help the DAP WG and I'd like to make sure that somehow we have this discussion during TPAC. Thus Agenda topic for joint DAP/Webapps-Widget is Security Considerations, including HTML5. regards, Frederick Frederick Hirsch, Nokia Co-Chair, W3C DAP Working Group
Re: Proposed additional topic for joint DAP/WebApps Widgets F2F session
On Oct 29, 2009, at 11:54 AM, ext David Rogers wrote: As discussed on the webapps call, in addition to Fredrick's proposal I think we need to understand the relationship between DAP / Widgets / WebApps / HTML5 more clearly. There are overlaps and architectural disparities which we should highlight and come up with a plan for dealing with. Please elaborate on the overlaps and architectural disparities. -Regards, Art Barstow
RE: Proposed additional topic for joint DAP/WebApps Widgets F2F session
LOL, I wasn't expecting me to do the legwork for you all :-) One example would be FileSystem in DAP and the File API in webapps. How do these two fit together? I only saw an email on thoughts/assumptions about this recently. To the outside observer, it is not easy to see what the differences are and how this all fits together. We need to have a clear view (on one sheet of paper) about where these overlaps are and what the plan is for dealing with them. I was assuming that the chairs are best placed to do put the starting input in for this. Thanks, David. -Original Message- From: Arthur Barstow [mailto:art.bars...@nokia.com] Sent: 29 October 2009 16:04 To: David Rogers Cc: Hirsch Frederick (Nokia-CIC/Boston); public-Webapps@w3.org WG; Charles McCathieNevile; W3C Device APIs and Policy WG; Robin Berjon; Nick Allott Subject: Re: Proposed additional topic for joint DAP/WebApps Widgets F2F session On Oct 29, 2009, at 11:54 AM, ext David Rogers wrote: As discussed on the webapps call, in addition to Fredrick's proposal I think we need to understand the relationship between DAP / Widgets / WebApps / HTML5 more clearly. There are overlaps and architectural disparities which we should highlight and come up with a plan for dealing with. Please elaborate on the overlaps and architectural disparities. -Regards, Art Barstow
Re: Proposed additional topic for joint DAP/WebApps Widgets F2F session
On Thu, 29 Oct 2009 17:18:31 +0100, David Rogers david.rog...@omtp.org wrote: LOL, I wasn't expecting me to do the legwork for you all :-) One example would be FileSystem in DAP and the File API in webapps. How do these two fit together? I only saw an email on thoughts/assumptions about this recently. To the outside observer, it is not easy to see what the differences are and how this all fits together. We need to have a clear view (on one sheet of paper) about where these overlaps are and what the plan is for dealing with them. I was assuming that the chairs are best placed to do put the starting input in for this. That's the major centrepiece of why we have a joint APIs/DAP meeting planned :) cheers Chaals Thanks, David. -Original Message- From: Arthur Barstow [mailto:art.bars...@nokia.com] Sent: 29 October 2009 16:04 To: David Rogers Cc: Hirsch Frederick (Nokia-CIC/Boston); public-Webapps@w3.org WG; Charles McCathieNevile; W3C Device APIs and Policy WG; Robin Berjon; Nick Allott Subject: Re: Proposed additional topic for joint DAP/WebApps Widgets F2F session On Oct 29, 2009, at 11:54 AM, ext David Rogers wrote: As discussed on the webapps call, in addition to Fredrick's proposal I think we need to understand the relationship between DAP / Widgets / WebApps / HTML5 more clearly. There are overlaps and architectural disparities which we should highlight and come up with a plan for dealing with. Please elaborate on the overlaps and architectural disparities. -Regards, Art Barstow -- Charles McCathieNevile Opera Software, Standards Group je parle français -- hablo español -- jeg lærer norsk http://my.opera.com/chaals Try Opera: http://www.opera.com
RE: Proposed additional topic for joint DAP/WebApps Widgets F2F session
Hi, So of course that was one example and I'm trying not to get into detail here - my main point is that currently we have no big picture view, I don't think that is good enough. This is why I want to put a specific agenda point forward for the following: I think a key output of TPAC for those overlapping groups / work items should be an overall architectural view highlighting overlaps and issues and an accompanying plan to deal with those issues. To reiterate, that is: webapps (APIs), webapps (widgets), DAP, HTML5 and the overall security considerations. I think the Chairs should jointly own this and it should be presentable to the outside world at any stage. Cheers, David. -Original Message- From: Charles McCathieNevile [mailto:cha...@opera.com] Sent: 29 October 2009 16:53 To: David Rogers; Arthur Barstow Cc: Hirsch Frederick (Nokia-CIC/Boston); public-Webapps@w3.org WG; W3C Device APIs and Policy WG; Robin Berjon; Nick Allott Subject: Re: Proposed additional topic for joint DAP/WebApps Widgets F2F session On Thu, 29 Oct 2009 17:18:31 +0100, David Rogers david.rog...@omtp.org wrote: LOL, I wasn't expecting me to do the legwork for you all :-) One example would be FileSystem in DAP and the File API in webapps. How do these two fit together? I only saw an email on thoughts/assumptions about this recently. To the outside observer, it is not easy to see what the differences are and how this all fits together. We need to have a clear view (on one sheet of paper) about where these overlaps are and what the plan is for dealing with them. I was assuming that the chairs are best placed to do put the starting input in for this. That's the major centrepiece of why we have a joint APIs/DAP meeting planned :) cheers Chaals Thanks, David. -Original Message- From: Arthur Barstow [mailto:art.bars...@nokia.com] Sent: 29 October 2009 16:04 To: David Rogers Cc: Hirsch Frederick (Nokia-CIC/Boston); public-Webapps@w3.org WG; Charles McCathieNevile; W3C Device APIs and Policy WG; Robin Berjon; Nick Allott Subject: Re: Proposed additional topic for joint DAP/WebApps Widgets F2F session On Oct 29, 2009, at 11:54 AM, ext David Rogers wrote: As discussed on the webapps call, in addition to Fredrick's proposal I think we need to understand the relationship between DAP / Widgets / WebApps / HTML5 more clearly. There are overlaps and architectural disparities which we should highlight and come up with a plan for dealing with. Please elaborate on the overlaps and architectural disparities. -Regards, Art Barstow -- Charles McCathieNevile Opera Software, Standards Group je parle français -- hablo español -- jeg lærer norsk http://my.opera.com/chaals Try Opera: http://www.opera.com
