- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Mon, 04 Jul 2005 04:26:48 +0200
- To: www-svg@w3.org
Dear Scalable Vector Graphics Working Group, http://www.w3.org/TR/2005/WD-SVGMobile12-20050413/feature.html seems to be quite inconsistent with respect to feature strings for attributes and properties. For example, image-rendering, shape-rendering, and text- rendering have associated feature strings but color-rendering does not. More generally, it is not clear when requiredFeatures for a given string would return true; that some attributes have feature strings seems to imply that it might be possible for an implementation to return true for http://www.w3.org/Graphics/SVG/feature/1.2/#Shape even though it does not support http://www.w3.org/Graphics/SVG/feature/1.2/#PaintAttribute it is however not clear whether this is the case. For http://www.w3.org/Graphics/SVG/feature/1.2/#SVG-all it is not clear whether http://www.w3.org/Graphics/SVG/feature/1.2/#SVG-static-DOM must return true aswell, the draft only notes that all the features that correspond to the latter must be supported; the definition for http://www.w3.org/Graphics/SVG/feature/1.2/#SVG notes "At least one of the following" must be supported, clearly that would be satisfied if an implementation returns true for #SVG-all but not for #SVG-static-DOM. http://www.w3.org/Graphics/SVG/feature/1.2/#SVG-static-DOM for example corresponds to the <script> and <handler> elements. It is not clear when these are considered "supported", does it mean that the user agent can successfully ignore the elements, or that it supports one language binding for use with these elements and all SVG uDOM features? Please change the draft such that all of this is explicitly defined. regards, -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Monday, 4 July 2005 02:26:55 UTC