W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > August 2008

Re: p:option not required without default value

From: Jeni Tennison <jeni@jenitennison.com>
Date: Fri, 29 Aug 2008 22:09:34 +0100
Cc: "public-xml-processing-model-wg WG" <public-xml-processing-model-wg@w3.org>
Message-Id: <7D3609E0-187E-4EF9-8DB2-1EDBB1E37CB6@jenitennison.com>
To: "Innovimax SARL" <innovimax@gmail.com>

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 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 29 August 2008 21:10:16 GMT