SVG 1.2 Tiny, previously in CR, went back to LC today.Â Which might seem like a step backwards, but is really a huge leap in the right direction.
Okay, you have no idea what I’m talking about, right?Â So, the W3C’s Recommendation track looks something like this:
- Editor’s Draft, where ideas are just being hashed out
- First Public Working Draft, where we have the basic direction, but still in rough form, and are seeking initial public feedback
- incremental Working Drafts, where the draft spec improves over time, based on review and comments
- Last Call Working Draft, where we pretty much think it’s done, and ask the public to give it a final once-over
- Candidate Recommendation, in which the spec is mostly stable, and where we invite implementors to actually write the code and provide the wisdom of experience
- Proposed Recommendation, where the W3C Members get a final chance to say what they like, don’t like, and provide their official comments for consideration to the Director
- Recommendation, where the Director (usually Tim Berners-Lee, in consultation with trusted advisors) looks at the spec, looks at the comments, and decides whether or not this should have the stamp of approval from W3C.
On the surface, SVG 1.2 Tiny going from Candidate Recommendation to Last Call seems rather counter-productive.Â But the truth of it is, the SVG spec has changed quite a lot for the better, due to lessons learned during implementation and building a test suite.Â But change is change, and if you change the spec any time before Recommendation status, you go back to Working Draft (in this case, Last Call Working Draft).Â This lets everyone review the current spec, and provide critical feedback before we move forward again.Â But with a solid test suite (though no test suite is ever really done), and several interoperable implementations, the current state of SVG 1.2 Tiny is much improved over the previous Last Call, so the path to Recommendation is actually much clearer this time.
I’m really proud of the work the SVG Working Group has done, and I’m honored to have been part of it.Â I’m glad that we are now a public working group, so people can see what we are working on and help steer us in the right direction (especially with the new SVG Interest Group that I co-chair with Jeff Schiller).Â I’m relieved that the long haul of completing SVG 1.2 Tiny may be coming to an end.Â And I’m confident that this specification will really push SVG forward.
And have we got some cool things planned for the coming months!!