- From: David Storey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 May 2018 05:51:07 +0000
- To: public-svg-issues@w3.org
dstorey has just labeled an issue for https://github.com/w3c/svgwg as "SVG Paths": == SVG Paths spec vs Paths chapter of SVG2 == https://svgwg.org/ lists an SVG Paths Editor's Draft at https://svgwg.org/specs/paths/ , but the SVG 2 ED also has a Paths chapter with similar content: https://svgwg.org/svg2-draft/paths.html . The situation is similar with some other drafts/chapters. It looks like the intention was to move some chapters into separate "module" specs, which sounds good. Except that the "old" chapter is still there, is apparently getting many more commits since the module spec was created: - https://github.com/w3c/svgwg/commits/master/master/paths.html - https://github.com/w3c/svgwg/commits/master/specs/paths To add to (my) confusion, the path module has at least one new (since SVG 1.1) feature that’s not in SVG 2 (Catmull-Rom commands). Shouldn’t one of the two copies at least have a big red warning saying "Don’t at this, look at the other one [link]"? Or better yet, be entirely removed and replaced with a link, like how the Transforms section https://svgwg.org/svg2-draft/coords.html#TransformProperty now only links to css-transforms? In the mean time, as an implementor, which spec should I read? See https://github.com/w3c/svgwg/issues/148
Received on Friday, 4 May 2018 05:51:26 UTC