15:05:06 RRSAgent has joined #css 15:05:06 logging to http://www.w3.org/2011/05/04-css-irc 15:05:13 zakim, this will be style 15:05:13 ok, plinss; I see Style_CSS FP()12:00PM scheduled to start in 55 minutes 15:05:24 rrsagent, make logs public 15:05:37 Martijnc has joined #css 15:05:45 davve has left #css 15:06:42 Martijnc_ has joined #css 15:19:14 nimbupani has joined #css 15:19:30 nimbupani has left #css 15:25:53 glazou has joined #css 15:26:07 Zakim, this will be Style 15:26:07 ok, glazou; I see Style_CSS FP()12:00PM scheduled to start in 34 minutes 15:26:08 rrsag 15:26:13 RRSAgent, make logs public 15:50:44 danielweck has joined #css 15:55:35 Style_CSS FP()12:00PM has now started 15:55:42 +[IPcaller] 15:55:52 zakim, who is on the phone? 15:55:52 On the phone I see [IPcaller] 15:55:58 +??P1 15:56:03 zakim, ipcaller is me 15:56:03 +jdaggett; got it 15:56:04 Zakim, ??P1 is me 15:56:05 +glazou; got it 15:56:30 +plinss 15:56:55 probably me, i'm on skype... 15:57:15 +??P35 15:57:28 nope 15:57:29 johnjan has joined #css 15:57:32 i'm muted 15:57:41 -glazou 15:57:47 Zakim, ??P35 is me 15:57:47 +danielweck; got it 15:57:48 dsinger_ has joined #css 15:58:02 +[Microsoft] 15:58:21 zakim, microsoft is johnjan 15:58:21 +johnjan; got it 15:58:34 +??P37 15:58:40 Zakim, ??P37 is me 15:58:40 +glazou; got it 15:58:46 stearns has joined #css 15:58:50 +[Apple] 15:58:58 sylvaing has joined #css 15:59:01 +dsinger 15:59:09 Zakim, Apple has me 15:59:09 +hober; got it 15:59:10 +fantasai 15:59:20 -dsinger 15:59:25 wow, noise city... 15:59:28 + +1.206.675.aaaa 15:59:40 Zakim, mute fantasai 15:59:40 fantasai should now be muted 15:59:52 oyvind has joined #css 15:59:56 +dsinger 15:59:56 zakim, aaaa is me 15:59:57 +stearns; got it 16:00:22 smfr has joined #css 16:00:24 wee, good conversations ahead... 16:00:29 +[Microsoft] 16:00:30 zakim, microsoft has me 16:00:31 +arronei_; got it 16:01:01 glazou: btw, i'll ask around about the question you asked me next week 16:01:09 + +47.21.65.aabb 16:01:11 + +1.408.636.aacc 16:01:13 glazou: it's golden week in japan 16:01:14 yeah 16:01:22 ok, great 16:01:22 Zakim, aacc is me 16:01:22 +smfr; got it 16:01:36 so he wasn't working on the css3 text spec 16:01:42 dear, dear 16:02:03 howcome has joined #css 16:02:07 +[Microsoft.a] 16:02:24 + +1.650.618.aadd 16:02:26 fantasai2 has joined #css 16:02:27 Zakim, [Microsoft.a] has sylvaing 16:02:27 +sylvaing; got it 16:02:32 Zakim, who is on the phone? 16:02:32 On the phone I see jdaggett, plinss, danielweck, johnjan, glazou, [Apple], fantasai (muted), stearns, dsinger (muted), [Microsoft], +47.21.65.aabb, smfr, [Microsoft.a], 16:02:36 ... +1.650.618.aadd 16:02:37 [Microsoft] has arronei_ 16:02:38 [Apple] has hober 16:02:38 arno1 has joined #css 16:02:40 [Microsoft.a] has sylvaing 16:03:09 zakim, aabb is howcome 16:03:09 +howcome; got it 16:03:20 Zakim, aabb is howcome 16:03:20 sorry, glazou, I do not recognize a party named 'aabb' 16:03:47 must be a bad week for the semantic web 16:03:54 +SteveZ 16:04:42 bradk has joined #css 16:05:01 http://www.w3.org/2006/tools/wiki/Zakim_Tips 16:05:03 http://www.w3.org/1998/12/bridge/info/name.php3 16:05:21 + +1.650.275.aaee 16:05:25 arno has joined #css 16:05:45 zakim, aaee is brad 16:05:46 sorry, jdaggett, I do not recognize a party named 'aaee' 16:05:59 scribenick: sylvaing 16:06:20 -bradk 16:06:31 glazou: extra agenda items ? 16:06:45 jdaggett: I'd like to take over editing of the line layout spec 16:06:59 jdaggett: and an update on the charter if possible 16:07:11 +bradk 16:07:18 TOPIC: CSSWG Charter 16:07:53 jdaggett: looking at the draft charter, the line grid spec ended on the charter as a medium priority spec even though we haven't discussed this 16:08:22 jdaggett: i'm not sure it should be a separate spec vs. being part of line layout. there seems to be a lot of overlap. why is it in the charter and how did it end up on the status page ? 16:08:55 szilles: I believe it was discussed in the context of line alignment across columns. and layout for east asian languages 16:09:10 jdaggett: sure but when did we agree to make it part of the charter ? 16:10:03 jdaggett: I don't think it warrants a separate spec. 16:10:19 szilles: for the sake of making progress it may be easier to list them as they are now 16:10:33 glazou: if it's on the charter we can work on it in the course of the charter 16:10:51 jdaggett: it is medium priority and the decision to make it so is unclear 16:11:14 This is a draft charter for discussion,right? And now we are discussing it. 16:11:51 szilles: the criteria for medium priority is a champion to push it forward. And Koji is the champion 16:12:04 -dsinger 16:12:08 Anyone can propose into the DRAFT 16:13:01 +FabGandon 16:13:02 (agreement to wait for Chris Lilley) 16:13:12 glazou: what else about the charter ? 16:13:34 Bert, you're listed by Zakim as FabGandon ?!? 16:13:51 howcome: I'm championing GCPM so should it be medium ? 16:13:53 +dsinger 16:14:16 szilles: I think it also needs to get to LC or CR in the period 16:14:30 fantasai: we also used to require implementors working on it 16:14:39 szilles: that is a reasonable criteria for High Priority 16:14:53 szilles: should we poll vendors on implementation interest ? 16:15:24 plinss: we did a private poll last night. it could be helpful to update the data we collected last time 16:15:34 s/night/time/ 16:16:22 glazou: we should stabilize the list and then run the poll 16:17:07 howcome: if those specs expected to reach PR are high priority then css3-multicol should be High. 16:17:20 +??P13 16:17:30 zakim, ??p13 is me 16:17:30 +kojiishi; got it 16:17:37 http://www.w3.org/2010/09/CSSWG/charter.html 16:17:46 howcome: everything being in scope I'm not sure we can read much in the hi/med/low ranking 16:18:00 We ought to prioritize staff, wg, f2f time etc. On the priorities 16:18:01 (I'm looking at the same as glazou) 16:19:26 glazou: taking the hi pri documents to CR is not the hard part. moving test suites along for them all is the larger work item 16:21:14 glazou: let's continue this discussion when Chris is present. 16:21:49 szilles: with the exception of jdaggett's and howcome's comment, does anybody on the call think something is missing or shouldn't be there ? 16:22:43 szilles: I thought ChrisL believed the draft was ready to go in front of the AC membership in two weeks so we should at least identify obvious bugs without waiting for ChrisL 16:23:12 glazou: my only concern is the number of documents in high-priority. are we creating an expectation of achieving PR for everything in high priority ? 16:23:47 szilles: there is no harm in having fewer things in high priority and exceeding expectations 16:23:49 glazou: yes 16:24:14 szilles: any good candidates to move from high to medium ? 16:24:40 glazou: this is something where poll data would be useful input since browser vendors commitment to implement and submit testcases is key 16:25:13 dsinger has joined #css 16:25:30 Zakim, mute fantasai 16:25:30 fantasai should now be muted 16:25:31 somebody is talking in the toilet 16:25:45 Zakim, unmute fantasai 16:25:45 fantasai should no longer be muted 16:25:48 Zakim, who is noisy? 16:25:59 dbaron, listening for 10 seconds I heard sound from the following: johnjan (13%), Bert (17%), SteveZ (72%), glazou (46%), [Microsoft.a] (13%) 16:26:02 +[Apple.a] 16:26:06 zakim, [apple] has dsinger 16:26:06 +dsinger; got it 16:26:10 -dsinger 16:26:58 -danielweck 16:27:21 +??P5 16:27:24 I think it may be a good idea... but I'd sort of like to think about it... and perhaps try it to see how it goes. 16:27:31 Zakim, ??P5 is me 16:27:31 +danielweck; got it 16:27:35 dbaron, agree. something we should pilot 16:27:48 (it == requiring test suite submission for dropping prefixes) 16:28:18 TOPIC: publishing updates to css3-lists and css3-images 16:28:31 fantasai: these are request from Tab. I'm in support. 16:28:41 fantasai: for lists, we should resolve outstanding issues and publish 16:28:51 glazou: css3-images. any objection to publishing a new draft ? 16:29:12 http://dev.w3.org/csswg/css3-images/ 16:29:17 dbaron: this draft seems to get more features 16:29:45 dbaron: was originally something we were going to get out quickly, but seems to be growing more features, which makes that harder 16:29:54 I'd like to move gradients forward in level 3; the rest in level 4 16:30:16 fantasai: one of the items was the image annotation which we moved out from backgrounds & borders. 16:30:37 fantasai: we have implementation of object-fit et al. but under other names. these are implemented but not in browsers 16:31:00 dbaron: now I'm a little less scared after reading through the TOC more closely 16:31:22 glazou: should we extract the parts that are ready for LC/CR ? 16:31:58 (some agreement to thin Level 3 and move the rest to Level 4 WD) 16:32:12 I think cross-fade() is also wrong -- using the wrong definition in terms of porter-duff. 16:32:25 glazou: it'd be better to do these edits before republishing 16:33:09 fantasai: cutting features is easy as long as we have WG agreement on what to keep/what to drop 16:33:21 fantasai: I can do the edits while Tab is away 16:33:36 glazou: I suggest we move this discussion to the mailing list so we conclude on the cuts at the next telcon 16:34:02 http://lists.w3.org/Archives/Public/www-style/2011Apr/0764.html 16:34:07 http://dev.w3.org/csswg/css3-lists/ 16:34:11 ACTION: fantasai start mailing list discussion on trimming css3-images 16:34:11 Created ACTION-320 - Start mailing list discussion on trimming css3-images [on Elika Etemad - due 2011-05-11]. 16:35:06 jdaggett: I think it would be helpful if Tab were here to decide on what list items are to be edited out 16:35:40 fantasai: for complex counter style, we should define Chinese ideographic because it's been defined and implemented before. EPUB needs it 16:36:08 glazou: are we OK with publishing now ? 16:36:48 nimbupani has joined #css 16:37:00 fantasai: there was discussion about the longhand style for ideographic counters up to large numbers. this has never been published and I'd like to at least have it as an appendix so we can refer to it later 16:37:03 nimbupani has left #css 16:37:58 fantasai: it'd be an informative appendix today, we don't lose this info and we still have the option of making it normative in the future 16:38:28 fantasai: ...so the spec can limit itself to a 10k range but we don't lose the correct information for ranges beyond that 16:38:44 and indeed, is someone wants to implement something that is robust into the trillions, they should be able to 16:38:54 s/is someone/if someone/ 16:39:03 howcome: I think there is merit in documenting this. I'm not sure it needs to be in the WD. 16:39:39 jdaggett: numbering systems are complex. I think the features need to target use-cases. 16:39:50 fantasai: my concern is that we have published definitions that were wrong 16:40:57 "Note: this algorithm truncates at 10,000; previous CSS publications went to a higher limit but had errors in the algorithms" 16:41:26 glazou: I propose to publish this WD as-is 16:41:33 jdaggett: sounds fine 16:41:38 No objections 16:41:49 RESOLVED: publish css3-lists WD 16:44:23 szilles: when we decide to publish a WD, we should also think of people who do not follow www-style on a daily basis 16:44:27 Steve: Publishing WDs is so that people who aren't following the mailing list daily can keep up with what's happening. 16:44:54 TOPIC: Line Layout module editor 16:45:09 jdaggett: I would like to take that up as css3-fonts is completed 16:45:29 jdaggett: dbaron is the current editor and I'd work with him to get his pending edits in and take it from there 16:45:47 szilles: I would like to be considered as a co-editor. 16:45:51 jdaggett: I'm fine with that 16:46:06 RESOLVED: jdaggett,szilles editors of Line Layout 16:46:17 TOPIC: Kyoto F2F - agenda items 16:47:27 szilles: since we have the workshop the day before, i'd like items discussed in the workshop to being our f2f agenda 16:47:42 szilles: so that some attendees of the workshop can easily attend both 16:48:05 szilles: I thought the discussions of css3-text and css3-writing-modes would be relevant to the workshop. any other ? 16:48:14 fantasai: these are the main ones 16:48:27 szilles: maybe Line Grid as well. 16:48:35 szilles: I would like to have a discussion of Regions and Grid Layout 16:48:38 howcome has left #css 16:48:58 glazou: everyone, please gather agenda items for Kyoto 16:49:18 TOPIC: CSS Snapshot publication 16:49:32 fantasai: also our handling of prefixing which is defined in the snapshot 16:49:43 http://dev.w3.org/csswg/css-2010/#experimental 16:50:02 -danielweck 16:50:12 +??P5 16:50:19 Zakim, ??P5 is me 16:50:19 +danielweck; got it 16:50:36 fantasai: our previous discussion was to clarify that section. 16:51:17 sylvaing: I thought dbaron wanted to think about it 16:51:23 dbaron: I think I'm fine with publishing 16:51:28 smfr: I think this is fine 16:51:31 howcome: no objection 16:51:57 szilles: i'm ok 16:52:09 -bradk 16:53:29 dbaron describes a possible exception to the rule 16:53:44 dbaron: I think we need some sort of exception for features that other browsers have already shipped unprefixed (e.g., 'text-overflow') 16:53:46 fantasai: yes, the CSSWG may allow certain features to be unprefixed for legacy reasons 16:54:27 szilles: I think it would be better for the WG to grant the exception 16:54:31 +bradk 16:55:46 dbaron: maybe we can note this as an issue for this publication 16:55:48 no objections 16:56:09 RESOLVED: release the document once this issue has been noted 16:56:14 TOPIC: Logo 16:56:14 http://daniel.weck.free.fr/CSS-Logo/ 16:56:20 arno has joined #css 16:56:33 howcome: i like it 16:56:52 glazou: i like it too 16:57:19 howcome and sylvain like the historic connection to the old logo 16:57:27 smfr: it looks 3d so i like it 16:57:27 smfr: It looks 3D, so I like it :) 16:57:42 not a huge fan of gill sans though.... 16:57:47 -bradk 16:58:28 -SteveZ 16:58:29 I'm not terribly excited about it. Why 3 boxes? Something about the box model? 16:58:40 glazou: thanks a lot to daniel for contributing this logo 16:58:48 plinss: i like it to but we were asked for a design brief 16:58:57 glazou: a proposal can't hurt 16:59:06 plinss: I'd like to capture the intent of what we're going for 16:59:26 plinss: i.e. 'this is what we want out of a logo and this is a proposal' 16:59:56 I'm also tired of Gill Sans 17:00:05 -howcome 17:00:33 Bert: so who will produce a design brief ? 17:00:47 danielweck: I wrote my own. maybe we can just improve on that 17:00:59 fantasai volunteers bradk... 17:01:14 CSS3 Speech 17:01:15 http://lists.w3.org/Archives/Public/www-style/2011Apr/0746.html 17:01:16 gee thanks. 17:01:17 phonemes 17:01:17 TOPIC: request to drop phonemes from css3-speech 17:01:30 http://www.w3.org/TR/css3-speech/#phonemes 17:01:34 -johnjan 17:01:51 It's 10:00 17:02:04 bradk: we're just a little bit over time 17:02:20 danielweck: the first link explains the current situation. there is a consensus that the phonemes property in the current css3 draft breaks the separation of content and presentation 17:02:50 -jdaggett 17:02:59 danielweck: i also argue that EPUB will drive this issue forward using an SSML-based solution. 17:03:21 glazou: so you argue this is not part of css3-speech because it'll be defined elsewhere 17:03:35 danielweck: right. and also that this is more likely to be part of HTML given an EPUB solution 17:03:53 (I once proposed: 'phoneme-map: "ape" = \676\324\486, "bar" = \9084\7854\78=4' which picks whatever string actually occurs in the text.) 17:04:02 glazou: i suggest a note be included to explain this removal 17:04:08 As far as the logo goes, I don't have anything better in mind, and I thank Daniel for his work. I'd like to see us agree on a design brief and see something grow from that, starting with multiple sketches in order to define the direction for further tightening. 17:04:08 danielweck: that's fine with me 17:05:44 Usually when designing a logo, there is more than one round of sketches and more than one week after the first round in order to arrive at a final logo. 17:06:06 -smfr 17:07:16 Peter's is indeed one possible implementation of my principle. 17:07:44 -[Microsoft] 17:07:46 -dbaron 17:07:51 -danielweck 17:07:52 -glazou 17:07:53 -[Apple] 17:07:54 -plinss 17:07:55 RESOLVED: remove phonemes property; include note to explain removal 17:07:55 -[Apple.a] 17:07:57 -kojiishi 17:08:02 -[Microsoft.a] 17:08:03 -stearns 17:08:04 -Bert 17:08:33 -fantasai 17:08:35 Style_CSS FP()12:00PM has ended 17:08:37 Attendees were jdaggett, glazou, plinss, danielweck, johnjan, dsinger, hober, fantasai, +1.206.675.aaaa, stearns, arronei_, +47.21.65.aabb, +1.408.636.aacc, smfr, [Microsoft], 17:08:40 ... +1.650.618.aadd, sylvaing, dbaron, howcome, SteveZ, +1.650.275.aaee, bradk, Bert, kojiishi, [Apple] 17:08:52 bradk: I think the proposal was for you to draw up the design briefl 17:08:59 bradk: not to design the logo 17:10:51 Ah. I could probably do that if I can find time. Maybe a draft to see if we all agree. I pretty much hate writing up design briefs, but I could probably knuckle down and come up with something. 17:11:52 Working backwards from the existing logos, I'd say 17:12:05 - Connection to the previous logo seems important to CSSWG 17:12:14 - Sense of "cascading" 17:12:24 - Sense of building something 17:13:42 howcome has joined #css 17:21:46 Ms2ger has joined #css 17:36:06 - modular components building on one another 17:36:42 - 3d logo vs 2d logo - more modern feel, impression of evolution from prior logo 17:37:19 - brings a feeling of "style" 17:40:55 Zakim, please excuse us 17:40:55 Zakim has left #css 17:41:42 RRSAgent, please excuse us 17:41:42 I see 1 open action item saved in http://www.w3.org/2011/05/04-css-actions.rdf : 17:41:42 ACTION: fantasai start mailing list discussion on trimming css3-images [1] 17:41:42 recorded in http://www.w3.org/2011/05/04-css-irc#T16-34-11