- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Jul 2017 22:26:59 +0000
- To: public-svg-issues@w3.org
> I wonder how best to proceed? Should there be one PR with a large change (EBNF), then a number of small changes (bugs), then another large change (closepath)? Or should there be three PRs in the same order, or many? Given the state of SVG standardization & software implementer commitments, it would probably be very helpful if we can develop two versions of the grammar: - One that accurately describes the SVG 1.1 grammar in the new syntax, fixing things like the unintentional removal of floating-point numbers and scientific notation - One that includes the new features (bearing command and segment-completing closepath). Ideally, have those two features as separate commits, so that one or the other could be cherry-picked if we get implementer support for one but not the other. Similarly, for any other syntax fixes/changes relative to SVG 1.1, it would be nice to have a clear commit documenting changes relative to the SVG 1.1-equivalent grammar. But it would also be useful to have tests of what the current software support is like, to demonstrate whether this is really a "new feature" or a "make the spec reflect reality" situation. > But if nothing keeps happening, maybe there's enough volunteers to fork it and document the de facto standard. I've already told Tom, but I'll repeat here: for things that are obvious errors (like floats vs integers, unintentionally changing the grammar relative to SVG 1.1), we can probably at least merge them in to the [Editor's Draft](https://svgwg.org/svg2-draft/), which is built from the master branch of this repo. However, we'd need to keep careful note of what changes are being made and why, so that eventually it can be merged back in to the official W3C spec process. To eventually merge it back into the W3C process, we'd also need to have licensing agreements from anyone contributing content that would become part of the spec. See the [Contributing guidelines for this repo](https://github.com/w3c/svgwg/blob/master/CONTRIBUTING.md), and the [W3C FAQ](https://www.w3.org/2003/12/22-pp-faq#non-participants). -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/svgwg/issues/335#issuecomment-318201125 using your GitHub account
Received on Wednesday, 26 July 2017 22:27:00 UTC