Hi, bulia-
bulia byak wrote (on 7/16/10 4:34 PM):
On Fri, Jul 16, 2010 at 4:40 AM, Jasper van de Gronde
However, don't let that stop you. In my mind the right solution here wouldn't be to make SVG simpler, but rather to make it easier to make a renderer. One of the things I've been thinking about is making a different (much more basic) format and defining how SVG maps to that format. At the very least it would make the standard much less ambiguous, but I expect it would also help in finding problem areas, and it could help implementations by suggesting a way to break down rendering.
That is a good idea I think. Right now, we often use Batik as the "standard" because in the spec, there are many unclear and confusing areas.
If there are areas which are unclear or confusing, you should ask for clarification on the SVG mailing list, www-svg@...2382... We continually issue errata, and right now are in the process of publishing an update, SVG 1.1 Second Edition, to roll some of these errata back into the spec. Browser vendors, other implementers, and even content creators have filed numerous "bugs" with the spec, and we try to correct them as quickly as possible; in addition to clarifying the text in the spec, we try also to make a new test for that feature, so it is clear to implementers what is expected.
Now is an especially good time to report problems with the spec, because it gives us an opportunity to improve it for SVG 2, which we have begun work on. If you have a list of specific issues, we would be very happy to see them.
If we had a "basic SVG", for example with featureset of Postscript, and a strictly-defined mapping from the rest of SVG to basic, it would help implementers a lot.
I'd be concerned about profiling SVG, since that risks fracturing consistency of support. You expressed concern about this lack of consistency in different implementations, and profiling tends to promote such fracturing. However, it's true that only certain features of SVG make sense to implement in a static authoring tool (for example, scripting doesn't necessarily make sense for a drawing tool.
Perhaps if you explained a bit more what you're looking for, and gave some examples, we could help address your needs in SVG 2. Maybe we could mark specific sections as applicable to different classes of user agent, such as static authoring tools.
Regards- -Doug Schepers W3C Team Contact, SVG and WebApps WGs