SVG QA activities: W3C validator adds SVG DOCTYPE overrides, and some more?
Posted by stelt apropos tools on Thu Oct 26th, 2006 at 14:21:45 BST
W3C has just updated its validator (known by anyone who has built more than a few webpages as THE validator) to include new options for SVG. A validator is important to ensure that content intended to be SVG does indeed conform to the specification, so it reaps the advantages of a standard and to prevent later unpleasant surprises (to make sure that you haven't simply been coding to a single implementation, and that the content survives being repurposed). Before, the official W3C Validator insisted on having a DOCTYPE in your content, a controversial imposition that not all authoring tools followed. The more flexible 'Jiggles' only accepts SVG 1.0 content, so this is a welcome change to the Validator.
See the full story for more ongoing activities on validators and cross-viewer SVG (related, but not the same):
See the full story for more ongoing activities on validators and cross-viewer SVG (related, but not the same):
-The W3C validator is being developed into a more modular implementation called the Unicorn.
This also gives next to the fact that the W3C validator's source is available, an extra option for cooperation, namely combining output.
There are quite a few validators and related test tools around the web that could adjust their output format a little to fit a Unicorn setting.
A quite untraditional example are the SVG-specific hacks recently added to the Open Clip Art project. Not just detecting errors, but also help in fixing them, dodging viewer limitations and giving other advice its scope is potentially somewhat wider.
sidenotes:
-tested a random batch of SVG files in collections:Tango bugs, Wikipedia bugs (compare that to average HTML!)
-SVG validity doesn't imply SVG conformance
-Also test on several viewers! (for desktops: Batik and Opera give the most valuable error feedback, none is 100% perfect),
-SVG 1.2, no longer using a DTD, seriously improves validation
This also gives next to the fact that the W3C validator's source is available, an extra option for cooperation, namely combining output.
There are quite a few validators and related test tools around the web that could adjust their output format a little to fit a Unicorn setting.
A quite untraditional example are the SVG-specific hacks recently added to the Open Clip Art project. Not just detecting errors, but also help in fixing them, dodging viewer limitations and giving other advice its scope is potentially somewhat wider.
sidenotes:
-tested a random batch of SVG files in collections:Tango bugs, Wikipedia bugs (compare that to average HTML!)
-SVG validity doesn't imply SVG conformance
-Also test on several viewers! (for desktops: Batik and Opera give the most valuable error feedback, none is 100% perfect),
-SVG 1.2, no longer using a DTD, seriously improves validation
SVG QA activities: W3C validator adds SVG DOCTYPE overrides, and some more? | 7 comments (7 topical, 0 editorial, 0 hidden)
SVG QA activities: W3C validator adds SVG DOCTYPE overrides, and some more? | 7 comments (7 topical, 0 editorial, 0 hidden)
Useful Links
- Create an account
- About SVG.org
- Frequently Asked Questions
- SVG.org Content with RSS

- Get SVG Help on IRC
- SVG.Open Conferences
- SVG Phones (169 and counting)
- JSR 226 Phones (28 and counting)
