W3C home > Mailing lists > Public > public-bpwg@w3.org > September 2008

Re: [Agenda] agenda for tomorrow

From: Francois Daoust <fd@w3.org>
Date: Thu, 25 Sep 2008 17:01:59 +0200
Message-ID: <48DBA7E7.1040806@w3.org>
To: "Sullivan, Bryan" <BS3131@att.com>
CC: public-bpwg@w3.org

Hi Bryan,

We took a more formal resolution today, in case it needs to be pointed out:


Sullivan, Bryan wrote:
> Hi Dan,
> I won't be able to make the meeting but please put this on the agenda; I agreed to get confirmation that the WebApps group responses to the MWBP comments to the Widgets 1.0 Requirements were accepted by MWBP (I think this was agreed in a previous call, but need to double check). We may move forward with further discussions in this area (e.g. for Widgets 2.0) but don't expect further discussion on the comments they did not accept, at this time.
> Here's my summary of where we are with the comments that I submitted:
> During the last few weeks of discussion and reflection in WebApps, MWBP, and OMTP (BONDI) it's become clearer that the scope of the WebApps group is about Widget packaging and interfaces (functional capabilities) rather than best practices (MWI's scope, e.g. usability, interoperability, efficiency) or policy (OMTP's scope, e.g. API security). The Widget 1.0 functional capabilities should support the policy and best practices objectives, but beyond the basic ability to do so, the Widgets 1.0 Requirements don't have to reflect the policy/best-practices objectives directly. In the Widgets 1.0 timeframe, we will move forward with these comments/objectives within MWBP where possible. 
> The MWABP (Mobile Web Application Best Practices) for example can make recommendations on the *use* of Widget interface features and Javascript functions (e.g. XMLHttpRequest) to achieve what the MWBP comments were attempting to promote, e.g. interoperability, through:
> (a) identification of the widget in HTTP requests (user-agent header)
> (b) disclosure of Widget and device capabilities (Profile and Accept headers)
> Example:
> var client = new XMLHttpRequest();
> client.open('GET', 'http://dcd.server.com/channel?ID=21');
> client.setRequestHeader('User-Agent', 'DCD Widget/1.0');
> client.setRequestHeader('Accept', 'application/vnd.oma.dcd, multipart/mixed, multipart/related');
> client.setRequestHeader('Profile', '"http://megawidgets.com/dcd-widget1.0.rdf"');
> client.send();
> Also the Widget packaging provides the ability to describe the Widget, and MWBP could use this as the container for recommended notices to the user about resource impacts and automatic behaviors. This does not provide distinct/semantic disclosure in Widgets 1.0 timeframe, but is at least a start. Outside W3C, this objective can be pursued through additional policy-related metadata for Widgets. Hopefully we can expand the Widget Configuration Document in the Widgets 2.0 timeframe, to include these additional objectives.
> Some objectives may require further standardization work, e.g. to select a non-default proxy in XMLHttpRequest may require further work on the XMLHttpRequest object itself, since this (*select* a proxy) does not seem to be an option of XMLHttpRequest as defined (http://www.w3.org/TR/XMLHttpRequest/). Outside direct support from XMLHttpRequest (and perhaps W3C), we may be able to achieve this objective through policy definition.
> I will provide some related text to the MWABP for our editor's meeting on Friday.
> Best regards,
> Bryan Sullivan | AT&T
> -----Original Message-----
> From: public-bpwg-request@w3.org [mailto:public-bpwg-request@w3.org] On Behalf Of Appelquist, Daniel, VF-Group
> Sent: Wednesday, September 24, 2008 10:06 AM
> To: public-bpwg@w3.org
> Subject: [Agenda] agenda for tomorrow
> Note: The meeting is W3C Member Only
> Chair: Dan
> Team Contact: Fran├žois
> Known Regrets: Kai, David, Bruce, Sean
> Please make sure that if you are sending regrets you do so _before_ the 
> call and please use the member list to do so:
> mailto:member-bpwg@w3.org?subject=Regrets%20for%20BPWG%202008-09-25
> Proposed Agenda
> Unfortunately I have not had the chance to put together a specific agenda for this call. Please send suggestions for specific items.
> 1. Taskforce reports
> 2. ISSUEs and ACTIONs
> 3. AOB
> Logistics:
> Date: 2008-09-25T1400Z
> [0700 US Pacific, 1000 US Eastern, 1500 UK, 1600 CET, 1700 Helsinki]
> Phone: tel:+16177616200, tel:+33489063499 or tel:+441173706152
>                     Code 2794 ("BPWG") followed by #
> IRC: irc://irc.w3.org:6665#bpwg
> --
> Daniel K. Appelquist
> +44 7748 111635
> daniel.appelquist@vodafone.com 
Received on Thursday, 25 September 2008 15:02:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:52 UTC