20:00:44 RRSAgent has joined #svg 20:00:44 logging to http://www.w3.org/2011/12/01-svg-irc 20:00:45 ericm_ has joined #svg 20:00:46 RRSAgent, make logs public 20:00:46 Zakim has joined #svg 20:00:48 Zakim, this will be GA_SVGWG 20:00:48 ok, trackbot; I see GA_SVGWG(SVG1)4:00PM scheduled to start in 60 minutes 20:00:49 Meeting: SVG Working Group Teleconference 20:00:49 Date: 01 December 2011 20:01:53 Zakim, room for 8? 20:01:56 ok, ed; conference Team_(svg)20:01Z scheduled with code 26633 (CONF3) for 60 minutes until 2101Z 20:02:51 Team_(svg)20:01Z has now started 20:02:57 +??P2 20:03:00 Zakim, ??P2 is me 20:03:03 +heycam; got it 20:03:07 Zakim, who is on the call? 20:03:11 On the phone I see heycam 20:03:14 + +1.408.543.aaaa 20:04:03 +Tav 20:04:04 "the conference is restricted at this time" 20:04:12 +Doug_Schepers 20:04:51 +cyril 20:08:24 +[IPcaller] 20:08:39 Zakim, [IP is me 20:08:39 +ed; got it 20:08:52 zakim, who's noisy? 20:09:04 shepazu, listening for 11 seconds I heard sound from the following: heycam (53%), Tav (9%), cyril (4%) 20:10:26 Agenda: http://lists.w3.org/Archives/Public/public-svg-wg/2011OctDec/0096.html 20:11:56 Zakim, who is on the call? 20:11:56 On the phone I see heycam, +1.408.543.aaaa, Tav, Doug_Schepers, cyril, ed 20:12:05 Zakim, +1 is ericm 20:12:05 +ericm; got it 20:12:58 Zakim, pick a scribe 20:12:58 Not knowing who is chairing or who scribed recently, I propose cyril 20:13:17 scribe: Cyril 20:13:23 scribeNick:Cyril 20:13:28 Topic: F2F 20:13:54 doug: would it be better to meet in California with the other WG ? 20:14:15 ... there is a possibility that either Chris or I could attend the F2F 20:14:45 ... there was a proposal by the WebApps chairs that the joint sessions in TPAC where useful but not sufficient 20:14:57 ... we thought that a mini tpac would be valuable 20:15:07 ... WebApps, DAP, SVG , CSS 20:15:14 ... maye WebEvents 20:15:35 ... the proposal is that it happens in California because of the people in California 20:15:43 CC: when ? 20:15:54 s/CC:/cyril:/ 20:16:06 ed: march was the proposed date 20:16:36 ... it could be earlier because if we decide to skip the January F2F it would be too close to may 20:16:56 yeah, having SVG meet in january, march and may just seemed a little too much 20:16:57 doug: heycam has mentionned that having both would be problematic 20:17:16 cyril: budget-wise ? 20:17:24 heycam: also time-wise 20:18:01 doug: there is also the matter of it being problematic to have so many meetings for W3C folks 20:18:04 -heycam 20:18:08 ChrisL has joined #svg 20:18:27 +??P2 20:18:29 Zakim, ??P2 is me 20:18:29 +heycam; got it 20:19:13 zakim, code? 20:19:13 the conference code is 26633 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), ChrisL 20:19:24 +ChrisL 20:19:53 cyril: meeting with other groups is good, but it wont' make us progress on SVG 2 20:20:21 doug: colocating doesn't mean having all meetings together 20:20:42 ... things like Component Model is something that we can't do by ourselves 20:21:29 doug: it's cheaper for me to go to California 20:21:41 chris: same plus cheaper/shorter for me 20:23:39 fwiw, I have no preference on meeting locations. They're all the same for me. 20:25:30 doug: I suggest that we go ahead and have the Sydney F2F and that we propose to have a mini-tpac later in the year 20:25:51 ... and that each group works towards milestones for the mini-tpac to be more efficient 20:26:04 sounds like a request for a well-in-advance agenda 20:26:10 ... for instance the Component model needs to be flushed-out to be more useful for SVG 20:26:50 cyril: and documents submitted in advance 20:27:34 doug: I don't want to substitute California with Bucharest 20:27:57 chris: me neither because of Libre Graphics and the AC meeting 20:28:29 ... all meetings are back to back 20:28:33 Note that the CSSWG is also meeting in San Diego later in the year, if you want another colocation that's not Bucharest. 20:28:38 http://www.w3.org/Graphics/SVG/WG/wiki/Meetings#F2F_Meeting_Information 20:28:40 ed: I updated the wiki with this 20:28:44 lgm weds 2-sat 5 20:29:10 css and svg sun 6 - sat qw 20:29:31 ac sun 13-tue 15 20:29:35 http://www.w3.org/Graphics/SVG/WG/wiki/Meetings#Upcoming_F2Fs 20:29:37 doug: what would you think if I tried to set up an SVG mini event? 20:30:06 ... a half day or evening workshop to get people to meet with us 20:30:32 chris: I don't know what is the community interested in Bucharest 20:30:43 doug: possibly too in Sydney 20:31:33 ed: what dates for Sydney 20:31:38 http://www.w3.org/Graphics/SVG/WG/wiki/F2F/Sydney_2012 20:32:28 hecyam: vincent would prefer a 3 day meeting 20:32:34 ... monday to friday 20:33:16 ... I think 4 days sound like a more reasonnable compromise 20:33:37 chris: tuesday to friday 20:33:53 -heycam 20:33:55 ed: I'll be travelling on tuesday 20:34:09 +??P2 20:34:11 Zakim, ??P2 is me 20:34:11 +heycam; got it 20:34:24 cyril: wednesday to saturday 20:35:11 heycam: i have to be in melbourne on monday, I need a bit of time on the weekend to prepare 20:35:39 s/ed: I'll be travelling on tuesday/ed: I'll (probably) be travelling on tuesday/ 20:36:29 doug: the event could be also an evening thing 20:36:54 heycam: as long as people have prepared before the F2F or they will be distracted 20:38:28 erik: the 11th to the 14th ? 20:39:33 RESOLUTION: the next F2F will be in Manly, 11-14/01/2012 20:42:54 http://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Requirements_Mailing_List_Feedback 20:42:54 Topic: SVG 2 Requirements 20:43:14 http://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Requirements_Mailing_List_Feedback#Use_CSS_.27white-space.27_instead_of_.27xml:space.27 20:43:43 heycam: what are our plans for publishing ? 20:44:01 ... do we want to wait until the list is fully reviewed ? 20:44:16 chris: do we publish in the TR space ? 20:44:41 ... a wiki is more useful than the TR space but the TR will be looked at by more people 20:45:00 doug: the editor's draft could be the wiki page 20:45:29 heycam: putting the document in good shape for the TR space will require some work 20:45:39 ... is it a useful effort ? 20:45:50 http://dev.w3.org/SVG/profiles/2.0/reqs/publish/ 20:47:56 a second pass doing prioritisation sounds like a good idea to me 20:47:57 ed: we will need a second pass on the reqs to prioritize 20:48:13 I am concerned that making local decisions about including or not will let us end up with a long list of things we've included 20:49:35 -heycam 20:50:15 I thought the second pass for prioritisation would be a real time thing, like on a telcon. 20:50:16 tav: it'll take weeks to write 20:50:23 ed: yes 20:50:23 And obviously the prose writing would be something to do offline. 20:50:36 So I'm not sure we could do it at the same time. 20:50:55 +??P2 20:50:56 Zakim, ??P2 is me 20:50:56 +heycam; got it 20:50:58 doug: I don't think that we need to go into further details in TR than on the wiki 20:51:42 chris: people who have looked at the requirements deeply will probably understand but outsiders will need text to understand the reqs (on the wiki or in the RT space) 20:51:54 s/RT/RT/ 20:51:56 s/RT/TR/ 20:52:13 doug: I like the idea of farming it out 20:52:35 cyril: on the wiki first 20:52:37 doug: yes 20:52:40 chris: yes 20:53:39 heycam: the proposal is that everyone expands on the wiki each requirements with a paragraph 20:54:03 chris: what about those that we have rejected 20:54:11 tav: it is useful to have it 20:54:25 chris: having the rationale is useful 20:56:41 chris: I'm suggesting that we update the current wiki page 20:57:29 doug: maybe instead of publishing in the TR space, we make a link to the Wiki page 20:58:26 ACTION: heycam to copy text from the current reqs document and add placeholders for people to fill in 20:58:27 Created ACTION-3179 - Copy text from the current reqs document and add placeholders for people to fill in [on Cameron McCormack - due 2011-12-08]. 20:58:53 Topic: white space 20:59:00 http://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Requirements_Mailing_List_Feedback#Use_CSS_.27white-space.27_instead_of_.27xml:space.27 20:59:54 we already decided this 21:00:25 doug: authoring tools will be shoving out the old xml thing 21:01:02 chris: I noticed the there is an effort in the Inkscape community to clean up the output 21:01:15 ... they could remove xml thing 21:02:06 RESOLUTION: SVG 2 will deprecate the use of xml:space to affect layout and will use the CSS white-space property 21:02:22 http://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Requirements_Mailing_List_Feedback#Allow_.40transform_to_apply_to_.3Ctspan.3E_elements 21:02:34 Topic: transforms on tspan elements 21:03:27 cyril: it's linked to http://www.w3.org/Graphics/SVG/WG/wiki/SVG2_Requirements_Mailing_List_Feedback#Consider_adding_transform.3D.22.22_to_.3Csvg.3E 21:03:33 vhardy has joined #svg 21:03:47 chris: I don't think adding transform on every element makes sense (e.g gradient stop) 21:04:05 tav: what happens if you transform a tspan to the next tspan 21:04:21 doug: the next tspan wouldn't be affected 21:04:27 -Tav 21:04:30 chris: unlike dx and dy, 21:04:43 ... we should be careful about making the difference clear 21:05:13 doug: I think a transform should not affect things like dx, dy 21:05:22 I can't call in... 21:06:13 tav trying connecting with the regular code 21:06:15 -ChrisL 21:06:21 -heycam 21:06:24 o 21:06:28 -Doug_Schepers 21:06:30 -cyril 21:06:31 -ed 21:06:42 Zakim, who is on the call? 21:06:42 On the phone I see ericm 21:06:44 -ericm 21:06:44 Team_(svg)20:01Z has ended 21:06:45 Attendees were heycam, +1.408.543.aaaa, Tav, Doug_Schepers, cyril, [IPcaller], ed, ericm, ChrisL 21:06:48 Zakim, this is svg 21:06:48 heycam, I see GA_SVGWG(SVG1)4:00PM in the schedule but not yet started. Perhaps you mean "this will be svg". 21:06:53 Zakim, this will be svg 21:06:53 ok, heycam; I see GA_SVGWG(SVG1)4:00PM scheduled to start 6 minutes ago 21:06:56 GA_SVGWG(SVG1)4:00PM has now started 21:07:01 +ChrisL 21:07:01 +Doug_Schepers 21:07:04 i'm in 7841 21:07:05 +cyril 21:07:07 + +1.415.832.aaaa 21:07:13 +??P5 21:07:15 Zakim, ??P5 is me 21:07:15 +heycam; got it 21:07:26 Zakim, who is on the call? 21:07:26 On the phone I see ChrisL, Doug_Schepers, cyril, +1.415.832.aaaa, heycam 21:07:31 +[IPcaller] 21:07:36 Zakim, +1.415 is vhardy 21:07:36 +vhardy; got it 21:07:38 Zakim, [IP is me 21:07:38 +ed; got it 21:07:50 Zakim, +1.415.832.aaaa is vhardy 21:07:50 sorry, vhardy, I do not recognize a party named '+1.415.832.aaaa' 21:08:05 rrsagent, here 21:08:05 See http://www.w3.org/2011/12/01-svg-irc#T21-08-05 21:08:21 ed: I agree, transform should not affect dx and dy 21:08:41 +Tav 21:08:58 s/should not affect dx and dy/should not affect text like dx and dy, taking up space and so on, it's purely a visual effect/ 21:09:00 heycam: the transform could apply after the text layout has been applied 21:09:35 chris: aaa tspan bbb tspan ccc 21:09:42 aabbcc 21:10:30 chris: if the tspan had a transform, it would not affect the position of cc 21:10:41 ... we need to think about nested tspans with transforms 21:10:48 tav: do we have use cases for that ? 21:11:35 " doesn't seem to apply the effects of a transform attribute. Doing so would make it easier to keep passages of text together for readability/searchability while still adjusting the position of style effects." 21:12:07 yes but what is it for? 21:12:17 doug: I'm happy with Chris's suggestion 21:12:19 is it for animating,so text jiggles around? 21:13:02 cyril: doesn't this complexify the implementation: two passes ? 21:13:10 tspan:hover {transform: translate(10,10) } 21:13:38 tav: I'd be happy to add it if I had one useful example 21:13:52 elusive text 21:14:00 a scale transform would be more useful 21:14:00 doug: when you are editing text 21:14:37 chris: the major use cases could be in dynamic 21:14:56 ... you don't want it to affect the other text 21:15:19 ... we should be sure it adds value before pushing it forward 21:16:48 heycam: the cost for us will not be extremely hard 21:17:14 doug: we should have a model for getting the computed geometry 21:17:31 ... the computed style is the style while all the changes have been made 21:17:51 ... the analog of that would be the geometry aside all the transforms applied to it 21:19:12 cyril: we need to explain about bounding boxes, glyph data (text api) 21:19:21 how does this affect text ona path? 21:19:37 doug: what about skew, does it apply ? 21:20:40 ed: doug had a point that it could be nice to have a consistent to be able to specify transforms everywhere 21:20:50 ... but I'm not sure it's worth the cost 21:22:37 heycam: the transform on the text is a transform on the whole text 21:22:39 -heycam 21:23:04 ... if you could a DOM method on a text element on some of the children 21:23:37 so at the moment with abc all the glyphs are within the same coordinate space 21:23:48 do we also have transform on inside text and if so, isn't this exactly the same as tspan? 21:24:04 this proposal would change that, so we do need to decide how that affects calling dom text positioning methods on the containing element 21:24:20 ChrisL, nice question, I wonder what implementations do there 21:24:31 +??P5 21:24:34 Zakim, ??P5 is me 21:24:34 +heycam; got it 21:25:59 heycam: I'm slightly in favor of adding it 21:26:13 data:image/svg+xml,link outside link 21:28:18 data:image/svg+xml,link outside link 21:29:08 ok so we should bring tspan into line with a here 21:29:26 RESOLUTION: SVG 2 will allow transforms on tspan 21:30:01 the next F2F will be in Manly, 11-14/01/2012 21:31:34 9-11 May for css, 9 is fx day 21:32:00 -ChrisL 21:32:04 -heycam 21:32:06 -ed 21:32:06 -vhardy 21:32:08 -Doug_Schepers 21:32:09 -Tav 21:34:03 RSSAgent, make minutes 21:34:44 I've edited the requirements page 21:38:28 RRSAgent, make minutes 21:38:28 I have made the request to generate http://www.w3.org/2011/12/01-svg-minutes.html cyril 21:38:52 RRSAgent, make minutes public 21:38:52 I'm logging. I don't understand 'make minutes public', cyril. Try /msg RRSAgent help 21:58:14 -cyril 21:58:15 GA_SVGWG(SVG1)4:00PM has ended 21:58:17 Attendees were ChrisL, Doug_Schepers, cyril, +1.415.832.aaaa, heycam, [IPcaller], vhardy, ed, Tav 23:48:50 Zakim has left #svg