- From: Ian Hickson <ian@hixie.ch>
- Date: Wed, 14 Dec 2005 06:50:46 +0000 (UTC)
- To: www-svg@w3.org
The Basic Data Types chapter (chapter 4) lacks UA conformance criteria. It states what the syntaxes are, but does not describe how to parse them. For example, what are the parsing rules for <list of xxx>? How should multiple commas in a row be parsed? Similarly with <xslt-qnames>: What if the prefix used is not declared? Where does it say that UAs must parse keywords case-sensitively? (There are requirements on content authors in the Styling chapter, but I can't find any matching requirements for UAs.) Please update the draft to give precise conformance criteria for user agents stating how each value is to be parsed, including covering details like how to handle leading and trailing whitespace, being explicit about what parse errors consist unsupported values (resulting in the attribute being ignored) and which parse errors should be handled in particular ways (without dropping the value), stating what the rules regarding case sensitivity are, and so forth. Note that there is currently a statement that the normative reference for syntax rules is the CSS2 specification, but this is clearly inaccurate, since: * SVG 1.2 Tiny presumably doesn't use the @rule/selector/property:value syntax of CSS, * CSS2 values don't acces unitless lengths, which the SVG 1.2 Tiny syntax chapter says are the only allowed syntax for lengths, * CSS2 properties and values are case-insensitive, but the SVG 1.2 Tiny styling chapter says it is case-sensitive, ...and various other things along those lines. -- Ian Hickson U+1047E )\._.,--....,'``. fL http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 14 December 2005 06:51:10 UTC