19:28:06 RRSAgent has joined #svg 19:28:06 logging to http://www.w3.org/2008/11/24-svg-irc 19:28:08 RRSAgent, make logs public 19:28:10 Zakim, this will be GA_SVGWG 19:28:10 ok, trackbot; I see GA_SVGWG()2:30PM scheduled to start in 2 minutes 19:28:11 Meeting: SVG Working Group Teleconference 19:28:11 Date: 24 November 2008 19:28:26 GA_SVGWG()2:30PM has now started 19:28:26 +Shepazu 19:31:04 +??P14 19:31:05 Zakim, ? is me 19:31:05 -??P14 19:31:05 +??P14 19:31:05 +heycam; got it 19:31:32 +??P15 19:32:01 +??P16 19:32:04 Zakim, ??P15 is me 19:32:04 +anthony; got it 19:32:12 Zakim, ??P15 is me 19:32:12 I already had ??P15 as anthony, ed 19:32:18 Zakim, ??P16 is me 19:32:18 +ed; got it 19:32:53 +Shepazu.a 19:32:56 -Shepazu.a 19:33:04 -Shepazu 19:33:12 +Shepazu 19:34:03 Zakim, who's here? 19:34:03 On the phone I see Shepazu, heycam, anthony, ed 19:34:04 On IRC I see RRSAgent, Zakim, ed, heycam, shepazu, anthony, trackbot, ed_work 19:34:17 regrets: CL 19:35:34 scribe: anthony 19:35:42 Agenda: http://lists.w3.org/Archives/Public/public-svg-wg/2008OctDec/0396.html 19:35:44 chair: Erik 19:36:02 Topic: Upcomming F2F meetings 19:36:21 ED: I saw that it was discussed at the last telcon 19:36:35 ... is there a registration page up for it? 19:36:44 DS: No, but I'll make one up now 19:42:14 ED: For the next F2F after that we are planning on having it in France? 19:42:36 DS: Raliegh 19:44:35 ... I'm going to Web Directions North in the first week of Feb 19:47:48 http://www.w3.org/2002/09/wbs/19480/SydneyF2F2009/ 19:48:26 DS: Registration link is there, adding it to the wiki page now 19:51:35 Topic: HTML and SVG coordination 19:51:51 ED: We did start some discussion at the TPAC with the HTML WG 19:52:00 ... we decided a number of goals for SVG inside of HTML5 19:52:14 ... probably didn't finish the discussion 19:52:25 DS: I think we should make this a priority 19:53:13 ... at the F2F in short the SVG WG acknowledged that it is desirable to have error correction 19:54:01 ... SVG should be in XML syntax and if the content creator doesn't make it in that syntax then error 19:54:06 ... correction is applied 19:54:20 CM: So it's a question of a validity 19:54:52 ... so I think it HTML they have various things that are parsing errors that get corrected 19:55:38 DS: The distinction is subtle but I'd like wording saying that the SVG is not correct but it will be corrected 19:56:35 ... E.g. There are certain elements that can't be left open in HTML5 19:57:12 ... We do see some benefit of this, but it should be serialised as XML 19:57:51 ... In HTML5 attribute values don't have quotes and this is allowed. But in SVG this is reported as an error 19:58:03 ... but in HTML5 this can be error corrected 19:59:32 CM: So there was in principle support for the error correction 19:59:59 DS: There should be no white list of SVG elements, any SVG element that is legal in SVG should be allowed 20:00:32 ... And it doesn't matter what language we are putting in there. The author shouldn't have to do anything special when they are 20:00:36 ... putting in SVG 20:01:14 s/error correction/that view of document validity and error correction?/ 20:01:52 ... so the white list only be that of what is supported by implementations rather than a specification 20:02:52 ... I think the parser requires a list of element stings 20:03:27 ... we may need to make some distinction about how SVG is treated 20:04:25 ... there were conflicts in names "a" element, "textArea", "font", "metadata" they were essentially black listed 20:04:36 ... they shouldn't be black listed or white listed 20:04:46 ... what are the next steps we need to take? 20:04:59 CM: Someone should write up the scheme you described? 20:06:25 DS: I need to go back and read Ian's proposal 20:07:28 ... he says exactly how it needs to be parsed, but if an implementation wants to parse it differently 20:07:38 ... then this should be allowed 20:07:49 ... it shouldn't say that you can't 20:08:06 CM: You wouldn't want those two different ways to result in different output 20:08:21 DS: Ideally no 20:08:32 ... I guess you have a point 20:09:11 CM: Uniform parsing is one of the requirements of HTML5 20:09:38 ED: Do we need to talk to the HTML Working Group again regarding the goals? 20:09:50 ... I'm wondering if Ian has everything he has to make a new proposal? 20:09:58 ... or if he needs more info 20:10:19 DS: We should probably come back with an email saying these are the goals we agreed to at TPAC 20:10:49 ... we'd like to move forward with this 20:11:05 ... perhaps we should have a conversation on our email list first 20:11:11 ED: Sure, I can do that 20:12:16 DS: We had some proposals some went down to the parser level. We have said that the HTML parser can be used to parse SVG 20:12:33 ... so it should be easier to say these are the goals that should be met 20:13:47 ... Simply putting it in the spec may not be good enough. We need to consider the implications of what's in there. 20:13:58 ... Compared to SVG in strict XML 20:14:08 ED: I will send an email out about this 20:14:23 ... and try to collect the goals we decided on 20:15:35 ACTION: Erik to Send an email to the SVG Working Group regarding the goals that were decided on at TPAC for SVG in HTML 20:15:35 Created ACTION-2355 - Send an email to the SVG Working Group regarding the goals that were decided on at TPAC for SVG in HTML [on Erik Dahlström - due 2008-12-01]. 20:15:54 Topic: Errata 1.1 20:16:34 ED: Has something been done about this? 20:16:42 AG: I had an action to split out the 1.1 20:16:50 ... but I haven't gotten around to doing this 20:17:39 ED: I think it would be helpful to check in what's been done on 1.1 2nd edition 20:18:18 http://www.w3.org/Graphics/SVG/Group/repository/errata/errata.xml 20:18:54 Undefined Behaviour with Filters 20:18:55 http://www.w3.org/Graphics/SVG/Group/repository/errata/errata.xml#undefined-behaviour-with-filters 20:19:23 ED: It's about 8 years old 20:22:54 ... His example is about making something less transparent, why not use opacity? Or am I missing something 20:23:41 DS: I think we should skip this one 20:23:56 ... and see if we can solve this in the next filters module 20:24:20 ... perhaps we can raise an issue on the filters module for this 20:24:52 CM: I think he's saying that the initial canvas is undefined 20:27:12 ... but I think that it might be 20:27:16 ISSUE-2185? 20:27:16 ISSUE-2185 -- Update SVG 1.2 Tiny to account for the change in the default overflow property in SVG 1.1 -- RAISED 20:27:16 http://www.w3.org/Graphics/SVG/WG/track/issues/2185 20:27:18 Topic: ISSUE-2185 20:28:02 DS: The paragraph in question is the last one in 7.10 20:28:27 http://lists.w3.org/Archives/Public/public-svg-wg/2008JulSep/0344.html 20:28:34 ... it seemed to me that we should correct this to match the behaviour we are allowing which is here 20:28:50 ... that overflow is only hidden for things that are not root 20:28:59 ... I think that was for SVG elements only 20:29:30 the element 20:29:44 ... I thought they were talking about the root element 20:30:02 ED: That's at least how I understood the elemail from David H 20:30:18 ... I guess we could do some slight rewording if you want 20:30:49 DS: Doesn't it contradict 20:31:01 ED: It's still informative 20:31:59 DS: We could say that this paragraph is missinformative =P 20:32:30 s/missinformative/misinformative (or possibly disinformative) 20:32:37 s/missinformative/misinformative (or possibly disinformative)/ 20:33:11 DS: We could add 20:33:31 [[ since the initial value for the 'overflow' property is hidden for non-root elements that establish viewports ([SVG11], section 14.3.3). ]] 20:33:48 DS: That would satisfy me 20:34:11 ... and that would accurately describe what we are doing for SVG 1.1 20:34:22 ... I don't know if saying initial value is exactly right 20:34:41 http://www.w3.org/TR/2003/REC-SVG11-20030114/masking.html#OverflowProperty 20:34:43 CM: I think the property only has one initial value 20:34:59 ED: Overflow is pretty verbose 20:35:09 ... different initial values depending on the element 20:35:46 DS: We probably should try to correct more than we want to at this time 20:35:54 ... this will change eventually 20:36:16 s/... I don't know if/CM: I don't know if/ 20:36:34 Resolution: We will change the informative section 7.10 to match the wording of the SVG 1.1 errata 20:38:03 ACTION: Doug to Make the change as agreed to for ISSUE-2185 20:38:03 Created ACTION-2356 - Make the change as agreed to for ISSUE-2185 [on Doug Schepers - due 2008-12-01]. 20:38:57 DS: As issues come in for spelling and typos, I am correcting them in Master, but not in the Published (PR) draft 20:39:10 ... whenever we go to Rec they will appear in it 20:41:11 http://www.w3.org/Graphics/SVG/Group/repository/errata/errata.xml#script_animatable_xlink_href 20:41:18 Topic: Errata items 20:42:22 ED: This one is about xlink:href is animatable 20:42:35 ... in Tiny 1.2 we say it can't be 20:43:00 CM: Is this because xlink:href is defined one place? 20:43:05 ED: It could be 20:43:17 ... I think some have it in the attribute list 20:43:36 CM: It's mentioned in "use" for example 20:43:48 ... maybe it should be something we have for Core 20:44:00 ... list the attributes for each element def 20:44:13 DS: I already raised an issue on that already 20:44:39 ... the build script should build it form the schema 20:44:49 ED: I would to move this errata item to proposed 20:45:37 AG: I don't have any problems with this one 20:46:03 Resolution: We will move the Errata item "Clarify if xlink:href on