- From: Michael[tm] Smith via GitHub <sysbot+gh@w3.org>
- Date: Sun, 24 May 2020 00:17:15 +0000
- To: public-svg-issues@w3.org
> Thanks for that link, @sideshowbarker. To confirm: although the folder is called `svg11`, you've been updating it in place for SVG 2 features, correct? Correct. More specifically, the aspiration is for it to conform to whatever the current SVG spec happens to require — regardless of what version label the spec might have — in the same way that the schema intends to conform to the current requirements in the HTML (Living) Standard. > The [history](https://github.com/validator/validator/commits/master/schema/svg11) shows that you've added support for a number of new features. Right — but it’s worth noting I’ve only done on that case-by-case, just in response to bug reports from user/developers. Specifically, I’ve not done any systematic audit against the changes made to document-conformance requirements in the spec between SVG 1.1 and the current SVG spec. But if others are able to examine the requirements changed between SVG 1.1 and the current SVG spec, and create issues/PRs for any cases found where the schema and checker aren’t conforming to the current spec requirements, then I’d be happy to spend time updating the schema to bring it into conformance. One thing that’s also worth keeping in mind is that in the checker architecture, the requirements aren’t addressed only by that schema but also by an accompanying datatype-checking library and by some additional custom (Java) code. https://github.com/validator/validator/blob/master/src/nu/validator/datatype/SvgPathData.java for example, a part of the datatype library, is for checking the `d` attribute’s datatype/microsyntax. -- GitHub Notification of comment by sideshowbarker Please view or discuss this issue at https://github.com/w3c/svgwg/issues/699#issuecomment-633157642 using your GitHub account
Received on Sunday, 24 May 2020 00:17:17 UTC