06:30:26 RRSAgent has joined #svg 06:30:26 logging to http://www.w3.org/2009/10/28-svg-irc 06:30:28 RRSAgent, make logs public 06:30:28 Zakim has joined #svg 06:30:30 Zakim, this will be GA_SVGWG 06:30:30 ok, trackbot; I see GA_SVGWG()2:30AM scheduled to start now 06:30:31 Meeting: SVG Working Group Teleconference 06:30:31 Date: 28 October 2009 06:31:04 GA_SVGWG()2:30AM has now started 06:31:11 +??P0 06:31:21 Zakim,??P0 is me 06:31:21 +ed; got it 06:35:30 +Doug_Schepers 06:36:06 +??P2 06:36:13 zakim, ??P2 is me 06:36:13 +anthony; got it 06:41:03 http://mcc.id.au/2007/03/telcon/ 06:46:49 Scribe: anthony 06:46:53 Chair: Erik 06:46:56 Topic: Telcon Times 06:47:16 DS: I see 20:00 UTC 06:47:26 ED: That would be 21:00 for Chris and me 06:48:01 AG: That would be 8:00am following day for me 06:48:16 DS: Marked 18:30 on Monday as bad 06:48:53 ... no wait just double checking 06:49:16 ... we talked about 19:00 to 20:30 UTC 06:50:51 ... Chris marked 19:00 to 20:30 UTC as best and then good 06:51:08 ... for him that would be 20:00 to 21:30 UTC + 1 06:51:23 ED: I would prefer to start 20:30 UTC + 1 06:51:42 ...or better still 21:00 UTC+1 06:52:16 DS: Chris has that for Monday and Thursday as good and best 06:52:21 ... for me that would be 06:53:18 ... 15:00 my time 06:53:53 AG: So for me that would be 7am the following day which is fine 06:56:15 DS: Starting at 20:00 UTC and going for an hour and a half 06:56:24 ... one thing Chris said wanted to have a block of time 06:56:28 ... before and after 06:56:37 ... for getting together to do work 06:57:14 ... we could have this as an understood convention 06:57:19 ... that this is going on 06:57:29 ... and is time to use for actions 06:57:39 ... just a convention to follow, more for him 06:57:52 ... I'll probably do the same thing 06:58:17 ED: Did we want to go for two telcons or one 06:58:22 DS: I think we should go for two 06:58:29 ... so lets go ahead and block off those times 06:58:32 ... just incase 06:58:48 ED: That would be Monday and Thursday 20:00 UTC 06:59:37 RESOLUTION: We will change telephone conference times to Monday and Thursday 20:00 UTC 07:00:29 ACTION: Erik to Email the change of telephone conference times to the group and update the wiki page with the new times 07:00:29 Created ACTION-2687 - Email the change of telephone conference times to the group and update the wiki page with the new times [on Erik Dahlström - due 2009-11-04]. 07:01:02 DS: Chris and I will not be at the telcon next week 07:01:09 ... because we will be at TPAC 07:01:26 ED: So the new times will be active the week after next 07:01:49 ... I think it's Monday 9th 07:02:04 ... Doug you will make sure Zakim knows the new times as well? 07:02:11 DS: I'll change that now 07:04:49 Topic: SVG Full 1.1 Marathon 07:05:02 ED: Should we start off with having a telcon 07:05:14 ... or is it fine to do the work normal office hours? 07:05:26 ... for me it will be fine to have a telcon at the time we usually have 07:05:30 ... just to start off 07:05:49 DS: I'm not fussed either way 07:07:52 ED: Try to be available on IRC and try to be available for a small telcon will be good 07:07:59 ... I pretty much know what I need to do anyway 07:08:07 ... I thought I'd move some of the tests from the old errata location 07:08:13 ... to the test suite 07:08:23 ... we have some tests there that cover some things that are not tested at the moment 07:08:32 ... we need to do some more reviewing of tests 07:08:42 ... and make sure the Java binding appendix goes in 07:12:53 AG: Do we want the svgweb version to be available as a local version only or as a web version or both? 07:13:38 ED: It would be convenient to have the svgweb version as an online reference 07:13:44 ... if you have time you can do both 07:15:14 Topic: Rendering Order and Z-Index proposal 07:15:33 ED: I guess we could discuss it but Chris and JWatt are not here 07:15:42 DS: I saw JWatt's proposal 07:15:48 ... and it seemed reasonable 07:16:04 ... I'm not totally convinced it covers all the use cases we have 07:18:59 ... Andrew's doesn't seem like it has effective preventions for abuse 07:19:23 ... JWatt's provide a consistent method for resolving complicated cases 07:19:32 ... I think that if we do this 07:19:39 ... we should caution people to use this sparingly 07:19:50 ... and talk about cases with hit testing 07:20:21 ED: cases I've seen this pop up is pseudo 3D 07:20:34 DS: We should also think of this in the context of 3D Transforms 07:21:21 ... we should look at tightly integrating this with 3D Transforms 07:21:30 +??P3 07:21:48 Zakim, P3 is me 07:21:48 sorry, jwatt, I do not recognize a party named 'P3' 07:21:56 Zakim, ??P3 is me 07:21:56 +jwatt; got it 07:23:20 DS: I personally like the idea that z-index would be the name of the property 07:23:38 ... I think people who are using z-index from HTML and CSS will know what they are looking for 07:23:46 ED: Being able to move elements in the tree 07:23:53 ... without taking them out of the tree 07:24:05 ... is useful 07:24:44 ... it gives you z-index type benefits for some operations 07:25:03 DS: I think it's orthogonal, both are useful 07:25:10 ED: It doesn't complicate the rendering model 07:25:17 ... but I guess people want z-index anyway 07:25:25 DS: It only works when using scripting 07:26:12 ... this sounds like something for DOM 4, like what happens when you move an element - do you reload it 07:26:27 ... I think the best thing to do is move forward on z-index with the CSS 07:26:43 ... this is something to think about this for 3D Transforms anyway 07:27:14 ... when you are structuring documents specifying things in z-index can be very useful 07:35:11 -anthony 07:35:54 +??P2 07:36:01 Zakim, ??P2 is me 07:36:01 +anthony; got it 07:36:15 ... we should stay what happens in the default case that when a transform z puts something behind something else 07:36:30 ED: The proposal from JWatt is that being put into spec text? 07:36:44 JW: Would it be better to put it into something 07:36:52 ... instead of it's own stand alone document 07:37:05 ... seems a bit weird to have a single property in it's own document 07:38:00 DS: Let's say that we have this single property defined if an implementer wanted to do SVG 1.1 + this 07:38:06 ... that would permit them to do so 07:38:23 ... they could say we implement SVG 1.1 and this 07:38:44 JW: What's the difference to them taking it out of a spec 07:38:51 ... and saying they just do that 07:38:59 ... feature? 07:39:58 DS: People will want very clear conformance criteria to say they support a particular spec 07:41:39 JW: As an implementer I can see the bits and I put it together 07:41:47 ... but as an author it's difficult 07:42:01 ... having picking and choosing things can make things worse 07:42:23 ... for example people might just implement it because it's part of spec 07:44:33 DS: What about putting it into 3D Transforms? 07:44:58 JW: Well I'm not opposed to having it as separate spec or putting it somewhere 07:45:24 ... I just don't see how it's going to be easier to comment on 07:52:33 DS: The more I think about it I think it belongs in compositing 07:52:45 ED: Because it affects the rendering model 07:52:55 ... it should go into render concepts 07:53:04 DS: Certainly that's where it should go in 2.0 07:57:17 AG: [rambles on about defining a rendering model spec to bring all the work together] 07:58:19 ED: Do we want to start the rendering concepts spec right away 07:59:51 ... or do we need to something fire? 07:59:57 s/fire/first/ 08:00:05 DS: I think that is a very useful level 08:02:09 ... start with the rendering model from 1.2 08:02:18 ... reconcile that with 1.1 08:02:23 ... put in rendering index 08:05:05 RESOLUTION: We will start writing a rendering concepts specification detailing the rendering model 08:05:53 ACTION: Jonathan to Begin authoring the rendering concepts specification 08:05:53 Created ACTION-2688 - Begin authoring the rendering concepts specification [on Jonathan Watt - due 2009-11-04]. 08:06:46 Topic: list collection 08:07:19 DS: right now you create a list collection and you put it into the newest collection 08:07:30 JW: I sent two replies to that 08:07:45 ... did you see them? 08:07:53 DS: I only saw one of them 08:08:15 ED: Forgot to CC Doug 08:08:22 ... I would like this feedback to go to the public list 08:14:07 JW: We plan to implement what the spec says 08:14:16 ... probably do it at the same time we do animation for lists 08:14:25 ... code needs to be rewritten for animaiton 08:14:36 ED: Doing live objects and removal of lists 08:14:43 ... there's no extra costs 08:14:49 ... you do one you get the other one free 08:14:58 JW: My opinion you do it live 08:15:26 s/removal of lists/removal of objects from previous lists/ 08:15:51 ... you take one matrix from one list and put it into another list then you have two elements using the same matrix 08:16:14 ... you have to tell both elements when one changes 08:16:32 ... so if using hundreds of elements this can be a performance hit 08:16:49 DS: Seems like you guys both agreed that it's better to do it this way 08:17:03 Topic: CSS pseudo classes for 08:17:26 DS: Do you guys agree that CSS pseudo classes should be supported in SVG? 08:17:36 ... even though they aren't 08:17:41 ED: They are in Opera 08:17:45 ... and in FireFox 2 08:17:56 JW: Just consistency in the web platform 08:17:59 s/2/too/ 08:18:36 ED: It's a bug if it doesn't work 08:18:38 s/even though they aren't/even if they aren't 08:21:17 -anthony 08:21:18 -jwatt 08:21:18 -Doug_Schepers 08:21:20 GA_SVGWG()2:30AM has ended 08:21:21 Attendees were ed, Doug_Schepers, anthony, jwatt 08:21:26 Zakim, bye 08:21:26 Zakim has left #svg 08:21:32 RRSAgent, make minutes 08:21:32 I have made the request to generate http://www.w3.org/2009/10/28-svg-minutes.html anthony