14:57:43 RRSAgent has joined #bpwg 14:57:44 logging to http://www.w3.org/2008/03/25-bpwg-irc 14:57:45 RRSAgent, make logs public 14:57:46 Zakim has joined #bpwg 14:57:47 Zakim, this will be BPWG 14:57:47 ok, trackbot-ng; I see MWI_BPWG(CTTF)11:00AM scheduled to start in 3 minutes 14:57:48 Meeting: Mobile Web Best Practices Working Group Teleconference 14:57:49 Date: 25 March 2008 14:58:11 Agenda: http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Mar/0029.html 14:58:42 Regrets: kemp, Magnus, Bryan 14:58:52 Chair: francois 14:59:00 zakim, code? 14:59:00 the conference code is 2283 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), francois 14:59:20 rob has joined #bpwg 14:59:56 MWI_BPWG(CTTF)11:00AM has now started 15:00:00 + +049238aaaa 15:00:03 + +0208995aabb 15:00:05 - +0208995aabb 15:00:05 + +0208995aabb 15:00:12 zakim, aaaa is francois 15:00:12 +francois; got it 15:00:14 zakim, aabb is me 15:00:14 +jo; got it 15:00:16 SeanP has joined #bpwg 15:00:42 MartinJ has joined #bpwg 15:00:49 zakim, who's on the phone? 15:00:49 On the phone I see jo, francois 15:01:02 regrets+ andrews 15:01:34 + +0207287aacc 15:01:46 + +1.630.414.aadd 15:01:48 zakim, aacc is me 15:01:48 +rob; got it 15:01:50 + +0777613aaee 15:01:59 Zakim, aadd isme 15:01:59 I don't understand 'aadd isme', SeanP 15:02:07 zakim, aadd is SeanP 15:02:07 +SeanP; got it 15:02:08 zakim, aaee is me 15:02:09 +MartinJ; got it 15:02:09 Zakim aadd is me 15:03:34 Scribe: SeanP 15:03:37 ScribeNick: SeanP 15:04:09 Francois: Today we should go through our actions. 15:04:12 Topic: ACTION-682: Write a proposal on the HEAD request handling (§3.1.2) 15:04:39 Francois: Based on Martin's text 15:04:45 -> http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Mar/0009.html Martin's proposal 15:04:55 Present- Matt 15:05:05 Francois: I simplified one of the sentences. 15:05:20 "Clients can issue HTTP HEAD requests in order to determine if a 15:05:20 resource is of a type and/or size that they are capable of handling. A 15:05:20 proxy may convert a HEAD request into a GET request if it requires the 15:05:20 response body to determine the characteristics of the transformed 15:05:20 response that it would return if the client issues a GET request. Where 15:05:21 this occurs, the proxy should (subject to HTTP cache directives) cache 15:05:23 the response that it receives so that if the client immediately follows 15:05:26 the HEAD request with a GET request for the same URI, the proxy is not 15:05:26 Francois: Any problems with the proposed text? 15:05:29 required to send a second GET request to the server." 15:05:43 PROPOSED RESOLUTION: use above text to resolve ACTION-682 15:05:53 subject to HTTP cache directives => providing in accordance with normal HTTP caching rules 15:06:49 PROPOSED RESOLUTION: leave above text to resolve ACTION-682 in the hands of the editor 15:06:50 +1 15:06:56 +1 15:06:58 +1 15:07:11 -SeanP 15:07:37 RESOLUTION: leave above text to resolve ACTION-682 in the hands of the editor 15:07:43 Close ACTION-682 15:07:43 ACTION-682 Write a proposal on the HEAD request handling. closed 15:07:54 Topic: ACTION-683: Inference on URIs (§3.1.2) 15:08:12 + +1.630.773.aaff 15:08:21 -> http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Mar/0019.html rob's contribution 15:08:25 Zakim, aaff is me 15:08:25 +SeanP; got it 15:09:01 Francois: Rob, you suggested we no change anything 15:09:25 Rob: I think the statement that is already there is all we can say. 15:09:31 Zakim, mute me 15:09:31 SeanP should now be muted 15:09:50 Francois: I think that is fine. We'll leave it up to CT proxy vendors. 15:10:03 ...Jo are you OK with that? 15:10:21 Jo: This is another "remaining silent" thing. 15:10:30 -MartinJ 15:10:35 ...It is worth mentioning that the server could give you some clues. 15:10:55 ...If we are going to go with POWDER we should mention it in this section 15:11:10 Francois: Unsure about what we should say about POWDER. 15:11:26 Jo: Should say that these resources do this, those do that, etc. 15:11:46 +MartinJ 15:12:40 Jo: I think we have time. We've have time to find out how we should do the POWDER 15:13:05 Francois: Not sure how to put it in the document given that POWDER does not exist. 15:13:44 Jo: I think we are pretty close to resolving everything we want to put in the document except for the POWDER stuff. 15:14:19 ...I think it is time to go to a FPWD and leave as editorial notes about the richer vocabulary. 15:15:07 PROPOSED RESOLUTION: for ACTION-683, no change in bullet 3 of 3.1.2 15:15:18 PROPOSED RESOLUTION: for ACTION-683, no change in bullet 3 of 3.1.2 save POWDER editorial's note 15:15:48 +1 15:15:51 +1 15:16:04 +1 15:16:12 RESOLUTION: for ACTION-683, no change in bullet 3 of 3.1.2 save POWDER editorial's 15:16:19 Close ACTION-683 15:16:20 ACTION-683 Raise an issue on inferencing from the structure of the URI what assumptions to make about another from the point of view of the CT Proxy closed 15:16:37 Topic: ACTION-684: Bad practice to strip comments in VIA header (§3.1.4) 15:17:21 Francois: You mentioned in 3.1.4 that this reverses HTTP 15:17:45 ...HTTP says the proxy may strip comments. 15:17:57 s/You/Jo, you/ 15:18:17 Jo: It is probably worth finding out why HTTP says this. 15:18:31 ...It seems kind of odd that HTTP says this. 15:18:50 Francois: Good point. I'll ask an HTTP expert. 15:19:12 Jo: Should say that if you are complying with transformation guidelines, you should not strip the comment. 15:19:24 ACTION: daoust to check why HTTP RFC states comments MAY be removed from a VIA header. 15:19:24 Created ACTION-722 - Check why HTTP RFC states comments MAY be removed from a VIA header. [on François Daoust - due 2008-04-01]. 15:20:04 Francois: Jo, do you think you will come up with a note. 15:20:30 Jo: The answer about having the editorial note is yes. 15:20:51 PROPOSED RESOLUTION: Yes we should add a note, pending FD's ACTION-722 15:21:25 PROPOSED RESOLUTION: Yes we should add a note on it being bad practice to strip comments from Via HEader (ACTION-684), pending FD's ACTION-722 15:21:36 +1 15:21:38 +1 15:22:13 PROPOSED RESOLUTION: Yes we should add a note on it being bad practice to strip comments from Via Header (ACTION-684) and that this is not consistent with HTTP, pending FD's ACTION-722 15:22:20 +1 15:22:31 RESOLUTION: Yes we should add a note on it being bad practice to strip comments from Via Header (ACTION-684) and that this is not consistent with HTTP, pending FD's ACTION-722 15:22:40 Topic: ACTION-685: how to embed original headers (§3.1.4) 15:23:04 Francois: I sent an email on Friday about this. 15:23:39 ...Maybe we could address this next week since everyone was on vacation at the end of the week. 15:25:30 Francois: HTTP doesn't say anything about bodies in GET requests. 15:25:35 Jo: I think it does. 15:25:51 Jo: We could do some tests with real web servers. 15:26:48 ...We can test whether if we put an extra thing in a request, existing servers fail. 15:27:20 Francois: We may have to make a test. 15:27:31 Jo: Agreed. 15:27:56 Topic: ACTION-706: Reword §2.5.1 15:27:57 Jo: We'll need to read your email about this and have a discussion next week. 15:28:43 Francois: We had a discussion about control by the user. 15:29:15 -> http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080313#d0e331 2.5.1 15:29:21 ...Jo, you added an editorial note. Do we need to resolve on this? 15:29:38 q+ 15:30:04 Jo: The text of 2.5.1 as it stands was proposed by Bryan. 15:30:24 ack rob 15:30:25 ...I'm wonding if what is in 2.5.1 is strong enough. 15:31:18 Rob: My comment is that some of the CT servers are on particular web sites. They wouldn't bother to set up a session. 15:31:33 ...It is probably best to leave it is "MAY". 15:31:56 Francois: I may agree. 15:32:28 Francois: We agree that static settings are out of scope. 15:32:40 ...What we are really talking about is session settings. 15:33:07 Francois: We'll leave it as a MAY? 15:33:27 Zakim, unmute me 15:33:27 SeanP should no longer be muted 15:33:58 Zakim, mute me 15:33:58 SeanP should now be muted 15:34:10 PROPOSED RESOLUTION: stick to "may" in 2.5.1, and change "persistent" to something less strong 15:35:24 Jo: I think we need to think about what a "session" is. 15:35:39 ...not sure what we mean by session right now. 15:36:28 ...I think 2.5.1 needs to be taken on the list. 15:37:50 ACTION: daoust to raise discussion on session settings vs persistent settings for 2.5.1 and 2.5.3 15:37:50 Created ACTION-723 - Raise discussion on session settings vs persistent settings for 2.5.1 and 2.5.3 [on François Daoust - due 2008-04-01]. 15:38:21 Topic: ACTION-707: Include examples in §2.5.1 bullet 3 15:38:50 Francois: Examples look fine to me. 15:39:07 Close ACTION-707 15:39:07 ACTION-707 Include examples in 2.5.1 bullet 3 per the dicussion above closed 15:39:21 Topic: ACTION-708: Update 2.5.2 15:39:49 ACTION-708? 15:39:49 ACTION-708 -- Jo Rabin to update 2.5.2 in accordance with discussion and Seoul resolution on preferences -- due 2008-03-18 -- OPEN 15:39:49 http://www.w3.org/2005/MWI/BPWG/Group/track/actions/708 15:39:54 Francois: Not sure I remember what this action was about. 15:40:22 ...Was to rewrite section 2.5.2 given what happened a the Seoul F2F 15:41:04 Francois: It was about if the user preferences contradict the server preferences. 15:41:20 ...We do have a resolution on this. 15:42:03 ...Discussed this in the context of that this is the way CSS works. 15:42:34 Jo: we need a better way to say this. 15:43:33 s/...Discussed/Jo: Discussed/ 15:43:36 ACTION: Jo to raise discussion on list as to clarification of 2.5.2 "In cases where user preferences contradict server preferences, server preferences prevail, except where the user specifically requires their preferences to over-rule those of the server." 15:43:36 Created ACTION-724 - Raise discussion on list as to clarification of 2.5.2 \"In cases where user preferences contradict server preferences, server preferences prevail, except where the user specifically requires their preferences to over-rule those of the server.\" [on Jo Rabin - due 2008-04-01]. 15:44:09 Close ACTION-708 15:44:09 ACTION-708 Update 2.5.2 in accordance with discussion and Seoul resolution on preferences closed 15:44:16 Topic: ACTION-709: Write some examples for 2.5.3 15:44:32 -> http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Mar/0018.html fd's proposal 15:44:39 "The preferences of users and of servers MAY be ascertained by means 15:44:39 outside the scope of this document. These means include but are not 15:44:39 limited to: 15:44:39 - the use by transforming proxies of a disallow-list of Web sites for 15:44:39 which content transformation is known to be useless and/or to break 15:44:40 delivered content. 15:44:42 - the use by the transforming proxies of an allow-list of Web sites for 15:44:44 which content transformation is known to be necessary. 15:44:46 - user static preferences, e.g. provisioned by their CT service provider 15:44:48 or directly by the user through self-care web sites. 15:44:50 - terms and conditions of service, as agreed upon between the user and 15:44:52 the CT service provider." 15:44:54 Francois: This is where I had a chat with Bryan about static and persistent settings as opposed to session settings. 15:45:46 ...The third point needs to be re-examined in light of the earlier discussion on this call. 15:45:55 PROPOSED RESOLUTION: remove user static preferences in above text for the time being, and use the resulting text for 2.5.3 under ACTION-709 15:45:55 Jo: These look pretty complete. 15:46:11 +1 15:46:21 RESOLUTION: remove user static preferences in above text for the time being, and use the resulting text for 2.5.3 under ACTION-709 15:46:31 Topic: ACTION-718: re Ajax/XHR requests and CT 15:46:55 -> http://lists.w3.org/Archives/Public/public-bpwg-ct/2008Mar/0028.html fd's thoughts on this 15:46:57 Francois: I raised this problem. 15:47:23 ...I tried to rephrase the discussion about this problem. 15:48:15 ...the XHR request will use the same headers as a normal request, so there is no way to tell if it is XHR request. 15:48:58 ...for simple calls in a web page; it it transformed the page, the CT proxy should know how to handle the request. 15:49:30 ...the problem is for untransformed pages, it doesn't know that an XHR request should not be transformed as well. 15:50:09 ....Martin said that requests and responses should only be transformed when the CT proxy knows that they originated from a transformed request. 15:50:36 ...Bryan said that as a best practice, XHR request should change the UA. 15:50:56 ...Good idea, will be hard to ask all developers to do this. 15:51:24 ...Could recommend that developers add no-transform to XHR request. 15:51:50 Jo: no-transform is consistent with other things we have said in the document. 15:52:09 Francois: We've already said that elsewhere in the document. 15:52:42 Jo: We said we weren't going to discuss clients and users and we are drifting back to that. 15:52:55 ...In this case it may we worth saying something. 15:53:06 Francois: I don't see how we can make it work. 15:53:39 ...How can the proxy determine that calls originate from a page if it did not transform the page. 15:54:55 Francois: Suppose you have a web page that contains too much JavaScript to transform. In the page there are some XHR calls. 15:55:47 ...The CT proxy must be consistent.. It must not transform these XHR calls. There is no real way to detect that it is an XHR call. 15:55:50 q+ 15:55:58 ack SeanP 15:59:13 Francois: It will work in the future. We need to worry about legacy stuff. 15:59:46 Jo: Is this much of an issue. What are the chances that what comes back is in the form that needs to be transformed? 16:00:07 Francois: We may be creating an issue out of nothing. 16:00:20 ...Let me come up with some smarter text on that. 16:00:51 ...I'll come up with something along the lines of a warning about XHR. 16:01:18 Jo: I don't see anywhere in this document about what content types the CT proxy will intervene in. 16:01:31 ...We should put something in about that. 16:02:38 Francois: We mention CT in the list of heuristics for determining whether a page is mobile. 16:03:38 -rob 16:04:03 Jo: It would be interesting to learn what is left alone. 16:04:34 ACTION: SeanP to send a list of content-types for which content transformation applies 16:04:34 Sorry, couldn't find user - SeanP 16:04:39 ACTION: Patterson to send a list of content-types for which content transformation applies 16:04:39 Created ACTION-725 - Send a list of content-types for which content transformation applies [on Sean Patterson - due 2008-04-01]. 16:04:49 s/mention CT/mention content types/ 16:04:50 action- 4 16:05:41 -jo 16:05:42 -MartinJ 16:05:42 -SeanP 16:05:47 RRSAgent, draft minutes 16:05:47 I have made the request to generate http://www.w3.org/2008/03/25-bpwg-minutes.html francois 16:05:49 MartinJ has left #bpwg 16:05:57 zakim, list attendees 16:05:57 As of this point the attendees have been +049238aaaa, +0208995aabb, francois, jo, +0207287aacc, +1.630.414.aadd, rob, +0777613aaee, SeanP, MartinJ, +1.630.773.aaff 16:10:42 disconnecting the lone participant, francois, in MWI_BPWG(CTTF)11:00AM 16:10:46 MWI_BPWG(CTTF)11:00AM has ended 16:10:47 Attendees were +049238aaaa, +0208995aabb, francois, jo, +0207287aacc, +1.630.414.aadd, rob, +0777613aaee, SeanP, MartinJ, +1.630.773.aaff 16:14:42 rob has left #bpwg 16:23:08 RRSAgent, draft minutes 16:23:08 I have made the request to generate http://www.w3.org/2008/03/25-bpwg-minutes.html francois 16:29:09 i/...Maybe we could address this next week since everyone/I do not see any possibility to embed original headers in the generic case without requiring changes on the content providers side/ 16:29:11 RRSAgent, draft minutes 16:29:11 I have made the request to generate http://www.w3.org/2008/03/25-bpwg-minutes.html francois 16:43:37 RRSAgent, bye 16:43:37 I see 4 open action items saved in http://www.w3.org/2008/03/25-bpwg-actions.rdf : 16:43:37 ACTION: daoust to check why HTTP RFC states comments MAY be removed from a VIA header. [1] 16:43:37 recorded in http://www.w3.org/2008/03/25-bpwg-irc#T15-19-24 16:43:37 ACTION: daoust to raise discussion on session settings vs persistent settings for 2.5.1 and 2.5.3 [2] 16:43:37 recorded in http://www.w3.org/2008/03/25-bpwg-irc#T15-37-50 16:43:37 ACTION: Jo to raise discussion on list as to clarification of 2.5.2 "In cases where user preferences contradict server preferences, server preferences prevail, except where the user specifically requires their preferences to over-rule those of the server." [3] 16:43:37 recorded in http://www.w3.org/2008/03/25-bpwg-irc#T15-43-36 16:43:37 ACTION: Patterson to send a list of content-types for which content transformation applies [5] 16:43:37 recorded in http://www.w3.org/2008/03/25-bpwg-irc#T16-04-39