- From: Amelia Bellamy-Royds <amelia.bellamy.royds@gmail.com>
- Date: Mon, 14 May 2018 13:44:04 -0600
- To: www-svg <www-svg@w3.org>
- Message-ID: <CAFDDJ7ymr6ToV8CCu+-Easdbc2rNhAScFdT4TmyD3ms+xng9jQ@mail.gmail.com>
Minutes are online: https://www.w3.org/2018/05/14-svg-minutes.html We were discussing path forward & features at risk for SVG 2 / 2.1 A few GitHub issues have already been opened based on the discussion, but too late for github-bot to copy over the conversation automatically. The following resolutions were made: 1. We'll focus on shipping SVG 2.0 by forking current master branch into two branches - master tracking SVG 2.0 and svg-next tracking next generation graphic technologies. SVG 2.0 will remove all features currently at risk and focus on testing and shipping inteoperable core of the specification as outlined in the charter 2. As we have an updated SVG 2.0 in master branch and publish an updated CR, we'll simultaneously publish FPWD of SVG 2.1 (tentative name) from svg-next branch to signal the group commitment to next generation graphical features 3. Remove mesh gradients and hatches from SVG 2.0, keep in 2.1 4. Remove <solidcolor> element and its solid-color / solid-opacity style properties from SVG 2 and 2.1 (I see I forgot to record a proper resolution, but we also agreed to make <cursor> fully obsolete.) See the minutes for the rest of the discussion. ~ABR
Received on Monday, 14 May 2018 19:44:30 UTC