- From: Jeni Tennison <jeni@jenitennison.com>
- Date: Fri, 29 Aug 2008 22:09:34 +0100
- To: "Innovimax SARL" <innovimax@gmail.com>
- Cc: "public-xml-processing-model-wg WG" <public-xml-processing-model-wg@w3.org>
Mohamed, On 29 Aug 2008, at 22:02, Innovimax SARL wrote: > On Fri, Aug 29, 2008 at 10:23 PM, Jeni Tennison > <jeni@jenitennison.com> wrote: >> So what >> about: >> >> * in the declaration of an atomic step >> * the required attribute is used to indicate whether the option is >> required or not > > ok > >> * the select attribute may be used to declare a default value; if >> it's >> not specified the default is implementation-defined > > ok > >> >> * in the declaration of a pipeline >> * if the select attribute is present, it's used as a default >> value (and >> required must be 'no') > > ok > >> * if the select attribute is not present, required must be 'yes', >> and >> defaults to that value if it's not specified > > shouldn't this one be > > * if the select attribute is not present, required must be 'yes', so > there's no need for defaulting I was meaning that 'required' would default to 'no' (so if select was present you could specify required="no" and that's OK, or not specify the required attribute at all, but if you specified required="yes" then you'd get an error). Jeni -- Jeni Tennison http://www.jenitennison.com
Received on Friday, 29 August 2008 21:10:16 UTC