14:56:37 RRSAgent has joined #bpwg 14:56:37 logging to http://www.w3.org/2008/03/11-bpwg-irc 14:56:39 RRSAgent, make logs public 14:56:39 Zakim has joined #bpwg 14:56:41 Zakim, this will be BPWG 14:56:41 ok, trackbot-ng; I see MWI_BPWG(CTTF)11:00AM scheduled to start in 4 minutes 14:56:42 Meeting: Mobile Web Best Practices Working Group Teleconference 14:56:42 Date: 11 March 2008 14:56:59 Agenda: http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Mar/0003.html 14:57:05 Chair: francois 14:57:24 Regrets: Bryan, MartinJ, Murari 14:57:43 zakim, code? 14:57:43 the conference code is 2283 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), francois 14:58:14 MWI_BPWG(CTTF)11:00AM has now started 14:58:15 jo has joined #bpwg 14:58:21 + +049238aaaa 14:58:31 zakim, aaaa is me 14:58:31 +francois; got it 14:58:35 zakim, code? 14:58:35 the conference code is 2283 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), jo 14:59:08 + +0208995aabb 14:59:19 zakim, aabb is me 14:59:19 +jo; got it 14:59:52 hgerlach has joined #bpwg 14:59:57 + +46.3.17.47.aacc 14:59:58 hi 15:00:03 zakim, +46 is me 15:00:07 +Magnus; got it 15:00:40 andrews has joined #bpwg 15:00:50 + +049211aadd 15:00:51 SeanP has joined #bpwg 15:01:42 + +0207287aaee 15:01:45 zakim, aadd is heiko 15:01:46 +heiko; got it 15:02:07 zakim, aadd is hgerlach 15:02:07 sorry, francois, I do not recognize a party named 'aadd' 15:02:08 rob has joined #bpwg 15:02:28 zakim, aaee is rob 15:02:30 + +1.630.414.aaff 15:02:32 +rob; got it 15:02:41 Zakim, aaff is me 15:02:42 +SeanP; got it 15:03:28 zakim, who's on the call? 15:03:34 zakim, who is on the call? 15:03:44 On the phone I see francois, jo, Magnus, heiko, rob, SeanP 15:03:52 On the phone I see francois, jo, Magnus, heiko, rob, SeanP 15:03:59 zakim, wake up 15:03:59 I don't understand 'wake up', jo 15:04:30 Scribe: Jo 15:05:13 Topic: Introduction 15:05:25 + +0789972aagg 15:05:41 francois: [review of what happened at the F2F and pointer to summary] 15:05:45 zakim, aagg is andrew 15:05:45 +andrew; got it 15:06:34 francois: jo proposed an editor's meeting ... I can host at Sofia (SE France) 15:06:50 ... who would be able to come? 15:07:01 ... dates would be next week or the week after 15:07:19 No, sorry 15:07:26 I don't think I'll be able to make it 15:07:50 jo: needs to be before Easter 15:08:03 francois: perhaps we can wait an extra week? 15:08:12 heiko: could we do it in the UK? 15:08:26 jo: need a host in the UK 15:10:01 ... if noone else wants to attend then Francois and I can sort this out between us 15:13:45 PROPOSED RESOLUTION: Francois and Jo to roganise work as they see fit and present group with final pre-FPWD 15:13:49 +1 (and thank you) 15:13:53 +1 15:13:55 +1 15:14:09 RESOLUTION: Francois and Jo to roganise work as they see fit and present group with final pre-FPWD 15:15:43 jo: the only bits that open to discuss in that context are the bits after 3.1.4 15:16:03 ... following resolution at F2F 15:16:34 Topic: Aarons Contribution ACTION-666 15:16:43 -> http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Mar/0000.html Aaron's contribution 15:17:21 francois: this is content for 2.5 control of the behavior of the proxy 15:17:34 ... goes in the same direction as we agreed to go 15:17:46 ... maybe inconsistent with other things we say 15:18:21 ... question is how should proxy indicate it could transform? 15:19:18 ... if the content has not been modified then the proxy should indicate that a transformed version is available 15:19:28 ... how should this happen? 15:19:52 ... I don't see how this can happen without transforming the page 15:19:58 q+ 15:20:07 magnus: there could be an insterstitial page 15:20:29 francois: yes, I suggested that but it would be a lousy user experience 15:20:39 ack SeanP 15:20:53 heiko: i think it should be only done once 15:21:03 seanP: you could insert a little link 15:21:33 francois: yes, I noted that in response to aaron, but that would imply inconsistent behavior 15:22:20 seanP: one possiblity is some user agreement that it you wanted it you could get it 15:22:43 francois: the list of options should contain this as an option that the user can set 15:23:04 ... sometimes you are looking at a page and you wish you could transform it or not 15:23:23 ... if the server issued a cache-control no-transform the link would be missing 15:23:29 q+ 15:23:40 ack SeanP 15:23:50 ... the proxy MAY indicate that a transformed version is available only where it decided not to transform 15:24:08 q+ 15:24:23 ack rob 15:24:28 seanP: further on your point about having a link sometimes and sometimes not might be confusing, I am not really sure that would be a bad user experience 15:25:00 q+ 15:25:13 rob: there is the issue about confusion and there is also the question about wanting to split the page and in those circumstances the user might want to transform in this case 15:25:26 ack hgerlach 15:25:42 ... so its worth saying you can switch it off and on but saying how is probably out of scope 15:26:18 heiko: can we differentiate three things - leave things completley untouched, second, just headers and footers 15:27:17 francois: we are trying to allow the server to have a "switch off" and if we allow adding a link that is something to be avoided 15:28:31 ... we could complete Aaron's text to say that this should not be done to pages that can not be transformed 15:28:36 PROPOSED RESOLUTION: keep aaron's text as it is for 2.5.1 15:29:20 q+ 15:30:22 -> http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080227#sec-ServerResponse current editor's text 15:32:12 ack Magnus 15:33:00 jo: Don't think we should discuss adding a link to the unmodified content to say that it could be modified 15:33:05 Transforming proxies SHOULD provide to their users an indication that the content being viewed has been adapted for 15:33:05 mobile presentation. If the content has not been modified, because of 15:33:05 server or user preferences, but transformation is possible and 15:33:05 potentially useful, the proxy MAY indicate that a transformed version 15:33:05 is available. 15:33:26 ... that could appear later in the document - this section is an overview 15:34:54 francois: take jo's point that whatever we resolve on the second bit it could go later in the document 15:35:31 ... magnus, would you leave out the bit on saying that the content can be modified 15:35:58 magnus: my main problem is that the resolution can't be left as is, as it has a number of comments 15:36:56 ... I'd be happy with just taking the first sentence and then saying that the original content can be retireved without saying how exactly 15:37:17 ... could also have the bit on sticky sessions 15:37:49 ... I'm trying to look at this in the context of the document which is an overview 15:37:58 ... [discusses how it can be worded] 15:39:10 Transforming proxies MAY provide to their users: 15:39:10 - An indication that the content being viewed has been adapted for 15:39:10 mobile presentation. 15:39:10 - An option to view the original, unmodified content. 15:39:10 - some "sticky" preferences to their users. 15:39:43 q+ 15:39:46 francois: this is to emphasize the point that this is just a discussion 15:39:48 ack SeanP 15:40:30 seanp: we have talked about providing a link to unmodified content - what to do if the unmodified content crashes the phone? 15:40:59 francois: good point but does not remove the need for a link in the generic case, the proxy could offer a warning 15:41:06 ... in that case 15:41:09 q+ 15:41:13 ack jo 15:42:49 Transforming proxies SHOULD provide to their users: 15:42:49 - An indication that the content being viewed has been adapted for 15:42:49 mobile presentation. 15:42:49 - An option to view the original, unmodified content. 15:42:49 - some session settings to their users. 15:43:09 jo: I'd prefer to leave the normative wording even though this is less of a prescriptive section, otherwise there's a danger that the document may appear to contradict itself when it goes on to discuss it later 15:44:20 ... I think it's SHOULD on the first two and a MAY on the third 15:44:44 Transforming proxies SHOULD provide to their users: 15:44:44 - An indication that the content being viewed has been adapted for 15:44:44 mobile presentation. 15:44:45 - An option to view the original, unmodified content. 15:44:45 They MAY also provide session settings to their users. 15:44:52 +1 15:45:11 +1 15:45:19 +1 15:45:23 ACTION: Jo to reword 2.5.1 along the lines proposed by Francois 15:45:23 Created ACTION-706 - Reword 2.5.1 along the lines proposed by Francois [on Jo Rabin - due 2008-03-18]. 15:45:24 +1 15:46:06 francois: additional qeustion, should we mention examples of session settings 15:46:13 magnus: that would be OK 15:46:29 francois: relates to the list of directives we removed from the document 15:46:39 ... seems to me to be useful 15:47:37 magnus: examples being: never transform no matter what, only transform if absolutely necessary, transform as much as possible and so on 15:47:59 jo: that is similar to the list we will try to codify in POWDER as server preferences 15:48:47 ACTION: Jo to include examples in 2.5.1 bullet 3 per the dicussion above 15:48:47 Created ACTION-707 - Include examples in 2.5.1 bullet 3 per the dicussion above [on Jo Rabin - due 2008-03-18]. 15:49:14 heiko: I expect POWDER is for the device capability database 15:49:34 ... it's a follow on to WURFL? 15:49:46 jo: no 15:50:34 ... we have been looking at it as a way of describing server preferences 15:51:18 heiko: we need to capture the dependences on other projects, we need to understand device capabilities 15:51:30 francois: we don't want to depend on POWDER 15:51:39 ... and don't want to be delayed by it 15:51:55 ... or indeed the DDR 15:52:41 francois: on 2.5.2 15:53:21 Transforming proxies MUST provide support for control over the content 15:53:21 transformation process by origin servers. 15:53:36 These control mechanisms are detailed in section 3 (Behavior of Components). 15:54:31 sorry quys, I have to leave for the next call:-(, cheers Heiko 15:54:37 +q 15:54:42 ack andrews 15:55:00 andrew: are we only referring to no-transform here? 15:55:08 -heiko 15:55:40 francois: the controls are in section 3, at the moment it is true that no-transform is the only control we have but maybe there will be more control by POWDER later 15:57:10 jo: points out that vary and warning transformation applied are both means of control 15:57:48 francois: I don't think we should list warning transformation applied as a means of control 15:57:55 jo: agreed 15:58:28 ACTION: Jo to update 2.5.2 in accordance with discussion and Seoul resolution on preferences 15:58:28 Created ACTION-708 - Update 2.5.2 in accordance with discussion and Seoul resolution on preferences [on Jo Rabin - due 2008-03-18]. 15:59:48 francois: aaron leaves 2.5.3 untouched, do we need to say more 15:59:48 This is another place where some examples may help. 15:59:51 jo: not sure 16:00:15 francois: it's a bit useless as is so examples would help 16:00:27 ACTION: daoust to write some examples for 2.5.3 16:00:27 Created ACTION-709 - Write some examples for 2.5.3 [on François Daoust - due 2008-03-18]. 16:01:39 jo: I'll try to update the doc in the next couple of days 16:01:51 -Magnus 16:01:55 [adjourned] 16:02:07 Close ACTION-666 16:02:07 ACTION-666 Draft section 2.6 listing user control options that SHOULD be supported closed 16:02:09 s/[adjourned]// 16:02:17 [adjourned] 16:02:22 -SeanP 16:02:23 -francois 16:02:25 -andrew 16:02:25 -jo 16:02:25 -rob 16:02:26 MWI_BPWG(CTTF)11:00AM has ended 16:02:27 Attendees were +049238aaaa, francois, +0208995aabb, jo, +46.3.17.47.aacc, Magnus, +049211aadd, +0207287aaee, heiko, +1.630.414.aaff, rob, SeanP, +0789972aagg, andrew 16:02:30 rob has left #bpwg 16:02:34 zakim, list attendees 16:02:34 sorry, francois, I don't know what conference this is 16:02:41 RRSAgent, draft minutes 16:02:41 I have made the request to generate http://www.w3.org/2008/03/11-bpwg-minutes.html francois 16:03:05 Present: Francois, Jo, SeanP, AndrewS, Magnus, Heiko, Rob 16:03:29 rrsagent, make logs public 16:03:36 rrsagent, make minutes 16:03:36 I have made the request to generate http://www.w3.org/2008/03/11-bpwg-minutes.html jo 16:05:56 rrsagent, off