Please do not define attribute value syntaxes in terms of XSD datatypes

> Value restrictions for the state or property. These restrictions are  
> expressed in terms of XML Schema Datatypes [XSD]. The following XSD  
> Datatypes are used in this specification.
>
> 	• boolean: a true/false value, expressed in attribute values as  
> true or false.

I think defining boolean as "true" or "false" makes sense, but that's  
not what defining it in terms of XSD means! XSD also allows "  true   
", "false   ", "0", "1", "   0", etc.

Please remove the reference to XSD and define the format for the  
attribute datatypes in detail either by putting the entire definition  
in ARIA or by referencing HTML5 microsyntaxes normatively.

Please do not allow leading or trailing whitespace in booleans,  
enumerations (aka. NMTOKEN), numbers and singular IDREF values. Please  
do not import the arbitrary XSD restriction that IDs must be NCNames;  
HTML5, for example, allows a broader range of ID values.

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/

Received on Tuesday, 14 April 2009 11:38:08 UTC