13:28:06 RRSAgent has joined #bpwg 13:28:06 logging to http://www.w3.org/2009/07/07-bpwg-irc 13:28:08 RRSAgent, make logs public 13:28:08 Zakim has joined #bpwg 13:28:10 Zakim, this will be BPWG 13:28:10 ok, trackbot; I see MWI_BPWG()9:30AM scheduled to start in 2 minutes 13:28:11 Meeting: Mobile Web Best Practices Working Group Teleconference 13:28:11 Date: 07 July 2009 13:29:13 MWI_BPWG()9:30AM has now started 13:29:13 cgi-irc has joined #bpwg 13:29:20 +DKA 13:29:31 zakim,code? 13:29:31 the conference code is 2794 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), adam 13:29:39 miguel has joined #bpwg 13:29:41 DKA has joined #bpwg 13:29:53 zakim, who's here? 13:29:53 On the phone I see DKA 13:29:54 On IRC I see DKA, miguel, adam, Zakim, RRSAgent, yeliz, francois, trackbot 13:30:01 +adam 13:30:13 Agenda: http://lists.w3.org/Archives/Public/public-bpwg/2009Jul/0010.html 13:30:16 Chair: DKA 13:30:54 Regrets: nacho, jeff, abel, brucel, achuter, tom, phila 13:31:33 +Francois 13:31:46 EdC has joined #bpwg 13:32:00 SeanP has joined #bpwg 13:32:24 zakim, who's here? 13:32:24 On the phone I see DKA, adam, Francois 13:32:26 On IRC I see SeanP, EdC, DKA, miguel, adam, Zakim, RRSAgent, yeliz, francois, trackbot 13:32:40 +??P1 13:32:47 zakim, ??P1 is yeliz 13:32:47 +yeliz; got it 13:32:56 zakim, mute me 13:32:56 yeliz should now be muted 13:33:14 +miguel 13:33:30 +SeanP 13:34:24 +EdC 13:34:59 Scribe: francois 13:35:26 Regrets+ chaals 13:36:14 jo has joined #bpwg 13:36:21 zakim, code? 13:36:21 the conference code is 2794 (tel:+1.617.761.6200 tel:+33.4.89.06.34.99 tel:+44.117.370.6152), jo 13:36:36 Topic: Administrativa 13:36:42 DKA: do we still have a WG? 13:36:57 -> http://lists.w3.org/Archives/Member/member-bpwg/2009Jul/0001.html FD's announcement of charter extension 13:36:59 + +0208995aaaa 13:37:11 zakim, aaaa is me 13:37:11 +jo; got it 13:37:28 francois: charter extension approved until the end of the year! 13:37:30 /me is happy to have his existential doubts settled 13:37:35 dka: happy to exist. 13:38:15 dka: question about calls during summer period. I'll be away end of July beginning of August. 13:38:28 ... That does not necessarily entail we need to cancel the calls. 13:38:36 Should we poll people present? 13:39:06 francois: Yes, I'll be away next two weeks. 13:39:34 dka: I just want to avoid having a call scheduled and people end up waiting for other participants to join. 13:39:52 I have no plans to be absent in the coming 5 weeks. 13:40:05 /me is away from July 29 to Aug 17 13:40:17 ... Francois, do you think you can set up a poll? 13:40:54 francois: sure. One thing is that if Jo and Dan are both away, we should cancel the corresponding call(s). BPWG can't survive without chairs. 13:41:04 ACTION-986? 13:41:04 ACTION-986 -- François Daoust to enquires as to status of CSS Media Queries Rec -- due 2009-07-07 -- PENDINGREVIEW 13:41:04 http://www.w3.org/2005/MWI/BPWG/Group/track/actions/986 13:41:11 Topic: Use of media queries 13:41:37 -> http://lists.w3.org/Archives/Public/public-bpwg/2009Jul/0009.html Status of CSS media queries 13:41:52 dka: let's start with ACTION-986 on francois 13:41:55 ACTION-986? 13:41:55 ACTION-986 -- François Daoust to enquires as to status of CSS Media Queries Rec -- due 2009-07-07 -- PENDINGREVIEW 13:41:55 http://www.w3.org/2005/MWI/BPWG/Group/track/actions/986 13:43:52 francois: the important point is that the CSS media queries spec is not blocked for lack of implementations. 13:44:06 ... There are some in mobile browsers although not in all browsers, for sure. 13:44:25 ... It really depends on what we want to put in the best practices. 13:44:34 Shouldn't the BP have a caveat regarding the implementation of various query elements, i.e. "device-width" vs. "color" or "orientation" ? 13:44:58 dka: Some people wanted to remove all mentions to CSS media queries. I think it should be emphasized for mobile developers. 13:45:22 adam: What is it that we want to specifically call out about CSS media queries? 13:45:57 dka: I think it is particularly relevant to mobile developers, because it allows to use specific device capabilities. 13:46:22 ... it's not particularly dynamic capabilities, but still a good thing to have. 13:46:57 adam: OK. I think the possibilities are pretty limited for me as a developer, but I agree. 13:47:39 q+ 13:48:16 ack jo 13:48:37 dka: francois, do you think you can take an action to craft some text? 13:48:56 I suspect that device-width is generally supported in CSS media queries because of other elements such as viewport. 13:49:18 francois: Sure. I think I agree with Adam that it's not that super useful. Some properties are not exactly supported, and the possibilities are not super wow. 13:49:43 q+ 13:49:43 jo: I think it's actually not a best practice. 13:50:41 ... If Dan can have the tons of developers he knows that consider use of CSS media queries as a best practice to explain how they use it. 13:50:48 ... that would be great. 13:50:59 ack edc 13:51:33 q+ 13:51:39 EdC: CSS media queries are only useful in the context of viewports. 13:52:43 dka: ok, why don't you give me an action to see how people use CSS media queries around here? 13:52:57 ... and an action on Francois to craft some nominal text on CSS media queries. 13:53:56 adam: I think francois should not spend time for the time being. Let's fine people who use it in practice. 13:54:23 ... If you can find somebody who has some insight here, then that would be useful. 13:54:24 Q+ 13:54:35 dka: I'm happy to take an action. 13:55:03 ACTION: dan to find people who use CSS media queries to tell whether it's a BP 13:55:03 Created ACTION-994 - Find people who use CSS media queries to tell whether it's a BP [on Daniel Appelquist - due 2009-07-14]. 13:55:03 ack francois 13:55:52 http://www.w3.org/2005/MWI/BPWG 13:55:52 q- 13:57:04 francois: just to note that BPWG's home page actually uses CSS media queries to send different stylesheets depending on the incoming devices. 13:57:15 dka: OK, that's one data point. 13:57:29 q+ 13:57:42 adam: I still need to update a few links in the document. 13:57:43 Wasn't there a long-standing issue with canvases and svg? 13:58:04 jo: I have some typos for you, adam. There's also quite a few open actions and issues against this document. 13:58:12 ... We need to resolve them. 13:58:29 adam: Yes. There's also some SVG/canvas issue opened on Jeff. 13:59:15 dka: Is there anything that prevents us from resolving the issues? 13:59:21 ... Let's try to enumerate them. 14:00:16 jo: let me paste the URI to the opened issues and actions. 14:00:16 http://www.w3.org/2005/MWI/BPWG/Group/track/products/14 14:01:34 Topic: ISSUE-262 14:01:37 ISSUE-262? 14:01:37 ISSUE-262 -- Discuss the option to offer choices of presentation as a best practices for mobile web apps -- OPEN 14:01:37 http://www.w3.org/2005/MWI/BPWG/Group/track/issues/262 14:01:45 dka: Is this something that we can close? 14:02:07 Isn't 262 handled somehow in the practice re: classes of devices? 14:02:08 adam: can somebody summarize what it means? 14:02:28 http://www.w3.org/2005/MWI/BPWG/Group/Drafts/BestPractices-2.0/ED-mobile-bp2-20090619#d1e1515 14:03:17 dka: the issue is whether the "Use Device Classification to Simplify Content Adaptation" is a best practice or not. 14:03:26 adam: the Google's home page does this. 14:03:39 dka: I don't think this is very controversial, actually. 14:03:44 ... I suggest that we resolve it. 14:04:10 PROPOSED RESOLUTION: CLose issue-262 and keep section 3.6.5 in mwabp. 14:04:19 s/Use Device Classification to Simplify Content Adaptation/Offer Users a Choice of Interfaces/ 14:04:23 +1 14:04:26 +1 14:04:28 +1 14:04:28 +1 14:04:30 +1 14:04:41 +1 14:04:53 RESOLUTION: CLose issue-262 and keep section 3.6.5 in mwabp. 14:04:56 +1 14:05:01 RESOLUTION: CLose issue-262 and keep section 3.6.5 in mwabp. 14:05:04 close ISSUE-262 14:05:04 ISSUE-262 Discuss the option to offer choices of presentation as a best practices for mobile web apps closed 14:05:37 Topic: ISSUE-263 - how to keep the screen alive? 14:05:43 ISSUE-263? 14:05:43 ISSUE-263 -- How to keep the screen alive (re null gestures) - what to recommend? -- OPEN 14:05:43 http://www.w3.org/2005/MWI/BPWG/Group/track/issues/263 14:05:56 dka: I suggest that we close it. We didn't go anywhere. 14:06:11 adam: I think it would rather be a bad practice to keep the screen alive. I'd rather close this. 14:06:41 PROPOSED RESOLUTION: We close issue-263 and drop the idea of keeping the screen alive as a bp. 14:06:46 +1 14:06:50 +1 14:06:54 +1 14:06:55 0 14:06:56 +1 14:07:28 dka: Yes, this would be left to implementations. 14:07:38 RESOLUTION: We close issue-263 and drop the idea of keeping the screen alive as a bp. 14:07:46 close issue-263 14:07:46 ISSUE-263 How to keep the screen alive (re null gestures) - what to recommend? closed 14:08:00 Topic: ISSUE-264 - progressive enhancement 14:08:17 adam: I think this was done when I rewrote the section on the delivery context. 14:08:22 ... So that's complete. 14:08:25 PROPOSED RESOLUTION: Close Issue-264 as it has been completed. 14:08:28 +1 14:09:09 http://www.w3.org/TR/mwabp/#bp-devcap-scripting (captures aspects of the original concept) 14:09:24 +1 14:09:27 +1 14:09:46 RESOLUTION: Close Issue-264 as it has been completed. 14:09:57 0 14:10:09 close ISSUE-264 14:10:09 ISSUE-264 How to rephrase progressive enhancement to make it fit as a BP? closed 14:10:27 ISSUE-265? 14:10:27 ISSUE-265 -- Discussion of Jonathan's Submission ref separation of structure presentation and behavior at http://docs.google.com/View?docid=dhpvgnmn_54d7cbhrhn -- OPEN 14:10:27 http://www.w3.org/2005/MWI/BPWG/Group/track/issues/265 14:10:29 Topic: ISSUE-265 - Jonathan's submission 14:10:39 adam: I had an action to respond to this. 14:11:10 ... I should just complete my action and respond, I guess. 14:11:39 dka: I think we should close the issue and leave you finish your action. 14:11:39 PROPOSED RESOLUTION: close issue-265 and keep Adam's action open to write up a note to Jonathan why he does not think this makes it as a best practice. 14:11:48 +1 14:11:56 +1 14:12:13 +1 14:12:16 RESOLUTION: close issue-265 and keep Adam's action open to write up a note to Jonathan why he does not think this makes it as a best practice 14:12:22 close issue-265 14:12:22 ISSUE-265 Discussion of Jonathan's Submission ref separation of structure presentation and behavior at http://docs.google.com/View?docid=dhpvgnmn_54d7cbhrhn closed 14:12:40 Topic: ISSUE-268 - Test cases to illustrate MWABP 14:12:47 ISSUE-268? 14:12:47 ISSUE-268 -- Test cases to illustrate mobile web application best practices -- OPEN 14:12:47 http://www.w3.org/2005/MWI/BPWG/Group/track/issues/268 14:12:51 q+ 14:12:56 ack francois 14:13:10 ack me 14:13:14 ACTION-721? 14:13:14 ACTION-721 -- François Daoust to prepare a report's form to fill to test Aaron static/dynamic example -- due 2008-08-14 -- OPEN 14:13:14 http://www.w3.org/2005/MWI/BPWG/Group/track/actions/721 14:13:45 francois: I miserably failed to complete my action here 14:13:55 PROPOSED RESOLUTION: We abandon action-721 and issue-268 for this version of the Mobile Web Application Best Practices and defer it to v2. 14:14:03 ... I suggest we drop it. It was supposed to be the start of a complete testing framework. 14:14:27 adam: It would not be trivial to do it. 14:14:28 PROPOSED RESOLUTION: We abandon action-721 and issue-268 for this version of the Mobile Web Application Best Practices. 14:14:33 +1 14:14:34 +1 14:14:36 +1 14:14:47 +1 (I wish we had more bench-marking / testing but it would be a very big task). 14:15:25 RESOLUTION: We abandon action-721 and issue-268 for this version of the Mobile Web Application Best Practices. 14:15:34 close ACTION-721 14:15:34 ACTION-721 Prepare a report's form to fill to test Aaron static/dynamic example closed 14:15:39 close ISSUE-268 14:15:39 ISSUE-268 Test cases to illustrate mobile web application best practices closed 14:15:59 ISSUE-279? 14:15:59 ISSUE-279 -- 4.3.3 Provide Disclosures that are Timely and Accessible -- OPEN 14:15:59 http://www.w3.org/2005/MWI/BPWG/Group/track/issues/279 14:16:03 dka: [mumbling about mobileAppOK] 14:16:26 Topic: ISSUE-279 - Provide timely disclosures 14:16:33 adam: I think this is done. 14:16:35 ACTION-861? 14:16:35 ACTION-861 -- Bryan Sullivan to propose text ref ISSUE-279 -- due 2008-10-15 -- OPEN 14:16:35 http://www.w3.org/2005/MWI/BPWG/Group/track/actions/861 14:16:46 dka: is the action completed? 14:16:59 adam: yes, I think Bryan did that. 14:17:13 PROPOSED RESOLUTION: The text has moved on since the points in ISSUE-279 were made so we will close ISSUE-279 and ACTION-861. 14:17:27 So these are no longer relevant... 14:17:27 +1 14:17:29 +1 14:17:32 +1 14:17:44 q? 14:17:53 RESOLUTION: The text has moved on since the points in ISSUE-279 were made so we will close ISSUE-279 and ACTION-861. 14:17:58 close ISSUE-279 14:17:58 ISSUE-279 4.3.3 Provide Disclosures that are Timely and Accessible closed 14:18:02 close ACTION-861 14:18:02 ACTION-861 Propose text ref ISSUE-279 closed 14:18:22 Topic: ISSUE 280 - User awareness and control 14:18:26 ISSUE-280? 14:18:26 ISSUE-280 -- 3.3 User awareness and control -- OPEN 14:18:26 http://www.w3.org/2005/MWI/BPWG/Group/track/issues/280 14:18:39 adam: same here, it predates the discussion we had during last F2F. I think it can be safely closed. 14:19:07 PROPOSED RESOLUTION: The text has moved on since the points made in ISSUE-280 so we will close ISSUE-280. 14:19:13 +1 14:19:19 +1 14:19:19 0 14:19:50 RESOLUTION: The text has moved on since the points made in ISSUE-280 so we will close ISSUE-280. 14:19:55 ISSUE-281? 14:19:55 ISSUE-281 -- MWA should disclose their capabilities in HTTP requests, to allow service adaptation -- OPEN 14:19:55 http://www.w3.org/2005/MWI/BPWG/Group/track/issues/281 14:19:56 close ISSUE-280 14:19:56 ISSUE-280 3.3 User awareness and control closed 14:20:41 adam: It's been dormant for some time now. 14:20:49 ... It's out of scope. 14:20:57 PROPOSED RESOLUTION: WRT ISSUE-281, this is out of scope for MWABP so we will close ISSUE-281 and take no action. 14:21:01 +1 14:21:02 ... I'm for closing it 14:21:05 +1 14:21:25 +1 14:21:33 i/adam: It's/Topic: ISSUE-281 - capabilities disclosure in HTTP requests/ 14:21:37 RESOLUTION: WRT ISSUE-281, this is out of scope for MWABP so we will close ISSUE-281 and take no action. 14:21:40 close ISSUE-281 14:21:40 ISSUE-281 MWA should disclose their capabilities in HTTP requests, to allow service adaptation closed 14:21:42 ISSUE-287? 14:21:43 ISSUE-287 -- Propose merging 3.1.1 and 3.1.2 in MWABP -- OPEN 14:21:43 http://www.w3.org/2005/MWI/BPWG/Group/track/issues/287 14:21:59 Topic: ISSUE-287 - merging 3.1.1 and 3.1.2 14:22:09 dka: does this still make sense? 14:22:25 no longer relevant => close it. 14:22:28 adam: instead of merging, we replaced them with application data. So the topic's moot. 14:22:40 PROPOSED RESOLUTION: Issue-287 is moot so we will close issue-287. 14:22:43 +1 14:22:53 +1 14:23:16 +1 14:23:17 +1 14:23:18 RESOLUTION: Issue-287 is moot so we will close issue-287. 14:23:21 close ISSUE-287 14:23:21 ISSUE-287 Propose merging 3.1.1 and 3.1.2 in MWABP closed 14:23:34 Topic: ISSUE-290 - desirable goal of MWABP statements 14:23:36 ISSUE-290? 14:23:36 ISSUE-290 -- Desirable Goal of MWABP statements -- OPEN 14:23:36 http://www.w3.org/2005/MWI/BPWG/Group/track/issues/290 14:23:50 adam: Jonathan raised this during last F2F. We had no further discussion on this. 14:24:09 q+ 14:24:11 ... I don't think desirable goals would add much value, they would just add text. 14:24:37 q- 14:24:47 dka: considering Johnathan is not here, should we give him some kind of deadline to come up with some text? 14:24:55 adam: He did propose some document. 14:25:00 http://lists.w3.org/Archives/Public/public-bpwg/2009Mar/0132.html 14:26:24 q? 14:26:26 dka: I'm not so happy about so quickly abandoning this idea. 14:26:44 ... What do you think, francois? 14:27:32 francois: it's related to the icons we want to have, but don't really have for the time being, right? 14:27:56 adam: It's close but not exactly the same. We should still keep the icons. 14:28:36 dka: the desirable goals are more text we may want to add to each statement. 14:28:53 ... It just seems like a bit of work. 14:28:58 q+ 14:29:14 ... Within 3.4 for instance, we could include a bit more text about performance 14:30:21 ack francois 14:30:22 ... Why don't we leave it open and somebody send a message to Jonathan about ISSUE-290? 14:31:51 francois: I'm unclear about the added value compared to the existing structure of the document. Consider the section on User-Experience, it's pretty clear the BPs are about improving the user experience. 14:32:39 dka: It may be a way to flag a BP that sits in a section and that also has an impact on some other section. 14:33:01 ... That would be kind of a low impact way to do what Jonathan is suggesting. 14:33:40 adam: As a principal, I don't have any objection against this. 14:34:44 ... Sections preambles already try to mention that. For instance the Conservative User of Resources and the section on User Experience 14:36:28 Adam should look through J.J.'s email and apply additional text as necessary to reflect the additional desireable goals as a note after each individual BP. 14:36:56 ACTION: Adam to look through J.J.'s email and apply additional text as necessary to reflect the additional desireable goals as a note after each individual BP. 14:36:56 Created ACTION-995 - Look through J.J.'s email and apply additional text as necessary to reflect the additional desireable goals as a note after each individual BP. [on Adam Connors - due 2009-07-14]. 14:37:18 dka: so we'll leave ISSUE-290 opened for the time being. 14:37:25 ... with an attached action 14:37:57 ISSUE-291? 14:37:57 ISSUE-291 -- widget best practices -- OPEN 14:37:57 http://www.w3.org/2005/MWI/BPWG/Group/track/issues/291 14:38:12 Topic: ISSUE-291 - widget best practices 14:38:36 dka: my view is that we should not do this. 14:38:44 ... and that we should close the issue. 14:38:50 ... Not because it's not important. 14:39:18 At least an explicit statement in the document about the non-inclusion of widgets? 14:39:24 ... But because there is not enough implementation experience in the wild to say things about that at this time. 14:39:43 ... I talked with Art Barstow, chair of the Webapps WG about a Widget Best Practices document. 14:40:03 ... We agreed that if it were to be done, the Web apps WG would be the correct place to do it. 14:40:15 PROPOSED RESOLUTION: The group will not add widget BPs to MWABP and will not work on a special widget BP doc at this time; close ISSUE-291. 14:40:17 +1 14:40:18 q+ 14:40:25 ack edc 14:40:55 EdC: will you put a note that we exclude widgets from the document? 14:41:06 http://www.w3.org/TR/mwabp/#webapp-defined 14:41:11 adam: There's already some text in 1.3.2. I think it's fine as it stands. 14:41:56 dka: I think we need to modify that text. Remove the words "being considered" 14:42:43 ... Two different things. In one sense, the BPs are applicable to widgets, because it's just a package for a web app. 14:43:06 ... But there's some specific stuff in widgets, such as localization. 14:43:11 PROPOSED RESOLUTION: The group will not add widget BPs to MWABP and will not work on a special widget BP doc at this time; close ISSUE-291. We will put an explicit statement in the doc stating that widgets-specifc BPs are out in scope because not enough implementation experience exists at time of writing. 14:43:26 +1 14:43:27 +1 14:43:32 +1 14:43:58 +1 14:44:08 RESOLUTION: The group will not add widget BPs to MWABP and will not work on a special widget BP doc at this time; close ISSUE-291. We will put an explicit statement in the doc stating that widgets-specifc BPs are out in scope because not enough implementation experience exists at time of writing. 14:44:20 Also think you should change the reference to: http://www.w3.org/TR/widgets/ 14:44:55 close ISSUE-291 14:44:55 ISSUE-291 widget best practices closed 14:46:29 dka: one open issue remaining on MWABP, that's good! 14:47:33 Topic: CT - URI patterns 14:47:44 dka: Eduardo, you wanted to talk about that. 14:47:54 http://lists.w3.org/Archives/Public/public-bpwg/2009Jun/0101.html 14:48:57 EdC: this is Francois' response to my comment that explains why the note is correct, but is terse. The meaning is likely to be lost by readers. 14:49:30 -> http://lists.w3.org/Archives/Public/public-bpwg/2009Jun/0108.html Eduardo's proposed clarification 14:49:42 http://lists.w3.org/Archives/Public/public-bpwg/2009Jun/0108.html 14:50:05 EdC: The sentence in the guidelines has all the semantics required, but is a bit unclear. So I suggest to add a clarifying sentence. 14:50:56 dka: can we turn that into a proposed resolution? 14:52:11 PROPOSED RESOLUTION: The URI of the request plays no part in determining wehter request header values are modified and in particular,whether or not a urI PATTERN IS MENTIONED IN 4.2.9 IS NOT MATERIAL TO THIS JUDGEMNT 14:52:12 PROPOSED RESOLUTION: add the following sentence to the 2nd note of 4.1.5: "For the sake of clarity: a URI not matching those specified in 4.2.9 does not 14:52:12 imply that the corresponding site delivers content unsuitable for mobile devices." 14:52:56 jo: I just wanted to avoid the double negative. 14:53:53 ... I think it is better to say that the URI of the request plays no part here, that is basically what we're trying to say 14:53:54 q+ 14:53:58 ack fran 14:53:59 ack framc 14:54:51 francois: agree with Jo. Double negative is usually unclear. 14:55:14 "The purpose of the note was to emphasize the opposite: the absence of a 14:55:15 mobile indication in a URI pattern does not mean that HTTP header field 14:55:15 values should be transformed." 14:55:27 +1 to Jo's resolution and giving the editor some leeway. 14:55:52 jo: can you leave it to the editor to come up with some text on the basis that it will be easier to understand? 14:56:58 ACTION: Jo to add agreed text to 4.1.5 trying to avoid inserting too many negatives, not, not 14:56:59 Created ACTION-996 - Add agreed text to 4.1.5 trying to avoid inserting too many negatives, not, not [on Jo Rabin - due 2009-07-14]. 14:57:36 -1 to tea. 14:57:40 jo: Eduardo, do you agree? 14:57:46 +1 to tea party 14:58:35 EdC: shouldn't it rather be "and whether or not the URI pattern matches one of those defined in 4.2.9"? 14:59:04 PROPOSED RESOLUTION: The URI referred to inthe request plays no part in determining whether request header values are modified and in particular,whether or not a a URI ,matches the PATTERNs MENTIONED IN 4.2.9 IS NOT MATERIAL TO THIS JUDGEMNT 15:00:06 +1 15:00:08 -jo 15:00:49 +1 15:01:07 RESOLUTION: The URI referred to in the request plays no part in determining whether request header values are modified and in particular,whether or not a a URI, matches the patterns mentioned in 4.2.9 IS NOT MATERIAL TO THIS JUDGEMNT 15:01:29 dka: That sounds like a lovely coda to our great call, today! 15:01:42 ... Thanks everyone! 15:01:44 -DKA 15:01:46 bye 15:01:47 -Francois 15:01:49 -adam 15:01:49 bye 15:01:53 -EdC 15:01:54 -miguel 15:01:58 [Call adjourned] 15:01:59 miguel has left #bpwg 15:02:00 -yeliz 15:02:24 -SeanP 15:02:26 MWI_BPWG()9:30AM has ended 15:02:28 Attendees were DKA, adam, Francois, yeliz, miguel, SeanP, EdC, +0208995aaaa, jo 15:02:50 RRSAgent, draft minutes 15:02:50 I have made the request to generate http://www.w3.org/2009/07/07-bpwg-minutes.html francois 15:27:37 zakim, bye 15:27:37 Zakim has left #bpwg 15:27:41 RRSAgent, bye 15:27:41 I see 3 open action items saved in http://www.w3.org/2009/07/07-bpwg-actions.rdf : 15:27:41 ACTION: dan to find people who use CSS media queries to tell whether it's a BP [1] 15:27:41 recorded in http://www.w3.org/2009/07/07-bpwg-irc#T13-55-03 15:27:41 ACTION: Adam to look through J.J.'s email and apply additional text as necessary to reflect the additional desireable goals as a note after each individual BP. [2] 15:27:41 recorded in http://www.w3.org/2009/07/07-bpwg-irc#T14-36-56 15:27:41 ACTION: Jo to add agreed text to 4.1.5 trying to avoid inserting too many negatives, not, not [3] 15:27:41 recorded in http://www.w3.org/2009/07/07-bpwg-irc#T14-56-58