SVG Working Group Teleconference -- 22 Feb 2010

<trackbot> Date: 22 February 2010

<shepazu> no it's not...

<shepazu> oh, nm

<shepazu> trackbot, end telcon

<trackbot> Meeting: SVG Working Group Teleconference

<trackbot> Date: 22 February 2010

CSS/SVG fx taskforce

<ed> http://lists.w3.org/Archives/Public/www-svg/2010Feb/0041.html

<scribe> Scribe: anthony

DS: Called out because of loose wording for optical kerning
... for text wrapping
... I'll try to work up some diagrams

ED: I would have to agree to John
... that it is a lower priority
... compared to other coordination issues

DS: It still is important, so wouldn't want to bury it

ED: Was hoping to have more people on the call
... might have to coordinate by email

DS: With respect to priorities I could add to the charter a priority for a list of deliverables
... I could put them in an order for highest to lowest priority

ED: Sounds good to me anyway

AG: Might want to add wording to say that the priorities may change

DS: This document can be a live document
... wouldn't be subject to the process constrains of a WG charter
... the work is in the respective charters, this is a document about how we are going to do the combined work

<dsinger> I think we shoulda reminded CSS (and Zakim :-()

<dsinger> I'm here (muted)

<dsinger> we are happy to talk about harmonizing 2D transforms and transitions...

<dsinger> 3D transforms are further off, and animations are more...controversial

AG: What about 3D Transforms any common ground there?

dsinger: Yes, I think the demand for them is not as high

DS: How are we going to do these deliverables?
... single specification by both groups?
... syntax for CSS & SVG?
... 2 specifications?

<dsinger> I really don't know! Good questions for the list, perhaps?

DS: 3 specifications?
... My suggestion is one deliverable that has the SVG and CSS syntax
... since the CSS is applicable to SVG and HTML
... and the SVG may also be applicable to HTML
... not sure how the CSS WG would feel about that

ED: That's a good question to put to the list
... haven't seen much activity on the list

DS: I think if we start having conversations there people will start subscribing

ED: Don't like the cross posting thing either

DS: Maybe the first few messages we send we can BCC both CSS and SVG
... so when they reply the can reply to the list

<scribe> ACTION: Anthony to Send an email about the possibly of a combined specification for 2D Transforms for CSS & SVG and then a single specification for 3D Transforms [recorded in http://www.w3.org/2010/02/22-svg-minutes.html#action01]

<trackbot> Created ACTION-2731 - Send an email about the possibly of a combined specification for 2D Transforms for CSS & SVG and then a single specification for 3D Transforms [on Anthony Grasso - due 2010-03-01].

<scribe> ACTION: Erik to To email the list about canned filter effects [recorded in http://www.w3.org/2010/02/22-svg-minutes.html#action02]

<trackbot> Created ACTION-2732 - To email the list about canned filter effects [on Erik Dahlström - due 2010-03-01].

<scribe> ACTION: Doug to Respond about the optical kerning and text wrapping [recorded in http://www.w3.org/2010/02/22-svg-minutes.html#action03]

<trackbot> Created ACTION-2733 - Respond about the optical kerning and text wrapping [on Doug Schepers - due 2010-03-01].

Charter Priorities

DS: Gradient and paint servers?
... I think high

ED: Yes I think they are high

DS: 2D Transforms/3D Transforms?

AG: 2D high, 3D medium

DS: Filters and Canned effects?
... high

ED: I think so

DS: Animations and transitions?

ED: Animations medium, transitions high

DS: I think Apple want to get transitions out soon
... so Transitions high, and Animation medium
... Parameters?
... Medium
... Advanced Text Layout

<ed> s/ED: Animations high, transitions medium?/ED: Animations medium, transitions high/

DS: Low
... Content layout
... and calc
... Low/medium

ED: Not sure if you saw the feedback but one of the guys implemented the image fit in Opera
... and we might need to coordinate on that
... we might have to make changes in the SVG spec as well
... but possibly it could fit everything in the CSS one
... Anything else on the list?

DS: Think that's it

Test suite for 1.1se

ED: I started go through the test suite and noting down the issues as I went along
... I committed a few patches
... and there are still a few issues to be sorted
... I think we should use the new pass criteria in the template

AG: Do you want to email me the list of issue
... and I can start on them

ED: I'll note everything down as I go along

SVG 2.0

DS: I successfully got a cut down version of 2.0 building
... I used SVG Tiny 1.2 as a base
... started cutting down files
... until it was working
... the actual content is not in there yet
... but I'm going to start putting that in
... there are 2 more steps I'd like to do
... integrating new syntax
... have the build system output the syntax for the proposed spec conventions

<shepazu> http://www.w3.org/StyleSheets/spec-conventions.html

DS: come up with a classification status for the section of the spec
... one class that explains where it came from - SVG 1.1 SVG Tiny 1.2
... then either changed/needs review/reviewed

ED: possible to markup with a mix of both

DS: Say we get some stuff out of SVG Tiny 1.2. I would mark that up as needs review
... I would mark that paragraph as coming from SVG Tiny 1.2, but needs review

ED: I guess that makes sense. I'm just wondering if it's going to be simple to keep track of it
... I have a feeling it will get messy as you do more editing on it

DS: At as certain point it will be as complete as it can get and we can take out what the origin was
... I think it's useful to know what the origin was
... With SVG Tiny 1.2 it's missing elements and attributes
... I imagine we will need to refine this process
... but I'd like to get started
... It might be good as part of the process
... if we have a document that keeps track of what we are up to
... bit like a gotcha list
... when editing

ED: Understand what you mean
... I guess we can discuss it in the next telcon if you commit it soon

CSS Clip property

ED: Problem is CSS changed the way the clip property between version 1 and 2
... basically we have Robert Longson saying it would be nice to have implemented only one way
... I'm not sure if Webkit does CSS clip in SVG
... Opera does implement it for SVG elements and treat the clips differently

DS: Can we pick that up on Thursday?

AG: Do you think it's going to be a significant change?

ED: To reference CSS 2 will be a significant change
... from what I remember I think we said it would be a really big change to reference CSS 2.1

DS: for SVG Tiny 1.2

ED: I'm not sure if we discussed it in the context of 1.1
... I guess it will be interesting to know how bigger impact will be to change the reference
... Want to give an action about?

DS: Should raise an issue about it

ED: I'll raise the issue

- DRAFT -

SVG Working Group Teleconference

22 Feb 2010

Attendees

Contents

CSS/SVG fx taskforce

Charter Priorities

Test suite for 1.1se

SVG 2.0

CSS Clip property

Summary of Action Items

Scribe.perl diagnostic output