Re: </optional> element

On Mon, 2006-16-10 at 13:18 -0400, Joel M. Halpern wrote:
> The LFB Class definition (and structure definitions) needs an 
> indication of whether a given element is mandatory or optional.
> We have that defined as an <optional/> element.
> We could instead have done it as an attribute of the element 
> declaration itself.
> 
> The element accessibility property tells whether the element is 
> permitted / supported, thus indicating to the CE whether the FE 
> supports that optional element. (Independent of whether it is present or not.)
> 
> So, I think what you are asking for is already covered?
> 

For some reason my brain was triggered by Weiming's comments (on abuse
of resources) into computing that the <optional/> detail requires to
have memory allocation in an implementation. It doesnt (unlike the
accessibility property). So ignore what i said.

cheers,
jamal