14:56:09 RRSAgent has joined #bpwg 14:56:09 logging to http://www.w3.org/2007/12/04-bpwg-irc 14:56:32 Meeting: BPWG Content Transformation Task Force Teleconference 14:56:41 Date: 2007-12-04 14:56:45 Chair: Jo 14:57:13 Regrets: Bryan 14:58:17 Agenda: http://lists.w3.org/Archives/Public/public-bpwg-ct/2007Dec/0000.html 14:58:57 kemp has joined #bpwg 14:59:57 zakim, code? 14:59:57 the conference code is 2283 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), Magnus 15:00:13 MWI_BPWG(BCTF)10:00AM has now started 15:00:20 +Magnus 15:00:56 +jo 15:01:27 SeanP has joined #bpwg 15:03:27 +SeanP 15:04:00 + +078997aaaa 15:04:21 zakim, aaaa is Andrew 15:04:21 +Andrew; got it 15:06:30 - +078997aaaa 15:08:11 Present: Jo, Magnus, SeanP, Andrew, Aaron_IRC_Only 15:09:18 Scribe: Jo 15:09:30 Topic: HTTP Liaison 15:10:37 + +078997aabb 15:10:47 zakim, aabb is andrew 15:10:47 sorry, jo, I do not recognize a party named 'aabb' 15:10:49 zakim, who is here? 15:10:49 On the phone I see Andrew, jo, SeanP, +078997aaee 15:10:50 On IRC I see SeanP, kemp, RRSAgent, Zakim, jo, Andrew, Magnus, matt, trackbot-ng, dom 15:11:01 zakim, aaee is andrew 15:11:01 +andrew; got it 15:11:18 -> http://lists.w3.org/Archives/Public/public-bpwg-ct/2007Dec/0000.html agenda 15:12:07 Jo: I dropped Mark Nottingham a note but no response yet 15:12:21 ... dom suggested someone in W3C which I will follow up 15:12:27 Topic: Leader 15:13:00 Jo: still no volunteers - I _really_ don't have time to do this! 15:13:18 Magnus: I think you should carry on Jo 15:13:21 jo: :-( 15:13:30 zakim, dial matt-voip 15:13:30 ok, matt; the call is being made 15:13:31 +Matt 15:13:40 zakim, drop matt-voip 15:13:40 sorry, matt, I do not see a party named 'matt-voip' 15:13:43 zakim, drop matt 15:13:43 Matt is being disconnected 15:13:44 -Matt 15:14:01 Topic: Draft 1b 15:14:11 -> http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/071124 Draft 1b 15:14:39 zakim, drop matt 15:14:39 sorry, matt, I do not see a party named 'matt' 15:14:42 zakim, dial matt-voip 15:14:42 ok, matt; the call is being made 15:14:44 +Matt 15:14:48 Magnus: Stand by what I said last week to wit that Chap 2 is a little dry and needs some examples etc. 15:15:53 + +049211aacc 15:17:16 jo: I think we discussed that we'd want to extend HTTP Cache-Control to allow gradations of no-transform 15:17:45 ... OK I don't know that we are ready to RESOLVE this 15:18:08 zakim, aacc is Heiko 15:18:08 +Heiko; got it 15:18:38 ... let's put this to one side for now and look at the requirements 15:19:03 [Heiko joins call and introduces himself] 15:20:02 -> http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/071124#Requirements REquirements Section 15:21:43 Example text for 2.1.1: Some CT proxy implementations may allow end-users to select personal preferences. For example, a CT proxy may allow a user to replace all embedded images with thumbnails. 15:21:45 jo: at 2.1 enable service features - need clarification of what service features means 15:22:10 andrew: select adaptation or not 15:23:25 jo: not sure that we are going to offer such a feature 15:23:25 matt has joined #bpwg 15:24:03 magnus: sure, but this is an example of how it may be elaborated to ease the flow of reading 15:24:39 jo: service features probably means gradation of trancoding features 15:25:10 jo: 2.1.2 "highest quality representation" - this is subjective? no? 15:25:31 hgerlach has joined #bpwg 15:25:34 andrew: highest resolution? 15:26:22 magnus: what he is getting at is to exploit device capabilities rather than go for an LCD approach 15:27:04 heiko: need to set the bar as to whether this is a high tier or low tier which will vary 15:27:49 ... need to decide whether to go for marketing or technical approcah 15:28:05 heiko: not just rely on device capabilities 15:28:54 ... is a mobile phone capable of rendering the content or not, sometimes this is to do with user experience and that is a marketing issue 15:29:09 ScribeNick: Matt 15:29:59 Jo: Yes, that's probably right, but I think the exact nature of how a transforming proxy lays things out is a different issue than say what Magnus has construed it as. (?) 15:30:34 Jo: In 2.1.2, we're saying if a device has capabilities that you can exploit that you should exploit them when you are transforming things. 15:30:58 s/Magnus/Sean/ 15:31:13 s/magnus: what/seanp: what/ 15:31:14 s/magnus: what/sean: What/ 15:32:30 Jo: 2.1.2 "compatible" results in a usable experience. In reflowing this text, I would construe compatible and usable to mean in terms of the DI glossary a "functional experience" -- the user can perceive what the author intended. (vs. a harmonized user experience.) 15:33:08 heiko: We use 'use case completion rate', a number of use cases that must be completed... 15:33:39 Jo: Yes, that's an interesting formalization. How would we get at that in this document? What we're looking for is something that probably doesn't have usecases as such. 15:34:12 heiko: In general you have a use case for any page, any time the user is accessing the page via content-adaptation that the user must be able to complete the use case for that page. 15:34:40 Jo: Yes, that makes sense, except that we have no control over the use cases. We have practically unlimited content -- that is, the Web. I don't think we are intending to write use cases here. 15:34:56 Jo: Any suggestions for scoping as suggested by this sentence? 15:36:04 s/https/https or POSTs 15:36:11 q+ 15:36:12 q+ 15:36:19 heiko: Regarding 2.1.2, the 'highest quality' -- we're never going to give the highest quality, we have to reduce the image size for instance. In the end we're looking for the best on the phone. Never the highest quality. 15:36:19 ack a 15:36:49 Andrew: I take your point, but we should differentiate between optimization (speeding delivery) and content transformation (enabling pages designed for a large screen to be presented on a small screen device). 15:37:05 heiko: Did we define content somewhere before? Maybe this is required somewhere. 15:37:18 Andrew: In my view it's an important differentiation. 15:37:43 Jo: That's not necessarily the case in my view -- that's the heart of why we need relaxation on no-transform. 15:38:06 ack m 15:38:25 [note to change highest quality -> functional user experience] 15:38:40 Magnus: I agree with Heiko, in 2.1.2 it needs to be scoped out for different types of content. For example, image type makes perfect sense to deliver highest quality. Markup itself, we might want to reduce it in size for instance. 15:39:01 Heiko: Nevertheless, we should compress images. 15:39:09 ACTION: Magnus to suggest some text for 2.1.2 15:39:10 Created ACTION-605 - Suggest some text for 2.1.2 [on Magnus Lönnroth - due 2007-12-11]. 15:39:48 Jo: 2.1.3 CT-Awareness. 15:40:10 Heiko: What does CT awareness in browsers mean? 15:40:23 Jo: A browser can make it known to a CT proxy that it is capable of using the guidelines specified in this document. 15:40:33 Jo: i.e. it knows how to do or not do things. 15:40:41 Jo: I'm not sure this is a requirement, but let's leave it in for the time being. 15:41:00 Jo: 2.1.4, user agent id and capabilities disclosure. 15:41:47 Heiko: If we are asking the user to configure the user for it's needs, then we don't need our solution. The user will always be able to solve "how would you like it?" -- if we have a tool it should work without user interaction. 15:42:02 Jo: I think Bryan is saying 'MAY' 15:42:18 q+ 15:42:18 q+ 15:42:22 q? 15:42:52 ack a 15:42:53 zakim, mute me 15:42:53 Matt should now be muted 15:43:39 Andrew: I agree with Heiko, we don't want to push all the decisions to the user. What we're talking about here might be more of a made-for-mobile page vs a desktop page and you might want to give a choice. The majority of the cases the page will be made for one device or another and the CT can be automatically applied. 15:43:43 ack sean 15:44:11 SeanP: I took the 2.1.4 statement to mean that the user can tell the CT Proxy whether they want the desktop or mobile version. 15:44:29 Jo: That's not really what it says though here, is it? I think what Bryan is saying that the user can choose to either have the original user agent disclosed or not. 15:44:48 SeanP: Yes, it does mention user-agent. I was thinking more of the capabilities part, but yes... 15:45:13 Jo: There is a difference between the capabilities of the user-agent and the representation you're going to get. 15:45:53 Jo: Because it's a mobile browser it doesn't mean you always want a mobile presentation, that's not strongly related to the user-agent (except that we know if the user-agent is capable of rendering a desktop representation). I don't think the text is representing that clearly. 15:46:23 Jo: Perhaps a note saying we must be able to make a distinction between what the user wants and forcing a mobile presentation. 15:46:34 Jo: 2.1.5 original representation availability 15:47:10 Heiko: If you are caching the CP response, it may already be depending on the user-agent, so maybe the response is not related when you resend the request. (?) 15:47:57 Jo: I don't think that's what this is saying. 15:48:19 Jo: I think it's just saying if you've done some work on it, you should hang on to it, presumably in case it's required later. But I think I find this section questionable. I'm not sure why this is necessary. 15:48:57 Heiko: When the user goes to some portal and buys the wallpaper for instance. We optimize the wallpaper size, then he'll never have the wallpaper in the resolution he likes, so he must be able to request the original wallpaper. 15:49:10 Jo: Right, but what is missing from this is a mechanism for re-requesting. 15:49:21 Heiko: Well, if you have a one-time URL, it'll be expired... 15:49:47 Jo: For this to be viable I'd have to have a mechanism for "I requested this from you, please give me the original" -- which isn't in HTTP. 15:49:54 Heiko: Today it's done with a reload request. 15:50:19 Heiko: If the user hits reload it sends the original content. 15:50:36 Jo: This is achieved by the browser sending a cache-control: no request, right? 15:50:54 Heiko: The second time it must cache the original response. 15:51:24 ACTION: Heiko to detail reload re: section 2.1.5 original representation availability 15:51:24 Created ACTION-606 - Detail reload re: section 2.1.5 original representation availability [on Heiko Gerlach - due 2007-12-11]. 15:51:29 Action: Heiko to detail what he means by "reload" request on mailing list 15:51:29 Created ACTION-607 - Detail what he means by \"reload\" request on mailing list [on Heiko Gerlach - due 2007-12-11]. 15:52:07 Magnus: I think we could combine 2.1.4 and 2.1.5 so the user could change their preferences, and re-request the document and get the original representation. 15:52:15 Magnus: But is that something we want to cover in the document? 15:52:21 Jo: I think it's getting a bit elaborate. 15:52:23 zakim, unmute me 15:52:23 Matt should no longer be muted 15:53:00 Jo: I think what bothers me is that the proxy has to keep the original representation for some amount of time... there's a lot of complexity in there that we probably won't be able to address at this level. 15:53:39 Jo: The wallpaper case could be handled by having the host know that this shouldn't be reformatted. 15:53:41 Jo: Was hoping to not get into complex protocols... 15:53:43 Magnus: Agreed. 15:54:39 Jo: Let's each send detailed comments to the list on the remaining portions of section 2. 15:54:59 ACTION: All to read and send detailed comments to the list on the remaining portions of section 2. 15:54:59 Sorry, couldn't find user - All 15:55:18 Jo: Adjourned. 15:55:21 zakim, unmute me 15:55:21 Matt was not muted, matt 15:55:49 thanks, bye 15:56:08 s/Magnus/SeanP/ 15:56:31 s/Magnus: But/SeanP: But/ 15:56:38 s/Magnus: I/SeanP: I/ 15:56:44 rrsagent, draft minutes 15:56:44 I have made the request to generate http://www.w3.org/2007/12/04-bpwg-minutes.html matt 15:56:53 rrsagent, make minutes member 15:56:53 I'm logging. I don't understand 'make minutes member', matt. Try /msg RRSAgent help 15:56:57 rrsagent, make minutes member-visible 15:56:57 I'm logging. I don't understand 'make minutes member-visible', matt. Try /msg RRSAgent help 15:57:00 rrsagent, make minutes member-visible 15:57:00 I'm logging. I don't understand 'make minutes member-visible', matt. Try /msg RRSAgent help 15:57:04 rrsagent, make minutes public 15:57:04 I'm logging. I don't understand 'make minutes public', matt. Try /msg RRSAgent help 15:57:07 rrsagent, make logs public 15:58:25 -Andrew 15:58:25 zakim, drop me 15:58:26 Matt is being disconnected 15:58:29 -Matt 15:58:30 -jo 15:58:31 -Heiko 15:58:37 -SeanP 15:58:55 -andrew 15:58:56 MWI_BPWG(BCTF)10:00AM has ended 15:58:57 Attendees were Magnus, jo, SeanP, +078997aaaa, Andrew, +078997aabb, Matt, +049211aacc, Heiko 15:59:02 Scribe: Jo, Matt 15:59:18 Present+ Heiko 15:59:25 rrsagent, draft minutes 15:59:25 I have made the request to generate http://www.w3.org/2007/12/04-bpwg-minutes.html matt 15:59:27 RRSagent, draft minutes 15:59:27 I have made the request to generate http://www.w3.org/2007/12/04-bpwg-minutes.html jo 16:04:42 zakim, excuse us 16:04:42 Zakim has left #bpwg