12:13:16 RRSAgent has joined #bpwg 12:13:16 logging to http://www.w3.org/2008/02/28-bpwg-irc 12:13:20 cool 12:13:28 RRSagent, bye 12:13:49 Hmm 12:13:51 RRSagent, make log public 12:13:55 rrsagent, bye 12:13:55 I see no action items 14:57:40 RRSAgent has joined #bpwg 14:57:40 logging to http://www.w3.org/2008/02/28-bpwg-irc 14:57:42 RRSAgent, make logs public 14:57:42 Zakim has joined #bpwg 14:57:44 Zakim, this will be BPWG 14:57:44 ok, trackbot-ng, I see MWI_BPWG()10:00AM already started 14:57:45 Meeting: Mobile Web Best Practices Working Group Teleconference 14:57:45 Date: 28 February 2008 14:57:48 +Shah 14:57:50 Chair: DKA 14:58:05 Agenda: http://lists.w3.org/Archives/Public/public-bpwg/2008Feb/0157.html 14:58:10 hello... jeffs is lurking on voice-channel 14:58:29 zakim, code? 14:58:29 the conference code is 2794 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), francois 14:59:04 +francois 14:59:46 +??P6 14:59:50 DKA has joined #bpwg 15:00:10 zakim, who's here? 15:00:10 On the phone I see Jeff, Shah, francois, ??P6 15:00:11 On IRC I see DKA, Zakim, RRSAgent, yeliz, jeffs, achuter, jo, matt, francois, trackbot-ng, dom 15:00:15 miguel has joined #bpwg 15:00:23 Present- Matt 15:00:25 zakim, ??P6 is DKA 15:00:25 +DKA; got it 15:00:27 matt has left #bpwg 15:00:33 +jo 15:00:43 Regrets+ Dom 15:00:51 + +1.781.267.aaaa 15:00:53 [Regrets from me, I'm in a conflicting meeting] 15:00:55 MartinJ has joined #bpwg 15:01:09 adam has joined #bpwg 15:01:11 +josema 15:01:39 zakim, josema is me 15:01:39 +miguel; got it 15:01:41 +??P13 15:01:48 Regrets+ drooks, kemp, srowen, EdM, rob, Tony, chaals 15:01:55 zakim, ??P13 is me 15:01:55 +MartinJ; got it 15:01:56 + +0207881aabb 15:01:56 abel has joined #bpwg 15:01:56 zakim, abel is with me 15:01:57 +abel; got it 15:01:58 +??P19 15:01:59 - +0207881aabb 15:02:01 zakim, mute 15:02:01 I don't understand 'mute', achuter 15:02:05 zakim, nacho is with me 15:02:05 +nacho; got it 15:02:06 zakim, mute me 15:02:06 sorry, achuter, I do not know which phone connection belongs to you 15:02:11 nacho has joined #bpwg 15:02:12 zakim, who's on the phone? 15:02:12 On the phone I see Jeff, Shah, francois, DKA, jo, +1.781.267.aaaa, miguel, MartinJ, ??P19 15:02:13 AlanT has joined #bpwg 15:02:14 miguel has miguel, abel, nacho 15:02:27 zakim, who is making noise? 15:02:29 +??P17 15:02:31 -??P19 15:02:35 + +0207881aacc 15:02:37 jo, listening for 10 seconds I heard sound from the following: francois (50%), ??P17 (27%), ??P19 (31%) 15:02:43 zakim, ??P19 is achuter 15:02:44 I already had ??P19 as +049303aacc, francois 15:02:49 zakim, aacc is me 15:02:49 +adam; got it 15:02:59 skarim has joined #bpwg 15:03:00 zakim, who's on the phone? 15:03:00 On the phone I see Jeff, Shah, francois, DKA, jo, +1.781.267.aaaa, miguel, MartinJ, ??P17, adam 15:03:00 Emmanuel has joined #bpwg 15:03:03 miguel has miguel, abel, nacho 15:03:18 zakim, aaaa is adam 15:03:18 +adam; got it 15:03:18 zakim, aacc is Adam 15:03:19 sorry, jo, I do not recognize a party named 'aacc' 15:03:29 +Kai 15:03:37 zakim, who is on the call? 15:03:37 On the phone I see Jeff, Shah, francois, DKA, jo, adam.a, miguel, MartinJ, ??P17, adam, Kai 15:03:39 miguel has miguel, abel, nacho 15:03:57 Kai has joined #bpwg 15:04:29 +??P28 15:04:34 zakim, ??P28 is me 15:04:34 +achuter; got it 15:04:51 zakim, who is here? 15:04:51 On the phone I see Jeff, Shah, francois, DKA, jo, adam.a, miguel, MartinJ, ??P17, adam, Kai, achuter (muted) 15:04:53 miguel has miguel, abel, nacho 15:04:54 On IRC I see Kai, Emmanuel, skarim, AlanT, nacho, abel, adam, MartinJ, miguel, DKA, Zakim, RRSAgent, yeliz, jeffs, achuter, jo, francois, trackbot-ng, dom 15:05:42 zakim, ??P17 is Yeliz 15:05:42 +Yeliz; got it 15:05:54 zakim, mute yeliz 15:05:54 Yeliz should now be muted 15:06:14 Noting potential additional agenda points for today: content tasting and modification of HTTP headers, the use of POWDER (in context of CT Task Force). Francois has suggested these might be useful to answer before the f2f next week. 15:06:27 zakim, who is here? 15:06:27 On the phone I see Jeff, Shah, francois, DKA, jo, adam.a, miguel, MartinJ, Yeliz (muted), adam, Kai, achuter (muted) 15:06:29 miguel has miguel, abel, nacho 15:06:31 On IRC I see Kai, Emmanuel, skarim, AlanT, nacho, abel, adam, MartinJ, miguel, DKA, Zakim, RRSAgent, yeliz, jeffs, achuter, jo, francois, trackbot-ng, dom 15:06:49 Chair: Jo 15:07:00 I can scribe. 15:07:15 Topics: Administrivia 15:07:25 Topic: US clock change 15:07:35 PROPOSED RESOLUTION: BPWG Call to stay on Euro Time till March 30th 15:07:48 Jo: We won't be having a call next week - the next call will be the 13th. 15:07:59 + +1.703.265.aadd 15:08:12 Jo: Proposal to stay on european time - GMT - during the US time change. 15:08:15 zakim, aadd is AlanT 15:08:15 +AlanT; got it 15:08:29 RESOLUTION: BPWG Call to stay on Euro Time till March 30th 15:08:54 Topic: Decision on Zaragoza 15:08:57 ACTION: daoust to make sure next calls will stick to european time 15:08:57 Created ACTION-675 - Make sure next calls will stick to european time [on François Daoust - due 2008-03-06]. 15:09:12 Jo: We had to make a decision quickly and the results of the poll point to 16-20 of June. 15:09:19 Jo: Registration will start soon. 15:09:59 Nacho: the formal decisions have happened from both bp and dd groups. Right now I'm waiting for some information and I will send the details to the list next week. 15:10:01 Jo: Thanks. 15:10:28 Topic: Task force report: Content Transformation 15:10:43 -> http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/CT/editors-drafts/Guidelines/080227 latest draft 15:10:54 Francois: I would like to present the latest draft to the working group. 15:11:17 Francois: Summarizing: what needs to be done before we go to fpwd and afterwards. 15:11:28 Francois: We had a lot of discussion on scope and this is what we agreed. 15:12:18 Francois: First, [burst of music], extending http for communications between the different actors is not the way to go - it's beyond our charter and http isn't open for modifications - not flexible enough. 15:12:47 Francois: The big CT picture could take into account OMA DPE, W3C DCCI, or Powder. 15:13:09 Francois: So we decided to stick with existing technologies and try to avoid new http headers. It's not settled if we need one or not at the moment. 15:14:08 Francois: As legacy browsers are the target for the moment, we decided to leave the browser aside and so communications between CT proxy and user must be through web pages. Future browsers may add cache-control no-transform header. 15:14:26 Francois: These are the two main points. Now there are 2 things that need to be answered before fpwd. 15:15:11 Francois: First is regarding the way the CT proxy works. We haven't had time in the last call to take a resolution. How should the proxy work - should it do "content tasting" - sending an http request, looking at the answer to see if it is correct? 15:15:37 Francois: Does it have to change the user agent? If there is no need to change the user agent, then we probably don't need any additional http headers. 15:15:55 "tasting" should read "testing" 15:16:45 Francois: Second big question: something introduced in last draft - use of POWDER. POWDER could be used on the server side. 15:17:22 q+ to say that this depends on how DRs are discoverable 15:17:35 Francois: do we have a dependency on powder or do we just want to reference powder. It doesn't exist - it's at fpwd at the moment. So we might run into the same problem we've had with xhtml basic - waiting for Powder. 15:18:05 Magnus has joined #bpwg 15:18:21 ack k 15:18:21 Kai, you wanted to say that this depends on how DRs are discoverable 15:18:43 +Magnus 15:18:49 Kai: Info on POWDER - we have 2 types of documents, the web resoruce and the description that describes the web resource. 15:18:58 Kai: We are discussing URI schemes. 15:20:10 Kai: wrt content tasting, 2 ways to do it - look at the resource itself or look at the description resources. Because of the problems we've discovered with numerical URIs, it is under discussion to close off tasting through tasting descripion resources but this is not prefered. 15:20:38 Jo: Any other questions on POWDER or CT? 15:20:56 Jo: I think we're going to spend some time in Korea discussing these issues. 15:21:24 Jo: We may not be able to take resolutions in Korea but we will be able to make some progress in workshopping these issues. 15:21:48 Topic: MobileOK Pro 15:22:33 Kai: draft is finished. It's out there, please look at it. In the mail I posted I mentioned the task force would ask the main group to make this a fpwd. 15:23:05 Kai: also emulator code has been pasdsed to Dave Rooks. 15:23:19 Kai: Progress has been good. 15:23:35 Jo: We'll be addressing this also in Korea. 15:23:48 -> http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/mobileOKPro/drafts/ED-mobileOK-pro10-tests-20080228 mobileOK Pro doc 15:24:25 Topic: Korea F2F Agenda Discussion 15:24:41 -> http://docs.google.com/Doc?id=dd3jk8v_89f6vrqk9w Draft Agenda for F2F 15:25:34 DKA: I put together an agenda. Problem is we'll have a restricted number of participants. I included some time to get input from Korean people 15:25:46 ... to see what would be useful to have in BP2.0 15:26:10 ... some time for the CT TF, mobileOK Pro TF 15:26:33 ... The more time we can spend flushing things in documents, the better 15:26:57 ... as opposed to taking resolutions as we'll be a small number of participants 15:27:52 q+ 15:27:55 q- 15:28:29 Topic: Accessibility 15:28:41 Jo: Where did we get to? 15:28:45 Alan: Tab order. 15:28:50 http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/Accessibility/drafts/ED-mwbp-wcag-20080129/mwbp-wcag20.html#TAB_ORDER 15:30:13 Jo: Any comments? 15:30:19 Jo: Tables_alternatives 15:30:25 aconnors has joined #bpwg 15:30:40 Alan: this one is odd but some users might find it more complicated. 15:30:42 q+ 15:31:00 q- 15:31:02 Alan: This is in the mobile context use an alternative not on all contexts. 15:31:22 q+ 15:31:33 ack k 15:31:57 Kai: [censored] 15:32:43 Jo: We need to say that there is no added benefit for users with disabilities and move on. I think we should remain silent on whether it makes it more difficult for users with disabilities. 15:32:49 Jo: let's move on to tables_layout 15:33:06 Alan: there are 2 aspecst - using a table for layout might cause incorrect reading order. 15:33:33 Alan: If you use tables for layout, it's difficult for the user to modifyt the layout by using their own stylesheet. 15:33:54 Jo: Most mobile browsers do support tables so the comment about non-support might not be correct. 15:34:01 do not use tables for layout 15:34:18 Jo: Moving on to nested_tables 15:34:25 +1 15:34:41 tables_nested 15:35:14 Alan: if tables are nested for layout then for a screen reading user it makes it very confusing. So it's best avoided. 15:35:36 -MartinJ 15:35:44 Jo: Other comments on tables_nested? 15:35:51 Jo: Tables_support? 15:35:56 Jo: No added benefit. 15:35:58 Alan: yes. 15:36:01 Jo: testing. 15:36:18 [long pause] 15:36:46 Jo: It helps to some degree but it won't give you a benefit. 15:36:50 Jo: Other comments? 15:36:55 Jo: Thematic Consistency? 15:36:56 +??P10 15:37:44 Jo: I think this could do with more. Can we put a pin in this discussion and we can raise an issue on the list to discuss it? 15:37:53 zakim, ??P10 is me 15:37:53 +MartinJ; got it 15:38:03 Alan: the concept is the same - access the same content from a range of devices and also with a range of user abilities. 15:39:37 ACTION: achuter Discuss on the list THEMATIC_CONSISTENCY 15:39:37 Created ACTION-676 - Discuss on the list THEMATIC_CONSISTENCY [on Alan Chuter - due 2008-03-06]. 15:39:40 Jo: The point of the best practice is the other way around - what we're saying you shouldn't do is to provide pages with different meanings from the same URI depending on the circumstances of the access. Example of bbc.co.uk/mobile which provides mobile-friendly content if you're on a mobile devices and instructions for use of mobile if you're on a PC - this is not best practice. 15:39:46 Jo: Moving on - URIs. 15:40:18 Alan: Users especially with motor disabilities might have difficulty typing them in the same way that a user of a mobile device has trouble typing them on a keypad. 15:40:25 Jo: Anybody got anything else? 15:40:31 zakim, unmute yeliz 15:40:31 Yeliz should no longer be muted 15:40:31 Jo: Moving on - use of color. 15:41:14 add anything on greyscale? 15:41:18 if you are curious http://www.w3.org/2005/MWI/BPWG/Group/TaskForces/mobileOKPro/drafts/ED-mobileOK-pro10-tests-20080228#use_of_color 15:41:22 Alan: User of the mobile device might not see the color because of bad ambient lighting, other users might not see the color at all either because they can't see or because they have color perception deficits. So it's comon cause. 15:41:43 I am only on IRC not dialed into call 15:41:59 Jeff: Putting in 2 worth - choosing colors that go to greyscale properly. 15:42:13 Jo: We don't have that in BP1 but maybe we could put it in BP2. 15:42:21 Jeff: Yes I tell my students there. 15:42:29 I suggest you send something to the list on that, Jeff? 15:42:52 will send something to list on color choices and decay to greyscale 15:42:54 Alan: it's not about using high contrast colors but rather not using colors to convey information (e.g. red means stop). 15:42:58 Thanks. 15:43:25 Jo: We had a formula in the BP document but we removed it at one point. 15:43:58 Under URIS change d in WCAG 1.0. to 2.0 15:44:05 Yeliz: UI wanted to say about keep URIs of entry points short - that should refer to 2.0 not 1.0. 15:44:19 Jo: Valid Markup - last one of the document. 15:44:39 Regrets+ hgerlach 15:44:56 zakim, mute yeliz 15:44:56 Yeliz should now be muted 15:44:56 Alan: This one corresponds to a 1.0 checkpoint but at 2.0 they removed requirement for valid code at one stage and then changed it to "Well formed" markup. 15:45:21 Alan: The arguments in the wcag working group is that it doesn't give accessibilty benefit. Does it bring a benefit or not? 15:45:33 Jo: I don't think it's for us to judge. 15:45:43 Jo: It does give you WCAG (1.0) compliance. 15:45:57 Alan: Yes but it's hard to justify whether it brings benefits to users with disabilities. 15:46:11 s/(1.0)/(2.0)/ 15:46:27 Jo: We're done with that document for now. 15:47:01 Jo: You're able to make changes now you've been waiting to make. Yeliz made some contributions and those can be folded in as well. OK? 15:47:09 Jo: Thanks again, Alan. 15:47:31 Jo: BP 2.0 - discussion of recent inputs on the mailing list. 15:47:52 Topic: BP 2.0 15:48:59 DKA: Have RIT done anything on scripting that we could bring into next week's f2f? 15:49:46 q+ 15:50:11 Jeff: I don't know that I have anything concrete to contribute until what scripting. 15:50:45 Jeff: Seperate javascript into seperate files for PC sites and for mobile it makes more sense to put it inline. 15:51:10 Jeff: I'll try to get some some written materials to the list by the weekend. 15:51:22 ack ac 15:51:52 [Adam's mail on AJAX being an opportunity to reduce network access problems took me aback, but sounds very interesting to me] 15:51:59 [dom's random thought of the day] 15:52:15 Adam: one suggestion was not to build the DOM on device but to send the whole html vs building the DOM on the device - trade offs there where it might make sens to do some experimentation. 15:52:19 will go for obvious general-level javascript BP, like inline vs separate files etc... 15:52:27 DKA: that sounds relevant. 15:54:17 [in response to Dom's, Jo's random thought is that the best place to that into account "dynamic" properties of the device is in the client and not to use OMA DPE] 15:54:17 Adam: I could do a simple test case for this. 15:54:39 s/to that into/to take into/ 15:55:02 DKA: Could Francois set up a space for the bp 2.0 doc test cases? 15:56:16 ACTION: Dan to create an issue to start bringing together potential test cases. 15:56:16 Created ACTION-677 - Create an issue to start bringing together potential test cases. [on Daniel Appelquist - due 2008-03-06]. 15:56:23 Jo: I'm going to end the meeting there. 15:56:28 Enjoy Seoul!! I would like to be there. 15:56:37 Jo: That's it. Bye! 15:56:37 bye 15:56:39 byee 15:56:39 Bye! 15:56:40 -adam 15:56:41 yes 15:56:41 -Kai 15:56:41 -Shah 15:56:42 bye 15:56:43 -Jeff 15:56:43 -francois 15:56:44 -achuter 15:56:45 -DKA 15:56:46 -Yeliz 15:56:47 -adam.a 15:56:48 abel has left #bpwg 15:56:49 -miguel 15:56:51 -AlanT 15:56:53 -jo 15:57:00 nacho has left #bpwg 15:57:01 -Magnus 15:57:05 yeliz has left #bpwg 15:57:06 zakim, adam.a is really Magnus 15:57:06 sorry, francois, I do not recognize a party named 'adam.a' 15:57:14 zakmi, list attendees 15:57:18 oops i left 15:57:18 zakim, list attendees 15:57:18 As of this point the attendees have been Jeff, Shah, francois, DKA, jo, +1.781.267.aaaa, miguel, MartinJ, +0207881aabb, abel, nacho, +0207881aacc, adam, Kai, achuter, Yeliz, 15:57:21 ... +1.703.265.aadd, AlanT, Magnus 15:58:11 -MartinJ 15:58:13 MWI_BPWG()10:00AM has ended 15:58:15 Attendees were Jeff, Shah, francois, DKA, jo, +1.781.267.aaaa, miguel, MartinJ, +0207881aabb, abel, nacho, +0207881aacc, adam, Kai, achuter, Yeliz, +1.703.265.aadd, AlanT, Magnus 15:58:25 RRSAgent, draft minutes 15:58:25 I have made the request to generate http://www.w3.org/2008/02/28-bpwg-minutes.html francois 15:58:40 MartinJ has left #bpwg 16:21:15 skarim has left #bpwg 16:26:40 jo has left #bpwg 16:46:22 RRSAgent, bye 16:46:22 I see 3 open action items saved in http://www.w3.org/2008/02/28-bpwg-actions.rdf : 16:46:22 ACTION: daoust to make sure next calls will stick to european time [1] 16:46:22 recorded in http://www.w3.org/2008/02/28-bpwg-irc#T15-08-57 16:46:22 ACTION: achuter Discuss on the list THEMATIC_CONSISTENCY [2] 16:46:22 recorded in http://www.w3.org/2008/02/28-bpwg-irc#T15-39-37 16:46:22 ACTION: Dan to create an issue to start bringing together potential test cases. [3] 16:46:22 recorded in http://www.w3.org/2008/02/28-bpwg-irc#T15-56-16 16:46:25 Zakim, bye 16:46:25 Zakim has left #bpwg