20:00:25 RRSAgent has joined #svg 20:00:25 logging to http://www.w3.org/2009/11/19-svg-irc 20:00:27 RRSAgent, make logs public 20:00:27 Zakim has joined #svg 20:00:29 Zakim, this will be GA_SVGWG 20:00:29 ok, trackbot; I see GA_SVGWG()3:00PM scheduled to start now 20:00:30 Meeting: SVG Working Group Teleconference 20:00:30 Date: 19 November 2009 20:01:36 GA_SVGWG()3:00PM has now started 20:01:43 +??P2 20:01:52 Zakim, ?? is me 20:01:52 +ed; got it 20:02:16 +Shepazu 20:03:35 +??P3 20:03:42 jwatt has joined #svg 20:04:15 Zakim, who's here? 20:04:15 On the phone I see ed, Shepazu, ??P3 20:04:16 On IRC I see jwatt, Zakim, RRSAgent, ed, karl, anthony, shepazu, trackbot, ed_work, eseidelDesk 20:04:22 Zakim, ?? is me 20:04:22 +jwatt; got it 20:07:35 +??P4 20:07:42 Zakim, ??P4 is me 20:07:42 +anthony; got it 20:08:14 Agenda: http://lists.w3.org/Archives/Public/public-svg-wg/2009OctDec/0041.html 20:08:49 http://www.w3.org/Graphics/SVG/WG/wiki/Roadmap 20:08:58 Scribe: Jonathan Watt 20:09:02 scribenick: jwatt 20:09:48 Topic: Roadmap 20:09:50 DS: the table is really out of date 20:12:57 AG: Compositing could go to LC in Feb/Mar I think 20:15:16 DS: how about May for CR then? 20:15:32 ED: the earlier there's a testsuite the better 20:17:16 DS: PR Aug; Rec Sep 20:17:21 AG: sounds fine 20:17:36 ED: so Filters 20:18:33 ED: I'd prefer to have a couple more drafts before going to LC 20:18:51 ...especially since i'd like to put in the CSS canned filters, and perhaps new syntax as well 20:19:01 ...probably a few more primitives 20:20:06 JW: I'd like to revisit the need for authors to specify filter regions, and filterRes 20:20:18 ED: I would like to resolve that too 20:20:54 ED: I think Sep for LC 20:21:01 DS: I think that's pretty far away 20:23:43 Scribe: anthony 20:23:51 scribenick: anthony 20:24:30 DS: Let's say June 2010 for Use Case & Requirements for Layout 20:24:41 ... He'd probably be working on the spec at the same time 20:24:49 ... so let's say July 2010 20:24:58 ... for FPWD 20:25:06 ... then LC October 20:25:19 .... that would put CR in December 20:25:39 ... and PR in June 2011 20:27:08 ... Masking and Clipping? 20:27:13 AG: Who is doing that anyway? 20:27:26 DS: Emmons 20:27:55 ED: It's basically dealing with coordinate systems 20:28:22 DS: don't really need a lot of changes 20:28:26 we have some issues raised on masks/clippaths, we should address those... and pinnedclip maybe 20:28:39 ... I'm going to give it the same time line as Compositing 20:29:19 ...and perhaps use of clip/mask in CSS/HTML 20:29:55 ED: Not convinced we need a separate module for it 20:30:04 DS: You mean do it as part of SVG 2.0 instead? 20:30:14 ED: Yeah, although it might be good for other specs 20:30:32 DS: Media Access Events is the same, it's pretty much done 20:30:48 ... just need someone to finish it 20:31:03 ... Paint Servers 20:31:17 ... I'm going to put that on the same time line as filters 20:31:26 ... what do you think? 20:31:45 ED: Who is the editor for that? 20:31:53 DS: I would say Chris 20:32:03 ED: The guy from Inkscape 20:34:06 DS: Print spec 20:34:22 AG: Print will become Colour Management and Pagination 20:34:33 DS: I couldn't find a Pagination spec 20:34:40 AG: Currently there is none 20:34:53 ED: That line needs to be split up 20:35:06 ... into two lines 20:37:05 DS: It went to LC in September? 20:37:10 AG: Yes, something like that 20:37:26 http://www.w3.org/TR/SVGColor12/ 20:37:52 ED: Looks like FPWD 20:38:13 DS: And it was October 20:38:32 ... shouldn't it be called Colour Management? 20:40:08 AG: Yeah you're right 20:40:14 DS: Chris didn't think that there was that much more to do on the spec 20:40:37 ... try to get Colour Management to LC in December 20:41:34 ... For pagination I'm going to say May 2010 for FPWD 20:41:40 ... LC December 2010 20:42:09 ... CR March 2011 20:42:40 ... PR October 2011 20:42:47 ... Rec December 2011 20:44:31 http://www.w3.org/TR/SVG-Transforms/ 20:45:17 20 March 2009 20:45:25 FPWD 20:47:14 DS: Transformations, LC in July 20:47:49 JW: If we combine with CSS is that a new document? 20:49:09 AG: October 2010 CR 20:49:41 DS: May, June for Rec? 20:49:43 AG: Ok 20:50:26 DS: Vector Effects 20:50:36 ... I'm going to move those dates all back 1 year 20:51:18 JW: Should turn the dates into links to specs 20:51:43 ... Mozilla will implement Vector Effects, ED are you happy with that? 20:52:10 ED: Not sure exactly how cheap some of the operations are 20:52:33 DS: Will Firefox implement this? 20:54:03 JW: The reason I ask is stroking a stroke is something unknown to current rendering libraries 20:54:36 s/Mozilla will/do you think we can/ 20:55:10 JW: I think it's going to be harder to implement than it looks 20:55:26 DS: The feature set probably wont change that much 20:55:42 ... but the basic syntax and what it allows you to do seems pretty straight forward to me 20:55:57 ... do we think the language itself is going to change? 20:56:26 ... the process allows us to go to CR 20:56:34 ... and if we need to change it then go back to LC 21:00:20 ED: Maybe push that back a bit mre 21:00:26 s/mre/more/ 21:00:33 ... I'd say the same time as filters 21:00:45 DS: Webfonts 21:00:55 ED: Not sure what that is about really 21:01:01 DS: I'm going to say move that to CSS 21:01:12 ED: Chris will probably know more about that 21:04:11 DS: SVG 2.0 moving all the dates to 2011 21:07:06 Topic: IntersectionList 21:07:10 http://lists.w3.org/Archives/Public/www-svg/2009Nov/0015.html 21:07:27 ED: That's the start of the thread and it goes on and on and on and on and on 21:08:14 ... the node lists are static 21:08:26 ... and that's what we say in the 2nd edition spec 21:08:45 ... the second parameter to the method is it the root of the subtree to search or is it something else? 21:08:54 ... I'm pretty sure Opera implemented to be the subtree 21:09:08 ... the results are limited to be the children of the subtree element 21:09:17 DS: That seems kind of strange to me 21:09:29 JW: Limiting it to the subtree? 21:09:32 DS: Yes 21:09:35 JW: Why? 21:09:43 DS: Where is it likely that someone will use these things 21:10:07 ... and I just don't see where moving it to a subtree makes sense 21:10:15 ... from a performance stand point it makes sense 21:10:26 ... but I don't know why someone would want to limit it to a subtree 21:10:35 JW: So a joining area of a drawing application 21:10:39 s/and it goes on and on and on and on and on// 21:10:48 ... so if can restrict it 21:10:58 ... it makes sense 21:11:04 DS: Ok yeah, you're right 21:11:42 ED: Do you think it's a good idea to clarify it to be the subtree root? 21:12:05 DS: Which bit are saying? getIntersectionList? 21:12:06 ED: Yes 21:12:14 DS: It doesn't say that 21:12:44 JW: I don't see it makes sense any other way than what Opera has done 21:12:46 [[referenceElement -- If not null, then only return elements whose drawing order has them below the given reference element.]] 21:12:54 DS: There are two interpretations of it 21:13:06 ... I've never seen 'below' to define a subtree 21:13:23 ... I think what they meant in the spec is rendering order 21:13:37 JW: I think rendering order doesn't make sense and no one has done that 21:13:47 DS: One thing you mentioned which is important 21:13:53 ... is collision dectection 21:14:11 s/dectection/detection/ 21:15:10 ED: Collision detection is pretty common for games 21:15:36 JW: In some 3D games I've seen, the character goes halfway through an object before the collision is detected 21:15:45 ... in that case they are not using the geometry 21:16:22 ED: Do we want to resolve that it is a subtree 21:16:30 DS: It is clearly subtree 21:16:35 ... that is not the intent of 1.1 21:16:41 .... we can change it for 2.0 21:16:47 ED: I don't agree witht hat 21:16:56 s/witht hat/with that/ 21:17:01 ... that's not the way I read it 21:17:09 DS: ASV6 did it the way I described 21:17:28 ... I don't mind us changing it, I don't think that was the original intent 21:17:46 ... and I'm not sure form a process point of view if we can change it that way 21:17:57 ED: It is ambiguous at the moment 21:18:08 ... what we have not is not interoperable at the moment 21:19:01 JW: I'd have to side with DS about what it means 21:19:13 ... but what they describe it is difficult to implement 21:19:54 ... We are not doing any more errata for 2nd Edition are we? 21:20:02 ED: I wouldn't mind putting something in 21:20:09 ... we already have test cases 21:20:35 DS: We could ask Chris, JF or Dino if we want to clarify 21:21:46 DS: In line with JW was saying, we should just define what we think is correct 21:22:59 ... the way it's defined in 1.1 is not the we want people to do it anyway 21:23:05 ... let's just start over 21:23:15 ... and not fix the mistakes of the past 21:23:34 ... at some point we have to move on 21:26:00 ED: Batik probably does it as well 21:26:22 ... since CM implemented it 21:26:55 s/implemented/wrote a test (that I'm reviewing) for/ 21:31:56 ... If you think it's not worth it and if you're willing to take the risk of different interpretations of it 21:32:04 DS: What if put the question to the list? 21:32:54 JW: I don't see any reason to restrict to a rect. I'd push for a new API 21:33:19 ... maybe getIntersectionList could stay there and call into the more complex one 21:34:05 ED: People on the list seem to prefer the subtree model 21:34:28 DS: I think it's a waste of time to fix stuff that's broken from the start 21:34:46 JW: ED is going to do it. Then he can get on with reviewing tests 21:36:23 DS: Are you the same as Batik on tests? 21:36:30 ED: Not all of them 21:37:13 ACTION: Erik to Investigate getIntersectionList and add clarification to the specification 21:37:13 Created ACTION-2695 - Investigate getIntersectionList and add clarification to the specification [on Erik Dahlström - due 2009-11-26]. 21:38:45 Topic: Deprecating CSS Value 21:38:51 http://lists.w3.org/Archives/Public/www-svg/2009Nov/0054.html 21:39:03 ED: Don't know if there is anything we can do 21:39:08 s/CSS Value/CSSValue/ 21:39:20 ... but we could put some informative note in the 1.1 specification 21:39:29 ... saying don't use this 21:39:33 ... or deprecate it 21:39:39 DS: Not sure if you can deprecate it 21:39:54 ED: So an informative note 21:40:03 ... it's a bit harder if we want to remove stuff I guess 21:40:23 ... I don't think any user agent implemented that to a large degree 21:40:47 ... Opera did for colour and it was hard 21:40:58 DS: Actually maybe we should deprecate it 21:41:03 ... then we don't have to test it 21:41:12 s/hard/hard to use/ 21:41:33 ED: Is it possible for us to do that? 21:41:52 ... what does it mean, it doesn't remove it? 21:42:14 DS: Discourage people from using it and tells them we will remove it later 21:42:53 deprecate SVGStylable.getPresentationAttribute and SVGPaint, SVGColor (which inherit from CSSValue) 21:44:10 ACTION: Erik to Deprecate SVGStylable.getPresentationAttribute and SVGPaint, SVGColor in SVG 1.1 2nd Edition 21:44:10 Created ACTION-2696 - Deprecate SVGStylable.getPresentationAttribute and SVGPaint, SVGColor in SVG 1.1 2nd Edition [on Erik Dahlström - due 2009-11-26]. 21:46:03 Topic: CSSUnit and Values 21:46:19 DS: We will put this off for 2.0 21:46:33 RESOLUTION: We will put this off for SVG 2.0 21:46:42 ED: We should have an issue for it 21:46:55 http://www.w3.org/Graphics/SVG/WG/track/issues/2278 maybe? 21:47:27 ... maybe we should raise a new issue 21:49:51 ISSUE-2300 21:49:53 btw 21:49:59 -anthony 21:50:05 -Shepazu 21:50:11 -ed 21:50:13 -jwatt 21:50:15 GA_SVGWG()3:00PM has ended 21:50:16 Attendees were ed, Shepazu, jwatt, anthony 21:50:28 Zakim, bye 21:50:28 Zakim has left #svg 21:50:37 RRSAgent, make minutes 21:50:37 I have made the request to generate http://www.w3.org/2009/11/19-svg-minutes.html anthony 22:50:34 shepazu: if you send out that email to find out what the SVG-oldies reasoning was for making the second arg for getIntersectionList be paint order, can you CC me?