See also: IRC log
<trackbot> Date: 29 January 2015
<ed> agenda: https://lists.w3.org/Archives/Public/www-svg/2015Jan/0035.html + http://www.w3.org/Graphics/SVG/WG/wiki/Agenda
<AmeliaBR> ScribeNick AmeliaBR
<ed> https://svgwg.org/svg2-draft/painting.html#OrientAttribute
<AmeliaBR> ed: I put an issue in spec text, some things are not well defined currently. Specifically, how to compute the directionality of markers.
<AmeliaBR> ... some guidelines are in the path implementation notes, but this doesn't cover all aspects. E.g. Issue 18, when a curve segment has a null control point (coincides with end point). Should the direction be the direction of the visible line?
<AmeliaBR> ...that requires looking at previous points to calculate geometry. Otherwise, if you only use control point, direction is undefined.
<AmeliaBR> Tav: I agree, use the visible line. This is what Inkscape does.
<AmeliaBR> ed: I think there might be other similar issues, e.g. in stroking. We should have a clear definition for all cases.
<AmeliaBR> ... The text currently in SVG 2 draft has changed from 1.1, some wording has been lost. I'm not sure if re-introducing the text will address all issues. I suspect Cameron (who's not here today) might have the best idea of why the changes were made.
<AmeliaBR> Tav: I think I had the same issue with arc line joins, had to go back to previous points to figure out the direction.
<AmeliaBR> ed: Did you make a specific issue in the spec?
<AmeliaBR> Tav: I don't think so, I'll have to dig up my code.
<AmeliaBR> ed: Should we resolve to add instructions to look at all points as necessary to calculate direction?
<AmeliaBR> Tav: I think so. We need to use the visible curve.
<AmeliaBR> AmeliaBR: I agree to, anything else would confuse people.
<AmeliaBR> ed: So next issue is where to define this. In an appendix?
<AmeliaBR> AmeliaBR: We already have some sections about detailed geometrical calculations at end, could add there.
<AmeliaBR> ed: makes sense.
<AmeliaBR> RESOLUTION: Instructions for orient attribute should require agents to calculate the visible directionality and curvature, even if they have to process multiple points.
<AmeliaBR> Tav: There are also issues in implementing markers on closed paths. I'll talk about that more at Sydney.
<ChrisLittle> zakim 388.aaa is me
<AmeliaBR> ed: I could take the action to come up with proposed text, although Cameron has been doing most of the marker work.
<AmeliaBR> ACTION on Cameron: Draft text to implement the resolution just passed re orientation of markers.
<trackbot> Error finding 'on'. You can review and register nicknames at <http://www.w3.org/Graphics/SVG/WG/track/users>.
<AmeliaBR> ACTION: Cameron to Draft text to implement the resolution just passed re orientation of markers. [recorded in http://www.w3.org/2015/01/29-svg-minutes.html#action01]
<trackbot> Created ACTION-3699 - : draft text to implement the resolution just passed re orientation of markers. [on Cameron McCormack - due 2015-02-05].
<ed> scribeNick: ed
<AmeliaBR> Bogdan: (?): We tried to quantitatively assess how many issues remain, and assigned editors to chapters, as indicated in linked wiki page.
<scribe> scribenick: AmeliaBR
Tav: I want to make clear, annotations are not necessarily an indication of things that need to be changed. Some explain why we made a change; they should be changed in the final version.
Bogdan: That's good to know.
ed: Do you think it is useful to go through the remaining chapters to clear up all remaining issues, or is that too early?
Bogdan: I think it's too early.
There are many issues remaining, too much for a call. But I
think we can set up teams to work through those issues.
... I'd appreciate if people can review the table (in linked
wiki) and make sure it looks right for the summary of issues
and work to do.
ed: I think it looks good as a kind of litmus test of readiness.
Bogdan: I think we can probably make some progress before the face to face, I don't want to waste time by waiting to start at that meeting.
ed: I think I will go through (review and try to do some actions) the specs before then.
Bogdan: One thing I'm concerned, is that some issues may be showing up only because they haven't been correctly closed in the tracking system.
Tav: I think there are many issues that will require discussion, we haven't decided what to do
Bogdan: I realize some issues require discussion. But will we wait until we can go forward with all issues, or can we focus on this table and address the issues we can.
Tav: I think many of the issues are simple, and can be solved quickly in face to face.
ed: I think we should try to move forward, and make it clear to the larger community that we will be publishing smaller changes more frequently. I think that's what we previously discussed.
Bogdan: So should we announce something on mailing list?
ed: I think so, at least to www-svg and maybe CSS.
<scribe> ACTION: Bogdan to Compose email about intentions to devise the current spec, and move to a more rapid pace of updates [recorded in http://www.w3.org/2015/01/29-svg-minutes.html#action02]
<trackbot> Created ACTION-3700 - Compose email about intentions to devise the current spec, and move to a more rapid pace of updates [on Bogdan Brinza - due 2015-02-05].
ed: Send this to private working group list for review?
Bogdan: ... yep.
ed: Any agenda requests?
AmeliaBR: we could update on decisions from accessibility group.
Richard: We decided on a couple changes to the API mapping spec. A few issues have come up, but I don't think they will stop first-pass working draft. I've asked for review from the main PF working group as well, and we will be coordinating with the HTML mapping work.
<ChrisLittle> bye
SVG Accessibility minutes for more details: http://www.w3.org/2015/01/23-svg-a11y-minutes.html
<ed> trackbot, end telcon
ed: meeting adjourned then
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Succeeded: s/go through/go through (review and try to do some actions)/ Found ScribeNick: ed Found ScribeNick: AmeliaBR Inferring Scribes: ed, AmeliaBR Scribes: ed, AmeliaBR ScribeNicks: ed, AmeliaBR Default Present: [IPcaller], ed, Thomas_Smailus, stakagi, AmeliaBR, Tav, krit, nikos, birtles, [Microsoft], cabanier, ChrisLittle, Rich_Schwerdtfeger Present: [IPcaller] ed Thomas_Smailus stakagi AmeliaBR Tav krit nikos birtles [Microsoft] cabanier ChrisLittle Rich_Schwerdtfeger WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 29 Jan 2015 Guessing minutes URL: http://www.w3.org/2015/01/29-svg-minutes.html People with action items: bogdan cameron[End of scribe.perl diagnostic output]