- From: John Foliot <foliot@wats.ca>
- Date: Wed, 20 Aug 2008 14:50:20 -0700
- To: "'Laura Carlson'" <laura.lee.carlson@gmail.com>, "'Al Gilman'" <Alfred.S.Gilman@ieee.org>
- Cc: "'Ian Hickson'" <ian@hixie.ch>, "'W3C WAI-XTECH'" <wai-xtech@w3.org>
Laura Carlson wrote:
>
> The Specification Guidelines in the W3C QA Framework advise
> specification authors to:
>
> "Provide as much information as possible to narrow the allowable
> choices and to increase predictability...Narrowing choices and
> increasing predictability enhance the likelihood of interoperability
> since the implementer chooses from a reduced sample space. Narrowing
> choices, providing more information, and eliminating incorrect
> choices increases the chances of correct implementations. An
> enumerated list of values is one way to constrain the choice of
> optionality."
>
> Does "when possible" meets W3C QA Framework guidelines?
>
All things are potentially possible ('tis a question of time and resources,
and ROI), and as Ian himself suggests:
)\._.,--....,'``. fL
/, _.. \ _\ ;`._ ,.
"Things that are impossible just take longer." `._.-(,_..'--(,_..'`-.;.'
<smile>
JF
Received on Wednesday, 20 August 2008 21:52:13 UTC