FW: Content Transformation TF Report for BP Call 2007-09-20

Thanks Adam - forwarded to CT list.

 

________________________________

From: member-bpwg-request@w3.org [mailto:member-bpwg-request@w3.org] On Behalf Of Adam Connors
Sent: 20 September 2007 16:02
To: member-bpwg@w3.org
Subject: Re: Content Transformation TF Report for BP Call 2007-09-20

 

Two minor comments from me:

1) Editorial: This sentence went a bit wonky...
1.2.1 The principal advantage of Content Transformation is that *it* provides the ability for mobile users to enjoy a Web experience even though a large number of Web sites [that] are mobile unaware or mobile blocking.

 

(thks, typo noted)



2) Maybe out of scope but another issue of content transformation is that it's hard to get right, and bad content transformation is sometimes worse than no content transformation. Not sure if it's worth calling out explicitly or not... I guess the only way to ameliorate this is to ensure the proxy has good knowledge of the device, and the origin server being able to control the actions of the proxy adequately. 

BTW: Is this the right place to response with comments like this? Is there an issue tracker or some such I should be using?

(public-bpwg-ct list please)



Thanks,

Adam.

On 9/20/07, Alan Chuter <achuter@technosite.es> wrote:


The scope could be wider in Techniques "any non-desktop presentation of
content" as there are things like widgets that are desktop and need
transformation (I believe).

I agree with the Editorial Note that the techniques could be woven into 
the problems that are described in the first section of the document. As I
read the section "1.2.2 Issues with Content Transformation" I thought that
it describes the issues well, but there was a need for a conclusion to 
each issue about "where do we go from here?", to express or restate the
issue in terms of a solution rather than an issue. I don't mean to include
the solution, which is the subject of the guidelines document, but a 
description of the issue seen from the solution point of view.

Otherwise the document seems to work well for me.

Alan


En Thu, 20 Sep 2007 11:36:22 +0200, Jo Rabin < jrabin@mtld.mobi <mailto:jrabin@mtld.mobi> > escribió:

>
>
>
> Just to add a furhter couple of cents on this: we (the CT TF) have
> requested feedback on the Content Transformation Problem Statement,
> before a final draft is created. 
>
> This is by way of a reminder, or heads up, that the output of the TF is
> output of the group as a whole, and requires the same scrutiny as a
> document produced in the context of the whole WG. 
>
> I feel that the fact that we haven't had any feedback is unlikely to be
> indicative of it being perfect.
>
> Jo
>
>
>> -----Original Message-----
>> From: member-bpwg-request@w3.org [mailto:member-bpwg-request@w3.org]
> On
>> Behalf Of Rhys Lewis
>> Sent: 20 September 2007 10:16 
>> To: daniel; member-bpwg@w3.org
>> Subject: RE: Content Transformation TF Report for BP Call 2007-09-20
>>
>>
>> Doh! Thanks to Jo for pointing out that I failed to include a URI for 
>> reference [3]. It should have been
>>
>> [3]
> http://lists.w3.org/Archives/Public/public-bpwg-ct/2007Sep/0014.html 
>>
>> Best wishes
>> Rhys
>>
>> > -----Original Message-----
>> > From: Rhys Lewis [mailto:rhys@volantis.com]
>> > Sent: 20 September 2007 09:34 
>> > To: 'Appelquist, Daniel, VF-Group'; 'member-bpwg@w3.org'
>> > Subject: Content Transformation TF Report for BP Call 2007-09-20
>> > 
>> > Hello everyone,
>> >
>> > The CT TF has continued to make progress on it's problem
>> > statement [1] and guidelines [2]documents.
>> >
>> > In particular, we have just received a major contribution [3] 
>> > for the guidelines document from Magnus. I expect this to be
>> > a major topic for next week's call.
>> >
>> > Best wishes
>> > Rhys
>> >
>> > [1]
>> > http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-dr
>> > afts/ProblemStatement/070911
>> > [2]
>> > http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-dr
>> afts/Guidelines/2007-08/CTGuidelines.html 
>> >
>> > > -----Original Message-----
>> > > From: member-bpwg-request@w3.org
>> > > [mailto: member-bpwg-request@w3.org <mailto:member-bpwg-request@w3.org> ] On Behalf Of
>> > Appelquist, Daniel,
>> > > VF-Group
>> > > Sent: 19 September 2007 15:38
>> > > To: member-bpwg@w3.org
>> > > Subject: [agenda] Agenda for tomorrow's call
>> > >
>> > > Hi everyone
>> > >
>> > > Here is the proposed agenda for tomorrow's meeting 
>> > (logistics info at
>> > > the end of this message).
>> > >
>> > > Please send your regrets to the list if you cannot attend.
>> > > Also, please send updates on your action items. 
>> > >
>> > > Chair: Dan
>> > > Team contact: Mike
>> > > Known regrets: Jo
>> > > Scribe: volunteers needed
>> > >
>> > > Agenda: 
>> > >
>> > >
>> > > 1. Task Force Reports
>> > >     - content transformation (Rhys?)
>> > >       (Please review the draft problem statement)
>> > >
>> > > 2. Plans for Seoul
>> > >     - First week of March?
>> > >
>> > > 3. mobileOK Basic Tests 1.0 - final review and approval
>> > >     - do we need a "conformance" section? (Process issue - 
>> > Mike please
>> > > take note.)
>> > >
>> > > 4. Reminder on Boston
>> > >
>> > > 5. Agenda for Boston
>> > >
>> > > 6. AOB 
>> > >
>> > >
>> > > Logistics:
>> > >
>> > > Thursday 20 September 2007
>> > >
>> > > 7:00 PDT; 10:00 EDT; 15:00 BST; 16:00 CET; 17:00 Helsinki; 
>> > 23:00 Tokyo
>> > >
>> > > Zakim bridge: tel:+1 617 761 6200 Code: 2794 (BPWG) Also
>> > > (tel:+33 4 89 06 34 99 tel:+44 117 370 6152)
>> > >
>> > > irc://irc.w3.org:6665#BPWG
>> > >
>> > > Sorry for the lack of links - this agenda prepared on a mobile
>> > > devices.
>> > > --
>> > > Daniel K. Appelquist 
>> > > +44 7748 111635
>> > > daniel.appelquist@vodafone.com
>> > >
>>
>
>
>



--
Alan Chuter
Accessibility Consultant
Technosite (Fundación ONCE)
achuter@technosite.es
www.technosite.es
Tel. +34 91 121 03 35 
Skype: achuter1

If you are unable to reply to this message because of spam filter, try my
alternative address achuter.technosite@yahoo.com.

Si no puede contestar a este mensaje por culpa del filtro de spam, intente 
con mi dirección alternativa achuter.technosite@yahoo.com.