- From: Yves Savourel <ysavourel@enlaso.com>
- Date: Thu, 9 Aug 2012 09:47:35 -0600
- To: <public-multilingualweb-lt@w3.org>
Thanks for the updated text Arle. A few notes: -- For locQualityScore, locQualityCode, locQualityComment, and locQualitySeverity, since the default value is unknown why do we need a default value? (which is of a different type than an otherwise valid value) Maybe there should be no default for those attributes. -- locQualitySuggestion The default should probably be no value rather than an empty string. If we use \; to escape ; then \\ should be used to escape \. -- locQualityStatus Thanks for the addition. I'm not sure I would attach a meaning about the issue being resolved or not. To me it's just a ON/OFF toggle that may be used in various situation. We use it to hid some errors for example, then go back to them. Setting it to 'off' doesn't mean it's resolved. So it's not really a 'status'. Maybe locQualityEnabled='yes|no'? -- locQualityCode I'm getting more and more doubtful about that attribute. It has very limited interoperability value. I'm not sure it's worth having an attribute to hold it. Maybe tool should use their own attribute for their own values (data- in HTML5 and namespace in XML). And ITS should have only thing that make sense across tools. -ys
Received on Thursday, 9 August 2012 15:48:08 UTC